Re: [quicwg/base-drafts] Moving text on spinbit into transport (#2364)

Martin Thomson <notifications@github.com> Thu, 24 January 2019 01:09 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 922C7130F8B for <quic-issues@ietfa.amsl.com>; Wed, 23 Jan 2019 17:09:26 -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 cFPHOg5TjKIT for <quic-issues@ietfa.amsl.com>; Wed, 23 Jan 2019 17:09:24 -0800 (PST)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AF2C129BBF for <quic-issues@ietf.org>; Wed, 23 Jan 2019 17:09:24 -0800 (PST)
Date: Wed, 23 Jan 2019 17:09:23 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1548292163; bh=ioVtuOaN2xVD212so5r7G6LDo9KTPEtpvLBAYE7EtEU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=09zXcDHh9Xiu5rap4cBkNqOjbLQsZ5P14Vyvw8MDj6faHjpgBDrwS8LgwXSdkav6R IaHjB6h2OAZZWkXn4yUMihGOGHHQ/Fid5vPd/kPZ+WChJapysNHBToY4vyzWktDd9P m4oD+xGOs2JLTVvJtnbP7aPsXcoT/JaRQ2wRKNz0=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab5ef9bfbf24c72a1a031a6e565b006e95685eb9b692cf000000011860d24392a169ce17fa7dfa@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2364/c457027594@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2364@github.com>
References: <quicwg/base-drafts/pull/2364@github.com>
Subject: Re: [quicwg/base-drafts] Moving text on spinbit into transport (#2364)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c49104385a6a_5aa3fd0828d45b87103f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/szkvk39Ut0qf-Z-Len7cv21fgM8>
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: Thu, 24 Jan 2019 01:09:27 -0000

I think that this is one editorial discussion where I would like to see some discussion.

For me, the question of document organization is secondary to a question of status.  I think that we should target the spin bit document at experimental status, not proposed standard, which would make keeping the split between documents much more appropriate.  I'm sure that others will disagree with this position, so I think that discussion is very much warranted.

Incidentally, the change from exp to std in the document is in a commit entitled "typofix", done late last year by @britram.  I was - until just now when I checked - under the impression that the goal was an experimental RFC.  I suspect that we had a discussion on this point that settled on standards track, but I'm just remembering badly.

After that, then I think we want to talk about where this slots into the current document.  I'm not sure that the place that is selected here is right, but I want to get the big ticket questions out of the way first.

-- 
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/pull/2364#issuecomment-457027594