References from draft-jholland-taps-api-yang

This is an experimental product. 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.

Reference type help

Document Title Status Type Downref
BCP 14 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
BCP 215 YANG Tree Diagrams
Refs Ref'd by
Best Current Practice normatively references
BCP 216 Guidelines for Authors and Reviewers of Documents Containing YANG Data Models
Refs Ref'd by
Best Current Practice normatively references
draft-ietf-taps-arch An Architecture for Transport Services
Refs Ref'd by
Proposed Standard normatively references
draft-ietf-taps-interface An Abstract Application Layer Interface to Transport Services
Refs Ref'd by
Proposed Standard normatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
RFC 6991 Common YANG Data Types
Refs Ref'd by
Proposed Standard normatively references
RFC 7950 The YANG 1.1 Data Modeling Language
Refs Ref'd by
Proposed Standard normatively references
RFC 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Refs Ref'd by
Best Current Practice normatively references
RFC 8340 YANG Tree Diagrams
Refs Ref'd by
Best Current Practice normatively references
RFC 8343 A YANG Data Model for Interface Management
Refs Ref'd by
Proposed Standard normatively references
RFC 8407 Guidelines for Authors and Reviewers of Documents Containing YANG Data Models
Refs Ref'd by
Best Current Practice normatively references