RFC 8085: UDP Usage Guidelines

Publisher

RFC Editor (IETF)

URL

https://www.rfc-editor.org/rfc/rfc8085.html

Published

2017-03-01

Updated

unknown

Accessed

2026-10-02

HTTP status

200

License

IETF Trust Legal Provisions; no-redistribution; short excerpts and locators only

Source notes citing this source

• When one fragment of a SIP-over-UDP INVITE is dropped, the receiver never gets the INVITE, so the caller sees only its own retransmissions and then a timeout rather than an error response from the far end. inferred in context
• For UDP applications that cannot discover path MTU, RFC 8085 gives the effective send MTU as the smaller of 576 bytes and the first-hop MTU for IPv4, and 1280 bytes for IPv6. in context
• RFC 8085 notes that losing a single IP fragment loses the whole reassembled datagram, and that NATs and firewalls may discard fragments. in context
• RFC 8085 (BCP 145) says applications SHOULD NOT send UDP datagrams that result in IP packets exceeding the MTU along the path. in context
• RFC 8085 recommends PMTUD or Packetization Layer PMTUD for UDP applications, noting that PLPMTUD avoids depending on ICMP messages that middleboxes often filter. in context

Cite this source record

APA

WarmTransfer. (2017, March 1). RFC 8085: UDP Usage Guidelines. WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-8085-udp-usage-guidelines

BibTeX

@misc{warmtransfer-rfc-8085-udp-usage-guidelines,
  title  = {RFC 8085: UDP Usage Guidelines},
  author = {{WarmTransfer}},
  year   = {2017},
  url    = {https://warmtransfer.net/knowledge/sources/rfc-8085-udp-usage-guidelines},
  note   = {RFC Editor (IETF), accessed 2026-10-02}
}