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> Mon, 14 March 2022 19:42 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 E38A13A1317; Mon, 14 Mar 2022 12:42:22 -0700 (PDT)
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 17vN27o242nh; Mon, 14 Mar 2022 12:42:18 -0700 (PDT)
Received: from mail-pf1-x436.google.com (mail-pf1-x436.google.com [IPv6:2607:f8b0:4864:20::436]) (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 D8D513A1350; Mon, 14 Mar 2022 12:42:17 -0700 (PDT)
Received: by mail-pf1-x436.google.com with SMTP id s11so15734302pfu.13; Mon, 14 Mar 2022 12:42:17 -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=Ki3vR+Bvs8D4LYq0OtYKWEnCXvpRk/eJ4mD4nNKoYEI=; b=EfWCO7DEFROC63IoM9DeB2zVON+ylzdbQY/G/8Fz7vF7Z7E2cSkuy5IrIX3W9GP/ct UNqLHkIaS24jZS9AoSFgT+sy2Dbr8iaQMlfx7OWxEwVutuXw0Q761U1kyunlEMyQrRB5 QCnnmXdiQ5PoxzJeIrGWWKbklm2DGwECgD09WZo1D427o2D85c3RV9M6Kik9fR5hlQUx 78L3nliSJJdx3N5Y0lTnKq5+pKooZD7YAhlGFIVR6N6t/dXimOtsRAcPm1z4Ht/PLpi9 6Wk/FwgUgomTSdhluYt92GqJ+nSnq0EI3E1FQhjBtm1s5W7tzYt1H9cCbnVFKbQ7ZZbQ OIqA==
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=Ki3vR+Bvs8D4LYq0OtYKWEnCXvpRk/eJ4mD4nNKoYEI=; b=awATmNFQtx8VUipSx0KQYY5vJk33cmdNKf0JTdhcFRdovFB/UI+y2xDF7dLFL2rDJt EzZPaA/TKcZoNJJkigKcuALcyd0JPYLoIIxr7gnDYagbDmFyGIJ7Yv0XKbod8Gx5wpEE FynA0Yp5Q5EIS61dHnkyjgYdXymLSQYgkeMWP4jCtvy70y93YXKSAjgGo3z98gsluB8H kXZ8f5N3hqnmquRXIqPwaasFevskAGrrHAb6QwjhFO9OX45dLOdpkdW36Mk5543tQDM/ QzUkbM7E5O+CtoRdrnY7ZhjK3HJHHm9v7jZrGYB7/TF3VrrTfSXoV+zeC21iK8/uAQHV VIyw==
X-Gm-Message-State: AOAM533sUEAtmTc/aijZ/0NuyR6li5RcI8lO7zooYLaPXnru/2aDuSQ8 hAlYmaW4wPCHBgioqkNBbhg=
X-Google-Smtp-Source: ABdhPJzpKv8N5oSbBdA0rjAurjXsKdAoLki1RvugyTqt9en1/BxhwJuEUpqh3c1KEt0vErtquT3jLQ==
X-Received: by 2002:a05:6a00:729:b0:4f7:77ed:c256 with SMTP id 9-20020a056a00072900b004f777edc256mr22888397pfm.1.1647286936585; Mon, 14 Mar 2022 12:42:16 -0700 (PDT)
Received: from ?IPv6:2406:e003:1005:b501:db7:d041:a2d:ce65? ([2406:e003:1005:b501:db7:d041:a2d:ce65]) by smtp.gmail.com with ESMTPSA id v4-20020a056a00148400b004f9eaf80107sm392588pfu.203.2022.03.14.12.42.12 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 14 Mar 2022 12:42:15 -0700 (PDT)
To: Mirja Kuehlewind <ietf@kuehlewind.net>, John C Klensin <john-ietf@jck.com>, Lars Eggert <lars@eggert.org>
Cc: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, Peter Saint-Andre <stpeter@stpeter.im>, rfced-future@iab.org, "Rob Wilton (rwilton)" <rwilton@cisco.com>, Jay Daley <exec-director@ietf.org>, Internet Architecture Board <iab@iab.org>, The IESG <iesg@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> <040d9aac-04be-2bef-fad4-b41f2af271e9@gmail.com> <B87EBCF2-16FB-4A22-86FF-20603200E749@ietf.org> <e012452a-61d1-f499-f19e-6d3ff9863901@gmail.com> <4AD933FC-4032-4A10-92DD-A34ADEDD557F@eggert.org> <CANMZLAZmrdxQuGT=W36gUf3gEd3d1C_0c-hfdO2-gpFUOQf7sg@mail.gmail.com> <AB5E3E46-D450-4E21-B67B-D639F67734AE@eggert.org> <8b51b14e-7342-7336-2d3a-e163bf640c89@gmail.com> <066b58ac-ad6c-e5f0-5260-1b9e0267f198@stpeter.im> <242ecf9f-f7c7-7ff6-4199-ad8875b7ac6d@it.aoyama.ac.jp> <b17d4b9d-9456-41a7-0a62-45d35d2fbb07@gmail.com> <1350B8E6AB2C7ECF5AF881B2@PSB> <A3D873EB-9B8D-4416-A505-C1F11896F302@kuehlewind.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <8f92a337-3a11-2371-2d0d-c2762716f216@gmail.com>
Date: Tue, 15 Mar 2022 08:42:10 +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: <A3D873EB-9B8D-4416-A505-C1F11896F302@kuehlewind.net>
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/PaYy1tdd-DgaV4rVwU4ujO1X3cA>
X-Mailman-Approved-At: Mon, 14 Mar 2022 12:43:31 -0700
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: Mon, 14 Mar 2022 19:42:23 -0000

OK, I will take that as settling this point. I will submit draft-carpenter-rfced-iab-charter-08 with the liaison removed, for Lars to approve the posting if he agrees.

He still has to decide if that needs a 2nd last call, because it's a bit of a stretch to call it an editorial change.

Regards
    Brian Carpenter

On 14-Mar-22 23:24, Mirja Kuehlewind wrote:
> Hi John,
> 
> While I think it’s a good idea to probably document who is liaising with the IAB at each point of time, I don’t think we need to 
add the text you proposed to do that. For me the liaison that are listed in RFC2850 are the ones that are mandatory to accept for the IAB (as the community thinks that close interaction of these groups is important). However, I don’t think RFC2850 restricts the IAB in anyway to add additional liaisons (given liaisons don’t really have any special right in the process).
> 
> Mirja
> 
> 
>> On 12. Mar 2022, at 02:58, John C Klensin <john-ietf@jck.com> wrote:
>>
>>
>>
>> --On Saturday, March 12, 2022 13:40 +1300 Brian E Carpenter
>> <brian.e.carpenter@gmail.com> wrote:
>>
>>> On 12-Mar-22 13:21, Martin J. Dürst wrote:
>>>> On 2022-03-12 05:40, Peter Saint-Andre wrote:
>>>>> +1 to removing the liaison (no one seems to think it's
>>>>> needed) and +1 to the proposed text.
>>>>
>>>> +1 from me, too. I'm also okay if John Klensin's text gets
>>>> included, but I don't really think that text is necessary.
>>>> The IAB can talk to anybody they like at any time anyway.
>>>
>>> Another point is that the rfcefdp program would be stepping
>>> outside its
>>> role to propose a generic change to the IAB charter. I'd
>>> expect that sort
>>> of change to be proposed by the IAB itself.
>>
>> And I would like to hear from the IAB, or IAB members on this
>> subject.   If I am the only one who would like to leave that
>> door open, so be it.  If making the change that way seems
>> reasonable and noting that this is the first time the charter
>> document has been modified in more than 21 years in spite of far
>> greater changes to the IAB than the liaison list, why not put it
>> here and avoid extra work.  But the decision should definitely
>> be in the IAB's hands.
>>
>>     john
>>
>> -- 
>> Rfced-future mailing list
>> Rfced-future@iab.org
>> https://www.iab.org/mailman/listinfo/rfced-future
> 
> .
>