Re: [mpls] Concerns about ISD

Gyan Mishra <hayabusagsm@gmail.com> Sun, 01 May 2022 13:25 UTC

Return-Path: <hayabusagsm@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 1B811C14F745 for <mpls@ietfa.amsl.com>; Sun, 1 May 2022 06:25:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.084
X-Spam-Level:
X-Spam-Status: No, score=-2.084 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_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 ptIpk1vZbkcC for <mpls@ietfa.amsl.com>; Sun, 1 May 2022 06:25:05 -0700 (PDT)
Received: from mail-pg1-x52a.google.com (mail-pg1-x52a.google.com [IPv6:2607:f8b0:4864:20::52a]) (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 ACD94C14F73D for <mpls@ietf.org>; Sun, 1 May 2022 06:25:05 -0700 (PDT)
Received: by mail-pg1-x52a.google.com with SMTP id g3so9916205pgg.3 for <mpls@ietf.org>; Sun, 01 May 2022 06:25:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=wryTVlAmZq0tnjSwWrOI/kHgD+gthU7twz9QDnasOJY=; b=DSBEVPd8cQ54S/BatKj2ZCeR8+cAdqvHlN/en0gpS9IKGNwL0QPJyfFPm1lhcqy3BX Zz1mPMZdGTVkAOLsqxSp6p7asUJn4N4ROqk9mAvhA+PSmoxdV3FVEoj8OkLajVrlY2PP YyJlIEwariZXE6Ib/7TIeZfR/CjkScSQt3VaaTGEpIEf8rFDzsZa9wWG/+Cp7DppR4mQ Ur3v/Ov04Np9IHGaNd0DJ39T+C1nPZG0u+BIPc+tyeTrTSx3xg6pGylwm+0gXi7rjEqH hnMybKlwZAa9ixXmGzmFLUK4757heuVa7X9Rn48ECtppc+lhmJh6/G7b/KNcc9LuLGfp G1Gw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wryTVlAmZq0tnjSwWrOI/kHgD+gthU7twz9QDnasOJY=; b=ZbmhBaxzUt4VsJWn2AYc94DEAX8I5EnBBUit2BPZ1svOarjDYXa1ZH6T5qvHWdZGRu zEplFCSwJtrCnlJ37ETzUipOxN+vnlSs2oYFjKOf03Ys4LWd0IbSnMBqSxnx7jzGjTRo Pk9mkZr+TzbqB8aXs2RmGo3Kv/xPwlYVs9KHT3AX4XzQs5WBu+hpoNK6Rd2bDbW8Insx HBFqZEgQsbi0TFH1uYxlDdZ4/BrP5UnqrwB3EX23Afx48Z/hxFB1B3Peal7Vp5Vn1ke4 SipAkGgAP1Ra+/a3iV+oU/sH7I7pt4ncs9Ng1hXTM7vPnBFbVoU23NBET7XlzFyrMFaf SDwA==
X-Gm-Message-State: AOAM533MCS2nVyqJviAcjNBS8K5wfrgaBL3Z57nNkmjL+Ge9X5p8FHpk pQVZh29kuMxg+8nrmneoMyihfj85/YS5iovaeS8=
X-Google-Smtp-Source: ABdhPJxXwtHpGC0KAo2yweAQRUI5mgiB5xYpemz5hbjQEZWOnl8VfWmivlEdfylToLMRAUxoL7CTtooeb7PJ3B/1JtU=
X-Received: by 2002:a63:257:0:b0:3aa:a481:9159 with SMTP id 84-20020a630257000000b003aaa4819159mr6226078pgc.1.1651411504714; Sun, 01 May 2022 06:25:04 -0700 (PDT)
MIME-Version: 1.0
References: <6cc272447d2f4c779e85d5c42d3b3c6c@huawei.com> <8623637D-A32E-47A4-B5FC-4D2CF40BEDD1@tony.li> <6199e0e886f9437c95ef9b70719b00ec@huawei.com> <BCFD3F4A-36D6-47C2-B907-FC40B402F97C@tony.li> <3fb1f261ddff48deb0c2ea083cdbd16f@huawei.com> <6B96F21B-9331-4FA8-AD7B-84A4CA8B6FAB@tony.li> <903c57a48280454091495673ec2fe275@huawei.com> <BD5C1BE7-4633-4B51-BAC1-B2AE1C537F36@tony.li> <ad6b8c42b0aa4880b9dee02516f5e46f@huawei.com> <F5BB2CEB-CC8C-4E71-A2E7-B4212878C3B1@tony.li> <aa9c4b913d844410b2af90c8db78c194@huawei.com> <BY3PR05MB8081937B52E657713E8293BFC7ED9@BY3PR05MB8081.namprd05.prod.outlook.com> <a29c96be774845e582a66700d2264f7b@huawei.com> <e986565c98c24cadb858ca4abf6dbbfb@huawei.com> <BY3PR05MB8081A6A725740415356DB2EBC7FA9@BY3PR05MB8081.namprd05.prod.outlook.com> <eb8d7858982d449e94511f81eb9913c8@huawei.com> <BY3PR05MB808117E628EC6487362E6275C7FD9@BY3PR05MB8081.namprd05.prod.outlook.com> <ded09bb6ec864465982f5e025937c8e0@huawei.com> <BY3PR05MB80817C746EF6621F80730082C7FC9@BY3PR05MB8081.namprd05.prod.outlook.com> <41561193f7d448ff96129d6da20e49a2@huawei.com> <535C336B-545F-4E0E-A9DF-990FC0AB53CC@juniper.net>
In-Reply-To: <535C336B-545F-4E0E-A9DF-990FC0AB53CC@juniper.net>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Sun, 01 May 2022 09:24:53 -0400
Message-ID: <CABNhwV3LsUAL6c8Z8Qw5ZHAvhcteeBP3cULiZru_JmoL5555KQ@mail.gmail.com>
To: John E Drake <jdrake=40juniper.net@dmarc.ietf.org>
Cc: Tianran Zhou <zhoutianran@huawei.com>, mpls <mpls@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001dd85c05ddf33434"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/9syeQ2e4VYYQwVzNzuVHWxPry_U>
Subject: Re: [mpls] Concerns about ISD
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.34
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: Sun, 01 May 2022 13:25:11 -0000

Hi Tianran

Comment on-line

On Fri, Apr 29, 2022 at 12:05 PM John E Drake <jdrake=
40juniper.net@dmarc.ietf.org> wrote:

> Comment inline
>
> Sent from my iPhone
>
> On Apr 29, 2022, at 11:17 AM, Tianran Zhou <zhoutianran@huawei.com> wrote:
>
> 
>
> [External Email. Be cautious of content]
>
> Hi,
> Comments inline.
>
> Tianran
>
> >
> > Hi John,
> >
> >  If we want to reuse this for consistent design (easy for interop), how
> do you
> > want to encode it to ISD?
> >
> > [JD]  That's up to a given solution to propose, but probably two LSEs
> >
> > ZTR> It would be interesting to know your proposal.
>
> [JD]  As I said, the size of an NRP ID needs to be decided and any MNA
> solution needs propose how it is to be
> encoded
>
> ZTR> Ok, so any solution need to demonstrate how it works.
>
> >
> >
> > 2. If we really worry about the MSD of SR, why not use BSID as a direct
> way to
> > reduce the stack?
> >
> > [JD]  Because it can't be mandated
> >
> > ZTR> I am sorry, I do not understand why BSID is not applicable. What's
> the "
> > mandated " mean here?
>
> [JD]  MNA cannot require the use of BSIDs
>
> ZTR> Is this an agreed requirement? In the requirement draft? I still
> can’t understand. On one hand, you worry about low stack depth. On the
> other hand, you don’t want to use an easy way to solve this problem.
>
>     Gyan>. BSID is not a requirement for SR architecture per RFC 8402
 section 5, however is required for SR-TE.  All implementations of SR-MPLS
requires SR-TE for steering, however not mandated.  BGP SRv6 services TLV
encoding SRv6-BE w/o SRH or SRv6-TE w/ SRH TEA can function without SR
Policy.  So per John why BSID is not made a requirement for SR architecture
to give flexibility for implementation as well as to operators is my
understanding.  BSID does help with scalability and MSD and so most
operators deploying SR would take advantage of SR-TE BSID for SID list
compression.

> [JD]  I don’t think it’s realistic to tell a network operator that they
> have to deploy BSID in order to deploy MNA.  Also, I don’t think it’s a
> good solution became a label stack of BSIDs may still be too large and the
> node advertising the BSID is going to expand the the label stack with the
> path SIDS so the nodes on the path will have to deal with a large label
> stack.
>

> >
> > Tianran
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*