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

Brian Trammell <notifications@github.com> Thu, 24 January 2019 08:33 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 BDBA1130E58 for <quic-issues@ietfa.amsl.com>; Thu, 24 Jan 2019 00:33:36 -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 36fFZodeYzQF for <quic-issues@ietfa.amsl.com>; Thu, 24 Jan 2019 00:33:35 -0800 (PST)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 171BE130E2B for <quic-issues@ietf.org>; Thu, 24 Jan 2019 00:33:35 -0800 (PST)
Date: Thu, 24 Jan 2019 00:33:32 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1548318812; bh=kzmqO0kHgyZC77bm9bU7G0hLHGFSLgFAW5XggAJetcQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=FOyIG8jUpY8mVoroI7F2m/oejy1Sp5cxqCnqKHa27rQY/GBGOCrrKyvZx9/ZPB3sE 73UiyKYAFQWqwoG4Gwqo44RpGmy5tYDac/C9qM2hr74kjMwTlwx5i82raJyo2xGilk fjkhHwMzYhywaJdauUEIaNHEMPArzit4gQ7MQ45I=
From: Brian Trammell <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab54af65814ab0d0a78f2fa874b7a58ac1fcd5d3c592cf0000000118613a5c92a169ce17fa7dfa@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/c457110759@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_5c49785cb8b66_2b073f822b4d45bc4941cd"; 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/UlVvCX37njXuPOSZJsZAuQhfB3M>
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 08:33:37 -0000

haven’t had a chance to review the PR in detail yet, should do so today.

On document status, my understanding is:

- in London, we decided to adopt the spin bit as an experimental feature within the working group to generate more experience to inform an eventual adoption decision.

- in Bangkok, we achieved rough consensus to adopt the feature into the base protocol. The plan as I understood it is that documents were to be held separate until the spin-exp document reflected Bangkok consensus and the transport document was done with large-scale technical changes, after which they would be merged. This plan together the discussion about 2119 language made it clear to me that the spin bit would be proposed standard.

This PR does the merge, because the conditions (less transport change in the future, spin bit now reflects the consensus about probabilistic participation) have been met.

While general guidelines on on-path use of the signal belongs in the (informational) manageability draft, details about how exactly to generate metrics from this signal are IMO more experimental, and probably fit better over in IPPM (personal opinion, not a ruling from the chair)

-- 
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-457110759