Skip to main content

References to draft-ietf-avt-crtp

These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.

Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.

Document Title Status Type Downref
RFC 3544
As rfc2508
IP Header Compression over PPP
References Referenced by
Proposed Standard normatively references
RFC 3545
As rfc2508
Enhanced Compressed RTP (CRTP) for Links with High Delay, Packet Loss and Reordering
References Referenced by
Proposed Standard normatively references
RFC 4170
As rfc2508
Tunneling Multiplexed Compressed RTP (TCRTP)
References Referenced by
Best Current Practice normatively references
RFC 4247
As rfc2508
Requirements for Header Compression over MPLS
References Referenced by
Informational normatively references
RFC 5285
As rfc2508
A General Mechanism for RTP Header Extensions
References Referenced by
Proposed Standard normatively references
RFC 8285
As rfc2508
A General Mechanism for RTP Header Extensions
References Referenced by
Proposed Standard normatively references
RFC 3095
As rfc2508
RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed
References Referenced by
Proposed Standard informatively references
RFC 3557
As rfc2508
RTP Payload Format for European Telecommunications Standards Institute (ETSI) European Standard ES 201 108 Distributed Speech Recognition Encoding
References Referenced by
Proposed Standard informatively references
RFC 3819
As rfc2508
Advice for Internet Subnetwork Designers
References Referenced by
Best Current Practice informatively references
RFC 3890
As rfc2508
A Transport Independent Bandwidth Modifier for the Session Description Protocol (SDP)
References Referenced by
Proposed Standard informatively references
RFC 4362
As rfc2508
RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTP
References Referenced by
Proposed Standard informatively references
RFC 4413
As rfc2508
TCP/IP Field Behavior
References Referenced by
Informational informatively references
RFC 4612
As rfc2508
Real-Time Facsimile (T.38) - audio/t38 MIME Sub-type Registration
References Referenced by
Historic informatively references
RFC 4840
As rfc2508
Multiple Encapsulation Methods Considered Harmful
References Referenced by
Informational informatively references
RFC 4901
As rfc2508
Protocol Extensions for Header Compression over MPLS
References Referenced by
Proposed Standard informatively references
RFC 4995
As rfc2508
The RObust Header Compression (ROHC) Framework
References Referenced by
Proposed Standard informatively references
RFC 5761
As rfc2508
Multiplexing RTP Data and Control Packets on a Single Port
References Referenced by
Proposed Standard informatively references
RFC 5795
As rfc2508
The RObust Header Compression (ROHC) Framework
References Referenced by
Proposed Standard informatively references
RFC 6864
As rfc2508
Updated Specification of the IPv4 ID Field
References Referenced by
Proposed Standard informatively references
RFC 8088
As rfc2508
How to Write an RTP Payload Format
References Referenced by
Informational informatively references
RFC 9065
As rfc2508
Considerations around Transport Header Confidentiality, Network Operations, and the Evolution of Internet Transport Protocols
References Referenced by
Informational informatively references
RFC 9291
As rfc2508
A YANG Network Data Model for Layer 2 VPNs
References Referenced by
Proposed Standard informatively references
RFC 9392
As rfc2508
Sending RTP Control Protocol (RTCP) Feedback for Congestion Control in Interactive Multimedia Conferences
References Referenced by
Informational informatively references
RFC 3599
As rfc2508
Request for Comments Summary RFC Numbers 3500-3599
References Referenced by
Informational Possible Reference
RFC 3794
As rfc2508
Survey of IPv4 Addresses in Currently Deployed IETF Transport Area Standards Track and Experimental Documents
References Referenced by
Informational Possible Reference
RFC 2507
As rfc2508
IP Header Compression
References Referenced by
Proposed Standard Reference
RFC 2509
As rfc2508
IP Header Compression over PPP
References Referenced by
Proposed Standard Reference
RFC 2688
As rfc2508
Integrated Services Mappings for Low Speed Networks
References Referenced by
Proposed Standard Reference
RFC 2689
As rfc2508
Providing Integrated Services over Low-bitrate Links
References Referenced by
Informational Reference
RFC 2736
As rfc2508
Guidelines for Writers of RTP Payload Format Specifications
References Referenced by
Best Current Practice Reference
RFC 2757
As rfc2508
Long Thin Networks
References Referenced by
Informational Reference
RFC 3006
As rfc2508
Integrated Services in the Presence of Compressible Flows
References Referenced by
Proposed Standard Reference
RFC 3096
As rfc2508
Requirements for robust IP/UDP/RTP header compression
References Referenced by
Informational Reference
RFC 3135
As rfc2508
Performance Enhancing Proxies Intended to Mitigate Link-Related Degradations
References Referenced by
Informational Reference
RFC 3150
As rfc2508
End-to-end Performance Implications of Slow Links
References Referenced by
Best Current Practice Reference
RFC 3242
As rfc2508
RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTP
References Referenced by
Proposed Standard Reference
RFC 3336
As rfc2508
PPP Over Asynchronous Transfer Mode Adaptation Layer 2 (AAL2)
References Referenced by
Proposed Standard Reference
RFC 3409
As rfc2508
Lower Layer Guidelines for Robust RTP/UDP/IP Header Compression
References Referenced by
Informational Reference