[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ms-ospf
Subject:    [Lsr] =?utf-8?q?draft-draft-peng-lsr-algorithm-related-adjacency?= =?utf-8?q?-sid?=
From:       <chen.ran () zte ! com ! cn>
Date:       2021-03-11 8:51:52
Message-ID: 202103111651528716447 () zte ! com ! cn
[Download RAW message or body]

[Attachment #2 (multipart/related)]

[Attachment #4 (multipart/alternative)]

[Attachment #6 (text/plain)]

Hi Tony, 


   Thanks for your comments. The reason why this draft is proposed is that:


   Currently, the current FA draft only defines that the algorithm identifier is \
included as part of a  Prefix-SID advertisement,that maybe not satisfy some scenarios \
where multiple algorithm share the same link resource.  


    For example, an SR-TE policy may be instantiated within specific Flex-algo plane, \
i.e.,the SID list requires to include algorithm related SIDs.  An algorithm-unware \
Adjacency-SID included in the SID list can just steer the packet towards the link, \
but can not apply different QoS policy for different algorithm.         


     Another example is that the TI-LFA backup path computed in Flex-algo plane may \
also contain an algorithm-unware Adjacency-SID, which maybe also used in other SR-TE \
instance that carries other service.

    This document complement that the algorithm identifier can be also  included as \
part of an Adjacency-SID advertisement for SR-MPLS.






Best Regards,


Ran


[Attachment #7 (text/html)]

<div class="zcontentRow"><p style="box-sizing: border-box; margin-top: 0px; \
margin-bottom: 0px; white-space: normal; min-height: 14px; line-height: 24px; \
font-size: 12px; outline: 0px !important; background-color: rgb(255, 255, \
255);"><span style="box-sizing: border-box; font-size: 14px; outline: 0px \
!important;">Hi Tony,&nbsp;</span></p><p style="box-sizing: border-box; margin-top: \
0px; margin-bottom: 0px; white-space: normal; min-height: 14px; line-height: 24px; \
font-size: 12px; outline: 0px !important; background-color: rgb(255, 255, \
255);"><span style="box-sizing: border-box; font-size: 14px; outline: 0px \
!important;">&nbsp; &nbsp;Thanks for your comments.&nbsp;The reason why this draft is \
proposed is that:</span></p><p style="box-sizing: border-box; margin-top: 0px; \
margin-bottom: 0px; white-space: normal; min-height: 14px; line-height: 24px; \
font-size: 12px; outline: 0px !important; background-color: rgb(255, 255, \
255);"><span style="box-sizing: border-box; font-size: 14px; outline: 0px \
!important;">&nbsp; &nbsp;Currently, the current FA draft only defines that \
the&nbsp;algorithm identifier is included as part of a&nbsp; Prefix-SID \
advertisement,that maybe not satisfy some scenarios where&nbsp;multiple algorithm \
share the same link resource. &nbsp;</span></p><p style="box-sizing: border-box; \
margin-top: 0px; margin-bottom: 0px; white-space: normal; min-height: 14px; \
line-height: 24px; font-size: 12px; outline: 0px !important; background-color: \
rgb(255, 255, 255);"><span style="box-sizing: border-box; font-size: 14px; outline: \
0px !important;">&nbsp; &nbsp; For example, an SR-TE policy may be instantiated \
within specific Flex-algo plane, i.e.,the SID list requires to include algorithm \
related SIDs. &nbsp;An algorithm-unware Adjacency-SID included in the SID list can \
just steer the packet towards the link, but can not apply different QoS policy for \
different algorithm. &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;</span></p><p \
style="box-sizing: border-box; margin-top: 0px; margin-bottom: 0px; white-space: \
normal; min-height: 14px; line-height: 24px; font-size: 12px; outline: 0px \
!important; background-color: rgb(255, 255, 255);"><span style="box-sizing: \
border-box; font-size: 14px; outline: 0px !important;">&nbsp; &nbsp; &nbsp;Another \
example is that the TI-LFA backup path computed in Flex-algo plane may also contain \
an algorithm-unware Adjacency-SID, which maybe also used in other SR-TE instance that \
carries other service.</span></p><p><span style="font-size: 14px;">&nbsp; &nbsp; This \
document complement that the algorithm identifier can be also &nbsp;included as part \
of an Adjacency-SID advertisement for SR-MPLS.</span></p><p \
style="font-size:12px;font-family:sans-serif;"><br></p><p \
style="font-size:12px;font-family:sans-serif;"><span style="font-size: 14px;">Best \
Regards,</span></p><p style="font-size:12px;font-family:sans-serif;"><span \
style="font-size: 14px;">Ran</span></p><p \
style="font-size:12px;font-family:sans-serif;"><br></p></div>



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


[prev in list] [next in list] [prev in thread] [next in thread]