From nobody Tue Nov 17 21:35:16 2020 Return-Path: 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 5098E3A1450; Tue, 17 Nov 2020 21:35:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.225 X-Spam-Level: * X-Spam-Status: No, score=1.225 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.276, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no 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 jPIpIl_1lb9E; Tue, 17 Nov 2020 21:35:13 -0800 (PST) Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0915B3A144D; Tue, 17 Nov 2020 21:35:12 -0800 (PST) X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=50.107.115.222; From: "Susan Hares" To: "'Ketan Talaulikar \(ketant\)'" , "'idr-chairs'" Cc: , "'Van De Velde, Gunter \(Nokia - BE/Antwerp\)'" References: <044301d6bbcc$1250dc60$36f29520$@ndzh.com> In-Reply-To: <044301d6bbcc$1250dc60$36f29520$@ndzh.com> Date: Wed, 18 Nov 2020 00:35:05 -0500 Message-ID: <00b701d6bd6c$924b62e0$b6e228a0$@ndzh.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B8_01D6BD42.A978DD50" X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHZnHWXKu0KqyRI4og4dRzCbNEKCgIRZCzfqbcSKvA= Content-Language: en-us X-Antivirus: AVG (VPS 201117-6, 11/17/2020), Outbound message X-Antivirus-Status: Not-Tested X-Authenticated-User: skh@ndzh.com Archived-At: Subject: Re: [Idr] IANA Early allocation request for draft-ietf-idr-bgp-ls-flex-algo X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Nov 2020 05:35:15 -0000 This is a multipart message in MIME format. ------=_NextPart_000_00B8_01D6BD42.A978DD50 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Ketan and Gunter: Thank you for your patience. I found out from Amanda at IANA that the process for adding this feature. I have sent a note to Alvaro requesting this early allocation. Cheers, Sue From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares Sent: Sunday, November 15, 2020 10:54 PM To: 'Ketan Talaulikar (ketant)'; 'idr-chairs' Cc: idr@ietf.org; 'Van De Velde, Gunter (Nokia - BE/Antwerp)' Subject: Re: [Idr] IANA Early allocation request for draft-ietf-idr-bgp-ls-flex-algo Ketan: Yes - it is part of the adopted draft. Thanks for letting me know I missed this in the WG Status. Sue From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Ketan Talaulikar (ketant) Sent: Tuesday, November 3, 2020 10:34 AM To: Susan Hares; idr-chairs Cc: idr@ietf.org; Van De Velde, Gunter (Nokia - BE/Antwerp) Subject: [Idr] IANA Early allocation request for draft-ietf-idr-bgp-ls-flex-algo Hello Sue/John, While the document is progressing on the WGLC, is it possible for us to request for early allocation for the following pending TLV code-point to aid implementation? https://tools.ietf.org/html/draft-ietf-idr-bgp-ls-flex-algo-04#section-5 1045 (suggested) - Flex Algorithm Exclude SRLG TLV Thanks, Ketan From: Van De Velde, Gunter (Nokia - BE/Antwerp) Sent: 03 November 2020 18:36 To: Ketan Talaulikar (ketant) ; Susan Hares ; idr@ietf.org Subject: RE: [Idr] IPR and WG LC for draft-ietf-idr-bgp-ls-flex-algo-04.txt (11/1 to 11/16) Hi Ketan, Thanks for the info. Having early allocation code point will help me to progress Nokia implementation. Kind Regards, G/ From: Ketan Talaulikar (ketant) Sent: Tuesday, November 3, 2020 13:55 To: Van De Velde, Gunter (Nokia - BE/Antwerp) ; Susan Hares ; idr@ietf.org Subject: RE: [Idr] IPR and WG LC for draft-ietf-idr-bgp-ls-flex-algo-04.txt (11/1 to 11/16) Hi Gunter, You are correct that early allocation has not been yet made for the FA Exclude SRLG TLV. This was because none of the authors had (yet) got to implement it and there was no request received for it. IMHO we should go ahead with a parallel request for early allocation if it is holding up an implementation. Do let know if we need to and if not wait for it happen at publication time. Thanks, Ketan From: Idr On Behalf Of Van De Velde, Gunter (Nokia - BE/Antwerp) Sent: 03 November 2020 18:06 To: Susan Hares ; idr@ietf.org Subject: Re: [Idr] IPR and WG LC for draft-ietf-idr-bgp-ls-flex-algo-04.txt (11/1 to 11/16) Hi Sue, All, Support to progress this draft. Please be aware that no code point is assigned yet to the Flex Algo Exclude SRLG TLV (chapter 3.5 of draft BGP-LS Extensions for Flex-Algo). Nokia has an implementation of this draft. G/ From: Idr On Behalf Of Susan Hares Sent: Monday, November 2, 2020 03:19 To: idr@ietf.org Subject: [Idr] IPR and WG LC for draft-ietf-idr-bgp-ls-flex-algo-04.txt (11/1 to 11/16) This begins a 2 week WG LC for draft-ietf-idr-bgp-ls-flex-algo-04.txt (11/1 to 11/16). The authors should send their IPR statements by Tuesday (11/3) or this WG LC will be extended 1 extra week. You can access the draft at: https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-flex-algo/ This draft is also needed to match BGP work to LSR specification for draft-ietf-lsr-flex-algo-13.txt (at IESG). There are 2 Cisco implementations of draft-ietf-idr-bgp-ls-flex-algo. Details on the implementations are at: https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-bgp-ls-flex-algo%20implem entations WG members should consider in their response: a) Are there technical issues with the flexible algorithm technology? b) Is this draft ready for publication? c) Will this technology aid LSR deployments? d) Are you concerned about the 2 implementations coming only from Cisco? If you know of any other planned implementations, please send Chairs this information or respond to this email to inform the WG. Cheers, Susan Hares ------=_NextPart_000_00B8_01D6BD42.A978DD50 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Ketan and Gunter:

 

Thank you for your = patience.  I found out from Amanda at IANA that the process for = adding this feature.  I have sent a note to Alvaro requesting this = early allocation.

 

Cheers, Sue =

 

From:= = Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan = Hares
Sent: Sunday, November 15, 2020 10:54 PM
To: = 'Ketan Talaulikar (ketant)'; 'idr-chairs'
Cc: idr@ietf.org; = 'Van De Velde, Gunter (Nokia - BE/Antwerp)'
Subject: Re: [Idr] = IANA Early allocation request for = draft-ietf-idr-bgp-ls-flex-algo

 

Ketan:

 

Yes – it is part = of the adopted draft.  Thanks for letting me know I missed this in = the WG Status.  

 

Sue =

 

 

 

From:= = Idr [mailto:idr-bounces@ietf.org] On Behalf Of Ketan Talaulikar = (ketant)
Sent: Tuesday, November 3, 2020 10:34 = AM
To: Susan Hares; idr-chairs
Cc: idr@ietf.org; Van = De Velde, Gunter (Nokia - BE/Antwerp)
Subject: [Idr] IANA = Early allocation request for = draft-ietf-idr-bgp-ls-flex-algo

 

Hello Sue/John,

 

While the document is progressing = on the WGLC, is it possible for us to request for early allocation for = the following pending TLV code-point to aid = implementation?

 

https://tools.ietf.org/html/draft-ietf-idr-bgp-ls-flex-algo-04#s= ection-5

 

    1045 (suggested) - Flex Algorithm = Exclude SRLG TLV

 

Thanks,

Ketan

 

From: Van De Velde, Gunter (Nokia - = BE/Antwerp) <gunter.van_de_velde@nokia.com>
Sent: 03 = November 2020 18:36
To: Ketan Talaulikar (ketant) = <ketant@cisco.com>; Susan Hares <shares@ndzh.com>; = idr@ietf.org
Subject: RE: [Idr] IPR and WG LC for = draft-ietf-idr-bgp-ls-flex-algo-04.txt (11/1 to = 11/16)

 

Hi = Ketan,

 

Thanks for the info.

Having early allocation code point will help me to = progress Nokia implementation.

 

Kind = Regards,

G/

 

From: Ketan Talaulikar (ketant) = <ketant@cisco.com> =
Sent: Tuesday, November 3, 2020 13:55
To: Van De = Velde, Gunter (Nokia - BE/Antwerp) <gunter.van_de_velde@nokia.c= om>; Susan Hares <shares@ndzh.com>; idr@ietf.org
Subject: RE: = [Idr] IPR and WG LC for draft-ietf-idr-bgp-ls-flex-algo-04.txt (11/1 to = 11/16)

 

Hi Gunter,

 

You are correct that early allocation has not been yet made = for the FA Exclude SRLG TLV. This was because none of the authors had = (yet) got to implement it and there was no request received for = it.

 

IMHO we should go ahead with a parallel request for early = allocation if it is holding up an implementation. Do let know if we need = to and if not wait for it happen at publication = time.

 

Thanks,

Ketan

 

From: Idr <idr-bounces@ietf.org> On = Behalf Of Van De Velde, Gunter (Nokia - BE/Antwerp)
Sent: = 03 November 2020 18:06
To: Susan Hares <shares@ndzh.com>; idr@ietf.org
Subject: Re: = [Idr] IPR and WG LC for draft-ietf-idr-bgp-ls-flex-algo-04.txt (11/1 to = 11/16)

 

Hi Sue, = All,

 

Support to progress this draft.

Please be aware that no code point is assigned yet to = the Flex Algo Exclude SRLG TLV (chapter 3.5 of draft BGP-LS Extensions = for Flex-Algo).

 

Nokia has an = implementation of this draft.

 

G/

 

 

From: Idr <idr-bounces@ietf.org> On = Behalf Of Susan Hares
Sent: Monday, November 2, 2020 = 03:19
To: idr@ietf.org
Subject: [Idr] = IPR and WG LC for draft-ietf-idr-bgp-ls-flex-algo-04.txt (11/1 to = 11/16)

 

This begins = a 2 week WG LC for  draft-ietf-idr-bgp-ls-flex-algo-04.txt =

(11/1 to 11/16). =   

 

The authors should send their IPR statements by = Tuesday (11/3)

or this WG LC will be = extended 1 extra week.

 

You can = access the draft at:

https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-flex-algo/

 

This draft is also needed to match BGP work to LSR = specification

for = draft-ietf-lsr-flex-algo-13.txt (at IESG).

 

There are 2 = Cisco implementations of draft-ietf-idr-bgp-ls-flex-algo. =

Details on the implementations are = at:

https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-= bgp-ls-flex-algo%20implementations

 

WG members = should consider in their response:

 

a) Are there = technical issues with the flexible algorithm technology? =

b) Is this draft ready for = publication?

c) Will this technology = aid LSR deployments?

d) Are you = concerned about the 2 implementations coming

only from Cisco?

 

If you know = of any other planned implementations, please send

Chairs this information or respond to this email to = inform the WG.

 

Cheers, = Susan Hares  

 

------=_NextPart_000_00B8_01D6BD42.A978DD50--