Re: NomCom eligibility & IETF 107
John C Klensin <john-ietf@jck.com> Tue, 07 April 2020 22:10 UTC
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C1AD3A095D for <ietf@ietfa.amsl.com>; Tue, 7 Apr 2020 15:10:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 A2LTPlQ5xUrc for <ietf@ietfa.amsl.com>; Tue, 7 Apr 2020 15:10:17 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA5DA3A0955 for <ietf@ietf.org>; Tue, 7 Apr 2020 15:10:17 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1jLwQA-0004Yn-F2; Tue, 07 Apr 2020 18:10:14 -0400
Date: Tue, 07 Apr 2020 18:10:08 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>, Bob Hinden <bob.hinden@gmail.com>
cc: IETF <ietf@ietf.org>
Subject: Re: NomCom eligibility & IETF 107
Message-ID: <9CC3084E16DEBB3233FAC1E1@PSB>
In-Reply-To: <CAC4RtVBjTjOWLMTFvM50DR2piOLQ4jniXTWPunOoMfvdkOzvXw@mail.gmail.com>
References: <CALaySJ+kFVXrVAkYLaO6MaPqDA29MzXhVFcxG0c6hZcBs-LqnQ@mail.gmail.com> <CAC4RtVAhfFLYwzqw6Qch3BpuMvqjZPzFJ5o1iTOwR+yqH8j-Aw@mail.gmail.c om> <CAC4RtVCzMPGuunYZBCSh90ddY2kKJ_Hqnot0s1jmhNQ7qT0xkg@mail.gmail.com> <89730DD8-0451-4658-A0CD-83A85E2055FE@episteme.net> <0C31D020-46FA-424E-8FFD-64BBE8F952E9@cooperw.in> <1E702B62-9982-48F2-B8D6-F4F80A8DE168@episteme.net> <20200331184236.GT18021@localhost> <CALaySJ+_+-kf+3nta8LwMiwPmqPmRdOgC7KAnDfeDgx0ThVa-w@mail.gmail.com> <CALaySJ+27gcT6x5BcKU1YHHv+xeaXDnxPU0yhtBSULb36VpFWA@mail.gmail.c om> <CAC4RtVBy7iVT4NVLw14+=a1ksWrg35q+dsKfs+9r2poiVo3wkg@mail.gmail.com> <0FC773BE-7B20-402C-AC7E-183A321741E0@gmail.com> <CAC4RtVBjTjOWLMTFvM50DR2piOLQ4jniXTWPunOoMfvdkOzvXw@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4lCMniSH7vIN9g2hedGnSSsX9PI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2020 22:10:22 -0000
--On Thursday, April 2, 2020 13:15 -0400 Barry Leiba <barryleiba@computer.org> wrote: >> I read the draft and I support it. > > Thanks, Bob. > >> One nit: Should it say that it updates BCP10? > > I think it should not, but should be its own BCP. > > We need a broader effort to update BCP 10, but this is a > one-time exception. Publishing it as a BCP is a process > formality, but sets no precedent and won't apply after this > year's NomCom is seated. I think it would be wrong for it to > formally update BCP 10. Barry, lLet me try an alternate theory out on you. First, however temporarily, this is a clarifying update to RFC 8713. Regardless of what decisions are made about BCP numbers, that update should be noted in the draft to make the thread clear and so, at least during the several months (or perhaps close to a year if there is a recall effort) in which this procedure is active and relevant, any effort to look up the topics covered by 8713 provides a clear path to this specification. I think, given that, treating it as part of BCP 10 follows, but I don't think it makes a lot of difference as long as the "updates" thread is clear. I don't think the "updates" relationship can be avoided. When the first sentence in Section 3 of the I-D says: The following text modifies, for the 2020-2021 NomCom selection only, the first two paragraphs (quoted above) of Section 4.14 of BCP 10 [RFC8713]: That is about as clear a candidate for "updating" (in this case 8713) as I've seen in some time. I do recognize what I think is your concern about BCP 10, but it seems to me that is easily handled: when the more permanent fix (the "[an]other update to BCP 10 [that] will be necessary..." comes along, it formally obsoletes this temporary document, making clear that the emergency interpretation no longer applies and specifying what does. Move it to Historic too, if that seems sensible. And, if having a dead document as part of BCP 10 bothers people. remove it at that time. Just a thought... john
- NomCom eligibility & IETF 107 Barry Leiba
- Re: NomCom eligibility & IETF 107 Lars Eggert
- RE: NomCom eligibility & IETF 107 Daniele Ceccarelli
- Re: NomCom eligibility & IETF 107 Mary B
- Re: NomCom eligibility & IETF 107 Russ Housley
- Re: NomCom eligibility & IETF 107 Carsten Bormann
- Re: NomCom eligibility & IETF 107 Russ Housley
- Re: NomCom eligibility & IETF 107 Paul Wouters
- Re: NomCom eligibility & IETF 107 Lars Eggert
- Re: NomCom eligibility & IETF 107 Keith Moore
- Re: NomCom eligibility & IETF 107 Eric Rescorla
- Re: NomCom eligibility & IETF 107 Stephen Farrell
- Re: NomCom eligibility & IETF 107 John C Klensin
- Re: NomCom eligibility & IETF 107 Alexandre Petrescu
- Re: NomCom eligibility & IETF 107 Carsten Bormann
- Re: NomCom eligibility & IETF 107 Barry Leiba
- Forced virtual IETF 109 as well as 107 (was: Re: … John C Klensin
- Re: NomCom eligibility & IETF 107 John C Klensin
- Re: NomCom eligibility & IETF 107 Bob Hinden
- Re: NomCom eligibility & IETF 107 John C Klensin
- Re: NomCom eligibility & IETF 107 Lars Eggert
- Re: NomCom eligibility & IETF 107 Paul Hoffman
- Re: NomCom eligibility & IETF 107 Salz, Rich
- Re: NomCom eligibility & IETF 107 Michael Richardson
- Re: NomCom eligibility & IETF 107 Toerless Eckert
- Re: NomCom eligibility & IETF 107 Vittorio Bertola
- Re: NomCom eligibility & IETF 107 Michael StJohns
- Re: NomCom eligibility & IETF 107 John C Klensin
- Re: NomCom eligibility & IETF 107 Randy Bush
- Re: Forced virtual IETF 109 as well as 107 (was: … tom petch
- Re: Forced virtual IETF 109 as well as 107 Alexandre Petrescu
- Re: Forced virtual IETF 109 as well as 107 Brian E Carpenter
- RE: NomCom eligibility & IETF 107 Eric Gray
- Re: NomCom eligibility & IETF 107 Michael Richardson
- Re: Forced virtual IETF 109 as well as 107 Phillip Hallam-Baker
- Re: NomCom eligibility & IETF 107 Job Snijders
- Re: NomCom eligibility & IETF 107 Randy Bush
- Re: NomCom eligibility & IETF 107 Andrew G. Malis
- Re: NomCom eligibility & IETF 107 Keith Moore
- Re: NomCom eligibility & IETF 107 Barry Leiba
- Re: NomCom eligibility & IETF 107 Victor Kuarsingh
- Re: NomCom eligibility & IETF 107 S Moonesamy
- Re: NomCom eligibility & IETF 107 Pete Resnick
- Re: NomCom eligibility & IETF 107 Stewart Bryant
- Re: NomCom eligibility & IETF 107 Stewart Bryant
- Re: NomCom eligibility & IETF 107 Phillip Hallam-Baker
- Re: NomCom eligibility & IETF 107 John C Klensin
- Re: NomCom eligibility & IETF 107 Michael Richardson
- Re: Forced virtual IETF 109 as well as 107 S Moonesamy
- Re: NomCom eligibility & IETF 107 Cullen Jennings
- AW: NomCom eligibility & IETF 107 N.Leymann
- Re: NomCom eligibility & IETF 107 Jay Daley
- Re: NomCom eligibility & IETF 107 Jim Fenton
- Re: NomCom eligibility & IETF 107 Brian E Carpenter
- Re: NomCom eligibility & IETF 107 John C Klensin
- Re: NomCom eligibility & IETF 107 Salz, Rich
- Re: Forced virtual IETF 109 as well as 107 Alexandre Petrescu
- Re: Forced virtual IETF 109 as well as 107 S Moonesamy
- Venue for post-IETF 107 Nomcom eligibility discus… Spencer Dawkins at IETF
- Re: Venue for post-IETF 107 Nomcom eligibility di… Samuel Weiler
- Re: Venue for post-IETF 107 Nomcom eligibility di… Alissa Cooper
- Re: Venue for post-IETF 107 Nomcom eligibility di… Spencer Dawkins at IETF
- Re: NomCom eligibility & IETF 107 Barry Leiba
- Re: NomCom eligibility & IETF 107 Salz, Rich
- Re: NomCom eligibility & IETF 107 Brian E Carpenter
- Re: NomCom eligibility & IETF 107 John C Klensin
- Re: NomCom eligibility & IETF 107 tom petch
- Re: NomCom eligibility & IETF 107 Lou Berger
- Re: NomCom eligibility & IETF 107 Loa Andersson
- Re: NomCom eligibility & IETF 107 Christian Hopps
- Re: NomCom eligibility & IETF 107 Spencer Dawkins at IETF
- Re: NomCom eligibility & IETF 107 Salz, Rich
- Re: NomCom eligibility & IETF 107 John C Klensin
- Re: NomCom eligibility & IETF 107 Bob Hinden
- Re: NomCom eligibility & IETF 107 Salz, Rich
- Re: NomCom eligibility & IETF 107 John C Klensin
- Re: NomCom eligibility & IETF 107 Barry Leiba
- Re: NomCom eligibility & IETF 107 Spencer Dawkins at IETF
- Re: NomCom eligibility & IETF 107 Michael Richardson
- Re: NomCom eligibility & IETF 107 Salz, Rich
- Re: NomCom eligibility & IETF 107 Michael StJohns
- Re: NomCom eligibility & IETF 107 Salz, Rich
- Re: NomCom eligibility & IETF 107 Pete Resnick
- Re: NomCom eligibility & IETF 107 Donald Eastlake
- Re: NomCom eligibility & IETF 107 Spencer Dawkins at IETF
- Re: NomCom eligibility & IETF 107 Jared Mauch
- Re: NomCom eligibility & IETF 107 Stewart Bryant
- Re: NomCom eligibility & IETF 107 Pete Resnick
- Re: NomCom eligibility & IETF 107 Lars Eggert
- RE: NomCom eligibility & IETF 107 Scott Mansfield
- Re: NomCom eligibility & IETF 107 Salz, Rich
- Re: NomCom eligibility & IETF 107 Michael Richardson
- Re: NomCom eligibility & IETF 107 Abdussalam Baryun
- Re: NomCom eligibility & IETF 107 Barry Leiba
- Re: NomCom eligibility & IETF 107 Pete Resnick
- Re: NomCom eligibility & IETF 107 Keith Moore
- Re: NomCom eligibility & IETF 107 Nico Williams
- Re: NomCom eligibility & IETF 107 Pete Resnick
- Re: NomCom eligibility & IETF 107 Nico Williams
- Re: NomCom eligibility & IETF 107 Salz, Rich
- Re: NomCom eligibility & IETF 107 Behcet Sarikaya
- Re: NomCom eligibility & IETF 107 Keith Moore
- Re: NomCom eligibility & IETF 107 Alissa Cooper
- Re: NomCom eligibility & IETF 107 Yoav Nir
- Re: NomCom eligibility & IETF 107 Michael StJohns
- Re: NomCom eligibility & IETF 107 Richard Barnes
- Re: NomCom eligibility & IETF 107 Victor Kuarsingh
- Re: NomCom eligibility & IETF 107 Pete Resnick
- Re: NomCom eligibility & IETF 107 Pete Resnick
- Re: NomCom eligibility & IETF 107 Nico Williams
- Re: NomCom eligibility & IETF 107 Barry Leiba
- Re: NomCom eligibility & IETF 107 Nico Williams
- Re: NomCom eligibility & IETF 107 Salz, Rich
- Re: NomCom eligibility & IETF 107 Barry Leiba
- Re: NomCom eligibility & IETF 107 Robert Elz
- Re: NomCom eligibility & IETF 107 Victor Kuarsingh
- Re: NomCom eligibility & IETF 107 Brian E Carpenter
- Re: NomCom eligibility & IETF 107 Spencer Dawkins at IETF
- Re: NomCom eligibility & IETF 107 Barry Leiba
- Re: NomCom eligibility & IETF 107 Michael Richardson
- Re: NomCom eligibility & IETF 107 Barry Leiba
- Re: NomCom eligibility & IETF 107 Joel Halpern
- Re: NomCom eligibility & IETF 107 Salz, Rich
- Re: NomCom eligibility & IETF 107 Salz, Rich
- Re: NomCom eligibility & IETF 107 Behcet Sarikaya
- Re: NomCom eligibility & IETF 107 Keith Moore
- Re: NomCom eligibility & IETF 107 Nico Williams
- Re: NomCom eligibility & IETF 107 Pete Resnick
- Re: NomCom eligibility & IETF 107 Barry Leiba
- Re: NomCom eligibility & IETF 107 Barry Leiba
- Re: NomCom eligibility & IETF 107 Bob Hinden
- Re: NomCom eligibility & IETF 107 Pete Resnick
- Re: NomCom eligibility & IETF 107 Barry Leiba
- Re: NomCom eligibility & IETF 107 John Levine
- Re: NomCom eligibility & IETF 107 Pete Resnick
- Re: NomCom eligibility & IETF 107 Brian E Carpenter
- Re: NomCom eligibility & IETF 107 Nico Williams
- Re: NomCom eligibility & IETF 107 Abdussalam Baryun
- Re: NomCom eligibility & IETF 107 John C Klensin