Hi Stefano
Sure, SRRI provided in this document can explicitly indicate a recursive
operation (or relationship).
But it maybe a default behavior to do recursive operation when an SR-NODE
received remote prefix-sid with L/V flag set according to the documents
already existed. For example,
prefix reachability advertisement received:
prefix (1.0.0.99/32)
prefix-sid (30004), L/V flag set, //ISIS-SR
"IPv4 Source Router ID" is 1.0.0.4 //rfc7794
Then, prefix 1.0.0.9/32 can do recursion to prefix 1.0.0.4/32 by default.
If "default behavior" is not accepted, we can define a new RECURSIVE flag
in Prefix-SID Sub-TLV.
BTW, all we discussed is SID recursive but not sharing, even the first
case in this draft is actually not SID sharing, otherwise it will be cared
by draft-ietf-spring-conflict-resolution.
Thanks
Deccan
"Stefano Previdi (sprevidi)" <[email protected]>
2016-08-22 21:38
收件人
"[email protected]" <[email protected]>,
抄送
SPRING WG <[email protected]>
主题
Re: [spring] WG adoption requested for
draft-filsfils-spring-sr-recursing-info
> On Aug 9, 2016, at 5:55 AM, [email protected] wrote:
>
> Other documents have already addressed this issue,
I don’t think so. Can you point to these documents ?
> for example, set L-flag of Prefix-SID Sub-TLV in
draft-ietf-isis-segment-routing-extensions-05 and contain IPv4 Source
Router ID in rfc7794.
the L flag has the solely purpose of indicating the sid contains a local
value. Typically it goes with the V flag that indicates a value (i.e.:
local label).
Nothing is mentioned regarding sharing the same sid among different
services.
s.
>
>
> Thanks,
>
> Deccan
>
>
>
>
>
> [spring] WG adoption requested for
draft-filsfils-spring-sr-recursing-info
> "John G. Scudder" <[email protected]> Sun, 24 July 2016 12:54 UTCShow
header
> Dear WG,
>
> As we discussed at our meeting, working group adoption has been
requested for draft-filsfils-spring-sr-recursing-info. Please reply to the
list with your comments, including although not limited to whether or not
you support adoption. Non-authors are especially encouraged to comment.
>
> We will end the call on August 31, 2015.
>
> Authors, please indicate whether you are aware of any relevant IPR and
if so, whether it has been disclosed.
>
> Thanks,
>
> --Bruno and John
>
>
> _______________________________________________
> spring mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/spring
>
_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring
