Re: [http-state] taking further cookie discussion to ietf-http-wg list ? (was: "Revising RFC6265"

Barry Leiba <barryleiba@computer.org> Fri, 13 November 2015 22:29 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: http-state@ietfa.amsl.com
Delivered-To: http-state@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14CA81B3364 for <http-state@ietfa.amsl.com>; Fri, 13 Nov 2015 14:29:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.256
X-Spam-Level:
X-Spam-Status: No, score=-0.256 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MALFORMED_FREEMAIL=0.001, MISSING_HEADERS=1.021, SPF_PASS=-0.001] autolearn=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 oRJuPrzktgKg for <http-state@ietfa.amsl.com>; Fri, 13 Nov 2015 14:29:54 -0800 (PST)
Received: from mail-vk0-x22e.google.com (mail-vk0-x22e.google.com [IPv6:2607:f8b0:400c:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 067F31B3363 for <http-state@ietf.org>; Fri, 13 Nov 2015 14:29:54 -0800 (PST)
Received: by vkbq142 with SMTP id q142so623724vkb.3 for <http-state@ietf.org>; Fri, 13 Nov 2015 14:29:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:cc:content-type; bh=im2TELAQrc+dQVxpTPT0hCVZ8XkXuez1eceILNdg1mI=; b=ss1qwZ65guJHv3zL1N2m5VBSaaK9SZ9SQg5O/tsue3E6pTbyj+sc08BASgfe3o0ivW vn39g22L6YAa/Lgs1s82VbQ/wGfxu6CoajiUIM6OHSBsQ4QRuSPBb4PYZzP3IiJ1YA0K J02yNHkoJLU+/ATdNgffGEOVkk6aJ9qGAp47I8reqT8BT/hk4Ydd1MhWMTJlP4ndkc8q BhDlCeSTgviOw+l099xy06bSV9bKoTEi8FIXyyyWoMtr44avTAJ6EYNZTfyoVQUtclbs amjZuoEB6kOKTIZf5eckInFIbi0Y8UjAg2ULrPGAA9w6s3Vlh6T6/BE8j3p/acTHnwJ8 xXKg==
MIME-Version: 1.0
X-Received: by 10.31.180.18 with SMTP id d18mt282371vkf.10.1447453793180; Fri, 13 Nov 2015 14:29:53 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.31.182.135 with HTTP; Fri, 13 Nov 2015 14:29:53 -0800 (PST)
In-Reply-To: <alpine.DEB.2.11.1511132302390.17326@tvnag.unkk.fr>
References: <56461C4C.2040606@KingsMountain.com> <alpine.DEB.2.11.1511132302390.17326@tvnag.unkk.fr>
Date: Sat, 14 Nov 2015 07:29:53 +0900
X-Google-Sender-Auth: g6FP3GB7VJUnJSvw1lTMnivv0_k
Message-ID: <CALaySJJ+FmHQHa5J1AwWgKAJPNkAsruE863EHovLNicF4Sv=9Q@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/http-state/uV_rk5wwb6jLWvaysPpOJJGQl1c>
Cc: Mark Nottingham <mnot@mnot.net>, HTTP State <http-state@ietf.org>
Subject: Re: [http-state] taking further cookie discussion to ietf-http-wg list ? (was: "Revising RFC6265"
X-BeenThere: http-state@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discuss HTTP State Management Mechanism <http-state.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/http-state>, <mailto:http-state-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/http-state/>
List-Post: <mailto:http-state@ietf.org>
List-Help: <mailto:http-state-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-state>, <mailto:http-state-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Nov 2015 22:29:55 -0000

>> therefore, I am thinking that we ought to close this http-state@ list to
>> further posting and place a final tombstone message here directing folks to
>> take any further cookie-related discussion to the http list
>> <ietf-http-wg@w3.org>;
>
> Sounds like a very sensible approach to me!

Yes, works for me, too.  Jeff, let me know when you think we should
take action, and I'll ask the Secretariat to do it.

Barry