References from rfc4313
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 14 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
BCP 78 |
Rights Contributors Provide to the IETF Trust References Referenced by |
Best Current Practice | informatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | Possible Reference | |
RFC 2326 |
Real Time Streaming Protocol (RTSP) References Referenced by |
Proposed Standard | informatively references | |
RFC 2608 |
Service Location Protocol, Version 2 References Referenced by |
Proposed Standard | informatively references | |
RFC 2782 |
A DNS RR for specifying the location of services (DNS SRV) References Referenced by |
Proposed Standard | informatively references | |
RFC 3238 |
IAB Architectural and Policy Considerations for Open Pluggable Edge Services References Referenced by |
Informational | normatively references | |
RFC 3261 |
SIP: Session Initiation Protocol References Referenced by |
Proposed Standard | informatively references | |
RFC 3351 |
User Requirements for the Session Initiation Protocol (SIP) in Support of Deaf, Hard of Hearing and Speech-impaired Individuals References Referenced by |
Informational | normatively references | |
RFC 3435 |
Media Gateway Control Protocol (MGCP) Version 1.0 References Referenced by |
Informational | informatively references | |
RFC 3525 |
Gateway Control Protocol Version 1 References Referenced by |
Historic | informatively references | |
RFC 4240 |
Basic Network Media Services with SIP References Referenced by |
Informational | informatively references |