draft-ietf-ccamp-otn-tunnel-model-04.txt   draft-ietf-ccamp-otn-tunnel-model-05.txt 
CCAMP Working Group H. Zheng CCAMP Working Group H. Zheng
Internet-Draft A. Guo Internet-Draft A. Guo
Intended status: Standards Track I. Busi Intended status: Standards Track I. Busi
Expires: February 11, 2019 Huawei Technologies Expires: February 24, 2019 Huawei Technologies
A. Sharma A. Sharma
Google Google
R. Rao R. Rao
Infinera Infinera
S. Belotti S. Belotti
Nokia Nokia
V. Lopez V. Lopez
Telefonica Telefonica
Y. Li Y. Li
China Mobile China Mobile
Y. Xu Y. Xu
CAICT CAICT
August 10, 2018 August 23, 2018
OTN Tunnel YANG Model OTN Tunnel YANG Model
draft-ietf-ccamp-otn-tunnel-model-04 draft-ietf-ccamp-otn-tunnel-model-05
Abstract Abstract
This document describes the YANG data model for OTN Tunnels. This document describes the YANG data model for OTN Tunnels.
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 11, 2019. This Internet-Draft will expire on February 24, 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 21 skipping to change at page 2, line 21
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology and Notations . . . . . . . . . . . . . . . . . . 2 2. Terminology and Notations . . . . . . . . . . . . . . . . . . 2
3. OTN Tunnel Model Description . . . . . . . . . . . . . . . . 3 3. OTN Tunnel Model Description . . . . . . . . . . . . . . . . 3
3.1. Overview of OTN Tunnel Model . . . . . . . . . . . . . . 3 3.1. Overview of OTN Tunnel Model . . . . . . . . . . . . . . 3
3.2. OTN-specific Parameters in Tunnel Model . . . . . . . . . 4 3.2. OTN-specific Parameters in Tunnel Model . . . . . . . . . 3
3.3. OTN Path Compute RPC . . . . . . . . . . . . . . . . . . 4 3.3. OTN Path Compute RPC . . . . . . . . . . . . . . . . . . 4
4. OTN Tunnel YANG Tree . . . . . . . . . . . . . . . . . . . . 4 4. OTN Tunnel YANG Tree . . . . . . . . . . . . . . . . . . . . 4
5. OTN Tunnel YANG Code . . . . . . . . . . . . . . . . . . . . 21 5. OTN Tunnel YANG Code . . . . . . . . . . . . . . . . . . . . 21
6. OTN Types YANG Code . . . . . . . . . . . . . . . . . . . . . 48 6. OTN Types YANG Code . . . . . . . . . . . . . . . . . . . . . 48
7. Security Considerations . . . . . . . . . . . . . . . . . . . 57 7. Security Considerations . . . . . . . . . . . . . . . . . . . 57
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 58 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 59
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 58 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 59
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 58 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 59
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 59 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 60
11.1. Normative References . . . . . . . . . . . . . . . . . . 59 11.1. Normative References . . . . . . . . . . . . . . . . . . 60
11.2. Informative References . . . . . . . . . . . . . . . . . 60 11.2. Informative References . . . . . . . . . . . . . . . . . 61
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 61 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 62
1. Introduction 1. Introduction
OTN transport networks can carry various types of client services. OTN transport networks can carry various types of client services.
In many cases, the client signal is carried over an OTN tunnel across In many cases, the client signal is carried over an OTN tunnel across
connected domains in a multi-domain network. These OTN services can connected domains in a multi-domain network. These OTN services can
either be transported or switched in the OTN network. If an OTN either be transported or switched in the OTN network. If an OTN
tunnel is switched, then additional parameters need to be provided to tunnel is switched, then additional parameters need to be provided to
create a Mux OTN service. create a Mux OTN service.
This document provides YANG model for creating OTN tunnel. The model This document provides YANG model for creating OTN tunnel. The model
augments the TE Tunnel model. augments the TE Tunnel model.
2. Terminology and Notations 2. Terminology and Notations
A simplified graphical representation of the data model is used in A simplified graphical representation of the data model is used in
this document. The meaning of the symbols in the YANG data tree this document. The meaning of the symbols in the YANG data tree
presented later in this draft is defined in presented later in this draft is defined in [RFC8340]. They are
provided below for reference.
[I-D.ietf-netmod-yang-tree-diagrams]. They are provided below for
reference.
o Brackets "[" and "]" enclose list keys. o Brackets "[" and "]" enclose list keys.
o Abbreviations before data node names: "rw" means configuration o Abbreviations before data node names: "rw" means configuration
(read-write) and "ro" state data (read-only). (read-write) and "ro" state data (read-only).
o Symbols after data node names: "?" means an optional node, "!" o Symbols after data node names: "?" means an optional node, "!"
means a presence container, and "*" denotes a list and leaf-list. means a presence container, and "*" denotes a list and leaf-list.
o Parentheses enclose choice and case nodes, and case nodes are also o Parentheses enclose choice and case nodes, and case nodes are also
skipping to change at page 21, line 42 skipping to change at page 21, line 36
| +--:(generic) | +--:(generic)
| | +--ro generic? rt-types:generalized-label | | +--ro generic? rt-types:generalized-label
| +--:(otn) | +--:(otn)
| +--ro tpn? uint16 | +--ro tpn? uint16
| +--ro tsg? identityref | +--ro tsg? identityref
| +--ro ts-list? string | +--ro ts-list? string
+--ro direction? te-label-direction +--ro direction? te-label-direction
5. OTN Tunnel YANG Code 5. OTN Tunnel YANG Code
<CODE BEGINS>file "ietf-otn-tunnel@2018-08-10.yang" <CODE BEGINS>file "ietf-otn-tunnel@2018-08-23.yang"
module ietf-otn-tunnel { module ietf-otn-tunnel {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-otn-tunnel"; namespace "urn:ietf:params:xml:ns:yang:ietf-otn-tunnel";
prefix "otn-tunnel"; prefix "otn-tunnel";
import ietf-te { import ietf-te {
prefix "te"; prefix "te";
reference
"I-D.ietf-teas-yang-te: A YANG Data Model for Traffic Engineering
Tunnels and Interfaces";
} }
import ietf-otn-types { import ietf-otn-types {
prefix "otn-types"; prefix "otn-types";
reference
"module ietf-otn-types in this Document";
} }
import ietf-te-types { import ietf-te-types {
prefix "te-types"; prefix "te-types";
reference
"I-D.ietf-teas-yang-te: A YANG Data Model for Traffic Engineering
Tunnels and Interfaces";
} }
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
reference "RFC 6991: Common YANG Data Types";
} }
organization organization
"IETF CCAMP Working Group"; "IETF CCAMP Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/ccamp/> "WG Web: <http://tools.ietf.org/wg/ccamp/>
WG List: <mailto:ccamp@ietf.org> WG List: <mailto:ccamp@ietf.org>
Editor: Haomian Zheng Editor: Haomian Zheng
<mailto:zhenghaomian@huawei.com> <mailto:zhenghaomian@huawei.com>
skipping to change at page 23, line 6 skipping to change at page 23, line 10
Editor: Victor Lopez Editor: Victor Lopez
<mailto:victor.lopezalvarez@telefonica.com> <mailto:victor.lopezalvarez@telefonica.com>
Editor: Yunbo Li Editor: Yunbo Li
<mailto:liyunbo@chinamobile.com> <mailto:liyunbo@chinamobile.com>
Editor: Yunbin Xu Editor: Yunbin Xu
<mailto:xuyunbin@ritt.cn>"; <mailto:xuyunbin@ritt.cn>";
description description
"This module defines a model for OTN Tunnel Services."; "This module defines a model for OTN Tunnel Services.
revision "2018-08-10" { Copyright (c) 2018 IETF Trust and the persons
identified as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
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).";
revision "2018-08-23" {
description description
"Revision 0.7"; "Initial Revision";
reference reference
"draft-ietf-ccamp-otn-tunnel-model-04"; "RFC XXXX: OTN Tunnel YANG Model";
// RFC Ed.: replace XXXX with actual RFC number, update date
// information and remove this note
} }
/* /*
* Groupings * Groupings
*/ */
grouping otn-tunnel-attributes { grouping otn-tunnel-attributes {
description "Parameters for OTN tunnel"; description "Parameters for OTN tunnel";
leaf src-client-signal { leaf src-client-signal {
skipping to change at page 48, line 4 skipping to change at page 48, line 42
type string; type string;
description "TE path name"; description "TE path name";
} }
uses p2p-path-ero; uses p2p-path-ero;
} }
} }
} }
} }
} }
} }
<CODE ENDS> <CODE ENDS>
6. OTN Types YANG Code 6. OTN Types YANG Code
<CODE BEGINS> file "ietf-otn-types@2018-08-10.yang" <CODE BEGINS> file "ietf-otn-types@2018-08-23.yang"
module ietf-otn-types { module ietf-otn-types {
namespace "urn:ietf:params:xml:ns:yang:ietf-otn-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-otn-types";
prefix "otn-types"; prefix "otn-types";
organization organization
"IETF CCAMP Working Group"; "IETF CCAMP Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/ccamp/> "WG Web: <http://tools.ietf.org/wg/ccamp/>
WG List: <mailto:ccamp@ietf.org> WG List: <mailto:ccamp@ietf.org>
skipping to change at page 49, line 5 skipping to change at page 49, line 43
Editor: Yunbo Li Editor: Yunbo Li
<mailto:liyunbo@chinamobile.com> <mailto:liyunbo@chinamobile.com>
Editor: Yunbin Xu Editor: Yunbin Xu
<mailto:xuyunbin@ritt.cn>"; <mailto:xuyunbin@ritt.cn>";
description description
"This module defines OTN types."; "This module defines OTN types.";
revision "2018-08-10" { revision "2018-08-23" {
description description
"Revision 0.8"; "Initial Revision";
reference reference
"draft-ietf-ccamp-otn-tunnel-model-04"; "RFC XXXX: OTN Tunnel YANG Model";
// RFC Ed.: replace XXXX with actual RFC number, update date
// information and remove this note
} }
identity tributary-slot-granularity { identity tributary-slot-granularity {
description description
"Tributary slot granularity"; "Tributary slot granularity";
reference reference
"G.709/Y.1331, February 2016: Interfaces for the Optical "G.709/Y.1331, February 2016: Interfaces for the Optical
Transport Network (OTN)"; Transport Network (OTN)";
} }
identity tsg-1.25G { identity tsg-1.25G {
base tributary-slot-granularity; base tributary-slot-granularity;
skipping to change at page 55, line 27 skipping to change at page 56, line 19
"G.709/Y.1331, February 2016: Interfaces for the "G.709/Y.1331, February 2016: Interfaces for the
Optical Transport Network (OTN)"; Optical Transport Network (OTN)";
} }
leaf priority { leaf priority {
type uint8; type uint8;
description "priority."; description "priority.";
} }
} }
/* Note: Suggest to be changed as otn-label-range; /* Note: Suggest to be changed as otn-label-range;
otn-topology/tunnel also need change */ otn-topology/tunnel also need change */
grouping otn-link-label { grouping otn-link-label {
description "link label information for OTN, for label-start/end"; description "link label information for OTN, for label-start/end";
choice otn-label-type { choice otn-label-type {
description description
"OTN label range type, either TPN range or TS range"; "OTN label range type, either TPN range or TS range";
case tributary-port { case tributary-port {
leaf tpn { leaf tpn {
type uint16 { type uint16 {
range "1..4095"; range "1..4095";
} }
skipping to change at page 56, line 12 skipping to change at page 57, line 6
"Tributary Slot Number. Applicable in case of mux services."; "Tributary Slot Number. Applicable in case of mux services.";
reference reference
"RFC7139: GMPLS Signaling Extensions for Control of Evolving "RFC7139: GMPLS Signaling Extensions for Control of Evolving
G.709 Optical Transport Networks."; G.709 Optical Transport Networks.";
} }
} }
} }
} }
/* Note: Suggest to be changed as otn-label; /* Note: Suggest to be changed as otn-label;
otn-topology/tunnel also need change */ otn-topology/tunnel also need change */
grouping otn-path-label { grouping otn-path-label {
description "label information for OTN, for label-hop"; description "label information for OTN, for label-hop";
leaf tpn { leaf tpn {
type uint16 { type uint16 {
range "1..4095"; range "1..4095";
} }
description description
"Tributary Port Number. Applicable in case of mux services."; "Tributary Port Number. Applicable in case of mux services.";
reference reference
"RFC7139: GMPLS Signaling Extensions for Control of Evolving "RFC7139: GMPLS Signaling Extensions for Control of Evolving
skipping to change at page 58, line 14 skipping to change at page 59, line 8
+---x otn-te-tunnel-path-compute This path compute RPC provides a +---x otn-te-tunnel-path-compute This path compute RPC provides a
mechanism to enable the client to query and/or subscribe on the mechanism to enable the client to query and/or subscribe on the
tunnel to be notified whenever it changes. Thus path computation is tunnel to be notified whenever it changes. Thus path computation is
only for the client reference, with no real deploy or resource only for the client reference, with no real deploy or resource
reservation. reservation.
8. IANA Considerations 8. IANA Considerations
It is proposed that IANA should assign new URIs from the "IETF XML It is proposed that IANA should assign new URIs from the "IETF XML
Registry" [RFC3688] as follows: URI: Registry" [RFC3688] as follows:
urn:ietf:params:xml:ns:yang:ietf-otn-tunnel Registrant Contact: The
IESG XML: N/A; the requested URI is an XML namespace. URI: URI: urn:ietf:params:xml:ns:yang:ietf-otn-tunnel
urn:ietf:params:xml:ns:yang:ietf-otn-types Registrant Contact: The Registrant Contact: The IESG
IESG XML: N/A; the requested URI is an XML namespace. This document XML: N/A; the requested URI is an XML namespace.
registers following YANG modules in the YANG Module Names registry
[RFC7950]. name: ietf-otn-tunnel namespace: URI: urn:ietf:params:xml:ns:yang:ietf-otn-types
urn:ietf:params:xml:ns:yang:ietf-otn-tunnel prefix: otn-tunnel Registrant Contact: The IESG
reference: RFC XXXX name: ietf-otn-types namespace: XML: N/A; the requested URI is an XML namespace.
urn:ietf:params:xml:ns:yang:ietf-otn-types prefix: otn-types
reference: RFC XXXX This document registers following YANG modules in the YANG Module
Names registry [RFC7950].
name: ietf-otn-tunnel
namespace: urn:ietf:params:xml:ns:yang:ietf-otn-tunnel
prefix: otn-tunnel
reference: RFC XXXX
name: ietf-otn-types
namespace: urn:ietf:params:xml:ns:yang:ietf-otn-types
prefix: otn-types
reference: RFC XXXX
9. Acknowledgements 9. Acknowledgements
TBD. TBD.
10. Contributors 10. Contributors
Dieter Beller Dieter Beller
Nokia Nokia
Email: dieter.beller@nokia.com Email: dieter.beller@nokia.com
skipping to change at page 59, line 28 skipping to change at page 60, line 35
Xu, "Transport Northbound Interface Applicability Xu, "Transport Northbound Interface Applicability
Statement", draft-ietf-ccamp-transport-nbi-app- Statement", draft-ietf-ccamp-transport-nbi-app-
statement-02 (work in progress), July 2018. statement-02 (work in progress), July 2018.
[I-D.ietf-teas-yang-te] [I-D.ietf-teas-yang-te]
Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., and Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., and
I. Bryskin, "A YANG Data Model for Traffic Engineering I. Bryskin, "A YANG Data Model for Traffic Engineering
Tunnels and Interfaces", draft-ietf-teas-yang-te-16 (work Tunnels and Interfaces", draft-ietf-teas-yang-te-16 (work
in progress), July 2018. in progress), July 2018.
[ITU-T] ITU-, T., "SERIES G: TRANSMISSION SYSTEMS AND MEDIA,
DIGITAL SYSTEMS AND NETWORKS; Digital networks; Interfaces
for the optical transport network", ITU-T Rec. G.709v5 ,
June 2016.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, (TLS) Protocol Version 1.2", RFC 5246,
DOI 10.17487/RFC5246, August 2008, DOI 10.17487/RFC5246, August 2008,
<https://www.rfc-editor.org/info/rfc5246>. <https://www.rfc-editor.org/info/rfc5246>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
skipping to change at page 60, line 26 skipping to change at page 61, line 40
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>. <https://www.rfc-editor.org/info/rfc8040>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>. <https://www.rfc-editor.org/info/rfc8342>.
11.2. Informative References 11.2. Informative References
[I-D.ietf-netmod-yang-tree-diagrams]
Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft-
ietf-netmod-yang-tree-diagrams-06 (work in progress),
February 2018.
[I-D.ietf-teas-actn-yang] [I-D.ietf-teas-actn-yang]
Lee, Y., zhenghaomian@huawei.com, z., Ceccarelli, D., Lee, Y., zhenghaomian@huawei.com, z., Ceccarelli, D.,
Yoon, B., and S. Belotti, "Applicability of YANG models Yoon, B., Dios, O., Shin, J., and S. Belotti,
for Abstraction and Control of Traffic Engineered "Applicability of YANG models for Abstraction and Control
Networks", draft-ietf-teas-actn-yang-01 (work in of Traffic Engineered Networks", draft-ietf-teas-actn-
progress), February 2018. yang-02 (work in progress), August 2018.
[RFC7062] Zhang, F., Ed., Li, D., Li, H., Belotti, S., and D. [RFC7062] Zhang, F., Ed., Li, D., Li, H., Belotti, S., and D.
Ceccarelli, "Framework for GMPLS and PCE Control of G.709 Ceccarelli, "Framework for GMPLS and PCE Control of G.709
Optical Transport Networks", RFC 7062, Optical Transport Networks", RFC 7062,
DOI 10.17487/RFC7062, November 2013, DOI 10.17487/RFC7062, November 2013,
<https://www.rfc-editor.org/info/rfc7062>. <https://www.rfc-editor.org/info/rfc7062>.
[RFC7138] Ceccarelli, D., Ed., Zhang, F., Belotti, S., Rao, R., and [RFC7138] Ceccarelli, D., Ed., Zhang, F., Belotti, S., Rao, R., and
J. Drake, "Traffic Engineering Extensions to OSPF for J. Drake, "Traffic Engineering Extensions to OSPF for
GMPLS Control of Evolving G.709 Optical Transport GMPLS Control of Evolving G.709 Optical Transport
Networks", RFC 7138, DOI 10.17487/RFC7138, March 2014, Networks", RFC 7138, DOI 10.17487/RFC7138, March 2014,
<https://www.rfc-editor.org/info/rfc7138>. <https://www.rfc-editor.org/info/rfc7138>.
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>.
Authors' Addresses Authors' Addresses
Haomian Zheng Haomian Zheng
Huawei Technologies Huawei Technologies
F3 R&D Center, Huawei Industrial Base, Bantian, Longgang District F3 R&D Center, Huawei Industrial Base, Bantian, Longgang District
Shenzhen, Guangdong 518129 Shenzhen, Guangdong 518129
P.R.China P.R.China
Email: zhenghaomian@huawei.com Email: zhenghaomian@huawei.com
 End of changes. 30 change blocks. 
49 lines changed or deleted 87 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/