Re: [spring] Penultimate Segment Popping and RFC8200 (Was Re: We don't seem to be following our processes (Re: Network Programming - Penultimate Segment Popping))

[Mark Smith <[e-mail]>]

On Wed, 11 Dec 2019 at 10:39, Robert Raszuk <[e-mail]> wrote:
>
> Dear Fernando,
>
> Allow me to make something very clear here.
>
>> And, since we are at it, please let me know if IPv6 is and end to end
>> protocol. And, if it is, how does that e2e-ness work with inserting and
>> removing EHs on the path to the ultimate destination of a packet.
>
>
> The dream of IPv6 flat end to endless is long gone if it ever was even real.

I would have to question your understanding of the term "end to end"
if you're make such an assertion.


>
> There is no end to end IPv6 or for that matter IPv4 delivery today across any network. Regardless if this is private or public network of any reasonable size and service portfolio.

I don't think you understand what end-to-end means with those assertions.

NAT breaks end-to-end.

If your assertion was true about IPv6, then you are asserting that
literally every IPv6 packet is going through NAT66 at some point.
That's certainly not happening.




>
> Some form of encapsulation or tunneling is used in enterprises, in ISPs, in SPs or even in largest public clouds.
>
> So if you think that you can send an IPv6 packet and that this packet will be delivered to its final destination without any encapsulation on the way - this is just unreal. And the sooner you and others like you realize this the better for everyone.
>
> Think about L3VPNs reachability segmentation, think about SFC/NSH, think about L2 transport emulation of your circuits, think about seamless mobility, LISP  ...
>
> Just a tiny reality check,
>
> Thx,
> R.
> _______________________________________________
> spring mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/spring