The YANG Package Statement
draft-bierman-netmod-yang-package-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Andy Bierman | ||
| Last updated | 2016-01-07 (Latest revision 2015-07-06) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-bierman-netmod-yang-package-00.txt
Abstract
This document describes mechanisms for defining a conceptual collection of YANG modules and protocol capability URIs, called a YANG package. Typically, modules with high cohesion that are designed to be used together to manage a service or product feature are included in a YANG package. The purpose of the package is not constrained by this document. For example, a YANG package may describe conformance requirements or simply describe the modules and protocol capabilities implemented in a specific platform.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)