[apps-discuss] FW: New Version Notification for draft-vyncke-v6ops-happy-eyeballs-cookie-01.txt
"Eric Vyncke (evyncke)" <evyncke@cisco.com> Fri, 06 March 2015 14:12 UTC
Return-Path: <evyncke@cisco.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF8081ACE12 for <apps-discuss@ietfa.amsl.com>; Fri, 6 Mar 2015 06:12:31 -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 Ah4lZhlTl-hH for <apps-discuss@ietfa.amsl.com>; Fri, 6 Mar 2015 06:12:25 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEA2A1A0419 for <apps-discuss@ietf.org>; Fri, 6 Mar 2015 06:12:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3658; q=dns/txt; s=iport; t=1425651146; x=1426860746; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=L+NgwdMsGR1BdA1IsN7LsbY3CLyyBUdUpqqAhi61QUg=; b=YGSL8fEhuMSByTnZNDRGe1XPiR9LBIiR5z4fduLtghx7+4jegN2g5/qy mb+UbdnqpsZQMmTt/CQrKE/XpvlBRMausJVZ/O3Avh1ESRVdUtHJ9joAZ XQSdrYT0evWAnfjKiYiPGRV8gl9Lh1JY7tUA3dD6bCQTYdRj6OHdbNBuo o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CmBgCAtflU/5BdJa1cgwZSVQUEgwa+aIVuAhyBHU0BAQEBAQF8hBABAQQjETMQEgIBCBoCJgICAjAVBgEGAwIEEwmIJggFtAWaVgEBAQEBAQQBAQEBAQEBG4EhiXaEJVCCaIFDBZAHg2OFaoEaOYJtjy8jgjKBPG+BA0F/AQEB
X-IronPort-AV: E=Sophos;i="5.11,353,1422921600"; d="scan'208";a="129555474"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-7.cisco.com with ESMTP; 06 Mar 2015 14:12:25 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t26ECOKT012326 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <apps-discuss@ietf.org>; Fri, 6 Mar 2015 14:12:24 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.138]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.03.0195.001; Fri, 6 Mar 2015 08:12:24 -0600
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Thread-Topic: New Version Notification for draft-vyncke-v6ops-happy-eyeballs-cookie-01.txt
Thread-Index: AQHQV+OAmfOoS9exuUuMXePFUNM3gp0P9LIA
Date: Fri, 06 Mar 2015 14:12:22 +0000
Message-ID: <D11F722B.3F1D4%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: <D5C70AD6CE8C8940910FC719487307FF@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/4Cg8W_X4N6q75AZeI11BQuXDbL4>
Subject: [apps-discuss] FW: New Version Notification for draft-vyncke-v6ops-happy-eyeballs-cookie-01.txt
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss/>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2015 14:12:32 -0000
You may find this short I-D interesting: it is related to all application using cookie (or any state) linked on an IP address in a world where user agents are dual-stack, are NAT by carrier-grade NAT, are multi-homed, ... => the mapping IP_address <=> user which was never correct is becoming more and more wrong :-) Comments are obviously welcome -é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 >
- [apps-discuss] FW: New Version Notification for d… Eric Vyncke (evyncke)