Re: [Idr] Early allocation request for draft-ietf-idr-segment-routing-te-policy

"Gaurav Dawra (gdawra)" <gdawra@cisco.com> Sat, 07 October 2017 00:52 UTC

Return-Path: <gdawra@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 D9918133342 for <idr@ietfa.amsl.com>; Fri, 6 Oct 2017 17:52:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Level:
X-Spam-Status: No, score=-14.52 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_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 0QCoNPqd9Ebp for <idr@ietfa.amsl.com>; Fri, 6 Oct 2017 17:52:17 -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 58FCB13331E for <idr@ietf.org>; Fri, 6 Oct 2017 17:52:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=23562; q=dns/txt; s=iport; t=1507337537; x=1508547137; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=x673AoIUJ5N5ZqRDdzsPDmZaMUIIG9yt7nd/3Cy93+0=; b=XS3VXZdAdEB8FJUu+AKg3frgQ04Z8ltgN59WslDNfLTzNpX0VpLjClJv 1PvEkfc5hxBPeLUzNB1oIho2KlnE8IQEnUcIxGDdW1i3QbMQyWtVReI10 3TpPdSdN9wUCyfZ3xCYChgD1qswFJ0juELgkxglvZrmY8WXCbB4cI8KHK A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CgAACpJNhZ/4kNJK1cGQEBAQEBAQEBAQEBBwEBAQEBgm9uZG4nB4Nzih+PboF2eZU2ghIKJYUWAhqEBj8YAQIBAQEBAQEBayiFGAEBAQEDI1YQAgEIEQMBAigDAgICMBQJCAIEDgWJTGQQpTCCJyeLEQEBAQEBAQEBAQEBAQEBAQEBAQEBARgFgy2CAoFRgWorgkk1gSSEABaCXS+CMgWhMwKUY5MKlSwCERkBgTgBHziBDngVSRIBhQccgWd2AYgsgRABAQE
X-IronPort-AV: E=Sophos;i="5.42,486,1500940800"; d="scan'208,217";a="302791145"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 07 Oct 2017 00:52:15 +0000
Received: from XCH-RTP-006.cisco.com (xch-rtp-006.cisco.com [64.101.220.146]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v970qFp3014197 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 7 Oct 2017 00:52:15 GMT
Received: from xch-rtp-012.cisco.com (64.101.220.152) by XCH-RTP-006.cisco.com (64.101.220.146) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Fri, 6 Oct 2017 20:52:14 -0400
Received: from xch-rtp-012.cisco.com ([64.101.220.152]) by XCH-RTP-012.cisco.com ([64.101.220.152]) with mapi id 15.00.1320.000; Fri, 6 Oct 2017 20:52:14 -0400
From: "Gaurav Dawra (gdawra)" <gdawra@cisco.com>
To: "John G. Scudder" <jgs@juniper.net>
CC: "idr@ietf.org" <idr@ietf.org>, "shares@ndzh.com" <shares@ndzh.com>, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "Jose Liste (jliste)" <jliste@cisco.com>, "Arjun Sreekantiah (asreekan)" <asreekan@cisco.com>, "Dhanendra Jain (dhjain)" <dhjain@cisco.com>
Thread-Topic: [Idr] Early allocation request for draft-ietf-idr-segment-routing-te-policy
Thread-Index: AQHTPwaEPuzOyPOTY0+MI0YZZ0Zy+Q==
Date: Sat, 07 Oct 2017 00:52:14 +0000
Message-ID: <67BCDF33-607F-420D-9BAB-51089FE69C55@cisco.com>
References: <D52C5D5F-3161-450E-A9E8-F03BBA46DD9E@juniper.net> <5021b09f13dd48468385583e31b0dd3e@XCH-ALN-001.cisco.com> <A57ADB73-A265-4300-AC6F-DDBEE7FFE7D0@juniper.net> <39C033F2-AE72-4FAE-BA6E-6586F3F0AE0B@cisco.com> <4B981052-C09C-4122-B320-9F4EA8A3589F@juniper.net>
In-Reply-To: <4B981052-C09C-4122-B320-9F4EA8A3589F@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.25.0.170815
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.154.160.246]
Content-Type: multipart/alternative; boundary="_000_67BCDF33607F420D9BAB51089FE69C55ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/E38f5_XfkIVIgkMLGEBzF3AsVng>
Subject: Re: [Idr] Early allocation request for draft-ietf-idr-segment-routing-te-policy
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: Sat, 07 Oct 2017 00:52:20 -0000

Hey John,

Understood. Thanks for clarification. Just wanted to indicate we support allocating the code points (whatever value they may be) as soon as possible.

Thanks again for considering our request.

Cheers,

Gaurav

From: "John G. Scudder" <jgs@juniper.net>
Date: Friday, October 6, 2017 at 1:31 PM
To: Gaurav Dawra <gdawra@cisco.com>
Cc: "idr@ietf.org" <idr@ietf.org>, "shares@ndzh.com" <shares@ndzh.com>, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "Jose Liste (jliste)" <jliste@cisco.com>, "Arjun Sreekantiah (asreekan)" <asreekan@cisco.com>, "Dhanendra Jain (dhjain)" <dhjain@cisco.com>
Subject: Re: [Idr] Early allocation request for draft-ietf-idr-segment-routing-te-policy

Hi Gaurav,

This thread is exactly to discuss the proposed early allocation for those sub-TLVs. However I'm a little confused (or perhaps concerned) by your note, since you list explicit values that aren't available. As you can see if you consult the IANA registry (https://www.iana.org/assignments/bgp-parameters/bgp-parameters.xhtml#tunnel-sub-tlvs) both 6 and 7 have already been allocated. 128 is currently unallocated and I see no reason that preference couldn't be satisfied, but I don't think the requests for 6 and 7 can be.

I would anticipate IANA would allocate the first two unused values for Preference and Binding SID.

As for when it will be done, the discussion period will close this coming Tuesday, October 10. Assuming no blocking objections are raised, I'll forward the request to the AD and IANA. They've usually been able to process such requests within a few days, so it's possible the values will be allocated before end of next week. Of course I'll keep the list posted about progress.

--John

On Oct 6, 2017, at 4:17 PM, Gaurav Dawra (gdawra) <gdawra@cisco.com<mailto:gdawra@cisco.com>> wrote:

John,

+1

We would like to request for allocation for following Sub-TLV to be. Pls let us know when the allocation is done.

Preference sub-TLV

6

Binding SID sub-TLV

7

Segment List sub-TLV

128



Cheers,

Gaurav

From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> on behalf of "John G. Scudder" <jgs@juniper.net<mailto:jgs@juniper.net>>
Date: Friday, October 6, 2017 at 5:50 AM
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com<mailto:ginsberg@cisco.com>>
Cc: "idr@ietf.org<mailto:idr@ietf.org>" <idr@ietf.org<mailto:idr@ietf.org>>, "shares@ndzh.com<mailto:shares@ndzh.com>" <shares@ndzh.com<mailto:shares@ndzh.com>>
Subject: Re: [Idr] Early allocation request for draft-ietf-idr-segment-routing-te-policy

On Oct 6, 2017, at 1:53 AM, Les Ginsberg (ginsberg) <ginsberg@cisco.com<mailto:ginsberg@cisco.com>> wrote:
[Les:] It is quite useful I think to point out this fact - but I fail to see how it is relevant to the early allocation decision.  Given that we know that these early codepoints are not available, I do not see that delaying early allocation helps in any way. If there are implementations that used these unassigned codepoints, the sooner we assign values the sooner these implementations can be updated to use values which will be interoperable - so if anything the facts argue that we should accelerate early allocation - not delay it.

That is a fine position to take and consistent with what I tried to express (whether it came through clearly or not).

Thanks,

--John