Hey Mark, I think the only place you can put uSIDs is in the IID field, and I went > to the effort of providing RFC references. >
I only tend to follow the rules which make sense or which violation even if they do not make sense goes against best practices, common rules or could endanger anyone or anything. RFCs you quote do not limit numer of ULAs to be one per network or even one per person - so I am not breaking any RFC if I use bunch of ULAs as it seems fit. When SPRING comes up with an out of the ordinary idea > This is far beyond SPRING topic. Operators and end users use RFC1918 everywhere as it gives them freedom and flexibility to construct their networks the way they like it. Sufficiently flexible min /8 private range must be made available for anyone's use if you want to see wider IPv6 adoption. And /8 as proven is not about need for 2^112 addresses - it's about constructing your network applications with well though addressing structure and hierarchy. This draft and the EH insertion draft show that this isn't and hasn't > happened. > I am not going to comment on the insertion part beyond the observation that when you apply new IPv6 header you are free to insert whatever you like into it. Likewise per RFC8200 when I see myself in destination address field of the outer IPv6 header I can process, insert or delete EHs as it seems fit. Extension headers (except for the Hop-by-Hop Options header) are not processed, inserted, or deleted by any node along a packet's delivery path, until the packet reaches the node (or each of the set of nodes, in the case of multicast) *identified in the Destination Address field of the IPv6 header.* I do not see any stretch of it in any SPRING related document. Best, R.
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
