Re: [Lsr] LSR WG Adoption call for "IS-IS Traffic Engineering (TE) Metric Extensions" - draft-ginsberg-lsr-isis-rfc7810bis-00

2018-04-12 Thread Padma Pillay-Esnault
Support Thanks Padma On Mon, Apr 9, 2018 at 9:28 PM, Les Ginsberg (ginsberg) wrote: > Support (as co-author). > > > > This correction is needed to insure that interoperability is assured. > > > > Les > > > > > > *From:* Lsr *On Behalf Of *Acee

Re: [Lsr] LSR WG Adoption call for "IS-IS Traffic Engineering (TE) Metric Extensions" - draft-ginsberg-lsr-isis-rfc7810bis-00

2018-04-12 Thread Yingzhen Qu
Support +1. Thanks, Yingzhen From: Lsr on behalf of Jeff Tantsura Date: Tuesday, April 10, 2018 at 12:47 AM To: "Acee Lindem (acee)" Cc: "lsr@ietf.org" Subject: Re: [Lsr] LSR WG Adoption call for "IS-IS Traffic

Re: [Lsr] Flex Algorithms Drafts

2018-04-12 Thread Tony Przygienda
On Thu, Apr 12, 2018 at 2:52 AM, Acee Lindem (acee) wrote: > Hi Peter, > > Ok - we'll decide during whether to merge during the WG adoption call. It > would be a good LSR experiment for a combined draft if there are no > significant differences between the protocols that would

Re: [Lsr] Flex Algorithms Drafts

2018-04-12 Thread Acee Lindem (acee)
Hi Peter, Ok - we'll decide during whether to merge during the WG adoption call. It would be a good LSR experiment for a combined draft if there are no significant differences between the protocols that would make a combined draft unwieldy. Thanks, Acee On 4/12/18, 3:35 AM, "Peter Psenak

Re: [Lsr] Flex Algorithms Drafts

2018-04-12 Thread Ketan Talaulikar (ketant)
Hi Acee, I don't see a problem with the merge for ISIS and OSPF specs in a single document in this case. Authors are mostly identical and even though the ISIS spec was published earlier, the OSPF spec is fully in sync and leverages all those comments. A lot of the text applies to both

Re: [Lsr] Flex Algorithms Drafts

2018-04-12 Thread Peter Psenak
Hi Acee, On 11/04/18 22:36 , Acee Lindem (acee) wrote: In preparation for WG adoption and IANA early code point allocation, I suggest that we rename the “Flexible Algorithm Definition TLV Metric Registry” to the “Flexible Algorithm Definition TLV Metric Type Registry” to avoid confusion as to