IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 09 September 2021 22:41 UTC

Return-Path: <brian.e.carpenter@gmail.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 5D88F3A0980 for <rfced-future@ietfa.amsl.com>; Thu, 9 Sep 2021 15:41:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, 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 c-ga10hR0yLs for <rfced-future@ietfa.amsl.com>; Thu, 9 Sep 2021 15:41:02 -0700 (PDT)
Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) (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 8335B3A097F for <rfced-future@iab.org>; Thu, 9 Sep 2021 15:41:02 -0700 (PDT)
Received: by mail-pf1-x434.google.com with SMTP id f65so72192pfb.10 for <rfced-future@iab.org>; Thu, 09 Sep 2021 15:41:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=KuztlwpHGEJ4FbG9Cc8NsYyV58gyzTcR0GxZcyxduNU=; b=SD3hrwcw6yPF1cy8BI0+EIpZ8sY7LjHYl95voOpwSZahvtEFJVQvyAnJvQrnlx0g1o M1jpDzFclZZj1XEwOgkpF7/ETJG6XuNlaVJbmPXkxMHQ2xNy2Vq51J4muNgggQAos75e wRwlvmJVUNQCG1lwnjGbZO6xzTAChy5BiLQ3RLtILNX4wbXUA5/XP0809QZV0PiwcTPR cyEFpUGAafOtAv0Mo2RxiDom1Pt+FgdVOnK7IBzruF+kc5Ft6cfoM6A3sWxns1CvCsNV 6vitQK5mtKJlwpuAJsULGjQ2jyaRHzyKT840/JvA3W4+bErkQjThCKcMtsilJ7KGgAVg Olyg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=KuztlwpHGEJ4FbG9Cc8NsYyV58gyzTcR0GxZcyxduNU=; b=D9EwryzgpvKfrdyJSsUcsR0Ac5APdWXPSrNotjw/OWzkV7CCpW5zxTnyro1AhvwAwO y6frRm88+G6wPptS/dgAtHygFNtIcRIwNHTZRjweat4aGbbAf8wXeZl7zZSBxaX6oHtu lihX3FlCv0wn5dXf4QgEIMbyo/r30kMBmmfQOUbuZkqdXdTyHVThC4snpxgsy9c+Nrsf X5bvF8RJ42HOGxXk3UrD+ruDJpgFCtCse+TJ+wez2YKhfJXN//yTlk3ZiiTFs9GDlgr3 zu4vODFko0Rz5w3KFAu/0s+/77QwfJ1c9CIlw94+kD1ifFpX5cmigjMZRjlgjqwYyf77 tnGA==
X-Gm-Message-State: AOAM5330+nlBi1ruwwG2VY6JmGn/Udb1fAzIZb0kaNGi4ZcAxoKbID/E JS3PpZUI/nhQY6bGPFSrPeByl9JB7tc=
X-Google-Smtp-Source: ABdhPJyCKoNq59XoNmhHxfh+GEvImEkZY26W/tSYPCVV7Yxjjyq5orzL23/pRJVTS49J3TZIhpjFDg==
X-Received: by 2002:a63:385e:: with SMTP id h30mr4657365pgn.187.1631227260747; Thu, 09 Sep 2021 15:41:00 -0700 (PDT)
Received: from ?IPv6:2406:e003:11aa:d701:80b2:5c79:2266:e431? ([2406:e003:11aa:d701:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id 66sm3230172pfx.29.2021.09.09.15.40.58 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 09 Sep 2021 15:41:00 -0700 (PDT)
To: Scott Bradner <sob@sobco.com>
Cc: Eliot Lear <lear@lear.ch>, rfced-future@iab.org
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> <C2701BC5-52DA-411A-A1CA-E5848ABDBE49@sobco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <e9650917-dfa8-a33f-b1ec-6ee7b040a8e3@gmail.com>
Date: Fri, 10 Sep 2021 10:40:56 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <C2701BC5-52DA-411A-A1CA-E5848ABDBE49@sobco.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/skb2CEnT6Ws2w3wVmjGE_zDKvHw>
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 22:41:08 -0000

On 10-Sep-21 01:56, Scott Bradner wrote:
> 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

We're getting a bit off topic here, but I agree that this was the original motivation. However, personally, I feel that the IETF and the RFC Series still have a lot to thank ISOC for so at the least they deserve a heads-up. You're probably correct that a "nod" is not formally needed.

   Brian

> 
> 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
>

v2.23.0 | Report a Bug | By Email