Re: [Idr] draft-ietf-idr-bgp-ls-segment-routing-ext-08 ( BGP Link-State extensions for Segment Routing )

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Fri, 31 August 2018 01:48 UTC

Return-Path: <ketant@cisco.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 4310C130DFC for <idr@ietfa.amsl.com>; Thu, 30 Aug 2018 18:48:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 EDd6UYJs0JLP for <idr@ietfa.amsl.com>; Thu, 30 Aug 2018 18:48:30 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 271C3130DF4 for <Idr@ietf.org>; Thu, 30 Aug 2018 18:48:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8976; q=dns/txt; s=iport; t=1535680110; x=1536889710; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=ZuwPeN1WfpwPhEjuvaDHMUFoVefYpxmsvkDBLMltqxc=; b=BMQ99PXNUMmmBiToKFhYucfQdnyUMJ5CQKaxs00vmctK2oRcoPYgbCNi yj06ERPzgCN+Stkaq9Whfk8DtzVTAsFy5u1E7ToFAEz2V9BaGNW+RJzgY iIrvRy13zjZmiGaJpUsXK8rrjtqJdBUdflrP1odSoJkWauugNFeyYjrJu k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CaAACmnYhb/4ENJK1aGQEBAQEBAQEBAQEBAQcBAQEBAYJXeGV/KAqLeY44kHaFM4F6C4RsAoMjITQYAQIBAQIBAQJtKIU3AQEBAQMtTBACAQgRBAEBLzIdCAEBBAENBQiDGoEdZKQqigKKEReBQT+BEoMSilYCjROFVIhWCQKPax+BP4Q0h0OBHIg6ingCERSBJB04gVJwFYMkgiUXEY4Gb4wQgRwBAQ
X-IronPort-AV: E=Sophos;i="5.53,309,1531785600"; d="scan'208,217";a="443745428"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 31 Aug 2018 01:48:29 +0000
Received: from XCH-ALN-007.cisco.com (xch-aln-007.cisco.com [173.36.7.17]) by alln-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id w7V1mTcG029960 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 31 Aug 2018 01:48:29 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-ALN-007.cisco.com (173.36.7.17) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Thu, 30 Aug 2018 20:48:28 -0500
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1367.000; Thu, 30 Aug 2018 20:48:28 -0500
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: Rajesh M <mrajesh@juniper.net>, "Idr@ietf.org" <Idr@ietf.org>
CC: Shraddha Hegde <shraddha@juniper.net>
Thread-Topic: draft-ietf-idr-bgp-ls-segment-routing-ext-08 ( BGP Link-State extensions for Segment Routing )
Thread-Index: AdQ/ZOjvqmWDxbGYSbWH0hgd2FdRNABZ0uQw
Date: Fri, 31 Aug 2018 01:48:28 +0000
Message-ID: <1b8c5b39e54e4cdc8c4237dc2167f2e0@XCH-ALN-008.cisco.com>
References: <BN3PR0501MB125186FB87889FCC0005E19BBE090@BN3PR0501MB1251.namprd05.prod.outlook.com>
In-Reply-To: <BN3PR0501MB125186FB87889FCC0005E19BBE090@BN3PR0501MB1251.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.69.238]
Content-Type: multipart/alternative; boundary="_000_1b8c5b39e54e4cdc8c4237dc2167f2e0XCHALN008ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.17, xch-aln-007.cisco.com
X-Outbound-Node: alln-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/6Benv4GEcp4-aFe_ZNr98O3uRvo>
Subject: Re: [Idr] draft-ietf-idr-bgp-ls-segment-routing-ext-08 ( BGP Link-State extensions for Segment Routing )
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.27
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, 31 Aug 2018 01:48:32 -0000

Hi Rajesh,

Please check inline below.

From: Idr <idr-bounces@ietf.org> On Behalf Of Rajesh M
Sent: 29 August 2018 12:32
To: Idr@ietf.org
Cc: Shraddha Hegde <shraddha@juniper.net>
Subject: [Idr] draft-ietf-idr-bgp-ls-segment-routing-ext-08 ( BGP Link-State extensions for Segment Routing )

About section 2.2.1 (Adjacency SID TLV) section 2.2.2 (LAN Adjacency SID TLV):
Here Flags field is specific to OSPF and ISIS. Until we know the protocol we will not be able to decode the received Flags.
[KT] Ack

About section 2.3.1 (Prefix-SID TLV) :
Here Flags field is specific to OSPF and ISIS. Until we know the protocol we will not be able to decode the received Flags.
[KT] Ack

Our understanding is
Protocol cannot be got from Node NLRI Format, Link NLRI Format, Prefix NLRI Format since multiple NLRIs can share same set of BGP-LS attribute.
[KT] This is about packing of BGP-LS updates. Since each BGP-LS NLRI has a unique set of attributes, it is not possible to pack multiple NLRIs in the same update. Doing this for NLRIs across protocol is even harder. The update messages end up being a single NLRI and its attributes. Would you agree? And as an extension we know the protocol when decoding the flags.

Thanks,
Ketan