draft-ietf-ccamp-wson-iv-info-05.txt   draft-ietf-ccamp-wson-iv-info-06.txt 
CCAMP G. Martinelli, Ed. CCAMP G. Martinelli, Ed.
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Informational X. Zhang, Ed. Intended status: Informational H. Zhang, Ed.
Expires: January 2, 2018 Huawei Technologies Expires: September 6, 2018 Huawei Technologies
G. Galimberti G. Galimberti
Cisco Cisco
A. Zanardi
D. Siracusa
F. Pederzolli
CREATE-NET
Y. Lee Y. Lee
F. Zhang F. Zhang
Huawei Technologies Huawei Technologies
July 2017 March 5, 2018
Information Model for Wavelength Switched Optical Networks (WSONs) with Information Model for Wavelength Switched Optical Networks (WSONs) with
Impairments Validation Impairments Validation
draft-ietf-ccamp-wson-iv-info-05 draft-ietf-ccamp-wson-iv-info-06
Abstract Abstract
This document defines an information model to support Impairment- This document defines an information model to support Impairment-
Aware (IA) Routing and Wavelength Assignment (RWA) functionality. Aware (IA) Routing and Wavelength Assignment (RWA) functionality.
This information model extends the information model for impairment- This information model extends the information model for impairment-
free RWA process in WSON to facilitate computation of paths where free RWA process in WSON to facilitate computation of paths where
optical impairment constraints need to considered. optical impairment constraints need to considered.
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 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 January 2, 2018. This Internet-Draft will expire on September 6, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 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
(http://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
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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Definitions, Applicability and Properties . . . . . . . . . . 3 2. Definitions, Applicability and Properties . . . . . . . . . . 3
2.1. Definitions . . . . . . . . . . . . . . . . . . . . . . . 4 2.1. Definitions . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Applicability . . . . . . . . . . . . . . . . . . . . . . 4 2.2. Applicability . . . . . . . . . . . . . . . . . . . . . . 4
2.3. Properties . . . . . . . . . . . . . . . . . . . . . . . 5 2.3. Properties . . . . . . . . . . . . . . . . . . . . . . . 5
3. ITU-T List of Optical Parameters . . . . . . . . . . . . . . 6 3. ITU-T List of Optical Parameters . . . . . . . . . . . . . . 6
4. Background from WSON-RWA Information Model . . . . . . . . . 9 4. Background from WSON-RWA Information Model . . . . . . . . . 8
5. Optical Impairment Information Model . . . . . . . . . . . . 10 5. Optical Impairment Information Model . . . . . . . . . . . . 9
5.1. The Optical Impairment Vector . . . . . . . . . . . . . . 10 5.1. The Optical Impairment Vector . . . . . . . . . . . . . . 10
5.2. Node Information . . . . . . . . . . . . . . . . . . . . 11 5.2. Node Information . . . . . . . . . . . . . . . . . . . . 10
5.2.1. Impairment Matrix . . . . . . . . . . . . . . . . . . 11 5.2.1. Impairment Matrix . . . . . . . . . . . . . . . . . . 10
5.2.2. Impairment Resource Block Information . . . . . . . . 12 5.2.2. Impairment Resource Block Information . . . . . . . . 12
5.3. Link Information . . . . . . . . . . . . . . . . . . . . 13 5.3. Link Information . . . . . . . . . . . . . . . . . . . . 12
5.4. Path Information . . . . . . . . . . . . . . . . . . . . 13 5.4. Path Information . . . . . . . . . . . . . . . . . . . . 12
6. Encoding Considerations . . . . . . . . . . . . . . . . . . . 13 6. Encoding Considerations . . . . . . . . . . . . . . . . . . . 13
7. Control Plane Architectures . . . . . . . . . . . . . . . . . 14 7. Control Plane Architectures . . . . . . . . . . . . . . . . . 13
7.1. IV-Centralized . . . . . . . . . . . . . . . . . . . . . 14 7.1. IV-Centralized . . . . . . . . . . . . . . . . . . . . . 14
7.2. IV-Distributed . . . . . . . . . . . . . . . . . . . . . 15 7.2. IV-Distributed . . . . . . . . . . . . . . . . . . . . . 14
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 9. Contributing Authors . . . . . . . . . . . . . . . . . . . . 14
10. Security Considerations . . . . . . . . . . . . . . . . . . . 15 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 11. Security Considerations . . . . . . . . . . . . . . . . . . . 15
11.1. Normative References . . . . . . . . . . . . . . . . . . 15 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
11.2. Informative References . . . . . . . . . . . . . . . . . 16 12.1. Normative References . . . . . . . . . . . . . . . . . . 16
12.2. Informative References . . . . . . . . . . . . . . . . . 16
Appendix A. FAQ . . . . . . . . . . . . . . . . . . . . . . . . 17 Appendix A. FAQ . . . . . . . . . . . . . . . . . . . . . . . . 17
A.1. Why the Application Code does not suffice for Optical A.1. Why the Application Code does not suffice for Optical
Impairment Validation? . . . . . . . . . . . . . . . . . 17 Impairment Validation? . . . . . . . . . . . . . . . . . 17
A.2. Are DWDM network multivendor? . . . . . . . . . . . . . . 18 A.2. Are DWDM network multivendor? . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
1. Introduction 1. Introduction
In the context of Wavelength Switched Optical Network (WSON), In the context of Wavelength Switched Optical Network (WSON),
[RFC6163] describes the basic framework for a GMPLS and PCE-based [RFC6163] describes the basic framework for a GMPLS and PCE-based
skipping to change at page 4, line 8 skipping to change at page 3, line 46
This section provides some concepts to help understand the model and This section provides some concepts to help understand the model and
to make a clear separation from data plane definitions (ITU-T to make a clear separation from data plane definitions (ITU-T
recommendations). The first sub-section provides definitions while recommendations). The first sub-section provides definitions while
the Applicability sections uses the defined definitions to scope this the Applicability sections uses the defined definitions to scope this
document. document.
2.1. Definitions 2.1. Definitions
o Computational Model / Optical Computational Model. o Computational Model / Optical Computational Model.
Defined by ITU standard documents. In this context we look for Defined by ITU standard documents (e.g. [ITU.G680]). In this
models able to compute optical impairments for a given lightpath. context we look for models able to compute optical impairments for
a given lightpath.
o Information Model. o Information Model.
Defined by IETF (this document) and provides the set of Defined by IETF (this document) and provides the set of
information required by control plane to apply the Computational information required by control plane to apply the Computational
Model. Model.
o Level of Approximation. o Level of Approximation.
This concept refers to the Computational Model as it may compute This concept refers to the Computational Model as it may compute
optical impairment with a certain level of uncertainty. This optical impairment with a certain level of uncertainty. This
level is generally not measured but [RFC6566] Section 4.1.1 level is generally not measured but [RFC6566] Section 4.1.1
provides a rough classification about it. provides a rough classification about it.
skipping to change at page 9, line 41 skipping to change at page 9, line 29
information, is uniquely identified by advertising node and is a information, is uniquely identified by advertising node and is a
static information. Dynamic information related to the actual state static information. Dynamic information related to the actual state
of connections is available through specific extension to link of connections is available through specific extension to link
information. information.
The [RFC7446] introduces the concept of ResourceBlockInfo and The [RFC7446] introduces the concept of ResourceBlockInfo and
ResourcePool for the WSON nodes. The resource block is a collection ResourcePool for the WSON nodes. The resource block is a collection
of resources behaving in the same way and having similar of resources behaving in the same way and having similar
characteristics. The ResourceBlockInfo is defined as follow: characteristics. The ResourceBlockInfo is defined as follow:
<ResourceBlockInfo> ::= <ResourceBlockSet> [<InputConstraints>] <ResourceBlockInfo> ::= <ResourceBlockSet> [<InputConstraints>]
[<ProcessingCapabilities>] [<OutputConstraints>] [<ProcessingCapabilities>] [<OutputConstraints>]
The usage of resource block and resource pool is an efficient way to The usage of resource block and resource pool is an efficient way to
model constrains within a WSON node. model constrains within a WSON node.
5. Optical Impairment Information Model 5. Optical Impairment Information Model
The idea behind this document is to put optical impairment parameters The idea behind this document is to put optical impairment parameters
into categories and extend the information model already defined for into categories and extend the information model already defined for
impairment-free WSONs. The three categories are: impairment-free WSONs. The three categories are:
o Node Information. The concept of connectivity matrix is reused o Node Information. The concept of connectivity matrix is reused
and extended to introduce an impairment matrix, which represents and extended to introduce an impairment matrix, which represents
the impairments suffered on the internal path between two ports. the impairments suffered on the internal path between two ports.
In addition, the concept of Resource Block is also reused and In addition, the concept of Resource Block is also reused and
extended to provide an efficient modelization of per-port extended to provide an efficient representation of per-port
impairment. impairment.
o Link Information representing impairment information related to a o Link Information representing impairment information related to a
specific link or hop. specific link or hop.
o Path Information representing the impairment information related o Path Information representing the impairment information related
to the whole path. to the whole path.
All the above three categories will make use of a generic container, All the above three categories will make use of a generic container,
the Impairment Vector, to transport optical impairment information. the Impairment Vector, to transport optical impairment information.
skipping to change at page 11, line 14 skipping to change at page 10, line 40
The optional LabelSet object enables wavelength dependency property The optional LabelSet object enables wavelength dependency property
as per Table 1. LabelSet has its definition in [RFC7579]. as per Table 1. LabelSet has its definition in [RFC7579].
OPTICAL_PARAM. This object represents an optical parameter. The OPTICAL_PARAM. This object represents an optical parameter. The
Impairment vector can contain a set of parameters as identified by Impairment vector can contain a set of parameters as identified by
[ITU.G697] since those parameters match the terms of the linear [ITU.G697] since those parameters match the terms of the linear
impairments computational models provided by [ITU.G680]. This impairments computational models provided by [ITU.G680]. This
information model does not speculate about the set of parameters information model does not speculate about the set of parameters
(since defined elsewhere, e.g. ITU-T), however it does not preclude (since defined elsewhere, e.g. ITU-T), however it does not preclude
extentions by adding new parameters. extensions by adding new parameters.
5.2. Node Information 5.2. Node Information
5.2.1. Impairment Matrix 5.2.1. Impairment Matrix
Impairment matrix describes a list of the optical parameters that Impairment matrix describes a list of the optical parameters that
applies to a network element as a whole or ingress/egress port pairs applies to a network element as a whole or ingress/egress port pairs
of a network element. Wavelength dependency property of optical of a network element. Wavelength dependency property of optical
parameters is also considered. parameters is also considered.
skipping to change at page 12, line 47 skipping to change at page 12, line 20
This representation shows the most general case however, the total This representation shows the most general case however, the total
amount of information transported by control plane protocols can be amount of information transported by control plane protocols can be
greatly reduced by proper encoding when the same set of values apply greatly reduced by proper encoding when the same set of values apply
to all LinkSet pairs. to all LinkSet pairs.
5.2.2. Impairment Resource Block Information 5.2.2. Impairment Resource Block Information
This information model reuses the definition of Resource Block This information model reuses the definition of Resource Block
Information adding the associated impairment vector. Information adding the associated impairment vector.
ResourceBlockInfo ::= <ResourceBlockSet> [<InputConstraints>] ResourceBlockInfo ::= <ResourceBlockSet> [<InputConstraints>]
[<ProcessingCapabilities>] [<OutputConstraints>] [<OIV>] [<ProcessingCapabilities>] [<OutputConstraints>] [<OIV>]
The object ResourceBlockInfo is than used as specified within The object ResourceBlockInfo is than used as specified within
[RFC7446]. [RFC7446].
5.3. Link Information 5.3. Link Information
For the list of optical parameters associated to the link, the same For the list of optical parameters associated to the link, the same
approach used for the node-specific impairment information can be approach used for the node-specific impairment information can be
applied. The link-specific impairment information is extended from applied. The link-specific impairment information is extended from
[RFC7446] as the following: [RFC7446] as the following:
skipping to change at page 13, line 35 skipping to change at page 13, line 5
optical impairment and/or parameter, cannot be derived (using a optical impairment and/or parameter, cannot be derived (using a
simple function) from the set of node / link contributions. simple function) from the set of node / link contributions.
An equivalent case is the option reported by [RFC6566] on IV- An equivalent case is the option reported by [RFC6566] on IV-
Candidate paths where, the control plane knows a list of optically Candidate paths where, the control plane knows a list of optically
feasible paths so a new path setup can be selected among that list. feasible paths so a new path setup can be selected among that list.
Independent from the protocols and functions combination (i.e. RWA Independent from the protocols and functions combination (i.e. RWA
vs. Routing vs. PCE), the IV-Candidates imply a path property stating vs. Routing vs. PCE), the IV-Candidates imply a path property stating
that a path is optically feasible. that a path is optically feasible.
<PathInfo> ::= <OIV> The concept of Optical Impairment Vector (OIV) might be used or
extended to report optical impairment information at path level
[EDITOR NOTE: section to be completed, especially to evaluate however this is case is letf for future studies.
protocol implications. Likely resemble to RSVP ADSPEC].
6. Encoding Considerations 6. Encoding Considerations
Details about encoding will be defined in a separate document Details about encoding will be defined in a separate document
[I-D.martinelli-ccamp-wson-iv-encode] however worth remembering that, [I-D.martinelli-ccamp-wson-iv-encode] however worth remembering that,
within [ITU.G697] Appending V, ITU already provides a guideline for within [ITU.G697] Appending V, ITU already provides a guideline for
encoding some optical parameters. encoding some optical parameters.
In particular [ITU.G697] indicates that each parameter shall be In particular [ITU.G697] indicates that each parameter shall be
represented by a 32 bit floating point number. represented by a 32 bit floating point number.
skipping to change at page 14, line 21 skipping to change at page 13, line 35
This kind of information will enable IA-RWA process to make some This kind of information will enable IA-RWA process to make some
additional considerations on wavelength feasibility. [RFC6566] additional considerations on wavelength feasibility. [RFC6566]
Section 4.1.3 reports some considerations regarding this degree of Section 4.1.3 reports some considerations regarding this degree of
confidence during the impairment validation process. confidence during the impairment validation process.
7. Control Plane Architectures 7. Control Plane Architectures
This section briefly describes how the definitions contained in this This section briefly describes how the definitions contained in this
information model will match the architectural options described by information model will match the architectural options described by
[RFC6566]. [RFC6566]. This section does not suggest suggested any specific
protocol option.
The first assumption is that the WSON GMPLS extensions are available The assumption is that WSON GMPLS extensions are available and
and operational. To such extent, the WSON-RWA will provide the operational. To such extent, the WSON-RWA will provide the following
following information through its path computation (and RWA process): information through its path computation (and RWA process):
o The wavelengths connectivity, considering also the connectivity o The wavelengths connectivity, considering also the connectivity
constraints limited by reconfigurable optics, and wavelengths constraints limited by reconfigurable optics, and wavelengths
availability. availability.
o The interface compatibility at the physical level. o The interface compatibility at the physical level.
o The Optical-Elettro-Optical (OEO) availability within the network o The Optical-Elettro-Optical (OEO) availability within the network
(and related physical interface compatibility). As already stated (and related physical interface compatibility). As already stated
by the framework this information it's very important for by the framework this information it's very important for
skipping to change at page 14, line 49 skipping to change at page 14, line 16
computation function may use an available OEO point to find a computation function may use an available OEO point to find a
feasible path. In normally operated networks OEO are mainly feasible path. In normally operated networks OEO are mainly
uses to support optically unfeasible path than mere wavelength uses to support optically unfeasible path than mere wavelength
conversion. conversion.
B. The OEO points reset the optical impairment information since B. The OEO points reset the optical impairment information since
a new light is generated. a new light is generated.
7.1. IV-Centralized 7.1. IV-Centralized
Centralized IV process is performed by a single entity (e.g., a PCE). Centralized IV process is performed by a single entity (e.g. a PCE or
Given sufficient impairment information, it can either be used to other external entities). Given sufficient impairment information,
provide a list of paths between two nodes, which are valid in terms it can either be used to provide a list of paths between two nodes,
of optical impairments. Alternatively, it can help validate whether which are valid in terms of optical impairments. Alternatively, it
a particular selected path and wavelength is feasible or not. This can help validate whether a particular selected path and wavelength
requires distribution of impairment information to the entity is feasible or not.
performing the IV process.
This Information Model doesn't make any hypothesis on distribution Centralized IV functions requires exchange of impairment information
method for optical parameters but only defines the essential build to the entity performing the IV process from network nodes. This
blocks. A centralized entity may get knowledge of required information exchange may requires implementation of this information
information through routing protocols or other mechanism such as BGP- model within an exsting protocol (i.e. routing procol vs PCEP vs BGP-
LS. LS vs others).
7.2. IV-Distributed 7.2. IV-Distributed
Assuming the information model is implemented through a routing Assuming the information model is implemented through a routing
protocol, every node in the WSON network shall be able to perform an protocol, every node in the WSON network shall be able to perform an
RWA-IV function. RWA-IV function.
The signalling phase may provide additional checking as others The signalling phase may provide additional checking as others
traffic engineering parameters. traffic engineering parameters.
8. Acknowledgements 8. Acknowledgements
Authors would like to acknoledge Greg Bernstein and Moustafa Kattan Authors would like to acknoledge Greg Bernstein and Moustafa Kattan
as authors of a previous similar draft whose content partially as authors of a previous similar draft whose content partially
converged here. converged here.
Authors would like to thank ITU SG15/Q6 and in particular Peter Authors would like to thank ITU SG15/Q6 and in particular Peter
Stassar and Pete Anslow for providing useful information and text to Stassar and Pete Anslow for providing useful information and text to
CCAMP through join meetings and liaisons. CCAMP through join meetings and liaisons.
9. IANA Considerations 9. Contributing Authors
This document was the collective work of several authors. The text
and content of this document was contributed by the editors and the
co-authors listed below:
Xian Zhang
Huawei Technologies
F3-5-B R&D Center, Huawei Base
Bantian, Longgang District
Shenzen 518129
P.R. China
Phone: +86 755 28972913
Email: zhang.xian@huawei.com
Domenico Siracusa
CREATE-NET
via alla Cascata 56/D, Povo
Trento 38123
Italy
Email: domenico.siracusa@create-net.org
Andrea Zanardi
CREATE-NET
via alla Cascata 56/D, Povo
Trento 38123
Italy
Email: andrea.zanardi@create-net.org
Federico Pederzolli
CREATE-NET
via alla Cascata 56/D, Povo
Trento 38123
Italy
Email: federico.perderzolli@create-net.org
10. IANA Considerations
This document does not contain any IANA requirement. This document does not contain any IANA requirement.
10. Security Considerations 11. Security Considerations
This document defines an information model for impairments in optical This document defines an information model for impairments in optical
networks. If such a model is put into use within a network it will networks. If such a model is put into use within a network it will
by its nature contain details of the physical characteristics of an by its nature contain details of the physical characteristics of an
optical network. Such information would need to be protected from optical network. Such information would need to be protected from
intentional or unintentional disclosure. intentional or unintentional disclosure.
11. References 12. References
11.1. Normative References 12.1. Normative References
[ITU.G650.1] [ITU.G650.1]
International Telecommunications Union, "Transmission International Telecommunications Union, "Transmission
media and optical systems characteristics - Optical fibre media and optical systems characteristics - Optical fibre
cable", ITU-T Recommendation G.650.1, July 2010. cable", ITU-T Recommendation G.650.1, July 2010.
[ITU.G650.2] [ITU.G650.2]
International Telecommunications Union, "Definitions and International Telecommunications Union, "Definitions and
test methods for statistical and non-linear related test methods for statistical and non-linear related
attributes of single-mode fibre and cable", attributes of single-mode fibre and cable",
skipping to change at page 16, line 41 skipping to change at page 16, line 47
[ITU.GSUP39] [ITU.GSUP39]
International Telecommunications Union, "Optical System International Telecommunications Union, "Optical System
Design and Engineering Considerations", Design and Engineering Considerations",
ITU-T Recommendation G. Supplement 39, September 2012. ITU-T Recommendation G. Supplement 39, September 2012.
[ITU.GSUP47] [ITU.GSUP47]
International Telecommunications Union, "General aspects International Telecommunications Union, "General aspects
of optical fibres and cables", ITU-T Recommendation G. of optical fibres and cables", ITU-T Recommendation G.
Supplement 47, September 2012. Supplement 47, September 2012.
11.2. Informative References 12.2. Informative References
[I-D.martinelli-ccamp-wson-iv-encode] [I-D.martinelli-ccamp-wson-iv-encode]
Martinelli, G., Zhang, X., Galimberti, G., Siracusa, D., Martinelli, G., Zhang, X., Galimberti, G., Lee, Y., and F.
Zanardi, A., Pederzolli, F., Lee, Y., and F. Zhang, Zhang, "Information Encoding for WSON with Impairments
"Information Encoding for WSON with Impairments Validation", draft-martinelli-ccamp-wson-iv-encode-09
Validation", draft-martinelli-ccamp-wson-iv-encode-07 (work in progress), February 2018.
(work in progress), October 2016.
[LS78] International Telecommunications Union SG15/Q6, "LS/s on [LS78] International Telecommunications Union SG15/Q6, "LS/s on
CCAMP Liaison to ITU-T SG15 Q6 and Q12 on WSON", CCAMP Liaison to ITU-T SG15 Q6 and Q12 on WSON",
LS https://datatracker.ietf.org/liaison/1288/, October LS https://datatracker.ietf.org/liaison/1288/, October
2013. 2013.
[RFC6163] Lee, Y., Ed., Bernstein, G., Ed., and W. Imajuku, [RFC6163] Lee, Y., Ed., Bernstein, G., Ed., and W. Imajuku,
"Framework for GMPLS and Path Computation Element (PCE) "Framework for GMPLS and Path Computation Element (PCE)
Control of Wavelength Switched Optical Networks (WSONs)", Control of Wavelength Switched Optical Networks (WSONs)",
RFC 6163, DOI 10.17487/RFC6163, April 2011, RFC 6163, DOI 10.17487/RFC6163, April 2011,
<http://www.rfc-editor.org/info/rfc6163>. <https://www.rfc-editor.org/info/rfc6163>.
[RFC6566] Lee, Y., Ed., Bernstein, G., Ed., Li, D., and G. [RFC6566] Lee, Y., Ed., Bernstein, G., Ed., Li, D., and G.
Martinelli, "A Framework for the Control of Wavelength Martinelli, "A Framework for the Control of Wavelength
Switched Optical Networks (WSONs) with Impairments", Switched Optical Networks (WSONs) with Impairments",
RFC 6566, DOI 10.17487/RFC6566, March 2012, RFC 6566, DOI 10.17487/RFC6566, March 2012,
<http://www.rfc-editor.org/info/rfc6566>. <https://www.rfc-editor.org/info/rfc6566>.
[RFC7446] Lee, Y., Ed., Bernstein, G., Ed., Li, D., and W. Imajuku, [RFC7446] Lee, Y., Ed., Bernstein, G., Ed., Li, D., and W. Imajuku,
"Routing and Wavelength Assignment Information Model for "Routing and Wavelength Assignment Information Model for
Wavelength Switched Optical Networks", RFC 7446, Wavelength Switched Optical Networks", RFC 7446,
DOI 10.17487/RFC7446, February 2015, DOI 10.17487/RFC7446, February 2015,
<http://www.rfc-editor.org/info/rfc7446>. <https://www.rfc-editor.org/info/rfc7446>.
[RFC7579] Bernstein, G., Ed., Lee, Y., Ed., Li, D., Imajuku, W., and [RFC7579] Bernstein, G., Ed., Lee, Y., Ed., Li, D., Imajuku, W., and
J. Han, "General Network Element Constraint Encoding for J. Han, "General Network Element Constraint Encoding for
GMPLS-Controlled Networks", RFC 7579, GMPLS-Controlled Networks", RFC 7579,
DOI 10.17487/RFC7579, June 2015, DOI 10.17487/RFC7579, June 2015,
<http://www.rfc-editor.org/info/rfc7579>. <https://www.rfc-editor.org/info/rfc7579>.
Appendix A. FAQ Appendix A. FAQ
A.1. Why the Application Code does not suffice for Optical Impairment A.1. Why the Application Code does not suffice for Optical Impairment
Validation? Validation?
Application Codes are encoded within GMPLS WSON protocol through the Application Codes are encoded within GMPLS WSON protocol through the
Optical Interface Class as defined in [RFC7446]. Optical Interface Class as defined in [RFC7446].
The purpose of the Application Code in RWA is simply to assess the The purpose of the Application Code in RWA is simply to assess the
skipping to change at page 18, line 25 skipping to change at page 18, line 30
Giovanni Martinelli (editor) Giovanni Martinelli (editor)
Cisco Cisco
via Santa Maria Molgora, 48/C via Santa Maria Molgora, 48/C
Vimercate, MB 20871 Vimercate, MB 20871
Italy Italy
Phone: +39 039 2092044 Phone: +39 039 2092044
Email: giomarti@cisco.com Email: giomarti@cisco.com
Xian Zhang (editor) Haomian Zhang (editor)
Huawei Technologies Huawei Technologies
F3-5-B R&D Center, Huawei Base F3 R&D Center, Huawei Base
Bantian, Longgang District Bantian, Longgang District
Shenzen 518129 Shenzen 518129
P.R. China P.R. China
Phone: +86 755 28972465 Phone: +86 755 28972465
Email: zhang.xian@huawei.com Email: zhenghaomian@huawei.com
Gabriele M. Galimberti Gabriele M. Galimberti
Cisco Cisco
Via Santa Maria Molgora, 48/C Via Santa Maria Molgora, 48/C
Vimercate, MB 20871 Vimercate, MB 20871
Italy Italy
Phone: +39 039 2091462 Phone: +39 039 2091462
Email: ggalimbe@cisco.com Email: ggalimbe@cisco.com
Andrea Zanardi
CREATE-NET
via alla Cascata 56/D, Povo
Trento 38123
Italy
Email: andrea.zanardi@create-net.org
Domenico Siracusa
CREATE-NET
via alla Cascata 56/D, Povo
Trento 38123
Italy
Email: domenico.siracusa@create-net.org
Federico Pederzolli
CREATE-NET
via alla Cascata 56/D, Povo
Trento 38123
Italy
Email: federico.perderzolli@create-net.org
Young Lee Young Lee
Huawei Technologies Huawei Technologies
1700 Alma Drive, Suite 100 1700 Alma Drive, Suite 100
Plano, TX 75075 Plano, TX 75075
U.S.A U.S.A
Email: ylee@huawei.com Email: ylee@huawei.com
Fatai Zhang Fatai Zhang
Huawei Technologies Huawei Technologies
 End of changes. 40 change blocks. 
97 lines changed or deleted 110 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/