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

[Robert Raszuk <[e-mail]>]

By your books does RFC 2473 or RFC 4798 or 100s of other RFCs which
encapsulate IPv6 packets all violate Internet Standard I presume IPv6 spec
?

One of us clearly is missing the point. I will let list members judge which
one :)

Cheers,
R.


On Wed, Dec 11, 2019 at 12:43 AM Fernando Gont <[e-mail]>
wrote:

> On 10/12/19 18:39, Robert Raszuk 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.
>
> You seem to missing the point. You are proposing behavior that goes
> against an Internet Standard.
>
> The fact that you are doing Standards Track work while violating an
> Internet Standard is simply amusing.
>
> If you want to do that, formally update the relevan spec. *That* is the
> way to go, as opposed to find your own reason for circumventing existing
> specifications.
>
> Thanks,
> --
> Fernando Gont
> SI6 Networks
> e-mail: [e-mail]
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>
>
>
>
>