[RTG-DIR]Re: [Last-Call] Re: Rtgdir last call review of draft-ietf-mpls-msd-yang-07

Dhruv Dhody <dhruv.ietf@gmail.com> Wed, 05 June 2024 06:22 UTC

Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: rtg-dir@ietfa.amsl.com
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B58AFC14F736; Tue, 4 Jun 2024 23:22:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level:
X-Spam-Status: No, score=-7.096 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_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tx77RIKBBfzk; Tue, 4 Jun 2024 23:22:46 -0700 (PDT)
Received: from mail-vs1-xe34.google.com (mail-vs1-xe34.google.com [IPv6:2607:f8b0:4864:20::e34]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC987C14F6B4; Tue, 4 Jun 2024 23:22:41 -0700 (PDT)
Received: by mail-vs1-xe34.google.com with SMTP id ada2fe7eead31-48bbcaf093bso1320058137.2; Tue, 04 Jun 2024 23:22:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1717568560; x=1718173360; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=JzVzKkjHrULcHklS+ZuvcZHTdqIctCORJYxuyVVhocI=; b=V7Hkw6JLinK2YKMWKnWY6FNFdocpSGpLkzTrqTx3XOW6rHrDPdosj6h1MDDKjdpbt6 fzigP0yEogRvV3wAzP8wkn+Zz4MwcTQU8cS33vt+BKX8oq9W/Wf+ztzifCbdQgc/S1xd nEurs44sdKWd6n9kWtxZsXY/Fij3sUlqUmCkSVf2CZBOqG+vJaNvBakw0XgG3TEnc/lN lrazUEQ5FlEkNyKi2sPnAds+ojIq4NzLh7JrCMichGAsydEeBLt7MMHAu5pQ+WY/sP4X rRw13b2CQBwAn9xKDPHWInVXcCc4Z1ak6EctCoDBD0+y+yA++Z2NA65PKe4hSjs0pLMs ZWvA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717568560; x=1718173360; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=JzVzKkjHrULcHklS+ZuvcZHTdqIctCORJYxuyVVhocI=; b=dyjaFA53b3tOeSITyV59ybQDUMSxhc4INv5fL9jBgAk0xXfYfEfthopqii3wji35sv auf7M58mM/l26IDKTaSCPdZzqsvflH2mQtv12sY0QuAlOhcTFoAVfk6UrMd0smM2iTyf 3nN6U97BGLt1xzt99+A2uSE9/OoWDE2ZB6oRpj7P77DR3AM38rFpwFSNOOVHYSowT2h6 BUNdKtmbP5stQTf6nDYXAbJ3D/qgbY2rfIkiUvZ/RqmbepniQiORvMffWmzaMz0znQSw HvylZJ8szHCHSkyD9KmHkTh1UTBOfA7Tve1IvdnPUaprROTYlyPWP3BSGsUAk9B2Fqfa E7sA==
X-Forwarded-Encrypted: i=1; AJvYcCWq6tc2Y7+gHaJAE/QkuxAW9/biiu/OeH1B8NwECEP2uZFBAJYhWinm1tehINz9owY+jWl5E61WB7QptuSKubQ7nOPymFZxl7x68mliOO9kuqxFR+kCH/BGDVxymP7+TiaFgis2GaEWA0CUBEEdzDj/4vpn00Bf+Tjxi8aoxmUvXAX8PzdFXDKvgUU=
X-Gm-Message-State: AOJu0Yy1Cxniz1d0oeoQjW46jQqn3SXIBd9wonRuY4KlIio3VrA+VUoD Zn1io3ECLp2kfzwjVQQG8kb9VkSgAgeB8Pu5tTii4pP6kgjFoF3bsEFPX8g9cZo99B5oTsFMFi6 HchPyxd4kO/D88SgoTFfBq5/EBKk=
X-Google-Smtp-Source: AGHT+IGd8TQtAGfWtvHcLPubzUOmCq5W8SLo4kWnvNzFdMNDcuQHIw29jLgr0v5BMbhEpWgHnE1/g0kIU/orAm+MXSs=
X-Received: by 2002:a05:6102:2a46:b0:48b:a171:b162 with SMTP id ada2fe7eead31-48c0483e845mr1953865137.9.1717568559670; Tue, 04 Jun 2024 23:22:39 -0700 (PDT)
MIME-Version: 1.0
References: <171743797081.42914.4518891340142384843@ietfa.amsl.com> <CABY-gOMdwJRExQ0mP-gH4QaW_=3m8SbQB__wgWpe0E-1XGVVHg@mail.gmail.com>
In-Reply-To: <CABY-gOMdwJRExQ0mP-gH4QaW_=3m8SbQB__wgWpe0E-1XGVVHg@mail.gmail.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Wed, 05 Jun 2024 07:22:02 +0100
Message-ID: <CAB75xn7UGmejG1YP3VSjtWMswyZiCt2vyADCWk8gChjqtZqgXQ@mail.gmail.com>
To: Yingzhen Qu <yingzhen.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000e06f15061a1e970e"
Message-ID-Hash: 72GMADY4UTLMDQ7VHHKVG4OOLQPQQNKB
X-Message-ID-Hash: 72GMADY4UTLMDQ7VHHKVG4OOLQPQQNKB
X-MailFrom: dhruv.ietf@gmail.com
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: Dhruv Dhody <dd@dhruvdhody.com>, rtg-dir@ietf.org, draft-ietf-mpls-msd-yang.all@ietf.org, last-call@ietf.org, mpls@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [RTG-DIR]Re: [Last-Call] Re: Rtgdir last call review of draft-ietf-mpls-msd-yang-07
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/keKXBzisfruuhIz1eyFxVhUMmPU>
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>

Thanks for taking my comments into consideration! The new revision looks
good to me!

On Wed, Jun 5, 2024 at 6:55 AM Yingzhen Qu <yingzhen.ietf@gmail.com> wrote:

> Hi Dhruv,
>
> Thanks for the review and comments. I've uploaded version -08 to address
> your comments. Please see my detailed answers below.
>
> Thanks,
> Yingzhen
>
> On Mon, Jun 3, 2024 at 11:06 AM Dhruv Dhody via Datatracker <
> noreply@ietf.org> wrote:
>
>> Reviewer: Dhruv Dhody
>> Review result: Has Issues
>>
>> Hello,
>>
>> I have been selected as the Routing Directorate reviewer for this draft.
>> The
>> Routing Directorate seeks to review all routing or routing-related drafts
>> as
>> they pass through the IETF last call and IESG review, and sometimes on
>> special
>> request. The purpose of the review is to assist the Routing ADs. For more
>> information about the Routing Directorate, please see
>> https://wiki.ietf.org/en/group/rtg/RtgDir
>>
>> Although these comments are primarily for the use of the Routing ADs, it
>> would
>> be helpful if you could consider them along with any other IETF Last Call
>> comments that you receive, and strive to resolve them through discussion
>> or by
>> updating the draft.
>>
>> Document: draft-ietf-mpls-msd-yang-07
>> Reviewer: Dhruv Dhody
>> Review Date: 2024-06-03
>> IETF LC End Date: 2024-06-04
>> Intended Status: Proposed Standard
>>
>> ## Summary:
>>
>> * I have some minor concerns about this document that I think should be
>> resolved before publication.
>>
>> ## Comment:
>>
>> * This draft defines 2 YANG models one is IANA-maintained to mirror the
>> msd-type registry and the other is augmenting base MPLS to include MSD
>> values.
>>
>> ### Major Issues:
>>
>> - Please remove the BCP14 boilerplate (Section 1.1) as you are not using
>> any of
>> those keywords. Also, remove from the ietf-mpls-msd YANG model.
>>
> [Yingzhen]: removed.
>
>>
>> - You should explicitly state that this is an initial version of
>> "iana-msd-types" YANG model - "This document defines the initial version
>> of the
>> IANA-maintained 'iana-msd-types' YANG module."
>>
>> [Yingzhen]: fixed.
>
>
>> ### Minor Issues:
>>
>> - Title: Please change to "A YANG Data Model for MPLS Maximum Segment
>> Identifier (SID) Depth (MSD)". Also, update the reference in the YANG
>> model
>> around RFC XXXX.
>>
>> [Yingzhen]: changed the title to "YANG Data Model for MPLS Maximum
> Segment Identifier (SID) Depth (MSD)" .
>
> - The abstract suggests that only one YANG model is defined in this I-D.
>> Consider rephrasing or adding some hints about the IANA model as well.
>>
>> [Yingzhen]: updated.
>
>
>> - Section 1, "YANG [RFC7950] is a data definition language.."; I suggest
>> changing it to data modeling as that is the term used in the referenced
>> RFC.
>>
>> [Yingzhen]: modified.
>
>
>> - Section 1, I am unsure about the text "The augmentation defined in this
>> document requires support..."; isn't it obvious that one needs to support
>> the
>> model one is augmenting...
>>
>> [Yingzhen]: removed this sentence.
>
>
>> - Section 4, please add this text in the description inside the YANG
>> module -
>> "This YANG module is maintained by IANA and reflects the 'IGP MSD-Types'
>> registry."
>>
>> [Yingzhen]: Done.
>
>
>> - identity msd-erld, should also have a reference to RFC9088.
>>
>> [Yingzhen]: Done.
>
>
>> - In "ietf-mpls-msd", please remove the reference "RFC XXXX: A YANG Data
>> Model
>> for MPLS MSD." immediately after the module description. The revision
>> statement
>> is the correct place to have this reference.
>>
>> [Yingzhen]: removed.
>
>
>> - leaf msd-value should also include text for "0 represents the lack of
>> ability
>> to support a SID stack of any depth".
>>
>
> [Yingzhen]: Added.
>
>>
>> - I can not parse "A type of Node MSD is the smallest same type link MSD
>> supported by the node.";"
>>
>
> [Yingzhen]: tried to rephrase.  Hope it reads better now.
>
>>
>> - RFC8340 should be normatively referenced.
>>
>> [Yingzhen]: RFC8340 has been an informational reference in YANG RFCs.
>
> ### Nits:
>>
>> - s/(MSD) Types as the IANA the IGP MSD-Types registry/(MSD) Types as per
>> the
>> IANA IGP MSD-Types registry/
>>
>> - s/which itself augments [RFC8349]/which itself augments routing RIB data
>> model [RFC8349]/
>>
>> - s/IANA maintained module/IANA-maintained module/
>>
>> - s/This module will be maintained by IANA if more MSD types are added to
>> the
>> registry./This module will be maintained by IANA and updated if and when
>> there
>> is any change in the registry./
>>
>> - s/and it is to provide support of different types of MSDs in MPLS data
>> plane./and it provides support for different types of MSDs in the MPLS
>> data
>> plane./
>>
>> - s/read-only data decided by/read-only data as per/
>>
>> - Section 4, expand SID on first use in the YANG model.
>>
>> [Yingzhen]: nits all fixed.
>
>
>> Thanks,
>> Dhruv
>>
>>
>>
>> --
> last-call mailing list -- last-call@ietf.org
> To unsubscribe send an email to last-call-leave@ietf.org
>