On 04.01.2026 23:52, Tom Herbert wrote:
Sure. IETF can deprecate the protocol for new cases or make it a SHOULD NOT to use, but it's up to individual implementations determine the actions taken to best suit the needs of their users.
I'm not sure how much new code is needed for a new recommendation since the two implementations I pointed to both implement ESP, but if it's any, you have to have a *very* strong justification to overcome both the initial costs and new maintenance costs. That is for you to take up with the routing people. Joel tells me that the rtgarea might not be the right place. Maybe talk to the ADs. Surely a draft would be needed.
One point about maintenance costs: they're the cost of doing business if the code is used. That in itself isn't an argument. But there are probably some externalities involved here. If the routing area is causing a problem for IPv6 deployment, that's something to be addressed.
Eliot
OpenPGP_0x87B66B46D9D27A33.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ Int-area mailing list -- [email protected] To unsubscribe send an email to [email protected]
