< draft-zhang-ccamp-l1-topo-yang-06.txt   draft-zhang-ccamp-l1-topo-yang-07.txt >
CCAMP Working Group X. Zhang CCAMP Working Group H. Zheng
Internet-Draft K. Xiang Internet-Draft Z. Fan
Intended status: Standards Track Huawei Technologies Intended status: Standards Track Huawei Technologies
Expires: September 9, 2017 A. Sharma Expires: October 27, 2017 A. Sharma
Infinera Google
X. Liu X. Liu
Ericsson Jabil
March 08, 2017 April 25, 2017
A YANG Data Model for Optical Transport Network Topology A YANG Data Model for Optical Transport Network Topology
draft-zhang-ccamp-l1-topo-yang-06 draft-zhang-ccamp-l1-topo-yang-07
Abstract Abstract
A transport network is a server-layer network designed to provide A transport network is a server-layer network designed to provide
connectivity services for a client-layer network to carry the client connectivity services for a client-layer network to carry the client
traffic transparently across the server-layer network resources. A traffic transparently across the server-layer network resources. A
transport network can be constructed from equipments utilizing any of transport network can be constructed from equipments utilizing any of
a number of different transport technologies such as the evolving a number of different transport technologies such as the evolving
Optical Transport Networks (OTN) or packet transport as provided by Optical Transport Networks (OTN) or packet transport as provided by
the MPLS-Transport Profile (MPLS-TP). the MPLS-Transport Profile (MPLS-TP).
skipping to change at page 2, line 10 skipping to change at page 2, line 10
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 9, 2017. This Internet-Draft will expire on October 27, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 34 skipping to change at page 2, line 34
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 . . . . . . . . . . . . . . . . . . 3 2. Terminology and Notations . . . . . . . . . . . . . . . . . . 3
3. YANG Data Model for OTN Topology . . . . . . . . . . . . . . 4 3. YANG Data Model for OTN Topology . . . . . . . . . . . . . . 4
3.1. the YANG Tree . . . . . . . . . . . . . . . . . . . . . . 4 3.1. the YANG Tree . . . . . . . . . . . . . . . . . . . . . . 4
3.2. Explanation of the OTN Topology Data Model . . . . . . . 5 3.2. Explanation of the OTN Topology Data Model . . . . . . . 5
3.3. The YANG Code . . . . . . . . . . . . . . . . . . . . . . 6 3.3. The YANG Code . . . . . . . . . . . . . . . . . . . . . . 5
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
5. Manageability Considerations . . . . . . . . . . . . . . . . 13 5. Manageability Considerations . . . . . . . . . . . . . . . . 13
6. Security Considerations . . . . . . . . . . . . . . . . . . . 13 6. Security Considerations . . . . . . . . . . . . . . . . . . . 13
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 13 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 13
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
9.1. Normative References . . . . . . . . . . . . . . . . . . 14 9.1. Normative References . . . . . . . . . . . . . . . . . . 14
9.2. Informative References . . . . . . . . . . . . . . . . . 15 9.2. Informative References . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
skipping to change at page 6, line 7 skipping to change at page 5, line 48
per priority level. For example, for a ODU3 link, it may advertise per priority level. For example, for a ODU3 link, it may advertise
32*ODU0, 16*ODU1, 4*ODU2 available, assuming only a single priority 32*ODU0, 16*ODU1, 4*ODU2 available, assuming only a single priority
level is supported. If one of ODU2 resource is taken to establish a level is supported. If one of ODU2 resource is taken to establish a
ODU path, then the availability of this ODU link is updated as ODU path, then the availability of this ODU link is updated as
24*ODU0, 12*ODU1, 3*ODU2 available. If there are equipment hardware 24*ODU0, 12*ODU1, 3*ODU2 available. If there are equipment hardware
limitations, then a subset of potential ODU type SHALL be advertised. limitations, then a subset of potential ODU type SHALL be advertised.
For instance, an ODU3 link may only support 4*ODU2. For instance, an ODU3 link may only support 4*ODU2.
3.3. The YANG Code 3.3. The YANG Code
<CODE BEGINS> file " ietf-otn-topology@2017-03-08.yang" <CODE BEGINS> file "ietf-otn-topology@2017-04-25.yang"
module ietf-otn-topology { module ietf-otn-topology {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-otn-topology"; namespace "urn:ietf:params:xml:ns:yang:ietf-otn-topology";
prefix "otntopo"; prefix "otntopo";
import ietf-network { import ietf-network {
prefix "nd"; prefix "nd";
} }
skipping to change at page 6, line 38 skipping to change at page 6, line 32
prefix "tran-types"; prefix "tran-types";
} }
organization organization
"Internet Engineering Task Force (IETF) CCAMP WG"; "Internet Engineering Task Force (IETF) CCAMP WG";
contact contact
" "
WG List: <mailto:ccamp@ietf.org> WG List: <mailto:ccamp@ietf.org>
ID-draft editor: ID-draft editor:
Xian ZHANG (zhang.xian@huawei.com); Haomian Zheng (zhenghaomian@huawei.com);
Anurag Sharma (AnSharma@infinera.com); Zheyu Fan (fanzheyu2@huawei.com);
Anurag Sharma (ansha@google.com);
Xufeng Liu (Xufeng_Liu@jabil.com)
"; ";
description description
"This module defines a protocol independent Layer 1/ODU "This module defines a protocol independent Layer 1/ODU
topology data model."; topology data model.";
revision 2017-03-08 { revision 2017-04-25 {
description description
"Revision 0.2"; "Revision 0.3";
reference reference
"draft-zhang-ccamp-l1-topo-yang-05.txt"; "draft-zhang-ccamp-l1-topo-yang-07.txt";
} }
/* /*
typedef typedef
*/ */
typedef adaptation-type { typedef adaptation-type {
type enumeration { type enumeration {
enum CBR { enum CBR {
description "Constant Bit Rate."; description "Constant Bit Rate.";
} }
enum ATMvp { enum ATMvp {
description "ATM VP."; description "ATM VP.";
} }
enum GFP { enum GFP {
description "Generic Framing Procedure."; description "Generic Framing Procedure.";
skipping to change at page 13, line 22 skipping to change at page 13, line 22
6. Security Considerations 6. Security Considerations
The data following the model defined in this draft is exchanged via, The data following the model defined in this draft is exchanged via,
for example, the interface between an orchestrator and a transport for example, the interface between an orchestrator and a transport
network controller. The security concerns mentioned in network controller. The security concerns mentioned in
[I-D.ietf-teas-yang-te-topo] for using ietf-te-topology.yang model [I-D.ietf-teas-yang-te-topo] for using ietf-te-topology.yang model
also applies to this draft. also applies to this draft.
The YANG module defined in this document can be accessed via the The YANG module defined in this document can be accessed via the
RESTCONF protocol defined in [I-D.ietf-netconf-restconf], or maybe RESTCONF protocol defined in [RFC8040], or maybe via the NETCONF
via the NETCONF protocol [RFC6241]. protocol [RFC6241].
There are a number of data nodes defined in the YANG module which are There are a number of data nodes defined in the YANG module which are
writable/creatable/deletable (i.e., config true, which is the writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., POST) to these in some network environments. Write operations (e.g., POST) to these
data nodes without proper protection can have a negative effect on data nodes without proper protection can have a negative effect on
network operations. network operations.
Editors note: to list specific subtrees and data nodes and their Editors note: to list specific subtrees and data nodes and their
sensitivity/vulnerability. sensitivity/vulnerability.
skipping to change at page 13, line 46 skipping to change at page 13, line 46
We would like to thank Igor Bryskin, Zhe Liu, Dieter Beller and We would like to thank Igor Bryskin, Zhe Liu, Dieter Beller and
Daniele Ceccarelli for their comments and discussions. Daniele Ceccarelli for their comments and discussions.
8. Contributors 8. Contributors
Baoquan Rao Baoquan Rao
Huawei Technologies Huawei Technologies
Email: raobaoquan@huawei.com Email: raobaoquan@huawei.com
Sergio Belotti Xian Zhang
Alcatel Lucent Huawei Technologies
Email: Sergio.belotti@alcatel-lucent.com Email: zhang.xian@huawei.com
Sergio Belotti
Nokia
Email: sergio.belotti@nokia.com
Huub van Helvoort Huub van Helvoort
Hai Gaoming BV Hai Gaoming BV
the Netherlands the Netherlands
Email: huubatwork@gmail.com Email: huubatwork@gmail.com
9. References 9. References
9.1. Normative References 9.1. Normative References
[I-D.ietf-netconf-restconf]
Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", draft-ietf-netconf-restconf-18 (work in
progress), October 2016.
[I-D.ietf-netmod-rfc6087bis]
Bierman, A., "Guidelines for Authors and Reviewers of YANG
Data Model Documents", draft-ietf-netmod-rfc6087bis-12
(work in progress), March 2017.
[I-D.ietf-teas-yang-te-topo] [I-D.ietf-teas-yang-te-topo]
Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and
O. Dios, "YANG Data Model for TE Topologies", draft-ietf- O. Dios, "YANG Data Model for TE Topologies", draft-ietf-
teas-yang-te-topo-06 (work in progress), October 2016. teas-yang-te-topo-08 (work in progress), March 2017.
[I-D.sharma-ccamp-otn-tunnel-model] [I-D.sharma-ccamp-otn-tunnel-model]
ansharma@infinera.com, a., Rao, R., and X. Zhang, "OTN Zhang, X., xiangkun, x., ansharma@infinera.com, a., and R.
Tunnel YANG Model", draft-sharma-ccamp-otn-tunnel-model-00 Rao, "OTN Tunnel YANG Model", draft-sharma-ccamp-otn-
(work in progress), October 2016. tunnel-model-01 (work in progress), March 2017.
[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>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010,
<http://www.rfc-editor.org/info/rfc6020>. <http://www.rfc-editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<http://www.rfc-editor.org/info/rfc6241>. <http://www.rfc-editor.org/info/rfc6241>.
[RFC7062] Zhang, F., Ed., Li, D., Li, H., Belotti, S., and D.
Ceccarelli, "Framework for GMPLS and PCE Control of G.709
Optical Transport Networks", RFC 7062,
DOI 10.17487/RFC7062, November 2013,
<http://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,
<http://www.rfc-editor.org/info/rfc7138>. <http://www.rfc-editor.org/info/rfc7138>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<http://www.rfc-editor.org/info/rfc8040>.
9.2. Informative References 9.2. Informative References
[I-D.ietf-ccamp-wson-yang] [I-D.ietf-ccamp-wson-yang]
Lee, Y., Dhody, D., Zhang, X., Guo, A., Lopezalvarez, V., Lee, Y., Dhody, D., Zhang, X., Guo, A., Lopezalvarez, V.,
King, D., and B. Yoon, "A Yang Data Model for WSON Optical King, D., and B. Yoon, "A Yang Data Model for WSON Optical
Networks", draft-ietf-ccamp-wson-yang-05 (work in Networks", draft-ietf-ccamp-wson-yang-05 (work in
progress), February 2017. progress), February 2017.
[I-D.ietf-netmod-rfc6087bis]
Bierman, A., "Guidelines for Authors and Reviewers of YANG
Data Model Documents", draft-ietf-netmod-rfc6087bis-12
(work in progress), March 2017.
[I-D.vergara-ccamp-flexigrid-yang] [I-D.vergara-ccamp-flexigrid-yang]
Madrid, U., Perdices, D., Lopezalvarez, V., Dios, O., Madrid, U., Perdices, D., Lopezalvarez, V., Dios, O.,
King, D., Lee, Y., and G. Galimberti, "YANG data model for King, D., Lee, Y., and G. Galimberti, "YANG data model for
Flexi-Grid Optical Networks", draft-vergara-ccamp- Flexi-Grid Optical Networks", draft-vergara-ccamp-
flexigrid-yang-04 (work in progress), March 2017. flexigrid-yang-04 (work in progress), March 2017.
[RFC7062] Zhang, F., Ed., Li, D., Li, H., Belotti, S., and D.
Ceccarelli, "Framework for GMPLS and PCE Control of G.709
Optical Transport Networks", RFC 7062,
DOI 10.17487/RFC7062, November 2013,
<http://www.rfc-editor.org/info/rfc7062>.
Authors' Addresses Authors' Addresses
Xian Zhang Haomian Zheng
Huawei Technologies Huawei Technologies
F3-5-B 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: zhang.xian@huawei.com Email: zhenghaomian@huawei.com
Kun Xiang Zheyu Fan
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: xiangkun@huawei.com Email: fanzheyu2@huawei.com
Anurag Sharma Anurag Sharma
Infinera Google
1600 Amphitheatre Parkway
Mountain View, CA 94043
Email: ansha@google.com
Email: ansharma@infinera.com
Xufeng Liu Xufeng Liu
Ericsson Jabil
Email: xufeng.liu@ericsson.com Email: Xufeng_Liu@jabil.com
 End of changes. 32 change blocks. 
50 lines changed or deleted 56 lines changed or added

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