References from draft-jholland-taps-api-yang
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 |
References Referenced by |
normatively references | ||
| BCP 215 |
References Referenced by |
normatively references | ||
| BCP 216 |
References Referenced by |
normatively references | ||
| draft-ietf-taps-arch |
Architecture and Requirements for Transport Services
References Referenced by |
Proposed Standard | normatively references | |
| draft-ietf-taps-interface |
An Abstract Application Layer Interface to Transport Services
References Referenced by |
Proposed Standard | normatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 6991 |
Common YANG Data Types
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7950 |
The YANG 1.1 Data Modeling Language
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8340 |
YANG Tree Diagrams
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8343 |
A YANG Data Model for Interface Management
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8407 |
Guidelines for Authors and Reviewers of Documents Containing YANG Data Models
References Referenced by |
Best Current Practice | normatively references |