[Int-area] RFC 6967 on Analysis of Potential Solutions for Revealing a Host Identifier (HOST_ID) in Shared Address Deployments

rfc-editor@rfc-editor.org Tue, 18 June 2013 21:46 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B801821F85F7; Tue, 18 Jun 2013 14:46:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.48
X-Spam-Level:
X-Spam-Status: No, score=-102.48 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23kYXZO9Fie0; Tue, 18 Jun 2013 14:46:21 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 9CFC121F8425; Tue, 18 Jun 2013 14:46:17 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A927D6217D; Tue, 18 Jun 2013 14:44:06 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130618214406.A927D6217D@rfc-editor.org>
Date: Tue, 18 Jun 2013 14:44:06 -0700
Cc: int-area@ietf.org, rfc-editor@rfc-editor.org
Subject: [Int-area] RFC 6967 on Analysis of Potential Solutions for Revealing a Host Identifier (HOST_ID) in Shared Address Deployments
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2013 21:46:21 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6967

        Title:      Analysis of Potential Solutions for 
                    Revealing a Host Identifier (HOST_ID) in 
                    Shared Address Deployments 
        Author:     M. Boucadair, J. Touch,
                    P. Levis, R. Penno
        Status:     Informational
        Stream:     IETF
        Date:       June 2013
        Mailbox:    mohamed.boucadair@orange.com, 
                    touch@isi.edu, 
                    pierre.levis@orange.com,
                    repenno@cisco.com
        Pages:      24
        Characters: 53498
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-intarea-nat-reveal-analysis-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6967.txt

This document is a collection of potential solutions for revealing 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 packets according
to the sending host.  The host identifier must be unique to each host
under the same shared IP address.

This document analyzes a set of potential solutions for revealing a
host identifier and does not recommend a particular solution,
although it does highlight the hazards of some approaches.

This document is a product of the Internet Area Working Group Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC