References from rfc4856
This is an experimental product. 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.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| BCP 13 |
Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures Refs Ref'd by |
Best Current Practice | normatively references | |
| BCP 14 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| BCP 78 |
Rights Contributors Provide to the IETF Trust Refs Ref'd by |
Best Current Practice | informatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | Possible Reference | |
| RFC 2586 |
The Audio/L16 MIME content type Refs Ref'd by |
Informational | informatively references | |
| RFC 3190 |
RTP Payload Format for 12-bit DAT Audio and 20- and 24-bit Linear Sampled Audio Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 3550 |
RTP: A Transport Protocol for Real-Time Applications Refs Ref'd by |
Internet Standard | normatively references | |
| RFC 3551 |
RTP Profile for Audio and Video Conferences with Minimal Control Refs Ref'd by |
Internet Standard | normatively references | |
| RFC 3555 |
MIME Type Registration of RTP Payload Formats Refs Ref'd by |
Proposed Standard | Possible Reference | |
| RFC 4288 |
Media Type Specifications and Registration Procedures Refs Ref'd by |
Best Current Practice | Possible Reference | |
| RFC 4566 |
SDP: Session Description Protocol Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 4855 |
Media Type Registration of RTP Payload Formats Refs Ref'd by |
Proposed Standard | normatively references |