Re: RFC6265bis status

Daniel Stenberg <daniel@haxx.se> Wed, 05 October 2016 06:03 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC6EE129537 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 4 Oct 2016 23:03:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.917
X-Spam-Level:
X-Spam-Status: No, score=-9.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 eXm3XOqFc6qJ for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 4 Oct 2016 23:03:33 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F3F9129525 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 4 Oct 2016 23:03:32 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1brfEr-0001qy-9t for ietf-http-wg-dist@listhub.w3.org; Wed, 05 Oct 2016 05:59:33 +0000
Resent-Date: Wed, 05 Oct 2016 05:59:33 +0000
Resent-Message-Id: <E1brfEr-0001qy-9t@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <daniel@haxx.se>) id 1brfEn-0001qD-PR for ietf-http-wg@listhub.w3.org; Wed, 05 Oct 2016 05:59:29 +0000
Received: from giant.haxx.se ([80.67.6.50]) by maggie.w3.org with esmtp (Exim 4.80) (envelope-from <daniel@haxx.se>) id 1brfEl-0001Ay-JL for ietf-http-wg@w3.org; Wed, 05 Oct 2016 05:59:29 +0000
Received: from giant.haxx.se (localhost.localdomain [127.0.0.1]) by giant.haxx.se (8.15.2/8.15.2/Debian-4) with ESMTPS id u955x4XW026719 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <ietf-http-wg@w3.org>; Wed, 5 Oct 2016 07:59:04 +0200
Received: from localhost (dast@localhost) by giant.haxx.se (8.15.2/8.15.2/Submit) with ESMTP id u955x49e026680 for <ietf-http-wg@w3.org>; Wed, 5 Oct 2016 07:59:04 +0200
X-Authentication-Warning: giant.haxx.se: dast owned process doing -bs
Date: Wed, 05 Oct 2016 07:59:03 +0200
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: HTTP working group mailing list <ietf-http-wg@w3.org>
In-Reply-To: <2D2BCE5A-4EFD-453F-A928-40200715E226@mnot.net>
Message-ID: <alpine.DEB.2.20.1610050751260.28134@tvnag.unkk.fr>
References: <2D2BCE5A-4EFD-453F-A928-40200715E226@mnot.net>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Received-SPF: pass client-ip=80.67.6.50; envelope-from=daniel@haxx.se; helo=giant.haxx.se
X-W3C-Hub-Spam-Status: No, score=-7.5
X-W3C-Hub-Spam-Report: AWL=1.327, BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.64, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: maggie.w3.org 1brfEl-0001Ay-JL 66b05f6cb8e1e4b1df91a0e85a11fd32
X-Original-To: ietf-http-wg@w3.org
Subject: Re: RFC6265bis status
Archived-At: <http://www.w3.org/mid/alpine.DEB.2.20.1610050751260.28134@tvnag.unkk.fr>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/32477
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

On Wed, 5 Oct 2016, Mark Nottingham wrote:

> It seems like we're at a point where we can start incorporating the draft 
> proposals into a complete document, so that we can see how it works as a 
> whole, identify any remaining issues, and discuss them

We ran into an interesting cookie issue the other day in curl. Namely how to 
deal with two otherwise identically named cookies where the domain property 
differs only in a leading dot or not:

   https://curl.haxx.se/mail/lib-2016-09/0103.html

The two points being:
  1 - Are they two cookies or one?
  2 - In which order should they be sent by the client if two.

A revised spec should probably detail this too so that browsers (and others) 
will align.

-- 

  / daniel.haxx.se