Re: [Lsr] 答复: WG Last Call draft-ietf-lsr-isis-invalid-tlv

2020-01-02 Thread Les Ginsberg (ginsberg)
Aijun - Since advertising some sort of capability would also be unusable until all routers were upgraded to understand the new capability advertisement this does not help.  The consequences of enabling a form of authentication which is not supported by all nodes is an inconsistent LSPDB

[Lsr] 答复: Questions on Prefix Unreachable Announcement

2020-01-02 Thread Aijun Wang
Hi, Huaimo: Thanks for your review. After the holiday, let’s begin the discussion. Your understanding for generating the PUA(Prefix Unreachable Announcement) is correct, but the process for stop the PUA is not the way that we proposed. In theory, the ABR will send the PUA once when it

[Lsr] 答复: WG Last Call draft-ietf-lsr-isis-invalid-tlv

2020-01-02 Thread Aijun Wang
Is there any method to indicate or negotiate the support of ISO10589/RFC5304/RFC6233 because they are not back compatible? What will be the consequence when not all of the routers within the IGP domain support the same RFC? Will it valuable to add more clarification for the above incompatible

Re: [Lsr] WG Last Call draft-ietf-lsr-isis-invalid-tlv

2020-01-02 Thread Jeff Tantsura
yes/support Happy New Year all! Cheers, Jeff On Jan 2, 2020, 11:07 AM -0800, Christian Hopps , wrote: > This begins a 2 week WG Last Call, ending after Jan 16th, 2020, for > draft-ietf-lsr-isis-invalid-tlv. > > https://datatracker.ietf.org/doc/draft-ietf-lsr-isis-invalid-tlv/ > > Tony P (other

Re: [Lsr] WG Last Call draft-ietf-lsr-isis-invalid-tlv

2020-01-02 Thread Tony Li
As co-author: This is only 20 years overdue. Ship it already. :-) T > On Jan 2, 2020, at 11:06 AM, Christian Hopps wrote: > > This begins a 2 week WG Last Call, ending after Jan 16th, 2020, for > draft-ietf-lsr-isis-invalid-tlv. > >

Re: [Lsr] WG Last Call draft-ietf-lsr-isis-invalid-tlv

2020-01-02 Thread Antoni Przygienda
No knowledge of any undisclosed IPR On 1/2/20, 11:40 AM, "Paul Wells" wrote: Support (as co-author). Thanks, Paul On 1/2/20 2:06 PM, Christian Hopps wrote: > This begins a 2 week WG Last Call, ending after Jan 16th, 2020, for > draft-ietf-lsr-isis-invalid-tlv.

Re: [Lsr] WG Last Call draft-ietf-lsr-isis-invalid-tlv

2020-01-02 Thread Paul Wells
Support (as co-author). Thanks, Paul On 1/2/20 2:06 PM, Christian Hopps wrote: This begins a 2 week WG Last Call, ending after Jan 16th, 2020, for draft-ietf-lsr-isis-invalid-tlv. https://datatracker.ietf.org/doc/draft-ietf-lsr-isis-invalid-tlv/ Tony P (other authors already responded

Re: [Lsr] WG Last Call draft-ietf-lsr-isis-invalid-tlv

2020-01-02 Thread Antoni Przygienda
Support +1 obviously --- tony On 1/2/20, 11:35 AM, "Les Ginsberg (ginsberg)" wrote: As co-author, I obviously support moving the draft forward. The impetus for writing the draft was a real world interoperability problem - so there should be no debate about whether the draft is

Re: [Lsr] WG Last Call draft-ietf-lsr-isis-invalid-tlv

2020-01-02 Thread Les Ginsberg (ginsberg)
As co-author, I obviously support moving the draft forward. The impetus for writing the draft was a real world interoperability problem - so there should be no debate about whether the draft is needed. All parties involved in the problem have actively participated in writing the draft - so I

Re: [Lsr] WG Last Call draft-ietf-lsr-isis-invalid-tlv

2020-01-02 Thread Acee Lindem (acee)
Speaking as WG Member: I support publication. This is document fills a long-standing gap in the IS-IS specification. Thanks, Acee On 1/2/20, 2:09 PM, "Lsr on behalf of Christian Hopps" wrote: This begins a 2 week WG Last Call, ending after Jan 16th, 2020, for

[Lsr] WG Last Call draft-ietf-lsr-isis-invalid-tlv

2020-01-02 Thread Christian Hopps
This begins a 2 week WG Last Call, ending after Jan 16th, 2020, for draft-ietf-lsr-isis-invalid-tlv. https://datatracker.ietf.org/doc/draft-ietf-lsr-isis-invalid-tlv/ Tony P (other authors already responded during the adoption poll), please indicate your knowledge of any IPR related to this

[Lsr] lsr - New Meeting Session Request for IETF 107

2020-01-02 Thread IETF Meeting Session Request Tool
A new meeting session request has just been submitted by Acee Lindem, a Chair of the lsr working group. - Working Group Name: Link State Routing Area Name: Routing Area Session Requester: Acee Lindem Number of Sessions: 2 Length of