IETF Logo Mail Archive

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

Rajesh M <mrajesh@juniper.net> Mon, 03 September 2018 05:05 UTC

Return-Path: <mrajesh@juniper.net>
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 5612D130DD5 for <idr@ietfa.amsl.com>; Sun, 2 Sep 2018 22:05:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Level:
X-Spam-Status: No, score=-2.71 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_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 kq7RtsPvc6tz for <idr@ietfa.amsl.com>; Sun, 2 Sep 2018 22:05:29 -0700 (PDT)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80D5D130DC8 for <Idr@ietf.org>; Sun, 2 Sep 2018 22:05:29 -0700 (PDT)
Received: from pps.filterd (m0108156.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w834x7kD030617; Sun, 2 Sep 2018 22:05:27 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=tNeeUCzmLwpgiiwccw+MtcIW+qV5XUKdpOl8HYI1TY0=; b=x0vCSfmBsXgjr6t0PnhtfsSpBtl2LKApkPu56C5oFp4/RKwLKccs9EZiW7MTXcWOXl5o m86EW/jI0UUhH9Oterg7LCOQB+hJl/SAxM5dP0TvlqFho0AP5AWfgaYuRlEBI/BWDK+B XIPgt1i/t2D/QQf1KP/OPZDYnS0sCEezbMwyzlc44hLxmtxZS/Fvh3DODuHK9hjhj1IU Zr24X7zRKN97N+Xc/jC3aojkrjyQH6HJrQxaf2k7Wtfh7rdGpcMFsx6wTlVMhXfxi5EN 4j1WBtrXDSyB2YISIuXTuMjtg3QlR+WHTG2oTFjmNiDbIBQRb8ku8sfYrMaOsBgiWOlW Wg==
Received: from nam03-by2-obe.outbound.protection.outlook.com (mail-by2nam03lp0055.outbound.protection.outlook.com [216.32.180.55]) by mx0a-00273201.pphosted.com with ESMTP id 2m7ssnhyx8-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sun, 02 Sep 2018 22:05:27 -0700
Received: from CY1PR0501MB1257.namprd05.prod.outlook.com (10.160.225.156) by CY1PR0501MB1609.namprd05.prod.outlook.com (10.161.162.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1122.11; Mon, 3 Sep 2018 05:05:24 +0000
Received: from CY1PR0501MB1257.namprd05.prod.outlook.com ([fe80::70dd:daca:755b:bf36]) by CY1PR0501MB1257.namprd05.prod.outlook.com ([fe80::70dd:daca:755b:bf36%3]) with mapi id 15.20.1122.009; Mon, 3 Sep 2018 05:05:23 +0000
From: Rajesh M <mrajesh@juniper.net>
To: "Ketan Talaulikar (ketant)" <ketant@cisco.com>, "Idr@ietf.org" <Idr@ietf.org>
CC: Shraddha Hegde <shraddha@juniper.net>, Ram Santhanakrishnan <ramsk@juniper.net>, Balaji Rajagopalan <balajir@juniper.net>
Thread-Topic: draft-ietf-idr-bgp-ls-segment-routing-ext-08 ( BGP Link-State extensions for Segment Routing )
Thread-Index: AdQ/ZOjvqmWDxbGYSbWH0hgd2FdRNABZ0uQwAAiPZqAAApUB0ACR94JA
Date: Mon, 03 Sep 2018 05:05:22 +0000
Message-ID: <CY1PR0501MB125784FE0D78FE2090C76CCFBE0C0@CY1PR0501MB1257.namprd05.prod.outlook.com>
References: <BN3PR0501MB125186FB87889FCC0005E19BBE090@BN3PR0501MB1251.namprd05.prod.outlook.com> <1b8c5b39e54e4cdc8c4237dc2167f2e0@XCH-ALN-008.cisco.com> <BN3PR0501MB1251EDECC0D1AA439AF0AA11BE0F0@BN3PR0501MB1251.namprd05.prod.outlook.com> <35adb6bae30a4ea88decef19ee51c6c9@XCH-ALN-008.cisco.com>
In-Reply-To: <35adb6bae30a4ea88decef19ee51c6c9@XCH-ALN-008.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 11.0.400.15
dlp-reaction: no-action
x-originating-ip: [116.197.184.12]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY1PR0501MB1609; 6:4R3veAgeSlnC5FvkxZEjaNbwHb2rzLHIdXu5yRngzcKGGntj91tb8Jy2vZSAe6QJR7DLhUSLbTwMqRELbq3l7JaYRBaUbAWKptlmC9B9u8GeJ7BRWHJvnjNNGLAfpxiBYzvCnnIG5UCu90sVur/AhDW8lyEXgqcQc25Hz+V2UrdvpBTmy3sP/2OVSteTky064Aqjg133wlym5vaH+xd8dB2vbew3uJej0sh0sTYl2a6BIyjZJ3Kd7A1yrKRP/hqsEGH4Jvl9tYmY03EoCjIuSLdIYfmDED9mfU/qxLKOlLGb7merk4kM5dKqVO+uEnJ/r+LSLnTsDBsdopyEH5t8rplZIhrnlJ7XGyNcC1z9dpNwRq+wWUBZWz8BFDtxTZeuln4gpDCy4ONsy3pSBdp+gy7rERTg9CSX9O3IREAjBUZMPs51K9Q6PU6IH6NZchXspsrE/HVMG1ZeRzDcfe/C/A==; 5:HLyaY8L601MkNnb5NQUWPVuCVHGB0uHqC2d/Ep7/juulUYnpWIrppXlsGpjcLenmzX/92+PqXjDD11Tgqo/XJXvql5gSbp+pDGGxnSWRaHK1p8aj8XmzT2jCEq3Q8vO4kM9CUFFhbI+yFN82Ts9Kffv6NT3tIXoNAm51yY/7K/s=; 7:wlpKyOuDNTZghr2pp2ihFXfIznjvs7eKMCWmESOYfO5kg/GHGThvSZifLCsgFmH9gZWkJPZQGyKd67GEocjtBi7IX5+JtgAaX5mkPeiB9HD1S0Vm3Eoe/cPdrrJqsEJoWMm9uiGZ39g/nyoQTvaM+aev9rmq/XfUHZu2OUBHx/MjEZKwRNZ6Ta81s1XUq8QvDD3oVS6rpPh6BTK0Q9lBt7B0MMOsrFRSpPPwTKZQyqE4W+dVJr8vuWl+nXCi1Eg2
x-ms-exchange-antispam-srfa-diagnostics: SOS;SOR;
x-forefront-antispam-report: SFV:SKI; SCL:-1; SFV:NSPM; SFS:(10019020)(366004)(39860400002)(396003)(346002)(376002)(136003)(199004)(189003)(53936002)(25786009)(107886003)(5660300001)(55016002)(6436002)(54896002)(6306002)(5250100002)(486006)(9686003)(236005)(4326008)(229853002)(14444005)(2501003)(2900100001)(256004)(74316002)(26005)(11346002)(476003)(446003)(93886005)(186003)(6246003)(81156014)(105586002)(8676002)(106356001)(81166006)(33656002)(86362001)(2906002)(54906003)(97736004)(6116002)(790700001)(110136005)(102836004)(14454004)(478600001)(68736007)(7696005)(76176011)(7736002)(316002)(99286004)(66066001)(53546011)(8936002)(3846002)(6506007); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0501MB1609; H:CY1PR0501MB1257.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
x-ms-office365-filtering-correlation-id: 1e503a06-1357-4830-f0e9-08d6115ada9c
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989137)(5600074)(711020)(4618075)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(2017052603328)(7153060)(7193020); SRVR:CY1PR0501MB1609;
x-ms-traffictypediagnostic: CY1PR0501MB1609:
x-microsoft-antispam-prvs: <CY1PR0501MB1609F1C44D7BFB1804CC6364BE0C0@CY1PR0501MB1609.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(138986009662008)(95692535739014)(21748063052155);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(10201501046)(93006095)(93001095)(3231311)(944501410)(52105095)(3002001)(6055026)(149027)(150027)(6041310)(20161123558120)(20161123562045)(20161123564045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(201708071742011)(7699016); SRVR:CY1PR0501MB1609; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0501MB1609;
x-forefront-prvs: 0784C803FD
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 00alCIuVVFan4XSdvxWBnIDTYsxopXT9e4I5JKaRTxHy1J4x/peI5ysiYrRgQwidtr39PRNSlFsCexwE3kQubngsDg2ey3Tckl4LcDuBtU2VeOdKep19AgNF3nml9qqgSHoPGrR1aAt605+J1W4LI4Wt+1VXe/CbhYe1Z/Zmk5NAUVBIfL2AZpcVT3rueHmw6nEfpqtUq8PNrzhkFtHjJjzjIxqUzwzOacNQfAwhdDXXdlUIVHnNvf5OMfqZgnUx49W9HvClnuBOBeg0K2raJsVIfnQW2DNHsgh2oM4WPMZ+bMbyH+Hsx1eTUH7Nwwkl0MCb3nfcy7GOH7JrQD9nFne7NRGxUtuFch2kmr9pp4s=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_CY1PR0501MB125784FE0D78FE2090C76CCFBE0C0CY1PR0501MB1257_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 1e503a06-1357-4830-f0e9-08d6115ada9c
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Sep 2018 05:05:23.0429 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0501MB1609
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-09-03_03:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1809030055
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/RmS-kr14bs9Tttc8uQl2IH19jRA>
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: Mon, 03 Sep 2018 05:05:32 -0000

Please find the response inline.

From: Ketan Talaulikar (ketant) <ketant@cisco.com>
Sent: Friday, August 31, 2018 1:21 PM
To: Rajesh M <mrajesh@juniper.net>; Idr@ietf.org
Cc: Shraddha Hegde <shraddha@juniper.net>; Ram Santhanakrishnan <ramsk@juniper.net>; Balaji Rajagopalan <balajir@juniper.net>
Subject: RE: draft-ietf-idr-bgp-ls-segment-routing-ext-08 ( BGP Link-State extensions for Segment Routing )

Hi Rajesh,

There is also a problem with your suggestion.

The moment we add protocol to the attribute it can no longer be shared between NLRIs across protocols in any case. So I don't see how it helps in the BGP packing.

I agree with you, we cannot share attributes across OSPF/ISIS.
My suggestion is to add protocol tlv as optional attribute for Node/Link/Prefix attributes. So that backward compatibility is not an issue.


There are several implementations of this draft which are shipping and deployed. So changing encodings in a manner that is not backward compatible is a challenge at this stage.

Thanks,
Ketan

From: Rajesh M <mrajesh@juniper.net<mailto:mrajesh@juniper.net>>
Sent: 31 August 2018 11:22
To: Ketan Talaulikar (ketant) <ketant@cisco.com<mailto:ketant@cisco.com>>; Idr@ietf.org<mailto:Idr@ietf.org>
Cc: Shraddha Hegde <shraddha@juniper.net<mailto:shraddha@juniper.net>>; Ram Santhanakrishnan <ramsk@juniper.net<mailto:ramsk@juniper.net>>; Balaji Rajagopalan <balajir@juniper.net<mailto:balajir@juniper.net>>
Subject: RE: draft-ietf-idr-bgp-ls-segment-routing-ext-08 ( BGP Link-State extensions for Segment Routing )

Hi Ketan,

Attributes might end Up same even across protocol (OSPF/ISIS). It's not good to make that Assumption.
our suggestion is to : Mandatory add protocol as part of the Node/Link/Prefix attributes to ensure the same.

Thanks
Rajesh

From: Ketan Talaulikar (ketant) <ketant@cisco.com<mailto:ketant@cisco.com>>
Sent: Friday, August 31, 2018 7:18 AM
To: Rajesh M <mrajesh@juniper.net<mailto:mrajesh@juniper.net>>; Idr@ietf.org<mailto:Idr@ietf.org>
Cc: Shraddha Hegde <shraddha@juniper.net<mailto:shraddha@juniper.net>>
Subject: RE: draft-ietf-idr-bgp-ls-segment-routing-ext-08 ( BGP Link-State extensions for Segment Routing )

Hi Rajesh,

Please check inline below.

From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> On Behalf Of Rajesh M
Sent: 29 August 2018 12:32
To: Idr@ietf.org<mailto:Idr@ietf.org>
Cc: Shraddha Hegde <shraddha@juniper.net<mailto: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

v2.23.0 | Report a Bug | By Email