Op sec, Given the number of udp related developments, I created this I-d to express concern about further udp work and expound on some operational practices that conflict with udp growth.
Your feedback is welcome. ========= A new version of I-D, draft-byrne-opsec-udp-advisory-00.txt has been successfully submitted by Cameron Byrne and posted to the IETF repository. Name: draft-byrne-opsec-udp-advisory Revision: 00 Title: Advisory Guidelines for UDP Deployment Document date: 2015-07-20 Group: Individual Submission Pages: 5 URL: https://www.ietf.org/internet-drafts/draft-byrne-opsec-udp-advisory-00.txt Status: https://datatracker.ietf.org/doc/draft-byrne-opsec-udp-advisory/ Htmlized: https://tools.ietf.org/html/draft-byrne-opsec-udp-advisory-00 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. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat
_______________________________________________ OPSEC mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsec
