References from draft-algermissen-software-system-life-cycle-model
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 |
normatively references | ||
BCP 14 |
References Referenced by |
normatively references | ||
RFC 1034 |
Domain names - concepts and facilities
References Referenced by |
Internet Standard | normatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 2181 |
Clarifications to the DNS Specification
References Referenced by |
Proposed Standard | normatively references | |
RFC 2782 |
A DNS RR for specifying the location of services (DNS SRV)
References Referenced by |
Proposed Standard | informatively references | |
RFC 3232 |
Assigned Numbers: RFC 1700 is Replaced by an On-line Database
References Referenced by |
Informational | normatively references | |
RFC 6763 |
DNS-Based Service Discovery
References Referenced by |
Proposed Standard | informatively references | |
RFC 6838 |
Media Type Specifications and Registration Procedures
References Referenced by |
Best Current Practice | normatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
RFC 8259 |
The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by |
Internet Standard | normatively references | |
STD 13 |
References Referenced by |
normatively references | ||
STD 90 |
References Referenced by |
normatively references |