Skip to main content

References from RFC 3555

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 13
References Referenced by
normatively references
BCP 14
References Referenced by
normatively references
RFC 2029 RTP Payload Format of Sun's CellB Video Encoding
References Referenced by
Proposed Standard Possible Reference
RFC 2032 RTP Payload Format for H.261 Video Streams
References Referenced by
Proposed Standard Possible Reference
RFC 2045 Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
References Referenced by
Draft Standard normatively references
RFC 2048 Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures
References Referenced by
Best Current Practice normatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice Possible Reference
RFC 2190 RTP Payload Format for H.263 Video Streams
References Referenced by
Historic Possible Reference
RFC 2198 RTP Payload for Redundant Audio Data
References Referenced by
Proposed Standard Possible Reference
RFC 2250 RTP Payload Format for MPEG1/MPEG2 Video
References Referenced by
Proposed Standard Possible Reference
RFC 2327 SDP: Session Description Protocol
References Referenced by
Proposed Standard normatively references
RFC 2343 RTP Payload Format for Bundled MPEG
References Referenced by
Experimental Possible Reference Possible Downref
RFC 2429 RTP Payload Format for the 1998 Version of ITU-T Rec. H.263 Video (H.263+)
References Referenced by
Proposed Standard Possible Reference
RFC 2431 RTP Payload Format for BT.656 Video Encoding
References Referenced by
Proposed Standard Possible Reference
RFC 2435 RTP Payload Format for JPEG-compressed Video
References Referenced by
Proposed Standard Possible Reference
RFC 2586 The Audio/L16 MIME content type
References Referenced by
Informational Possible Reference Possible Downref
RFC 2658 RTP Payload Format for PureVoice(tm) Audio
References Referenced by
Proposed Standard Possible Reference
RFC 3190 RTP Payload Format for 12-bit DAT Audio and 20- and 24-bit Linear Sampled Audio
References Referenced by
Proposed Standard normatively references
RFC 3550 RTP: A Transport Protocol for Real-Time Applications
References Referenced by
Internet Standard normatively references
RFC 3551 RTP Profile for Audio and Video Conferences with Minimal Control
References Referenced by
Internet Standard normatively references