Skip to main content

References to draft-ietf-avt-rtp-mime

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 4102
As rfc3555
Registration of the text/red MIME Sub-Type
References Referenced by
Proposed Standard normatively references
RFC 4184
As rfc3555
RTP Payload Format for AC-3 Audio
References Referenced by
Proposed Standard normatively references
RFC 4288
As rfc3555
Media Type Specifications and Registration Procedures
References Referenced by
Best Current Practice normatively references
RFC 4425
As rfc3555
RTP Payload Format for Video Codec 1 (VC-1)
References Referenced by
Proposed Standard normatively references
RFC 4587
As rfc3555
RTP Payload Format for H.261 Video Streams
References Referenced by
Proposed Standard normatively references
RFC 4598
As rfc3555
Real-time Transport Protocol (RTP) Payload Format for Enhanced AC-3 (E-AC-3) Audio
References Referenced by
Proposed Standard normatively references
RFC 4612
As rfc3555
Real-Time Facsimile (T.38) - audio/t38 MIME Sub-type Registration
References Referenced by
Historic normatively references
RFC 4629
As rfc3555
RTP Payload Format for ITU-T Rec. H.263 Video
References Referenced by
Proposed Standard normatively references
RFC 4695
As rfc3555
RTP Payload Format for MIDI
References Referenced by
Proposed Standard normatively references
RFC 4733
As rfc3555
RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals
References Referenced by
Proposed Standard normatively references
RFC 4749
As rfc3555
RTP Payload Format for the G.729.1 Audio Codec
References Referenced by
Proposed Standard normatively references
RFC 3551
As rfc3555
RTP Profile for Audio and Video Conferences with Minimal Control
References Referenced by
Internet Standard informatively references
RFC 4351
As rfc3555
Real-Time Transport Protocol (RTP) Payload for Text Conversation Interleaved in an Audio Stream
References Referenced by
Historic informatively references
RFC 4396
As rfc3555
RTP Payload Format for 3rd Generation Partnership Project (3GPP) Timed Text
References Referenced by
Proposed Standard informatively references
RFC 4504
As rfc3555
SIP Telephony Device Requirements and Configuration
References Referenced by
Informational informatively references
RFC 4573
As rfc3555
MIME Type Registration for RTP Payload Format for H.224
References Referenced by
Proposed Standard informatively references
RFC 4855
As rfc3555
Media Type Registration of RTP Payload Formats
References Referenced by
Proposed Standard Possible Reference
RFC 4856
As rfc3555
Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences
References Referenced by
Proposed Standard Possible Reference
RFC 5109
As rfc3555
RTP Payload Format for Generic Forward Error Correction
References Referenced by
Proposed Standard Possible Reference
RFC 7261
As rfc3555
Offer/Answer Considerations for G723 Annex A and G729 Annex B
References Referenced by
Proposed Standard Possible Reference