RFC 4340: Datagram Congestion Control Protocol (DCCP)

The Datagram Congestion Control Protocol (DCCP) is a transport protocol that provides bidirectional unicast connections of congestion-controlled unreliable…

Read RFC 4340 on the RFC Editor

Incoming relationships (56 related RFCs)

Showing 50 of 56 related RFCs.

Updated by, Normatively referenced by — RFC 6335: Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry
Updated by — RFC 5596: Datagram Congestion Control Protocol (DCCP) Simultaneous-Open Technique to Facilitate NAT/Middlebox Traversal
Updated by, Normatively referenced by — RFC 5595: The Datagram Congestion Control Protocol (DCCP) Service Codes
Updated by, Normatively referenced by — RFC 6773: DCCP-UDP: A Datagram Congestion Control Protocol UDP Encapsulation for NAT Traversal
Normatively referenced by — RFC 6056: Recommendations for Transport-Protocol Port Randomization
Normatively referenced by — RFC 7657: Differentiated Services (Diffserv) and Real-Time Communication
Normatively referenced by — RFC 6092: Recommended Simple Security Capabilities in Customer Premises Equipment (CPE) for Providing Residential IPv6 Internet Service
Normatively referenced by — RFC 5238: Datagram Transport Layer Security (DTLS) over the Datagram Congestion Control Protocol (DCCP)
Normatively referenced by — RFC 6633: Deprecation of ICMP Source Quench Messages
Normatively referenced by — RFC 5597: Network Address Translation (NAT) Behavioral Requirements for the Datagram Congestion Control Protocol
Normatively referenced by — RFC 5622: Profile for Datagram Congestion Control Protocol (DCCP) Congestion ID 4: TCP-Friendly Rate Control for Small Packets (TFRC-SP)
Normatively referenced by — RFC 5762: RTP and the Datagram Congestion Control Protocol (DCCP)
Normatively referenced by — RFC 7122: Datagram Convergence Layers for the Delay- and Disruption-Tolerant Networking (DTN) Bundle Protocol and Licklider Transmission Protocol (LTP)
Normatively referenced by — RFC 5634: Quick-Start for the Datagram Congestion Control Protocol (DCCP)
Normatively referenced by — RFC 6323: Sender RTT Estimate Option for the Datagram Congestion Control Protocol (DCCP)
Normatively referenced by — RFC 9693: Benchmarking Methodology for Stateful NATxy Gateways
Normatively referenced by — RFC 9897: Datagram Congestion Control Protocol (DCCP) Extensions for Multipath Operation with Multiple Addresses
Informatively referenced by — RFC 5226: Guidelines for Writing an IANA Considerations Section in RFCs
Informatively referenced by — RFC 8126: Guidelines for Writing an IANA Considerations Section in RFCs
Informatively referenced by — RFC 6347: Datagram Transport Layer Security Version 1.2
Informatively referenced by — RFC 6991: Common YANG Data Types
Informatively referenced by — RFC 5245: Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols
Informatively referenced by — RFC 8085: UDP Usage Guidelines
Informatively referenced by — RFC 6763: DNS-Based Service Discovery
Informatively referenced by — RFC 9147: The Datagram Transport Layer Security (DTLS) Protocol Version 1.3
Informatively referenced by — RFC 6887: Port Control Protocol (PCP)
Informatively referenced by — RFC 5104: Codec Control Messages in the RTP Audio-Visual Profile with Feedback (AVPF)
Informatively referenced by — RFC 5405: Unicast UDP Usage Guidelines for Application Designers
Informatively referenced by — RFC 6679: Explicit Congestion Notification (ECN) for RTP over UDP
Informatively referenced by — RFC 7202: Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution
Informatively referenced by — RFC 7567: IETF Recommendations Regarding Active Queue Management
Informatively referenced by — RFC 8899: Packetization Layer Path MTU Discovery for Datagram Transports
Informatively referenced by — RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field
Informatively referenced by — RFC 7414: A Roadmap for Transmission Control Protocol (TCP) Specification Documents
Informatively referenced by — RFC 8900: IP Fragmentation Considered Fragile
Informatively referenced by — RFC 6021: Common YANG Data Types
Informatively referenced by — RFC 4782: Quick-Start for TCP and IP
Informatively referenced by — RFC 8087: The Benefits of Using Explicit Congestion Notification (ECN)
Informatively referenced by — RFC 9911: Common YANG Data Types
Informatively referenced by — RFC 4828: TCP Friendly Rate Control (TFRC): The Small-Packet (SP) Variant
Informatively referenced by — RFC 6077: Open Research Issues in Internet Congestion Control
Informatively referenced by — RFC 6940: REsource LOcation And Discovery (RELOAD) Base Protocol
Informatively referenced by — RFC 9040: TCP Control Block Interdependence
Informatively referenced by — RFC 9330: Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture
Informatively referenced by — RFC 9331: The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S)
Informatively referenced by — RFC 6574: Report from the Smart Object Workshop
Informatively referenced by — RFC 9522: Overview and Principles of Internet Traffic Engineering
Informatively referenced by — RFC 6013: TCP Cookie Transactions (TCPCT)
Informatively referenced by — RFC 7605: Recommendations on Using Assigned Transport Port Numbers
Informatively referenced by — RFC 8782: Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification