draft-ietf-ccamp-rsvp-te-sdh-otn-oam-ext-03.txt   draft-ietf-ccamp-rsvp-te-sdh-otn-oam-ext-04.txt 
Network Working Group A. Kern Network Working Group A. Kern
Internet-Draft A. Takacs Internet-Draft A. Takacs
Intended status: Standards Track Ericsson Intended status: Standards Track Ericsson
Expires: April 2012 October 26, 2011 Expires: September 3, 2012 March 2, 2012
GMPLS RSVP-TE Extensions for SONET/SDH and OTN OAM Configuration GMPLS RSVP-TE Extensions for SONET/SDH and OTN OAM Configuration
draft-ietf-ccamp-rsvp-te-sdh-otn-oam-ext-03 draft-ietf-ccamp-rsvp-te-sdh-otn-oam-ext-04
Abstract Abstract
GMPLS has been extended to support connection establishment in both GMPLS has been extended to support connection establishment in both
SONET/SDH [RFC4606] and OTN [RFC4328] networks. However support for SONET/SDH [RFC4606] and OTN [RFC4328] networks. However support for
the configuration of the supervision functions is not specified. the configuration of the supervision functions is not specified.
Both SONET/SDH and OTN implement supervision functions to qualify the Both SONET/SDH and OTN implement supervision functions to qualify the
transported signals. This document defines extensions to RSVP-TE for transported signals. This document defines extensions to RSVP-TE for
SONET/SDH and OTN OAM configuration based on the OAM Configuration SONET/SDH and OTN OAM configuration based on the OAM Configuration
Framework defined in [GMPLS-OAM-FWK]. Framework defined in [GMPLS-OAM-FWK].
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF 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), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. 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."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on September 3, 2012.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire April 2012
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2012 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
described in the BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Overview of SONET/SDH and OTN OAM related functions . . . . . 5 2. Overview of SONET/SDH and OTN OAM related functions . . . . . 5
2.1. Continuity supervision . . . . . . . . . . . . . . . . . . 5 2.1. Continuity supervision . . . . . . . . . . . . . . . . . . 5
2.2. Connectivity supervision . . . . . . . . . . . . . . . . . 5 2.2. Connectivity supervision . . . . . . . . . . . . . . . . . 5
2.2.1. SONET/SDH . . . . . . . . . . . . . . . . . . . . . . 5 2.2.1. SONET/SDH . . . . . . . . . . . . . . . . . . . . . . 5
2.2.2. OTN . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.2.2. OTN . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3. Signal quality supervision . . . . . . . . . . . . . . . . 5 2.3. Signal quality supervision . . . . . . . . . . . . . . . . 6
2.3.1. SONET/SDH . . . . . . . . . . . . . . . . . . . . . . 6 2.3.1. SONET/SDH . . . . . . . . . . . . . . . . . . . . . . 6
2.3.2. OTN . . . . . . . . . . . . . . . . . . . . . . . . . 6 2.3.2. OTN . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.4. Delay measurement . . . . . . . . . . . . . . . . . . . . 6
3. RSVP-TE signaling extensions . . . . . . . . . . . . . . . . . 7 3. RSVP-TE signaling extensions . . . . . . . . . . . . . . . . . 7
3.1. Operation overview . . . . . . . . . . . . . . . . . . . . 7 3.1. Operation overview . . . . . . . . . . . . . . . . . . . . 7
3.1.1. Continuity Check supervision . . . . . . . . . . . . . 7 3.1.1. Continuity Check supervision . . . . . . . . . . . . . 7
3.1.2. Connectivity Monitoring supervision . . . . . . . . . 7 3.1.2. Connectivity Monitoring supervision . . . . . . . . . 8
3.1.2.1. SDH/SONET . . . . . . . . . . . . . . . . . . . . 7 3.1.2.1. SDH/SONET . . . . . . . . . . . . . . . . . . . . 8
3.1.2.2. OTN . . . . . . . . . . . . . . . . . . . . . . . 8 3.1.2.2. OTN . . . . . . . . . . . . . . . . . . . . . . . 8
3.1.3. Signal quality supervision . . . . . . . . . . . . . . 9 3.1.3. Signal quality supervision . . . . . . . . . . . . . . 9
3.2. Signaling support of Virtual Concatenation Groups (VCG) . 9 3.2. Signaling support of Virtual Concatenation Groups (VCG) . 9
3.3. OAM types and functions . . . . . . . . . . . . . . . . . 10 3.3. OAM types and functions . . . . . . . . . . . . . . . . . 10
3.4. SONET/SDH OAM Configuration sub-TLV . . . . . . . . . . . 10 3.4. SONET/SDH OAM Configuration sub-TLV . . . . . . . . . . . 10
3.5. OTN OAM Configuration sub-TLV . . . . . . . . . . . . . . 11 3.5. OTN OAM Configuration sub-TLV . . . . . . . . . . . . . . 11
3.6. TTI Configuration Sub-TLV . . . . . . . . . . . . . . . . 11 3.6. TTI Configuration Sub-TLV . . . . . . . . . . . . . . . . 11
3.6.1. SDH TTI Configuration Sub-TLV . . . . . . . . . . . . 11 3.6.1. SDH TTI Configuration Sub-TLV . . . . . . . . . . . . 11
3.6.2. OTN TTI Configuration Sub-TLV . . . . . . . . . . . . 12 3.6.2. OTN TTI Configuration Sub-TLV . . . . . . . . . . . . 12
3.7. Degraded signal thresholds Sub-TLV . . . . . . . . . . . . 13 3.7. Degraded signal thresholds Sub-TLV . . . . . . . . . . . . 14
4. Error handling . . . . . . . . . . . . . . . . . . . . . . . . 15 4. Error handling . . . . . . . . . . . . . . . . . . . . . . . . 16
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
6. Security Considerations . . . . . . . . . . . . . . . . . . . 17 6. Security Considerations . . . . . . . . . . . . . . . . . . . 18
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.1. Normative References . . . . . . . . . . . . . . . . . . . 19 8.1. Normative References . . . . . . . . . . . . . . . . . . . 20
8.2. Informative References . . . . . . . . . . . . . . . . . . 19 8.2. Informative References . . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22
1. Introduction 1. Introduction
Both SONET/SDH and OTN implement supervision functions to qualify the Both SONET/SDH and OTN implement supervision functions to qualify the
transported signals. Supervision functions include continuity, transported signals. Supervision functions include continuity,
connectivity, signal quality, alignment and payload supervision. The connectivity, signal quality, alignment and payload supervision. The
ITU-T G.806 [G.806] recommendation defines the generic framework of ITU-T G.806 [G.806] recommendation defines the generic framework of
the supervision functions, which are then further specified for the supervision functions, which are then further specified for
SONET/SDH and OTN in technology specific documents. SONET/SDH and OTN in technology specific documents.
GMPLS has been extended to support connection establishment in both GMPLS has been extended to support connection establishment in SONET/
SONET/SDH [RFC4606] and OTN [RFC4328] networks. These documents SDH [RFC4606], OTN [RFC4328] and OTNv3 [OTNv3_SIG] networks. These
however do not support the configuration of the respective documents however do not support the configuration of the respective
supervision functions. supervision functions.
[GMPLS-OAM-FWK] defines a technology-agnostic framework for GMPLS to [GMPLS-OAM-FWK] defines a technology-agnostic framework for GMPLS to
support the establishment and configuration of the pro-active OAM support the establishment and configuration of the pro-active OAM
functions of signalled connections. The properties of the OAM functions of signalled connections. The properties of the OAM
functions are exchanged during connection establishment and may be functions are exchanged during connection establishment and may be
modified during the life of the connection. The technology specific modified during the life of the connection. The technology specific
parameters to be exchanged are to be described in accompanying parameters to be exchanged are to be described in accompanying
documents. This document defines the extensions for SONET/SDH and documents. This document defines the extensions for SONET/SDH and
OTN OAM configuration for end-to-end monitoring. OTN OAM configuration for end-to-end monitoring.
2. Overview of SONET/SDH and OTN OAM related functions 2. Overview of SONET/SDH and OTN OAM related functions
SONET/SDH [G.707] and OTN [G.709] provide a variety of supervision SONET/SDH [G.707] and OTN [G.709v3] provide a variety of supervision
functions. Here we only consider continuity, connectivity and signal functions. Among these functions we consider continuity,
quality supervision functions, as these are the candidates for GMPLS connectivity and signal quality supervision functions, as these are
based configuration. the candidates for GMPLS based configuration. We also consider delay
measurement management function of OTN.
2.1. Continuity supervision 2.1. Continuity supervision
Continuity supervision provides methods monitoring the health of a Continuity supervision provides methods monitoring the health of a
connection (trail). connection (trail).
2.2. Connectivity supervision 2.2. Connectivity supervision
The connectivity supervision function provides a method to detect The connectivity supervision function provides a method to detect
misconnections. The detection procedure is based on emitting a Trace misconnections. The detection procedure is based on emitting a Trace
skipping to change at page 7, line 5 skipping to change at page 6, line 39
For OTN, in the digital transport layers (OTUk and ODUk) only the For OTN, in the digital transport layers (OTUk and ODUk) only the
bursty error distribution model errors with the Degraded Signal bursty error distribution model errors with the Degraded Signal
defect level is supported. Two parameters are defined: Ratio of the defect level is supported. Two parameters are defined: Ratio of the
bad frames in a one second interval (0% to 100% or 0 to number of bad frames in a one second interval (0% to 100% or 0 to number of
frames per 1-second interval) and Number of consecutive intervals frames per 1-second interval) and Number of consecutive intervals
(between 2 and 10). Signal quality supervision in the optical (between 2 and 10). Signal quality supervision in the optical
transport layers is not specified by [G.798], it is indicated to be transport layers is not specified by [G.798], it is indicated to be
for further study. for further study.
2.4. Delay measurement
[G.709v3] introduced a tool for measuring round-trip delay of a
bidirectional ODU path or tandem connection. For implementing delay
measurement a one-bit delay measurement (DM) signal is defined in the
ODUk header. That signal is constant value (either 0 or 1). One
endpoint initiates a delay measurement by inverting the bit emitted
in the DM signal. The remote endpoint loops back the DM signal;
therefore, the delay measurement initiating node will receive the
inverted signal from the remote endpoint. This way the initiating
endpoint will determine the round trip delay.
3. RSVP-TE signaling extensions 3. RSVP-TE signaling extensions
3.1. Operation overview 3.1. Operation overview
RFC 4606 and RFC 4328 define the RSVP-TE extensions necessary to RFC 4606 and RFC 4328 define the RSVP-TE extensions necessary to
manage SDH/SONET and OTN optical and digital hierarchy connections. manage SDH/SONET and OTN optical and digital hierarchy connections.
The monitoring functions associated to these connections may be Connections for recent version of OTN, the OTNv3 are configured
configured together with configuring the connection itself. according to [OTNv3_SIG]. The monitoring functions associated to
these connections may be configured together with configuring the
connection itself.
The LSP Attribute Flag "OAM MEP entities desired" [GMPLS-OAM-FWK] is The LSP Attribute Flag "OAM MEP entities desired" [GMPLS-OAM-FWK] is
used to signal that the monitoring functions at the endpoints must be used to signal that the monitoring functions at the endpoints must be
established. The "OAM MIP entities desired" flag must be set to 0 established. The "OAM MIP entities desired" flag must be set to 0
and must be ignored. and must be ignored.
To configure OAM parameters the OAM Configuration TLV can be included To configure OAM parameters the OAM Configuration TLV can be included
in the LSP_ATTRIBUTES object. The TLV identifies which OAM in the LSP_ATTRIBUTES object. The TLV identifies which OAM
technology ("OAM Type" field) to be used as well as which OAM technology ("OAM Type" field) to be used as well as which OAM
functions are to be enabled (OAM Function Flags sub-TLV). For SONET/ functions are to be enabled (OAM Function Flags sub-TLV). For SONET/
SDH and OTN the "Continuity Check" and "Connectivity Verification" SDH and OTN the "Continuity Check" and "Connectivity Verification"
flags control the Continuity and Connectivity supervision functions, flags control the Continuity and Connectivity supervision functions,
while the "Performance Monitoring/Loss" flag enables the Signal while the "Performance Monitoring/Loss" flag enables the Signal
Quality supervision function. Since delay monitoring is not used for Quality supervision function.
SONET/SDH or OTN the "Performance Monitoring/Delay" flag must be
cleared. Recent release of OTN [G.709v3] introduced delay measurement for
paths. Such node enables delay measurement by setting "Performance
Monitoring/Delay" flag. By setting that flag the node also indicates
that it will initiate the delay measurement proactively; therefore,
the remote endpoint node should not initate delay measurement over
the configured connection proactively. Equipments designed according
to earlier version of G709 must clear "Performance Monitoring/Loss"
flag and upon receiving OAM configuration message with "Performance
Monitoring/Delay" flag set must generate "OAM Problem/Unsupported OAM
Function" error. The "Performance Monitoring/Delay" flag must be
cleared for SONET/SDH as it is not supported by SONET/SDH.
For additional details the appropriate technology specific sub-TLV For additional details the appropriate technology specific sub-TLV
can be carried in the OAM Configuration TLV. can be carried in the OAM Configuration TLV.
3.1.1. Continuity Check supervision 3.1.1. Continuity Check supervision
In case of both discussed technologies, setting up continuity In case of both discussed technologies, setting up continuity
supervision function for a connection does not need further supervision function for a connection does not need further
configuration besides enabling it. Therefore, by setting the configuration besides enabling it. Therefore, by setting the
"Connectivity Monitoring" Flag of OAM Function implicitly enables the "Connectivity Monitoring" Flag of OAM Function implicitly enables the
skipping to change at page 9, line 40 skipping to change at page 9, line 49
Furthermore, as only one level is allowed a single Signal quality Furthermore, as only one level is allowed a single Signal quality
supervision TLV is added to the OTN OAM Configuration TLV. supervision TLV is added to the OTN OAM Configuration TLV.
3.2. Signaling support of Virtual Concatenation Groups (VCG) 3.2. Signaling support of Virtual Concatenation Groups (VCG)
A key capability of both, SONET/SDH and OTN is the support of virtual A key capability of both, SONET/SDH and OTN is the support of virtual
concatenation. This inverse multiplexing method uses multiplicity of concatenation. This inverse multiplexing method uses multiplicity of
parallel basic signals. The supervision function parameters of these parallel basic signals. The supervision function parameters of these
basic signals can be different. basic signals can be different.
[GMPLS-VCAT-LCAS] summarises GMPLS signaling capabilities to support [RFC6344] summarises GMPLS signaling capabilities to support virtual
virtual concatenation and proposes extensions to that. A Virtual concatenation and proposes extensions to that. A Virtual
Concatenated Group (VCG) is constructed from several individual data Concatenated Group (VCG) is constructed from several individual data
plane signals. The co-routed signals of a VCG could be provisioned plane signals. The co-routed signals of a VCG could be provisioned
together using a single RSVP-TE session (co-signaled). As different together using a single RSVP-TE session (co-signaled). As different
OAM configuration may be applied to each of these individual signals, OAM configuration may be applied to each of these individual signals,
the OAM configuration extension is applied as follows. the OAM configuration extension is applied as follows.
We assume that the same OAM type and the same set of OAM functions We assume that the same OAM type and the same set of OAM functions
apply to every individual signal of the VCG. A single OAM apply to every individual signal of the VCG. A single OAM
Configuration TLV is carried in the LSP_ATTRIBUTES Object, while Configuration TLV is carried in the LSP_ATTRIBUTES Object, while
multiple instances of technology specific OAM configuration sub-TLVs multiple instances of technology specific OAM configuration sub-TLVs
are added: one instance per individual signal. The order of these are added: one instance per individual signal. The order of these
TLVs refers to the logical order of the basic signals (as they are TLVs refers to the logical order of the basic signals (as they are
listed in the Label Object). listed in the Label Object).
[GMPLS-VCAT-LCAS] allows extension/pruning of a VCG. To achieve it [RFC6344] allows extension/pruning of a VCG. To achieve it the
the traffic descriptor, which encodes how the VCG is structured, in traffic descriptor, which encodes how the VCG is structured, in the
the RSVP-TE session is updated. If the VCG is updated the contents RSVP-TE session is updated. If the VCG is updated the contents of
of the OAM Configuration TLV needs to be updated accordingly. the OAM Configuration TLV needs to be updated accordingly.
3.3. OAM types and functions 3.3. OAM types and functions
This document defines two new code points for the "OAM Type" field of This document defines two new code points for the "OAM Type" field of
the OAM Configuration TLV, defined in [GMPLS-OAM-FWK]: SONET/SDH OAM the OAM Configuration TLV, defined in [GMPLS-OAM-FWK]: SONET/SDH OAM
and OTN Digital Hierarchy OAM. and OTN Digital Hierarchy OAM.
OAM Type Description OAM Type Description
------------ ------------------ ------------ ------------------
3 SONET/SDH OAM 3 SONET/SDH OAM
4 OTN Digital Hierarchy OAM 4 OTN Digital Hierarchy OAM
The "OAM Function Flags sub-TLV", defined in [GMPLS-OAM-FWK]. SONET/ The "OAM Function Flags sub-TLV", defined in [GMPLS-OAM-FWK]. SONET/
SDH and OTN supervision functions are defined in this document for SDH and OTN supervision functions are defined in this document for
the following flags: "Continuity Check", "Connectivity Verification" the following flags: "Continuity Check", "Connectivity Verification",
and "Performance Monitoring/Loss". As delay measurement is not "Performance Monitoring/Loss" and "Performance Monitoring/Delay".
supported, requesting that function SHOULD generate an error with
code/value "OAM Problem/Unsupported OAM Function".
3.4. SONET/SDH OAM Configuration sub-TLV 3.4. SONET/SDH OAM Configuration sub-TLV
SONET/SDH OAM Configuration sub-TLV is defined to encode the SONET/SDH OAM Configuration sub-TLV is defined to encode the
parameters of continuity, connectivity and signal quality supervision parameters of continuity, connectivity and signal quality supervision
functions for SONET/SDH networks. functions for SONET/SDH networks.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 15, line 11 skipping to change at page 16, line 11
The field "DEG_M" defines monitoring time-frame in 1 second periods The field "DEG_M" defines monitoring time-frame in 1 second periods
assuming bursty distribution of errors. The valid values are 2 to 10 assuming bursty distribution of errors. The valid values are 2 to 10
periods. periods.
4. Error handling 4. Error handling
In addition to error values specified in [GMPLS-OAM-FWK] this In addition to error values specified in [GMPLS-OAM-FWK] this
document defines the following values for the "OAM Problem" Error document defines the following values for the "OAM Problem" Error
Code. Code.
o If Performance Measurement/Delay flag is set in the OAM Functions o In case of SONET/SDH if Performance Measurement/Delay flag is set
Flag sub-TLV, an error must be generated "OAM Problem/Unsupported in the OAM Functions Flag sub-TLV, an error must be generated "OAM
OAM Function". Problem/Unsupported OAM Function".
o In case of OTN if the equipment does not support delay measurement
and the Performance Measurement/Delay flag is set in the received
OAM Functions Flag sub-TLV, an error must be generated "OAM
Problem/Unsupported OAM Function".
o In case of SONET/SDH OAM when the length or format of the TTI to o In case of SONET/SDH OAM when the length or format of the TTI to
be configured is not supported by the referred SONET/SDH layer, an be configured is not supported by the referred SONET/SDH layer, an
error must be generated: "OAM Problem/TTI Length Mismatch". error must be generated: "OAM Problem/TTI Length Mismatch".
o If both "S" and "D" bits in OTN TTI Configuration TLV are set to o If both "S" and "D" bits in OTN TTI Configuration TLV are set to
0, error must be generated: "OAM Problem/Invalid CC/CV 0, error must be generated: "OAM Problem/Invalid CC/CV
configuration" configuration"
o If the APP is set to 1 and the next or the previous sub-TLV is not o If the APP is set to 1 and the next or the previous sub-TLV is not
skipping to change at page 19, line 25 skipping to change at page 20, line 25
8.2. Informative References 8.2. Informative References
[G.707] International Telecommunications Union, "Network node [G.707] International Telecommunications Union, "Network node
interface for the synchronous digital hierarchy (SDH)", interface for the synchronous digital hierarchy (SDH)",
ITU-T Recommendation G.707, January 2007. ITU-T Recommendation G.707, January 2007.
[G.709] International Telecommunications Union, "Interfaces for [G.709] International Telecommunications Union, "Interfaces for
the Optical Transport Network (OTN)", ITU-T the Optical Transport Network (OTN)", ITU-T
Recommendation G.709, March 2003. Recommendation G.709, March 2003.
[G.709v3] International Telecommunications Union, "Interfaces for
the Optical Transport Network (OTN)", ITU-T
Recommendation G.709, December 2009.
[G.798] International Telecommunications Union, "Characteristics [G.798] International Telecommunications Union, "Characteristics
of optical transport network hierarchy equipment of optical transport network hierarchy equipment
functional blocks", ITU-T Recommendation G.798, functional blocks", ITU-T Recommendation G.798,
December 2006. December 2006.
[G.806] International Telecommunications Union, "Characteristics [G.806] International Telecommunications Union, "Characteristics
of transport equipment - Description methodology and of transport equipment - Description methodology and
generic functionality", ITU-T Recommendation G.806, generic functionality", ITU-T Recommendation G.806,
January 2009. January 2009.
[GMPLS-VCAT-LCAS] [OTNv3_SIG]
Bernstein, G., Rabbat, R., and H. Helvoort, "Operating Zhang, F., Zhang, G., Belotti, S., Ceccarelli, D., and K.
Virtual Concatenation (VCAT) and the Link Capacity Pithewan, "Operating Virtual Concatenation (VCAT) and the
Adjustment Scheme (LCAS) with Generalized Multi-Protocol Link Capacity Adjustment Scheme (LCAS) with Generalized
Label Switching (GMPLS)", Multi-Protocol Label Switching (GMPLS)",
draft-ietf-ccamp-gmpls-vcat-lcas-07 (work in progress), draft-ietf-ccamp-gmpls-signaling-g709v3-01 (work in
December 2008. progress), October 2011.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4328] Papadimitriou, D., "Generalized Multi-Protocol Label [RFC4328] Papadimitriou, D., "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Extensions for G.709 Optical Switching (GMPLS) Signaling Extensions for G.709 Optical
Transport Networks Control", RFC 4328, January 2006. Transport Networks Control", RFC 4328, January 2006.
[RFC4606] Mannie, E. and D. Papadimitriou, "Generalized Multi- [RFC4606] Mannie, E. and D. Papadimitriou, "Generalized Multi-
Protocol Label Switching (GMPLS) Extensions for Protocol Label Switching (GMPLS) Extensions for
Synchronous Optical Network (SONET) and Synchronous Synchronous Optical Network (SONET) and Synchronous
Digital Hierarchy (SDH) Control", RFC 4606, August 2006. Digital Hierarchy (SDH) Control", RFC 4606, August 2006.
[RFC6344] Bernstein, G., Caviglia, D., Rabbat, R., and H. Helvoort,
"Operating Virtual Concatenation (VCAT) and the Link
Capacity Adjustment Scheme (LCAS) with Generalized Multi-
Protocol Label Switching (GMPLS)", RFC 6344, August 2011.
Authors' Addresses Authors' Addresses
Andras Kern Andras Kern
Ericsson Ericsson
Laborc u. 1. Laborc u. 1.
Budapest, 1037 Budapest, 1037
Hungary Hungary
Email: andras.kern@ericsson.com Email: andras.kern@ericsson.com
 End of changes. 23 change blocks. 
59 lines changed or deleted 91 lines changed or added

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