Re: [Last-Call] Last Call: <draft-halpern-gendispatch-consensusinformational-02.txt> (IETF Stream Documents Require IETF Rough Consensus) to Best Current Practice

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 25 January 2020 02:28 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 028FB120227; Fri, 24 Jan 2020 18:28:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 1nb8tNHCULOx; Fri, 24 Jan 2020 18:28:36 -0800 (PST)
Received: from mail-pg1-x52c.google.com (mail-pg1-x52c.google.com [IPv6:2607:f8b0:4864:20::52c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 398141200D8; Fri, 24 Jan 2020 18:28:36 -0800 (PST)
Received: by mail-pg1-x52c.google.com with SMTP id l24so2072705pgk.2; Fri, 24 Jan 2020 18:28:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=s4rnC4LYUedmWyVX8xgvDbNnhOCnHG+5IDHnnmM++kg=; b=A7+4Pic8DKe2DYdRVdsQ2/rN2KAV+UmuM6GULKNCQliGq9VwSVRSlT6MsJwSeyeWKd T+YSw6hQZrKA1FE/odzT7vfcsEgB0h+qe9QOeMg6BUwj/SxOIcye5GDck37DE9FE0wmt rjIQAEq51hYxSv6LOHFiJM/6vnv8UvHx5WbYxuh8GLrZl3sozH79LLzE12unCCbv43NH M0Mtu5b+GIURs8fJlhSJNszo5H+4bFF8WQb5Ptni3+hJmLoD5zZJECuwWJsUrjn9t86T FDFWLa8BCcBykoVVJID+0IXB37VGCY5k29YD3KOmdl+X7CaQ36ksGoNWjl6bRcMlFf33 yT5A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=s4rnC4LYUedmWyVX8xgvDbNnhOCnHG+5IDHnnmM++kg=; b=ncD6zIVUtMAD4jrWYFeqx70FdGCrHMXpY/eieB2J2wcHrYSSZMigZWhIp8PUyn7DqL FgwzW3Q8ctAz0IVSNqBgpDrOdDfNWsYiZ41pgDITQzc1F436f6OtOpCIBpft4ARH9X4U 3g0wzMsAWsTP6Ry0BarIs4d2RzR6INEopPdGT1nhOW09WdtsL9/AfCLaJPtyhREyK+sf kroDUEOTZKX9d9hDaquf6jf60Rd1ioej/ep9yg408GEujErLPqM69OcJVUClsOdAT7ri gRO0v7HTdcqvkxRd9v9mjM9YNlbVHMW8A1/RkOZMpw4/pCvTHeSSQ5FRrF3thEAp90x3 M9KQ==
X-Gm-Message-State: APjAAAWgYAc0Gk4NJG2Y9l8uSytm4mkTXt22wgzuDRlDJRt/1AIBINAg +fMwwaeVrZYDoF6OfuGlSYGLz4Ek
X-Google-Smtp-Source: APXvYqxYYcfZL95LOepMCUg8EdBSz9H8vQ6eKIF7fdDaJ5P4POMPK88SMu86ZUtEvohP0BiAjR0K1Q==
X-Received: by 2002:a65:6088:: with SMTP id t8mr7515203pgu.329.1579919315414; Fri, 24 Jan 2020 18:28:35 -0800 (PST)
Received: from [192.168.178.30] (88.161.69.111.dynamic.snap.net.nz. [111.69.161.88]) by smtp.gmail.com with ESMTPSA id a19sm7659812pju.11.2020.01.24.18.28.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 24 Jan 2020 18:28:34 -0800 (PST)
To: Rob Sayre <sayrer@gmail.com>
Cc: Eric Rescorla <ekr@rtfm.com>, last-call@ietf.org, draft-halpern-gendispatch-consensusinformational@ietf.org
References: <CAChr6Sy5-ejdjw5zgZgiF1hSyuiAErmas-dbWFmx1b+1vftT1Q@mail.gmail.com> <CABcZeBOMVYpEYaEUzYsa0ApDfGtA6oD5P67A40=HQVBN+yTuKQ@mail.gmail.com> <CAChr6Sz7vihWaoeG8H11JzQ5YqrbYLPLneuY3PD4syMYEaKQ4w@mail.gmail.com> <CABcZeBMeuPQnUtOvxxscN2Si+s5ntx11RE-fRQararL+ePmDXA@mail.gmail.com> <34c2fd47-40b4-2126-98b1-b530b5215808@gmail.com> <CAChr6Sz6TF2H1xnkWZKC+7OaMONfxuP-51zCkkPgCdR0iBrRDw@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <aad86cb4-18d7-f331-0461-10d49b1a913c@gmail.com>
Date: Sat, 25 Jan 2020 15:28:29 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CAChr6Sz6TF2H1xnkWZKC+7OaMONfxuP-51zCkkPgCdR0iBrRDw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/hsOnxqsIXV-uWz2ogZi_AqleI88>
Subject: Re: [Last-Call] Last Call: <draft-halpern-gendispatch-consensusinformational-02.txt> (IETF Stream Documents Require IETF Rough Consensus) to Best Current Practice
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jan 2020 02:28:38 -0000

On 25-Jan-20 15:08, Rob Sayre wrote:
> 
> 
> On Fri, Jan 24, 2020 at 6:03 PM Brian E Carpenter <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
> 
>     On 25-Jan-20 14:48, Eric Rescorla wrote:
>     ...
>     >>     However, there are a bunch of ways for the IESG to block publication of IRTF or Independent Stream documents given in RFC 5742.
>     >
>     >
>     > This seems off topic for this document, which, as noted above, only refers to the IETF stream.
> 
>     Also it's inaccurate. The IESG has no blocking power. The most the IESG can do is request the Independent Stream Editor not to publish a draft, or to request them to insert a specific IESG note, but the ISE has the final say. Similarly for IRTF drafts, where authority lies with the IRSG.
> 
> 
> Has the IESG ever been crossed in this way? I've seen some RFCs with IESG disapproval notes, but nothing more.

You'd better ask that question on the rfc-interest@rfc-editor.org list.

    Brian