Re: [quicwg/base-drafts] Describe the two processes. (9f6e285)

Mark Nottingham <> Thu, 14 February 2019 06:34 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EE658128B14 for <>; Wed, 13 Feb 2019 22:34:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Status: No, score=-8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id s8ZWJ2D8Fq2q for <>; Wed, 13 Feb 2019 22:34:20 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4EE24128766 for <>; Wed, 13 Feb 2019 22:34:20 -0800 (PST)
Date: Wed, 13 Feb 2019 22:34:19 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1550126059; bh=+VvOsgBVHLL1uGSWI+1aCFJXUlR2SQRbD+moaDNniOs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=M0Rj+ZL56Fd9wzSnHwJ+54kePWdqORnEfFuAlnkTTT7bk+iYdkhw5OkypwtjdZU72 H/xuQikv4JrtRlsx8P399MYpEXdbp9G73oqmFuDvryO77LxlEIEG34RY57TfXRBx6p DbBmfHpClm54/uuDbmTz9l4GdXF5qjU15Uifl48E=
From: Mark Nottingham <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/commit/9f6e285ad51c3439d5abd0ba24ad4ecd081c7a25/>
In-Reply-To: <quicwg/base-drafts/commit/>
References: <quicwg/base-drafts/commit/>
Subject: Re: [quicwg/base-drafts] Describe the two processes. (9f6e285)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c650bebd5f5_5bb23f88aa6d45bc1223c7"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mnot
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
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: Thu, 14 Feb 2019 06:34:22 -0000

@janaiyengar no. there are two ways to get a `has-consensus` flag:

* Under the early process, we canvas the list after the draft is published
* Under the late process, we establish consensus directly, before the issue is incorporated

Marking things as `has-consensus` without explicitly asking on the list is circumventing both of these.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: