Have any little-endian protocols been standardised with RFCs by the IETF?

Question

Historically, network protocol RFCs have used big-endian (network order) fields.

I am currently involved in the design of a new (UDP) protocol, which, one-day, might be standardised with an RFC.

Would having little-endian fields be a problem with standards committees?

Are there any examples of IETF-standardised protocols which use little-endian byte ordering?

(It does seem rather pointless to use big-endian representations in new protocols, as big-endian architectures are essentially dead.)

Answer 1

DO NOT USE LITTLE_ENDIAN. Among other things, the classic set of functions for dealing with endians-ness only include the concepts of "host" endian and "network" endian. There's no standard method of dealing with "little" endian.

Answer 2

Kerberos (eg. RFC6542) is a Proposed Standard and used little endian, so do RFC7748 elliptic curves.

Still, getting a new protocol approved that neither has very good reasons ("it's common in elliptic curve calculations" was, as was "Kerberos is already widely deployed"; "all my systems are LE anyway" will probably not be) will probably be not easy and need much discussion; see QUIC's for an example of such a discussion -- and note that QUIC does use network byte order.