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> Thu, 10 March 2022 22:23 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 BD9A23A0CF9; Thu, 10 Mar 2022 14:23:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.11
X-Spam-Level:
X-Spam-Status: No, score=-2.11 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, T_SCC_BODY_TEXT_LINE=-0.01] 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 rkREFYcbAGDF; Thu, 10 Mar 2022 14:23:02 -0800 (PST)
Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) (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 905263A088C; Thu, 10 Mar 2022 14:23:02 -0800 (PST)
Received: by mail-pj1-x102e.google.com with SMTP id mr24-20020a17090b239800b001bf0a375440so9431857pjb.4; Thu, 10 Mar 2022 14:23:02 -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=uQ6mPCUor9ujE8IvRJLeAHYb5rHTIixtAPOHjpicZqw=; b=JLcBtfhKGneMr3yH2znr/YDn1xwuuiNCONRFxotZIbogE9G8LcG02rPZv9ruWQco60 oFsQpfQ/kuRIO2NhTf7XbtnS22c8oa7a83BPIccSmPA8GGB61yidedAoxUCm+Vngc8VH A0gxlg2DcVUS6OvhDetX3X0kVR244V/GD/48A/kXLTPEoEGlCDNcXl6CGsXlyG+3/Z3e yiZm3vQAmuJQn4Pgh0n1oGgNopPAMytO8unVIVHKpkP5sEAqCP4U3z8aAzeVFIHXDOmn m0Pp2asxUuQGnN5BBk7dZVLwC/tHVGfjiu+rcbHDnEJp0iB1cpSzBUGWavWDKPZxi81b d5bg==
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=uQ6mPCUor9ujE8IvRJLeAHYb5rHTIixtAPOHjpicZqw=; b=QBGHXxqNWCik0SI3wgp+6fB0Hpxww3/8K9bAVZzicO03Tn26LOsx1ayh/4EWFm15az 9/BcjTv2cQN7grjOfmz+QEVywxkpq8I9C+1qY/vHzTQnNW8ot8ttCzbRqwSLtUi8klkl 39OmjKbsIGLbGfeBepSCl5U3aCptN4W3WNi8iifhaf+J0dl/JD0C9POKZklkK0R5aUTB 6kIVWWV5ofM2f2lMYr8TBRtDioor43qRRsrPGbmKfkfN0yQeRqd1QJzbZXioYCQnTy2L 0zSyFWzQU1kS8A2WU8teAuuLDL5MRNAGR5/ZcUtRxr7EGA2XEv9x91K2VlLbm6MNSd4J ItLQ==
X-Gm-Message-State: AOAM532uV4hu3/z7sWCaylpX34JBAvcXXJAWJuPnVwSjiiz2GCMp4+zE NqfFAA4WjimnXTZ38ImtALWoirqSRzCKqQ==
X-Google-Smtp-Source: ABdhPJwpZBZL3arhQ/AtB71uRWeClIZjzWe8DGRTmvMriLngWvwjyUauU+0DCj/Z6LDakWKpvn6giw==
X-Received: by 2002:a17:90b:3503:b0:1bc:5d68:e7a2 with SMTP id ls3-20020a17090b350300b001bc5d68e7a2mr7377665pjb.29.1646950981384; Thu, 10 Mar 2022 14:23:01 -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 d16-20020a056a00245000b004f771b48736sm4070203pfj.194.2022.03.10.14.22.57 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 10 Mar 2022 14:23:00 -0800 (PST)
To: Peter Saint-Andre <stpeter@stpeter.im>, Jay Daley <exec-director@ietf.org>
Cc: Mirja Kuehlewind <ietf@kuehlewind.net>, Lars Eggert <lars@eggert.org>, "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> <bf702de8-a876-3d9f-23d8-4ba49f86bd05@gmail.com> <E8C97678-AD00-402B-9646-DEFF6E76263D@ietf.org> <d4ac965c-65b1-e909-864c-cb14e27a3b0f@stpeter.im>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <040d9aac-04be-2bef-fad4-b41f2af271e9@gmail.com>
Date: Fri, 11 Mar 2022 11:22:54 +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: <d4ac965c-65b1-e909-864c-cb14e27a3b0f@stpeter.im>
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/HLeDPGsxiL9Is7-PpXSnVWPVoWo>
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: Thu, 10 Mar 2022 22:23:04 -0000

On 11-Mar-22 11:12, Peter Saint-Andre wrote:
> On 3/10/22 2:32 PM, Jay Daley wrote:
>>
>>
>>> On 11/03/2022, at 10:16 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>>
>>> On 11-Mar-22 09:57, 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. 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?
>>>
>>> IMHO, no. The IAB asks for a liaison *from* the RFC Editor function,
>>
>> Asking the function for a liaison made sense when there was a single point of control that could make that decision.  Under the new model, there isn’t that point of control.  As the draft text proposed by Peter puts it:
>>
>>> Under version 3 of the RFC Editor Model, various
>>> responsibilities of the RFC Editor Function are now performed
>>> alone or in combination by the RSWG, RSAB, RPC, RFC Series
>>> Consulting Editor (RSCE), and IETF LLC, which collectively
>>> comprise the essence of the RFC Editor Function.
>>
>> We’re going to need a whole new complex process just to sort out how these individuals parts are to agree on a single liaison, if "asking the function" continues to be the way forward.
> 
> Right, and I suggest that we avoid that complex process by not having a
> liaison to the IAB from the "RFC Editor Function" (if the IAB and RPC
> etc. feel that we need a liaison from the RPC then that's much easier to
> arrange).

Again, fix it later. The language in draft-carpenter-rfced-iab-charter
allows for it to be fixed later (that was intentional). If the RFC Editor
function decides not to appoint a liaison, that's fine too.

    Brian

     Brian