draft-ietf-i2rs-yang-l2-network-topology-05.txt   draft-ietf-i2rs-yang-l2-network-topology-06.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 Q. Wu
Expires: December 31, 2018 June 29, 2018 Expires: April 25, 2019 Huawei Technologies
October 22, 2018
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-05 draft-ietf-i2rs-yang-l2-network-topology-06
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 38
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 December 31, 2018. This Internet-Draft will expire on April 25, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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
skipping to change at page 2, line 15 skipping to change at page 2, line 16
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 . . . . . . . . . . . . . . . . 5 3. Layer 2 Topology Yang Module . . . . . . . . . . . . . . . . 5
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
5. Security Considerations . . . . . . . . . . . . . . . . . . . 17 5. Security Considerations . . . . . . . . . . . . . . . . . . . 17
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 19
7.1. Normative References . . . . . . . . . . . . . . . . . . 19 7.1. Normative References . . . . . . . . . . . . . . . . . . 19
7.2. Informative References . . . . . . . . . . . . . . . . . 19 7.2. Informative References . . . . . . . . . . . . . . . . . 20
Appendix A. Companion YANG model for non-NMDA compliant Appendix A. Companion YANG model for non-NMDA compliant
implementations . . . . . . . . . . . . . . . . . . 20 implementations . . . . . . . . . . . . . . . . . . 20
Appendix B. An Example . . . . . . . . . . . . . . . . . . . . . 24 Appendix B. An Example . . . . . . . . . . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29
1. Introduction 1. Introduction
[RFC8345] defines the YANG [RFC6020] [RFC7950] data models of the [RFC8345] defines the YANG [RFC6020] [RFC7950] data models of the
abstract (generic) network and network topology. Such models can be abstract (generic) network and network topology. Such models can be
augmented with technology-specific details to build more specific augmented with technology-specific details to build more specific
topology models. 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
skipping to change at page 3, line 46 skipping to change at page 3, line 46
+--rw l2-network-attributes +--rw l2-network-attributes
+--rw name? string +--rw name? string
+--rw flag* l2-flag-type +--rw flag* l2-flag-type
augment /nw:networks/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 sys-mac-address? yang:mac-address +--rw sys-mac-address? yang:mac-address
+--rw management-vid? vlan {VLAN}? +--rw management-vid? vlan {VLAN}?
+--rw nick-name* trill-nickname {TRILL}? +--rw flag* node-flag-type
+--rw vn-id* vni {VXLAN}?
+--rw flag* l2-flag-type
augment /nw:networks/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* l2-flag-type +--rw flag* link-flag-type
+--rw rate? decimal64 +--rw rate? decimal64
+--rw delay? uint32 +--rw delay? uint32
+--rw srlg* uint32 +--rw srlg* uint32
augment /nw:networks/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) | +--:(ethernet)
| | +--rw mac-address? yang:mac-address | | +--rw mac-address? yang:mac-address
skipping to change at page 5, line 31 skipping to change at page 5, line 28
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> file "ietf-l2-topology@2018-06-29.yang" <CODE BEGINS> file "ietf-l2-topology@2018-10-18.yang"
module ietf-l2-topology { module ietf-l2-topology {
yang-version 1.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 {
skipping to change at page 6, line 33 skipping to change at page 6, line 30
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of This version of this YANG module is part of
draft-ietf-i2rs-yang-l2-network-topo-04; draft-ietf-i2rs-yang-l2-network-topo-06;
see the RFC itself for full legal notices."; see the RFC itself for full legal notices.";
revision "2018-06-29" { revision "2018-10-18" {
description "Initial revision"; description "Initial revision";
reference "draft-ietf-i2rs-l2-network-topology-05"; reference "draft-ietf-i2rs-l2-network-topology-06";
} }
/* /*
* Typedefs * Typedefs
*/ */
typedef vlan { typedef vlan {
type uint16 { type uint16 {
range "0..4095"; range "0..4095";
} }
description "VLAN ID"; description "VLAN ID";
reference "IEEE 802.1Q";
} }
typedef trill-nickname { typedef trill-nickname {
type uint16; type uint16;
description "TRILL Nickname"; description "TRILL Nickname";
reference "RFC 6326";
} }
typedef vni { typedef vni {
type uint32 { type uint32 {
range "1..16777215"; range "1..16777215";
} }
description "VxLAN Network Identifier"; description "VxLAN Network Identifier";
reference "RFC 7348";
} }
typedef l2-flag-type { typedef l2-flag-type {
type identityref { type identityref {
base "flag-identity"; base "flag-identity";
} }
description "Base type for l2 flags"; description "Base type for l2 flags";
} }
typedef node-flag-type {
type identityref {
base "flag-identity";
}
description "Node flag attributes";
}
typedef link-flag-type {
type identityref {
base "flag-identity";
}
description "Link flag attributes";
}
typedef l2-network-event-type { typedef l2-network-event-type {
type enumeration { type enumeration {
enum "add" { enum "add" {
value 0; value 0;
description "An L2 node or link or termination-point description "An L2 node or link or termination-point
has been added"; has been added";
} }
enum "remove" { enum "remove" {
value 1; value 1;
skipping to change at page 8, line 11 skipping to change at page 8, line 23
feature VLAN { feature VLAN {
description description
"Indicates that the system supports the "Indicates that the system supports the
vlan functions"; vlan functions";
} }
feature QinQ { feature QinQ {
description description
"Indicates that the system supports the "Indicates that the system supports the
qinq functions"; qinq functions";
reference "IEEE 802.1ad";
} }
feature PBB { feature PBB {
description description
"Indicates that the device supports the "Indicates that the device supports the
provider-backbone-bridging functions"; provider-backbone-bridging functions";
reference "IEEE 802.1ah";
} }
feature VPLS { feature VPLS {
description description
"Indicates that the device supports the "Indicates that the device supports the
VPLS functions"; VPLS functions";
reference "RFC 4761, RFC 4762"; reference "RFC 4761, RFC 4762";
} }
feature TRILL { feature TRILL {
skipping to change at page 11, line 51 skipping to change at page 12, line 19
} }
leaf sys-mac-address { leaf sys-mac-address {
type yang:mac-address; type yang:mac-address;
description "System MAC-address"; description "System MAC-address";
} }
leaf management-vid { leaf management-vid {
if-feature VLAN; if-feature VLAN;
type vlan; type vlan;
description "System management VID"; description "System management VID";
} }
leaf-list nick-name {
if-feature TRILL;
type trill-nickname;
description "Nickname of the RBridge";
}
leaf-list vn-id {
if-feature VXLAN;
type vni;
description "VNI of the VxLAN";
}
leaf-list flag { leaf-list flag {
type l2-flag-type; type node-flag-type;
description "Node operational flags"; description "Node operational flags";
} }
} }
} // grouping l2-node-attributes } // grouping l2-node-attributes
grouping l2-link-attributes { grouping l2-link-attributes {
description "L2 link attributes"; description "L2 link attributes";
container l2-link-attributes { container l2-link-attributes {
description "Containing L2 link attributes"; description "Containing L2 link attributes";
leaf name { leaf name {
type string; type string;
description "Link name"; description "Link name";
} }
leaf-list flag { leaf-list flag {
type l2-flag-type; type link-flag-type;
description "Link flags"; description "Link flags";
} }
leaf rate { leaf rate {
type decimal64 { type decimal64 {
fraction-digits 2; fraction-digits 2;
} }
description "Link rate"; description "Link rate";
} }
leaf delay { leaf delay {
type uint32; type uint32;
description "Link delay in microseconds"; description "Link delay in microseconds";
} }
leaf-list srlg { leaf-list srlg {
type uint32; type uint32;
description description
"List of Shared Risk Link Groups "List of Shared Risk Link Groups
this link belongs to."; this link belongs to.";
reference "RFC 4202";
} }
} }
} // grouping l2-link-attributes } // grouping l2-link-attributes
grouping l2-termination-point-attributes { grouping l2-termination-point-attributes {
description "L2 termination point attributes"; description "L2 termination point attributes";
container l2-termination-point-attributes { container l2-termination-point-attributes {
description "Containing L2 TP attributes"; description "Containing L2 TP attributes";
leaf description { leaf description {
type string; type string;
description "Port description"; description "Port description";
} }
leaf maximum-frame-size { leaf maximum-frame-size {
skipping to change at page 14, line 23 skipping to change at page 14, line 29
description "Interface Layer 2 address"; description "Interface Layer 2 address";
} }
leaf encapsulation { leaf encapsulation {
type identityref { type identityref {
base encapsulation-type; base encapsulation-type;
} }
description description
"Encapsulation type of this termination point."; "Encapsulation type of this termination point.";
} }
} //case legacy } //case legacy such as atm, ppp, hdlc,etc.
} //choice termination-point-type } //choice termination-point-type
leaf tp-state { leaf tp-state {
type enumeration { type enumeration {
enum in-use { enum in-use {
value 0; value 0;
description description
"the termination point is in forwarding state"; "the termination point is in forwarding state";
} }
skipping to change at page 17, line 27 skipping to change at page 17, line 33
URI: urn:ietf:params:xml:ns:yang:ietf-l2-topology-state URI: urn:ietf:params:xml:ns:yang:ietf-l2-topology-state
Registrant Contact: The IESG. Registrant Contact: The IESG.
XML: N/A; the requested URI is an XML namespace. XML: N/A; the requested URI is an XML namespace.
This document registers the following YANG modules in the "YANG This document registers the following YANG modules in the "YANG
Module Names" registry [RFC6020]: Module Names" registry [RFC6020]:
Name: ietf-l2-topology Name: ietf-l2-topology
Namespace: urn:ietf:params:xml:ns:yang:ietf-l2-topology Namespace: urn:ietf:params:xml:ns:yang:ietf-l2-topology
Prefix: l2t Prefix: l2t
Reference: draft-ietf-i2rs-yang-l2-network-topology-05.txt (RFC form) Reference: draft-ietf-i2rs-yang-l2-network-topology-06.txt (RFC form)
Name: ietf-l2-topology-state Name: ietf-l2-topology-state
Namespace: urn:ietf:params:xml:ns:yang:ietf-l2-topology-state Namespace: urn:ietf:params:xml:ns:yang:ietf-l2-topology-state
Prefix: l2t-s Prefix: l2t-s
Reference: draft-ietf-i2rs-yang-l2-network-topology-05.txt (RFC form) Reference: draft-ietf-i2rs-yang-l2-network-topology-06.txt (RFC form)
5. Security Considerations 5. Security Considerations
The YANG module defined in this document is designed to be accessed The YANG module defined in this document is designed to be accessed
via network management protocols such as NETCONF [RFC6241] or via network management protocols such as NETCONF [RFC6241] or
RESTCONF [RFC8040] . The lowest NETCONF layer is the secure transport RESTCONF [RFC8040] . The lowest NETCONF layer is the secure transport
layer, and the mandatory-to-implement secure transport is Secure layer, and the mandatory-to-implement secure transport is Secure
Shell (SSH) [RFC6242]. The lowest RESTCONF layer is HTTPS, and the Shell (SSH) [RFC6242]. The lowest RESTCONF layer is HTTPS, and the
mandatory-to-implement secure transport is TLS [RFC5246]. mandatory-to-implement secure transport is TLS [RFC5246].
skipping to change at page 21, line 8 skipping to change at page 21, line 18
state and ietf-network-topology-state (instead of ietf-network and state and ietf-network-topology-state (instead of ietf-network and
ietf-network-topology) and all its data nodes are non-configurable. ietf-network-topology) and all its data nodes are non-configurable.
The companion module ietf-l2-topology SHOULD NOT be supported by The companion module ietf-l2-topology SHOULD NOT be supported by
implementations that support NMDA. It is for this reason that this implementations that support NMDA. It is for this reason that this
module is defined in the Appendix. module is defined in the Appendix.
As the structure of this modules mirrors that of its underlying As the structure of this modules mirrors that of its underlying
modules, the YANG tree is not depicted separately. modules, the YANG tree is not depicted separately.
<CODE BEGINS> file "ietf-l2-topology-state@2018-06-29.yang" <CODE BEGINS> file "ietf-l2-topology-state@2018-10-18.yang"
module ietf-l2-topology-state { module ietf-l2-topology-state {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-l2-topology-state"; namespace "urn:ietf:params:xml:ns:yang:ietf-l2-topology-state";
prefix "l2t-s"; prefix "l2t-s";
import ietf-network-state { import ietf-network-state {
prefix "nw-s"; prefix "nw-s";
} }
import ietf-network-topology-state { import ietf-network-topology-state {
skipping to change at page 22, line 5 skipping to change at page 22, line 16
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of This version of this YANG module is part of
draft-ietf-i2rs-yang-l2-network-topo-05; draft-ietf-i2rs-yang-l2-network-topo-05;
see the RFC itself for full legal notices."; see the RFC itself for full legal notices.";
revision "2018-06-29" { revision "2018-10-18" {
description "Initial revision"; description "Initial revision";
reference "draft-ietf-i2rs-l2-network-topology-05"; reference "draft-ietf-i2rs-l2-network-topology-06";
} }
/* /*
* Data nodes * Data nodes
*/ */
augment "/nw-s:networks/nw-s:network/nw-s:network-types" { augment "/nw-s:networks/nw-s:network/nw-s:network-types" {
description description
"Introduce new network type for L2 topology"; "Introduce new network type for L2 topology";
uses l2t:l2-network-type; uses l2t:l2-network-type;
skipping to change at page 26, line 46 skipping to change at page 27, line 20
} }
}, },
{ {
"tp-id": "3-2-1", "tp-id": "3-2-1",
"ietf-l2-topology: "ietf-l2-topology:
l2-termination-point-attributes": { l2-termination-point-attributes": {
"mac-address": "A3:B2:C3:D4:E5:F1" "mac-address": "A3:B2:C3:D4:E5:F1"
} }
} }
], ],
"ietf-l3-unicast-topology:l3-node-attributes": { "ietf-l2-topology:l2-node-attributes": {
"management-address": ["10.1.1.3"] "management-address": ["10.1.1.3"]
} }
} }
], ],
"ietf-network-topology:link": [ "ietf-network-topology:link": [
{ {
"link-id": "D1,1-2-1,D2,2-1-1", "link-id": "D1,1-2-1,D2,2-1-1",
"source": { "source": {
"source-node": "D1", "source-node": "D1",
"source-tp": "1-2-1" "source-tp": "1-2-1"
skipping to change at line 1340 skipping to change at page 29, line 37
Email: jie.dong@huawei.com Email: jie.dong@huawei.com
Xiugang Wei Xiugang Wei
Huawei Technologies Huawei Technologies
Huawei Campus, No. 156 Beiqing Rd. Huawei Campus, No. 156 Beiqing Rd.
Beijing 100095 Beijing 100095
China China
Email: weixiugang@huawei.com Email: weixiugang@huawei.com
Qin Wu
Huawei Technologies
101 Software Avenue, Yuhua District
Nanjing 210012
China
Email: bill.wu@huawei.com
 End of changes. 31 change blocks. 
34 lines changed or deleted 42 lines changed or added

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