On the Implementation of the TCP Urgent Mechanism
RFC 6093, “On the Implementation of the TCP Urgent Mechanism”, is a Proposed Standard document published in January 2011 by F. Gont, A. Yourtchenko. It updates RFC 793, RFC 1011, RFC 1122. It has been obsoleted by RFC 9293 — refer to the newer document for the authoritative version. The canonical text is published by the RFC Editor.
Abstract
This document analyzes how current TCP implementations process TCP urgent indications and how the behavior of some widely deployed middleboxes affects how end systems process urgent indications. This document updates the relevant specifications such that they accommodate current practice in processing TCP urgent indications, raises awareness about the reliability of TCP urgent indications in the Internet, and recommends against the use of urgent indications (but provides advice to applications that do). [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 6093 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6092 Recommended Simple Security Capabilities in Customer Premises Equipment for Providing Residential IPv6 Internet Service
- RFC 6094 Summary of Cryptographic Authentication Algorithm Implementation Requirements for Routing Protocols
- RFC 6091 Using OpenPGP Keys for Transport Layer Security Authentication
- RFC 6095 Extending YANG with Language Abstractions
- RFC 6090 Fundamental Elliptic Curve Cryptography Algorithms
- RFC 6096 Stream Control Transmission Protocol Chunk Flags Registration
- RFC 6089 Flow Bindings in Mobile IPv6 and Network Mobility Basic Support
- RFC 6097 Local Mobility Anchor Discovery for Proxy Mobile IPv6