draft-ietf-i2rs-yang-dc-fabric-network-topology-07.txt   draft-ietf-i2rs-yang-dc-fabric-network-topology-08.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: September 19, 2018 R. Gu Expires: September 28, 2018 R. Gu
China Mobile China Mobile
H. Ananthakrishnan H. Ananthakrishnan
Packet Design Packet Design
March 18, 2018 March 27, 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-07 draft-ietf-i2rs-yang-dc-fabric-network-topology-08
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 Network. Center Network.
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.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 September 19, 2018. This Internet-Draft will expire on September 28, 2018.
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 25 skipping to change at page 2, line 25
3.2.1. Fabric Topology . . . . . . . . . . . . . . . . . . . 5 3.2.1. Fabric Topology . . . . . . . . . . . . . . . . . . . 5
3.2.2. Fabric node extension . . . . . . . . . . . . . . . . 6 3.2.2. Fabric node extension . . . . . . . . . . . . . . . . 6
3.2.3. Fabric termination-point extension . . . . . . . . . 7 3.2.3. Fabric termination-point extension . . . . . . . . . 7
4. Fabric YANG Module . . . . . . . . . . . . . . . . . . . . . 7 4. Fabric YANG Module . . . . . . . . . . . . . . . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
6. Security Considerations . . . . . . . . . . . . . . . . . . . 20 6. Security Considerations . . . . . . . . . . . . . . . . . . . 20
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 21 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 21
8.1. Normative References . . . . . . . . . . . . . . . . . . 21 8.1. Normative References . . . . . . . . . . . . . . . . . . 21
8.2. Informative References . . . . . . . . . . . . . . . . . 22 8.2. Informative References . . . . . . . . . . . . . . . . . 22
Appendix A. Non NMDA -state modules . . . . . . . . . . . . . . 23 Appendix A. Non NMDA -state modules . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28
1. Introduction 1. Introduction
Normally, a data center (DC) network is composed of single or Normally, a data center (DC) network is composed of single or
multiple fabrics which are also known as PODs (Points Of Delivery). multiple fabrics which are also known as PODs (Points Of Delivery).
These fabrics may be heterogeneous due to implementation of different These 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 enrolled. For example, Fabric A may use VXLAN while features are enrolled. 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
skipping to change at page 3, line 6 skipping to change at page 3, line 6
Luckily, for a DC network, a fabric can be considered as an atomic Luckily, for a DC network, a fabric can be considered as an atomic
structure for management purposes. From this point of view, the structure for management purposes. From this point of view, the
management of the DC network can be decomposed into a set of tasks to management of the DC network can be decomposed into a set of tasks to
manage each fabric separately, as well as the fabric manage each fabric separately, as well as the fabric
interconnections. This way, the overall management task becomes very interconnections. This way, the overall management task becomes very
flexible and makes it easy to expand and adopt to DC networks that flexible and makes it easy to expand and adopt to DC networks that
evolve over time. 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 [6020][7950] for fabric-based data center topology. To do data model [RFC6020][RFC7950] for fabric-based data center topology.
so, it augments the generic network and network topology data models To do so, it augments the generic network and network topology data
defined in [I-D.ietf-i2rs-yang-network-topo] with information that is models defined in [RFC8345] with information that is specific to Data
specific to Data Center fabric networks. 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 [I-D.ietf- Within the context of topology architecture defined in [RFC8345] and
i2rs-yang-network-topo] and [I.D. draft-ietf-i2rs-usecase-reqs- [I.D. draft-ietf-i2rs-usecase-reqs-summary], this model can also be
summary], this model can also be treated as an application of the treated as an application of the I2RS network topology model
I2RS network topology model [I-D.ietf-i2rs-yang-network-topo] in the [RFC8345] in the scenario of Data center network management. It can
scenario of Data center network management. It can also act as a also act as a service topology when mapping network elements at the
service topology when mapping network elements at the fabric layer to fabric layer to elements of other topologies, such as L3 topologies
elements of other topologies, such as L3 topologies as defined in as defined in [RFC8346].
[I.D. draft-ietf-i2rs-yang-l3-topology].
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, etc.) as well
as its connections to other fabrics while putting the underlay as its connections to other fabrics while putting the underlay
topology aside. As such, clients can consume the topology topology aside. As such, clients can consume the topology
information at the fabric level with no need to be aware of the information at the fabric level with no need to be aware of the
entire set of links and nodes in the corresponding underlay networks. entire set of links and nodes in the corresponding underlay networks.
A fabric topology can be configured by a network administrator using A fabric topology can be configured by a network administrator using
the controller by adding physical devices and links into a fabric. the controller by adding physical devices and links into a fabric.
skipping to change at page 5, line 11 skipping to change at page 5, line 11
such as VLAN, VXLAN etc. The main purpose of this module is to such as VLAN, VXLAN etc. The main purpose of this module is to
configure and manage fabrics and their connections. It provides a configure and manage fabrics and their connections. It provides a
fabric-based topology view for data center applications. fabric-based 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 [I-D.draft-ietf-netmod-yang-tree- The notation syntax follows [RFC8340].
diagrams].
module: ietf-fabric-topology module: ietf-fabric-topology
augment /nw:networks/nw:network/nw:network-types: augment /nw:networks/nw:network/nw:network-types:
+--rw fabric-network! +--rw fabric-network!
augment /nw:networks/nw:network/nw:node: augment /nw:networks/nw:network/nw:node:
+--rw fabric-attributes +--rw fabric-attributes
+--rw fabric-id? fabric-id +--rw fabric-id? fabric-id
+--rw name? string +--rw name? string
+--rw type? fabrictype:underlay-network-type +--rw type? fabrictype:underlay-network-type
+--rw description? string +--rw description? string
skipping to change at page 6, line 10 skipping to change at page 6, line 10
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, a fabric itself is composed of a set of network
elements i.e. devices, and related links. The configuration of a elements i.e. devices, and related links. The configuration of a
fabric is contained under the "fabric-attributes" container depicted fabric is contained under the "fabric-attributes" container depicted
as follows. The notation syntax follows [I-D.draft-ietf-netmod-yang- as follows. The notation syntax follows [RFC8340].
tree-diagrams].
+--rw fabric-attributes +--rw fabric-attributes
+--rw fabric-id? fabric-id +--rw fabric-id? 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 16 skipping to change at page 7, line 16
Since a fabric can be considered as a node, "termination-points" can Since a fabric can be considered as a node, "termination-points" can
represent fabric "ports" that connect to other fabrics, end hosts, as represent fabric "ports" that connect to other fabrics, end hosts, as
well as devices inside the fabric. well as devices inside the fabric.
As such, the set of "termination-points" of a fabric indicate all As such, the set of "termination-points" of a fabric indicate all
connections of the fabric, including its internal connections, connections of the fabric, including its internal connections,
interconnections with other fabrics, and connections to end hosts. interconnections with other fabrics, and connections to end hosts.
The structure of fabric ports is as follows. The notation syntax The structure of fabric ports is as follows. The notation syntax
follows [I-D.draft-ietf-netmod-yang-tree-diagrams]. follows [RFC8340].
The structure of fabric ports is as follows: The structure of fabric ports is as follows:
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
+--ro device-port? tp-ref +--ro device-port? tp-ref
+--ro (tunnel-option)? +--ro (tunnel-option)?
skipping to change at page 7, line 45 skipping to change at page 7, line 45
port can be mapped to a device node in the underlay network. port 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 [ietf-i2rs-yang-network-topo], and This module imports typedefs from [RFC8345], and it references
it references [RFC7348] and [draft-ietf-netmod-rfc7277bis]. [RFC7348] and [RFC8344].
NOTE TO RFC EDITOR: (1) Please replace above reference to draft-ietf-
i2rs-yang-network-topo-20 and [draft-ietf-netmod-rfc7277bis] with RFC
numbers when published (i.e. RFC xxxx). (2) Please replace the date
in the revision statement with the date of publication when
published."
<CODE BEGINS> file "ietf-dc-fabric-types@2017-12-21.yang" <CODE BEGINS> file "ietf-dc-fabric-types@2017-12-21.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;
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>
skipping to change at page 8, line 29 skipping to change at page 8, line 23
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>
Editor: Danian Shi Editor: Danian Shi
<mailto:shidanian@huawei.com>"; <mailto:shidanian@huawei.com>";
description description
"This module contains a collection of YANG definitions for Fabric. "This module contains a collection of YANG definitions for Fabric.
Copyright (c) 2016 IETF Trust and the persons identified as Copyright (c) 2018 IETF Trust and the persons identified as
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). (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-03 with RFC draft-ietf-i2rs-yang-dc-fabric-network-topology-03 with RFC
number when published (i.e. RFC xxxx)."; number when published (i.e. RFC xxxx).";
revision "2017-12-21"{ revision "2017-12-21"{
skipping to change at page 13, line 42 skipping to change at page 13, line 35
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 reference
"draft-ietf-i2rs-yang-network-topo-20 "RFC 8345:A Data Model for Network Topologies";
NOTE TO RFC EDITOR:
(1) Please replace above reference to
draft-ietf-i2rs-yang-network-topo-20 with RFC
number when published (i.e. RFC xxxx).
(2) Please replace the date in the revision statement with the
date of publication when published.";
} }
import ietf-network-topology { import ietf-network-topology {
prefix nt; prefix nt;
reference reference
"draft-ietf-i2rs-yang-network-topo-20 "RFC 8345:A Data Model for Network Topologies";
NOTE TO RFC EDITOR:
(1) Please replace above reference to
draft-ietf-i2rs-yang-network-topo-20 with RFC
number when published (i.e. RFC xxxx).
(2) Please replace the date in the revision statement with the
date of publication when published.";
} }
import ietf-dc-fabric-types { import ietf-dc-fabric-types {
prefix fabrictypes; prefix fabrictypes;
reference reference
"draft-ietf-i2rs-yang-dc-fabric-network-topology-03 "draft-ietf-i2rs-yang-dc-fabric-network-topology-03
NOTE TO RFC EDITOR: NOTE TO RFC EDITOR:
(1) Please replace above reference to draft-ietf-i2rs-yang-dc (1) Please replace above reference to draft-ietf-i2rs-yang-dc
-fabric-network-topology-03 with RFC number when publised -fabric-network-topology-03 with RFC number when publised
(i.e. RFC xxxx). (i.e. RFC xxxx).
(2) Please replace the data in the revision statement with the (2) Please replace the date in the revision statement with the
data of publication when published."; data of publication when published.";
} }
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>
Editor: Danian Shi Editor: Danian Shi
<mailto:shidanian@huawei.com>"; <mailto:shidanian@huawei.com>";
description description
"This module contains a collection of YANG definitions for Fabric. "This module contains a collection of YANG definitions for Fabric.
Copyright (c) 2016 IETF Trust and the persons identified as Copyright (c) 2018 IETF Trust and the persons identified as
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). (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;see the RFC draft-ietf-i2rs-yang-dc-fabric-network-topology;see the RFC
itself for full legal notices. 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-03 with RFC draft-ietf-i2rs-yang-dc-fabric-network-topology-03 with RFC
number when published (i.e. RFC xxxx)."; number when published (i.e. RFC xxxx).";
revision "2018-02-11"{ revision "2018-02-11"{
skipping to change at page 18, line 4 skipping to change at page 17, line 34
type string; type string;
description description
"Name of the fabric"; "Name of the fabric";
} }
leaf type { leaf type {
type fabrictypes:underlay-network-type; type fabrictypes:underlay-network-type;
description description
"The type of physical network that implements this "The type of physical network that implements this
fabric.Examples are vlan, and trill."; fabric.Examples are vlan, and trill.";
} }
container vni-capacity { container vni-capacity {
description "Number of vni(VXLAN Network Identifier defined in RFC 7348)s that the fabric has."; description "Number of vni(VXLAN Network Identifier
defined in RFC 7348)s that the fabric has.";
leaf min { leaf min {
type int32; type int32;
description description
"Vni min capacity"; "Vni min capacity";
} }
leaf max { leaf max {
type int32; type int32;
description description
"Vni max capacity"; "Vni max capacity";
skipping to change at page 21, line 30 skipping to change at page 21, line 16
We wish to acknowledge the helpful contributions, comments, and We wish to acknowledge the helpful contributions, comments, and
suggestions that were received from Alexander Clemm, Donald E. suggestions that were received from Alexander Clemm, Donald E.
Eastlake, Xufeng Liu, Susan Hares, Wei Song, Luis M. Contreras and Eastlake, Xufeng Liu, Susan Hares, Wei Song, Luis M. Contreras and
Benoit Claise. Benoit Claise.
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.draft-ietf-i2rs-yang-l3-topology]
Clemm, A., Medved, J., Tkacik, T., Liu, X., Bryskin, I.,
Guo, A., Ananthakrishnan, H., Bahadur, N., and V. Beeram,
"A YANG Data Model for Layer 3 Topologies", I-D draft-
ietf-i2rs-yang-l3-topology-04, September 2016.
[I-D.draft-ietf-i2rs-yang-network-topo]
Clemm, A., Medved, J., Tkacik, T., Varga, R., Bahadur, N.,
and H. Ananthakrishnan, "A YANG Data Model for Network
Topologies", I-D draft-ietf-i2rs-yang-network-topo-06,
September 2016.
[I-D.draft-ietf-netmod-revised-datastores-06]
Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "A Revised Conceptual Model for YANG
Datastores", I-D draft-ietf-netmod-revised-datastores-06,
October 2017.
[I-D.draft-ietf-netmod-rfc7277bis]
Bjorklund, M., "A YANG Data Model for IP Management", I-D
draft-ietf-netmod-rfc7277bis-03, January 2018.
[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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC5246] Dierks, T. and E. Rescorla, "Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "Transport Layer Security
(TLS) Protocol Version 1.2", August 2008, (TLS) Protocol Version 1.2", August 2008,
<http://www.rfc-editor.org/info/rfc5246>. <http://www.rfc-editor.org/info/rfc5246>.
[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the
skipping to change at page 22, line 47 skipping to change at page 22, line 9
Networks", August 2014, Networks", August 2014,
<http://www.rfc-editor.org/info/rfc7348>. <http://www.rfc-editor.org/info/rfc7348>.
[RFC7950] Bjorklund, M., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, Auguest 2016. RFC 7950, DOI 10.17487/RFC7950, Auguest 2016.
[RFC8040] Bierman, A., Bjorklund, B., and K. Watsen, "RESTCONF [RFC8040] Bierman, A., Bjorklund, B., and K. Watsen, "RESTCONF
Protocol", Jan 2017, Protocol", Jan 2017,
<http://www.rfc-editor.org/info/rfc8040>. <http://www.rfc-editor.org/info/rfc8040>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore
Architecture", RFC 8342, March 2018.
[RFC8344] Bjorklund, M., "A YANG Data Model for IP Management",
RFC 8344, March 2018,
<http://www.rfc-editor.org/info/rfc8344>.
[RFC8345] Clemm, A., Medved, J., Tkacik, T., Varga, R., Bahadur, N.,
and H. Ananthakrishnan, "A YANG Data Model for Network
Topologies", RFC 8345, March 2018,
<http://www.rfc-editor.org/info/rfc8345>.
[RFC8346] Clemm, A., Medved, J., Tkacik, T., Liu, X., Bryskin, I.,
Guo, A., Ananthakrishnan, H., Bahadur, N., and V. Beeram,
"A YANG Data Model for Layer 3 Topologies", RFC 8346,
March 2018, <http://www.rfc-editor.org/info/rfc8346>.
8.2. Informative References 8.2. Informative References
[I-D.draft-ietf-i2rs-usecase-reqs-summary] [I-D.draft-ietf-i2rs-usecase-reqs-summary]
Hares, S. and M. Chen, "Summary of I2RS Use Case Hares, S. and M. Chen, "Summary of I2RS Use Case
Requirements", I-D draft-ietf-netmod-yang-tree-diagrams, Requirements", I-D draft-ietf-i2rs-usecase-reqs-summary,
May 2015. May 2015.
[I-D.draft-ietf-netmod-yang-tree-diagrams]
Bjorklund, M. and L. Berger, "YANG Tree Diagrams", I-D
draft-ietf-netmod-yang-tree-diagrams, October 2017.
[I-D.draft-ietf-nvo3-geneve] [I-D.draft-ietf-nvo3-geneve]
Gross, J., Ganga, I., and T. Sridhar, "Geneve: Generic Gross, J., Ganga, I., and T. Sridhar, "Geneve: Generic
Network Virtualization Encapsulation", I-D draft-ietf- Network Virtualization Encapsulation", I-D draft-ietf-
nvo3-geneve-05, September 2017. nvo3-geneve-06, March 2018.
[RFC8340] Bjorklund, M. and L. Berger, "YANG Tree Diagrams",
RFC 8340, March 2018,
<http://www.rfc-editor.org/info/rfc8340>.
Appendix A. Non NMDA -state modules Appendix A. Non NMDA -state modules
The YANG module ietf-fabric-toplogy defined in this document augments The YANG module ietf-fabric-toplogy defined in this document augments
two modules, ietf-network and ietf-network-topology, that are two modules, ietf-network and ietf-network-topology, that are
designed to be used in conjunction with implementations that support designed to be used in conjunction with implementations that support
the Network Management Datastore Architecture (NMDA) defined in [I- the Network Management Datastore Architecture (NMDA) defined in
D.draft-ietf-netmod-revised-datastores]. In order to allow [RFC8342]. In order to allow implementations to use the model even
implementations to use the model even in case when NMDA is not in case when NMDA is not supported, a set of companion modules have
supported, a set of companion modules have been defined that been defined that represent a state model of networks and network
represent a state model of networks and network topologies, ietf- topologies, ietf-network-state and ietf-network-topology-state,
network-state and ietf-network-topology-state, respectively. 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
this in this document in conjunction with non-NMDA compliant this in this document in conjunction with non-NMDA compliant
implementations, a corresponding companion module needs to be implementations, a corresponding companion module needs to be
introduced as well. This companion module, ietf-fabric-topology- introduced as well. This companion module, ietf-fabric-topology-
state, mirrors ietf-fabric-topology. However, the module augments state, mirrors ietf-fabric-topology. However, the module augments
ietf-network-state (instead of ietf-network and ietf-network- ietf-network-state (instead of ietf-network and ietf-network-
topology) and all of its data nodes are non-configurable. topology) and all of its data nodes are non-configurable.
Like ietf-network-state and ietf-network-topology-state, ietf-fabric- Like ietf-network-state and ietf-network-topology-state, ietf-fabric-
skipping to change at page 24, line 4 skipping to change at page 23, line 34
<CODE BEGINS> file "ietf-dc-fabric-topology-state@2018-02-11.yang" <CODE BEGINS> file "ietf-dc-fabric-topology-state@2018-02-11.yang"
module ietf-dc-fabric-topology-state { module ietf-dc-fabric-topology-state {
yang-version 1.1; yang-version 1.1;
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;
import ietf-network-state { import ietf-network-state {
prefix nws; prefix nws;
reference reference
"draft-ietf-i2rs-yang-network-topo-20 "RFC 8345:A Data Model for Network Topologies";
NOTE TO RFC EDITOR:
(1) Please replace above reference to
draft-ietf-i2rs-yang-network-topo-20 with RFC
number when published (i.e. RFC xxxx).
(2) Please replace the date in the revision statement with the
date of publication when published.";
} }
import ietf-dc-fabric-types { import ietf-dc-fabric-types {
prefix fabrictypes; prefix fabrictypes;
reference reference
"draft-ietf-i2rs-yang-dc-fabric-network-topology-03 "draft-ietf-i2rs-yang-dc-fabric-network-topology-03
NOTE TO RFC EDITOR: NOTE TO RFC EDITOR:
(1) Please replace above reference to draft-ietf-i2rs-yang-dc (1) Please replace above reference to draft-ietf-i2rs-yang-dc
-fabric-network-topology-03 with RFC number when published -fabric-network-topology-03 with RFC number when published
(i.e. RFC xxxx). (i.e. RFC xxxx).
(2) Please replace the data in the revision statement with the (2) Please replace the date in the revision statement with the
data of publication when published."; data of publication when published.";
} }
import ietf-dc-fabric-topology { import ietf-dc-fabric-topology {
prefix fabric; prefix fabric;
reference reference
"draft-ietf-i2rs-yang-dc-fabric-network-topology-03 "draft-ietf-i2rs-yang-dc-fabric-network-topology-03
NOTE TO RFC EDITOR: NOTE TO RFC EDITOR:
(1) Please replace above reference to draft-ietf-i2rs-yang-dc (1) Please replace above reference to draft-ietf-i2rs-yang-dc
-fabric-network-topology-03 with RFC number when published -fabric-network-topology-03 with RFC number when published
(i.e. RFC xxxx). (i.e. RFC xxxx).
(2) Please replace the data in the revision statement with the (2) Please replace the date in the revision statement with the
data of publication when published."; data of publication when published.";
} }
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>
skipping to change at page 25, line 16 skipping to change at page 24, line 39
learned, or topology that results from applying toplogy learned, or topology that results from applying toplogy
that has been configured per the ietf-dc-fabric-topology that has been configured per the ietf-dc-fabric-topology
model, mirroring the corresponding data nodes in this model. model, mirroring the corresponding data nodes in this model.
This model mirrors the configuration tree of This model mirrors the configuration tree of
ietf-dc-fabric-topology, but contains only read-only state ietf-dc-fabric-topology, but contains only read-only state
data. The model is not needed when the implemtation data. The model is not needed when the implemtation
infrastructure supports the Network Management Datastore infrastructure supports the Network Management Datastore
Architecture(NMDA). Architecture(NMDA).
Copyright (c) 2016 IETF Trust and the persons identified Copyright (c) 2018 IETF Trust and the persons identified
as authors of the code. All rights reserved. as 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(http://trustee.ietf.org/license-info). Relating to IETF Documents(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;see the RFC draft-ietf-i2rs-yang-dc-fabric-network-topology;see the RFC
itself for full legal notices. 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-03 with RFC number draft-ietf-i2rs-yang-dc-fabric-network-topology-03 with RFC number
when published (i.e. RFC xxxx)."; when published (i.e. RFC xxxx).";
revision "2018-02-11" { revision "2018-02-11" {
 End of changes. 32 change blocks. 
98 lines changed or deleted 66 lines changed or added

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