RFC 8085

RFC 8085
Title	RFC 8085
Status	Best Current Practice
Author	R. Stewart, M. et al.
Published	February 2017
Pages	28
Doi	10.17487/RFC8085

RFC 8085

RFC 8085 is an informational Best Current Practice document that provides guidance for applications and implementers using the User Datagram Protocol (UDP). It consolidates operational experience and offers pragmatic recommendations for behavior, error handling, path MTU considerations, and interactions with middleboxes. The document aims to improve interoperability between endpoints, network devices, and applications across diverse deployment environments.

Introduction

The Introduction situates the document in the context of Internet standards development and operational practice, referencing work from the Internet Engineering Task Force, the Internet Architecture Board, and historical protocol efforts such as Transmission Control Protocol and Hypertext Transfer Protocol. It acknowledges deployment challenges that have been observed in the wake of protocols influenced by the Real-time Transport Protocol and the Domain Name System, and draws on operational experience from organizations like Cisco Systems, Juniper Networks, and Google. The section frames the need for guidance to avoid common pitfalls encountered by software projects tied to platforms such as Android (operating system), iOS, and server environments like Linux and FreeBSD.

Background and Motivation

This section explains the motivation rooted in observed failures, interoperability issues, and middlebox behavior first documented in reports from the IETF Transport Area, the IETF Applications and Real-Time Area, and operational forums including the Network Working Group. It references incidents and studies tied to deployment environments like Amazon Web Services, Microsoft Azure, and content delivery networks operated by Akamai Technologies and Cloudflare. Historical antecedents include protocol evolution discussions around Stream Control Transmission Protocol, QUIC, and the transition from legacy Internet Protocol behaviors. The rationale highlights how developments in mobile networks from operators such as Verizon Communications and AT&T and observations from carriers in the European Union and Asia-Pacific Economic Cooperation region have influenced expectations for UDP behavior.

UDP Usage Guidelines

This section lays out specific recommendations for application designers, citing examples from protocols like DNS over UDP, NTP, SIP (Session Initiation Protocol), and emerging transport designs such as QUIC and RTP. It recommends conservative practices for port selection, retry strategies, and congestion awareness, informed by experiences from projects by IETF QUIC Working Group, researchers at University of California, Berkeley, and operators at Internet2. The guidelines discuss interactions with operating systems including Windows, macOS, and distributions from Red Hat and Debian and address behavior on mobile stacks found on Samsung Electronics and Qualcomm platforms. Recommendations emphasize resilient client behavior similar to that advocated in studies by Stanford University and the Massachusetts Institute of Technology.

Protocol Considerations and Best Practices

This section provides technical best practices covering checksum handling, packetization, path MTU discovery, and fragmentation. It cites influential protocol specifications and analyses related to IPv6, ICMPv6, IPsec, and tunneling mechanisms like GRE and IP-in-IP. The guidance addresses middlebox interaction, referencing work by researchers from Princeton University and the University of Cambridge, and operational reports from backbone operators such as Level 3 Communications and NTT Communications. It recommends designing application-layer retransmission and congestion control strategies inspired by algorithms developed at IETF Congestion Control Research Group and earlier models used in TCP Reno and TCP Cubic studies.

Security and Privacy Considerations

The security section discusses threats such as amplification attacks, spoofing, and traffic analysis, referencing mitigation techniques informed by standards like RFC 6806 and encryption frameworks used in protocols like DTLS and TLS. It highlights relevance to infrastructure operated by entities such as CERT Coordination Center, European Union Agency for Cybersecurity, and law-enforcement collaborations, and cites research from institutions including Carnegie Mellon University and ETH Zurich. Recommended practices include rate limiting, proper validation of source addresses, application-layer cryptographic integrity, and considerations for privacy-preserving designs influenced by work on DNS over HTTPS and Encrypted SNI.

Implementation and Deployment Guidance

This final section gives implementers pragmatic advice for testing, logging, and incremental deployment, drawing on lessons from large-scale deployments by Facebook, Netflix, and Spotify. It advises coordination with network operators like Sprint Corporation and content networks run by Fastly and recommends toolchains and testbeds used in academia and industry such as PerfSONAR, Wireshark, and emulation platforms maintained by NetEm and the Mininet project. Operational checklist items include monitoring strategies, gradual rollout plans, and fallback behaviors to ensure robustness across edge environments like satellite communications providers and constrained networks managed by IEEE 802.11 and 3GPP operators.

Category:Internet standards