draft-ietf-ccamp-microwave-framework-01.txt   draft-ietf-ccamp-microwave-framework-02.txt 
CCAMP WG J. Ahlberg CCAMP WG J. Ahlberg
Internet-Draft Ericsson AB Internet-Draft Ericsson AB
Intended status: Informational LM. Contreras Intended status: Informational LM. Contreras
Expires: December 22, 2017 TID Expires: April 23, 2018 TID
A. Ye Min M.Ye
Huawei Huawei Technologies CO., Ltd
M. Vaupotic M. Vaupotic
Aviat Networks Aviat Networks
J. Tantsura J. Tantsura
Individual Individual
K. Kawada K. Kawada
NEC Corporation NEC Corporation
X. Li X. Li
NEC Laboratories Europe NEC Laboratories Europe
I. Akiyoshi I. Akiyoshi
NEC NEC
CJ. Bernardos CJ. Bernardos
UC3M UC3M
June 20, 2017 D. Spreafico
Nokia - IT
October 20, 2017
A framework for Management and Control of microwave and A framework for Management and Control of microwave and
millimeter wave interface parameters millimeter wave interface parameters
draft-ietf-ccamp-microwave-framework-01 draft-ietf-ccamp-microwave-framework-02
Abstract Abstract
To ensure an efficient data transport, meeting the requirements To ensure an efficient data transport, meeting the requirements
requested by today's transport services, the unification of control requested by today's transport services, the unification of control
and management of microwave and millimeter wave radio link interfaces and management of microwave and millimeter wave radio link interfaces
is a precondition for seamless multilayer networking and automated is a precondition for seamless multilayer networking and automated
network wide provisioning and operation. network wide provisioning and operation.
This document describes the required characteristics and use cases This document describes the required characteristics and use cases
skipping to change at page 1, line 48 skipping to change at page 1, line 50
management model that is aligned with how other packet technology management model that is aligned with how other packet technology
interfaces in a microwave/millimeter wave node are modeled, the need interfaces in a microwave/millimeter wave node are modeled, the need
to support core parameters and at the same time allow for optional to support core parameters and at the same time allow for optional
product/feature specific parameters supporting new, unique innovative product/feature specific parameters supporting new, unique innovative
features until they have become mature enough to be included in the features until they have become mature enough to be included in the
standardized model. standardized model.
The purpose is to create a framework for identification of the The purpose is to create a framework for identification of the
necessary information elements and definition of a YANG Data Model necessary information elements and definition of a YANG Data Model
for control and management of the radio link interfaces in a for control and management of the radio link interfaces in a
microwave/millimeter wave node. microwave/millimeter wave node. Some part of the resulting model MAY
be generic which COULD also be used by other technology.
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 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 December 22, 2017. This Internet-Draft will expire on April 23, 2018.
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 3, line 42 skipping to change at page 3, line 42
6. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 12 6. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 12
7. Gap Analysis on Models . . . . . . . . . . . . . . . . . . . 13 7. Gap Analysis on Models . . . . . . . . . . . . . . . . . . . 13
7.1. Microwave Radio Link Functionality . . . . . . . . . . . 13 7.1. Microwave Radio Link Functionality . . . . . . . . . . . 13
7.2. Generic Functionality . . . . . . . . . . . . . . . . . . 14 7.2. Generic Functionality . . . . . . . . . . . . . . . . . . 14
7.3. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 16 7.3. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 16
8. Security Considerations . . . . . . . . . . . . . . . . . . . 16 8. Security Considerations . . . . . . . . . . . . . . . . . . . 16
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
10.1. Normative References . . . . . . . . . . . . . . . . . 17 10.1. Normative References . . . . . . . . . . . . . . . . . 17
10.2. Informative References . . . . . . . . . . . . . . . . 17 10.2. Informative References . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
1. Terminology and Definitions 1. Terminology and Definitions
Microwave is a band of spectrum with wavelengths ranging from 1 Microwave is a band of spectrum with wavelengths ranging from 1
meter to 1 millimeter and with frequencies ranging between 300 MHz meter to 1 millimeter and with frequencies ranging between 300 MHz
and 300 GHz. Microwave radio technology is widely used for point-to- and 300 GHz. Microwave radio technology is widely used for point-to-
point telecommunications because of their small wavelength that point telecommunications because of their small wavelength that
allows conveniently-sized antennas to direct them in narrow beams, allows conveniently-sized antennas to direct them in narrow beams,
and their comparatively higher frequencies that allows broad and their comparatively higher frequencies that allows broad
bandwidth and high data transmission rates. bandwidth and high data transmission rates.
skipping to change at page 6, line 13 skipping to change at page 6, line 13
future when demands on capacity and packet features increases. future when demands on capacity and packet features increases.
Microwave is already today able to fully support the capacity needs Microwave is already today able to fully support the capacity needs
of a backhaul in a radio access network and will evolve to support of a backhaul in a radio access network and will evolve to support
multiple gigabits in traditional frequency bands and beyond 10 multiple gigabits in traditional frequency bands and beyond 10
gigabits in the millimeter wave. L2 packet features are normally an gigabits in the millimeter wave. L2 packet features are normally an
integrated part of microwave nodes and more advanced L2 & L3 integrated part of microwave nodes and more advanced L2 & L3
features will over time be introduced to support the evolution of features will over time be introduced to support the evolution of
the transport services to be provided by a backhaul/transport the transport services to be provided by a backhaul/transport
network. Note that the wireless access technologies such as 3/4/5G & network. Note that the wireless access technologies such as 3/4/5G &
Wi-Fi are not within the scope of this microwave model work. WiFi are not within the scope of this microwave model work.
The main application for microwave is backhaul for mobile broadband. The main application for microwave is backhaul for mobile broadband.
Those networks will continue to be modernized using a combination of Those networks will continue to be modernized using a combination of
microwave and fiber technologies. The choice of technology is a microwave and fiber technologies. The choice of technology is a
question about fiber presence and cost of ownership, not about question about fiber presence and cost of ownership, not about
capacity limitations in microwave. capacity limitations in microwave.
Open and standardized interfaces are a pre-requisite for efficient Open and standardized interfaces are a pre-requisite for efficient
management of equipment from multiple vendors, integrated in a management of equipment from multiple vendors, integrated in a
single system/controller. This framework addresses management and single system/controller. This framework addresses management and
control of the radio link interface(s) and the relationship to other control of the radio link interface(s) and the relationship to other
packet interfaces, typically to Ethernet interfaces, in a microwave packet interfaces, typically to Ethernet interfaces, in a microwave
node. A radio link provides the transport over the air, using one or node. A radio link provides the transport over the air, using one or
several carriers in aggregated or protected configurations. several carriers in aggregated or protected configurations.
Managing and controlling a transport service over a microwave node Managing and controlling a transport service over a microwave node
involves both radio link and packet functionality. involves both radio link and packet functionality.
Already today there are numerous IETF data models, RFCs and drafts, Already today there are numerous IETF data models, RFCs and drafts,
with technology specific extensions that cover a large part of the with technology specific extensions that cover a large part of the
packet domain. Examples are IP Management [RFC7277], Routing packet domain. Examples are IP Management [RFC7277], Routing
Management [RFC8022] and Provider Bridge [PB-YANG]. Management [RFC8022] and Provider Bridge [PB-YANG] They are based
They are based on RFC 7223 [RFC7223], which is the IETF YANG on RFC 7223 [RFC7223], which is the IETF YANG model for Interface
model for Interface Management, and is an evolution of the SNMP IF- Management, and is an evolution of the SNMP IF-MIB [RFC2863].
MIB [RFC2863].
Since microwave nodes will contain more and more packet Since microwave nodes will contain more and more packet
functionality which is expected to be managed using those models, functionality which is expected to be managed using those models,
there are advantages if radio link interfaces can be modeled and be there are advantages if radio link interfaces can be modeled and be
managed using the same structure and the same approach, specifically managed using the same structure and the same approach, specifically
for use cases in which a microwave node is managed as one common for use cases in which a microwave node are managed as one common
entity including both the radio link and the packet functionality, entity including both the radio link and the packet functionality,
e.g. at basic configuration of node & connections, centralized e.g. at basic configuration of node & connections, centralized
trouble shooting, upgrade and maintenance. All interfaces in a node, trouble shooting, upgrade and maintenance. All interfaces in a node,
irrespective of technology, would then be accessed from the same irrespective of technology, would then be accessed from the same
core model, i.e. RFC 7223, and could be extended with technology core model, i.e. RFC 7223, and could be extended with technology
specific parameters in models augmenting that core model. The specific parameters in models augmenting that core model. The
relationship/connectivity between interfaces could be given by the relationship/connectivity between interfaces could be given by the
physical equipment configuration, e.g. the slot in which the Radio physical equipment configuration, e.g the slot in which the Radio
Link Terminal (modem) is plugged in could be associated with a Link Terminal (modem) is plugged in could be associated with a
specific Ethernet port due to the wiring in the backplane of the specific Ethernet port due to the wiring in the backplane of the
system, or it could be flexible and therefore configured via a system, or it could be flexible and therefore configured via a
management system or controller. management system or controller.
+------------------------------------------------------------------+ +------------------------------------------------------------------+
| Interface [RFC7223] | | Interface [RFC7223] |
| +------------------+ | | +------------------+ |
| |Ethernet Port | | | |Ethernet Port | |
| +------------------+ | | +------------------+ |
skipping to change at page 12, line 10 skipping to change at page 12, line 10
Information and actions required by a manager/operator to Information and actions required by a manager/operator to
investigate and understand the underlying issue to a problem in the investigate and understand the underlying issue to a problem in the
performance and/or functionality of a radio link terminal and the performance and/or functionality of a radio link terminal and the
associated carrier terminations. associated carrier terminations.
6. Requirements 6. Requirements
For managing a microwave node including both the radio link and the For managing a microwave node including both the radio link and the
packet functionality, a unified data model is desired to unify the packet functionality, a unified data model is desired to unify the
modeling of the radio link interfaces and the packet interfaces modeling of the radio link interfaces and the packet interfaces
using the same structure and the same modelling approach. using the same structure and the same modelling approach. If some
part of model is generic for other technology usage, it should be
clearly stated.
The purpose of the YANG Data Model is for management and control of The purpose of the YANG Data Model is for management and control of
the radio link interface(s) and the relationship/connectivity to the radio link interface(s) and the relationship/connectivity to
other packet interfaces, typically to Ethernet interfaces, in a other packet interfaces, typically to Ethernet interfaces, in a
microwave node. microwave node.
The capability of configuring and managing microwave nodes includes The capability of configuring and managing microwave nodes includes
the following requirements for the modelling: the following requirements for the modelling:
1) It MUST be possible to configure, manage and control a radio link 1) It MUST be possible to configure, manage and control a radio link
skipping to change at page 14, line 26 skipping to change at page 14, line 26
[I-D.ahlberg-ccamp-microwave-radio-link] provides a model proposal [I-D.ahlberg-ccamp-microwave-radio-link] provides a model proposal
for radio interfaces, which includes support for basic configuration, for radio interfaces, which includes support for basic configuration,
status and performance but lacks full support for alarm management status and performance but lacks full support for alarm management
and interface layering, i.e. the connectivity of the transported and interface layering, i.e. the connectivity of the transported
capacity (TDM & Ethernet) with other internal technology specific capacity (TDM & Ethernet) with other internal technology specific
interfaces in a microwave node. interfaces in a microwave node.
The recommendation is to use the structure of the IETF: Radio Link The recommendation is to use the structure of the IETF: Radio Link
Model [I-D.ahlberg-ccamp-microwave-radio-link] as the starting point, Model [I-D.ahlberg-ccamp-microwave-radio-link] as the starting point,
since it is a data model providing the wanted alignment with RFC since it is a data model providing the wanted alignment with RFC
7223. For the definition of the detailed leaves/parameters, the 7223. For the definition of the detailed leafs/parameters, the
recommendation is to use the IETF: Radio Link Model and the ONF: recommendation is to use the IETF: Radio Link Model and the ONF:
Microwave Modeling [ONF-model] as the basis and to define new ones Microwave Modeling [ONF-model] as the basis and to define new ones
to cover identified gaps. The parameters in those models have been to cover identified gaps. The parameters in those models have been
defined by both operators and vendors within the industry and the defined by both operators and vendors within the industry and the
implementations of the ONF Model have been tested in the Proof of implementations of the ONF Model have been tested in the Proof of
Concept events in multi-vendor environments, showing the validity of Concept events in multi-vendor environments, showing the validity of
the approach proposed in this framework document. the approach proposed in this framework document.
It is also recommended to add the required data nodes to describe It is also recommended to add the required data nodes to describe
the interface layering for the capacity provided by a radio link the interface layering for the capacity provided by a radio link
skipping to change at page 15, line 13 skipping to change at page 15, line 13
in chapter 7.1. in chapter 7.1.
+------------------------------------+-----------------------------+ +------------------------------------+-----------------------------+
| Generic Functionality | Recommendation | | Generic Functionality | Recommendation |
| | | | | |
+------------------------------------+-----------------------------+ +------------------------------------+-----------------------------+
|1.Fault Management | | |1.Fault Management | |
| | | | | |
| Alarm Configuration | New Radio Link Model | | Alarm Configuration | New Radio Link Model |
| | | | | |
| Alarm notifications/ | [I-D.vallin-netmod- | | Alarm notifications/ | [I-D.vallin-ccamp- |
| synchronization | alarm-module] | | synchronization | alarm-module] |
+------------------------------------+-----------------------------+ +------------------------------------+-----------------------------+
|2.Performance Management | | |2.Performance Management | |
| | | | | |
| Performance Configuration/ | New Radio Link Model | | Performance Configuration/ | New Radio Link Model |
| Activation | | | Activation | |
| | | | | |
| Performance Collection | New Radio Link Model & | | Performance Collection | New Radio Link Model & |
| | XML files | | | XML files |
+------------------------------------+-----------------------------+ +------------------------------------+-----------------------------+
|3.Physical/Equipment Inventory | [I-D.ietf-netmod-entity] | |3.Physical/Equipment Inventory | [I-D.ietf-netmod-entity] |
+------------------------------------+-----------------------------+ +------------------------------------+-----------------------------+
Figure 4. Recommendation on how to support generic functionality Figure 4. Recommendation on how to support generic functionality
Microwave specific alarm configurations are recommended to be Microwave specific alarm configurations are recommended to be
included in the new radio link model and could be based on what is included in the new radio link model and could be based on what is
supported in the IETF and ONF Radio Link Models. Alarm notifications supported in the IETF and ONF Radio Link Models. Alarm notifications
and synchronization are general and is recommended to be supported and synchronization are general and is recommended to be supported
by a generic model, such as [I-D.vallin-netmod-alarm-module]. by a generic model, such as [I-D.vallin-ccamp-alarm-module].
Activation of interval counters & thresholds could be a generic Activation of interval counters & thresholds could be a generic
function but it is recommended to be supported by the new radio link function but it is recommended to be supported by the new radio link
specific model and can be based on both the ONF and IETF Microwave specific model and can be based on both the ONF and IETF Microwave
Radio Link models. Radio Link models.
Collection of interval/historical counters is a generic function Collection of interval/historical counters is a generic function
that needs to be supported in a node. File based collection via SFTP that needs to be supported in a node. File based collection via SFTP
and collection via a Netconf/YANG interfaces are two possible and collection via a Netconf/YANG interfaces are two possible
options and the recommendation is to include support for the latter options and the recommendation is to include support for the latter
skipping to change at page 16, line 23 skipping to change at page 16, line 23
2) Use the structure in the IETF: Radio Link Model [I-D.ahlberg- 2) Use the structure in the IETF: Radio Link Model [I-D.ahlberg-
ccamp-microwave-radio-link] as the starting point. It augments ccamp-microwave-radio-link] as the starting point. It augments
RFC 7223 and is thereby as required aligned with the structure RFC 7223 and is thereby as required aligned with the structure
of the models for management of the packet domain. of the models for management of the packet domain.
3) Use established microwave equipment and radio standards, such 3) Use established microwave equipment and radio standards, such
as ETSI EN 302 217 [EN 302 217-2], and the IETF: Radio Link as ETSI EN 302 217 [EN 302 217-2], and the IETF: Radio Link
Model [I-D.ahlberg-ccamp-microwave-radio-link] and the Model [I-D.ahlberg-ccamp-microwave-radio-link] and the
ONF: Microwave Modeling [ONF-model] as the basis for the ONF: Microwave Modeling [ONF-model] as the basis for the
definition of the detailed leaves/parameters to support the definition of the detailed leafs/parameters to support the
specified use cases and requirements, and proposing new ones specified use cases and requirements, and proposing new ones
to cover identified gaps. to cover identified gaps.
4) Add the required data nodes to describe the interface layering 4) Add the required data nodes to describe the interface layering
for the capacity provided by a radio link terminal and the for the capacity provided by a radio link terminal and the
associated Ethernet and TDM interfaces, using the principles associated Ethernet and TDM interfaces, using the principles
and data nodes for interface layering described in RFC 7223 as and data nodes for interface layering described in RFC 7223 as
a basis. a basis.
5) Include support for configuration of microwave specific alarms 5) Include support for configuration of microwave specific alarms
in the Microwave Radio Link model and rely on a generic model in the Microwave Radio Link model and rely on a generic model
such as [I.D.vallin-netmod-alarm-module] for notifications and such as [I.D.vallin-ccamp-alarm-module] for notifications and
alarm synchronization. alarm synchronization.
6) Use a generic model such as [I-D.ietf-netmod-entity] for 6) Use a generic model such as [I-D.ietf-netmod-entity] for
physical/equipment inventory. physical/equipment inventory.
It is furthermore recommended that the Microwave Radio Link YANG It is furthermore recommended that the Microwave Radio Link YANG
Date Model should be validated by both operators and vendors as Date Model should be validated by both operators and vendors as
part of the process to make it stable and mature. part of the process to make it stable and mature. During the
Hackathon in IETF 99, a project "SDN Applications for microwave
radio link via IETF YANG Data Model" successfully validated this
framework and the YANG data model[I.D.ietf-ccamp-mw-yang]. The
project also received the BEST OVERALL award from the Hackathon.
8. Security Considerations 8. Security Considerations
TBD TBD
9. IANA Considerations 9. IANA Considerations
This memo includes no request to IANA. This memo includes no request to IANA.
10. References 10. References
skipping to change at page 17, line 42 skipping to change at page 17, line 42
[I-D.ahlberg-ccamp-microwave-radio-link] [I-D.ahlberg-ccamp-microwave-radio-link]
Ahlberg, J., Carlson, J., Lund, H., Olausson, T., Ye, M., Ahlberg, J., Carlson, J., Lund, H., Olausson, T., Ye, M.,
and M. Vaupotic, "Microwave Radio Link YANG Data Models", and M. Vaupotic, "Microwave Radio Link YANG Data Models",
draft-ahlberg-ccamp-microwave-radio-link-01 (work in draft-ahlberg-ccamp-microwave-radio-link-01 (work in
progress), May 2016. progress), May 2016.
[I-D.ietf-netmod-entity] [I-D.ietf-netmod-entity]
Bierman A., Bjorklund M., Dong J., Romascanu D., "A YANG Bierman A., Bjorklund M., Dong J., Romascanu D., "A YANG
Data Model for Entity Management", draft-ietf-netmod- Data Model for Entity Management", draft-ietf-netmod-
entity-03 (work in progress), March 2017. entity-05 (work in progress), October 2017.
[I-D.vallin-netmod-alarm-module] [I-D.vallin-ccamp-alarm-module]
Vallin S. and Bjorklund M., "YANG Alarm Module", draft- Vallin S. and Bjorklund M., "YANG Alarm Module", draft-
vallin-netmod-alarm-module-02 (work in progress), May vallin-ccamp-alarm-module-00 (work in progress), October
2016. 2017.
[RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing [RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing
Management", RFC 8022, DOI 10.17487/RFC8022, Management", RFC 8022, DOI 10.17487/RFC8022, November 2016
November 2016, <http://www.rfc-editor.org/info/rfc8022>.
[I.D.zhang-ccamp-l1-topo-yang] [I.D.zhang-ccamp-l1-topo-yang]
Zhang X., Rao B., Sharma A., Liu X., "A YANG Data Model Zhang X., Rao B., Sharma A., Liu X., "A YANG Data Model
for Layer 1 (ODU) Network Topology", draft-zhang-ccamp-l1- for Layer 1 (ODU) Network Topology", draft-zhang-ccamp-l1-
topo-yang-03 (work in progress), July 2016. topo-yang-03 (work in progress), July 2016.
[I.D.ietf-ospf-yang] [I.D.ietf-ospf-yang]
Yeung D., Qu Y., Zhang J., Bogdanovic D., Sreenivasa K., Yeung D., Qu Y., Zhang J., Bogdanovic D., Sreenivasa K.,
"Yang Data Model for OSPF Protocol", draft-ietf-ospf-yang- "Yang Data Model for OSPF Protocol", draft-ietf-ospf-yang-
05,(work in progress), July 2016. 05,(work in progress), July 2016.
[ONF-model] [ONF-model]
"Microwave Modeling - ONF Wireless Transport Group", May "Microwave Modeling - ONF Wireless Transport Group", May
2016. 2016.
[ONF CIM] [ONF CIM]
"Core Information Model", ONF TR-512, ONF, September 2016 "Core Information Model", ONF TR-512, ONF, September 2016
[PB-YANG] "IEEE 802.1X and 802.1Q YANG models, Marc,H.", October [PB-YANG] "IEEE 802.1X and 802.1Q YANG models", Marc,H., October
2015. 2015.
[EN 302 217-2] [EN 302 217-2]
ETSI, "Fixed Radio Systems; Characteristics and ETSI, "Fixed Radio Systems; Characteristics and
requirements for point to-point equipment and antennas; requirements for point to-point equipment and antennas;
Part 2: Digital systems operating in frequency bands from Part 2: Digital systems operating in frequency bands from
1 GHz to 86 GHz; Harmonised Standard covering the 1 GHz to 86 GHz; Harmonised Standard covering the
essential requirements of article 3.2 of Directive essential requirements of article 3.2 of Directive
2014/53/EU", EN 302 217-2 V3.1.1, May 2017. 2014/53/EU", EN 302 217-2 V3.1.1, May 2017.
[I.D.ietf-ccamp-mw-yang]
Ahlberg, J., Ye, M., Li,X., Kawada K., Bernardos C.,
Spreafico D., Vaupotic M., "A YANG Data Model for
Microwave Radio Link", draft-ietf-ccamp-mw-yang-01,(work
in progress), July 2016.
Authors' Addresses Authors' Addresses
Jonas Ahlberg Jonas Ahlberg
Ericsson AB Ericsson AB
Lindholmspiren 11 Lindholmspiren 11
Goeteborg 417 56 Goeteborg 417 56
Sweden Sweden
Email: jonas.ahlberg@ericsson.com Email: jonas.ahlberg@ericsson.com
Luis M. Contreras Luis M. Contreras
Telefonica I+D Telefonica I+D
Ronda de la Comunicacion, S/N Ronda de la Comunicacion, S/N
Madrid 28050 Madrid 28050
Spain Spain
Email: luismiguel.contrerasmurillo@telefonica.com Email: luismiguel.contrerasmurillo@telefonica.com
Ye Min (Amy) Ye Min
Huawei Technologies CO., Ltd Huawei Technologies CO., Ltd
No.1899, Xiyuan Avenue No.1899, Xiyuan Avenue
Chengdu 611731 Chengdu 611731
P.R.China P.R.China
Email: amy.yemin@huawei.com Email: amy.yemin@huawei.com
Marko Vaupotic Marko Vaupotic
Aviat Networks Aviat Networks
Motnica 9 Motnica 9
skipping to change at line 902 skipping to change at page 20, line 35
Email: i-akiyoshi@ah.jp.nec.com Email: i-akiyoshi@ah.jp.nec.com
Carlos J. Bernardos Carlos J. Bernardos
Universidad Carlos III de Madrid Universidad Carlos III de Madrid
Av. Universidad, 30 Av. Universidad, 30
Leganes, Madrid 28911 Leganes, Madrid 28911
Spain Spain
Email: cjbc@it.uc3m.es Email: cjbc@it.uc3m.es
Daniela Spreafico
Nokia - IT
Via Energy Park, 14
Vimercate (MI) 20871
Italy
Email: daniela.spreafico@nokia.com
 End of changes. 25 change blocks. 
30 lines changed or deleted 43 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/