On 4/12/19 13:37, Ron Bonica wrote: [...] > > It seems to me that the following are equally controversial: > > > > * A transit node inserting a Routing header > * A transit node removing a Routing header > > > > We have agreed to move discussion of RH insertion out of the Network > Programming draft and into another draft. Shouldn’t discussion of RH > removal be treated similarly.
Of course yes. It seems there's some level of recurrency in this area. Folks trying to do an under-the-cover update of RFC8200 (wrt header insertion), or simply ignoring what RFC8200 says. We have been a long way in this area (to an extent of having to send back to the wg what would become RFC8200 (then rfc2460bis) because folks from one specific vendor were trying to push that agenda. It would seem to me that having us wg participants remind folks that you can't just violate specs (RFC8200, and Internet Standard) at will, or keep an eye on every move that is taken in this respect (e.g. <https://mailarchive.ietf.org/arch/msg/ipv6/12Qwp_eeQT2EmbUrSxBLL5HTcnM>) does not seem to be the best way to spend our time, and also becomes uncomfortable. It also seems to me that the work of spring and 6man should be better coordinated. At times it would seem to me like things are cooked up in spring, and then 6man is expected to adapt to that. -- when, if you want to change a standard, the place to do it is 6man, and not elsewhere. So, to make the point clear, until there is a point where there is wg consensus in 6man to formally update RFC8200, an Internet Standard, can we please remove from all wg documents any sort of EH insertion/removal/mangling? In that light, may I ask the ADs that these things are better taken care of? And that given the controversy around the topic, any decision taken in this respect is CC'ed to 6man, and a decision is taken *on the maIling list* (as it should)? Thanks, -- 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