Re: [Rfced-future] Last Call Reviews of documents associated with the change in the RFC Editor model
Eliot Lear <lear@lear.ch> Mon, 14 February 2022 20:21 UTC
Return-Path: <lear@lear.ch>
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 D52B83A0DCE; Mon, 14 Feb 2022 12:21:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.604
X-Spam-Level:
X-Spam-Status: No, score=-1.604 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.714, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=lear.ch
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 7MB1nAOT4nln; Mon, 14 Feb 2022 12:21:09 -0800 (PST)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 354173A0D9A; Mon, 14 Feb 2022 12:21:07 -0800 (PST)
Received: from [IPV6:2001:420:c0c0:1011::6] ([IPv6:2001:420:c0c0:1011:0:0:0:6]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 21EKL3FN118967 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Mon, 14 Feb 2022 21:21:04 +0100
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1644870064; bh=OvHpgC630buq8CtE1jCEtAMEQjZOsvyh3KTDLXiVXnc=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=azJiQnTDVrSll0G/MrA4tjUmYIiM5huOLTfPz6JvH5hW4gFTqT+t0SsjlfkR2fdEb 3Rhs+mbLzPH/TrnbgOJSkepfsncFw7eROpfTSdQ9+mYvtoiQk+2r4teKDDgydCcF64 Xl3nI+uBSjhHs1bDTRm45XMexgKFCztDrK7SRaUM=
Message-ID: <13c819ef-9024-6ec7-a534-6e3e1a05c60b@lear.ch>
Date: Mon, 14 Feb 2022 21:21:02 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.6.0
Content-Language: en-US
To: Dan Romascanu <dromasca@gmail.com>
Cc: "rfced-future@iab.org" <rfced-future@iab.org>, Last Call <last-call@ietf.org>
References: <CAFgnS4W5CL-CKccHQJ1RRPeNCCzKY-g0paECCw66T5AepWWmyg@mail.gmail.com> <bd032a12-a78b-ab40-9464-25c98d68ace3@lear.ch> <CAFgnS4UYpsxaBAeQMK3EtaCSC20Pdwb6rBqoXtEgaWj=qSVEZg@mail.gmail.com>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <CAFgnS4UYpsxaBAeQMK3EtaCSC20Pdwb6rBqoXtEgaWj=qSVEZg@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------d0DLyFX0YuX18FA82z7Wtdfq"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/iFV9ap5_Zec828s7CAju5OnXObs>
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:21:14 -0000
AHHH.... Ok. My bad. Quite a number of documents flying around on this one. Eliot On 14.02.22 21:19, Dan Romascanu wrote: > 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 >> >> >> >> >> >> >> >>
- [Rfced-future] Last Call Reviews of documents ass… Dan Romascanu
- Re: [Rfced-future] Last Call Reviews of documents… Eliot Lear
- Re: [Rfced-future] Last Call Reviews of documents… Dan Romascanu
- Re: [Rfced-future] Last Call Reviews of documents… Eliot Lear