Re: [tsvwg] [OPSAWG] TSVWG WGLC: draft-ietf-tsvwg-transport-encrypt-08, closes 23 October 2019

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Tue, 05 November 2019 10:26 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
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 57CB01208B1; Tue, 5 Nov 2019 02:26:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 96pqZCMY__5d; Tue, 5 Nov 2019 02:26:51 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:42:150::2]) by ietfa.amsl.com (Postfix) with ESMTP id 12B661208AA; Tue, 5 Nov 2019 02:26:50 -0800 (PST)
Received: from gorry-mac.erg.abdn.ac.uk (unknown [IPv6:2001:630:42:110:e55f:a14f:6fbb:b4cc]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id BF6AB1B001D2; Tue, 5 Nov 2019 10:26:39 +0000 (GMT)
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Peter Gutmann <pgut001@cs.auckland.ac.nz>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, "IETF IPPM WG (ippm@ietf.org)" <ippm@ietf.org>, tsvwg-chairs <tsvwg-chairs@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>, "quic@ietf.org" <quic@ietf.org>, "saag@ietf.org" <saag@ietf.org>
References: <CE03DB3D7B45C245BCA0D2432779493630766752@MX307CL04.corp.emc.com> <4460_1571933453_5DB1CD0D_4460_57_4_5AE9CCAA1B4A2248AB61B4C7F0AD5FB931F030A0@OPEXCAUBM44.corporate.adroot.infra.ftgroup> <1572918247420.10381@cs.auckland.ac.nz> <CABcZeBPy_39o37snzy8F6iyLQMg1aGkYbhy0A1N-PxFUmAmB0g@mail.gmail.com> <f2b1f803-b559-a166-8009-baff551bec5c@joelhalpern.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <5df30dd2-6841-7140-43bf-8c1b9603653f@erg.abdn.ac.uk>
Date: Tue, 5 Nov 2019 10:26:39 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <f2b1f803-b559-a166-8009-baff551bec5c@joelhalpern.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/MkdJUPELttoF4tOh3nYjJn2KIsQ>
Subject: Re: [tsvwg] [OPSAWG] TSVWG WGLC: draft-ietf-tsvwg-transport-encrypt-08, closes 23 October 2019
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 05 Nov 2019 10:26:53 -0000

Thanks for the various comments on process.

I expect both editors and the Chairs to work with our AD to confirm the 
intended scope, and then to decide on the next steps. This author wants 
to clarify how IETF transport protocols have been designed and have 
been/are being used.

Gorry (as one of the editors of this document).


On 05/11/2019 02:39, Joel M. Halpern wrote:
> If the authors want to publish it as an RFC so as to comment on other 
> RFCs, they could approach the Independent Stream Editor.  That sort of 
> publication is one of the explicit purposes of the Independent Stream.
>
> Yours,
> Joel
>
> On 11/4/2019 9:34 PM, Eric Rescorla wrote:
>>
>>
>> On Mon, Nov 4, 2019 at 5:44 PM Peter Gutmann 
>> <pgut001@cs.auckland.ac.nz <mailto:pgut001@cs.auckland.ac.nz>> wrote:
>>
>>     I actually think it's a pretty good summary, and delivers exactly 
>> what's
>>     promised in the title.  OTOH I can also see that it's going to get
>>     bikeshedded
>>     to death, and will probably never be editable into a form where
>>     people won't
>>     complain about it no matter how many changes are made. 
>> Alternatively, it'll
>>     end up watered down to a point where no-one can complain any more
>>     but it won't
>>     say anything terribly useful by then.
>>
>>     Perhaps it could be published as is with a comment that it
>>     represents the
>>     opinions of the authors?  Although given that it's Informational 
>> and not
>>     Standards-track or a BCP, that should be a given anyway.
>>
>>
>> Actually, no. Most IETF documents, even informational ones, bear a 
>> statement that they have IETF Consensus.
>>
>> See: https://tools.ietf.org/html/rfc5741#section-3.2.1 
>> <https://tools.ietf.org/html/rfc5741#section-3..2.1>
>>
>> -Ekr
>>
>>
>>     Peter.
>>
>>
>>
>>
>> _______________________________________________
>> OPSAWG mailing list
>> OPSAWG@ietf.org
>> https://www.ietf.org/mailman/listinfo/opsawg
>>