Dear colleagues,
I have a couple of questions about the life span of the Path Segment.

Suppose that some entity has computed and instantiated an SR LP that follows a 
specific path from the ingress node to the  egress node across a single IGP 
domain. This path is expressed as a sequence of valid IGP Segments (e.g., Node 
and/or Adjacency segments) .
Suppose also that a Path Segment has been allocated by the egress node for this 
path, and the ingress node is aware of this and inserts the label acting as the 
SID for the Path segments immediately after the last SID of the path.

Now my questions:

1.       What happens to the Path Segment when one of the IGP segments defining 
the original path fails?

a.       To the best of my understanding the path itself becomes invalid

b.       Will the Path Segment that identifies the now invalid path be retained 
indefinitely, or would it be invalidated as well and the label acting as its 
SID released?

2.       Suppose that the entity that has computed and instantiated the 
original path re-computes it and instantiate a new valid path.

a.       Should the new path (that replaces the invalidated original one) be 
allocated with the same Path Segment as the original path, or should a new Path 
Segment be allocated for it?

b.       If the Path Segment allocated for the invalidated path is released 
(see (1b) above), can the label that identified it be re-used as the Path 
Segment ID immediately, or only after some delay?

>From my POV the answers to these questions do not depend on the actual method 
>by which the Path Segments are allocated and propagated from the egress node 
>to the ingress one.
And while my questions explicitly mention IGP Segments that define the SR LSP 
for which the Path Segment is allocated, the desired behavior should not depend 
on the type of segments used in the definition of the path.

Your feedback would be highly appreciated.

Regards, and lots of thanks in advance,
Sasha

Office: +972-39266302
Cell:      +972-549266302
Email:   [email protected]


___________________________________________________________________________

This e-mail message is intended for the recipient only and contains information 
which is 
CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received 
this 
transmission in error, please inform us by e-mail, phone or fax, and then 
delete the original 
and all copies thereof.
___________________________________________________________________________
_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring

Reply via email to