Hi Tony, well said.
With this in mind I'd rather ask: Do we really need SID list compression at all?
If silicon sooner or later get's tailored for SRv6, can't it be made to simply parse big enough headers?
IMHO SRv6 is the one thing that really allows for full flexibility for whatever use-cases may come up in the future. Any compression scheme has drawbacks.
Best regards, Martin Am 03.08.21 um 16:55 schrieb Tony Li:
Hi all, I have a bit of a different perspective. Whatever solution is selected, it will be basically forever. Vendors will cut this into silicon. Quite literally set in stone. It will get deployed and there will be no turning back. We should pick the best possible solution because we will have to live with it. Forever. That far surpasses the pain of having to replace whatever folks have deployed so far. Thus, while I wish no one undue pain, the fact is that current deployment, popularity, and market share aren’t compelling reasons to make a selection. We need the technically optimal solution. Please choose carefully. Please choose wisely. Please choose for the very long haul. Tony _______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
_______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
