Advisory Guidelines for UDP Deployment
draft-byrne-opsec-udp-advisory-00

Document Type Expired Internet-Draft (individual)
Last updated 2016-01-21 (latest revision 2015-07-20)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-byrne-opsec-udp-advisory-00.txt

Abstract

User Datagram Protocol (UDP) is commonly used as a volumetric attack transport on the internet. Some network operators experience surges of UDP attack traffic that are multiple orders of magnitude above the baseline traffic rate for UDP. Application developers should be advised that UDP is being rate-limited on a bits-per-second and packet-per-second basis by network operators to enforce known good baseline traffic levels for UDP. UDP has been abused to such an extent that legitimate use may become collateral damage and application and protocol developers should avoid using UDP as a transport when possible.

Authors

Cameron Byrne (cameron.byrne@t-mobile.com)
Jason Kleberg (jason.kleberg@t-mobile.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)