]> Keio University / WIDE Project

Endo 5322 Fujisawa, Kanagawa 252-0882 JP daiya@sfc.wide.ad.jp

Preferred Networks / WIDE Project

1-6-1 Otemachi Chiyoda, Tokyo 100-0004 JP panda@wide.ad.jp

General Internet Engineering Task Force UDP UDP-Options This document defines the protocol number option in UDP options. The protocol number option specifies the protocol immediately following the UDP header.

Introduction The User Datagram Protocol provides only a port number and a checksum as a minimum functional transport protocol. Because of its simplicity and interoperability in the Internet, new transport protocols such as QUIC and SCTP are implemented over UDP. However, UDP has no field in the header that identifies the encapsulated protocol. Typically, the IANA port number is used for that purpose, but the port number corresponds to the service of the communication. We argue that it is a clear misuse of the port number to indicate the protocol on UDP. Currently, it is not possible to provide the UDP layer with information that maps UDP to the transport protocols implemented on top of UDP. Transport Options for UDP is a proposal for extending UDP to have an options area, using the difference between the total length field in the IP header and the length field in the UDP field. It allows options to be added in TLV(Type-Length-Value) format. This document describes the protocol number option, which allows information about the protocol following the UDP header to be provided in the UDP options area.

Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

UDP-based Protocol Extensibility

Spread of applications using UDP-based transport protocols Frequently, new transport protocols are implemented based on UDP, such as QUIC, and are used as transport protocols for existing applications. The following are examples of applications that operate using UDP-based transport protocols. HTTP

• HTTP/3 - HTTP over QUIC, uses UDP port 443.

DNS

• DNS over Datagram Transport Layer Security - uses UDP port 853.
• DNS over Dedicated QUIC Connections - uses UDP port 853, same as DNS over DTLS.

Concerns about limited UDP-based transport extensibility The UDP header does not have any information to identify the encapsulated protocol. Without this information, problems may arise when there are applications that can communicate with multiple transport protocols using the same port number. In the case of client-server communication, the server cannot instantly determine which transport protocol was used to send the packet sent by the client. For instance, when a new transport protocol other than QUIC is developed and used that is based on UDP and works as a transport for HTTP, the server will not be able to instantly identify whether QUIC is used as the transport protocol or the new one is used. Therefore, if the next protocol after the UDP header is a transport protocol, it should be possible to have a field in the UDP layer information that identifies the protocol that follows the UDP header.

Protocol Number in UDP Options The protocol number is a number to identify the protocol immediately following the UDP header. In many cases, the port number of the transport layer is available for this number, but a new protocol number is needed for protocols that do not have a port number, such as QUIC.

Option Format The UDP option is provided in the form of a TLV. The protocol number is represented by 16 bits. It is shown in Figure 1.

Option format

Recommendation TBD

IANA Considerations On publication, request IANA to create a new registry for protocol numbers. The details of the number will be described in a later revision. Also, request IANA to assign one number from the Safe Options range of the UDP Option Kind Number as Protocol Number (PROTONUM).

Security Considerations This document should not affect the security of the Internet.

References Normative References Informative References

Acknowledgements TBD