On Oct 7, 2015, at 4:21 PM, Pushpasis Sarkar <[email protected]<mailto:[email protected]>> wrote:
HI Stefano, From: "Stefano Previdi (sprevidi)" Date: Wednesday, October 7, 2015 at 7:31 PM To: Pushpasis Sarkar Cc: Robert Raszuk, Hannes Gredler, "[email protected]<mailto:[email protected]>", Isis-wg, "Clarence Filsfils (cfilsfil)" Subject: Re: [spring] [Isis-wg] Handling same SID mapped to different prefixes and vice versa cases You decide on a per-prefix base, which node-sid of the originator you want to use (if any). [Pushpasis] The default policy for deciding the sid to use should be the sid associated with prefix in the advertisement. Off course that can be overridden with some local policy but that is upto the implementation. The default behavior should be to use the sid associated with the prefix originally. With that default behavior the ingress should be able to use the same tunnel for more than one prefixes all originated from the same node. Which means that the originator should be able associate the same node-sid with more than one prefixes originated locally on that node. The question I have is what is the problem if we associate the same index for multiple prefix as long as those prefixes are all originated on the same node? I don’t see a issue yet. If you can pick an example and illustrate the issue you have in mind, perhaps it will help me to get convinced as well.. because you brake a simple rule of sid unicity and you will not be able to distinguish the case where two prefix legitimately share he same sid from the misconfiguration case. Also, you do not address all use cases with your solution. s. Thanks -Pushpasis
_______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
