Hi Jie and Ketan,




Thank you both for the good discussion.


Yes, the intent of the document aligns completely with Ketan39s opinion.


Sorry for the confusion caused by the use-case description in the document 
sec2.2, and we will calrify this part in the next version.





Best Regards,


Liyan





----邮件原文----发件人:Ketan Talaulikar  <[email protected]>收件人:"Dongjie (Jimmy)" 
<[email protected]>抄 送: Yingzhen Qu  
<[email protected]>,lsr  <[email protected]>,lsr-chairs  
<[email protected]>发送时间:2024-02-29 15:45:15主题:Re: [Lsr] WG Adoption Call - 
draft-gong-lsr-ospf-unreachable-link(02/23/24 - 03/08/24)Hi Jie,Regarding your 
point (2), my understanding is that this feature applies to OSPF cost (i.e., 
IGP metric) and as an extension is applicable to both the "base" SPF as well as 
any SPF computation (including FlexAlgo) that uses IGP metric. You are right, 
that the draft should clarify this. Moreover, the use-case description of 
flex-algo in section 2.2 is misleading - it can be achieved using this feature 
only if the flex-algo definition is using some metric type other than IGP 
metric.
The authors can correct my understanding.
Thanks,
Ketan



On Thu, Feb 29, 2024 at 1:01PM Dongjie (Jimmy) 
<[email protected]> wrote:



Hi Yingzhen, 


 


I’ve read the latest version of this document and support its adoption.  It is 
a useful feature in general to exclude some of the links from SPF  computation. 


 


I also have some comments for the authors to consider, they can be solved after 
the adoption. 


 


1.       I’m not sure the purpose is to advertise an unreachable link in OSPF, 
from the use cases in the draft, the link is still reachable and  can be used 
for some services, just it needs be excluded from normal SPF calculation. If 
this is correct, it is better the title of the draft and the name of the new 
capability Flag need to be updated to reflect this. 


 


2.       In the Flex-Algo use case, if the metric of a link is set to 
MaxLinkMetric (0xFFFF) to exclude it from normal SPF computation, while a  
Flex-Algo is defined to use the same metric type for path calculation, will it 
cause the link also be excluded from the Flex-Algo path computation? If not, 
will metric value 0xFFFF be used in the Flex-Algo computation? In other word, 
the interaction between  this new feature and Flex-Algo needs to be further 
elaborated. 


 


Best regards,


Jie


 




From: Lsr [mailto:[email protected]] On Behalf Of Yingzhen Qu Sent: Friday, 
February 23, 2024 1:28 PM To: lsr <[email protected]> lsr-chairs 
<[email protected]> Subject: [Lsr] WG Adoption Call - 
draft-gong-lsr-ospf-unreachable-link (02/23/24 - 03/08/24)




 

Hi,   This email begins a 2 week WG adoption poll for the following draft: 
https://datatracker.ietf.org/doc/draft-gong-lsr-ospf-unreachable-link/   Please 
review the document and indicate your support or objections by March 8th, 2024. 
Authors and contributors, please respond to the list indicating whether you are 
aware of any IPR that applies to the draft. Thanks, Yingzhen 





_______________________________________________ Lsr mailing list [email protected] 
https://www.ietf.org/mailman/listinfo/lsr 



_______________________________________________
Lsr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lsr

Reply via email to