IETF Logo Mail Archive

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

Joe Touch <touch@strayalpha.com> Tue, 05 November 2019 02:48 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D20A812004D; Mon, 4 Nov 2019 18:48:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.219
X-Spam-Level:
X-Spam-Status: No, score=-1.219 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.com
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 juEw0VAwdU6y; Mon, 4 Nov 2019 18:48:15 -0800 (PST)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (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 84D0112006B; Mon, 4 Nov 2019 18:48:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:Sender:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=MI9VPaT4MWXUkvZ3EDHHG7c+aFzawpuCBeYNDUjeBPM=; b=S99XQZIcmaScOKcfk6ijkkKHA mEQumxwXHoDAp6H0f4AYW2QRSB5VfmOr8SciQDbMAFR1angMb16MPgJ84ncLJz9pgrwfzNVwJxv6U n6JASNY8QoXSJsQpz4pFnBST1pq1qYXcprmUUqjiNEuCBFg0Bx6UgIoB+abfuzCHYgvfcKZkwyGdx ZC8RjQgezhg2YcHFBuwuPTSIM3vXWxPogrOfCbGwDPnSh9yYRQl1iqGpXh5WsqnJ/gkD9Q9y0qyv8 e4zBd4oYdZBn1Xz8LpPSUp45vc2TYF8C4JMsIkHcr8sQZSR2x6Wzs3v8+xx0BW4o+LtfCMGkcsW49 ghxULFubg==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:59561 helo=[192.168.1.10]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1iRot8-0021UN-2s; Mon, 04 Nov 2019 21:48:14 -0500
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: [tsvwg] [OPSAWG] TSVWG WGLC: draft-ietf-tsvwg-transport-encrypt-08, closes 23 October 2019
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <f2b1f803-b559-a166-8009-baff551bec5c@joelhalpern.com>
Date: Mon, 04 Nov 2019 18:48:09 -0800
Cc: Peter Gutmann <pgut001@cs.auckland.ac.nz>, "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>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7E9CB639-6CAD-4152-8927-86EC44DF5B9A@strayalpha.com>
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>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/b8gfB29C3ytC0buUG0dGHqo4IXs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2019 02:48:17 -0000


> On Nov 4, 2019, at 6:39 PM, Joel M. Halpern <jmh@joelhalpern.com> 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.

That only happens if the WG and IESG say this is out of scope for the IETF. I.e., the ISE isn’t an end-run.

IMO, given the fact that this is squarely within TSVWG and there’s no consensus, the way forward is clear.

Not every ID turns into an RFC, nor should it.

Joe

v2.23.0 | Report a Bug | By Email