draft-ietf-i2rs-yang-l2-network-topology-01.txt   draft-ietf-i2rs-yang-l2-network-topology-02.txt 
Network Working Group J. Dong Network Working Group J. Dong
Internet-Draft X. Wei Internet-Draft X. Wei
Intended status: Standards Track Huawei Technologies Intended status: Standards Track Huawei Technologies
Expires: January 7, 2016 July 6, 2015 Expires: June 24, 2016 December 22, 2015
A YANG Data Model for Layer-2 Network Topologies A YANG Data Model for Layer-2 Network Topologies
draft-ietf-i2rs-yang-l2-network-topology-01 draft-ietf-i2rs-yang-l2-network-topology-02
Abstract Abstract
This document defines a YANG data model for Layer 2 network This document defines a YANG data model for Layer 2 network
topologies. topologies.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
skipping to change at page 1, line 37 skipping to change at page 1, line 37
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 7, 2016. This Internet-Draft will expire on June 24, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Layer-2 Topology Model . . . . . . . . . . . . . . . . . . . 2 2. Layer 2 Topology Model . . . . . . . . . . . . . . . . . . . 2
3. Layer-2 Topology Yang Module . . . . . . . . . . . . . . . . 6 3. Layer-2 Topology Yang Module . . . . . . . . . . . . . . . . 6
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
5. Security Considerations . . . . . . . . . . . . . . . . . . . 18 5. Security Considerations . . . . . . . . . . . . . . . . . . . 18
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.1. Normative References . . . . . . . . . . . . . . . . . . 18 7.1. Normative References . . . . . . . . . . . . . . . . . . 18
7.2. Informative References . . . . . . . . . . . . . . . . . 18 7.2. Informative References . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction 1. Introduction
[I-D.ietf-i2rs-yang-network-topo] defines the Yang [RFC6020] [I-D.ietf-i2rs-yang-network-topo] defines the Yang [RFC6020]
[RFC6021] data models of the abstract (generic) network and network [RFC6991] [I-D.ietf-netmod-rfc6020bis]data models of the abstract
topology. Such models can be augmented with technology-specific (generic) network and network topology. Such models can be augmented
details to build more specific topology models. with technology-specific details to build more specific topology
models.
This document defines the Yang data model for Layer 2 network This document defines the Yang data model for Layer 2 network
topologies by augmenting the generic network and network topology topologies by augmenting the generic network and network topology
data models with L2 specific topology attributes. data models with L2 specific topology attributes.
2. Layer-2 Topology Model 2. Layer 2 Topology Model
The Layer 2 network topology model is designed to be generic and The Layer 2 network topology model is designed to be generic and
applicable to Layer 2 networks built with different L2 technologies. applicable to Layer 2 networks built with different L2 technologies.
The Layer 2 topology model applies the generic network and network The Layer 2 topology model applies the generic network and network
topology models to Layer 2 network topologies, and augments the topology models to Layer 2 network topologies, and augments the
generic models with information specific in Layer 2 networks. The generic models with information specific in Layer 2 networks. The
relationship between the Layer 2 topology model and the generic relationship between the Layer 2 topology model and the generic
network and network topology model is shown in the figure below: network and network topology model is shown in the figure below:
+---------------------+ +---------------------+
| ietf-network | | ietf-network |
+----------^----------+ +----------^----------+
| |
| |
+---------------------+ +---------------------+
|ietf-network-topology| |ietf-network-topology|
+----------^----------+ +----------^----------+
| |
| |
+----------^----------+ +----------^----------+
| ietf-l2-topology | | ietf-l2-topology |
+---------------------+ +---------------------+
Figure 1. L2-topology model structure Figure 1. L2-topology model structure
In order to represent a Layer 2 network topology, the generic network In order to represent a Layer 2 network topology, the generic network
and topology models are augmented with Layer-2 specific information, and topology models are augmented with Layer-2 specific information,
such as the identifiers, descriptions, attributes and states of the such as the identifiers, descriptions, attributes and states of the
Layer-2 networks, nodes, links and termination points. Some of the Layer-2 networks, nodes, links and termination points. Some of the
information may be collected via Link Layer Discovery Protocl (LLDP) information may be collected via Link Layer Discovery Protocl (LLDP)
or other Layer-2 protocols, and some of them may be locally or other Layer-2 protocols, and some of them may be locally
configured. configured.
The structure of "ietf-l2-topology" data model is depicted in the The structure of "ietf-l2-topology" data model is depicted in the
following diagram. Brackets enclose list keys, "rw" means following diagram. Brackets enclose list keys, "rw" means
configuration data, "ro" means operational state data, "?" designates configuration data, "ro" means operational state data, "?" designates
optional nodes, "*" designates nodes that can have multiple optional nodes, "*" designates nodes that can have multiple
instances. instances.
module: ietf-l2-topology module: ietf-l2-topology
augment /nw:network/nw:network-types: augment /nw:networks/nw:network/nw:network-types:
+--rw l2-network! +--rw l2-network!
augment /nw:network: augment /nw:networks/nw:network:
+--rw l2-network-attributes +--rw l2-network-attributes
+--rw name? string +--rw name? string
+--rw flag* flag-type +--rw flag* flag-type
augment /nw:network/nw:node: augment /nw:networks/nw:network/nw:node:
+--rw l2-node-attributes +--rw l2-node-attributes
+--rw name? string +--rw name? string
+--rw description? string +--rw description? string
+--rw management-address* inet:ip-address +--rw management-address* inet:ip-address
+--rw management-vid? vlan {VLAN}? +--rw management-vid? vlan {VLAN}?
+--rw nick-name* trill-nickname {TRILL}? +--rw nick-name* trill-nickname {TRILL}?
+--rw flag* flag-type +--rw flag* flag-type
augment /nw:network/nt:link: augment /nw:networks/nw:network/nt:link:
+--rw l2-link-attributes +--rw l2-link-attributes
+--rw name? string +--rw name? string
+--rw flag* flag-type +--rw flag* flag-type
+--rw rate? decimal64 +--rw rate? decimal64
+--rw delay? uint32 +--rw delay? uint32
+--rw srlg* uint32 +--rw srlg* uint32
augment /nw:network/nw:node/nt:termination-point: augment /nw:networks/nw:network/nw:node/nt:termination-point:
+--rw l2-termination-point-attributes +--rw l2-termination-point-attributes
+--rw description? string +--rw description? string
+--rw maximum-frame-size? uint32 +--rw maximum-frame-size? uint32
+--rw (l2-termination-point-type)? +--rw (l2-termination-point-type)?
| +--:(ethernet)
| | +--rw mac-address? yang:mac-address
| | +--rw eth-encapsulation? identityref
| | +--rw port-vlan-id? vlan {VLAN}?
| | +--rw vlan-id-name* [vlan-id] {VLAN}?
| | +--rw vlan-id vlan
| | +--rw vlan-name? string
| +--:(legacy)
| +--rw encapsulation? identityref
+--ro tp-state? enumeration
notifications:
+---n l2-node-event
| +--ro event-type? l2-network-event-type
| +--ro network-ref? -> /nw:networks/network/network-id
| +--ro node-ref? -> /nw:networks/network[nw:network-id = current()/../network-ref]/node/node-id
| +--ro l2-network!
| +--ro l2-node-attributes
| +--ro name? string
| +--ro description? string
| +--ro management-address* inet:ip-address
| +--ro management-vid? vlan {VLAN}?
| +--ro nick-name* trill-nickname {TRILL}?
| +--ro flag* flag-type
+---n l2-link-event
| +--ro event-type? l2-network-event-type
| +--ro network-ref? -> /nw:networks/network/network-id
| +--ro link-ref? -> /nw:networks/network[nw:network-id = current()/../network-ref]/nt:link/link-id
| +--ro l2-network!
| +--ro l2-link-attributes
| +--ro name? string
| +--ro flag* flag-type
| +--ro rate? decimal64
| +--ro delay? uint32
| +--ro srlg* uint32
+---n l2-termination-point-event
+--ro event-type? l2-network-event-type
+--ro network-ref? -> /nw:networks/network/network-id
+--ro node-ref? -> /nw:networks/network[nw:network-id = current()/../network-ref]/node/node-id
+--ro tp-ref? -> /nw:networks/network[nw:network-id = current()/../network-ref]/node[nw:node-id = current()/../node-ref]/nt:termination-point/tp-id
+--ro l2-network!
+--ro l2-termination-point-attributes
+--ro description? string
+--ro maximum-frame-size? uint32
+--ro (l2-termination-point-type)?
| +--:(ethernet) | +--:(ethernet)
| | +--rw mac-address? yang:mac-address | | +--ro mac-address? yang:mac-address
| | +--rw eth-encapsulation? identityref | | +--ro eth-encapsulation? identityref
| | +--rw port-vlan-id? vlan {VLAN}? | | +--ro port-vlan-id? vlan {VLAN}?
| | +--rw vlan-id-name* [vlan-id] {VLAN}? | | +--ro vlan-id-name* [vlan-id] {VLAN}?
| | +--rw vlan-id vlan | | +--ro vlan-id vlan
| | +--rw vlan-name? string | | +--ro vlan-name? string
| +--:(legacy) | +--:(legacy)
| +--rw encapsulation? identityref | +--ro encapsulation? identityref
+--ro tp-state? enumeration +--ro tp-state? enumeration
notifications:
+---n l2-node-event
| +--ro event-type? l2-network-event-type
| +--ro network-ref? leafref
| +--ro node-ref? leafref
| +--ro l2-network!
| +--ro l2-node-attributes
| +--ro name? string
| +--ro description? string
| +--ro management-address* inet:ip-prefix
| +--ro management-vid? vlan {VLAN}?
| +--ro nick-name* trill-nickname {TRILL}?
| +--ro flag* flag-type
+---n l2-link-event
| +--ro event-type? l2-network-event-type
| +--ro network-ref? leafref
| +--ro link-ref? leafref
| +--ro l2-network!
| +--ro l2-link-attributes
| +--ro name? string
| +--ro flag* flag-type
| +--ro rate? decimal64
| +--ro delay? uint32
| +--ro srlg* uint32
+---n l2-termination-point-event
+--ro event-type? l2-network-event-type
+--ro network-ref? leafref
+--ro node-ref? leafref
+--ro tp-ref? leafref
+--ro l2-network!
+--ro l2-termination-point-attributes
+--ro description? string
+--ro maximum-frame-size? uint32
+--ro (termination-point-type)?
| +--:(ethernet)
| | +--ro mac-address? yang:mac-address
| | +--ro eth-encapsulation? identityref
| | +--ro port-vlan-id? vlan {VLAN}?
| | +--ro vlan-id-name* [vlan-id] {VLAN}?
| | +--ro vlan-id vlan
| | +--ro vlan-name? string
| +--:(legacy)
| +--ro encapsulation? identityref
+--ro tp-state? enumeration
The L2-topology module augments the generic ietf-network and ietf- The L2-topology module augments the generic ietf-network and ietf-
network-topology modules as follows: network-topology modules as follows:
o A new network type "l2-network-type" is introduced. This is o A new network type "l2-network-type" is introduced. This is
represented by a container object, and is inserted under the represented by a container object, and is inserted under the
"network-types" container of the generic ietf-network module in "network-types" container of the generic ietf-network module in
[I-D.ietf-i2rs-yang-network-topo]. [I-D.ietf-i2rs-yang-network-topo].
o Additional network attributes are introduced in a grouping "l2- o Additional network attributes are introduced in a grouping "l2-
skipping to change at page 6, line 7 skipping to change at page 6, line 7
o Links in the ietf-network-topology module are augmented as well o Links in the ietf-network-topology module are augmented as well
with a set of Layer-2 parameters, allowing to associate a link with a set of Layer-2 parameters, allowing to associate a link
with a name, a set of Layer-2 link attributes and flags. with a name, a set of Layer-2 link attributes and flags.
o The optional L2 technology specific attributes are introduced in o The optional L2 technology specific attributes are introduced in
this module as Layer-2 features. this module as Layer-2 features.
3. Layer-2 Topology Yang Module 3. Layer-2 Topology Yang Module
<CODE BEGINS> <CODE BEGINS> file "ietf-l2-topology@2015-12-22.yang"
file "ietf-l2-topology@2015-06-23.yang"
module ietf-l2-topology { module ietf-l2-topology {
yang-version 1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-l2-topology"; namespace "urn:ietf:params:xml:ns:yang:ietf-l2-topology";
prefix "l2t"; prefix "l2t";
import ietf-network { import ietf-network {
prefix "nw"; prefix "nw";
} }
import ietf-network-topology { import ietf-network-topology {
prefix "nt"; prefix "nt";
} }
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
} }
import ietf-yang-types { import ietf-yang-types {
prefix "yang"; prefix "yang";
} }
organization "TBD"; organization
contact "I-D Editor: jie.dong@huawei.com"; "IETF I2RS (Interface to the Routing System) Working Group";
contact
"WG Web: <http://tools.ietf.org/wg/i2rs/>
WG List: <mailto:i2rs@ietf.org>
WG Chair: Susan Hares
<mailto:shares@ndzh.com>
WG Chair: Jeffrey Haas
<mailto:jhaas@pfrc.org>
Editor: Jie Dong
<mailto:jie.dong@huawei.com>
Editor: Xiugang Wei
<mailto:weixiugang@huawei.com>";
description description
"This module defines a basic model for "This module defines a basic model for
the layer-2 topology of a network"; the layer-2 topology of a network";
revision "2015-06-23" { revision "2015-12-22" {
description "Initial revision"; description "Initial revision";
reference "draft-ietf-i2rs-l2-network-topology-01"; reference "draft-ietf-i2rs-l2-network-topology-02";
} }
/* /*
* Typedefs * Typedefs
*/ */
typedef vlan { typedef vlan {
type uint16 { type uint16 {
range "0..4095"; range "0..4095";
} }
skipping to change at page 14, line 44 skipping to change at page 15, line 9
} // grouping l2-termination-point-attributes } // grouping l2-termination-point-attributes
/*** grouping of network/node/link/tp leaf-refs ***/ /*** grouping of network/node/link/tp leaf-refs ***/
grouping network-ref { grouping network-ref {
description description
"Grouping for an absolute reference to a network topology "Grouping for an absolute reference to a network topology
instance."; instance.";
leaf network-ref { leaf network-ref {
type leafref { type leafref {
path "/nw:network/nw:network-id"; path "/nw:networks/nw:network/nw:network-id";
} }
description description
"An absolute reference to a network topology instance."; "An absolute reference to a network topology instance.";
} }
} }
grouping link-ref { grouping link-ref {
description description
"Grouping for an absolute reference to a link instance."; "Grouping for an absolute reference to a link instance.";
uses network-ref; uses network-ref;
leaf link-ref { leaf link-ref {
type leafref { type leafref {
path "/nw:network" path "/nw:networks/nw:network"
+"[nw:network-id = current()/../network-ref]" +"[nw:network-id = current()/../network-ref]"
+"/nt:link/nt:link-id"; +"/nt:link/nt:link-id";
} }
description description
"An absolute reference to a link instance."; "An absolute reference to a link instance.";
} }
} }
grouping node-ref { grouping node-ref {
description description
"Grouping for an absolute reference to a node instance."; "Grouping for an absolute reference to a node instance.";
uses network-ref; uses network-ref;
leaf node-ref { leaf node-ref {
type leafref { type leafref {
path "/nw:network" path "/nw:networks/nw:network"
+"[nw:network-id = current()/../network-ref]" +"[nw:network-id = current()/../network-ref]"
+"/nw:node/nw:node-id"; +"/nw:node/nw:node-id";
} }
description description
"An absolute reference to a node instance."; "An absolute reference to a node instance.";
} }
} }
grouping tp-ref { grouping tp-ref {
description description
"Grouping for an absolute reference to a termination point."; "Grouping for an absolute reference to a termination point.";
uses node-ref; uses node-ref;
leaf tp-ref { leaf tp-ref {
type leafref { type leafref {
path "/nw:network" path "/nw:networks/nw:network"
+"[nw:network-id = current()/../network-ref]" +"[nw:network-id = current()/../network-ref]"
+"/nw:node[nw:node-id = current()/../node-ref]" +"/nw:node[nw:node-id = current()/../node-ref]"
+"/nt:termination-point/nt:tp-id"; +"/nt:termination-point/nt:tp-id";
} }
description description
"Grouping for an absolute reference to a TP."; "Grouping for an absolute reference to a TP.";
} }
} }
/* /*
* Data nodes * Data nodes
*/ */
augment "/nw:network/nw:network-types" {
augment "/nw:networks/nw:network/nw:network-types" {
description description
"Introduce new network type for L2 topology"; "Introduce new network type for L2 topology";
uses l2-network-type; uses l2-network-type;
} }
augment "/nw:network" { augment "/nw:networks/nw:network" {
when "nw:network-types/l2-network" { when "/nw:networks/nw:network/nw:network-types/l2-network" {
description description
"Augmentation parameters apply only for networks "Augmentation parameters apply only for networks
with L2 topology"; with L2 topology";
} }
description description
"Configuration parameters for the L2 network "Configuration parameters for the L2 network
as a whole"; as a whole";
uses l2-network-attributes; uses l2-network-attributes;
} }
augment "/nw:network/nw:node" { augment "/nw:networks/nw:network/nw:node" {
when "../nw:network-types/l2-network" { when "/nw:networks/nw:network/nw:network-types/l2-network" {
description description
"Augmentation parameters apply only for networks "Augmentation parameters apply only for networks
with L2 topology"; with L2 topology";
} }
description description
"Configuration parameters for L2 at the node "Configuration parameters for L2 at the node
level"; level";
uses l2-node-attributes; uses l2-node-attributes;
} }
augment "/nw:network/nt:link" { augment "/nw:networks/nw:network/nt:link" {
when "/nw:network/nw:network-types/l2-network" { when "/nw:networks/nw:network/nw:network-types/l2-network" {
description description
"Augmentation parameters apply only for networks "Augmentation parameters apply only for networks
with L2 topology"; with L2 topology";
} }
description "Augment L2 topology link information"; description "Augment L2 topology link information";
uses l2-link-attributes; uses l2-link-attributes;
} }
augment "/nw:network/nw:node/nt:termination-point" { augment "/nw:networks/nw:network/nw:node/nt:termination-point" {
when "/nw:network/nw:network-types/l2-network" { when "/nw:networks/nw:network/nw:network-types/l2-network" {
description description
"Augmentation parameters apply only for networks "Augmentation parameters apply only for networks
with L2 topology"; with L2 topology";
} }
description description
"Augment L2 topology termination point configuration"; "Augment L2 topology termination point configuration";
uses l2-termination-point-attributes; uses l2-termination-point-attributes;
} }
/* /*
* Notifications * Notifications
*/ */
notification l2-node-event { notification l2-node-event {
description "Notification event for L2 node"; description "Notification event for L2 node";
leaf event-type { leaf event-type {
skipping to change at page 17, line 50 skipping to change at page 18, line 17
uses tp-ref; uses tp-ref;
uses l2-network-type; uses l2-network-type;
uses l2-termination-point-attributes; uses l2-termination-point-attributes;
} }
} // module l2-topology } // module l2-topology
<CODE ENDS> <CODE ENDS>
4. IANA Considerations 4. IANA Considerations
TBD This document makes no request of IANA.
Note to RFC Editor: this section may be removed on publication as an
RFC.
5. Security Considerations 5. Security Considerations
The transport protocol used for sending the topology data MUST The transport protocol used for sending the topology data MUST
support authentication and SHOULD support encryption. The data-model support authentication and SHOULD support encryption. The data-model
by itself does not create any security implications. by itself does not create any security implications.
6. Acknowledgements 6. Acknowledgements
The authors would like to acknowledge the comments and suggestions The authors would like to acknowledge the comments and suggestions
received from Susan Hares, Alia Atlas, Juergen Schoenwaelder, Mach received from Susan Hares, Alia Atlas, Juergen Schoenwaelder, Mach
Chen, Alexander Clemm and Sriganesh Kini. Chen, Alexander Clemm and Sriganesh Kini.
7. References 7. References
7.1. Normative References 7.1. Normative References
[I-D.ietf-i2rs-yang-network-topo] [I-D.ietf-i2rs-yang-network-topo]
Clemm, A., Medved, J., Varga, R., Tkacik, T., Bahadur, N., Clemm, A., Medved, J., Varga, R., Tkacik, T., Bahadur, N.,
and H. Ananthakrishnan, "A Data Model for Network and H. Ananthakrishnan, "A Data Model for Network
Topologies", draft-ietf-i2rs-yang-network-topo-01 (work in Topologies", draft-ietf-i2rs-yang-network-topo-02 (work in
progress), June 2015. progress), December 2015.
[I-D.ietf-netmod-rfc6020bis]
Bjorklund, M., "The YANG 1.1 Data Modeling Language",
draft-ietf-netmod-rfc6020bis-09 (work in progress),
December 2015.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010. DOI 10.17487/RFC6020, October 2010,
<http://www.rfc-editor.org/info/rfc6020>.
[RFC6021] Schoenwaelder, J., "Common YANG Data Types", RFC 6021, [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
October 2010. RFC 6991, DOI 10.17487/RFC6991, July 2013,
<http://www.rfc-editor.org/info/rfc6991>.
7.2. Informative References 7.2. Informative References
[I-D.amante-i2rs-topology-use-cases] [I-D.amante-i2rs-topology-use-cases]
Medved, J., Previdi, S., Lopez, V., and S. Amante, Medved, J., Previdi, S., Lopez, V., and S. Amante,
"Topology API Use Cases", draft-amante-i2rs-topology-use- "Topology API Use Cases", draft-amante-i2rs-topology-use-
cases-01 (work in progress), October 2013. cases-01 (work in progress), October 2013.
[I-D.medved-i2rs-topology-requirements] [I-D.medved-i2rs-topology-requirements]
Medved, J., Previdi, S., Gredler, H., Nadeau, T., and S. Medved, J., Previdi, S., Gredler, H., Nadeau, T., and S.
 End of changes. 33 change blocks. 
131 lines changed or deleted 158 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/