Re: [quicwg/base-drafts] Merge normative -spin-exp text into -transport (#2369)
mirjak <notifications@github.com> Thu, 24 January 2019 09:52 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 3B8DC130FCD for <quic-issues@ietfa.amsl.com>; Thu, 24 Jan 2019 01:52:48 -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 7EimRj6kIApx for <quic-issues@ietfa.amsl.com>; Thu, 24 Jan 2019 01:52:46 -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 49CB5130EB3 for <quic-issues@ietf.org>; Thu, 24 Jan 2019 01:52:46 -0800 (PST)
Date: Thu, 24 Jan 2019 01:52:45 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1548323565; bh=i2vmmR4jpXSDWfwT3NLiAqQHBDsK1MTKtZKBaifzGy8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GWtiB3TZ47WfRXKqV/kcf6gNOJGVwhxLJUHAwLZ2lhhiXB07V6yh07F0S5DGJREMN vRM9jYhjc/lP2zecPySF/FsqNO3a/yZRd0SW0+DY7ApgKinWwGDOUHAgcEf3vNaO4v VTvSkJKqodZIULWt4Kc85g53M3Kqk/ke+Ty5pFaM=
From: mirjak <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab5691e4e645a82af9cefa3afef3842f5816c99c3792cf0000000118614ced92a169ce17ff5580@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/457135370@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_5c498aed29f75_39583fc1342d45bc884110"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mirjak
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/S5P42NY1HCQmXoQevNMSImjhE_E>
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 09:52:48 -0000
My understanding was always that the plan was to merge this into the transport doc and never that the the spin-exp is meant to be published as an own doc. The chairs only hold us at some point to create an own doc (instead of trying to get an PR up to date) such that it is easier to people to experiment until we have a final decision and merge it in. We even had a hum on this in Bangkok: 6. To include the spin bit in the specification, as laid out here. Some decisions can still be made. Yes: Strong hum (4-5 hums for inclusion, no against) No: Medium-Strong hum (less) I asked at the end of the session if we are ready to merge and got a yes. I don't know what this discussion is about because we really have already clear consensus here. I will close the issue. -- 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-457135370
- [quicwg/base-drafts] Merge normative -spin-exp te… Brian Trammell
- Re: [quicwg/base-drafts] Merge normative -spin-ex… Brian Trammell
- Re: [quicwg/base-drafts] Merge normative -spin-ex… Brian Trammell
- Re: [quicwg/base-drafts] Merge normative -spin-ex… mirjak
- Re: [quicwg/base-drafts] Merge normative -spin-ex… Marcus Ihlar
- Re: [quicwg/base-drafts] Merge normative -spin-ex… Marten Seemann
- Re: [quicwg/base-drafts] Merge normative -spin-ex… Brian Trammell
- Re: [quicwg/base-drafts] Merge normative -spin-ex… Kazuho Oku
- Re: [quicwg/base-drafts] Merge normative -spin-ex… Marcus Ihlar
- Re: [quicwg/base-drafts] Merge normative -spin-ex… Loganaden Velvindron
- Re: [quicwg/base-drafts] Merge normative -spin-ex… hardie
- Re: [quicwg/base-drafts] Merge normative -spin-ex… Jana Iyengar
- Re: [quicwg/base-drafts] Merge normative -spin-ex… hardie
- Re: [quicwg/base-drafts] Merge normative -spin-ex… Brian Trammell
- Re: [quicwg/base-drafts] Merge normative -spin-ex… Roni Even
- Re: [quicwg/base-drafts] Merge normative -spin-ex… Martin Thomson
- Re: [quicwg/base-drafts] Merge normative -spin-ex… Martin Thomson