IETF Logo Mail Archive

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

Lars Eggert <lars@eggert.org> Thu, 10 March 2022 21:30 UTC

Return-Path: <lars@eggert.org>
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 AD84D3A1C27; Thu, 10 Mar 2022 13:30:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.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, 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 (1024-bit key) header.d=eggert.org
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 rPojJvV1dzMB; Thu, 10 Mar 2022 13:30:00 -0800 (PST)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:4000:400:211:32ff:fe22:186f]) (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 B61453A1C2B; Thu, 10 Mar 2022 13:29:58 -0800 (PST)
Received: from smtpclient.apple (unknown [IPv6:2a00:ac00:4000:400:a554:7080:603c:d8ab]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 64D701D5F4A; Thu, 10 Mar 2022 23:29:47 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1646947787; bh=YeXdcXslnUb875F+2NKW8ew03lCqYDWp+ISihIituOI=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=ojTvpFbiT1yCWlUu7dIHtsUfDpHZfwuGPEJiN+xNGmxB2TMFELyDCkMlrZuvKlWiI rqXowyEzvnmYoXvcQfQ95jYBNW2aWiZf3CTdJzs941+zMiM2w7vdzVXTOQD125rfiu CphGiHY3lbe5QtxE1hVIq9NPXxC9KSGbF/RFzABo=
Content-Type: multipart/signed; boundary="Apple-Mail=_C9D8CDDB-FC81-4ACB-87D3-417A5DE43C29"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <6dabea27-8abe-4251-f9a1-8e8297c64fb4@gmail.com>
Date: Thu, 10 Mar 2022 23:29:46 +0200
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>
Message-Id: <F07193A5-2F60-4C8C-ABAE-9FCCADC1B39A@eggert.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>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-MailScanner-ID: 64D701D5F4A.A5F27
X-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/D-1CYL9VrtJsyhB-dKg1JQQKCao>
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 21:30:03 -0000

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?

Thanks,
Lars

v2.23.0 | Report a Bug | By Email