In general, I’m not sure it is worth adding aliases for various names used in different RFCs. But you could argue that this is appropriate because the old names are unnecessarily long. Another example would be HTTPStatus.REQUESTED_RANGE_NOT_SATISFIABLE vs “Range Not Satisfiable” <https://tools.ietf.org/html/rfc7233#section-4.4>.

If we were to go ahead with this, it would need a documentation update. A test case would also be nice, ensuring that the new name is the “one true” name, and the old name is an alias.