Re: [Rfced-future] RFC Editor liaison to the IAB? [was: Re: Comment on draft-iab-rfcefdp-rfced-model-12]

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 11 March 2022 00:26 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 428853A0CF8; Thu, 10 Mar 2022 16:26:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.109
X-Spam-Level:
X-Spam-Status: No, score=-7.109 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, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable 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 ndryGCbZ1GLV; Thu, 10 Mar 2022 16:26:41 -0800 (PST)
Received: from mail-pj1-x102b.google.com (mail-pj1-x102b.google.com [IPv6:2607:f8b0:4864:20::102b]) (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 506473A0CDB; Thu, 10 Mar 2022 16:26:41 -0800 (PST)
Received: by mail-pj1-x102b.google.com with SMTP id gj15-20020a17090b108f00b001bef86c67c1so6716227pjb.3; Thu, 10 Mar 2022 16:26:41 -0800 (PST)
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=5viBvq3nOk3VbY7VMFMfBAdl1A1LV52SisvKDuwb++M=; b=b3I4bnnglzRH6PTDckcW1s3JxWSQKB/YFjQw5J4kchU1UvAlNoKYpLv7/Lvz6XRtTT k2v0dch4uCKmFlMFBaD+C5JEHVfcOOVwDrSl3tk3Sp/U5hdswdyh1MwDEPg+OaNxgybL oeDZqsVJY5jRaFl9AKqbQ3NptyLucPb5LovGhnvdX2t9NNR82uZpKbcmcWLhgGKedWUS NIqRQi2b/Dm49aJPBW1jXLuOCiJCFqlXd453nfTZMJ/k0qPrnKWBQeNRabaO4ifa3knP yNY5Gb7K9RZTj3I+kVhpGPXJ/UHIgwPmMsJRItc7co76+YIP9YTH/pxXtOuekYOJLuKE b5+g==
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=5viBvq3nOk3VbY7VMFMfBAdl1A1LV52SisvKDuwb++M=; b=nzgarRA7063XcnbDzGVO1AQ50usW9+7NnXY50HEhiJLzfs4AXHQnsQ/AhQwtXEsTTV V3NLApyDdvGAv0D4bDsXzN+M8qhQlmfnkHUfXzBn0aYyg0C7BM9SmQAxPiQI6oYke2nZ PQOljKBrtTXDUZ/1zGRIEj8rmEEe9aVsEkAVwDrR7zB0xkTzIdI7dECHbE09Y5hp8I29 68HZBiL6smfO3f/Bx++41b84H+Dj1ekePy3O545UkKkQ/cfN2b/2Q/s742CG+DRfT5mC kFW34yD1HZsJXqThkrTZuhqb1rxeEm81Gb/CwVwforgit+sDebekOD6zGb2JHKDDVpgS Nn7g==
X-Gm-Message-State: AOAM5325oABXbG6klEOQq8hawU264Mojwe3mw7wvWc6889d3sr9ZG/NL /lF6Io6m9kNlKl3n/kYTw2c=
X-Google-Smtp-Source: ABdhPJxY4wl6bqMIy7jFwB9FMPmM6PIrKJTzrPig5K5j9v8fFvdiSbhYAepNUyNw6FSDT8rIj8IBbg==
X-Received: by 2002:a17:90b:4d05:b0:1bf:7d65:f1f7 with SMTP id mw5-20020a17090b4d0500b001bf7d65f1f7mr7952194pjb.108.1646958400059; Thu, 10 Mar 2022 16:26:40 -0800 (PST)
Received: from ?IPv6:2406:e003:1005:b501:80b2:5c79:2266:e431? ([2406:e003:1005:b501:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id l5-20020a056a0016c500b004f140564a00sm8392148pfc.203.2022.03.10.16.26.35 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 10 Mar 2022 16:26:39 -0800 (PST)
To: Jean Mahoney <jmahoney@amsl.com>, Mirja Kuehlewind <ietf@kuehlewind.net>, Peter Saint-Andre <stpeter@stpeter.im>, Lars Eggert <lars@eggert.org>
Cc: "rfced-future@iab.org" <rfced-future@iab.org>, Internet Architecture Board <iab@iab.org>, The IESG <iesg@ietf.org>, "Rob Wilton (rwilton)" <rwilton=40cisco.com@dmarc.ietf.org>
References: <BY5PR11MB41963ABAE51BC46E205087BDB50B9@BY5PR11MB4196.namprd11.prod.outlook.com> <134294e0-5bd5-9b22-2d95-f6032e67f516@stpeter.im> <7D016D6C-ACCE-4431-BC83-905ECB885B5F@kuehlewind.net> <777e0c64-fd7b-6c04-916c-a17cb211110e@amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <f828cd1b-f0bb-a236-4a71-5c5b108ec420@gmail.com>
Date: Fri, 11 Mar 2022 13:26:32 +1300
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: <777e0c64-fd7b-6c04-916c-a17cb211110e@amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/5A3GjHYo29ik6NbAh2WiehWFa-o>
Subject: Re: [Rfced-future] RFC Editor liaison to the IAB? [was: Re: Comment on draft-iab-rfcefdp-rfced-model-12]
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: Fri, 11 Mar 2022 00:26:48 -0000

On 11-Mar-22 13:00, Jean Mahoney wrote:
> Hi all,
> 
> (with my RPC hat on)
> 
> On 3/10/22 2:57 PM, Mirja Kuehlewind wrote:
>> This is indeed a good question. Thanks Rob for bring this up!
>>
>> I actually think there are two options here: either the IAB could have 
a liaison from the RPC or, if the RPC thinks this is not needed, we probably just don’t need a liaison in the new model.
> 
> [JM] The RPC doesn't feel that a liaison to the IAB is necessary;
> however, we hope the IAB will invite the RPC to participate in meetings
> as needed.

That makes sense to me and there is no text in any of the drafts that
suggests an RPC liaison. I'll reply to Jay's message on the more general
question.

     Brian

> 
> Best regards,
> 
> Jean
> 
> 
>> This seems like the only two option to me, given we definitely don’t need a liaison from the RSAB as the IAB is sending one of the representatives and I don’t think it practically makes sense to have liaison from the RSWG. Or maybe having the RSCE as a liaison to the IAB could be another option but I don’t think that would be of real interest for the new RSCE role…?
>>
>> It seems like this is actually something we might also want to update as well in draft-carpenter-rfced-iab-charter. Brian? Lars?
>>
>>
>>
>>> On 10. Mar 2022, at 21:13, Peter Saint-Andre <stpeter@stpeter.im> wrote:
>>>
>>> On 3/10/22 3:41 AM, Rob Wilton (rwilton) wrote:
>>>> Changing the title to help ensure that this comment is tracked against draft-iab-rfcefdp-rfced-model.
>>>> Still suffering from Covid, and I'm now way behind on email, so perhaps this has already been resolved, but I think that the issue below needs to be resolved before the document is published.
>>>> Regards,
>>>> Rob
>>>> -----Original Message-----
>>>> From: Brian E Carpenter <brian.e.carpenter@gmail.com>
>>>> Sent: 07 March 2022 19:40
>>>> To: Rob Wilton (rwilton) <rwilton@cisco.com>; The IESG <iesg@ietf.org>
>>>> Cc: draft-carpenter-rfced-iab-charter@ietf.org; rfced-future@iab.org
>>>> Subject: Re: Robert Wilton's No Objection on draft-carpenter-rfced-iab-charter-06: (with COMMENT)
>>>> Rob,
>>>> On 07-Mar-22 23:58, Robert Wilton via Datatracker wrote:
>>>> ...
>>>>     
>>>>> Hi,
>>>>>
>>>>>       Note that RFC 2850 states that the RFC Editor appoints a liaison
>>>>>       member to the IAB.  This does not change, but refers to the RFC
>>>>>       Editor function as described in [I-D.iab-rfcefdp-rfced-model].
>>>>>
>>>>> It isn't entirely clear to me exactly who (as in which person or body) is
>>>>> actually responsible for appointing a liaison member to the IAB (given, as per
>>>>> draft-iab-rfcefdp-rfced-model, the RFC editor function responsibilities are
>>>>> split up into multiple entities).  My assumption is that this would 
be RSAB,
>>>>> but perhaps I mistaken.  Would it be helpful to clarify this - perhaps in
>>>>> draft-iab-rfcefdp-rfced-model?
>>>> Indeed, I don't think it belongs in the IAB charter. Hence I suggest 
that this
>>>> is really a comment that the IAB Program (in Cc:) should look at.
>>> This is a good question.
>>>
>>> One key assumption underlying version 3 of the RFC Editor Model is that the process for policy definition and implementation is no longer under the purview of the IAB. Therefore, I question whether the IAB still needs a liaison from the RFC Editor Function (whose responsibilities are now 
spread across multiple entities) and I would defer to the IAB (cc'd) on whether they think this is needed. (If so, we'll need to figure out who does the appointing, but one step at a time.)
>>>
>>> Peter
>>>
>>>