Re: [quicwg/base-drafts] Merge normative -spin-exp text into -transport (#2369)

Brian Trammell <notifications@github.com> Mon, 28 January 2019 12:01 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1412A131026 for <quic-issues@ietfa.amsl.com>; Mon, 28 Jan 2019 04:01:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.553
X-Spam-Level:
X-Spam-Status: No, score=-12.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 H73UaBiIPI-K for <quic-issues@ietfa.amsl.com>; Mon, 28 Jan 2019 04:01:10 -0800 (PST)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4B22131023 for <quic-issues@ietf.org>; Mon, 28 Jan 2019 04:01:09 -0800 (PST)
Date: Mon, 28 Jan 2019 04:01:08 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1548676868; bh=41owG0MblFrXO99r5Q1tKTIKFQy8J3I0zTeJrwK9hZA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HfyadJH3V+S+aCTeT22Ns8KbzfTmODo65Yk9SQBRmS+X+5sw+eGNkcXbET3yDMoKY +3bCNnGqZkLqOeCGnwFV98vrbo9UzCUYYZQSdton1DE3gPAYQ/NXze25bIb/mO5Ix7 QUaAJuy1Y33qEeLvkI74fEFXdr8EdimWOKlNbvus=
From: Brian Trammell <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab7d77d65f5b3f784ee9a9c87cbd10493202d1c0d092cf000000011866b10492a169ce17ff5580@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2369/458105065@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2369@github.com>
References: <quicwg/base-drafts/issues/2369@github.com>
Subject: Re: [quicwg/base-drafts] Merge normative -spin-exp text into -transport (#2369)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c4eef04cc42a_40823fbacc2d45bc109342"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: britram
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Maz5Mbir6asXbvK17mFV0jRP5yY>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jan 2019 12:01:13 -0000

In advance of the Tokyo meeting, I came in here to say what @hardie said. On review the std/exp question was pretty clearly answered in BKK.

I personally don't care deeply whether the normative bits of the spin bit live in -transport or in their own document, though I don't buy the arguments for doing so. Addressing @marten-seemann's point: yes, -transport is big (but, after the recent editorial rework, *much* easier to navigate, so there's that). #2364 seems to weigh in at ~2 old-style pages, so while all efforts to reduce document size are appreciated, I don't think not adding the spin bit generation language will make a material difference. Other strictly-optional features of the transport protocol are not separated out. For example, connection migration is strictly-speaking optional on the client side, and is far more complicated both technically and editorially, such that a separate document on connection migration might even make the entire set of final documents more usable. But nobody has yet suggested that (and, to make it very clear, I am not suggesting that either).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/2369#issuecomment-458105065