IETF Logo Mail Archive

Re: [quicwg/base-drafts] Tweak the split between quic-transport and quic-tls drafts (#3717)

Martin Thomson <notifications@github.com> Fri, 18 September 2020 00:10 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 0BB193A0F77 for <quic-issues@ietfa.amsl.com>; Thu, 17 Sep 2020 17:10:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level:
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.695, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 vJEUGCCpr_AT for <quic-issues@ietfa.amsl.com>; Thu, 17 Sep 2020 17:10:06 -0700 (PDT)
Received: from out-26.smtp.github.com (out-26.smtp.github.com [192.30.252.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CC113A0F75 for <quic-issues@ietf.org>; Thu, 17 Sep 2020 17:10:06 -0700 (PDT)
Received: from github-lowworker-292e294.va3-iad.github.net (github-lowworker-292e294.va3-iad.github.net [10.48.102.70]) by smtp.github.com (Postfix) with ESMTP id 281815E0E7A for <quic-issues@ietf.org>; Thu, 17 Sep 2020 17:10:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1600387805; bh=WwSWhxltecEfRJId2hhR1el0gksYRv16zj1F5kSISq8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=A2XN2nGvfb9EBVZkkGIDK/V79zfHhTWBBpd07PnQuER5hmfYIx+a1zz1ucpAKpwdN ev8CXPZGjjHIVPl1xmW+U3UuB9A54CcFQkaodjSekqtbdXvVsT2nKn9AnzZzm9FKau fNXGwOGmuKUydCrNHfHvJBIOMfmoCJ8xhhdNNvCM=
Date: Thu, 17 Sep 2020 17:10:05 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYOHPX2XQFAOGVB2QF5N7N53EVBNHHCLE33VA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3717/694567068@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3717@github.com>
References: <quicwg/base-drafts/issues/3717@github.com>
Subject: Re: [quicwg/base-drafts] Tweak the split between quic-transport and quic-tls drafts (#3717)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f63fadd17f82_2f0619f0410a4"; 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/JhNJEHvPUbAeoifKXWiXSN5UoQo>
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: Fri, 18 Sep 2020 00:10:08 -0000

As you say, WGLC happened.  I know that Jana wants to get some editorial work in after that (small language fixups, maybe a tiny bit of shuffling of content).  So this really comes down to one question: When do you want QUIC to be published?

Any time we allow for editorial cleanup adds directly to the time it takes to publish.  If WGLC passes this time around with no major issues, then we could immediately publish a -31 draft and make a publication request.

Second is the risk that we invalidate the WGLC when we do *any* significant amount of editorial work.  If we plan another round of calls, then this costs little.  If we don't (see above), then this carries some risk of restarting the clock.

I guess you could interpret this as "finish this before September 24 or avoid risky changes".  I don't know how realistic either one is.

-- 
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/3717#issuecomment-694567068

v2.23.0 | Report a Bug | By Email