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

The information below is for an old version of the document
Document Type Active Internet-Draft (intarea WG)
Last updated 2013-04-24 (latest revision 2013-04-15)
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Suresh Krishnan
Shepherd write-up Show (last changed 2013-01-22)
IESG IESG state IESG Evaluation::Revised I-D Needed
Consensus Boilerplate Unknown
Telechat date
Needs a YES.
Responsible AD Brian Haberman
Send notices to intarea-chairs@tools.ietf.org, draft-ietf-intarea-nat-reveal-analysis@tools.ietf.org
IANA IANA review state IANA - Review Needed
IANA action state None
INTAREA WG                                                  M. Boucadair
Internet-Draft                                            France Telecom
Intended status: Informational                                  J. Touch
Expires: October 18, 2013                                        USC/ISI
                                                                P. Levis
                                                          France Telecom
                                                                R. Penno
                                                                   Cisco
                                                          April 16, 2013

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

Abstract

   This document is a collection of solutions to reveal a host
   identifier (denoted as HOST_ID) when a Carrier Grade NAT (CGN) or
   application proxies are involved in the path.  This host identifier
   could be used by a remote server to sort out the packets by sending
   host.  The host identifier must be unique to each host under the same
   shared IP address.

   This document analyzes a set of solution candidates to reveal a host
   identifier; no recommendation is sketched in the document.

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 18, 2013.

Copyright Notice

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

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

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  On HOST_ID  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  HOST_ID and Privacy . . . . . . . . . . . . . . . . . . . . .   5
   4.  Detailed Solutions Analysis . . . . . . . . . . . . . . . . .   7
     4.1.  Use the Identification Field of IPv4 Header (IP-ID) . . .   7
       4.1.1.  Description . . . . . . . . . . . . . . . . . . . . .   7
       4.1.2.  Analysis  . . . . . . . . . . . . . . . . . . . . . .   7
     4.2.  Define an IP Option . . . . . . . . . . . . . . . . . . .   8
       4.2.1.  Description . . . . . . . . . . . . . . . . . . . . .   8
       4.2.2.  Analysis  . . . . . . . . . . . . . . . . . . . . . .   8
     4.3.  Define a TCP Option . . . . . . . . . . . . . . . . . . .   8
       4.3.1.  Description . . . . . . . . . . . . . . . . . . . . .   8
       4.3.2.  Analysis  . . . . . . . . . . . . . . . . . . . . . .   8
     4.4.  Inject Application Protocol Message Headers . . . . . . .  10
       4.4.1.  Description . . . . . . . . . . . . . . . . . . . . .  10
       4.4.2.  Analysis  . . . . . . . . . . . . . . . . . . . . . .  11
     4.5.  PROXY Protocol  . . . . . . . . . . . . . . . . . . . . .  11
       4.5.1.  Description . . . . . . . . . . . . . . . . . . . . .  12
       4.5.2.  Analysis  . . . . . . . . . . . . . . . . . . . . . .  12
     4.6.  Assign Port Sets  . . . . . . . . . . . . . . . . . . . .  12
       4.6.1.  Description . . . . . . . . . . . . . . . . . . . . .  12
       4.6.2.  Analysis  . . . . . . . . . . . . . . . . . . . . . .  13
     4.7.  Host Identity Protocol (HIP)  . . . . . . . . . . . . . .  13
       4.7.1.  Description . . . . . . . . . . . . . . . . . . . . .  13
       4.7.2.  Analysis  . . . . . . . . . . . . . . . . . . . . . .  13
     4.8.  Use of a Notification Channel (e.g., ICMP)  . . . . . . .  14
       4.8.1.  Description . . . . . . . . . . . . . . . . . . . . .  14
Show full document text