Re: [Idr] Few questions about Segment Routing extensions for BGP LS (draft-ietf-idr-bgp-ls-segment-routing-ext)

Boris Hassanov <bhassanov@yahoo.com> Fri, 20 August 2021 16:35 UTC

Return-Path: <bhassanov@yahoo.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7632F3A154E for <idr@ietfa.amsl.com>; Fri, 20 Aug 2021 09:35:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.318
X-Spam-Level:
X-Spam-Status: No, score=-1.318 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_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mkyLNk8oSfKU for <idr@ietfa.amsl.com>; Fri, 20 Aug 2021 09:35:25 -0700 (PDT)
Received: from sonic301-3.consmr.mail.bf2.yahoo.com (sonic301-3.consmr.mail.bf2.yahoo.com [74.6.129.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CA723A154D for <idr@ietf.org>; Fri, 20 Aug 2021 09:35:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1629477324; bh=wyTzjXKxizeTdi7MYZr80nR4bGi9rWImldXTVxS8r3s=; h=Date:From:To:In-Reply-To:References:Subject:From:Subject:Reply-To; b=nXc4e2TZ9Ovvx4n8YA1rRvzIbfWcm1rSQMikLIuadNi1PcJaYfRbmsSYmyFEJ6BJNQbS6/gzSlKy4tlPGzYLNGeXcF49UnBbk68eoRrTVssRNEuGCwmsjZK0OfPeO+F7AOoHrjrFZoSECplpBhHPacl+5GAw0VWak7PyVojdK6KbxuKseNSrLbAbAfUJyGdwHIdVNHcb69TpOqRodG9f9HwpLpxTfESBJG8/2QWx4W1lbS86QklEgLemAfkEgP6k3hX5n+57Stm53T8UuoVfGhouJXHxNsKEwGm3SeMzLp6zH3kYbAvo3xTH8N+dsP4jWM5HIGowIcdpWwCv1/tdng==
X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1629477324; bh=729w5jmeA6qL2WmasK2Mu4FuGy3XG51JfvpYDzdqCgz=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=q2fyeF0kOPr2F/VCH1IrOU5lwCQgwbC84prTeZrzuqDoipKDuwDRhEMRmSzbYcic3pdRJvE4Y8kFRYNZiP2yQi/mkwCvCRoLS2dvYPnVhS7G/jy9GOPdkQVXASO64d5pCEUjll+z4E5Yygtjkl47aENDOmUdUtEt16N7d7sxeIF1vyL05pByKFzGKjjr/JCD7psFqoBHwI7+GY0ryQHUzsA68QHl1LElvbwg5Am3jZfixHuKT5XqPUarIZdrGcQUkYV42TDSVd13rb9xxoBco9Kq5OFIzMM5CZsUPfh49Xj/9KVfP3A+7BPO6XxnonvJ3Jgib3n5tpkzAdUnoIKcCQ==
X-YMail-OSG: RqGyMI8VM1kfEA.VO8Vs6SsLstAb6RXfoY3SuHkai46eMqzU.FoUL8fhi0dvtme yEHvHkd9opnOMJ_ksZPWTlZzM8hQeVf2lGUN6Ze3xDpog4OuvFTzL3ZZItzXH.sO3nCPzppk8Uhh wHwmOQaTcJBDS9JCJWzdwngv0FJGZ23rCU6p4mhqAxVriXDAGFECHkFdE3t87lHvnbfrJCB0o8ZE R2l2bYzyNbQnptrkONDfINSuPlJeLJ4ZEAfoJ_mY.765_UwrV3854GmTix8GziPvm8_Zk900KwCl 67jUGJ18uQRcAjGy1kLdGudIJqPqSpaICq5UKe60DdCJ5giFWl2vC4lVy4RTgOAFCYgE0eAeITJr wzBPlafPxOKKE1KCk22igv9f_7UqcQkcac1t4.z9_kbrd94JXXH4Vd.zvq0zf5804bRGzvgQ4Epm Cj3cxqZ492oh_PqkQj40wnOK_EyvLxOAsRiHDlgqkvT.sbUvMjv2eLpJ4r95L_CrmFZp1qk1z.M8 HKtK3OKJYwqpE2ptPtcyr4JGB1Cgc7RxBtjawRG2MGNJXfR0KkKJGeYUo7Mm9uw3xYDvMKDMf.wa B0MXZ96UqfTK5JH.EuxCCgNae81SkmzCH6ybkofND380YOgZnKh36eUdqB6kO3IO6NV1RFsYqE9i RMAGYJlI7UxKEkhXGdG10u0_W_HraitW7XJ.e_JppMQ0_3EgbzRXKc0STPzvRZF2yRoc9Xr6c8c3 5jSTtZkrpU6hksLFfKQMZKvD8Cy9eeT8Cdl7SOhq.RYwLRH.X4pf9i5ELwWpP4mZoqsyztSNKyuv EYUdqbhHxCB7ujv0JsIWB.6SEB2YO7ymGAVe3vEHuo_fkm4qH1DlremTYeAUgh_2QnGA3IwPKXh. PbZ417mvOkIvpsZVRbdbJpPoV1L.0r0fZ8nSzWY0QNFpO0.OB26Lf8_7z5h49zU7J7enpwiXA8kY UBoj8KVlrLrvDETnjp1jqIZ_MLY9bl._NN6zCZfBW17N2.WeQy_.2JTU3LaTdhlVkoJp7bDcuv3l 9Xn2VmR6R44GZuDxxqkB8WpJYt3TfbOKruOSFMHDDc03btFNcA2v1fvhhAtkMCXGtDuc78zrWIHW Vv49Pk31p2YT.9kyn3GRroJeR_ctVk1fR7oUwAUnz2UWNWQ.lbkhAHRmL139voMJ2XgrJ6dorjb1 duX3zcmxQzmJar56U9wa6mplyfX9y.oUrVwWyjaz1Cf1zaowmdpeUeQ0tL_4.uOc.lpKHGfBPPVX glRUnpeONL_T6oGO8QhJT3wsLzKfz6GeRa8hyCvOvDHjm7_PFrsTrBZbUSRgEJMv0QGV5mPpMEpA mFcxq6hPN._seu7VrvT7BDQvqoaMyrf9Ie3.SdLc85J0VKyx9MmtfLbmvT4GLdrGnX0Ofz8Gidvr QYKxKSp9qoo.AECZsh.0tuXM0JhGGNlZ3.Y3.MAIY9X8Bpmzaq3uPEpTu3XGepjAh3Hk7sNnHv6i z8VHdiylfR3XBrbCvoYu_NLM3Z4VEvUWhxywwZo82t6.WPU469SRuFwWVj3KpbYJbu3lxhgwVS91 YYf4VwqseRMEmdaeZSLI732LLbVV6kKE.5vPCW_yAurX7yGHyALoGpF55PlApo73fgc6CJsbkZ49 qVqdle.cD0X3dV4rJ9raX9CQkf5oS3BySitSRn9B5hUTRDUCP2SaJb3XifWj3xWSlLsgpqs8s8f3 VDxHfB_u_L4HKLeoDLYMOBRTbKLAhaLSFHQNb3f9hNUX03lNHcjeWcIhQT7P5Fq6Ti1FYDImFo8a DZziB5HAfmBA.mJP8IA7Xo10mHtMtB13rBHVAG2tTjoOGsJmgRjUYfioutiao9Lkp803YILipeI_ GPKNmyq3JXnsbKFv.clLOVvv0hG6_baUh0qEp4YMtbcZ1PTLkARLOiPmWzlwsjfdZjWYV1.I0xIm g5qCtjp_LckZv7IbFJY6JAu2dwdiHGPJJNxKKD1HyEXOcIFmhll9UXv5XmUg090inDuemGO4aY.v zg5ZWapjlhsqKFilTX7wk8JBgagEBxyVuMKrjy29E_jacavjmOyaqR4PZLZqPQxWwCfyOTtVhoW7 qOgTa2KM0xs31JdeYveid8rGjeQbz0o2B917oPDwlMWo4v45re6TWXpcZYs6CiBnI77I488Hw.j4 0JVwOJAqQWA5g8ALed9Wmyt4jpFSf_Dt1VfRi_9NojPQr9BDwcqkvtaRH1lTAFgkTCqXVRkcH6Sw Z2EV2ZYNF2u2s.i3B4PyQYOzVbUiem1tCrTomOTLSxEeXtoY80sJFd8441tZcJyoFuXtqWygOvFZ 29rOat0OPsWRjJnJ5qOwg_5XywQPiIWA24iPffFaM8H2zZCXKoA--
X-Sonic-MF: <bhassanov@yahoo.com>
Received: from sonic.gate.mail.ne1.yahoo.com by sonic301.consmr.mail.bf2.yahoo.com with HTTP; Fri, 20 Aug 2021 16:35:24 +0000
Date: Fri, 20 Aug 2021 16:35:18 +0000 (UTC)
From: Boris Hassanov <bhassanov@yahoo.com>
To: Boris Hassanov <bhassanov=40yahoo.com@dmarc.ietf.org>, IDR List <idr@ietf.org>, "Ketan Talaulikar (ketant)" <ketant=40cisco.com@dmarc.ietf.org>
Message-ID: <834507420.378150.1629477318882@mail.yahoo.com>
In-Reply-To: <MW3PR11MB457012F92C38715126ED4F7EC1E49@MW3PR11MB4570.namprd11.prod.outlook.com>
References: <1162423632.764584.1626861282633.ref@mail.yahoo.com> <1162423632.764584.1626861282633@mail.yahoo.com> <MW3PR11MB457012F92C38715126ED4F7EC1E49@MW3PR11MB4570.namprd11.prod.outlook.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_378149_1556636166.1629477318879"
X-Mailer: WebService/1.1.18850 YMailNorrin
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/QagXe0JQPb0kaWT5jXzF2pE6ie4>
Subject: Re: [Idr] Few questions about Segment Routing extensions for BGP LS (draft-ietf-idr-bgp-ls-segment-routing-ext)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Aug 2021 16:35:31 -0000

 Hi Ketan,
Sorry for delay with reply, I decided to postpone it after IETF-111.
Let's return back to Anycast SID. I carefully read RFC 9085 section 2.3.2 and cannot see there Anycast flag at all ( may be I missed it somewhere):" Flags: a variable-length Flag field (according to the Length field).      Flags are routing protocol specific and are to be set as below:

      *  IS-IS flags correspond to the IPv4/IPv6 Extended Reachability
         Attribute Flags defined in Section 2.1 of [RFC7794].  In the
         case of the X-flag when associated with IPv6 prefix
         reachability, the setting corresponds to the setting of the
         X-flag in the fixed format of IS-IS TLVs 236 [RFC5308] and 237
         [RFC5120].

      *  OSPFv2 flags correspond to the Flags field of the OSPFv2
         Extended Prefix TLV defined in Section 2.1 of [RFC7684].

      *  OSPFv3 flags map to the Prefix Options field defined in
         Appendix A.4.1.1 of [RFC5340] and extended in Section 3.1 of
         [RFC8362]."

Those IS-IS and OSPF flags are only define N-flag (Node flag in RFC 7794 and RFC 7684 section 2.1).  So looks that Anycast flag is missing there.
So my question  is still the same -  how can we (besides topology learning tricks) explicitly distinguish it from Node SID without Anycast flag?
Thank you.

SY,Boris
   

 On Thursday, July 22, 2021, 11:44:05 AM GMT+3, Ketan Talaulikar (ketant) <ketant=40cisco.com@dmarc.ietf.org> wrote:  
 
 
Hi Boris,
 
  
 
Using your original email to respond instead of top-posting so I do not miss anything in your original query. This builds on top of the responses from Robert and Jeff with some more details.
 
  
 
Please check inline below.
 
  
 
From: Idr <idr-bounces@ietf.org>On Behalf Of Boris Hassanov
Sent: 21 July 2021 15:25
To: IDR List <idr@ietf.org>
Subject: [Idr] Few questions about Segment Routing extensions for BGP LS (draft-ietf-idr-bgp-ls-segment-routing-ext)
 
  
 
Hi all,
 
  
 
1) Need an advice, I might be missing something but I see that Anycasi SID (3333 in the example below)  is in BGP-LS update as regular Prefix SID TLV:
  Path Attribute - BGP-LS Attribute             Flags: 0x80, Optional, Non-transitive, Complete                 1... .... = Optional: Set                 .0.. .... = Transitive: Not set                 ..0. .... = Partial: Not set                 ...0 .... = Extended-Length: Not set                 .... 0000 = Unused: 0x0             Type Code: BGP-LS Attribute (29)             Length: 12             Link State                 Prefix SID TLV                     Type: 1158                     Length: 8                     Flags: 0x40, Node-SID (N)                         0... .... = Re-advertisement (R): Not set                         .1.. .... = Node-SID (N): Set                         ..0. .... = No-PHP (P): Not set                         ...0 .... = Explicit-Null (E): Not set                         .... 0... = Value (V): Not set                         .... .0.. = Local (L): Not set                     Algorithm: 0                     SID/Index: 3333 
  
 
Here is confusion, how, let's say, a controller, which receives such BGP-LS update, could  distinguish it from regular Prefix/Node SID?
 
[KT] Node SID or Anycast SID are sub-sets of the Prefix SID and therefore both are advertised using the Prefix SID TLV. The way to distinguish them would be based on the flags in the Prefix Attribute Flags TLVhttps://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-ls-segment-routing-ext-18#section-2.3.2. It carries the Node and Anycast flags. Note that the Anycast flag was introduced very recently. The indication of Node flag surely eliminates the Prefix being Anycast – this is by definition. Of course, a prefix’s association with the Node or Anycast flag will depend on the accuracy of the router configuration by the operator. In the case of anycast, this can be verified by the controller using the network-wide topology.
 
  
 
Unfortunately draft-ietf-idr-bgp-ls-segment-routing-ext-18 does not clarify this issue because it only describes Prefix SID TLV type 1158. Any suggestions?
 
  
 
2)  draft-ietf-idr-bgp-ls-segment-routing-ext-18 has two types of labels TLV: SID/Label TLV type 1161 and Prefix SID  TLV type 1158.  I checked several vendors implementations of BGP-LS, all of them use only Prefix SID TLV.
 
Why the draft does not have some conditions or clarifications when to use SID/Label TLV and when Prefix SID TLV?
 
[KT] The SID/Label TLV (1161) is used as a sub-TLV of SR Capabilities and SRLB TLVs as indicated herehttps://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-ls-segment-routing-ext-18#section-2.1.1. I am not sure why this would be mixed up with the Prefix SID TLV which is very different.
 
  
 
Thanks,
 
Ketan

  
 
  
 
Thank you.
 
  
 
SY,
 
Boris
 
  
    _______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr