Re: [Rfced-future] approval path for our work

Scott Bradner <sob@sobco.com> Thu, 09 September 2021 13:57 UTC

Return-Path: <sob@sobco.com>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF5FE3A124C for <rfced-future@ietfa.amsl.com>; Thu, 9 Sep 2021 06:57:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.918
X-Spam-Level:
X-Spam-Status: No, score=-0.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_DYNAMIC=0.982, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 XpJtQPJUbktP for <rfced-future@ietfa.amsl.com>; Thu, 9 Sep 2021 06:57:06 -0700 (PDT)
Received: from sobco.sobco.com (173-166-5-71-newengland.hfc.comcastbusiness.net [173.166.5.71]) by ietfa.amsl.com (Postfix) with ESMTP id AF3383A125F for <rfced-future@iab.org>; Thu, 9 Sep 2021 06:57:00 -0700 (PDT)
Received: from smtpclient.apple (golem.sobco.com [136.248.127.162]) by sobco.sobco.com (Postfix) with ESMTPSA id 1F2169EF004; Thu, 9 Sep 2021 09:56:59 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Scott Bradner <sob@sobco.com>
In-Reply-To: <CANMZLAbEfS0E3vcenY5oCp+dvUBikwisAfFpjsuC8uNipntJqw@mail.gmail.com>
Date: Thu, 09 Sep 2021 09:56:58 -0400
Cc: Eliot Lear <lear@lear.ch>, rfced-future@iab.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C2701BC5-52DA-411A-A1CA-E5848ABDBE49@sobco.com>
References: <017a4166-0540-809b-360f-32e5af5b0512@lear.ch> <6839d5d5-83fb-5cd1-c86d-023017ce034f@gmail.com> <42f2f60a-f782-e340-abf9-f942be09f3a3@lear.ch> <CANMZLAbEfS0E3vcenY5oCp+dvUBikwisAfFpjsuC8uNipntJqw@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/3dvf5Wt3qFjITPeCkWiMv3HaTvs>
Subject: Re: [Rfced-future] approval path for our work
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2021 13:57:11 -0000

for what its worth - the "nod" from the ISOC board relative to IETF processes was
that the ISOC board voted to "accept" IETF  processes in order for the ISOC to be able to buy 
insurance to cover IETF decisions (IAB, IESG, WG chairs etc) 

if the insurance is now bought by the LLC then maybe the ISOC board no longer needs to nod

Scott

> On Sep 9, 2021, at 3:20 AM, Brian Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> > Why the nod from the Internet Society Board?  They're not once mentioned
> in the draft.
> 
> Maybe not,  but they used to pay for the series directly, hold the copyrights and the contract. They still supply the money. So it would be a courtesy at the very least.
> 
> Regards,
>     Brian Carpenter
>     (via tiny screen & keyboard)
> 
> On Thu, 9 Sep 2021, 18:55 Eliot Lear, <lear@lear.ch> wrote:
> Hi,
> 
> On 09.09.21 00:49, Brian E Carpenter wrote:
> >
> > If so, since it's a potential BCP, do I need to take it to gendisptach?
> > It expired a while ago:
> > https://datatracker.ietf.org/doc/html/draft-carpenter-rfced-iab-charter
> > I have an editorial update ready to go.
> 
> 
> I would think that the right approach.  If it gets hung up there, then 
> we can reconsider our options.
> 
> 
> >   
> >> We also agreed that whatever the approval path, we should circulate our
> >> LC far and wide so that everyone has an opportunity to comment.
> > Clearly. I feel that given what's *currently* in RFC 2850 and that the
> > IAB chartered this activity, we do need formal approval from the IAB
> > and a nod from both the Internet Society Board and the IESG.
> 
> Why the nod from the Internet Society Board?  They're not once mentioned 
> in the draft.
> 
> Eliot
> 
> 
> -- 
> Rfced-future mailing list
> Rfced-future@iab.org
> https://www.iab.org/mailman/listinfo/rfced-future