Re: [Idr] SR-Capabilities TLV in draft-ietf-idr-bgp-ls-segment-routing-ext-01

"Ketan Talaulikar Talaulikar (ketant)" <ketant@cisco.com> Mon, 10 April 2017 15:25 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 0350F129537 for <idr@ietfa.amsl.com>; Mon, 10 Apr 2017 08:25:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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
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 XvLO3-k5HETy for <idr@ietfa.amsl.com>; Mon, 10 Apr 2017 08:25:47 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F48D129501 for <idr@ietf.org>; Mon, 10 Apr 2017 08:25:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13538; q=dns/txt; s=iport; t=1491837946; x=1493047546; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=N1Q0ve+mvod555gCl4bcQP1UmooBTkJBaQ/gI9osVsM=; b=Sq/ua4tXbOHNRs4kZPvBhxi4xS/iLdnHZNfmtazCte1PPOxn5Lt56NsX +o8DFlsYfkg4TmHoe2iWgaYd5HCLg7ZgTIJmjfKUxlP3nRLyPPGr5pbXj jd4O+IUMMrc9gNvUCW7h/yoh6oPMKmOFXSgbsW4yVmgYZHY8nXFsOSbKu s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BDAQAAo+tY/40NJK1dGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgm5lYYELB41ykUeQI4U0gg+GJAKDYD8YAQIBAQEBAQEBayiFFQEBAQE?= =?us-ascii?q?DLVwCAQgOAwQBASgHMhQJCAEBBAESCIoHqyuKYwEBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAR2GUIRwhQyFLwWcewGST5FKk38BHzg+R1sVhRwcgWN1iFKBDQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.37,182,1488844800"; d="scan'208,217";a="409124611"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 10 Apr 2017 15:25:46 +0000
Received: from XCH-ALN-009.cisco.com (xch-aln-009.cisco.com [173.36.7.19]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id v3AFPkYt013495 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 10 Apr 2017 15:25:46 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-ALN-009.cisco.com (173.36.7.19) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 10 Apr 2017 10:25:45 -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.1210.000; Mon, 10 Apr 2017 10:25:45 -0500
From: "Ketan Talaulikar Talaulikar (ketant)" <ketant@cisco.com>
To: Simon Zhong <szhong@juniper.net>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: SR-Capabilities TLV in draft-ietf-idr-bgp-ls-segment-routing-ext-01
Thread-Index: AdKxXgD4Cpf4ePb3QmGGH9sXHoVJLwAsG3Pw
Date: Mon, 10 Apr 2017 15:25:45 +0000
Message-ID: <33d6b2c1e8164ae6abd36010fce175bb@XCH-ALN-008.cisco.com>
References: <CY4PR05MB28860927E141274AFB83BB7ED30E0@CY4PR05MB2886.namprd05.prod.outlook.com>
In-Reply-To: <CY4PR05MB28860927E141274AFB83BB7ED30E0@CY4PR05MB2886.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.154.160.39]
Content-Type: multipart/alternative; boundary="_000_33d6b2c1e8164ae6abd36010fce175bbXCHALN008ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/jdsqQWlyL0RltF0HPo0M4nPU_FA>
Subject: Re: [Idr] SR-Capabilities TLV in draft-ietf-idr-bgp-ls-segment-routing-ext-01
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
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, 10 Apr 2017 15:25:49 -0000

Hi Simon,

The pair "Range Size + SID/Label sub-TLV" would be repeated if there are more than one SRGB/SRLB ranges advertised by a node.

Thanks,
Ketan

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Simon Zhong
Sent: 09 April 2017 11:21
To: idr@ietf.org
Subject: [Idr] SR-Capabilities TLV in draft-ietf-idr-bgp-ls-segment-routing-ext-01

Hi,

I'm working on Wireshark bgp dissector and following description confuses me.

2.1.1.  SR-Capabilities TLV

   The SR Capabilities sub-TLV has following format:
......
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  Range Size                   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   //                SID/Label Sub-TLV (variable)                 //
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

This implies that there's one "Range Size" and one or more "SID/Lable Sub-TLV), however later in this section, it says:

     One or more entries, each of which have the following format:

         Range Size: 3 octet value indicating the number of labels in
         the range.

         SID/Label sub-TLV (as defined in Section 2.3.7.2).

Which sounds like one or more "Range Size" + "SID/Lable sub-TLV" combo are allowed.

The same applies to SR Local Block TLV as well.

So what's the intended behaviour? Thanks.

/Simon