RFC 5596: Datagram Congestion Control Protocol (DCCP) Simultaneous-Open Technique to Facilitate NAT/Middlebox Traversal
In plain English — editorial summary, not part of the RFC
This document specifies an update to the Datagram Congestion Control Protocol (DCCP), a connection-oriented and datagram-based transport protocol. The update adds support for the DCCP-Listen packet. This assists DCCP applications to communicate through middleboxes (e.g., a Network Address Port Translator or a DCCP server behind a firewall), where peering endpoints need to initiate communication in a near- simultaneous manner to establish necessary middlebox state. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5596
- Published
- September 2009
- Authors
- G. Fairhurst
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 25
- Also known as
- —
- Updates:
- RFC 4340
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5597Network Address Translation (NAT) Behavioral Requirements for the Datagram Congestion Control ProtocolCurrent
September 2009
- RFC 6323Sender RTT Estimate Option for the Datagram Congestion Control Protocol (DCCP)Current
July 2011
- RFC 6773DCCP-UDP: A Datagram Congestion Control Protocol UDP Encapsulation for NAT TraversalCurrent
November 2012
- RFC 6889Analysis of Stateful 64 TranslationCurrent
April 2013
- RFC 5844IPv4 Support for Proxy Mobile IPv6Current
May 2010
- RFC 6223Indication of Support for Keep-AliveCurrent
April 2011
- RFC 6544TCP Candidates with Interactive Connectivity Establishment (ICE)Current
March 2012
- RFC 6633Deprecation of ICMP Source Quench MessagesCurrent
May 2012
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?