HOST_ID: Use Cases
draft-boucadair-intarea-host-identifier-scenarios-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-10-17
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
IETF conflict review conflict-review-boucadair-intarea-host-identifier-scenarios
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
INTAREA Working Group                                       M. Boucadair
Internet-Draft                                                  D. Binet
Intended status: Informational                                  S. Durel
Expires: April 20, 2013                                   France Telecom
                                                                T. Reddy
                                                                   Cisco
                                                        October 17, 2012

                           HOST_ID: Use Cases
          draft-boucadair-intarea-host-identifier-scenarios-01

Abstract

   This document describes a set of scenarios in which host
   identification is required.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 20, 2013.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Boucadair, et al.        Expires April 20, 2013                 [Page 1]
Internet-Draft              Host ID Use Cases               October 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Scope  . . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Use Case 1: CGN  . . . . . . . . . . . . . . . . . . . . . . .  4
   4.  Use Case 2: A+P  . . . . . . . . . . . . . . . . . . . . . . .  4
   5.  Use Case 3: Application Proxies  . . . . . . . . . . . . . . .  5
   6.  Use Case 4: Open Wi-Fi or Provider Wi-Fi . . . . . . . . . . .  6
   7.  Use Case 5: Policy and Charging Control Architecture . . . . .  7
   8.  Use Case 6: Cellular Networks  . . . . . . . . . . . . . . . .  8
   9.  Use Case 7: Femtocells . . . . . . . . . . . . . . . . . . . .  9
   10. Security Considerations  . . . . . . . . . . . . . . . . . . . 10
   11. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
   12. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 10
   13. Informative References . . . . . . . . . . . . . . . . . . . . 10
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11

Boucadair, et al.        Expires April 20, 2013                 [Page 2]
Internet-Draft              Host ID Use Cases               October 2012

1.  Introduction

   The ultimate goal of this document is to enumerate scenarios which
   encounter the issue of uniquely identifying a host among those
   sharing the same IP address.  Examples of encountered issues are:

   o  Blacklist a misbehaving host without impacting all hosts sharing
      the same IP address.

   o  Enforce a per-subscriber/per-UE policy (e.g., limit access to the
      service based on some counters such as volume-based service
      offering); enforcing the policy will have impact on all hosts
      sharing the same IP address.

   o  If invoking a service has failed (e.g., wrong login/passwd), all
      hosts sharing the same IP address may not be able to access that
      service.

   o  Need to correlate between the internal address:port and external
      address:port to generate and therefore to enforce policies.

   It is out of scope of this document to list all the encountered
   issues as this is already covered in [RFC6269].

   The generic concept of host identifier, denoted as HOST_ID, is
   defined in [I-D.ietf-intarea-nat-reveal-analysis].

   The analysis of the use cases listed in this document indicates two
   root causes for the host identification issue:

   1.  Presence of address sharing (NAT, A+P, application proxies,
       etc.).

   2.  Use of tunnels between two administrative domains.
Show full document text