[RTG-DIR]Rtgdir early review of draft-ietf-mpls-mna-requirements-14
Andrew Alston via Datatracker <noreply@ietf.org> Fri, 24 May 2024 07:33 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: rtg-dir@ietf.org
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E5AB6C1D4C52; Fri, 24 May 2024 00:33:35 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Andrew Alston via Datatracker <noreply@ietf.org>
To: rtg-dir@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <171653601592.21054.11198298613171669916@ietfa.amsl.com>
Date: Fri, 24 May 2024 00:33:35 -0700
Message-ID-Hash: UNCCHSDDP7N3U7UX7RQDTJFDK3CCKK4V
X-Message-ID-Hash: UNCCHSDDP7N3U7UX7RQDTJFDK3CCKK4V
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-rtg-dir.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-mpls-mna-requirements.all@ietf.org, mpls@ietf.org
X-Mailman-Version: 3.3.9rc4
Reply-To: Andrew Alston <andrew-ietf@liquid.tech>
Subject: [RTG-DIR]Rtgdir early review of draft-ietf-mpls-mna-requirements-14
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-dir>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Owner: <mailto:rtg-dir-owner@ietf.org>
List-Post: <mailto:rtg-dir@ietf.org>
List-Subscribe: <mailto:rtg-dir-join@ietf.org>
List-Unsubscribe: <mailto:rtg-dir-leave@ietf.org>
Reviewer: Andrew Alston Review result: Has Issues Hello, I have been selected to do a routing directorate "early" review of https://datatracker.ietf.org/doc/draft-ietf-mpls-mna-requirements/ While this was originally specified as an early review, following conversations with the relevant AD, I have treated this as a last call review. Reviewer: Andrew Alston Review Date: 24/05/2024 Intended Status: Informational (See comments section) Summary: No issues found, the document is ready to proceed to the IESG - with an important caveat as mentioned below. Comments: I found the document to be well written and easy to understand, and well as being comprehensive in nature. I have concerns however about the intended status of this document. Has the working group considered making this document standards track rather than informational. My rationale for asking this question is founded in the amount of normative language in the document. This document will obviously feed into other standards track future documents, that MUST conform to what this document lays out, as such, this document almost becomes a standards document by which other standards are to be authored - and is far more than just an informational document. It is rare to see a document with this amount of normative language in an informational context, as such, at minimum, I believe that if this discussion has not happened on the mailing list, it should occur and there needs to be a fairly comprehensive writeup in the shepards review as to a justification of track. Beyond that, thank you for the document - as stated I found it well written and clear.
- [RTG-DIR]Rtgdir early review of draft-ietf-mpls-m… Andrew Alston via Datatracker
- [RTG-DIR]Re: Rtgdir early review of draft-ietf-mp… Loa Andersson
- [RTG-DIR]Re: Rtgdir early review of draft-ietf-mp… Matthew Bocci (Nokia)
- [RTG-DIR]Re: Rtgdir early review of draft-ietf-mp… Stewart Bryant