[v6ops] FW: New Version Notification for draft-vyncke-v6ops-happy-eyeballs-cookie-01.txt

"Eric Vyncke (evyncke)" <evyncke@cisco.com> Fri, 06 March 2015 13:52 UTC

Return-Path: <evyncke@cisco.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F3781ACD4D for <v6ops@ietfa.amsl.com>; Fri, 6 Mar 2015 05:52:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6BZa4vyujEzh for <v6ops@ietfa.amsl.com>; Fri, 6 Mar 2015 05:52:23 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E45C1A1DBE for <v6ops@ietf.org>; Fri, 6 Mar 2015 05:52:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3520; q=dns/txt; s=iport; t=1425649943; x=1426859543; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=jjDJsJDEaaT9c4nlLhTSN49+t7OkwfF0NLpLMSDL7kg=; b=T4WGKOTCzRUZh6AAfg4ojcyfdTVlrwfBjEK+v0gCkhIwTPgTzWvOPmqZ 96zlBqxw/tpFThtbaNXviaq254giAG/90f+JVBFaJTaMBts3A4L5Z+ea+ hZ51PBQl28TeMXsan4yy7WWxu/YuxoSoJCq8hTXeN47xkukMBOi+pylkm U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CmBgCzsPlU/5xdJa1cgwZSVQUEgwa+aIVuAhyBHU0BAQEBAQF8hBABAQQjETMQEgIBCBoCJgICAjAVBgEGAwIEEwmIJggFtCKaVQEBAQEBAQQBAQEBAQEBG4EhiXaEJVCCaIFDBZAHg2OFaoEaOYJtjy8jgjKBPG+BA0F/AQEB
X-IronPort-AV: E=Sophos;i="5.11,352,1422921600"; d="scan'208";a="129556927"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-4.cisco.com with ESMTP; 06 Mar 2015 13:52:22 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id t26DqMN2031724 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <v6ops@ietf.org>; Fri, 6 Mar 2015 13:52:22 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.138]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.03.0195.001; Fri, 6 Mar 2015 07:52:22 -0600
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: New Version Notification for draft-vyncke-v6ops-happy-eyeballs-cookie-01.txt
Thread-Index: AQHQV+OAmfOoS9exuUuMXePFUNM3gp0P7xkA
Date: Fri, 06 Mar 2015 13:52:20 +0000
Message-ID: <D11F6F36.3F1BF%evyncke@cisco.com>
References: <20150306075938.24593.60303.idtracker@ietfa.amsl.com>
In-Reply-To: <20150306075938.24593.60303.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.6.141106
x-originating-ip: [10.55.185.71]
Content-Type: text/plain; charset="utf-8"
Content-ID: <79E5C700BFA2014CA5C12952D87C7EF6@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/dmX55CYcTJO1C5Ra8ivVWNoyqAw>
Subject: [v6ops] FW: New Version Notification for draft-vyncke-v6ops-happy-eyeballs-cookie-01.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2015 13:52:25 -0000

As discussed earlier, here is a -01 version adding numerous comments to be
accurate and making it more generic (hence changing the title but not the
filename).

Not sure whether it should be a WG document though.

Comments are welcome of course

-éric

On 6/03/15 08:59, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
wrote:

>
>A new version of I-D, draft-vyncke-v6ops-happy-eyeballs-cookie-01.txt
>has been successfully submitted by Eric Vyncke and posted to the
>IETF repository.
>
>Name:		draft-vyncke-v6ops-happy-eyeballs-cookie
>Revision:	01
>Title:		HTTP State Management Mechanisms with Multiple Addresses User
>Agents
>Document date:	2015-03-06
>Group:		Individual Submission
>Pages:		7
>URL:            
>http://www.ietf.org/internet-drafts/draft-vyncke-v6ops-happy-eyeballs-cook
>ie-01.txt
>Status:         
>https://datatracker.ietf.org/doc/draft-vyncke-v6ops-happy-eyeballs-cookie/
>Htmlized:       
>http://tools.ietf.org/html/draft-vyncke-v6ops-happy-eyeballs-cookie-01
>Diff:           
>http://www.ietf.org/rfcdiff?url2=draft-vyncke-v6ops-happy-eyeballs-cookie-
>01
>
>Abstract:
>   HTTP servers usually save session states in their persistent storage
>   indexed by session cookies generated by the HTTP servers.  It is up
>   to the HTTP user-agent to send this session cookie on each HTTP
>   request.  Some HTTP servers check whether the cookie is associated
>   with the HTTP user-agent by the means of the user-agent IP address.
>   Everything linking a state to an IP address (such as OAuth access
>   code) to an IP address has the same issue.
>
>   If the Happy Eyeball mechanism is used to select between IPv6 and
>   IPv4, it may happen that while using the same HTTP server, some HTTP
>   requests are done over IPv6 and the others over IPv4, which leads to
>   two different sets of session states in the HTTP server.  This has
>   the consequence of inconsistencies at the HTTP server.
>
>   The only purpose of this document is to document this issue in more
>   details than in section 8.2 of RFC 6883 including security
>   considerations and mitigations.
>
>   A similar problem arises with the use of non RFC 6888 compliant
>   Carrier-Grade NAT (CGN) devices used to access an IPv4-only HTTP
>   server or HTTP user-agent using multi-homing.
>
>                  
>        
>
>
>Please note that it may take a couple of minutes from the time of
>submission
>until the htmlized version and diff are available at tools.ietf.org.
>
>The IETF Secretariat
>