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

Benjamin Kaduk <kaduk@mit.edu> Sat, 25 January 2020 18:45 UTC

Return-Path: <kaduk@mit.edu>
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 95B5A120044 for <last-call@ietfa.amsl.com>; Sat, 25 Jan 2020 10:45:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 XsFHoTLDTHWP for <last-call@ietfa.amsl.com>; Sat, 25 Jan 2020 10:45:56 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BA0D120048 for <last-call@ietf.org>; Sat, 25 Jan 2020 10:45:56 -0800 (PST)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 00PIjodq001440 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 25 Jan 2020 13:45:53 -0500
Date: Sat, 25 Jan 2020 10:45:50 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: Rob Sayre <sayrer@gmail.com>
Cc: "Joel M. Halpern" <jmh@joelhalpern.com>, last-call@ietf.org, Eric Rescorla <ekr@rtfm.com>
Message-ID: <20200125184550.GF77560@kduck.mit.edu>
References: <CABcZeBOMVYpEYaEUzYsa0ApDfGtA6oD5P67A40=HQVBN+yTuKQ@mail.gmail.com> <CAChr6Sz7vihWaoeG8H11JzQ5YqrbYLPLneuY3PD4syMYEaKQ4w@mail.gmail.com> <99d34ee9-8ea6-a77f-39fc-f1889a050358@joelhalpern.com> <CAChr6SwHd2=Qf2SSbQeKs1CS_c1UuBqPEtO_x4MmF71iv0zE9Q@mail.gmail.com> <CABcZeBMdonehuZ3re4UnGY2_B6A2sOBqkoE+m4SfBa8N3vYEhg@mail.gmail.com> <CAChr6Sw1LSXj=L2WAu=R1QfBi4UFDXC5Z6EODqwJ6-z9o5Z5vw@mail.gmail.com> <CABcZeBPBhGZDxnh2p=trL8yHveBiMsy38+-G_7oQu_eR+45d5w@mail.gmail.com> <CAChr6SyNTsz9uZNiN16OHLj6e=Xhcn1A8pr105Of+y_Jw8HSFw@mail.gmail.com> <994c4462-ef24-6d46-3bec-8aa5e14b9f78@joelhalpern.com> <CAChr6Sy80-74g4cgKESwmdn3WSNjU_2XsjkChH9_8-ELnytC_Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAChr6Sy80-74g4cgKESwmdn3WSNjU_2XsjkChH9_8-ELnytC_Q@mail.gmail.com>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/woBXWgAZgOWcyz0UfTLY2b-vO1w>
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 18:45:59 -0000

Apologies for the pedanticism, but there are some frequently confused
items in here (and the terminology of
https://ietf.org/about/groups/iesg/statements/iesg-discuss-criteria/ has
since evolved).

On Fri, Jan 24, 2020 at 08:25:32PM -0800, Rob Sayre wrote:
> On Fri, Jan 24, 2020 at 7:31 PM Joel M. Halpern <jmh@joelhalpern.com> wrote:
> 
> > Rob, this document deliberately addresses a very narrow issue that while
> > admittedly rare has come up a few times.
> >
> 
> It would help if you could describe the documents your draft applies to:
> 
> Document Classes Reviewed by the IESG
> 1) Protocol Actions
> 2) Document Actions (WG)
> 3) Document Actions (Individual)

This is "Individual submission to an AD" (i.e., IETF-stream AD-sponsored),
as distinct from "Independent submission to the ISE" (i.e., ISE-stream).

> 4) Document Actions (from RFC-Editor)

The current terminology used for these (e.g., at
https://datatracker.ietf.org/iesg/agenda/) is to talk of a "(RFC 5742)
conflict-review response" for the "IRTF and Independent Submission stream
documents" (i.e., item 3.4 on the linked IESG agenda).  The "Document
Actions (From RFC-Editor)" terminology used in the IESG statement on
discuss-criteria seems confusing at least to me, so I'm not sad to see it
go.

> I'm assuming the draft does not apply to #1, since those would not be
> Informational or Experimental. If the draft is not intended to apply to #4
> (even as an "end run"), that would be helpful to state.
> 
> That leaves #2 or #3. If the draft is concerned about #3, I think it
> should state what the IESG is to do if the draft reappears as individual
> submission.

I assume you mean Independent Submission here (i.e., via ISE).

> If the document is about #2, that would be good to state as well.

In light of the above, it seems clear that this draft is proposing changes
to (2) and (3).

-Ben