IETF Logo Mail Archive

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:20 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 2DC2F3A0C82; Thu, 10 Mar 2022 14:20:01 -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 OZT8OxD_KKfl; Thu, 10 Mar 2022 14:19:57 -0800 (PST)
Received: from mail-pj1-x1035.google.com (mail-pj1-x1035.google.com [IPv6:2607:f8b0:4864:20::1035]) (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 BD59A3A1C93; Thu, 10 Mar 2022 14:19:57 -0800 (PST)
Received: by mail-pj1-x1035.google.com with SMTP id e3so6366827pjm.5; Thu, 10 Mar 2022 14:19:57 -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=US9FHo007kduV9jbaiArb2I5kjRtaNDYUD8cRjDjQF0=; b=EtIYBqka0L5yg+6o8h/UiZTNAZOuZyyXmRzNqoV29bEtXiez6nojr2Jinw8Goe3q6D kMGR+4DjTU5A6xaSodqdZ1jUIcUtH9SuXbOQZ2T8H2e3+RVW+xvsQpb8J4P1T9YZpwD8 L61EwM2z0Fr0LlWDVzvM1ibVmKvMe0S6+drJBHAwH56hODIjgqXSUgNxQs2Uk6qI0fPE XnJo3x8Squ27im0QE0tvSUivEgl+g41l53ehYx1dR/bvvoP7UUxIJSUZJmIINZTE8anR FPdRdCVU50fHv+aJzvcFpGJV++Eyhx0bSXjrr4/03Jyq+wT7vbkjd/0dUQnFERIoQCRu 9AFg==
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=US9FHo007kduV9jbaiArb2I5kjRtaNDYUD8cRjDjQF0=; b=Clu5sGH5qFQrh0up7t1SEbMoiEY+0Oen9jq0Pm/F5xgSmFfW03mUsHOVBJ8ZAalrjp GLfwXI1BguBbo/RImgGorscGvp2oU+FVUBQxk8a+GsdPFYRDk/h9talZRfZ7ko8c4fNl TFi8ChKc1FYboAbZxvJa2cU/vzBD7HLFGsWX/x9zhjclNjQVY1iXHqfK06wq14TrMFDe HtQ2jTSGi29YmA+37jHidn+KNHt3EJ/cKz25TFfW1X6MeyZEC24R9YOIfSlnuq4lkO47 3jGtur3842fXfLJA1sSO66K8old/uifsV1LSvhVYIr3BLIGAXx0XlwOpO32m3Guvi4OA cUsA==
X-Gm-Message-State: AOAM530IvGXCGugwqYZxkdNNRZR894tpD5B8J24QLhE9zppUMwB3nMja rWF/96QYdgJ8jF8UBmNbCDM=
X-Google-Smtp-Source: ABdhPJwM0XmzAH/FycdUMsolDMfllPSc7znr+UuGTbd7H6VlU7ioZ6hLK/Cz+pnAo0zV2Rcdq3+73w==
X-Received: by 2002:a17:902:cf02:b0:14d:54cf:9a6a with SMTP id i2-20020a170902cf0200b0014d54cf9a6amr6959869plg.137.1646950796546; Thu, 10 Mar 2022 14:19:56 -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 f20-20020a056a001ad400b004f6e8f8f90bsm7999830pfv.109.2022.03.10.14.19.53 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 10 Mar 2022 14:19:56 -0800 (PST)
To: Lars Eggert <lars@eggert.org>
Cc: Mirja Kühlewind <ietf@kuehlewind.net>, "rfced-future@iab.org" <rfced-future@iab.org>, Internet Architecture Board <iab@iab.org>, The IESG <iesg@ietf.org>, Peter Saint-Andre <stpeter@stpeter.im>, "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> <702330E0-0D47-47AD-8434-C6F1EF6CA40F@eggert.org> <6dabea27-8abe-4251-f9a1-8e8297c64fb4@gmail.com> <F07193A5-2F60-4C8C-ABAE-9FCCADC1B39A@eggert.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <0f3753ef-a490-b05c-229d-b559dab45c57@gmail.com>
Date: Fri, 11 Mar 2022 11:19:50 +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: <F07193A5-2F60-4C8C-ABAE-9FCCADC1B39A@eggert.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/HSkvJ-RpTkcerFV7yc6vsBfaNok>
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:20:01 -0000

On 11-Mar-22 10:29, Lars Eggert wrote:
> Hi,
> 
> On 2022-3-10, at 23:20, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>> No, I disagree. It's not the receiver of a liaison that specifies how the liaison is appointed, it's the sender.
> 
> RFC2850 says in Section 1.2:
> 
>     The Internet Society, the RFC Editor, the IANA and the IESG each
>     appoints a liaison member to the IAB. These liaison positions may not
>     be held by a full member of the IAB.
> 
> Irrespective of whether it's the IAB or the RFC Editor that does the appointing or asking for a liaison, if there is a change, that text would need an update, no?

That's why draft-carpenter-rfced-iab-charter has always said:

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

     Brian

v2.23.0 | Report a Bug | By Email