On Thu, Feb 27, 2020 at 1:45 AM Fernando Gont <fg...@si6networks.com> wrote:
> Hello, Eric, > > On 26/2/20 20:18, Eric Vyncke (evyncke) wrote: > > Writing this without any hat, > > > > Please note that on the logical side, it still have to be "proven" that > this idea is strictly forbidden by RFC 8200. > > Here's the proof part: > > 1) Isn't IPv6 end to end? > > 2) How do core components of IPv6, such as AH and PMTUD work in the > present of intermediate nodes that can add and/or remove arbitrary > extension headers? > > It should be clear from the above that EH insertion/deletion is forbidden. > As I already explained to you this is not true. The wording of RFC8200 clearly allows this. The node addresses by the DA of the packet can do this. I understand that you would like to modify the wording of RFC8200 to make your point true but it simply is not. Repeating a false statement does not make it true. Cheers Dirk > Since this topic has been brought up again and again, I have submitted > an errata to RFC8200 which clarifies the intended behaviour: > * https://www.rfc-editor.org/errata/eid5933 > > (that's what Errata's are for, after all... and it should be clear that > the EH processing part, overall, needs improvements). > > Thanks! > > Cheers, > -- > Fernando Gont > SI6 Networks > e-mail: fg...@si6networks.com > PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492 > > > > > _______________________________________________ > spring mailing list > spring@ietf.org > https://www.ietf.org/mailman/listinfo/spring >
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
