Skip to main content

References from draft-eckel-siprec-rtp-rec

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.

Reference type help

Document Title Status Type Downref
BCP 131
References Referenced by
informatively references
BCP 14
References Referenced by
normatively references
draft-ietf-siprec-architecture An Architecture for Media Recording Using the Session Initiation Protocol
References Referenced by
Informational informatively references
draft-ietf-siprec-protocol Session Recording Protocol
References Referenced by
Proposed Standard informatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 3550 RTP: A Transport Protocol for Real-Time Applications
References Referenced by
Internet Standard informatively references
RFC 3551 RTP Profile for Audio and Video Conferences with Minimal Control
References Referenced by
Internet Standard informatively references
RFC 3711 The Secure Real-time Transport Protocol (SRTP)
References Referenced by
Proposed Standard informatively references
RFC 4585 Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)
References Referenced by
Proposed Standard informatively references
RFC 4961 Symmetric RTP / RTP Control Protocol (RTCP)
References Referenced by
Best Current Practice informatively references
RFC 5104 Codec Control Messages in the RTP Audio-Visual Profile with Feedback (AVPF)
References Referenced by
Proposed Standard informatively references
RFC 5124 Extended Secure RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/SAVPF)
References Referenced by
Proposed Standard informatively references
RFC 5168 XML Schema for Media Control
References Referenced by
Informational informatively references
RFC 5761 Multiplexing RTP Data and Control Packets on a Single Port
References Referenced by
Proposed Standard informatively references
RFC 6222 Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)
References Referenced by
Proposed Standard informatively references
RFC 6263 Application Mechanism for Keeping Alive the NAT Mappings Associated with RTP / RTP Control Protocol (RTCP) Flows
References Referenced by
Proposed Standard informatively references
STD 64
References Referenced by
informatively references
STD 65
References Referenced by
informatively references