Re: [Rfced-future] Last Call Reviews of documents associated with the change in the RFC Editor model

Dan Romascanu <dromasca@gmail.com> Mon, 14 February 2022 20:19 UTC

Return-Path: <dromasca@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 5DB603A0E6E for <rfced-future@ietfa.amsl.com>; Mon, 14 Feb 2022 12:19:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 3xVGkKcQu_uJ for <rfced-future@ietfa.amsl.com>; Mon, 14 Feb 2022 12:19:48 -0800 (PST)
Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (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 613303A0DD8 for <rfced-future@iab.org>; Mon, 14 Feb 2022 12:19:45 -0800 (PST)
Received: by mail-ej1-x633.google.com with SMTP id lw4so9002308ejb.12 for <rfced-future@iab.org>; Mon, 14 Feb 2022 12:19:45 -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=Xvwi0Ysdf6bbpQRST/c4o4C0ct+87rEVmfr7EdbUOnk=; b=iUITXnMuLgfh7gTGa1HAhklsRauPVW6BvmJhrgrz7S/yAjFMnzlItS5X56atoc4A9t +TIakI+zA/qMaN9jT72vAvRo1i21NOeiUwkRbGSBoZN43sSFEFhyeX6xjxRj5ThOj+BF Vgnfz/LCtySaKPF0iF5Ao2tL7BZRnx0pjnTMeBWGD54fz7mD/Cl+NLzkwA6t2d0SI8La gppeNexfbJ6bhunCDbp3whv7jrTkPXi6pekM/joPrXoPRm0O3TGM+Cm3AEhUpTmb2TKG yag6OfMo2QVpQo88WqDq1Auzn4ePHlRltyivxT1qOAA3zSPKHC1arH3Dtq81eh+DReWj 3WDA==
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=Xvwi0Ysdf6bbpQRST/c4o4C0ct+87rEVmfr7EdbUOnk=; b=E01MUghlUqhhS1ZWEWzNWPGIbshq+o87Qqt5nEbSd/m/t27EYJUGViXpr0Ur2wFsOW 4lHEsy4quOmuE5AB2Gvjah46S4wqHxIHBhRo3g7iIYI2bjclBoiuo3WafKhHumBtwW7d 9U9Kl4JobeNZH2JpIRd8PGmT2Etbft4IIzdDDot7k7/QgBLt5CnfPruKRYIDycMJp2aQ vnSbt06i5pb2qFp87bf5tSAwvYeECRNnnUxfLKVuOJH25SxDetpOMR/XYA4/d51XuyCw LhZBaup9aBFwzSeHQ2YMFp5Ba/jQDqgrb2iHkKDUcOnxQ7Bjj4J73RF55p7ceIOaTQsB 97yQ==
X-Gm-Message-State: AOAM533DWtwM2F/SM5o3ilwai672f3YbBKT317t8yvkIHEjVINGc51VO WmOBzn7FkS9nO+eOKz41zDBVRF9hZFarow4WuJE=
X-Google-Smtp-Source: ABdhPJwn0Kl8xaCLhuLq2mS3hzR25cs8GNhkeanVIAw1QCyV7XifBLJ/7YoGJWuuPFXpTB5rZaIfoXEmx18pMq/IHa8=
X-Received: by 2002:a17:907:8a05:: with SMTP id sc5mr400991ejc.49.1644869981934; Mon, 14 Feb 2022 12:19:41 -0800 (PST)
MIME-Version: 1.0
References: <CAFgnS4W5CL-CKccHQJ1RRPeNCCzKY-g0paECCw66T5AepWWmyg@mail.gmail.com> <bd032a12-a78b-ab40-9464-25c98d68ace3@lear.ch>
In-Reply-To: <bd032a12-a78b-ab40-9464-25c98d68ace3@lear.ch>
From: Dan Romascanu <dromasca@gmail.com>
Date: Mon, 14 Feb 2022 22:19:30 +0200
Message-ID: <CAFgnS4UYpsxaBAeQMK3EtaCSC20Pdwb6rBqoXtEgaWj=qSVEZg@mail.gmail.com>
To: Eliot Lear <lear@lear.ch>
Cc: Last Call <last-call@ietf.org>, rfced-future@iab.org, Robert Wilton <rwilton@cisco.com>, yang-doctors@ietf.org, "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>, Mehmet <mersue@gmail.com>, Lars Eggert <lars@eggert.org>
Content-Type: multipart/alternative; boundary="000000000000f997ab05d80022f8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/m7JfLk5aeRwxY54xBxtzNWBDHFk>
Subject: Re: [Rfced-future] Last Call Reviews of documents associated with the change in the RFC Editor model
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 Feb 2022 20:19:57 -0000

Hi Eliott,

My comment was made on
https://datatracker.ietf.org/doc/html/draft-rsalz-2028bis-05.

The title of this document is ''Entities Involved in the IETF Standards
Process'.The Abstract of this document says:

>    This document describes the individuals and organizations involved in

   the IETF standards process, as described in IETF BCP 9.  It includes
   brief descriptions of the entities involved, and the role they play
   in the standards process.


This kind of contradicts your statement:


> This document does not address IETF process, but rather the evolution of
the process that oversees the RFC series and RFC editor.

So I believe that my comment stands.

Regards,

Dan

On Mon, Feb 14, 2022 at 7:19 PM Eliot Lear <lear@lear.ch> wrote:

> Hi Dan,
>
> Thanks for your review.  YANG and directorate reviews are part of IETF
> process.  This document does not address IETF process, but rather the
> evolution of the process that oversees the RFC series and RFC editor.
>
> As such, IMHO discussing YANG reviews or directorate reviews is out of
> scope.
>
> Regards,
>
> Eliot
>
>
> On 14.02.22 16:35, Dan Romascanu wrote:
>
> Hi,
>
> I reviewed on behalf of the YANG Doctors team the four documents submitted
> for comments associated with the change in the RFC Editor model. My reading
> and review concerns only aspects related to documents related to YANG,
> containing or refering to YANG models and the review process of these
> documents.
>
> Here are my findings and comments:
>
> https://datatracker.ietf.org/doc/html/draft-carpenter-rfced-iab-charter-05
>
> Ready
>
> https://datatracker.ietf.org/doc/html/draft-rsalz-2028bis-05
>
> Ready with Issues
>
> The document is ready from the perspective of the YANG Doctors, with one
> comment. The document does not mention in any place the role of the IETF
> Directorates and review teams such as the YANG Doctors in the IETF
> documents review process. As the reviews of these teams are part of the
> process I suggest considering adding text, possibly in Section 3.
>
> ttps://datatracker.ietf.org/doc/html/draft-rosen-rfcefdp-update-2026-01
> <https://datatracker.ietf.org/doc/html/draft-rosen-rfcefdp-update-2026-01>
>
> Ready
>
> https://datatracker.ietf.org/doc/html/draft-iab-rfcefdp-rfced-model-11
>
> Ready
>
> Thanks and Regards,
>
> Dan
>
>
>
>
>
>
>
>
>