Re: [yang-doctors] [Lsr] Yangdoctors last call review of draft-ietf-isis-sr-yang-19

Yingzhen Qu <yingzhen.ietf@gmail.com> Mon, 22 January 2024 23:27 UTC

Return-Path: <yingzhen.ietf@gmail.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9376C18DB9B; Mon, 22 Jan 2024 15:27:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 710aWIcEMR9o; Mon, 22 Jan 2024 15:27:37 -0800 (PST)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (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 17020C18DB8D; Mon, 22 Jan 2024 15:27:37 -0800 (PST)
Received: by mail-lj1-x236.google.com with SMTP id 38308e7fff4ca-2cdfa8e69b5so41193731fa.0; Mon, 22 Jan 2024 15:27:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1705966055; x=1706570855; 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=7Nl4tFqKW0Kl42rXiP8xwGLvX0REyCN8TBxAgAKZWrw=; b=E15fW23oVvsPETT5Zpjy8KGH+45KDkJuymO2xoXzv3imTr4ozEr5j7gJrB9UgXBc0q KbQyZZ/iT/u3r31yQn5CcllnJbh/mKaJ/ZvkmZ9OWfgNmnUNC+iJ+m6oVsntHQLV0DCA tn7zjdNdnVNpMW3B25QhgT/ictcLNR+x8SJH9Xgv3PneC5mx1ivkxfMOzKtcoASmRHd2 2faYpqzAL27Sqt5a/LK0XGnIglfnValvyeLyM/yUkbIX2FYl/uz5yJCbw0jcVtabR3xp Fk85bGhYbFBPmvDu6OF081Ylv7sauy/FZ6e06lNK6x0hz2aPvEl+mvX+tHf4/d3XG98U db3w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705966055; x=1706570855; 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=7Nl4tFqKW0Kl42rXiP8xwGLvX0REyCN8TBxAgAKZWrw=; b=R7i26EhsIjYX1ESJR1x8o28ENM7Ss9Ch+qm2/Awn2c38PXkdlI3q53DF9XS0n3shqC DqM5QlWOVnSS13EWyYaAgf/P6SfYBt9YInR9iIFWoauHBARI9PeuxLt6hL57A69QmdQe LVT/rSqMelc63MChGpyDvuDsd6B7zM9N9xMBM4Ib2seWzNLAz+YM3fmpxCCsPzt+CsgQ rsZyD4XDJJ8BSiB7frauSlOn0GY4bV/3jijNrFZmUyb3zTd942Hc0vHKnAkKi+2qN1ll zI2ADxrkBFfVsNZfN2Ts+Jt4YQHcrEx94cheih00U3KT874L00juAcgjhclHhuyye33b qMkA==
X-Gm-Message-State: AOJu0YxaziAWAdS2vH9jA1tIa79E2C4N+yyAZRAtzdi968NgO0GQ1cPB OAh/DRvIdTLyhkoVUjhQ+gdjTlPpKstjps6tcWtzQrI9aPnCbjyYCcjx7+y/roXvguYv5dxfGc0 WsyV9OD8gZqrfOnj4UyiH4b1+vg==
X-Google-Smtp-Source: AGHT+IEb0K8w4keMHABeamMBA4SPXGaGRBmjmduLEFsMsvpTu0Lzfh0TSe5BrvV2HDskI/WxhdYm+oGYVph3vf3FPbw=
X-Received: by 2002:a2e:9eca:0:b0:2cd:6376:7d85 with SMTP id h10-20020a2e9eca000000b002cd63767d85mr1262323ljk.21.1705966054495; Mon, 22 Jan 2024 15:27:34 -0800 (PST)
MIME-Version: 1.0
References: <170519187203.2829.6087985821024655929@ietfa.amsl.com> <CABY-gOPzVTaCxfV=AWQwnitxyvMZUZozJP1mERZKn-8WDGeerA@mail.gmail.com> <457672390.513436.1705794832190@mail.yahoo.com> <1578607120.745334.1705932427000@mail.yahoo.com> <CABY-gOO1utYVBes7Uy+oJCnY0k0HntO+bps2-aAGr1PMCSgXEw@mail.gmail.com> <1810383000.864133.1705953157608@mail.yahoo.com>
In-Reply-To: <1810383000.864133.1705953157608@mail.yahoo.com>
From: Yingzhen Qu <yingzhen.ietf@gmail.com>
Date: Mon, 22 Jan 2024 15:27:22 -0800
Message-ID: <CABY-gONijODYBWPsoWZWTxug+FUeL0SZDmc1hv5bTwxSQPBjig@mail.gmail.com>
To: Reshad Rahman <reshad@yahoo.com>
Cc: "yang-doctors@ietf.org" <yang-doctors@ietf.org>, "draft-ietf-isis-sr-yang.all@ietf.org" <draft-ietf-isis-sr-yang.all@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>, "lsr@ietf.org" <lsr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ad5823060f912c45"
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/pmMYh6HR0afALuZVk59SKQvKwCs>
Subject: Re: [yang-doctors] [Lsr] Yangdoctors last call review of draft-ietf-isis-sr-yang-19
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Email list of the yang-doctors directorate <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jan 2024 23:27:41 -0000

HI Reshad,

I've uploaded version -21, which includes the changes we discussed.

Thanks,
Yingzhen

On Mon, Jan 22, 2024 at 11:52 AM Reshad Rahman <reshad@yahoo.com> wrote:

> Thanks Yingzhen. Yes I am good with that.
>
> Regards,
> Reshad.
>
> On Monday, January 22, 2024, 02:39:17 PM EST, Yingzhen Qu <
> yingzhen.ietf@gmail.com> wrote:
>
>
> Hi Reshad,
>
> Thanks for the review.
>
> The "sid-binding-tlv" and "mt-sid-binding-tlv" are relatively big with
> more content, so I thought it might be easier to read with a container. But
> you're right, it's not following the YANG traditions, how about the
> following?
>
>     container sid-binding-tlvs {
>       list sid-binding-tlv {
>         key "prefix";
>         uses sid-binding-tlv;
>         description
>           "Sid/label binding TLV, type 149.";
>       }
>       description
>         "List of sid/label binding TLVs.";
>     }
>     container mt-sid-binding-tlvs {
>       list mt-sid-binding-tlv {
>         key "prefix mt-id";
>         uses sid-binding-tlv;
>         leaf mt-id {
>           type uint16;
>           description
>             "A 12-bit field containing the non-zero ID
>              of the topology.";
>         }
>         description
>           "Multi-Topology SID/Label binding TLV, type 150.";
>         reference
>           "RFC 8667 - IS-IS Extensions for Segment Routing,
>            Section 2.5";
>       }
>       description
>         "List of multi-topology sid/label binding TLVs.";
>     }
>
> Thanks,
> Yingzhen
>
> On Mon, Jan 22, 2024 at 6:07 AM Reshad Rahman <reshad@yahoo.com> wrote:
>
> Hi,
>
> Typically we have a container (plural) including a list (singular). In -20
> it was done the other way round. Since this is read-only, IIRC we don't
> need the container including a list as we do for read-write. Is the
> container there for convenience?
>
> Regards,
> Reshad.
>
>
>   augment /rt:routing/rt:control-plane-protocols
>           /rt:control-plane-protocol/isis:isis/isis:database
>           /isis:levels/isis:lsp:
>     +--ro sid-binding-tlvs* []
>     |  +--ro sid-binding-tlv
>     |     +--ro prefix?                inet:ip-prefix
>     |     +--ro range?                 uint16
>     |     +--ro sid-binding-flags
>     |     |  +--ro flags*   identityref
>     |     +--ro prefix-sid-sub-tlvs* []
>     |     |  +--ro prefix-sid-sub-tlvs
>     |     |     +--ro prefix-sid-sub-tlv* [sid]
>     |     |        +--ro prefix-sid-flags
>     |     |        |  +--ro flags*   identityref
>     |     |        +--ro algorithm?          identityref
>     |     |        +--ro sid                 uint32
>     |     +--ro sid-sub-tlvs* []
>     |     |  +--ro sid-sub-tlv
>     |     |     +--ro length?   uint8
>     |     |     +--ro sid?      uint32
>     |     +--ro unknown-tlvs
>     |        +--ro unknown-tlv* []
>     |           +--ro type?     uint16
>     |           +--ro length?   uint16
>     |           +--ro value?    yang:hex-string
>     +--ro mt-sid-binding-tlvs* []
>        +--ro mt-sid-binding-tlvs
>           +--ro prefix?                inet:ip-prefix
>           +--ro range?                 uint16
>           +--ro sid-binding-flags
>           |  +--ro flags*   identityref
>           +--ro prefix-sid-sub-tlvs* []
>           |  +--ro prefix-sid-sub-tlvs
>           |     +--ro prefix-sid-sub-tlv* [sid]
>           |        +--ro prefix-sid-flags
>           |        |  +--ro flags*   identityref
>           |        +--ro algorithm?          identityref
>           |        +--ro sid                 uint32
>           +--ro sid-sub-tlvs* []
>           |  +--ro sid-sub-tlv
>           |     +--ro length?   uint8
>           |     +--ro sid?      uint32
>           +--ro unknown-tlvs
>           |  +--ro unknown-tlv* []
>           |     +--ro type?     uint16
>           |     +--ro length?   uint16
>           |     +--ro value?    yang:hex-string
>           +--ro mt-id?                 uint16
>
> On Saturday, January 20, 2024, 06:53:52 PM EST, Reshad Rahman <
> reshad@yahoo.com> wrote:
>
>
> [Yingzhen]: Thanks for catching this. I've updated the description.
> <Reshad> I looked at the changes in -20. That grouping is now gone and the
> (mt-)sid-binding-tlvs lists have no key, is that the intent?
> Also container mt-sid-binding-tlvs should be renamed to mt-
> sid-binding-tlv.
>
>
>