Re: [mpls] draft-ietf-mpls-mna-hdr draft updates

Jaganbabu Rajamanickam <jaganbaburietf@gmail.com> Wed, 30 August 2023 17:31 UTC

Return-Path: <jaganbaburietf@gmail.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8631EC15107A; Wed, 30 Aug 2023 10:31:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, URIBL_BLOCKED=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 Fm4MDU2e8AOK; Wed, 30 Aug 2023 10:31:16 -0700 (PDT)
Received: from mail-wm1-x331.google.com (mail-wm1-x331.google.com [IPv6:2a00:1450:4864:20::331]) (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 37B70C14CF1D; Wed, 30 Aug 2023 10:31:16 -0700 (PDT)
Received: by mail-wm1-x331.google.com with SMTP id 5b1f17b1804b1-40037db2fe7so55369675e9.0; Wed, 30 Aug 2023 10:31:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1693416674; x=1694021474; 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=0x5+46H6bhdyVBTvAWRPT0RDUlllEt6wnxAV5TTpptg=; b=c4z1vLKA4zmD50cCObf16SVir5i27yE1eSGwmJItnhMECnCIzL55hnobxNhVCvYTA3 2H2yugW5/eodafs3xP7yeGMx8FWzYggxsB0a+1V4dBfyCQldjgIInafe2lET6p9eB0zX lmuHZF/oBoDyWI/0GCsSINCUloUDS6+iEDJFf9h0UJsE3lDSsxR6LvBZ3WFmZ8qrpc8u 8joD8kYL1dRT0q9rXMZ4iEUsC5d7jd/rDFR0UyGKPlAy8zCiuoA2IqFDC+pyfL9sOkGy Iy+Xm5DLrqsixgevs6rWj8WcHMSGzAlAniYTrdTFzk0ibwaI+eaWvAkWrtKI7tWdtUQU OYRg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693416674; x=1694021474; 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=0x5+46H6bhdyVBTvAWRPT0RDUlllEt6wnxAV5TTpptg=; b=Pyv8xFcpyAZPLHfS6fujOrV9rRbcTGDlG+2Il3u+Mh7rLQWb0Yggbe6SESL3mRUQh8 FGT56s0W7dKodsyErVP2eanqOwoEPHP2XCpiXSo6FLpaVKu0Iw0jn3oLd8I/9s1Z3jc/ Rq39R7fx32xKhUEKBCHfNpiVjxeP5CR1i8coBBBkGO/opQlBFUbQCLwdbaKy8Qeivs2J jvh/nPPbap1eC/JVa+RaEewogsNbzZLsULnT6hL4AmhCtQC8+uwiKRZlKZIVnmpHXhDC +zrPMGTzbxu7F61yKKVUbvpqv7exUKNp+nG/ykYvGoGGO4dhXj0OGxWn99RfWIPbTjU7 tVuw==
X-Gm-Message-State: AOJu0YxknHIicfwtnirf0zWqNSu9pb/0Ohk2WHCazR/yxCxmdjlycEWa biCaZmr2EFW99/h9M5kG+4PcTiV3RxZsau8knIw=
X-Google-Smtp-Source: AGHT+IGZKAoc7NoZtJOzbidARNHzUjmElypKsitYCgAQ/9gBhAjyt6YdgU6FMZJv5Cmj3Z3JlK6QiqE2lSHRwc1HbPo=
X-Received: by 2002:a5d:4a02:0:b0:317:3d6c:5b27 with SMTP id m2-20020a5d4a02000000b003173d6c5b27mr2582256wrq.46.1693416674530; Wed, 30 Aug 2023 10:31:14 -0700 (PDT)
MIME-Version: 1.0
References: <CAPOsKjESyVS-LcL9uPuYzLQvTTcuz-Eyfqh_Y236owrMd27sCQ@mail.gmail.com> <MN2PR11MB4064D18273A771FF06A6E6A2D01EA@MN2PR11MB4064.namprd11.prod.outlook.com> <CA+RyBmWcnhqhDjKhydRhe9mVrsFUnyDJb-Odp_L-5uB2mUyvWg@mail.gmail.com>
In-Reply-To: <CA+RyBmWcnhqhDjKhydRhe9mVrsFUnyDJb-Odp_L-5uB2mUyvWg@mail.gmail.com>
From: Jaganbabu Rajamanickam <jaganbaburietf@gmail.com>
Date: Wed, 30 Aug 2023 13:31:03 -0400
Message-ID: <CAPOsKjF-EZpETi+S7Nf8_0+CWRibpr-g33B99RstY3MixsRNMA@mail.gmail.com>
To: Greg Mirsky <gregimirsky@gmail.com>
Cc: "Jaganbabu Rajamanickam (jrajaman)" <jrajaman=40cisco.com@dmarc.ietf.org>, mpls <mpls@ietf.org>, mpls-chairs <mpls-chairs@ietf.org>, "draft-ietf-mpls-mna-hdr@ietf.org" <draft-ietf-mpls-mna-hdr@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005798eb0604274baf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/s2eVojr34GwNCNZbVoRnew2OYUs>
Subject: Re: [mpls] draft-ietf-mpls-mna-hdr draft updates
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Aug 2023 17:31:18 -0000

Hello Greg,

   Thanks for the review.

   We could add the text on RLD which you have suggested.

   For MSD, How about the below text in section "9.1 - Encapsulating Node
Responsibilities".

   The path computation needs to know the Maximum SID Depth (MSD)

   that can be imposed at the ingress node of a given SR path [RFC8664].

   This ensures that the label stack depth of a computed path does not

   exceed the maximum number of labels (i.e., MSD) the node is capable of
imposing.

   The MSD needs to include the MNA Sub-Stacks to be added.


Thanx,

Jags

On Mon, Aug 21, 2023 at 2:52 PM Greg Mirsky <gregimirsky@gmail.com> wrote:

> Hi Jags,
> thank you for sharing the updates. I have a couple of questions about RLD.
>
>    - The updated draft presents RLD as being a newly defined term
>    introduced in this draft. Although RLD might be related to ERLD-MSD defined
>    in RFC 9088, that is okay if the draft provides a clear definition of the
>    new term. Section 7, in my understanding, describes the usage of RLD but is
>    rather short on defining it. Would the following text be acceptable:
>
> Readable Label Depth is defined as the number of labels, starting from the
> top of the stack, a router can read in an MPLS packet received on its
> incoming interface(s).
>
>    - It looks like RLD is presented as a system-wide parameter. I think
>    that it might be more accurate to consider RLD per ingress interface (see
>    the proposed definition of RLD above).
>
> Also, do the Editors find it helpful to note that the Base MPLS Imposition
> MSD affects the imposition of the label stack that includes MNA?
>
> Regards,
> Greg
>
> On Mon, Aug 21, 2023 at 10:29 AM Jaganbabu Rajamanickam (jrajaman)
> <jrajaman=40cisco.com@dmarc.ietf.org> wrote:
>
>> Hello Everyone,
>>
>>    Attaching new attachments and resending.
>>
>>
>>
>> Thanx,
>>
>> Jags
>>
>>
>>
>> *From: *Jaganbabu Rajamanickam <jaganbaburietf@gmail.com>
>> *Date: *Monday, August 21, 2023 at 1:21 PM
>> *To: *mpls <mpls@ietf.org>
>> *Cc: *mpls-chairs <mpls-chairs@ietf.org>,
>> draft-ietf-mpls-mna-hdr@ietf.org <draft-ietf-mpls-mna-hdr@ietf.org>
>> *Subject: *draft-ietf-mpls-mna-hdr draft updates
>>
>> Hello Everyone,
>>
>>    Based on the WG discussion and comments, we have updated the draft. I
>> am attaching the latest draft and the diff before publishing. Please take a
>> look and provide feedback.
>>
>>
>>
>> Below are the updates made to the draft.
>>
>>
>>
>>    1. Define and use term RLD (Readable Label Depth)
>>    2. Add MNA Label in Figure 1
>>    3. Packet format to show bits 0 – 9
>>    4. Reserved bits are marked as MUST be zero and ignored on receipt
>>    5. Section 7 to clarify PHP node behaviour
>>    6. Section 7.1 added on “actions on node pushing labels”
>>    7. Deleted stale section of 13.3 on “Network Actions Flags with
>>    Ancillary Data”
>>    8. Designated Editors
>>    9. Informational References (both moved from normative)
>>
>>
>>
>>
>>
>> Thanx,
>>
>> Jags
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>
>