draft-ietf-ccamp-oam-configuration-fwk-05.txt   draft-ietf-ccamp-oam-configuration-fwk-06.txt 
Network Working Group A. Takacs Network Working Group A. Takacs
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Standards Track D. Fedyk Intended status: Standards Track D. Fedyk
Expires: September 15, 2011 Alcatel-Lucent Expires: January 12, 2012 Alcatel-Lucent
J. He J. He
Huawei Huawei
March 14, 2011 July 11, 2011
GMPLS RSVP-TE extensions for OAM Configuration GMPLS RSVP-TE extensions for OAM Configuration
draft-ietf-ccamp-oam-configuration-fwk-05 draft-ietf-ccamp-oam-configuration-fwk-06
Abstract Abstract
OAM is an integral part of transport connections, hence it is OAM is an integral part of transport connections, hence it is
required that OAM functions are activated/deactivated in sync with required that OAM functions are activated/deactivated in sync with
connection commissioning/decommissioning; avoiding spurious alarms connection commissioning/decommissioning; avoiding spurious alarms
and ensuring consistent operation. In certain technologies OAM and ensuring consistent operation. In certain technologies OAM
entities are inherently established once the connection is set up, entities are inherently established once the connection is set up,
while other technologies require extra configuration to establish and while other technologies require extra configuration to establish and
configure OAM entities. This document specifies extensions to configure OAM entities. This document specifies extensions to
skipping to change at page 2, line 26 skipping to change at page 2, line 26
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 15, 2011. This Internet-Draft will expire on January 12, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 4, line 11 skipping to change at page 4, line 11
8.1. Normative References . . . . . . . . . . . . . . . . . . . 22 8.1. Normative References . . . . . . . . . . . . . . . . . . . 22
8.2. Informative References . . . . . . . . . . . . . . . . . . 22 8.2. Informative References . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24
1. Introduction 1. Introduction
GMPLS is designed as an out-of-band control plane supporting dynamic GMPLS is designed as an out-of-band control plane supporting dynamic
connection provisioning for any suitable data plane technology; connection provisioning for any suitable data plane technology;
including spatial switching (e.g., incoming port or fiber to outgoing including spatial switching (e.g., incoming port or fiber to outgoing
port or fiber), wavelength-division multiplexing (e.g., DWDM), time- port or fiber), wavelength-division multiplexing (e.g., DWDM), time-
division multiplexing (e.g., SONET/SDH, G.709), and lately Ethernet division multiplexing (e.g., SONET/SDH, G.709), and Ethernet Provider
Provider Backbone Bridging -- Traffic Engineering (PBB-TE) and MPLS Backbone Bridging -- Traffic Engineering (PBB-TE) and MPLS. In most
Transport Profile (MPLS-TP). In most of these technologies there are of these technologies there are Operations, Administration and
Operations and Management (OAM) functions employed to monitor the Maintenance (OAM) functions employed to monitor the health and
health and performance of the connections and to trigger data plane performance of the connections and to trigger data plane (DP)
(DP) recovery mechanisms. Similarly to connections, OAM functions recovery mechanisms. Similarly to connections, OAM functions follow
follow general principles but also have some technology specific general principles but also have some technology specific
characteristics. characteristics.
OAM is an integral part of transport connections, hence it is OAM is an integral part of transport connections, hence it is
required that OAM functions are activated/deactivated in sync with required that OAM functions are activated/deactivated in sync with
connection commissioning/decommissioning; avoiding spurious alarms connection commissioning/decommissioning; avoiding spurious alarms
and ensuring consistent operation. In certain technologies OAM and ensuring consistent operation. In certain technologies OAM
entities are inherently established once the connection is set up, entities are inherently established once the connection is set up,
while other technologies require extra configuration to establish and while other technologies require extra configuration to establish and
configure OAM entities. In some situations the use of OAM functions, configure OAM entities. In some situations the use of OAM functions,
like those of Fault- (FM) and Performance Management (PM), may be like those of Fault- (FM) and Performance Management (PM), may be
skipping to change at page 5, line 5 skipping to change at page 5, line 5
activated via the management plane. On the other hand, it should be activated via the management plane. On the other hand, it should be
possible to activate/deactivate pro-active OAM functions via the possible to activate/deactivate pro-active OAM functions via the
GMPLS control plane as well. GMPLS control plane as well.
This document describes requirements on OAM configuration and control This document describes requirements on OAM configuration and control
via RSVP-TE, and specifies extensions to the RSVP-TE protocol via RSVP-TE, and specifies extensions to the RSVP-TE protocol
providing a framework to configure and control OAM entities along providing a framework to configure and control OAM entities along
with the capability to carry technology specific information. with the capability to carry technology specific information.
Extensions can be grouped into generic elements that are applicable Extensions can be grouped into generic elements that are applicable
to any OAM solution and technology specific elements that provide to any OAM solution and technology specific elements that provide
additional configuration parameters, only needed for a specific OAM additional configuration parameters, which are only needed for a
technology. This document specifies the technology agnostic specific OAM technology. This document specifies the technology
elements, which alone can be used to establish and control OAM agnostic elements, which alone can be used to establish and control
entities in the case no technology specific information is needed, OAM entities in the case no technology specific information is
and specifies the way additional technology specific OAM parameters needed, and specifies the way additional technology specific OAM
are provided. parameters are provided.
This document addresses end-to-end OAM configuration, that is, the This document addresses end-to-end OAM configuration, that is, the
setup of OAM entities bound to an end-to-end LSP, and configuration setup of OAM entities bound to an end-to-end LSP, and configuration
and control of OAM functions running end-to-end in the LSP. and control of OAM functions running end-to-end in the LSP.
Configuration of OAM entities for LSP segments and tandem connections Configuration of OAM entities for LSP segments and tandem connections
are out of the scope of this document. are out of the scope of this document.
The mechanisms described in this document provide an additional The mechanisms described in this document provide an additional
option for bootstrapping OAM that is not intended to replace or option for bootstrapping OAM that is not intended to replace or
deprecate the use of other technology specific OAM bootstrapping deprecate the use of other technology specific OAM bootstrapping
skipping to change at page 9, line 30 skipping to change at page 9, line 30
association creates a context for the OAM entities monitoring the association creates a context for the OAM entities monitoring the
LSP. On top of this association OAM entities may be configured to LSP. On top of this association OAM entities may be configured to
unambigously identify MPs and MEs. unambigously identify MPs and MEs.
In addition to MP and ME identification parameters pro-active OAM In addition to MP and ME identification parameters pro-active OAM
functions (e.g., Continuity Check (CC), Performance Monitoring) may functions (e.g., Continuity Check (CC), Performance Monitoring) may
have specific parameters requiring configuration as well. In have specific parameters requiring configuration as well. In
particular, the frequency of periodic CC packets and the measurement particular, the frequency of periodic CC packets and the measurement
interval for loss and delay measurements may need to be configured. interval for loss and delay measurements may need to be configured.
In some cases all the above parameters may be either derived form In some cases all the above parameters may be either derived from
some exiting information or pre-configured default values can be some exiting information or pre-configured default values can be
used. In the simplest case the control plane needs to provide used. In the simplest case the control plane needs to provide
information whether or not OAM entities need to be setup for the information whether or not OAM entities need to be setup for the
signaled LSP. If OAM entities are created signaling must provide signaled LSP. If OAM entities are created signaling must provide
means to activate/deactivate OAM message flows and associated alarms. means to activate/deactivate OAM message flows and associated alarms.
OAM identifiers as well as the configuration of OAM functions are OAM identifiers as well as the configuration of OAM functions are
technology specific, i.e., vary depending on the data plane technology specific, i.e., vary depending on the data plane
technology and the chosen OAM solution. In addition, for any given technology and the chosen OAM solution. In addition, for any given
data plane technology a set of OAM solutions may be applicable. The data plane technology a set of OAM solutions may be applicable. The
OAM configuration framework allows selecting a specific OAM solution OAM configuration framework allows selecting a specific OAM solution
to be used for the signaled LSP and provides technology specific TLVs to be used for the signaled LSP and provides technology specific TLVs
to carry further detailed configuration information. to carry further detailed configuration information.
3.1. Establishment of OAM Entities and Functions 3.1. Establishment of OAM Entities and Functions
In order to avoid spurious alarms OAM functions must be setup and In order to avoid spurious alarms OAM functions should be setup and
enabled in the appropriate order. When using the GMPLS control enabled in the appropriate order. When using the GMPLS control
plane, establishment and enabling of OAM functions must be bound to plane, establishment and enabling of OAM functions MUST be bound to
RSVP-TE message exchanges. RSVP-TE message exchanges.
An LSP may be signaled and established without OAM configuration An LSP can be signaled and established without OAM configuration
first, and OAM entities may be added later with a subsequent re- first, and OAM entities can be added later with a subsequent re-
signaling of the LSP. Alternatively, the LSP may be setup with OAM signaling of the LSP. Alternatively, the LSP can be setup with OAM
entities right with the first signaling of the LSP. The below entities right with the first signaling of the LSP. The below
procedures apply to both cases. procedures apply to both cases.
Before the initiator first sends a Path messages with OAM Before the initiator first sends a Path messages with OAM
Configuration information, it MUST establish and configure the Configuration information, it MUST establish and configure the
corresponding OAM entities locally, however OAM source functions MUST corresponding OAM entities locally, however OAM source functions MUST
NOT start sending any OAM messages. In the case of bidirectional NOT start sending any OAM messages. In the case of bidirectional
connections, the initiator node MUST setup the OAM sink function to connections, the initiator node MUST setup the OAM sink function to
be prepared to receive OAM messages but MUST suppress any OAM alarms be prepared to receive OAM messages but MUST suppress any OAM alarms
(e.g., due to missing or unidentified OAM messages). The Path (e.g., due to missing or unidentified OAM messages). The Path
skipping to change at page 13, line 30 skipping to change at page 13, line 30
to act on them. The LSP_ATTRIBUTES and the LSP_REQUIRED_ATTRIBUTES to act on them. The LSP_ATTRIBUTES and the LSP_REQUIRED_ATTRIBUTES
objects are defined in [RFC5420] to provide means to signal LSP objects are defined in [RFC5420] to provide means to signal LSP
attributes and options in the form of TLVs. Options and attributes attributes and options in the form of TLVs. Options and attributes
signaled in the LSP_ATTRIBUTES object can be passed transparently signaled in the LSP_ATTRIBUTES object can be passed transparently
through LSRs not supporting a particular option or attribute, while through LSRs not supporting a particular option or attribute, while
the contents of the LSP_REQUIRED_ATTRIBUTES object must be examined the contents of the LSP_REQUIRED_ATTRIBUTES object must be examined
and processed by each LSR. One TLV is defined in [RFC5420]: the and processed by each LSR. One TLV is defined in [RFC5420]: the
Attributes Flags TLV. Attributes Flags TLV.
One bit (IANA to assign): "OAM MEP entities desired" is allocated in One bit (IANA to assign): "OAM MEP entities desired" is allocated in
the LSP Attributes Flags TLV. If the "OAM MEP entities desired" bit the LSP Attributes Flags TLV to be used in the LSP_ATTRIBUTES object.
is set it is indicating that the establishment of OAM MEP entities If the "OAM MEP entities desired" bit is set it is indicating that
are required at the endpoints of the signaled LSP. If the the establishment of OAM MEP entities are required at the endpoints
establishment of MEPs is not supported an error must be generated: of the signaled LSP. If the establishment of MEPs is not supported
"OAM Problem/MEP establishment not supported". an error must be generated: "OAM Problem/MEP establishment not
supported".
If the "OAM MEP entities desired" bit is set but additional If the "OAM MEP entities desired" bit is set and additional
parameters need also to be configured, an OAM Configuration TLV MAY parameters need to be configured, an OAM Configuration TLV MAY be
be included in the LSP_ATTRIBUTES Object. included in the LSP_ATTRIBUTES Object.
One bit (IANA to assign): "OAM MIP entities desired" is allocated in One bit (IANA to assign): "OAM MIP entities desired" is allocated in
the LSP Attributes Flags TLV. This bit can only be set if the "OAM the LSP Attributes Flags TLV to be used in the LSP_ATTRIBUTES or
MEP entities desired" bit is set. If the "OAM MIP entities desired" LSP_REQUIRED_ATTRIBUES objects. This bit can only be set if the "OAM
bit is set in the LSP_ATTRIBUTES Flags TLV in the MEP entities desired" bit is set in. If the "OAM MIP entities
desired" bit is set in the LSP_ATTRIBUTES Flags TLV in the
LSP_REQUIRED_ATTRIBUTES Object, it is indicating that the LSP_REQUIRED_ATTRIBUTES Object, it is indicating that the
establishment of OAM MIP entities is required at every transit node establishment of OAM MIP entities is required at every transit node
of the signalled LSP. If the establishment of a MIP is not supported of the signalled LSP. If the establishment of a MIP is not supported
an error must be generated: "OAM Problem/MIP establishment not an error MUST be generated: "OAM Problem/MIP establishment not
supported". supported".
4.2. OAM Configuration TLV 4.2. OAM Configuration TLV
This TLV provides information about which OAM technology/method This TLV provides information about which OAM technology/method
should be used and carries sub-TLVs for any additional OAM should be used and carries sub-TLVs for any additional OAM
configuration information. The OAM Configuration TLV may be carried configuration information. The OAM Configuration TLV MAY be carried
in the LSP_ATTRIBUTES or LSP_REQUIRED_ATTRIBUTES object in Path and in the LSP_ATTRIBUTES or LSP_REQUIRED_ATTRIBUTES object in Path and
Resv messages. Resv messages. When carried in the LSP_REQUIRED_ATTRIBUTES object it
is indicating that intermediate nodes MUST recognize and eventually
react on the OAM configuration onformation.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (IANA) | Length | | Type (IANA) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OAM Type | Reserved | | OAM Type | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ sub-TLVs ~ ~ sub-TLVs ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: indicates a new type: the OAM Configuration TLV (3) (IANA to Type: indicates a new type: the OAM Configuration TLV (3) (IANA to
assign). assign).
OAM Type: specifies the technology specific OAM method. When carried OAM Type: specifies the technology specific OAM method. When carried
in the LSP_REQUIRED_ATTRIBUTES Object, if the requested OAM method is in the LSP_REQUIRED_ATTRIBUTES Object, if the requested OAM method is
not supported at a given node an error must be generated: "OAM not supported at a given node an error MUST be generated: "OAM
Problem/Unsupported OAM Type". When carried in the LSP_ATTRIBUTES Problem/Unsupported OAM Type". When carried in the LSP_ATTRIBUTES
Object, intermediate nodes not supporting the OAM Type pass the Object, intermediate nodes not supporting the OAM Type pass the
object forward unchanged as specified in [RFC5420] only Label Edge object forward unchanged as specified in [RFC5420] only Label Edge
Nodes must generate the error if the OAM Type is not supported. Nodes MUST generate the error if the OAM Type is not supported.
OAM Type Description OAM Type Description
------------ -------------------- ------------ --------------------
0-255 Reserved 0-255 Reserved
This document defines no types. IANA is requested to maintain the This document defines no types. IANA is requested to maintain the
values in a new "RSVP-TE OAM Configuration Registry". values in a new "RSVP-TE OAM Configuration Registry".
The receiving node based on the OAM Type will check if a The receiving node based on the OAM Type will check if a
corresponding technology specific OAM configuration sub-TLV is corresponding technology specific OAM configuration sub-TLV is
included. If the included technology specific OAM configuration sub- included. If the included technology specific OAM configuration sub-
TLV is different than what is specified in the OAM Type an error must TLV is different than what is specified in the OAM Type an error MUST
be generated: "OAM Problem/OAM Type Mismatch". IANA is requested to be generated: "OAM Problem/OAM Type Mismatch". IANA is requested to
maintain the sub-TLV space in the new "RSVP-TE OAM Configuration maintain the sub-TLV space in the new "RSVP-TE OAM Configuration
Registry". Registry".
Note that there is a hierarchical dependency in between the OAM Note that there is a hierarchical dependency in between the OAM
configuration elements. First, the "OAM MEP (and MIP) entities configuration elements. First, the "OAM MEP (and MIP) entities
desired" flag needs to be set. Only when that is set MAY an "OAM desired" flag needs to be set. Only when that is set MAY an "OAM
Configuration TLV" be included in the LSP_ATTRIBUTES or Configuration TLV" be included in the LSP_ATTRIBUTES or
LSP_REQUIRED_ATTRIBUTES Object. When this TLV is present, based on LSP_REQUIRED_ATTRIBUTES Object. When this TLV is present, based on
the "OAM Type" field, it MAY carry a technology specific OAM the "OAM Type" field, it MAY carry a technology specific OAM
skipping to change at page 15, line 42 skipping to change at page 16, line 5
~ OAM Function Flags ~ ~ OAM Function Flags ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
OAM Function Flags is bitmap with extensible length based on the OAM Function Flags is bitmap with extensible length based on the
Lenght field of the TLV. Bits are numbered from left to right. IANA Lenght field of the TLV. Bits are numbered from left to right. IANA
is requested to maintain the OAM Function Flags in the new "RSVP-TE is requested to maintain the OAM Function Flags in the new "RSVP-TE
OAM Configuration Registry". This document defines the following OAM Configuration Registry". This document defines the following
flags. flags.
OAM Function Flag bit# Description OAM Function Flag bit# Description
--------------------- --------------------------- --------------------- ---------------------------
0 Continuity Check (CC) 0 Continuity Check (CC)
1 Connectivity Verification (CV) 1 Connectivity Verification (CV)
2 Performance Monitoring/Loss (PM/Loss) 2 Fault Monitoring Signal (FMS)
3 Performance Monitoring/Delay (PM/Delay) 3 Performance Monitoring/Loss (PM/Loss)
4 Performance Monitoring/Delay (PM/Delay)
5 Performance Monitoring/Throughput Measurement
(PM/Throughput)
4.2.2. Technology Specific sub-TLVs 4.2.2. Technology Specific sub-TLVs
One technology specific sub-TLV MAY be defined for each "OAM Type". One technology specific sub-TLV MAY be defined for each "OAM Type".
This sub-TLV MUST contain any further OAM configuration information This sub-TLV MUST contain any further OAM configuration information
for that specific "OAM Type". The technology specific sub-TLV, when for that specific "OAM Type". The technology specific sub-TLV, when
used, MUST be carried within the OAM Configuration TLV. IANA is used, MUST be carried within the OAM Configuration TLV. IANA is
requested to maintain the sub-TLV space in the new "RSVP-TE OAM requested to maintain the sub-TLV space in the new "RSVP-TE OAM
Configuration Registry". Configuration Registry".
skipping to change at page 18, line 23 skipping to change at page 18, line 34
of the leaves could the OAM sink functions be established. If all of the leaves could the OAM sink functions be established. If all
leaves established OAM entities successfully, the root can enable the leaves established OAM entities successfully, the root can enable the
OAM message flow. On the other hand, if at some leaves the OAM message flow. On the other hand, if at some leaves the
establishment was unsuccessful additional actions will be needed establishment was unsuccessful additional actions will be needed
before the OAM message flow can be enabled. Such action could be to before the OAM message flow can be enabled. Such action could be to
setup two independent P2MP LSPs. One with OAM Configuration setup two independent P2MP LSPs. One with OAM Configuration
information towards leaves which successfully setup OAM. This can be information towards leaves which successfully setup OAM. This can be
done by prunning the leaves which failed to setup OAM of the done by prunning the leaves which failed to setup OAM of the
previously signalled P2MP LSP. The other P2MP LSP could be previously signalled P2MP LSP. The other P2MP LSP could be
constructed for leaves without OAM entities. What exact procedures constructed for leaves without OAM entities. What exact procedures
are needed are technology specific and should be described in are needed are technology specific and SHOULD be described in
technology specific documents. technology specific documents.
5. IANA Considerations 5. IANA Considerations
Two bits ("OAM Alarms Enabled" (O) and "OAM Flows Enabled" (M)) needs Two bits ("OAM Alarms Enabled" (O) and "OAM Flows Enabled" (M)) needs
to be allocated in the ADMIN_STATUS Object. to be allocated in the ADMIN_STATUS Object.
Two bits ("OAM MEP entities desired" and "OAM MIP entities desired") Two bits ("OAM MEP entities desired" and "OAM MIP entities desired")
needs to be allocated in the LSP Attributes Flags Registry. needs to be allocated in the LSP Attributes Flags Registry.
skipping to change at page 24, line 9 skipping to change at page 24, line 9
July 2010. July 2010.
[RFC6060] "Generalized Multiprotocol Label Switching (GMPLS) Control [RFC6060] "Generalized Multiprotocol Label Switching (GMPLS) Control
of Ethernet Provider Backbone Traffic Engineering of Ethernet Provider Backbone Traffic Engineering
(PBB-TE)", RFC 6060. (PBB-TE)", RFC 6060.
Authors' Addresses Authors' Addresses
Attila Takacs Attila Takacs
Ericsson Ericsson
Laborc u. 1. Konyves Kalman krt. 11.
Budapest, 1037 Budapest, 1097
Hungary Hungary
Email: attila.takacs@ericsson.com Email: attila.takacs@ericsson.com
Don Fedyk Don Fedyk
Alcatel-Lucent Alcatel-Lucent
Groton, MA 01450 Groton, MA 01450
USA USA
Email: donald.fedyk@alcatel-lucent.com Email: donald.fedyk@alcatel-lucent.com
 End of changes. 22 change blocks. 
49 lines changed or deleted 56 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/