A YANG Model for IP Link and Transport Service Mapping
draft-fu-pce-vnt-protection-group-00
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
|
|
|---|---|---|---|
| Authors | Pengcheng FU , Jianzhong FU , Ruiquan Jing | ||
| Last updated | 2016-10-28 | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-fu-pce-vnt-protection-group-00
Network Working Group PC. Fu
Internet-Draft JZ. FU
Intended status: Standards Track Huawei Technologies
Expires: May 1, 2017 AJ. Wang
RQ. Jing
China Telecom
October 28, 2016
A YANG Model for IP Link and Transport Service Mapping
draft-fu-pce-vnt-protection-group-00
Abstract
IP+optical is a cross-layer collaboration technology for unified
management of IP and optical networks.
Based on framework proposed in [ACTN-
FWK][I-D.ietf-teas-actn-framework], this draft presents specific
information about the IP+optical solution: hierarchical controllers +
disabled GMPLS UNIs. This solution does not involve UNI tunnel
objects. Therefore, the mapping between IP links and transport
services is key point of this solution.
The system uses loose-coupled dual-controllers to implement cross-
layer collaborative path calculation on the virtual network topology
(VNT), where the VNT provides the route calculation bridging
function. The VNT needs to be defined as a YANG model for
configuration management.
This draft provides a YANG model for the RESTCONF/NETCONF protocol.
This YANG module defines NBIs for the IP+optical super controller.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Fu, et al. Expires May 1, 2017 [Page 1]
Internet-Draft October 2016
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 1, 2017.
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. IP+optical solution . . . . . . . . . . . . . . . . . . . 2
1.2. Unified cross-layer algorithm . . . . . . . . . . . . . . 4
1.3. IP+VNT algorithm . . . . . . . . . . . . . . . . . . . . 5
1.4. VNT Proctect-Group . . . . . . . . . . . . . . . . . . . 6
2. VNT (IP Link) Model - YANG Tree . . . . . . . . . . . . . . . 7
3. VNT (IP Link) Model - YANG Code . . . . . . . . . . . . . . . 9
4. VNT (IP Link) Protection Group Model - YANG Tree . . . . . . 12
5. VNT (IP Link) Protection Group Model - YANG Code . . . . . . 13
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
7. Security Considerations . . . . . . . . . . . . . . . . . . . 15
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15
9. Normative References . . . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction
1.1. IP+optical solution
IP+optical is a cross-layer collaboration technology for unified
management of IP and optical networks. IP+optical adopts the C/S
architecture, where the IP network is the client-layer network and
the optical network is the server-layer network. The mapping between
IP-layer IP links and transport services is the key ability of an
Fu, et al. Expires May 1, 2017 [Page 2]
Internet-Draft October 2016
IP+optical network. Through the mapping, the services of IP layers
and those of transport layers can be associated to implement use
cases of IP+optical scenarios.
IP+optical use cases include multi-layer topology visualization,
automated network deployment, multi-layer automated service
deployment, multi-layer protection and restoration, multi-layer
optimization, and multi-layer maintenance window.
Based on framework proposed in [ACTN-
FWK][I-D.ietf-teas-actn-framework], this draft presents specific
information about the IP+optical solution: hierarchical controllers +
disabled GMPLS UNIs. This solution does not involve UNI tunnel
objects. Therefore, the mapping between IP links and transport
services is key point of this solution.
+----------+
|IP+Optical|
| Super |
|Controller|
+-/------\-+
/ \
+---------/--+ +--\--------+
| IP | | Optical |
| Controller | |Controller |
+----+-------+ +---+-------+
| |
+----+----------------+-------------+
/R | R |R R /
/ R R | /
IP / R . R . | R R /
Layer +-------------------------+---------+
. . . . | . .
. . . . | . .
. . . . | . .
. . . . | . .
. . . . | . .
+---------------------+-------------+
/ O . O . O . | O O /
/ O . O O /
Optical / O O O O O /
Layer +-----------------------------------+
In real-world situations, IP+optical super controllers can be
separately deployed or combined with other controllers. For example,
in IP+optical single-domain scenarios, an IP+optical super controller
can be combined with an IP domain controller. In IP multi-domain and
optical multi-domain scenarios, you can deploy one separate IP super
Fu, et al. Expires May 1, 2017 [Page 3]
Internet-Draft October 2016
controller and one separate optical super controller. The two super
controllers communicate through RESTConf interfaces and use the
IP+VNT algorithm to complete E2E cross-layer path calculation. In
such multi-domain scenarios, you can also deploy only one IP+optical
super controller and use a unified cross-layer algorithm in the
controller to complete E2E cross-layer path calculation.
The IP+optical solution implements cross-layer service provisioning
through cross-layer link and association of multi-layer topologies.
After service provisioning, this solution is required to present
multi-layer service views for users to learn service status. In
addition, the association management function needs to be available
during fault demarcation and locating and cross-layer protection and
restoration. To meet these demands, a service mapping needs to be
maintained between IP-layer IP links and optical-layer transport
services.
This draft provides a YANG model for the RESTCONF/NETCONF protocol.
This YANG module defines NBIs for the IP+optical super controller.
1.2. Unified cross-layer algorithm
In this model, inter-layer path computation is performed by a single
PCE that has topology visibility into all layers. Such a PCE is
called a multi-layer PCE. In Figure 2, the network is comprised of
two layers. LSRs H1, H2,H3, and H4 belong to the higher layer, and
LSRs H2, H3, L1, and L2 belong to the lower layer. The PCE is a
multi-layer PCE that has visibility into both layers. It can perform
end-to-end path computation across layers (single PCE path
computation). For instance, it can compute an optimal path
H1-H2-L1-L2-H3-H4 for a higher-layer LSP from H1 to H4. This path
includes the path of a lower-layer LSP from H2 to H3 that is already
in existence or not yet established. return it to H1.Of course, more
complex cooperation may be required if an optimal end-to-end path is
desired.
Fu, et al. Expires May 1, 2017 [Page 4]
Internet-Draft October 2016
Controller
+-----------------------------------+
| +--------------+ |
| |Multilayer-PCE| |
| +--------------+ |
| +--------++-----------++--------+ |
| |IP ||Cross-Layer||Optical | |
| |Topology||Topology ||Topology| |
| +--------++-----------++--------+ |
+----------------+------------------+
|
|
|
----- ----- | ----- -----
| R |--| R |........|.......| R |--| R |
| H1 | | H2 | | H3 | | H4 |
----- -----\ /----- -----
\----- -----/
| O |--| O |
| L1 | | L2 |
----- -----
1.3. IP+VNT algorithm
In this model, there is at least one PCE per layer, and each PCE has
topology visibility restricted to its own layer. Some providers may
want to keep the layer boundaries due to factors such as
organizational and/or service management issues. The choice for
multiple PCE computation instead of single PCE computation may also
be driven by scalability considerations, as in this mode a PCE only
needs to maintain topology information for one layer (resulting in a
size reduction for the Traffic Engineering Database (TED)).These PCEs
are called mono-layer PCEs. Mono-layer PCEs collaborate to compute
an end-to-end optimal path across layers. Figure 3 shows multiple
PCE inter-layer computation with inter-PCE communication. There is
one PCE in each layer. The PCEs from each layer collaborate to
compute an end-to-end path across layers. PCE Hi is responsible for
computations in the higher layer and may "consult" with PCE Lo to
compute paths across the lower layer. PCE Lo is responsible for path
computation in the lower layer. A simple example of cooperation
between the PCEs could be as follows:
o LSR H1 sends a request to PCE Hi for a path H1-H4.
o PCE Hi selects H2 as the entry point to the lower layer and H3 as
the exit point.
o PCE Hi requests a path H2-H3 from PCE Lo.
Fu, et al. Expires May 1, 2017 [Page 5]
Internet-Draft October 2016
o PCE Lo returns H2-L1-L2-H3 to PCE Hi.
o PCE Hi is now able to compute the full path (H1-H2-L1-L2-H3-H4)
IP Controller Optical Controller
+-----------------------+ +-----------------------------------+
| +------+ | | +-----------+ |
| |IP-PCE| | | |Optical-PCE| |
| +------+ | | +-----------+ |
|+--------++-----------+| | +--------++-----------++--------+ |
||IP ||VNT || | |VNT ||Cross-Layer||Optical | |
||Topology||Topology || | |Topology||Topology ||Topology| |
|+--------++-----------+| | +--------++-----------++--------+ |
+-----------+---+-------+ +----------+-----+------------------+
| |
| |
| |
| |
| |
----- ----- | ----- -----
| R |-+| R |......................|.| R |--| R |
| H1 | | H2 | | | H3 | | H4 |
----- -----\ | /----- -----
\ /
\ /
\ /
\ /
\----- -----/
| O |--| O |
| L1 | | L2 |
----- -----
1.4. VNT Proctect-Group
VNT protection groups support:.
o Manual and automatic service switchover and switchback
o 1:1 and N:1 working modes
o Protection of links with the same source but different sinks,
protection of links with different sources but the same sink, and
protection of links with both different sources and sinks
Fu, et al. Expires May 1, 2017 [Page 6]
Internet-Draft October 2016
(preamble)
Please view in a fixed-width font such as Courier.
VNT W
+-----------------------------------+
/R\---------R R R /
/ \ R /
IP / R VNT P R . R R /
Layer +-----------------------------------+
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
+-----------------------------------+
/ O O . O . O O /
/ . O O /
Optical / O O O O O /
Layer +-----------------------------------+
(postamble)
2. VNT (IP Link) Model - YANG Tree
(preamble)
Fu, et al. Expires May 1, 2017 [Page 7]
Internet-Draft October 2016
module: ietf-VNT
+--rw VNT
+--rw VNT* [VNT-id]
+--rw VNT-id
+--rw config
| +--rw VNT-id uint32
| +--rw VNT-name string
| +--rw Source C Node Type
| +--rw Source C Node Name
| +--rw Source C Interface Type
| +--rw Source C Interface IP
| +--rw Bind Interface Name
| +--rw Sink C Node Type
| +--rw Sink C Node Name
| +--rw Sink C Interface Type
| +--rw Sink C Interface IP
| +--rw Bind Interface Name
| +--rw Switch Type
| +--rw VLAN ID
| +--rw Latency
| +--rw MaxReservableBandwidth
| +--rw Bandwidth
| +--rw TEMetric
| +--rw ExplicitPathName
| +--rw Optical Protection Type
+--ro state
| +--ro VNT-id uint32
| +--ro VNT-name string
| +--ro Source C Node Type
| +--ro Source C Node Name
| +--ro Source C Interface Type
| +--ro Source C Interface IP
| +--ro Bind Interface Name
| +--ro Sink C Node Type
| +--ro Sink C Node Name
| +--ro Sink C Interface Type
| +--ro Sink C Interface IP
| +--ro Bind Interface Name
| +--ro Switch Type
| +--ro VLAN ID
| +--ro Latency
| +--ro MaxReservableBandwidth
| +--ro Bandwidth
| +--ro TEMetric
| +--ro ExplicitPathName
| +--ro Optical Protection Type
Fu, et al. Expires May 1, 2017 [Page 8]
Internet-Draft October 2016
(postamble)
3. VNT (IP Link) Model - YANG Code
(preamble)
module ietf-vnt {
namespace "urn:ietf:params:xml:ns:yang:ietf-vnt";
prefix "vnt";
import ietf-inet-types {
prefix inet;
}
import ietf-yang-types {
prefix yang;
}
import ietf-interfaces {
prefix if;
}
organization
"Huawei Technologies";
contact
"fupengcheng@huawei.com";
description
"The YANG module defines vnt.";
revision 2016-10-28 {
description "Initial revision.";
}
/* Typedefs */
typedef vlan {
type uint16 {
range "0..4095";
}
description "VLAN ID";
}
typedef protection-type {
type string;
description
"ip or optical protection type.";
}
Fu, et al. Expires May 1, 2017 [Page 9]
Internet-Draft October 2016
/* Main blocks */
container vnts {
description
"Virtual network topology.";
list vnt {
key "vnt-id";
description
"The list of configured interfaces on the device.";
leaf vnt-id {
type string;
description
"Id of vnt.";
}
leaf vnt-name {
type string;
description
"Name of vnt.";
}
leaf src-node-id {
type string;
description
"Id of node."
}
leaf src-interface-type {
type if:type;
description
"interface type.";
}
leaf src-interface-ip {
type inet:ipv4-address;
description
"Ip of interface.";
}
leaf src-bind-if-name {
type if:name;
description
"source node bind interface name.";
}
leaf sink-node-id {
type string;
Fu, et al. Expires May 1, 2017 [Page 10]
Internet-Draft October 2016
description
"Id of node."
}
leaf sink-interface-type {
type if:type;
description
"interface type.";
}
leaf sink-interface-ip {
type inet:ipv4-address;
description
"Ip of interface.";
}
leaf sink-bind-if-name {
type if:name;
description
"sink node bind interface name.";
}
leaf switch-type {
type uint16;
description
"switch type.";
}
leaf vlan-id {
type vlan;
description
"vlan id.";
}
leaf latency {
type uint32;
description
"latency.";
}
leaf max-reservable-bandwidth {
type decimal64;
description
"max reservable bandwidth.";
}
leaf bandwidth {
type decimal64;
Fu, et al. Expires May 1, 2017 [Page 11]
Internet-Draft October 2016
description
"bandwidth.";
}
leaf te-metric{
type uint32;
description
"te metric.";
}
leaf explicit-path-name {
type string;
description
"explicit path name";
}
leaf optical-protection-type {
type string;
description
"optical protection type.";
}
}
}
}
(postamble)
4. VNT (IP Link) Protection Group Model - YANG Tree
Fu, et al. Expires May 1, 2017 [Page 12]
Internet-Draft October 2016
(preamble)
module: ietf-VNT-Proctect-Group
+--rw VNT-Proctect-Group
+--rw VNT-Proctect-Group* [VNT-Proctect-Group-id]
+--rw VNT-Proctect-Group-id
+--rw config
| +--rw VNT-Proctect-Group-id uint32
| +--rw VNT-Proctect-Group-name string
| +--rw VNT-Proctect-Group-type [1:1/n:1]
| +--rw Work-VNT-list
| +--rw protect-VNT-list
| +--rw is-autoaction
| +--rw is-return
+--ro state
| +--ro VNT-Proctect-Group-id uint32
| +--ro VNT-Proctect-Group-name string
| +--ro VNT-Proctect-Group-type [1:1/n:1]
| +--ro Work-VNT-list
| +--ro protect-VNT-list
| +--ro is-autoaction
| +--ro is-return
(postamble)
5. VNT (IP Link) Protection Group Model - YANG Code
(preamble)
module ietf-vnt-protect-group {
namespace "urn:ietf:params:xml:ns:yang:ietf-vnt-protect-group";
prefix "vnt-protect-grp";
import ietf-inet-types {
prefix inet;
}
import ietf-yang-types {
prefix yang;
}
import ietf-vnt {
prefix vnt;
}
organization
"Huawei Technologies";
Fu, et al. Expires May 1, 2017 [Page 13]
Internet-Draft October 2016
contact
"fupengcheng@huawei.com";
description
"The YANG module defines vnt protect group.";
revision 2016-10-28 {
description "Initial revision.";
}
/* Main blocks */
container vnt-protect-groups {
description
"vnt protect groups.";
list vnt-protect-group {
key "group-id";
description
"The list of vnt protect groups.";
leaf group-id {
type uint32;
description
"Id of vnt protect group.";
}
leaf group-name {
type string;
description
"Name of vnt protect group.";
}
leaf group-type {
type enumeration {
enum "1:1" {
description
"1:1 type.";
}
enum "n:1" {
description
"n:1 type";
}
}
description
"type of vnt protect group."
}
list work-vnt-list {
Fu, et al. Expires May 1, 2017 [Page 14]
Internet-Draft October 2016
type vnt:vnts;
description
"work vnt list.";
}
list protect-vnt-list {
type vnt:vnts;
description
"protect vnt list.";
}
leaf is-autoaction {
type boolean;
description
"if it is autoaction.";
}
leaf is-return {
type boolean;
description
"if it need return.";
}
}
}
}
(postamble)
6. IANA Considerations
This document makes no request of IANA.
Note to RFC Editor: this section may be removed on publication as an
RFC.
7. Security Considerations
8. Acknowledgements
9. Normative References
[I-D.ietf-teas-actn-framework]
Ceccarelli, D. and Y. Lee, "Framework for Abstraction and
Control of Traffic Engineered Networks", draft-ietf-teas-
actn-framework-01 (work in progress), October 2016.
Fu, et al. Expires May 1, 2017 [Page 15]
Internet-Draft October 2016
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
Authors' Addresses
Pengcheng FU
Huawei Technologies
Email: fupengcheng@huawei.com
Jianzhong FU
Huawei Technologies
Email: fujianzhong@huawei.com
Aijun.Wang
China Telecom
Email: wangaj@ctbri.com.cn
Ruiquan Jing
China Telecom
Email: jingrq@ctbri.com.cn
Fu, et al. Expires May 1, 2017 [Page 16]