References from draft-atarashi-ngo-consider-architecture
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 |
Reference | ||
| BCP 78 |
References Referenced by |
Reference | ||
| draft-chisholm-netconf-model |
Using XML Schema to define NETCONF Content
References Referenced by |
Reference | ||
| draft-ietf-isms-tmsm |
Transport Subsystem for the Simple Network Management Protocol (SNMP)
References Referenced by |
Draft Standard | Reference | |
| draft-ietf-netconf-beep |
Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)
References Referenced by |
Proposed Standard | Reference | |
| draft-ietf-netconf-notification |
NETCONF Event Notifications
References Referenced by |
Proposed Standard | Reference | |
| draft-ietf-netconf-prot |
NETCONF Configuration Protocol
References Referenced by |
Proposed Standard | Reference | |
| draft-ietf-netconf-soap |
Using NETCONF over the Simple Object Access Protocol (SOAP)
References Referenced by |
Proposed Standard | Reference | |
| draft-ietf-netconf-ssh |
Using the NETCONF Configuration Protocol over Secure SHell (SSH)
References Referenced by |
Proposed Standard | Reference | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | Possible Reference | |
| RFC 2818 |
HTTP Over TLS
References Referenced by |
Informational | Reference | |
| RFC 3075 |
XML-Signature Syntax and Processing
References Referenced by |
Proposed Standard | Reference | |
| STD 62 |
References Referenced by |
Reference |