Analysis of Solution Candidates to Reveal a Host Identifier (HOST_ID) in Shared Address Deployments
draft-ietf-intarea-nat-reveal-analysis-02

The information below is for an old version of the document
Document Type Active Internet-Draft (intarea WG)
Last updated 2012-04-17
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
INTAREA WG                                                  M. Boucadair
Internet-Draft                                            France Telecom
Intended status: Informational                                  J. Touch
Expires: October 20, 2012                                        USC/ISI
                                                                P. Levis
                                                          France Telecom
                                                                R. Penno
                                                                   Cisco
                                                          April 18, 2012

Analysis of Solution Candidates to Reveal a Host Identifier (HOST_ID) in
                       Shared Address Deployments
               draft-ietf-intarea-nat-reveal-analysis-02

Abstract

   This document analyzes a set of solution candidates to mitigate some
   of the issues encountered when address sharing is used.  In
   particular, this document focuses on means to reveal a host
   identifier (HOST_ID) when a Carrier Grade NAT (CGN) or application
   proxies are involved in the path.  This host identifier must be
   unique to each host under the same shared IP address.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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 20, 2012.

Copyright Notice

Boucadair, et al.       Expires October 20, 2012                [Page 1]
Internet-Draft              Revealing HOST_ID                 April 2012

   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 October 20, 2012                [Page 2]
Internet-Draft              Revealing HOST_ID                 April 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Context  . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.2.  Purpose and Scope  . . . . . . . . . . . . . . . . . . . .  4
   2.  Problem to Be Solved . . . . . . . . . . . . . . . . . . . . .  5
     2.1.  IPv6 May Also Be Concerned . . . . . . . . . . . . . . . .  6
   3.  Solutions Analysis . . . . . . . . . . . . . . . . . . . . . .  6
     3.1.  Requirements . . . . . . . . . . . . . . . . . . . . . . .  6
     3.2.  Synthesis  . . . . . . . . . . . . . . . . . . . . . . . .  6
     3.3.  Recommendation . . . . . . . . . . . . . . . . . . . . . .  9
   4.  HOST_ID and Privacy  . . . . . . . . . . . . . . . . . . . . .  9
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 11
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 11
   7.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 11
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     8.1.  Normative References . . . . . . . . . . . . . . . . . . . 11
     8.2.  Informative References . . . . . . . . . . . . . . . . . . 12
   Appendix A.  Detailed Solutions Analysis . . . . . . . . . . . . . 14
     A.1.  Use the Identification Field of IP Header (IP-ID)  . . . . 14
       A.1.1.  Description  . . . . . . . . . . . . . . . . . . . . . 14
       A.1.2.  Analysis . . . . . . . . . . . . . . . . . . . . . . . 14
     A.2.  Define an IP Option  . . . . . . . . . . . . . . . . . . . 14
Show full document text