draft-ietf-i2rs-yang-dc-fabric-network-topology-11.txt   draft-ietf-i2rs-yang-dc-fabric-network-topology-12.txt 
I2RS Working Group Y. Zhuang I2RS Working Group Y. Zhuang
Internet-Draft D. Shi Internet-Draft D. Shi
Intended status: Standards Track Huawei Intended status: Standards Track Huawei
Expires: February 2, 2019 R. Gu Expires: May 25, 2019 R. Gu
China Mobile China Mobile
H. Ananthakrishnan H. Ananthakrishnan
Netflix Netflix
August 1, 2018 November 21, 2018
A YANG Data Model for Fabric Topology in Data Center Networks A YANG Data Model for Fabric Topology in Data Center Networks
draft-ietf-i2rs-yang-dc-fabric-network-topology-11 draft-ietf-i2rs-yang-dc-fabric-network-topology-12
Abstract Abstract
This document defines a YANG data model for fabric topology in Data This document defines a YANG data model for fabric topology in Data
Center Networks and it represents only one possible view of the dc Center Networks and it represents one possible view of the data
fabric. center fabric. This document focuses on the data model only and does
not endorse any kind of network design that could be based on the
abovementioned model.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 February 2, 2019. This Internet-Draft will expire on May 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 26 skipping to change at page 2, line 28
3.2.2. Fabric node extension . . . . . . . . . . . . . . . . 5 3.2.2. Fabric node extension . . . . . . . . . . . . . . . . 5
3.2.3. Fabric termination-point extension . . . . . . . . . 6 3.2.3. Fabric termination-point extension . . . . . . . . . 6
4. Fabric YANG Module . . . . . . . . . . . . . . . . . . . . . 7 4. Fabric YANG Module . . . . . . . . . . . . . . . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
6. Security Considerations . . . . . . . . . . . . . . . . . . . 21 6. Security Considerations . . . . . . . . . . . . . . . . . . . 21
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 22
8.1. Normative References . . . . . . . . . . . . . . . . . . 22 8.1. Normative References . . . . . . . . . . . . . . . . . . 22
8.2. Informative References . . . . . . . . . . . . . . . . . 23 8.2. Informative References . . . . . . . . . . . . . . . . . 23
Appendix A. Non NMDA -state modules . . . . . . . . . . . . . . 24 Appendix A. Non NMDA -state modules . . . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 30 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 31
1. Introduction 1. Introduction
Normally, a data center (DC) network is composed of single or A data center (DC) network can be composed of single or multiple
multiple fabrics which are also known as PODs (Points Of Delivery). fabrics which are also known as PODs (Points Of Delivery). These
These fabrics may be heterogeneous due to implementation of different fabrics may be heterogeneous due to implementation of different
technologies when a DC network is upgraded or new techniques and technologies when a DC network is upgraded or new techniques and
features are rolled out. For example, Fabric A may use VXLAN while features are rolled out. For example, Fabric A may use VXLAN while
Fabric B may use VLAN within a DC network. Likewise, an existing Fabric B may use VLAN within a DC network. Likewise, an existing
fabric may use VXLAN while a new fabric, for example a fabric fabric may use VXLAN while a new fabric, for example a fabric
introduced for DC upgrade and expansion, may implement a technique introduced for DC upgrade and expansion, may implement a technique
discussed in NVO3 WG, such as Geneve [I-D. draft-ietf-nvo3-geneve]. discussed in NVO3 WG, such as Geneve [I-D. draft-ietf-nvo3-geneve].
The configuration and management of such DC networks with The configuration and management of such DC networks with
heterogeneous fabrics will result in considerable complexity, heterogeneous fabrics could result in considerable complexity.
requiring a fair amount of sophistication.
Luckily, for a DC network, a fabric can be considered as an atomic For a DC network, a fabric can be considered as an atomic structure
structure for management purposes. From this point of view, the for management purposes. From this point of view, the management of
management of the DC network can be decomposed into a set of tasks to the DC network can be decomposed into a set of tasks to manage each
manage each fabric separately, as well as the fabric fabric separately, as well as the fabric interconnections. The
interconnections. This way, the overall management task becomes very advantage of this method is to make the overall management tasks
flexible and makes it easy to expand and adopt to DC networks that flexible and easy to extend in the future.
evolve over time.
As a basis for DC fabric management, this document defines a YANG As a basis for DC fabric management, this document defines a YANG
data model [RFC6020][RFC7950] for a possible view of the fabric-based data model [RFC6020][RFC7950] for a possible view of the fabric-based
data center topology. To do so, it augments the generic network and data center topology. To do so, it augments the generic network and
network topology data models defined in [RFC8345] with information network topology data models defined in [RFC8345] with information
that is specific to Data Center fabric networks. that is specific to data center fabric networks.
The model defines the generic configuration and operational state for The model defines the generic configuration and operational state for
a fabric-based network topology, which can subsequently be extended a fabric-based network topology, which can subsequently be extended
by vendors with vendor-specific information as needed. The model can by vendors with vendor-specific information as needed. The model can
be used by a network controller to represent its view of the fabric be used by a network controller to represent its view of the fabric
topology that it controls and expose this view to network topology that it controls and expose this view to network
administrators or applications for DC network management. administrators or applications for DC network management.
Within the context of topology architecture defined in [RFC8345], Within the context of topology architecture defined in [RFC8345],
this model can also be treated as an application of the I2RS network this model can also be treated as an application of the I2RS network
topology model [RFC8345] in the scenario of Data center network topology model [RFC8345] in the scenario of data center network
management. It can also act as a service topology when mapping management. It can also act as a service topology when mapping
network elements at the fabric layer to elements of other topologies, network elements at the fabric layer to elements of other topologies,
such as L3 topologies as defined in [RFC8346]. such as L3 topologies as defined in [RFC8346].
By using the fabric topology model defined in this document, people By using the fabric topology model defined in this document, people
can treat a fabric as a holistic entity and focus on characteristics can treat a fabric as a holistic entity and focus on characteristics
of a fabric (such as encapsulation type, gateway type, etc.) as well of a fabric (such as encapsulation type, gateway type.) as well as
as its connections to other fabrics while putting the underlay its connections to other fabrics while putting the underlay topology
topology aside. As such, clients can consume the topology aside. As such, clients can consume the topology information at the
information at the fabric level with no need to be aware of the fabric level with no need to be aware of the entire set of links and
entire set of links and nodes in the corresponding underlay networks. nodes in the corresponding underlay networks. A fabric topology can
A fabric topology can be configured by a network administrator using be configured by a network administrator using the controller by
the controller by adding physical devices and links into a fabric. adding physical devices and links into a fabric. Alternatively,
Alternatively, fabric topology can be learned from the underlay fabric topology can be learned from the underlay network
network infrastructure. infrastructure.
2. Definitions and Acronyms 2. Definitions and Acronyms
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
2.1. Terminology 2.1. Terminology
skipping to change at page 4, line 43 skipping to change at page 4, line 43
From the perspective of resource management and service provisioning From the perspective of resource management and service provisioning
for a data center network, the fabric topology model augments the for a data center network, the fabric topology model augments the
basic network topology model with definitions and features specific basic network topology model with definitions and features specific
to a DC fabric, to provide common configuration and operations for to a DC fabric, to provide common configuration and operations for
heterogeneous fabrics. heterogeneous fabrics.
3.2. Fabric Topology Model 3.2. Fabric Topology Model
The fabric topology model module is designed to be generic and can be The fabric topology model module is designed to be generic and can be
applied to data center fabrics built with different technologies, applied to data center fabrics built with different technologies,
such as VLAN, VXLAN etc. The main purpose of this module is to such as VLAN, VXLAN. The main purpose of this module is to configure
configure and manage fabrics and their connections. It provides a and manage fabrics and their connections. It provides a fabric-based
fabric-based topology view for data center applications. topology view for data center applications.
3.2.1. Fabric Topology 3.2.1. Fabric Topology
In the fabric topology module, a fabric is modeled as a node of a In the fabric topology module, a fabric is modeled as a node of a
network, as such the fabric-based data center network consists of a network, as such the fabric-based data center network consists of a
set of fabric nodes and their connections. The following depicts a set of fabric nodes and their connections. The following depicts a
snippet of the definitions to show the main structure of the model. snippet of the definitions to show the main structure of the model.
The notation syntax follows [RFC8340]. The notation syntax follows [RFC8340].
module: ietf-dc-fabric-topology module: ietf-dc-fabric-topology
skipping to change at page 5, line 27 skipping to change at page 5, line 27
+--... +--...
augment /nw:networks/nw:network/nw:node/nt:termination-point: augment /nw:networks/nw:network/nw:node/nt:termination-point:
+--ro fport-attributes +--ro fport-attributes
+--ro name? string +--ro name? string
+--ro role? fabric-port-role +--ro role? fabric-port-role
+--ro type? fabric-port-type +--ro type? fabric-port-type
The fabric topology module augments the generic ietf-network and The fabric topology module augments the generic ietf-network and
ietf-network-topology modules as follows: ietf-network-topology modules as follows:
o A new topology type "ietf-dc-fabric-topology" is introduced and o A new topology type "ietf-dc-fabric-topology" is defined and added
added under the "network-types" container of the ietf-network under the "network-types" container of the ietf-network module.
module.
o Fabric is defined as a node under the network/node container. A o Fabric is defined as a node under the network/node container. A
new container "fabric-attributes" is defined to carry attributes new container "fabric-attributes" is defined to carry attributes
for a fabric such as gateway mode, fabric types, involved device for a fabric such as gateway mode, fabric types, involved device
nodes, and links. nodes, and links.
o Termination points (in network topology module) are augmented with o Termination points (in network topology module) are augmented with
fabric port attributes defined in a container. The "termination- fabric port attributes defined in a container. The "termination-
point" here is used to represent a fabric "port" that provides point" here is used to represent a fabric "port" that provides
connections to other nodes, such as an internal device, another connections to other nodes, such as an internal device, another
fabric externally, or end hosts. fabric externally, or end hosts.
Details of the fabric node and the fabric termination point extension Details of the fabric node and the fabric termination point extension
will be explained in the following sections. will be explained in the following sections.
3.2.2. Fabric node extension 3.2.2. Fabric node extension
As an atomic network, a fabric itself is composed of a set of network As an atomic network (that is a set of nodes and links which composes
elements i.e. devices, and related links. The configuration of a a POD and also supports a single overlay/underlay instance), a fabric
fabric is contained under the "fabric-attributes" container depicted itself is composed of a set of network elements i.e. devices, and
as follows. The notation syntax follows [RFC8340]. related links. The configuration of a fabric is contained under the
"fabric-attributes" container depicted as follows. The notation
syntax follows [RFC8340].
+--rw fabric-attributes +--rw fabric-attributes
+--rw fabric-id? fabrictypes:fabric-id +--rw fabric-id? fabrictypes:fabric-id
+--rw name? string +--rw name? string
+--rw type? fabrictype:underlay-network-type +--rw type? fabrictype:underlay-network-type
+--rw vni-capacity +--rw vni-capacity
| +--rw min? int32 | +--rw min? int32
| +--rw max? int32 | +--rw max? int32
+--rw description? string +--rw description? string
+--rw options +--rw options
skipping to change at page 7, line 23 skipping to change at page 7, line 27
+--ro role? fabric-port-role +--ro role? fabric-port-role
+--ro type? fabric-port-type +--ro type? fabric-port-type
+--ro device-port? tp-ref +--ro device-port? tp-ref
+--ro (tunnel-option)? +--ro (tunnel-option)?
It augments the termination points (in network topology module) with It augments the termination points (in network topology module) with
fabric port attributes defined in a container. fabric port attributes defined in a container.
New nodes are defined for fabric ports including fabric name, role of New nodes are defined for fabric ports including fabric name, role of
the port within the fabric (internal port, external port to outside the port within the fabric (internal port, external port to outside
network, access port to end hosts), port type (l2 interface, l3 network, access port to end hosts), port type (L2 interface, L3
interface, etc). By defining the device-port as a tp-ref, a fabric interface). By defining the device-port as a tp-ref, a fabric port
port can be mapped to a device node in the underlay network. can be mapped to a device node in the underlay network.
Also, a new container for tunnel-options is introduced to present the Also, a new container for tunnel-options is introduced to present the
tunnel configuration on a port. tunnel configuration on a port.
The termination point information is learned from the underlay The termination point information is learned from the underlay
networks, not configured by the fabric topology layer. networks, not configured by the fabric topology layer.
4. Fabric YANG Module 4. Fabric YANG Module
This module imports typedefs from [RFC8345], and it references This module imports typedefs from [RFC8345], and it references
[RFC7348] and [RFC8344]. [RFC7348] and [RFC8344].
<CODE BEGINS> file "ietf-dc-fabric-types@2018-04-16.yang" <CODE BEGINS> file "ietf-dc-fabric-types@2018-11-08.yang"
module ietf-dc-fabric-types { module ietf-dc-fabric-types {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-dc-fabric-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-dc-fabric-types";
prefix fabrictypes; prefix fabrictypes;
import ietf-network { import ietf-network {
prefix nw; prefix nw;
reference reference
"RFC 8345:A Data Model for Network Topologies"; "RFC 8345:A Data Model for Network Topologies";
} }
organization organization
"IETF I2RS (Interface to the Routing System) Working Group"; "IETF I2RS (Interface to the Routing System) Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/i2rs/ > "WG Web: <http://tools.ietf.org/wg/i2rs/ >
WG List: <mailto:i2rs@ietf.org> WG List: <mailto:i2rs@ietf.org>
Editor: Yan Zhuang Editor: Yan Zhuang
<mailto:zhuangyan.zhuang@huawei.com> <mailto:zhuangyan.zhuang@huawei.com>
skipping to change at page 8, line 36 skipping to change at page 8, line 40
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
(https://trustee.ietf.org/license-info). (https://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-dc-fabric-network-topology; draft-ietf-i2rs-yang-dc-fabric-network-topology;
see the RFC itself for full legal notices. see the RFC itself for full legal notices.
NOTE TO RFC EDITOR: Please replace above reference to NOTE TO RFC EDITOR: Please replace above reference to
draft-ietf-i2rs-yang-dc-fabric-network-topology-09 with RFC draft-ietf-i2rs-yang-dc-fabric-network-topology-12 with RFC
number when published (i.e. RFC xxxx)."; number when published (i.e. RFC xxxx).";
revision "2018-04-16"{ revision "2018-11-08"{
description description
"Initial revision. "Initial revision.
NOTE TO RFC EDITOR: NOTE TO RFC EDITOR:
Please replace the following reference to Please replace the following reference to
draft-ietf-i2rs-yang-dc-fabric-network-topology-09 draft-ietf-i2rs-yang-dc-fabric-network-topology-12
with RFC number when published (i.e. RFC xxxx)."; with RFC number when published (i.e. RFC xxxx).";
reference reference
"draft-ietf-i2rs-yang-dc-fabric-network-topology-09"; "draft-ietf-i2rs-yang-dc-fabric-network-topology-12";
} }
identity fabric-type { identity fabric-type {
description description
"Base type for fabric networks"; "Base type for fabric networks";
} }
identity vxlan-fabric { identity vxlan-fabric {
base fabric-type; base fabric-type;
description description
"Vxlan fabric"; "VXLAN fabric";
} }
identity vlan-fabric { identity vlan-fabric {
base fabric-type; base fabric-type;
description description
"Vlan fabric"; "VLAN fabric";
} }
identity trill-fabric { identity trill-fabric {
base fabric-type; base fabric-type;
description "Trill fabric"; description "TRILL fabric";
} }
identity port-type { identity port-type {
description description
"Base type for fabric port"; "Base type for fabric port";
} }
identity eth { identity eth {
base port-type; base port-type;
description "ETH"; description "Ethernet";
} }
identity serial { identity serial {
base port-type; base port-type;
description "Serial"; description "Serial";
} }
identity bandwidth { identity bandwidth {
description "Base for bandwidth"; description "Base for bandwidth";
} }
identity bw-1M { identity bw-1M {
base bandwidth; base bandwidth;
description "1M"; description "1M";
} }
identity bw-10M { identity bw-10M {
base bandwidth; base bandwidth;
description "10M"; description "10Mbps";
} }
identity bw-100M { identity bw-100M {
base bandwidth; base bandwidth;
description "100M"; description "100Mbps";
} }
identity bw-1G { identity bw-1G {
base bandwidth; base bandwidth;
description "1G"; description "1Gbps";
} }
identity bw-10G { identity bw-10G {
base bandwidth; base bandwidth;
description "10G"; description "10Gbps";
} }
identity bw-25G {
base bandwidth;
description "25Gbps";
}
identity bw-40G { identity bw-40G {
base bandwidth; base bandwidth;
description "40G"; description "40Gbps";
} }
identity bw-100G{ identity bw-100G{
base bandwidth; base bandwidth;
description "100G"; description "100Gbps";
}
identity bw-400G {
base bandwidth;
description "400Gbps";
} }
identity device-role { identity device-role {
description "Base for the device role in a fabric."; description "Base for the device role in a fabric.";
} }
identity spine { identity spine {
base device-role; base device-role;
description "This is a spine node in a fabric."; description "This is a spine node in a fabric.";
} }
identity leaf { identity leaf {
base device-role; base device-role;
description "This is a leaf node in a fabric. "; description "This is a leaf node in a fabric. ";
skipping to change at page 11, line 16 skipping to change at page 11, line 27
identity service-capability { identity service-capability {
description "Base for the service of the fabric "; description "Base for the service of the fabric ";
} }
identity ip-mapping { identity ip-mapping {
base service-capability; base service-capability;
description "NAT."; description "NAT.";
} }
identity acl-redirect { identity acl-redirect {
base service-capability; base service-capability;
description "Acl redirect, which can provide SFC function."; description "ACL redirect, which can provide SFC function.";
} }
identity dynamic-route-exchange { identity dynamic-route-exchange {
base service-capability; base service-capability;
description "Dynamic route exchange."; description "Dynamic route exchange.";
} }
/* /*
* Typedefs * Typedefs
*/ */
typedef fabric-id { typedef fabric-id {
type nw:node-id; type nw:node-id;
description description
"An identifier for a fabric in a topology. "An identifier for a fabric in a topology.
This identifier can be generated when composing a fabric. This identifier can be generated when composing a fabric.
The composition of a fabric can be achived by defining a The composition of a fabric can be achieved by defining a
RPC, which is left for vendor specific implementation RPC, which is left for vendor specific implementation
and not provided in this model."; and not provided in this model.";
} }
typedef service-capabilities { typedef service-capabilities {
type identityref { type identityref {
base service-capability; base service-capability;
} }
description description
"Service capability of the fabric"; "Service capability of the fabric";
skipping to change at page 12, line 29 skipping to change at page 12, line 40
typedef link-ref { typedef link-ref {
type instance-identifier; type instance-identifier;
description "A reference to a link in topology"; description "A reference to a link in topology";
} }
typedef underlay-network-type { typedef underlay-network-type {
type identityref { type identityref {
base fabric-type; base fabric-type;
} }
description "The type of physical network that implements description "The type of physical network that implements
this fabric.Examples are vlan, and trill."; this fabric.Examples are VLAN, and TRILL.";
} }
typedef device-role { typedef device-role {
type identityref { type identityref {
base device-role; base device-role;
} }
description "Role of the device node."; description "Role of the device node.";
} }
typedef fabric-port-role { typedef fabric-port-role {
type identityref { type identityref {
base fabric-port-role; base fabric-port-role;
skipping to change at page 13, line 42 skipping to change at page 14, line 5
description "The device port it mapped to."; description "The device port it mapped to.";
} }
choice tunnel-option { choice tunnel-option {
description "Tunnel options to connect two fabrics. description "Tunnel options to connect two fabrics.
It could be L2 Tunnel or L3 Tunnel."; It could be L2 Tunnel or L3 Tunnel.";
} }
} }
} }
<CODE ENDS> <CODE ENDS>
<CODE BEGINS> file "ietf-dc-fabric-topology@2018-04-16.yang" <CODE BEGINS> file "ietf-dc-fabric-topology@2018-11-08.yang"
module ietf-dc-fabric-topology { module ietf-dc-fabric-topology {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-dc-fabric-topology"; namespace "urn:ietf:params:xml:ns:yang:ietf-dc-fabric-topology";
prefix fabric; prefix fabric;
import ietf-network { import ietf-network {
prefix nw; prefix nw;
reference
"RFC 8345:A Data Model for Network Topologies";
}
import ietf-network-topology { reference
prefix nt; "RFC 8345:A Data Model for Network Topologies";
}
reference import ietf-network-topology {
"RFC 8345:A Data Model for Network Topologies"; prefix nt;
}
import ietf-dc-fabric-types { reference
prefix fabrictypes; "RFC 8345:A Data Model for Network Topologies";
}
reference import ietf-dc-fabric-types {
"draft-ietf-i2rs-yang-dc-fabric-network-topology-09 prefix fabrictypes;
NOTE TO RFC EDITOR:
(1) Please replace above reference to
draft-ietf-i2rs-yang-dc-fabric-network-topology-09
with RFC number when publised (i.e. RFC xxxx).
(2) Please replace the data in the revision statement
with the data of publication when published.";
}
organization reference
"IETF I2RS (Interface to the Routing System) Working Group"; "draft-ietf-i2rs-yang-dc-fabric-network-topology-12
NOTE TO RFC EDITOR:
(1) Please replace above reference to
draft-ietf-i2rs-yang-dc-fabric-network-topology-12
with RFC number when publised (i.e. RFC xxxx).
(2) Please replace the data in the revision statement
with the data of publication when published.";
}
contact organization
"WG Web: <http://tools.ietf.org/wg/i2rs/ > "IETF I2RS (Interface to the Routing System) Working Group";
WG List: <mailto:i2rs@ietf.org>
Editor: Yan Zhuang contact
<mailto:zhuangyan.zhuang@huawei.com> "WG Web: <http://tools.ietf.org/wg/i2rs/ >
WG List: <mailto:i2rs@ietf.org>
Editor: Danian Shi Editor: Yan Zhuang
<mailto:shidanian@huawei.com>"; <mailto:zhuangyan.zhuang@huawei.com>
description Editor: Danian Shi
"This module contains a collection of YANG definitions for <mailto:shidanian@huawei.com>";
Fabric.
Copyright (c) 2018 IETF Trust and the persons identified as description
authors of the code. All rights reserved. "This module contains a collection of YANG definitions for
Fabric.
Redistribution and use in source and binary forms, with or Copyright (c) 2018 IETF Trust and the persons identified as
without modification, is permitted pursuant to, and subject authors of the code. All rights reserved.
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(https://trustee.ietf.org/license-info).
This version of this YANG module is part of Redistribution and use in source and binary forms, with or
draft-ietf-i2rs-yang-dc-fabric-network-topology; without modification, is permitted pursuant to, and subject
see the RFC itself for full legal notices. to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(https://trustee.ietf.org/license-info).
NOTE TO RFC EDITOR: Please replace above reference to This version of this YANG module is part of
draft-ietf-i2rs-yang-dc-fabric-network-topology-09 with RFC draft-ietf-i2rs-yang-dc-fabric-network-topology;
number when published (i.e. RFC xxxx)."; see the RFC itself for full legal notices.
revision "2018-04-16"{ NOTE TO RFC EDITOR: Please replace above reference to
description draft-ietf-i2rs-yang-dc-fabric-network-topology-12 with RFC
"Initial revision. number when published (i.e. RFC xxxx).";
NOTE TO RFC EDITOR: Please replace the following
reference to draft-ietf-i2rs-yang-dc-fabric-network
-topology-09 with RFC number when published
(i.e. RFC xxxx).";
reference
"draft-ietf-i2rs-yang-dc-fabric-network-topology-09";
}
/*identity fabric-context { revision "2018-11-08"{
description description
"Identity of fabric context"; "Initial revision.
}*/ NOTE TO RFC EDITOR: Please replace the following
reference to draft-ietf-i2rs-yang-dc-fabric-network
-topology-12 with RFC number when published
(i.e. RFC xxxx).";
reference
"draft-ietf-i2rs-yang-dc-fabric-network-topology-12";
}
//grouping statements //grouping statements
grouping fabric-network-type { grouping fabric-network-type {
description "Identify the topology type to be fabric."; description "Identify the topology type to be fabric.";
container fabric-network { container fabric-network {
presence "indicates fabric Network"; presence "indicates fabric Network";
description description
"The presence of the container node indicates "The presence of the container node indicates
fabric Topology"; fabric Topology";
}
} }
}
grouping fabric-options { grouping fabric-options {
description "Options for a fabric"; description "Options for a fabric";
leaf gateway-mode {
type enumeration {
enum centralized {
description "The Fabric uses centralized
gateway, in which gateway is deployed on SPINE
node.";
}
enum distributed {
description "The Fabric uses distributed
gateway, in which gateway is deployed on LEAF
node.";
}
}
default "distributed";
description "Gateway mode of the fabric";
}
leaf gateway-mode { leaf traffic-behavior {
type enumeration { type enumeration {
enum centralized { enum normal {
description "The Fabric uses centerilized description "Normal means no policy is needed
gateway,in which gateway is deployed on SPINE for all traffic";
node."; }
enum policy-driven {
description "Policy driven means policy is
needed for the traffic otherwise the traffic
will be discard.";
}
}
default "normal";
description "Traffic behavior of the fabric";
}
} leaf-list capability-supported {
enum distributed { type fabrictypes:service-capabilities;
description "The Fabric uses distributed description
gateway, in which gateway is deployed on LEAF "It provides a list of supported services of the
node."; fabric. The service-capabilities is defined as
} identity-ref. Users can define more services
} by defining new identities.";
default "distributed"; }
description "Gateway mode of the fabric"; }
}
leaf traffic-behavior { grouping device-attributes {
type enumeration { description "device attributes";
enum normal { leaf device-ref {
description "Normal means no policy is needed type fabrictypes:node-ref;
for all traffic"; description
} "The device that the fabric includes which refers
enum policy-driven { to a node in another topology.";
description "Policy driven means policy is }
needed for the traffic otherwise the traffic leaf-list role {
will be discard."; type fabrictypes:device-role;
} default fabrictypes:leaf;
} description
default "normal"; "It is a list of device-role to represent the roles
description "Traffic behavior of the fabric"; that a device plays within a POD, such as SPINE,
} LEAF, Border, or Border-Leaf.
The device-role is defined as identity-ref. If more
than 2 stage is used for a POD, users can
define new identities for the device-role.";
}
}
leaf-list capability-supported { grouping link-attributes {
type fabrictypes:service-capabilities; description "Link attributes";
description leaf link-ref {
"It provides a list of supported services of the type fabrictypes:link-ref;
fabric. The service-capabilities is defined as description
identity-ref. Developers can define more services "The link that the fabric includes which refers to
by defining new identies."; a link in another topology.";
} }
} }
grouping device-attributes { grouping port-attributes {
description "device attributes"; description "Port attributes";
leaf device-ref { leaf port-ref {
type fabrictypes:node-ref; type fabrictypes:tp-ref;
description description
"The device that the fabric includes which refers "The port that the fabric includes which refers to
to a node in another topolopogy."; a termination-point in another topology.";
} }
leaf-list role { leaf port-type {
type fabrictypes:device-role; type fabrictypes:port-type;
default fabrictypes:leaf; description
description "Port type is defined as identity-ref. If current
"It is a list of devce-role to represent the roles types includes ethernet or serial. If more types
that a device plays within a PoD, such as SPINE, are needed, developers can define new identities.";
LEAF, Border, or Border-Leaf. }
The device-role is defined as identity-ref. If more leaf bandwidth {
than 2 stage is used for a PoD, developers can type fabrictypes:bandwidth;
define new identities for the device-role."; description
} "Bandwidth of the port. It is defined as identity-ref.
} If more speeds are introduced, developers can define
new identities for them. Current speeds include 1M, 10M,
100M, 1G, 10G, 25G, 40G, 100G and 400G.";
grouping link-attributes { }
description "Link attributes"; }
leaf link-ref {
type fabrictypes:link-ref;
description
"The link that the fabric includes which refers to
a link in another topology.";
}
}
grouping port-attributes { grouping fabric-attributes {
description "Port attributes"; description "Attributes of a fabric";
leaf port-ref {
type fabrictypes:tp-ref;
description
"The port that the fabric includes which refers to
a termination-point in another topology.";
}
leaf port-type {
type fabrictypes:port-type;
description
"Port type is defined as identiy-ref. If current
types includes ethernet or serial. If more types
are needed, developers can define new identities.";
}
leaf bandwidth {
type fabrictypes:bandwidth;
description
"Bandwidth of the port. It is defined as identity-ref.
If more speeds are introduced, developers can define
new identies for them. Current speeds include 1M, 10M,
100M, 1G, 10G, 40G and 100G.";
}
}
grouping fabric-attributes { leaf fabric-id {
description "Attributes of a fabric"; type fabrictypes:fabric-id;
leaf fabric-id { description
type fabrictypes:fabric-id; "An identifier for a fabric in a topology.
This identifier can be generated when composing a fabric.
The composition of a fabric can be achieved by defining a
RPC, which is left for vendor specific implementation and
not provided in this model.";
}
leaf name {
type string;
description description
"An identifier for a fabric in a topology. "Name of the fabric";
This identifier can be generated when composing a fabric. }
The composition of a fabric can be achived by defining a
RPC, which is left for vendor specific implementation and
not provided in this model.";
}
leaf name { leaf type {
type string; type fabrictypes:underlay-network-type;
description description
"Name of the fabric"; "The type of physical network that implements this
} fabric.Examples are VLAN, and TRILL.";
}
leaf type { container vni-capacity {
type fabrictypes:underlay-network-type; description "The range of the VNI(VXLAN Network Identifier
description defined in RFC 7348)s that the POD uses.";
"The type of physical network that implements this
fabric.Examples are vlan, and trill.";
}
container vni-capacity { leaf min {
description "The range of the VNI(VXLAN Network Identifier type int32;
defined in RFC 7348)s that the PoD uses."; description
"The lower limit VNI.";
}
leaf min { leaf max {
type int32; type int32;
description description
"The lower limit Vni."; "The upper limit VNI.";
} }
}
leaf max { leaf description {
type int32; type string;
description description
"The upper limite Vni."; "Description of the fabric";
} }
}
leaf description { container options {
type string; description "Options of the fabric";
description uses fabric-options;
"Description of the fabric"; }
}
container options { list device-nodes {
description "Options of the fabric"; key device-ref;
uses fabric-options; description "Device nodes that are included in a fabric.";
} uses device-attributes;
}
list device-nodes { list device-links {
key device-ref; key link-ref;
description "Device nodes that include in a fabric."; description "Links that are included within a fabric.";
uses device-attributes; uses link-attributes;
} }
list device-links { list device-ports {
key link-ref; key port-ref;
description "Links that include within a fabric."; description "Ports that are included in the fabric.";
uses link-attributes; uses port-attributes;
} }
list device-ports { }
key port-ref;
description "Ports that include in the fabric.";
uses port-attributes;
}
} // augment statements
// augment statements augment "/nw:networks/nw:network/nw:network-types" {
description
"Introduce a new network type for Fabric-based topology";
augment "/nw:networks/nw:network/nw:network-types" { uses fabric-network-type;
description }
"Introduce new network type for Fabric-based topology";
uses fabric-network-type; augment "/nw:networks/nw:network/nw:node" {
when "/nw:networks/nw:network/nw:network-types/"
+"fabric:fabric-network"{
description
"Augmentation parameters apply only for networks
with fabric topology";
} }
description "Augmentation for fabric nodes created by
fabric topology.";
container fabric-attributes {
description
"Attributes for a fabric network";
augment "/nw:networks/nw:network/nw:node" { uses fabric-attributes;
when "/nw:networks/nw:network/nw:network-types/"
+"fabric:fabric-network"{
description
"Augmentation parameters apply only for networks
with fabric topology";
} }
description "Augmentation for fabric nodes created by }
fabric topology.";
container fabric-attributes {
description
"Attributes for a fabric network";
uses fabric-attributes;
}
augment "/nw:networks/nw:network/nw:node/nt:termination-point" {
when "/nw:networks/nw:network/nw:network-types/"
+"fabric:fabric-network" {
description
"Augmentation parameters apply only for networks
with fabric topology";
} }
description "Augmentation for port on fabric.";
augment "/nw:networks/nw:network/nw:node/nt:termination-point" { container fport-attributes {
when "/nw:networks/nw:network/nw:network-types/" config false;
+"fabric:fabric-network" { description
description "Attributes for fabric ports";
"Augmentation parameters apply only for networks uses fabrictypes:fabric-port;
with fabric topology";
} }
description "Augmentation for port on fabric."; }
}
container fport-attributes { <CODE ENDS>
config false;
description
"Attributes for fabric ports";
uses fabrictypes:fabric-port;
}
}
}
<CODE ENDS>
5. IANA Considerations 5. IANA Considerations
This document registers the following namespace URIs in the "IETF XML This document registers the following namespace URIs in the "IETF XML
Registry" [RFC3688]: Registry" [RFC3688]:
URI:urn:ietf:params:xml:ns:yang:ietf-dc-fabric-types URI:urn:ietf:params:xml:ns:yang:ietf-dc-fabric-types
Registrant Contact: The IESG. Registrant Contact: The IESG.
skipping to change at page 21, line 6 skipping to change at page 21, line 11
URI:urn:ietf:params:xml:ns:yang:ietf-dc-fabric-topology-state URI:urn:ietf:params:xml:ns:yang:ietf-dc-fabric-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]:
NOTE TO THE RFC EDITOR: In the list below, please replace references NOTE TO THE RFC EDITOR: In the list below, please replace references
to "draft-ietf-i2rs-yang-dc-fabric-network-topology-09 (RFC form)" to "draft-ietf-i2rs-yang-dc-fabric-network-topology-12 (RFC form)"
with RFC number when published (i.e. RFC xxxx). with RFC number when published (i.e. RFC xxxx).
Name: ietf-dc-fabric-types Name: ietf-dc-fabric-types
Namespace: urn:ietf:params:xml:ns:yang:ietf-dc-fabric-types Namespace: urn:ietf:params:xml:ns:yang:ietf-dc-fabric-types
Prefix: fabrictypes Prefix: fabrictypes
Reference: draft-ietf-i2rs-yang-dc-fabric-network-topology-09.txt Reference: draft-ietf-i2rs-yang-dc-fabric-network-topology-12.txt
(RFC form) (RFC form)
Name: ietf-dc-fabric-topology Name: ietf-dc-fabric-topology
Namespace: urn:ietf:params:xml:ns:yang:ietf-dc-fabric-topology Namespace: urn:ietf:params:xml:ns:yang:ietf-dc-fabric-topology
Prefix: fabric Prefix: fabric
Reference: draft-ietf-i2rs-yang-dc-fabric-network-topology-09.txt Reference: draft-ietf-i2rs-yang-dc-fabric-network-topology-12.txt
(RFC form) (RFC form)
Name: ietf-dc-fabric-topology-state Name: ietf-dc-fabric-topology-state
Namespace: urn:ietf:params:xml:ns:yang:ietf-dc-fabric-topology-state Namespace: urn:ietf:params:xml:ns:yang:ietf-dc-fabric-topology-state
Prefix: sfabric Prefix: sfabric
Reference: draft-ietf-i2rs-yang-dc-fabric-network-topology-09.txt Reference: draft-ietf-i2rs-yang-dc-fabric-network-topology-12.txt
(RFC form) (RFC form)
6. Security Considerations 6. 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 24, line 16 skipping to change at page 24, line 20
RFC 8344, March 2018, RFC 8344, March 2018,
<http://www.rfc-editor.org/info/rfc8344>. <http://www.rfc-editor.org/info/rfc8344>.
[RFC8346] Clemm, A., Medved, J., Tkacik, T., Liu, X., Bryskin, I., [RFC8346] Clemm, A., Medved, J., Tkacik, T., Liu, X., Bryskin, I.,
Guo, A., Ananthakrishnan, H., Bahadur, N., and V. Beeram, Guo, A., Ananthakrishnan, H., Bahadur, N., and V. Beeram,
"A YANG Data Model for Layer 3 Topologies", RFC 8346, "A YANG Data Model for Layer 3 Topologies", RFC 8346,
March 2018, <http://www.rfc-editor.org/info/rfc8346>. March 2018, <http://www.rfc-editor.org/info/rfc8346>.
Appendix A. Non NMDA -state modules Appendix A. Non NMDA -state modules
The YANG module ietf-dc-fabric-toplogy defined in this document The YANG module ietf-dc-fabric-topology defined in this document
augments two modules, ietf-network and ietf-network-topology, that augments two modules, ietf-network and ietf-network-topology, that
are designed to be used in conjunction with implementations that are designed to be used in conjunction with implementations that
support the Network Management Datastore Architecture (NMDA) defined support the Network Management Datastore Architecture (NMDA) defined
in [RFC8342]. In order to allow implementations to use the model in [RFC8342]. In order to allow implementations to use the model
even in case when NMDA is not supported, a set of companion modules even in case when NMDA is not supported, a set of companion modules
have been defined that represent a state model of networks and have been defined that represent a state model of networks and
network topologies, ietf-network-state and ietf-network-topology- network topologies, ietf-network-state and ietf-network-topology-
state, respectively. state, respectively.
In order to be able to use the model for fabric topologies defined in In order to be able to use the model for fabric topologies defined in
skipping to change at page 24, line 43 skipping to change at page 24, line 47
Like ietf-network-state and ietf-network-topology-state, ietf-dc- Like ietf-network-state and ietf-network-topology-state, ietf-dc-
fabric-topology-state SHOULD NOT be supported by implementations that fabric-topology-state SHOULD NOT be supported by implementations that
support NMDA. It is for this reason that the module is defined in support NMDA. It is for this reason that the module is defined in
the Appendix. the Appendix.
The definition of the module follows below. As the structure of the The definition of the module follows below. As the structure of the
module mirrors that of its underlying module, the YANG tree is not module mirrors that of its underlying module, the YANG tree is not
depicted separately. depicted separately.
<CODE BEGINS> <CODE BEGINS>
file "ietf-dc-fabric-topology-state@2018-04-16.yang" file "ietf-dc-fabric-topology-state@2018-11-08.yang"
module ietf-dc-fabric-topology-state { module ietf-dc-fabric-topology-state {
yang-version 1.1;
namespace
"urn:ietf:params:xml:ns:yang:ietf-dc-fabric-topology-state";
prefix sfabric;
import ietf-network-state { yang-version 1.1;
prefix nws; namespace
reference "urn:ietf:params:xml:ns:yang:ietf-dc-fabric-topology-state";
"RFC 8345:A Data Model for Network Topologies"; prefix sfabric;
}
import ietf-dc-fabric-types {
prefix fabrictypes;
reference import ietf-network-state {
"draft-ietf-i2rs-yang-dc-fabric-network-topology-09 prefix nws;
NOTE TO RFC EDITOR: reference
(1) Please replace above reference to draft-ietf-i2rs-yang "RFC 8345:A Data Model for Network Topologies";
-dc-fabric-network-topology-09 with RFC number when }
published (i.e. RFC xxxx). import ietf-dc-fabric-types {
(2) Please replace the data in the revision statement prefix fabrictypes;
with the data of publication when published.";
}
organization reference
"IETF I2RS (Interface to the Routing System) Working Group"; "draft-ietf-i2rs-yang-dc-fabric-network-topology-12
NOTE TO RFC EDITOR:
(1) Please replace above reference to draft-ietf-i2rs-yang
-dc-fabric-network-topology-09 with RFC number when
published (i.e. RFC xxxx).
(2) Please replace the data in the revision statement
with the data of publication when published.";
}
contact organization
"WG Web: <http://tools.ietf.org/wg/i2rs/ > "IETF I2RS (Interface to the Routing System) Working Group";
WG List: <mailto:i2rs@ietf.org>
Editor: Yan Zhuang contact
<mailto:zhuangyan.zhuang@huawei.com> "WG Web: <http://tools.ietf.org/wg/i2rs/ >
WG List: <mailto:i2rs@ietf.org>
Editor: Danian Shi Editor: Yan Zhuang
<mailto:shidanian@huawei.com>"; <mailto:zhuangyan.zhuang@huawei.com>
description Editor: Danian Shi
"This module contains a collection of YANG definitions for <mailto:shidanian@huawei.com>";
Fabric state, representing topology that is either learned,
or topology that results from applying toplogy that has been
configured per the ietf-dc-fabric-topology model, mirroring
the corresponding data nodes in this model.
This model mirrors the configuration tree of ietf-dc-fabric description
-topology, but contains only read-only state data. The model "This module contains a collection of YANG definitions for
is not needed when the implemtation infrastructure supports Fabric state, representing topology that is either learned,
the Network Management Datastore Architecture(NMDA). or topology that results from applying toplogy that has been
configured per the ietf-dc-fabric-topology model, mirroring
the corresponding data nodes in this model.
Copyright (c) 2018 IETF Trust and the persons identified as This model mirrors the configuration tree of ietf-dc-fabric
authors of the code. All rights reserved. -topology, but contains only read-only state data. The model
is not needed when the implementation infrastructure supports
the Network Management Datastore Architecture(NMDA).
Redistribution and use in source and binary forms, with or Copyright (c) 2018 IETF Trust and the persons identified as
without modification, is permitted pursuant to, and subject authors of the code. All rights reserved.
to the license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF Trust's Legal
Provisions Relating to IETF Documents
(http:s//trustee.ietf.org/license-info).
This version of this YANG module is part of Redistribution and use in source and binary forms, with or
draft-ietf-i2rs-yang-dc-fabric-network-topology; without modification, is permitted pursuant to, and subject
see the RFC itself for full legal notices. to the license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF Trust's Legal
Provisions Relating to IETF Documents
(http:s//trustee.ietf.org/license-info).
NOTE TO RFC EDITOR: Please replace above reference to This version of this YANG module is part of
draft-ietf-i2rs-yang-dc-fabric-network-topology-09 with RFC draft-ietf-i2rs-yang-dc-fabric-network-topology;
number when published (i.e. RFC xxxx)."; see the RFC itself for full legal notices.
revision "2018-04-16"{ NOTE TO RFC EDITOR: Please replace above reference to
description draft-ietf-i2rs-yang-dc-fabric-network-topology-12 with RFC
"Initial revision. number when published (i.e. RFC xxxx).";
NOTE TO RFC EDITOR:
Please replace the following reference to
draft-ietf-i2rs-yang-dc-fabric-network-topology-09
with RFC number when published (i.e. RFC xxxx).";
reference
"draft-ietf-i2rs-yang-dc-fabric-network-topology-09";
}
//grouping statements revision "2018-11-08"{
grouping fabric-network-type { description
description "Identify the topology type to be fabric."; "Initial revision.
container fabric-network { NOTE TO RFC EDITOR:
presence "indicates fabric Network"; Please replace the following reference to
description draft-ietf-i2rs-yang-dc-fabric-network-topology-12
"The presence of the container node indicates with RFC number when published (i.e. RFC xxxx).";
fabric Topology"; reference
} "draft-ietf-i2rs-yang-dc-fabric-network-topology-12";
} }
grouping fabric-options { //grouping statements
description "Options for a fabric"; grouping fabric-network-type {
description "Identify the topology type to be fabric.";
container fabric-network {
presence "indicates fabric Network";
description
"The presence of the container node indicates
fabric topology";
}
}
leaf gateway-mode { grouping fabric-options {
type enumeration { description "Options for a fabric";
enum centralized {
description "The Fabric uses centerilized
gateway, in which gateway is deployed on SPINE
node.";
}
enum distributed {
description "The Fabric uses distributed
gateway, in which gateway is deployed on LEAF
node.";
}
}
default "distributed";
description "Gateway mode of the fabric";
}
leaf traffic-behavior { leaf gateway-mode {
type enumeration { type enumeration {
enum normal { enum centralized {
description "Normal means no policy is needed description "The Fabric uses centralized
for all traffic"; gateway, in which gateway is deployed on SPINE
} node.";
enum policy-driven { }
description "Policy driven means policy is enum distributed {
needed for the traffic otherwise the traffic description "The Fabric uses distributed
will be discard."; gateway, in which gateway is deployed on LEAF
} node.";
} }
default "normal"; }
description "Traffic behavior of the fabric"; default "distributed";
} description "Gateway mode of the fabric";
}
leaf-list capability-supported { leaf traffic-behavior {
type fabrictypes:service-capabilities; type enumeration {
description enum normal {
"It provides a list of supported services of the description "Normal means no policy is needed
fabric. The service-capabilities is defined as for all traffic";
identity-ref. Developers can define more services }
by defining new identies."; enum policy-driven {
} description "Policy driven means policy is
} needed for the traffic otherwise the traffic
will be discarded.";
}
}
default "normal";
description "Traffic behavior of the fabric";
}
grouping device-attributes { leaf-list capability-supported {
description "device attributes"; type fabrictypes:service-capabilities;
leaf device-ref { description
type fabrictypes:node-ref; "It provides a list of supported services of the
description fabric. The service-capabilities is defined as
"The device that the fabric includes which refers identity-ref. Users can define more services
to a node in another topolopogy."; by defining new identities.";
} }
leaf-list role { }
type fabrictypes:device-role;
default fabrictypes:leaf;
description
"It is a list of devce-role to represent the roles
that a device plays within a PoD, such as SPINE,
LEAF, Border, or Border-Leaf.
The device-role is defined as identity-ref. If more
than 2 stage is used for a PoD, developers can
define new identities for the device-role.";
}
}
grouping link-attributes { grouping device-attributes {
description "Link attributes"; description "device attributes";
leaf link-ref { leaf device-ref {
type fabrictypes:link-ref; type fabrictypes:node-ref;
description description
"The link that the fabric includes which refers to "The device that the fabric includes which refers
a link in another topology."; to a node in another topology.";
} }
} leaf-list role {
type fabrictypes:device-role;
default fabrictypes:leaf;
description
"It is a list of devce-role to represent the roles
that a device plays within a POD, such as SPINE,
LEAF, Border, or Border-Leaf.
The device-role is defined as identity-ref. If more
than 2 stage is used for a POD, users can
define new identities for the device-role.";
}
}
grouping port-attributes { grouping link-attributes {
description "Port attributes"; description "Link attributes";
leaf port-ref { leaf link-ref {
type fabrictypes:tp-ref; type fabrictypes:link-ref;
description description
"The port that the fabric includes which refers to "The link that the fabric includes which refers to
a termination-point in another topology."; a link in another topology.";
} }
leaf port-type { }
type fabrictypes:port-type;
description
"Port type is defined as identiy-ref. If current
types includes ethernet or serial. If more types
are needed, developers can define new identities.";
}
leaf bandwidth {
type fabrictypes:bandwidth;
description
"Bandwidth of the port. It is defined as
identity-ref. If more speeds are introduced,
developers can define new identies for them.
Current speeds include 1M, 10M, 100M, 1G, 10G,
40G and 100G.";
}
}
grouping fabric-attributes { grouping port-attributes {
description "Attributes of a fabric"; description "Port attributes";
leaf port-ref {
type fabrictypes:tp-ref;
description
"The port that the fabric includes which refers to
a termination-point in another topology.";
}
leaf port-type {
type fabrictypes:port-type;
description
"Port type is defined as identity-ref. If current
types includes ethernet or serial. If more types
are needed, developers can define new identities.";
}
leaf bandwidth {
type fabrictypes:bandwidth;
description
"Bandwidth of the port. It is defined as
identity-ref. If more speeds are introduced,
developers can define new identities for them.
Current speeds include 1M, 10M, 100M, 1G, 10G,
25G, 40G, 100G and 400G.";
}
}
leaf fabric-id { grouping fabric-attributes {
type fabrictypes:fabric-id; description "Attributes of a fabric";
description
"Fabric id";
}
leaf name { leaf fabric-id {
type string; type fabrictypes:fabric-id;
description description
"Name of the fabric"; "Fabric id";
} }
leaf type { leaf name {
type fabrictypes:underlay-network-type; type string;
description description
"The type of physical network that implements this "Name of the fabric";
fabric.Examples are vlan, and trill."; }
}
container vni-capacity { leaf type {
description "The range of the VNI(VXLAN Network type fabrictypes:underlay-network-type;
Identifier defined in RFC 7348)s that the PoD uses."; description
"The type of physical network that implements this
fabric. Examples are VLAN, and TRILL.";
}
leaf min { container vni-capacity {
type int32; description "The range of the VNI(VXLAN Network
description Identifier defined in RFC 7348)s that the POD uses.";
"The lower limit Vni.";
}
leaf max { leaf min {
type int32; type int32;
description description
"The upper limite Vni."; "The lower limit VNI.";
} }
}
leaf description { leaf max {
type string; type int32;
description description
"Description of the fabric"; "The upper limit VNI.";
} }
}
container options { leaf description {
description "Options of the fabric"; type string;
uses fabric-options; description
} "Description of the fabric";
}
list device-nodes { container options {
key device-ref; description "Options of the fabric";
description "Device nodes that include in a fabric."; uses fabric-options;
uses device-attributes; }
} list device-nodes {
key device-ref;
description "Device nodes that are included in a fabric.";
uses device-attributes;
}
list device-links { list device-links {
key link-ref; key link-ref;
description "Links that include within a fabric."; description "Links that are included within a fabric.";
uses link-attributes; uses link-attributes;
} }
list device-ports { list device-ports {
key port-ref; key port-ref;
description "Ports that include in the fabric."; description "Ports that are included in the fabric.";
uses port-attributes; uses port-attributes;
} }
} }
// augment statements // augment statements
augment "/nws:networks/nws:network/nws:network-types" { augment "/nws:networks/nws:network/nws:network-types" {
description description
"Introduce new network type for Fabric-based logical "Introduce a new network type for Fabric-based logical
topology"; topology";
uses fabric-network-type; uses fabric-network-type;
} }
augment "/nws:networks/nws:network/nws:node" { augment "/nws:networks/nws:network/nws:node" {
when "/nws:networks/nws:network/nws:network-types" when "/nws:networks/nws:network/nws:network-types"
+"/sfabric:fabric-network"{ +"/sfabric:fabric-network"{
description "Augmentation parameters apply only for description "Augmentation parameters apply only for
networks with fabric topology."; networks with fabric topology.";
} }
description "Augmentation for fabric nodes."; description "Augmentation for fabric nodes.";
container fabric-attributes-state { container fabric-attributes-state {
description description
"Attributes for a fabric network"; "Attributes for a fabric network";
uses fabric-attributes; uses fabric-attributes;
} }
} }
} }
<CODE ENDS> <CODE ENDS>
Authors' Addresses Authors' Addresses
Yan Zhuang Yan Zhuang
Huawei Huawei
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012 Nanjing, Jiangsu 210012
China China
Email: zhuangyan.zhuang@huawei.com Email: zhuangyan.zhuang@huawei.com
Danian Shi Danian Shi
Huawei Huawei
 End of changes. 132 change blocks. 
587 lines changed or deleted 590 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/