Re: [Idr] Implementations of draft-ietf-idr-bgpls-segment-routing-epe (draft-ietf-ospf-link-overload)

"Acee Lindem (acee)" <acee@cisco.com> Fri, 06 April 2018 22:05 UTC

Return-Path: <acee@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 6ECDE120721; Fri, 6 Apr 2018 15:05:54 -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_RP_MATCHES_RCVD=-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 546d19oPLt3u; Fri, 6 Apr 2018 15:05:52 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DEA8120227; Fri, 6 Apr 2018 15:05:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16756; q=dns/txt; s=iport; t=1523052352; x=1524261952; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=E9q5TVtbxiWfkUVgU8LCvSkqDXhiu8u4ZsjQ7ifpgp4=; b=Mv0aD5GL6lzbkrvKEMo4ketH7l6XsHtBFuCibHiVHP+NDvPV0j6yVccV dSqLDpUyR91QjGvFZ1GVQ5N7nLSuzxGjU9wTJVKH8/edI3dG+fMjJqOUt WZ5R7M/UwgSPBUtk4Xa8QomZkMNsBQvaLZ1N9fENS+D9DaExt3TbRynSa U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D8AAAF7sda/4oNJK1dGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYJNdWFvKAqDVYgAjQqBdIEPhmKHEoRkFIFmCx6EZQIagh8?= =?us-ascii?q?hNBgBAgEBAQEBAQJsHAyFIgEBAQEDI1YQAgEIDgMDAQIrAgICHxEdCAIEAQ0?= =?us-ascii?q?FhClMAxUPqgyCHIcJDYErgX0Fh2uCE4EMIoJigk9CAgIBAYEgWIJgMIIkAog?= =?us-ascii?q?MiECGSywIAoVShWKCfYxAiRw8hgcCERMBgSQBHDiBUnAVOioBghgJghcXEYh?= =?us-ascii?q?IhT5vAY1UgRcBAQ?=
X-IronPort-AV: E=Sophos; i="5.48,417,1517875200"; d="scan'208,217"; a="95641714"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Apr 2018 22:05:51 +0000
Received: from XCH-RTP-014.cisco.com (xch-rtp-014.cisco.com [64.101.220.154]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id w36M5psr025306 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 6 Apr 2018 22:05:51 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-014.cisco.com (64.101.220.154) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Fri, 6 Apr 2018 18:05:50 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1320.000; Fri, 6 Apr 2018 18:05:50 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Alvaro Retana <aretana.ietf@gmail.com>, "idr@ietf.org" <idr@ietf.org>
CC: "draft-ietf-ospf-link-overload@ietf.org" <draft-ietf-ospf-link-overload@ietf.org>, "draft-ietf-idr-bgpls-segment-routing-epe@ietf.org" <draft-ietf-idr-bgpls-segment-routing-epe@ietf.org>, "lsr-chairs@ietf.org" <lsr-chairs@ietf.org>
Thread-Topic: Implementations of draft-ietf-idr-bgpls-segment-routing-epe (draft-ietf-ospf-link-overload)
Thread-Index: AQHTzdhRBkh67Y0yeE6B6I9CtvfdhKP0SyaA
Date: Fri, 6 Apr 2018 22:05:50 +0000
Message-ID: <F8627C4B-8C22-409C-B5C3-431BA0713BBE@cisco.com>
References: <CAMMESswT9uPCtrqAOBqo7qU+f2eEsxhNR6d=oBomYYDfce-1vg@mail.gmail.com>
In-Reply-To: <CAMMESswT9uPCtrqAOBqo7qU+f2eEsxhNR6d=oBomYYDfce-1vg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.200]
Content-Type: multipart/alternative; boundary="_000_F8627C4B8C22409CB5C3431BA0713BBEciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/f3O3hVY9PCWecdsA0ooSInktk7c>
Subject: Re: [Idr] Implementations of draft-ietf-idr-bgpls-segment-routing-epe (draft-ietf-ospf-link-overload)
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: Fri, 06 Apr 2018 22:05:54 -0000

Hi Alvaro,

There are implementations and deployments - https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-bgpls-segment-routing-epe%20

Also, it looks to me that 1101 is assigned to Peer Node SID already - https://www.iana.org/assignments/bgp-ls-parameters/bgp-ls-parameters.xhtml#node-descriptor-link-descriptor-prefix-descriptor-attribute-tlv

Also, I do not see early allocation for the BGP-LS OSPF Link Overload TLV although one is requested in the corresponding draft. Hence, I don’t see what the problem is.

Thanks,
Acee



From: Alvaro Retana <aretana.ietf@gmail.com>
Date: Friday, April 6, 2018 at 2:51 PM
To: IDR List <idr@ietf.org>
Cc: "draft-ietf-ospf-link-overload@ietf.org" <draft-ietf-ospf-link-overload@ietf.org>rg>, "draft-ietf-idr-bgpls-segment-routing-epe@ietf.org" <draft-ietf-idr-bgpls-segment-routing-epe@ietf.org>rg>, "lsr-chairs@ietf.org" <lsr-chairs@ietf.org>rg>, Acee Lindem <acee@cisco.com>
Subject: Implementations of draft-ietf-idr-bgpls-segment-routing-epe (draft-ietf-ospf-link-overload)

Dear idr WG:

draft-ietf-ospf-link-overload [1] defines a new BGP-LS Graceful-Link-Shutdown TLV.  When an early allocation was requested, it was mistakenly requested from the "BGP-LS NLRI-Types" registry [2], not from the "BGP-LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute TLVs” registry [3].  IANA allocated a value according to the request: 1101.

The mistake wasn't noticed until the document was in IESG Evaluation -- we are in the process of correcting it.  However, the 1101 code point in the "BGP-LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute TLVs” registry corresponds to the Peer-Node-SID, an early allocation made to draft-ietf-idr-bgpls-segment-routing-epe [4], which says that "several early implementations exist".

Are there implementations of draft-ietf-idr-bgpls-segment-routing-epe with the 1101 code point?  Are there deployments of those implementations?

Thanks!

Alvaro.


[1] https://datatracker.ietf.org/doc/draft-ietf-ospf-link-overload/
[2] https://www.iana.org/assignments/bgp-ls-parameters/bgp-ls-parameters.xhtml#nlri-types
[3] https://www.iana.org/assignments/bgp-ls-parameters/bgp-ls-parameters.xhtml#node-descriptor-link-descriptor-prefix-descriptor-attribute-tlv
[4] https://datatracker.ietf.org/doc/draft-ietf-idr-bgpls-segment-routing-epe/