IETF Logo Mail Archive

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

Brian Carpenter <brian.e.carpenter@gmail.com> Fri, 11 March 2022 07:06 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 C434D3A0E0A; Thu, 10 Mar 2022 23:06:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, HTML_MESSAGE=0.001, 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 yuaVXaCYO7rt; Thu, 10 Mar 2022 23:06:32 -0800 (PST)
Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (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 17D6E3A0E0D; Thu, 10 Mar 2022 23:06:32 -0800 (PST)
Received: by mail-lj1-x22c.google.com with SMTP id z26so10872254lji.8; Thu, 10 Mar 2022 23:06:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=yg6NMjO+mNRDwH3iKr+bZZcl67yvQR2bZoUk+vHNqN4=; b=U5vAprwr4PWN1Kn6LBxnqky/Wo5WXt8WI/5mQNqBpsJ8eQ27+Gv/YrThMS0pxnqcIE zoBGlj/YGzvzUTUTR1yMQKijwoxtBm8AlzMLxGF9tC+fsV7iWFpK1gjflB83SXvEjPYJ yrLB1otSZ5rOABYXeRsq/RnyktLfUMZEi9KyLoAQmPpvpxG7OWuy022//IU+fX50oPtJ NKdynSpOIFLxW/6bUlULV7kQSX3tKgueKRPC8HWlvis3rHOMXuQnOElXLZ9TtJlk0puH ZU+ciP1TKDuyvGMayue2gEoDvz3w2kYvQqKb2q8kK0VgRMW21pbwBNBdxyVuu+Lhbesb 9B2A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=yg6NMjO+mNRDwH3iKr+bZZcl67yvQR2bZoUk+vHNqN4=; b=kCT8lxChwYqKLE9AANhTnDlmgYAD/Un2kwkKoqEZFFoiFyS8HLwwtndOyWZU0/1ueD bmsiBYyXi+IX/78GzINbyFRGVDIPNsgQ4FIMuXOWngSgJgYfGpM659vlx/rqbqk/zwYT Db15ZVmrXJgvQhIPavWs+3Idj4WaupKO9iKkHe34Qv6doYLL4s0xOnS4/MrRfdBF5jNL 115FwK/hQ0JSLCazSjIKb1mMPl69+3aXbqQr3qZnySqtmSLfYT7652MAnMcjRglBpw7D kOl+vmHCF+2dpLjzoCmQrL3UAvBmZ2qPpDb28q0zYyZrlr37WwSBNHJ4nxhKxV26h9vc /0Pg==
X-Gm-Message-State: AOAM532AOzketo1qoVZKSCMPd4uPmPbaysrodGfZX8fKZfYmAcjY1fcJ eYYsEXRQulC3D8cmQrFmQ+5KAhxhAUcCjswYIII=
X-Google-Smtp-Source: ABdhPJzFj7WrzTs/RrBKZe4bGy4/MY9U6dkdRY5IoqmKcEAuFSDt/co+3bOTjUwtcgFIwQu2EfykC3rBI43U4Xju3Do=
X-Received: by 2002:a2e:b892:0:b0:249:2144:1b1d with SMTP id r18-20020a2eb892000000b0024921441b1dmr337727ljp.523.1646982389441; Thu, 10 Mar 2022 23:06:29 -0800 (PST)
MIME-Version: 1.0
References: <BY5PR11MB41963ABAE51BC46E205087BDB50B9@BY5PR11MB4196.namprd11.prod.outlook.com> <134294e0-5bd5-9b22-2d95-f6032e67f516@stpeter.im> <7D016D6C-ACCE-4431-BC83-905ECB885B5F@kuehlewind.net> <c743e34d-fe46-297e-8977-dd1e4ae1963b@lear.ch>
In-Reply-To: <c743e34d-fe46-297e-8977-dd1e4ae1963b@lear.ch>
From: Brian Carpenter <brian.e.carpenter@gmail.com>
Date: Fri, 11 Mar 2022 20:06:16 +1300
Message-ID: <CANMZLAaKo-JBpyhjdd_vr69mYWS-isN9oFZGrNpGFx4ByDqy=g@mail.gmail.com>
To: Eliot Lear <lear@lear.ch>
Cc: Mirja Kuehlewind <ietf@kuehlewind.net>, Peter Saint-Andre <stpeter@stpeter.im>, Lars Eggert <lars@eggert.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>
Content-Type: multipart/alternative; boundary="00000000000046275405d9ebf8f9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/ZapGsjaPqb85yQnLJOHnSwsL0s4>
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 07:06:37 -0000

I think Lars as the sponsoring AD has to make the call on this. It would be
a substantive change to an approved I-D.

Regards,
    Brian Carpenter
    (via tiny screen & keyboard)

On Fri, 11 Mar 2022, 19:11 Eliot Lear, <lear@lear.ch> wrote:

> I don't think the liaison is needed in the new model.  Jean indicates
> the the RPC doesn't need it, and the IAB can always invite them onto a
> call when needed.  I do think there are some status reporting
> requirements that should be drawn up in the RSWG, but that's for later.
>
> Since this is a change to 2850, I suggest it be tackled in 2850bis.
>
> Eliot
>
> On 10.03.22 21:57, Mirja Kuehlewind wrote:
> > 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.
>

v2.23.0 | Report a Bug | By Email