Hi, Les:

 

Since this draft is the main entry for the management of invalid tlv in isis, 
will it be more useful to include the description that you provide for its 
completeness?  Knowing the possible consequences may drive the operators to 
consider more carefully for their updating deployment.

 

Anyway, I support this draft.

 

Best Regards.

 

Aijun Wang

China Telecom

 

发件人: Les Ginsberg (ginsberg) [mailto:ginsb...@cisco.com] 
发送时间: 2020年1月3日 13:29
收件人: Aijun Wang; 'Christian Hopps'; lsr@ietf.org
抄送: lsr-...@ietf.org; 'Antoni Przygienda'
主题: RE: [Lsr] 答复: WG Last Call draft-ietf-lsr-isis-invalid-tlv

 

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 - which means protocol function is broken.

 

I would also point out that the incompatibilities are discussed in the original 
specifications (RFC 5304 and RFC 6232) - both of which have been published for 
a number of years. The points being made in this regard in this draft aren't 
new.

 

   Les

 

> -----Original Message-----

> From: Lsr <lsr-boun...@ietf.org> On Behalf Of Aijun Wang

> Sent: Thursday, January 02, 2020 6:31 PM

> To: 'Christian Hopps' <cho...@chopps.org>; lsr@ietf.org

> Cc: lsr-...@ietf.org; 'Antoni Przygienda' <p...@juniper.net>

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

> 

> 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

> scenario, instead of saying "... ... therefore can only be safely enabled

> when all nodes support the extensions"?

> 

> 

> Best Regards.

> 

> Aijun Wang

> China Telecom

> 

> -----邮件原件-----

> 发件人:  <mailto:lsr-boun...@ietf.org> lsr-boun...@ietf.org [ 
> <mailto:lsr-boun...@ietf.org> mailto:lsr-boun...@ietf.org] 代表 Christian

> Hopps

> 发送时间: 2020年1月3日 3:07

> 收件人:  <mailto:lsr@ietf.org> lsr@ietf.org

> 抄送:  <mailto:lsr-...@ietf.org> lsr-...@ietf.org; Christian Hopps; Antoni 
> Przygienda

> 主题: [Lsr] WG Last Call draft-ietf-lsr-isis-invalid-tlv

> 

> 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/> 
> 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 work to the list as well.

> 

> Thanks,

> Chris & Acee.

> 

> _______________________________________________

> Lsr mailing list

>  <mailto:Lsr@ietf.org> Lsr@ietf.org

>  <https://www.ietf.org/mailman/listinfo/lsr> 
> https://www.ietf.org/mailman/listinfo/lsr

> 

> _______________________________________________

> Lsr mailing list

>  <mailto:Lsr@ietf.org> Lsr@ietf.org

>  <https://www.ietf.org/mailman/listinfo/lsr> 
> https://www.ietf.org/mailman/listinfo/lsr

_______________________________________________
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr

Reply via email to