References from draft-ietf-appsawg-xdash
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 |
References Referenced by |
informatively references | ||
BCP 14 |
References Referenced by |
normatively references | ||
BCP 26 |
References Referenced by |
informatively references | ||
BCP 35 |
References Referenced by |
informatively references | ||
BCP 43 |
References Referenced by |
informatively references | ||
BCP 47 |
References Referenced by |
informatively references | ||
BCP 66 |
References Referenced by |
informatively references | ||
BCP 67 |
References Referenced by |
informatively references | ||
BCP 82 |
References Referenced by |
informatively references | ||
BCP 9 |
References Referenced by |
informatively references | ||
BCP 90 |
References Referenced by |
informatively references | ||
RFC 1123 |
Requirements for Internet Hosts - Application and Support
References Referenced by |
Internet Standard | informatively references | |
RFC 1154 |
Encoding header field for internet messages
References Referenced by |
Experimental | informatively references | |
RFC 2045 |
Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
References Referenced by |
Draft Standard | informatively references | |
RFC 2046 |
Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
References Referenced by |
Draft Standard | informatively references | |
RFC 2047 |
MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text
References Referenced by |
Draft Standard | informatively references | |
RFC 2068 |
Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by |
Proposed Standard | informatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 2426 |
vCard MIME Directory Profile
References Referenced by |
Proposed Standard | informatively references | |
RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by |
Draft Standard | informatively references | |
RFC 2822 |
Internet Message Format
References Referenced by |
Proposed Standard | informatively references | |
RFC 2939 |
Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types
References Referenced by |
Best Current Practice | informatively references | |
RFC 3406 |
Uniform Resource Names (URN) Namespace Definition Mechanisms
References Referenced by |
Best Current Practice | informatively references | |
RFC 3427 |
Change Process for the Session Initiation Protocol (SIP)
References Referenced by |
Best Current Practice | informatively references | |
RFC 3864 |
Registration Procedures for Message Header Fields
References Referenced by |
Best Current Practice | informatively references | |
RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | informatively references | |
RFC 4122 |
A Universally Unique IDentifier (UUID) URN Namespace
References Referenced by |
Proposed Standard | informatively references | |
RFC 4288 |
Media Type Specifications and Registration Procedures
References Referenced by |
Best Current Practice | informatively references | |
RFC 4395 |
Guidelines and Registration Procedures for New URI Schemes
References Referenced by |
Best Current Practice | informatively references | |
RFC 4512 |
Lightweight Directory Access Protocol (LDAP): Directory Information Models
References Referenced by |
Proposed Standard | informatively references | |
RFC 4566 |
SDP: Session Description Protocol
References Referenced by |
Proposed Standard | informatively references | |
RFC 5064 |
The Archived-At Message Header Field
References Referenced by |
Proposed Standard | informatively references | |
RFC 5451 |
Message Header Field for Indicating Message Authentication Status
References Referenced by |
Proposed Standard | informatively references | |
RFC 5545 |
Internet Calendaring and Scheduling Core Object Specification (iCalendar)
References Referenced by |
Proposed Standard | informatively references | |
RFC 5646 |
Tags for Identifying Languages
References Referenced by |
Best Current Practice | informatively references | |
RFC 5727 |
Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area
References Referenced by |
Best Current Practice | informatively references | |
RFC 5741 |
RFC Streams, Headers, and Boilerplates
References Referenced by |
Informational | Possible Reference | Possible Downref |
RFC 691 |
One more try on the FTP
References Referenced by |
Unknown | informatively references | |
RFC 737 |
FTP extension: XSEN
References Referenced by |
Unknown | informatively references | |
RFC 743 |
FTP extension: XRSQ/XRCP
References Referenced by |
Unknown | informatively references | |
RFC 775 |
Directory oriented FTP commands
References Referenced by |
Unknown | informatively references | |
RFC 822 |
STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
References Referenced by |
Internet Standard | informatively references | |
STD 11 |
References Referenced by |
informatively references | ||
STD 3 |
References Referenced by |
informatively references | ||
STD 66 |
References Referenced by |
informatively references |