]> Orange

Rennes 35000 France mohamed.boucadair@orange.com

Nokia

India kondtir@gmail.com

Operations and Management OPSAWG surplus area UDP options This document specifies new IP Flow Information Export (IPFIX) Information Elements for UDP options. Discussion Venues Discussion of this document takes place on the Operations and Management Area Working Group Working Group mailing list (opsawg@ietf.org), which is archived at . Source for this draft and an issue tracker can be found at .

Introduction IP Flow Information Export (IPFIX) is a protocol that is widely deployed in networks for traffic management purposes (). The protocol specifies the encoding of a set of basic data types and how the various Information Elements (IEs) are transmitted. In order to support the export of new flow-related measurement data, new IEs can be defined and registered in a dedicated IANA registry for interoperability. This document specifies new IPFIX Information Elements for UDP options (). A brief overview of UDP options is provided in . The IE specified in uses the new abstract data type ("unsigned256") defined in . Transport (including MTU) considerations are discussed in . Examples to illustrate the use of the new IPFIX Information Elements are provided in .

Conventions and Definitions 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. This document uses the IPFIX-specific terminology (e.g., Flow) defined in . As in the base IPFIX specification , these IPFIX-specific terms have the first letter of a word capitalized. The document adheres to the naming conventions for Information Elements per . Also, this document uses the terms defined in , especially "datagram" and "surplus area".

UDP Options at a Glance UDP does not support an extension mechanism similar to the options supported by other transport protocols, such as TCP , SCTP , or DCCP . Such a mechanism can be useful for various applications, e.g., to discover a path MTU or share timestamps. To fill that void, extends UDP with a mechanism to insert extensions in datagrams. To do so, and unlike the conventional approach that relies upon transport headers, uses trailers. Concretely, UDP options are placed in the surplus area (that is, the area of an IP payload that follows a UDP packet). See . An example of the use of UDP options for Datagram Packetization Layer Path Maximum Transmission Unit Discovery (DPLPMTUD) is described in .

Surplus Area +--------+---------+----------------------+------------------+ | IP Hdr | UDP Hdr | UDP user data | surplus area | +--------+---------+----------------------+------------------+ <------------------------------> UDP Length ]]>

Sections and introduce new IEs to export the observed UDP options. UDP options are unambiguously identified by means of a 1-byte field, called "Kind". Options indicated by Kind values in the range 0-191 are called SAFE options. Such options can be silently ignored by legacy receivers because they do not alter the UDP user data (). SAFE options are exported using the IE defined in . Options indicated by Kind values in the range 192-255 are called UNSAFE options. Such options are not safe for legacy receivers to ignore because they alter the UDP user data (). UNSAFE options are exported using the IE defined in . UDP options occur per-packet within a Flow and can be inserted at any time in the Flow. reserves two options for experiments: the Experimental option (EXP, Kind=127) for SAFE options and the UNSAFE Experimental option (UEXP, Kind=254). For both options, Experiment Identifiers (ExIDs) are used to differentiate concurrent use of these options. Known ExIDs are expected to be registered within IANA. specifies a new IPFIX IE to export observed ExIDs in the EXP options. Also, specifies a new IPFIX IE to export observed ExIDs in the UEXP options. Only 16-bit ExIDs are supported in . This document does not intend to elaborate operational guidance/implications of UDP options. The document focuses exclusively on exporting observed UDP options in datagrams.

New UDP IPFIX Information Elements

• RFC Editor Note: Please update "URL_IANA_UDP_OPTIONS" reference with the URL of the "UDP Option Kind Numbers" registry group and "URL_IANA_UDP_ExIDs" with the URL of the "UDP Experimental Option Experiment Identifiers (UDP ExIDs)" registry that will be created by IANA as per .

Given the Kind structure of SAFE and UNSAFE UDP options, using one single IE that would multiplex both types of option will limit the benefits of reduced-size encoding in the presence of UNSAFE options. In order to use less bits to report observed UDP options, distinct IEs are thus defined to report SAFE () and UNSAFE () UDP options.

udpSafeOptions

Name:

udpSafeOptions

ElementID:

TBD1

Description:

Observed SAFE UDP options in a Flow. The information is encoded in a set of bit fields.

Options are mapped to bits according to their option numbers. UDP option Kind 0 corresponds to the least-significant bit in the udpSafeOptions IE while Kind 191 corresponds to the 65th most-significant bit of the IE. The bit is set to 1 if the corresponding SAFE UDP option is observed at least once in the Flow. The bit is set to 0 if the option is never observed in the Flow. The 64 most-significant bits MUST be set to 0.

The reduced-size encoding per is followed whenever fewer octets are needed to report observed SAFE UDP options. For example, if only option Kinds <= 31 are observed, then the value of the udpSafeOptions IE can be encoded as unsigned32, or if only option Kinds <= 63 are observed, then the value of the udpSafeOptions IE can be encoded as unsigned64.

The presence of udpSafeExIDList is an indication that the SAFE Experimental option is observed in a Flow. The presence of udpSafeExIDList takes precedence over setting the corresponding bit in the udpSafeOptions IE for the same Flow. In order to optimize the use of the reduced-size encoding in the presence of udpSafeExIDList IE, the Exporter MUST NOT set to 1 the EXP flag of the udpSafeOptions IE that is reported for the same Flow.

Abstract Data Type:

unsigned256

Data Type Semantics:

flags

Additional Information:

See the "UDP Option Kind Numbers" registry at .

See for more details about UDP options.

Reference:

This-Document

udpUnsafeOptions

Name:

udpUnsafeOptions

ElementID:

TBD2

Description:

Observed UNSAFE UDP options in a Flow. The information is encoded in a set of bit fields.

Options are mapped to bits according to their option numbers. UDP option Kind 192 corresponds to the least-significant bit in the udpUnsafeOptions IE while Kind 255 corresponds to the most-significant bit of the IE. The bit is set to 1 if the corresponding UNSAFE UDP option is observed at least once in the Flow. The bit is set to 0 if the option is never observed in the Flow.

The reduced-size encoding per is followed whenever fewer octets are needed to report observed UNSAFE UDP options.

The presence of udpUnsafeExIDList is an indication that the UNSAFE Experimental option is observed in a Flow. The presence of udpUnsafeExIDList takes precedence over setting the corresponding bit in the udpUnsafeOptions IE for the same Flow. In order to optimize the use of the reduced-size encoding in the presence of udpUnsafeExIDList IE, the Exporter MUST NOT set to 1 the UEXP flag of the udpUnsafeOptions IE that is reported for the same Flow.

Abstract Data Type:

unsigned64

Data Type Semantics:

flags

Additional Information:

See the "UDP Option Kind Numbers" registry at .

See for more details about UDP options.

Reference:

This-Document

udpExID

Name:

udpExID

ElementID:

TBD3

Description:

Observed ExID in an Experimental option (EXP, Kind=127) or an UNSAFE Experimental option (UEXP, Kind=254).

A basicList of udpExID is used to report udpSafeExIDList and udpUnsafeExIDList values.

Abstract Data Type:

unsigned16

Data Type Semantics:

identifier

Additional Information:

See the "UDP Experimental Option Experiment Identifiers (UDP ExIDs)" registry at .

See for more details about ExIDs.

Reference:

This-Document

udpSafeExIDList

Name:

udpSafeExIDList

ElementID:

TBD4

Description:

Observed ExIDs in the Experimental option (EXP, Kind=127).

A basicList of udpExID Information Elements in which each udpExID Information Element carries the ExID observed in an EXP option.

Abstract Data Type:

basicList

Data Type Semantics:

list

Additional Information:

See the "UDP Experimental Option Experiment Identifiers (UDP ExIDs)" registry at .

See for more details about ExIDs.

Reference:

This-Document

udpUnsafeExIDList

Name:

udpUnsafeExIDList

ElementID:

TBD5

Description:

Observed ExIDs in the UNSAFE Experimental option (UEXP, Kind=254).

A basicList of udpExID Information Elements in which each udpExID Information Element carries the ExID observed in an UEXP option.

Abstract Data Type:

basicList

Data Type Semantics:

list

Additional Information:

See the "UDP Experimental Option Experiment Identifiers (UDP ExIDs)" registry at .

See for more details about ExIDs.

Reference:

This-Document

Examples

Reduced-size Encoding Given the UDP Kind allocation in and the option mapping defined in of this document, fewer octets are likely to be used for Flows with mandatory UDP options. shows an example of the Kind/bit mappings in the udpSafeOptions IE for a Flow in which End of Options List (EOL, Kind=0) and Alternate payload checksum (APC, Kind=2) options are observed. Only the bits that corresponds to EOL and APC options are set to 1.

An Example of udpSafeOptions IE with EOL and APC Options

One octet is sufficient to report these observed options because the leading zeros are dropped per the reduced-size encoding guidance. Concretely, the reported udpSafeOptions IE will be set to 0x05 ().

An Example of the Wire udpSafeOptions IE Value with EOL and APC Options

SAFE Experimental Option Let us now consider a UDP Flow in which SAFE Experimental options are observed. If a udpSafeOptions IE is exported for this Flow, then that IE will have the EXP bit set to 1 (). This example does not make any assumption about the presence of other UDP options ("X" can be set to 0 or 1).

An Example of udpSafeOptions with EXP Option

ExIDs and Reduced-size Encoding Now assume that EOL, APC, EXP, and UEXP options are observed in a Flow. Let us also consider that the observed SAFE Experimental options have ExIDs set to 0x9858 and 0xE2D4, and UNSAFE Experimental options have ExIDs set to 0xC3D9 and 0x1234. shows an excerpt of the Data Set encoding with a focus on SAFE Experimental options have ExIDs. The meaning of the fields is defined in .

Example of UDP Experimental Option ExID IEs

Following the guidance in , the reported udpSafeOptions IE will be set to 0x05 even in the presence of EXP options.

Security Considerations This document does not introduce new security considerations other than those already discussed in and . The reader may refer to for the security considerations related to UDP options.

IANA Considerations

IPFIX Information Elements This document requests IANA to add the following new IEs to the "IPFIX Information Elements" registry under the "IP Flow Information Export (IPFIX) Entities" registry group : New IPFIX Information Elements

Value	Name	Reference
TBD1	udpSafeOptions	of This-Document
TBD2	udpUnsafeOptions	of This-Document
TBD3	udpExID	of This-Document
TBD4	udpSafeExIDList	of This-Document
TBD5	udpUnsafeExIDList	of This-Document

• udpSafeOptions uses the abstract data type ("unsigned256") defined in .

References Normative References This document specifies the IP Flow Information Export (IPFIX) protocol, which serves as a means for transmitting Traffic Flow information over the network. In order to transmit Traffic Flow information from an Exporting Process to a Collecting Process, a common representation of flow data and a standard means of communicating them are required. This document describes how the IPFIX Data and Template Records are carried over a number of transport protocols from an IPFIX Exporting Process to an IPFIX Collecting Process. This document obsoletes RFC 5101. Orange Huawei This document specifies new IP Flow Information Export (IPFIX) Information Elements (IEs) to solve issues with existing ipv6ExtensionHeaders and tcpOptions IPFIX IEs, especially the ability to export any observed IPv6 extension headers or TCP options. In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. This document defines the data types and management policy for the information model for the IP Flow Information Export (IPFIX) protocol. This information model is maintained as the IANA "IPFIX Information Elements" registry, the initial contents of which were defined by RFC 5102. This information model is used by the IPFIX protocol for encoding measured traffic information and information related to the traffic Observation Point, the traffic Metering Process, and the Exporting Process. Although this model was developed for the IPFIX protocol, it is defined in an open way that allows it to be easily used in other protocols, interfaces, and applications. This document obsoletes RFC 5102. Independent Consultant Transport protocols are extended through the use of transport header options. This document updates RFC 768 (UDP) by indicating the location, syntax, and semantics for UDP transport layer options within the surplus area after the end of the UDP user data but before the end of the IP length. This document specifies an extension to the IP Flow Information Export (IPFIX) protocol specification in RFC 5101 and the IPFIX information model specified in RFC 5102 to support hierarchical structured data and lists (sequences) of Information Elements in data records. This extension allows definition of complex data structures such as variable-length lists and specification of hierarchical containment relationships between Templates. Finally, the semantics are provided in order to express the relationship among multiple list elements in a structured data record. [STANDARDS-TRACK] Informative References n.d. n.d. n.d. This document gives an overview of the IETF network management standards and summarizes existing and ongoing development of IETF Standards Track network management protocols and data models. The document refers to other overview documents, where they exist and classifies the standards for easy orientation. The purpose of this document is, on the one hand, to help system developers and users to select appropriate standard management protocols and data models to address relevant management needs. On the other hand, the document can be used as an overview and guideline by other Standard Development Organizations or bodies planning to use IETF management technologies and data models. This document does not cover Operations, Administration, and Maintenance (OAM) technologies on the data-path, e.g., OAM of tunnels, MPLS Transport Profile (MPLS-TP) OAM, and pseudowire as well as the corresponding management models. This document is not an Internet Standards Track specification; it is published for informational purposes. This document specifies the Transmission Control Protocol (TCP). TCP is an important transport-layer protocol in the Internet protocol stack, and it has continuously evolved over decades of use and growth of the Internet. Over this time, a number of changes have been made to TCP as it was specified in RFC 793, though these have only been documented in a piecemeal fashion. This document collects and brings those changes together with the protocol specification from RFC 793. This document obsoletes RFC 793, as well as RFCs 879, 2873, 6093, 6429, 6528, and 6691 that updated parts of RFC 793. It updates RFCs 1011 and 1122, and it should be considered as a replacement for the portions of those documents dealing with TCP requirements. It also updates RFC 5961 by adding a small clarification in reset handling while in the SYN-RECEIVED state. The TCP header control bits from RFC 793 have also been updated based on RFC 3168. This document describes the Stream Control Transmission Protocol (SCTP) and obsoletes RFC 4960. It incorporates the specification of the chunk flags registry from RFC 6096 and the specification of the I bit of DATA chunks from RFC 7053. Therefore, RFCs 6096 and 7053 are also obsoleted by this document. In addition, RFCs 4460 and 8540, which describe errata for SCTP, are obsoleted by this document. SCTP was originally designed to transport Public Switched Telephone Network (PSTN) signaling messages over IP networks. It is also suited to be used for other applications, for example, WebRTC. SCTP is a reliable transport protocol operating on top of a connectionless packet network, such as IP. It offers the following services to its users: The design of SCTP includes appropriate congestion avoidance behavior and resistance to flooding and masquerade attacks. The Datagram Congestion Control Protocol (DCCP) is a transport protocol that provides bidirectional unicast connections of congestion-controlled unreliable datagrams. DCCP is suitable for applications that transfer fairly large amounts of data and that can benefit from control over the tradeoff between timeliness and reliability. [STANDARDS-TRACK] University of Aberdeen University of Aberdeen This document specifies how a UDP Options sender implements Datagram Packetization Layer Path Maximum Transmission Unit Discovery (DPLPMTUD) as a robust method for Path Maximum Transmission Unit discovery. This method uses the UDP Options packetization layer. It allows an application to discover the largest size of datagram that can be sent across a network path. It also provides a way to allow the application to periodically verify the current maximum packet size supported by a path and to update this when required.

Acknowledgments Thanks to Benoît Claise for the discussion on the ordering of IPFIX IEs. Thanks to Paul Aitken for the review and comments. Thanks to Tommy Pauly for the tsvart review, Joe Touch for the intdir review, Robert Sparks for the genart review, Watson Ladd for the secdir review, and Jouni Korhonen for the opsdir review. Thanks to Thomas Graf for the Shepherd review. Thanks to Mahesh Jethanandani for the AD review. Thanks to Éric Vyncke for the IESG review.