Subject: [arch-d] IPv6 header insertion/removal (Fwd: Re: [spring] Is srv6 PSP a good idea)

From: Fernando Gont <[email-masked]>
Date: Wed, 26 Feb 2020 13:57:51 -0300

Folks,

This has been going on for at least months now.

So... IPv6 is not end to end?

-------- Forwarded Message --------
Subject: Re: [spring] Is srv6 PSP a good idea
Date: Wed, 26 Feb 2020 13:54:44 -0300
From: Fernando Gont <[email-masked]>
To: Dirk Steinberg <[email-masked]>
CC: Pablo Camarillo (pcamaril) <pcamaril=[email-masked]>, 
Mark Smith <[email-masked]>, SPRING WG <[email-masked]>

On 26/2/20 12:57, Dirk Steinberg wrote:
> Hi Fernando,
> 
> adding to my own comment and to be more specific:
> 
> The existing RFCs are very clear in their wording that
> the node identified in the Destination Address field of
> the  IPv6 header is free to do whatever it desires with
> the packet it just received. After all, the packet was
> addressed specifically to that node.
> 
> These nodes are called segment endpoint nodes in SRv6.
> 
> Only nodes that are *NOT* identified in the DA are
> prohibited from making any changes.
> This should be very clear, even if you seem to
> wish that IPv6 had been defined differently.

Are you saying that IPv6 allows for in the network header insertion/removal?

If so, please tell me how AH, Path-MTU Discovery, and ICMPv6 error 
reporting works -- all very basic functions of IPv6.

IPv6 is an end to end protocol. With RH you change the DA on the flight, 
because routing only works based on the DA -- there's no other way to 
specify waypoints.

If you claim otherwise, that can be, at best, a major misunderstanding 
of how IPv6 works.

Thanks,
-- 
Fernando Gont
e-mail: [email-masked] || [email-masked]
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1

-- 
Fernando Gont
e-mail: [email-masked] || [email-masked]
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1

-- 
Fernando Gont
SI6 Networks
e-mail: [email-masked]
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492