Alexandru, I think the major misunderstanding here has to do with your use
case. The route option as it was floated was not originally intended to
address your use case, and when it was changed to address your use case, it got
a lot less popular. Thiss was not because there's anything wrong with your
use case, but because it came to be perceived as more applicable to use cases
where, from an architectural perspective, the IETF would prefer to use RA.
That is, it came to be perceived as a generic replacement for RA, which wasn't
what the working group set out to do.
_______________________________________________
mif mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/mif
