Host Identification: Use Cases
draft-boucadair-intarea-host-identifier-scenarios-05

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-04-11
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)
Network Working Group                                  M. Boucadair, Ed.
Internet-Draft                                                  D. Binet
Intended status: Informational                                  S. Durel
Expires: October 13, 2014                                     B. Chatras
                                                          France Telecom
                                                                T. Reddy
                                                                   Cisco
                                                             B. Williams
                                                            Akamai, Inc.
                                                             B. Sarikaya
                                                                  L. Xue
                                                                  Huawei
                                                          April 11, 2014

                     Host Identification: Use Cases
          draft-boucadair-intarea-host-identifier-scenarios-05

Abstract

   This document describes a set of scenarios in which host
   identification is problematic.  The document does not include any
   solution-specific discussion.

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 October 13, 2014.

Copyright Notice

   Copyright (c) 2014 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

Boucadair, et al.       Expires October 13, 2014                [Page 1]
Internet-Draft              Host ID Use Cases                 April 2014

   (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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   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. Use Case 8: Overlay Network . . . . . . . . . . . . . . . . .  10
   11. Use Case 9: Emergency Calls . . . . . . . . . . . . . . . . .  12
   12. Use Case 10: Traffic Detection Function . . . . . . . . . . .  13
   13. Use Case 11: Fixed and Mobile Network Convergence . . . . . .  14
   14. Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . .  17
   15. Privacy Considerations  . . . . . . . . . . . . . . . . . . .  17
   16. Security Considerations . . . . . . . . . . . . . . . . . . .  17
   17. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
   18. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  18
   19. Informative References  . . . . . . . . . . . . . . . . . . .  18
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  20

1.  Introduction

   The goal of this document is to enumerate use cases which encounter
   the issue of uniquely identifying a host among those sharing the same
   IP address.  Examples of encountered issues in those use cases 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/password), all
Show full document text