Re: [tsvwg] ECN experimentation draft - support adoption

Anna Brunstrom <anna.brunstrom@kau.se> Wed, 30 November 2016 22:29 UTC

Return-Path: <prvs=0142fc1608=anna.brunstrom@kau.se>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A219C129BA1 for <tsvwg@ietfa.amsl.com>; Wed, 30 Nov 2016 14:29:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 dlF7akuQtV0q for <tsvwg@ietfa.amsl.com>; Wed, 30 Nov 2016 14:29:09 -0800 (PST)
Received: from nasse.dc.kau.se (smtp.kau.se [193.10.220.39]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E4A4129B95 for <tsvwg@ietf.org>; Wed, 30 Nov 2016 14:29:09 -0800 (PST)
X-Spam-Processed: mail.kau.se, Wed, 30 Nov 2016 23:29:02 +0100 (not processed: spam filter heuristic analysis disabled)
X-MDRemoteIP: 213.113.183.118
X-MDArrival-Date: Wed, 30 Nov 2016 23:29:02 +0100
X-Authenticated-Sender: anna.brunstrom@kau.se
X-Return-Path: anna.brunstrom@kau.se
X-Envelope-From: anna.brunstrom@kau.se
X-MDaemon-Deliver-To: tsvwg@ietf.org
To: tsvwg@ietf.org
References: <CE03DB3D7B45C245BCA0D243277949362F775181@MX307CL04.corp.emc.com>
From: Anna Brunstrom <anna.brunstrom@kau.se>
Message-ID: <e280e698-499b-4070-13d4-88007d9dd657@kau.se>
Date: Wed, 30 Nov 2016 23:29:00 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <CE03DB3D7B45C245BCA0D243277949362F775181@MX307CL04.corp.emc.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/nzfJmN2QCTCTej_Fxsr49eEjodM>
Subject: Re: [tsvwg] ECN experimentation draft - support adoption
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Nov 2016 22:29:11 -0000

I support adoption. I think opening up for experimentation in this space 
will be important.

Anna


On 2016-11-30 21:04, Black, David wrote:
> I support TSVWG adoption of this draft as its author (individual comment, not in WG chair role), and I'd ask anyone else who is interested in seeing this draft and the experiments that it enables progress to also please send a note supporting adoption of this draft to the TSVWG list.
>
> Thanks in advance, --David
>
>> -----Original Message-----
>> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of Black, David
>> Sent: Wednesday, November 23, 2016 4:25 PM
>> To: tsvwg@ietf.org
>> Subject: Re: [tsvwg] The TSVWG WG has placed draft-black-tsvwg-ecn-
>> experimentation in state "Call For Adoption By WG Issued"
>>
>> Written as draft author, *not* WG chair, here are a few more details.
>>
>>> Following discussion at the IETF meeting in Seoul, this email starts a
>>> formal adoption call for the above process draft. The draft, if adopted
>>> will form the *BASIS* for a PS Update to RFC 3168, allowing the way for
>>> experimentation using the ECT codepoint by publication of Experimental
>>> RFCs. The document also proposes ending the previous IETF experiment
>>> known as the "ECN Nonce".
>> This draft also enables experimentation with different sender responses
>> to ECN-detected congestion (CE-marked packets) by comparison to drops,
>> and with use of ECN on TCP control packets and retransmitted packets.
>> Drafts for these two areas of experimentation are being handled by
>> the TCPM WG - in contrast, L4S is expected to be handled by the TSVWG
>> WG.  Also, the ECT codepoint intended for experimentation is ECT(1).
>>
>> I want to emphasize "*BASIS*" above.  This is only an adoption call - the text
>> in this draft will almost certainly be modified before the WG is done with this
>> draft.
>>
>> Opposing adoption of this draft is effectively taking the position that one or
>> more of the referenced experiments are very bad ideas that should not be
>> pursued.
>>
>> Thanks, --David
>>
>>> -----Original Message-----
>>> From: IETF Secretariat [mailto:ietf-secretariat-reply@ietf.org]
>>> Sent: Wednesday, November 23, 2016 12:27 PM
>>> To: tsvwg@ietf.org; tsvwg-chairs@ietf.org; draft-black-tsvwg-ecn-
>>> experimentation@ietf.org
>>> Subject: The TSVWG WG has placed draft-black-tsvwg-ecn-experimentation in
>>> state "Call For Adoption By WG Issued"
>>>
>>>
>>> The TSVWG WG has placed draft-black-tsvwg-ecn-experimentation in state
>>> Call For Adoption By WG Issued (entered by Gorry Fairhurst)
>>>
>>> The document is available at
>>> https://datatracker.ietf.org/doc/draft-black-tsvwg-ecn-experimentation/
>>>
>>>
>>> Comment:
>>> Following discussion at the IETF meeting in Seoul, this email starts a
>>> formal adoption call for the above process draft. The draft, if adopted
>>> will form the *BASIS* for a PS Update to RFC 3168, allowing the way for
>>> experimentation using the ECT codepoint by publication of Experimental
>>> RFCs. The document also proposes ending the previous IETF experiment
>>> known as the "ECN Nonce".
>>>
>>> Comments are welcome on the list to indicate if such a document is
>>> considered useful for the IETF to publish, or expressing concerns about
>>> any of these topics. You may also send comments on the current text (and
>>> these are welcome), but, if you do, please also clearly indicate if you
>>> support the progress of work on this topic within TSVWG.
>>>
>>> All comments need to be received by 9th Dec 2016, after which a decision
>>> will be made on how to progress. (You may read about the adoption process
>>> in RFC7221.)