draft-ietf-ccamp-microwave-framework-00.txt   draft-ietf-ccamp-microwave-framework-01.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: June 16, 2017 TID Expires: December 22, 2017 TID
A. Ye Min A. Ye Min
Huawei Huawei
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
December 16, 2016 June 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-00 draft-ietf-ccamp-microwave-framework-01
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 2, line 20 skipping to change at page 2, line 20
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 April 27, 2017. This Internet-Draft will expire on December 22, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
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
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 . . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
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 4, line 30 skipping to change at page 4, line 30
wireless local area networks (WLANs) and broadband access. This band wireless local area networks (WLANs) and broadband access. This band
has short wavelengths that range from 10 millimeters to 1 has short wavelengths that range from 10 millimeters to 1
millimeter, namely millimeter band or millimeter wave. The 71 - 76 millimeter, namely millimeter band or millimeter wave. The 71 - 76
GHz, 81 - 86 GHz and 92-95 GHz bands are used for point-to-point GHz, 81 - 86 GHz and 92-95 GHz bands are used for point-to-point
high-bandwidth communication links, which allows for higher data high-bandwidth communication links, which allows for higher data
rates up to 10 Gbit/s but requires a license. Unlicensed short-range rates up to 10 Gbit/s but requires a license. Unlicensed short-range
data links can be used on 60 GHz millimeter wave. For instance, the data links can be used on 60 GHz millimeter wave. For instance, the
upcoming IEEE Wi-Fi standard 802.11ad will run on the 60 GHz upcoming IEEE Wi-Fi standard 802.11ad will run on the 60 GHz
spectrum with data transfer rates of up to 7 Gbit/s. spectrum with data transfer rates of up to 7 Gbit/s.
ETSI EN 302 217 series defines the characteristics and requirements
of microwave/millimeter wave equipment and antennas. Especially ETSI
EN 302 217-2 specifies the essential parameters for the systems
operating from 1.4GHz to 86GHz.
Carrier Termination and Radio Link Terminal are two concepts defined
to support modeling of microwave radio link features and parameters
in a structured and yet simple manner.
Carrier Termination is an interface for the capacity provided over Carrier Termination is an interface for the capacity provided over
the air by a single carrier. It is typically defined by its the air by a single carrier. It is typically defined by its
transmitting and receiving frequencies. transmitting and receiving frequencies.
Radio Link Terminal is an interface providing packet capacity and/or Radio Link Terminal is an interface providing packet capacity and/or
TDM capacity to the associated Ethernet and/or TDM interfaces in a TDM capacity to the associated Ethernet and/or TDM interfaces in a
node and used for setting up a transport service over a node and used for setting up a transport service over a
microwave/millimeter wave link. microwave/millimeter wave link.
Figure 1 provides a graphical representation of Carrier Termination Figure 1 provides a graphical representation of Carrier Termination
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 &
WiFi are not within the scope of this microwave model work. Wi-Fi 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 [I-D.ietf-netmod-routing-cfg] and Provider Bridge [PB- Management [RFC8022] and Provider Bridge [PB-YANG].
YANG] They are based on RFC 7223 [RFC7223], which is the IETF YANG They are based on RFC 7223 [RFC7223], which is the IETF YANG
model for Interface Management, and is an evolution of the SNMP IF- model for Interface 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 are managed as one common for use cases in which a microwave node is 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 8, line 38 skipping to change at page 8, line 38
These solutions are expected to evolve and benefit from an increased These solutions are expected to evolve and benefit from an increased
focus on standardization by simplifying multi-vendor management and focus on standardization by simplifying multi-vendor management and
remove the need for vendor/domain specific management. remove the need for vendor/domain specific management.
4.2. Software Defined Networking 4.2. Software Defined Networking
One of the main drivers for applying SDN from an operator One of the main drivers for applying SDN from an operator
perspective is simplification and automation of network provisioning perspective is simplification and automation of network provisioning
as well as E2E network service management. The vision is to have a as well as E2E network service management. The vision is to have a
global view of the network conditions spanning across different global view of the network conditions spanning across different
vendors? equipment and multiple technologies. vendors' equipment and multiple technologies.
If nodes from different vendors shall be managed by the same SDN If nodes from different vendors shall be managed by the same SDN
controller via a node management interface (north bound interface, controller via a node management interface (north bound interface,
NBI), without the extra effort of introducing intermediate systems, NBI), without the extra effort of introducing intermediate systems,
all nodes must align their node management interfaces. Hence, an all nodes must align their node management interfaces. Hence, an
open and standardized node management interface are required in a open and standardized node management interface are required in a
multi-vendor environment. Such standardized interface enables a multi-vendor environment. Such standardized interface enables a
unified management and configuration of nodes from different vendors unified management and configuration of nodes from different vendors
by a common set of applications. by a common set of applications.
skipping to change at page 12, line 35 skipping to change at page 12, line 35
configured for a carrier termination. configured for a carrier termination.
b) A radio link terminal MUST configure the associated carrier b) A radio link terminal MUST configure the associated carrier
terminations and the type of aggregation/bonding or protection terminations and the type of aggregation/bonding or protection
configurations expected for the radio link terminal. configurations expected for the radio link terminal.
c) The capability, e.g. the maximum modulation supported, and the c) The capability, e.g. the maximum modulation supported, and the
actual status/statistics, e.g. administrative status of the actual status/statistics, e.g. administrative status of the
carriers, SHOULD also be supported by the data model. carriers, SHOULD also be supported by the data model.
d) The definition of the features and parameters SHOULD be based
on established microwave equipment and radio standards, such
as ETSI EN 302 217 [EN 302 217-2] which specifies the essential
parameters for microwave systems operating from 1.4GHz to
86GHz.
2) It MUST be possible to map different traffic types (e.g. TDM, 2) It MUST be possible to map different traffic types (e.g. TDM,
Ethernet) to the transport capacity provided by a specific radio Ethernet) to the transport capacity provided by a specific radio
link terminal. link terminal.
3) It MUST be possible to configure and collect historical 3) It MUST be possible to configure and collect historical
measurements (for the use case described in section 5.4) to be measurements (for the use case described in section 5.4) to be
performed on a radio link interface, e.g. minimum, maximum and performed on a radio link interface, e.g. minimum, maximum and
average transmit power and receive level in dBm. average transmit power and receive level in dBm.
4) It MUST be possible to configure and retrieve alarms reporting 4) It MUST be possible to configure and retrieve alarms reporting
skipping to change at page 14, line 14 skipping to change at page 14, line 14
RFC 3444 [RFC3444] explains the difference between Information RFC 3444 [RFC3444] explains the difference between Information
Model(IM) and Data Models(DM). IM is to model managed objects at a Model(IM) and Data Models(DM). IM is to model managed objects at a
conceptual level for designers and operators, DM is defined at a conceptual level for designers and operators, DM is defined at a
lower level and includes many details for implementers. In addition, lower level and includes many details for implementers. In addition,
the protocol-specific details are usually included in DM. Since the protocol-specific details are usually included in DM. Since
conceptual models can be implemented in different ways, multiple DMs conceptual models can be implemented in different ways, multiple DMs
can be derived from a single IM. To ensure better interoperability, can be derived from a single IM. To ensure better interoperability,
it is better to focus on DM directly. it is better to focus on DM directly.
RFC 7223 describes an interface management model, however it doesn?t RFC 7223 describes an interface management model, however it doesn't
include technology specific information, e.g., for radio interface. include technology specific information, e.g., for radio interface.
[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 leafs/parameters, the 7223. For the definition of the detailed leaves/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 16, line 19 skipping to change at page 16, line 19
1) A Microwave Radio Link YANG Data Model should be defined with a 1) A Microwave Radio Link YANG Data Model should be defined with a
scope enough to support the use cases and requirements in scope enough to support the use cases and requirements in
chapter 5 and 6 of this document. chapter 5 and 6 of this document.
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 the IETF: Radio Link Model [I-D.ahlberg-ccamp-microwave- 3) Use established microwave equipment and radio standards, such
radio-link] and the ONF: Microwave Modeling [ONF-model] as the as ETSI EN 302 217 [EN 302 217-2], and the IETF: Radio Link
basis for the definition of the detailed leafs/parameters to Model [I-D.ahlberg-ccamp-microwave-radio-link] and the
support the specified use cases and requirements, and proposing ONF: Microwave Modeling [ONF-model] as the basis for the
new ones to cover identified gaps. definition of the detailed leaves/parameters to support the
specified use cases and requirements, and proposing new ones
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-netmod-alarm-module] for notifications and
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-00 (work in progress), May 2016. entity-03 (work in progress), March 2017.
[I-D.vallin-netmod-alarm-module] [I-D.vallin-netmod-alarm-module]
Vallin S. and Bjorklund M., "YANG Alarm Module", draft- Vallin S. and Bjorklund M., "YANG Alarm Module", draft-
vallin-netmod-alarm-module-00 (work in progress), October vallin-netmod-alarm-module-02 (work in progress), May
2016. 2016.
[I-D.ietf-netmod-routing-cfg] [RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing
Lhotka, L. and A. Lindem, "A YANG Data Model for Routing Management", RFC 8022, DOI 10.17487/RFC8022,
Management", draft-ietf-netmod-routing-cfg-24 (work in November 2016, <http://www.rfc-editor.org/info/rfc8022>.
progress), October 2016.
[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.
skipping to change at page 18, line 25 skipping to change at page 18, line 25
[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]
ETSI, "Fixed Radio Systems; Characteristics and
requirements for point to-point equipment and antennas;
Part 2: Digital systems operating in frequency bands from
1 GHz to 86 GHz; Harmonised Standard covering the
essential requirements of article 3.2 of Directive
2014/53/EU", EN 302 217-2 V3.1.1, May 2017.
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
 End of changes. 20 change blocks. 
25 lines changed or deleted 49 lines changed or added

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