Return-Path: 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 ; 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 ; 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 ; 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 Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.29 List-Id: Notification list for GitHub issues related to the QUIC WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2019 12:01:13 -0000 ----==_mimepart_5c4eef04cc42a_40823fbacc2d45bc109342 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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 ----==_mimepart_5c4eef04cc42a_40823fbacc2d45bc109342 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

In advance of the Tokyo meeting, I came in here to say what @hardi= e 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 a= rguments for doing so. Addressing @marten-seemann's poin= t: yes, -transport is big (but, after the recent editorial rework, mu= ch easier to navigate, so there's that). #2364 seems t= o 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 l= anguage 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 m= ore complicated both technically and editorially, such that a separate do= cument on connection migration might even make the entire set of final do= cuments more usable. But nobody has yet suggested that (and, to make it v= ery clear, I am not suggesting that either).

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5c4eef04cc42a_40823fbacc2d45bc109342--