Re: [spring] Spirit and Letter of the Law (was: Question about SRv6 Insert function)

[Robert Raszuk <[e-mail]>]

> 3) Now there's at least one I-D in spring that ignores RFC8200, and
> proposes EH-insertion as if it was allowed, essentially circumventing
> RFC8200, and IETF consensus.


Incorrect. RFC8200 makes it black on white clear that insertion, deletion
and mangling is allowed in IPv6 if destination is yourself in the packet's
IPv6 outer header.

So functions to insert SRH or delete it discussed in SPRING DO NOT violate
anything.

Remember - in SRv6 you *change* IPv6 dst at each end of segment. So each SR
segment node can legally  do whatever it needs with EH.

Is this clear enough?

- - -

There is other individual document in 6man proposing a solution for FRR in
IPv6 which goes beyond the above. But it in no way that should impact base
specs. As written base specs can be used 100% legally according to RFC8200
as it stands today.

Now if 6man response to proposl of SRv6 use case for FRR with TI-LFA will
state "IPv6 was not designed for that" - I am fine. It will make IPv6
deployments for sure much more robust. It may even help end to end
principle shine again and get all of your end IPv6 compute and set-top
boxes full open to global hackers.

Thx,
R.