References from rfc7035
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 26 |
Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by |
Best Current Practice | normatively references | |
BCP 73 |
An IETF URN Sub-namespace for Registered Protocol Parameters References Referenced by |
Best Current Practice | normatively references | |
RFC 1014 |
XDR: External Data Representation standard References Referenced by |
Unknown | normatively references | Possible Downref |
RFC 2046 |
Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types References Referenced by |
Draft Standard | normatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1 References Referenced by |
Draft Standard | normatively references | |
RFC 2818 |
HTTP Over TLS References Referenced by |
Informational | normatively references | Downref |
RFC 3553 |
An IETF URN Sub-namespace for Registered Protocol Parameters References Referenced by |
Best Current Practice | normatively references | |
RFC 3688 |
The IETF XML Registry References Referenced by |
Best Current Practice | normatively references | |
RFC 3863 |
Presence Information Data Format (PIDF) References Referenced by |
Proposed Standard | informatively references | |
RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax References Referenced by |
Internet Standard | normatively references | |
RFC 4119 |
A Presence-based GEOPRIV Location Object Format References Referenced by |
Proposed Standard | normatively references | |
RFC 4479 |
A Data Model for Presence References Referenced by |
Proposed Standard | informatively references | |
RFC 4776 |
Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information References Referenced by |
Proposed Standard | normatively references | |
RFC 5139 |
Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO) References Referenced by |
Proposed Standard | normatively references | |
RFC 5226 |
Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by |
Best Current Practice | normatively references | |
RFC 5246 |
The Transport Layer Security (TLS) Protocol Version 1.2 References Referenced by |
Proposed Standard | normatively references | |
RFC 5491 |
GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and Recommendations References Referenced by |
Proposed Standard | normatively references | |
RFC 5741 |
RFC Streams, Headers, and Boilerplates References Referenced by |
Informational | Possible Reference | Possible Downref |
RFC 5962 |
Dynamic Extensions to the Presence Information Data Format Location Object (PIDF-LO) References Referenced by |
Proposed Standard | normatively references | |
RFC 6225 |
Dynamic Host Configuration Protocol Options for Coordinate-Based Location Configuration Information References Referenced by |
Proposed Standard | normatively references | |
RFC 6848 |
Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF-LO) References Referenced by |
Proposed Standard | normatively references | |
STD 66 |
Uniform Resource Identifier (URI): Generic Syntax References Referenced by |
Internet Standard | normatively references |