Re: [Idr] [spring] questions about draft-ietf-idr-bgpls-srv6-ext-03

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Wed, 09 September 2020 09:05 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 0D1123A116C; Wed, 9 Sep 2020 02:05:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.597
X-Spam-Level:
X-Spam-Status: No, score=-9.597 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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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 header.b=goabzK+C; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=m+X1rTLG
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 c09cUYt-6TQ2; Wed, 9 Sep 2020 02:05:18 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E76FA3A1141; Wed, 9 Sep 2020 02:05:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=56600; q=dns/txt; s=iport; t=1599642317; x=1600851917; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Idh7JBVv+0bKi8L/ooFCdfsRCxwg4k/O88sTea5moOI=; b=goabzK+Cq2OVGCG6C+iRS0jdyyQ4/MpoUHP3XMxgXTIamv5PM4gA3sJX 7XB+GcHK37HNfecJQNCHg01eTCIR4BPMjMe8+OGiGzMXVUCyJg+nqO5SL 9SYLMATir+p1VOyItqP/zB4Yf9iS8eBYQNuHxc+62p689/BNV3ONUhao4 0=;
IronPort-PHdr: =?us-ascii?q?9a23=3AB60knRDx8H2+KlWLt9zVUyQJPHJ1sqjoPgMT9p?= =?us-ascii?q?ssgq5PdaLm5Zn5IUjD/qw00g3JQIzE5vMCgO3T4OjsWm0FtJCGtn1KMJlBTA?= =?us-ascii?q?QMhshemQs8SNWEBkv2IL+PDWQ6Ec1OWUUj8yS9Nk5YS8bjbkLfozu56jtBUh?= =?us-ascii?q?n6PBB+c+LyHIOahs+r1ue0rpvUZQgAhDe0bb5oahusqgCEvcgNiowkIaE0mR?= =?us-ascii?q?Y=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CmBQBCmlhf/49dJa1fHAEBAQEBAQc?= =?us-ascii?q?BARIBAQQEAQGCD4EjL1EHcFkvLAqELoNGA41xmHGCUwNQBQsBAQEMAQEYAQo?= =?us-ascii?q?KAgQBAYQHRAIXgXoCJDgTAgMBAQsBAQUBAQECAQYEbYVcDIVyAQEBAQMBARA?= =?us-ascii?q?RChMBASUHCwEPAgEGAhEEAQEhAQYDAgICJQsUBgMIAgQBDQUIGoMFgX5NAy0?= =?us-ascii?q?BAQ6WRpBpAoE5iGF2gTKDAQEBBYUSGIIQAwaBOIJxg2iCJYQsG4FBP4EQAQF?= =?us-ascii?q?Cgk0+glwBAQKBXyQHCYJhM4ItkxuGaottjwaBdgqCZZpTgwmJb5E0giqEPI4?= =?us-ascii?q?VgW2dagIEAgQFAg4BAQWBayOBV3AVO4JpUBcCDY4fDBeDToUUhUJ0AjUCBgE?= =?us-ascii?q?JAQEDCQF7jDYBgRABAQ?=
X-IronPort-AV: E=Sophos;i="5.76,409,1592870400"; d="scan'208,217";a="553152017"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 09 Sep 2020 09:05:16 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by rcdn-core-7.cisco.com (8.15.2/8.15.2) with ESMTPS id 08995G6N013183 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 9 Sep 2020 09:05:16 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 9 Sep 2020 04:05:16 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 9 Sep 2020 05:05:15 -0400
Received: from NAM11-CO1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Wed, 9 Sep 2020 04:05:15 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=EgnI/kl4UNily7PR5YIlQjOq3RwJteo8l92mEF74zbiBKhzHdyoDEbAdbQ7yVRTfH9yy5DFk95sCFENG+KGzZXkdYKV+WJfEmuJJkUuhfVry9ooeB+9jOA3HNrbsl7wRwAbA8XRMT5vCcS2xVShRfSD5S+HPdQSgTTVqawbkjiDsMPRhpIzOFENeEnRYimJPHl5QHIA/R36zbRAfrtfrn2/XGsBfNVgu1d6rcZhh4HJv96O6An6nGfZwZPCn8TH8Aq4/zSL/b+U0wbiAHleTH0KnGe0xvwI6eHGDGzqSpVQbCP3al1f8eO04JeAhC5uyKYq2DyU0uoThCUUpxsb1FA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Idh7JBVv+0bKi8L/ooFCdfsRCxwg4k/O88sTea5moOI=; b=a/VnGRieOYJ3WgcvrHajeJ3ZycWoOdMDYWOm40NojKtHJobEv92Y2eVElCJYYK+Vof/27VLY2t83bYoExFom5TyNUlUp0dlkrdQ7uswZgGeqEeS1apj93KZpbN56+nbTJpPQTy6uOsvZ90GwcnxhzlsWGsmANfG9n2uuyxBo/40oEz8+TCmaGYO/Nb7yuz1aVRZErFoH3W6aOptcSaSsdp97aMiWeuPU1MVFP9KWukwKqy3rn0AaD70+RIii4Lyxz6LRRVp0bf4E5WKVAL/nAk9pgsgp7fIdwGyDCqqS1gcZFhszND+u7HIkPRXQGwHxp5LfAMpBNqZCXCwKbxGkUg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Idh7JBVv+0bKi8L/ooFCdfsRCxwg4k/O88sTea5moOI=; b=m+X1rTLG3Vi/jAefKmTjqIhl9Cwf5/EXB0DSPRKF9nMHCu9ThLODspOcLVb/bA20oNHYBHxW97vhGsAXlpattanVk0/r8S7HhahvmF8DXzyl7oYt/a09NOZXP3IcRL4v6Y6F2rWCZddoc1On4mrbRnyXpW9s9+Lz0IVlL130By8=
Received: from MW3PR11MB4570.namprd11.prod.outlook.com (2603:10b6:303:5f::22) by MWHPR1101MB2365.namprd11.prod.outlook.com (2603:10b6:300:74::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3348.15; Wed, 9 Sep 2020 09:05:14 +0000
Received: from MW3PR11MB4570.namprd11.prod.outlook.com ([fe80::3c42:544a:c4b2:6135]) by MW3PR11MB4570.namprd11.prod.outlook.com ([fe80::3c42:544a:c4b2:6135%8]) with mapi id 15.20.3370.016; Wed, 9 Sep 2020 09:05:14 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: "Chengli (Cheng Li)" <c.l@huawei.com>, "peng.shaofu@zte.com.cn" <peng.shaofu@zte.com.cn>
CC: "idr@ietf.org" <idr@ietf.org>, "spring@ietf.org" <spring@ietf.org>
Thread-Topic: =?utf-8?B?UmU6W3NwcmluZ10gW0lkcl0gcXVlc3Rpb25zIGFib3V0wqBkcmFmdC1pZXRm?= =?utf-8?Q?-idr-bgpls-srv6-ext-03?=
Thread-Index: AQHWhMTXLmVo5HhHe0mfR/F38QwRaKlckpCAgANQr1CAAAiUgIAAANeAgAAaLBA=
Date: Wed, 9 Sep 2020 09:05:13 +0000
Message-ID: <MW3PR11MB457088E2E9641868E0ECE6FEC1260@MW3PR11MB4570.namprd11.prod.outlook.com>
References: 202009071112556199243@zte.com.cn, MW3PR11MB457048FF3673B4D737681C17C1260@MW3PR11MB4570.namprd11.prod.outlook.com <202009091527334241499@zte.com.cn> <C7C2E1C43D652C4E9E49FE7517C236CB02BC4967@dggeml529-mbx.china.huawei.com>
In-Reply-To: <C7C2E1C43D652C4E9E49FE7517C236CB02BC4967@dggeml529-mbx.china.huawei.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: huawei.com; dkim=none (message not signed) header.d=none;huawei.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [49.36.37.20]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b578e107-4259-443f-ee97-08d8549f76b5
x-ms-traffictypediagnostic: MWHPR1101MB2365:
x-microsoft-antispam-prvs: <MWHPR1101MB23655AC7A5D3022C9F562AD0C1260@MWHPR1101MB2365.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: /6IEYBVArilddx32nGyX3tbHir2Lja1zjTMLy9jPUEj0sGRFDFsECx/5lk2AHuaDnHRONWNKieKrpIVJ/RuaFglT57fxAXdvUIe3Q5fV1CxDhvAha1i/W1kfrbH9wL6GP7gaDhqYPs2XW8nCYcug3HYcwAsRpXS/Q2d1xvFfA6xThRzhFq3tmp+HV0NcXbkct37ur4+JILcnhDnBPDwAXDdETs9eRtwyTo6v2qY9fHGVSeR3RgagDqJjXpL94c8P7o6BWxBGSHKmnVjGj7rUfPgBTcv/hsJ+E+dNRYMX7JxkU195m0X60wrWS04vzTrOTpI4UiRLODh1GDj9BrDEF3zbVIHzQlEafKaLzPROp/ymA+9GsMDamrOPudSm6wZKl1wU6hJxR8deZ5bBtwarSQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MW3PR11MB4570.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(396003)(366004)(376002)(346002)(39850400004)(136003)(66446008)(86362001)(64756008)(478600001)(66946007)(66556008)(76116006)(52536014)(66476007)(966005)(6506007)(53546011)(166002)(83380400001)(71200400001)(110136005)(2906002)(5660300002)(26005)(316002)(54906003)(4326008)(55016002)(33656002)(9686003)(7696005)(8936002)(186003); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: NBgkUV8krgv9W5jKvIcIBVOkmZTVwlK0fqr0A8MwFCjrVud7hkdl5pgbaq5HronYwM4xrACXl9gajHR6CxMrizzCoyGHzWe/4M1LAd82k+/uP7OJFkJBG4i11O7yrnq2opgwRdbU30353VHskUwboL4mLAZY8ztyRIXtXtISvd/eacnXWxd/4Jovewt9l0vQqbjkmN4ZiXciB2f/Y7p3+/DWB87unjvlXflDN9hcW7isZ6nay2aCIoe+NoiYTnWP0Jscfv29sPzGHveYBHnZK0HoRgki/+oWjURSwhBv2JOHSf7u2hs6MMspIFqNesE6lCY0DYsCW2lL5A8mi5UIBrU5nX9Us8JaP6+TecER1uehfPD7Hu6YTMr3SvGAlWhLNkql4hLdk521pL8VsWKi2+8qezcxHkcNUF5GsGHOFx4NU++K+UziIqknvA7qrJ2u3LnBfc32rqQ0E1rLCSx1ef41fMHuyKRb1AUFA9fe+mCbOhjJDK+3hkg1CzoUHEVSDnlfPd1dv0hHuBNXsKd7nllmjRGevRoEWUz1QY6yW1Mtj8pyp8XUjT0+hDPVLs8dZNXqdr0oyTj/o/jfKQw19fSg9utbQQEui56k3IIyRlVlqn7/HsmLW/5EaH5iVjwpKgvDukqk6LvwhMMfVHDPSg==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MW3PR11MB457088E2E9641868E0ECE6FEC1260MW3PR11MB4570namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MW3PR11MB4570.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: b578e107-4259-443f-ee97-08d8549f76b5
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Sep 2020 09:05:13.9619 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Sd4jkoynEw0diEVfdameoAK4GhDbwNMxpJGxSQOsSB4jAQ7kkw2xtGygP6C5hVJXkwyMLAmbPVoQBJhBzr83tQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR1101MB2365
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.12, xch-aln-002.cisco.com
X-Outbound-Node: rcdn-core-7.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/dFJsBtGPIoSJUIB8jotMg9ETq14>
Subject: Re: [Idr] =?utf-8?q?=5Bspring=5D__questions_about=C2=A0draft-ietf-id?= =?utf-8?q?r-bgpls-srv6-ext-03?=
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: Wed, 09 Sep 2020 09:05:21 -0000

Sure. We can make this editorial change on the next update.

Thanks,
Ketan

From: Chengli (Cheng Li) <c.l@huawei.com>
Sent: 09 September 2020 13:01
To: peng.shaofu@zte.com.cn; Ketan Talaulikar (ketant) <ketant@cisco.com>
Cc: idr@ietf.org; spring@ietf.org
Subject: RE: Re:[spring] [Idr] questions about draft-ietf-idr-bgpls-srv6-ext-03

Hi Ketan and PSF,

Yes, I mean it may be better to add a new section to describe the SRv6 SID structure TLV, like section 8, instead of 7.3.

Thanks,
Cheng



From: peng.shaofu@zte.com.cn<mailto:peng.shaofu@zte.com.cn> [mailto:peng.shaofu@zte.com.cn]
Sent: Wednesday, September 9, 2020 3:28 PM
To: ketant=40cisco.com@dmarc.ietf.org<mailto:ketant=40cisco.com@dmarc.ietf.org>
Cc: Chengli (Cheng Li) <c.l@huawei.com<mailto:c.l@huawei.com>>; idr@ietf.org<mailto:idr@ietf.org>; spring@ietf.org<mailto:spring@ietf.org>
Subject: Re:[spring] [Idr] questions about draft-ietf-idr-bgpls-srv6-ext-03




Hi Ketan, Cheng,



Thanks for your reply.

I have get clear answer to my questions.

The third question is meaningless once the typo is corrected.



I also suggest that "structure TLV" can not be palced under section 7, as Cheng suggested.



Regards,

PSF




原始邮件
发件人:KetanTalaulikar(ketant) <ketant=40cisco.com@dmarc.ietf.org<mailto:ketant=40cisco.com@dmarc.ietf.org>>
收件人:Chengli (Cheng Li) <c.l@huawei.com<mailto:c.l@huawei.com>>;彭少富10053815;
抄送人:idr@ietf.org<mailto:idr@ietf.org> <idr@ietf.org<mailto:idr@ietf.org>>;spring@ietf.org <spring@ietf.org<mailto:spring@ietf.org>>;
日 期 :2020年09月09日 15:07
主 题 :Re: [spring] [Idr] questions about draft-ietf-idr-bgpls-srv6-ext-03
_______________________________________________
spring mailing list
spring@ietf.org<mailto:spring@ietf.org>
https://www.ietf.org/mailman/listinfo/spring
Hi PSF and Cheng,

Please check inline below.

From: Chengli (Cheng Li) <c.l@huawei.com<mailto:c.l@huawei.com>>
Sent: 07 September 2020 09:49
To: peng.shaofu@zte.com.cn<mailto:peng.shaofu@zte.com.cn>; Ketan Talaulikar (ketant) <ketant@cisco.com<mailto:ketant@cisco.com>>
Cc: idr@ietf.org<mailto:idr@ietf.org>; spring@ietf.org<mailto:spring@ietf.org>
Subject: RE: [Idr] questions about draft-ietf-idr-bgpls-srv6-ext-03

Hi PSF and Ketan,

IMHO, the SRv6 SID Structure TLV can be included in the sub-TLV field of SRv6 END.X TLV, SRv6 LAN END.X TLV (for adj SIDs) and SRv6 SID NLRI(for node SIDs). So I guess it may be a typo, the SRv6 End should be SRv6 End.X.
[KT] You are correct. It should be End.X and not End. Will fix this typo in the next update.

 We can double check the IANA section.

But from the text in Section 7, SRv6 SID attributes,

   This section specifies the new TLVs to be carried in the BGP Link
   State Attribute associated with the BGP-LS SRv6 SID NLRI.

The sub-TLVs defined in this section are associated with the SRv6 SID NLRI, so these sub-TLVs are associated with node SIDs.
[KT] This is correct – they are SIDs associated with the node.

Regarding Adj SIDs, the information is included in the Link NLRI. If so, do we need to make a new upper level for SRv6 SID Structure sub-TLV? Because it is not only apply for node SIDs but also link/adj SIDs.
[KT] I do not understand what you mean by “new upper level for SRv6 SID Structure sub-TLV”? Sec 7.3 clearly says how it can be encoded

   It is an optional TLV
   for use in the BGP-LS Attribute for an SRv6 SID NLRI and as an
   optional sub-TLV of the SRv6 End.X, IS-IS SRv6 LAN End.X and OSPFv3
   SRv6 LAN End.X TLVs.
Regarding the second question.  I think,

  *   an Adj-SID is included in the Link NLRI, with an optional SID Structure TLV as a sub-TLV. SRv6 SID NLRI and attributes are not needed to be included.
[KT] Correct – we are talking about End.X and LAN End.X here.


  *   a Node SID is included in the SRv6 SID NLRI, with TLVs like SRv6 Endpoint Behavior TLV, SRv6 BGP Peer Node SID TLV, SRv6 SID Structure TLV in the SRv6 SID attributes to describe the information of the node SID.
[KT] Correct.


[KT] I did not understand the third question from PSF

Thanks,
Ketan

Respect,
Cheng




From: Idr [mailto:idr-bounces@ietf.org]On Behalf Of peng.shaofu@zte.com.cn<mailto:peng.shaofu@zte.com.cn>
Sent: Monday, September 7, 2020 11:13 AM
To: ketant@cisco.com<mailto:ketant@cisco.com>
Cc: idr@ietf.org<mailto:idr@ietf.org>; spring@ietf.org<mailto:spring@ietf.org>
Subject: [Idr] questions about draft-ietf-idr-bgpls-srv6-ext-03




Hi Ketan,



I have a question for section 7.3.  SRv6 SID Structure TLV, and hope to get your answer.

It described:

SRv6 SID Structure TLV is used to advertise the length of each

   individual part of the SRv6 SID as defined in

   [I-D.ietf-spring-srv6-network-programming].  It is an optional TLV

   for use in the BGP-LS Attribute for an SRv6 SID NLRI and as an

   optional sub-TLV of the SRv6 End, IS-IS SRv6 LAN End.X and OSPFv3

   SRv6 LAN End.X TLVs.  The TLV has the following format:



My question is:

1) Becasue section 7 mentions that "This section specifies the new TLVs to be carried in the BGP Link State Attribute associated with the BGP-LS SRv6 SID NLRI.",

    so, can "structure TLV" be also associated with BGP-LS Link NLRI ?

2) As the description, does it mean that an SRv6 SID NLRI can contain SRv6 SID Information TLV for END SID or LAN End.X SID, then "structure TLV" is also associated with BGP-LS Link NLRI ?

3) Why the description skip End.X SID ?



Regards,

PSF