[RTG-DIR] Rtgdir early review of draft-ietf-mpls-mna-usecases-04

Dhruv Dhody via Datatracker <noreply@ietf.org> Sat, 13 April 2024 16:20 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 84718C14F6A5; Sat, 13 Apr 2024 09:20:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Dhruv Dhody via Datatracker <noreply@ietf.org>
To: rtg-dir@ietf.org
Cc: draft-ietf-mpls-mna-usecases.all@ietf.org, mpls@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.10.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <171302525152.8030.7167983985666849484@ietfa.amsl.com>
Reply-To: Dhruv Dhody <dd@dhruvdhody.com>
Date: Sat, 13 Apr 2024 09:20:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/e1yxYc0xrqocliUNifrYdaSHiu4>
Subject: [RTG-DIR] Rtgdir early review of draft-ietf-mpls-mna-usecases-04
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-dir/>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Apr 2024 16:20:51 -0000

Reviewer: Dhruv Dhody
Review result: Has Issues

I have been selected to do a routing directorate “early” review of this draft -

The routing directorate will, on request from the working group chair, perform
an “early” review of a draft before it is submitted for publication to the
IESG. The early review can be performed at any time during the draft’s lifetime
as a working group document. The purpose of the early review depends on the
stage that the document has reached.

As this review request was marked by the working group chairs as "In prep for
WG last call", my focus for the review was to determine whether the document is
ready to be published. Please consider my comments as if they are early
last-call comments.

For more information about the Routing Directorate, please see

Document: draft-ietf-mpls-mna-usecases-04
Reviewer: Dhruv Dhody
Review Date: 13 April 2024
Intended Status: Informational

## Summary:

## Major:

- Section 2.x, the listed use-cases lack text that can link them to MNA.
Basically, how do they act as a use case for MNA? What indication and ancillary
data will be carried? I can imagine how but it makes sense for the use-case I-D
to be explicit about it for the reader.

- Sections 3 and 4 read more as a requirement for the MNA solution and not as
use-cases. Perhaps they could be rephrased?

## Minor:

- I found the sentence "This document describes cases that introduce functions
that are based on special processing by forwarding hardware." hard to parse.
Consider rephrasing. Why hardware?

- Add references for special-purpose labels and extended special-purpose labels.

- We need to list a stronger motivation for MNA than just saving
special-purpose label space.

- Change RFC XXXX to RFC 9543

- The NRP Policy is not defined in RFC 9543, maybe the better reference is

- Security consideration, while I agree with the text but consider having some
useful pointers to other I-Ds could be useful.

## Nits:

- Please add MNA in the title of the I-D

- add "working group" at the end of the 2nd sentence in the abstract.