IETF Logo Mail Archive

[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 15:36 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 787503A105C for <rfced-future@ietfa.amsl.com>; Mon, 14 Feb 2022 07:36:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.097 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_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 B0rwoSVCupc8 for <rfced-future@ietfa.amsl.com>; Mon, 14 Feb 2022 07:36:09 -0800 (PST)
Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (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 C41CB3A105B for <rfced-future@iab.org>; Mon, 14 Feb 2022 07:36:08 -0800 (PST)
Received: by mail-ed1-x536.google.com with SMTP id u18so27592855edt.6 for <rfced-future@iab.org>; Mon, 14 Feb 2022 07:36:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to:cc; bh=MfSgJPv4YHqzI0fzL1MuxQA/SW1f1AB8SHnwNbR6v7o=; b=GQlvL0tIpQeapOhUJ8JlOWHlLk48+VssDy060hJ/zvUsOuuEwg6eNjaexdJHHvs048 mX8sKo4sdH/5vXVPdIQ1kjr/ZpbeOyEE+7Gvriil1tGcQ3pR1EkGmvAn2STSl9mI6ye+ m2GUf18PnuXuVQRVuh0wPxsJbzJrOz4LxORjoD/b0D5GOlygZH6PPcxDOKRdp63lc1r6 WrOs5QXYO0EWqSu5JbnzXfqONMQtvB9HKPquJEvoKhZ0k9sW4Uw4BfRPwsdcsRxJoClK aLzp4bXJPe++iIwDZf+zEqjB91apaSfXJKvlTm5WQb4y6HZdF6ZfgUdTyGEhFl1BRjpE Ig4w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=MfSgJPv4YHqzI0fzL1MuxQA/SW1f1AB8SHnwNbR6v7o=; b=jPquFj3DXHJLya3SSdVaW2+cIsycFYR0kNOVXwwQ/TaxrlkEXFHSLWA1oOYTVxOlEF v/5kvrO1ruO+fGJogPrHLbljTNE+38C5aw/rtAMFR53/VqlOC+94l4C9rPr/ar/xN+g/ uYGyu0K5ZAakdzpCyrVP/5gzmZ80D80PMvGXTsINkZl+iTqkuqHr280qwuZvCIp+woHP zmsWapdyTEhnCP2cgR73C+F/sx9UJsWxOvOpP+jREKus6OoCLEa+bBoP3P4KccF2nuw2 mSr18l77fBIn70IM/bRSBAp0DXAuN3KKrDf6ZEpd5K01VWdnNZYqodkRrI0l5MxAK1A6 4I6A==
X-Gm-Message-State: AOAM531AdjzWyAMFFghBJi8iaCSwh0gEa1RJ9/Mj3X8r9g3oZ/h7qQhU 6XBi22wDju0viTcJQqA4H0svmv34xC51G7J3bQu8kugjQAU=
X-Google-Smtp-Source: ABdhPJwTmtMunINExVDy9PFvi6fCHFOxZpQHo8qUkzdFS/biia6K2i62mAqlPm4IHMevtq028C4pkj3SEnj0L3+ayww=
X-Received: by 2002:a05:6402:2916:: with SMTP id ee22mr143191edb.3.1644852965225; Mon, 14 Feb 2022 07:36:05 -0800 (PST)
MIME-Version: 1.0
From: Dan Romascanu <dromasca@gmail.com>
Date: Mon, 14 Feb 2022 17:35:53 +0200
Message-ID: <CAFgnS4W5CL-CKccHQJ1RRPeNCCzKY-g0paECCw66T5AepWWmyg@mail.gmail.com>
To: Last Call <last-call@ietf.org>, rfced-future@iab.org
Cc: yang-doctors@ietf.org, "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>, Lars Eggert <lars@eggert.org>, Robert Wilton <rwilton@cisco.com>, Mehmet <mersue@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000b335ed05d7fc2c66"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/MUZPJyZBbisEzLlopQIq_Uh3qjQ>
Subject: [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 15:36:11 -0000

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

v2.23.0 | Report a Bug | By Email