RFC 5596: Datagram Congestion Control Protocol (DCCP) Simultaneous-Open Technique to Facilitate NAT/Middlebox Traversal

This document specifies an update to the Datagram Congestion Control Protocol (DCCP), a connection-oriented and datagram-based transport protocol. The update…

Read RFC 5596 on the RFC Editor

Outgoing relationships (11 related RFCs)

Updates — RFC 4340: Datagram Congestion Control Protocol (DCCP)
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Informative reference — RFC 3261: SIP: Session Initiation Protocol
Informative reference — RFC 793: Transmission Control Protocol
Informative reference — RFC 4566: SDP: Session Description Protocol
Informative reference — RFC 3022: Traditional IP Network Address Translator (Traditional NAT)
Informative reference — RFC 2663: IP Network Address Translator (NAT) Terminology and Considerations
Informative reference — RFC 4787: Network Address Translation (NAT) Behavioral Requirements for Unicast UDP
Informative reference — RFC 5382: NAT Behavioral Requirements for TCP
Informative reference — RFC 5597: Network Address Translation (NAT) Behavioral Requirements for the Datagram Congestion Control Protocol
Informative reference — RFC 3235: Network Address Translator (NAT)-Friendly Application Design Guidelines

Incoming relationships (5 related RFCs)

Normatively referenced by — RFC 5597: Network Address Translation (NAT) Behavioral Requirements for the Datagram Congestion Control Protocol
Informatively referenced by — RFC 8095: Services Provided by IETF Transport Protocols and Congestion Control Mechanisms
Informatively referenced by — RFC 5595: The Datagram Congestion Control Protocol (DCCP) Service Codes
Informatively referenced by — RFC 6773: DCCP-UDP: A Datagram Congestion Control Protocol UDP Encapsulation for NAT Traversal
Informatively referenced by — RFC 9897: Datagram Congestion Control Protocol (DCCP) Extensions for Multipath Operation with Multiple Addresses