draft-ietf-ccamp-lmp-04.txt   draft-ietf-ccamp-lmp-05.txt 
Network Working Group Jonathan P. Lang, Editor Network Working Group J. Lang, Editor
Internet Draft Internet Draft Calient Networks
Expiration Date: December 2002 Category: Standards Track August 2002
Expires: February 2003
June 2002
Link Management Protocol (LMP) Link Management Protocol (LMP)
draft-ietf-ccamp-lmp-04.txt draft-ietf-ccamp-lmp-05.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026 [RFC2026]. all provisions of Section 10 of RFC2026.
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), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as reference at any time. It is inappropriate to use Internet-Drafts as
material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Abstract
Optical networks are being developed to include photonic switches, For scalability purposes, multiple data links can be combined to
optical crossconnects, and routers that are configured with control form a single traffic engineering (TE) link. Furthermore, the
channels and data links. Furthermore, multiple data links may be management of TE links is not restricted to in-band messaging, but
combined to form a single traffic engineering (TE) link for routing instead can be done using out-of-band techniques. This document
purposes. This draft specifies a link management protocol (LMP) that specifies a link management protocol (LMP) that runs between
runs between neighboring nodes and is used to manage TE links. neighboring nodes and is used to manage TE links. Specifically, LMP
Specifically, LMP will be used to maintain control channel will be used to maintain control channel connectivity, verify the
connectivity, verify the physical connectivity of the data-bearing physical connectivity of the data links, correlate the link property
channels, correlate the link property information, suppress information, suppress downstream alarms, and localize link failures
downstream alarms, and localize link failures for for protection/restoration purposes in multiple kinds of networks.
protection/restoration purposes in both opaque and transparent
networks.
Table of Contents Table of Contents
1 Introduction ................................................ 4 1 Introduction ................................................ 5
2 LMP Overview ................................................ 5 1.1 Terminology ............................................. 5
3 Control Channel Management ................................... 7 2 LMP Overview ................................................ 8
3.1 Parameter Negotiation ................................... 8 3 Control Channel Management .................................. 10
3.2 Hello Protocol ........................................... 9 3.1 Parameter Negotiation ................................... 11
3.2.1 Hello Parameter Negotiation ....................... 9 3.2 Hello Protocol .......................................... 12
3.2.2 Fast Keep-alive .................................. 10 3.2.1 Hello Parameter Negotiation ...................... 12
3.2.3 Control Channel Down ............................. 11 3.2.2 Fast Keep-alive .................................. 13
3.2.4 Degraded (DEG) State ............................. 11 3.2.3 Control Channel Down ............................. 13
4 Link Property Correlation ................................... 11 3.2.4 Degraded State ................................... 14
5 Verifying Link Connectivity ................................. 13 4 Link Property Correlation ................................... 14
5.1 Example of Link Connectivity Verification ............... 16 5 Verifying Link Connectivity ................................. 16
6 Fault Management ............................................ 17 5.1 Example of Link Connectivity Verification ............... 18
6.1 Fault Detection ......................................... 17 6 Fault Management ............................................ 20
6.2 Fault Localization Procedure ............................ 18 6.1 Fault Detection ......................................... 20
6.3 Examples of Fault Localization .......................... 18 6.2 Fault Localization Procedure ............................ 20
6.4 Channel Activation Indication ........................... 19 6.3 Examples of Fault Localization .......................... 21
6.5 Channel Deactivation Indication ......................... 20 6.4 Channel Activation Indication ........................... 22
7 Message_Id Usage ............................................ 20 6.5 Channel Deactivation Indication ......................... 22
8 Graceful Restart ............................................ 21 7 Message_Id Usage ............................................ 23
9 Addressing .................................................. 22 8 Graceful Restart ............................................ 24
10 Exponential Back-off Procedures ............................. 23 9 Addressing .................................................. 25
10.1 Operation.................................................. 23 10 Exponential Back-off Procedures ............................. 25
10.2 Retransmission Algorithm .................................. 23 10.1 Operation............................................... 25
11 IANA Considerations ......................................... 24 10.2 Retransmission Algorithm ............................... 26
12 LMP Finite State Machines ................................... 24 11 LMP Finite State Machines ................................... 27
12.1 Control Channel FSM .................................... 24 11.1 Control Channel FSM .................................... 27
12.1.1 Control Channel States .......................... 24 11.1.1 Control Channel States .......................... 27
12.1.2 Control Channel Events .......................... 25 11.1.2 Control Channel Events .......................... 28
12.1.3 Control Channel FSM Description ................. 28 11.1.3 Control Channel FSM Description ................. 30
12.2 TE Link FSM ............................................ 29 11.2 TE Link FSM ............................................ 31
12.2.1 TE link States .................................. 29 11.2.1 TE Link States .................................. 31
12.2.2 TE link Events .................................. 29 11.2.2 TE Link Events .................................. 31
12.2.3 TE link FSM Description ......................... 30 11.2.3 TE Link FSM Description ......................... 32
12.3 Data Link FSM .......................................... 30 11.3 Data Link FSM .......................................... 32
12.3.1 Data Link States ................................ 31 11.3.1 Data Link States ................................ 33
12.3.2 Data Link Events ................................ 31 11.3.2 Data Link Events ................................ 33
12.3.3 Active Data Link FSM Description ................ 33 11.3.3 Active Data Link FSM Description ................ 35
12.3.4 Passive Data Link FSM Description ............... 34 11.3.4 Passive Data Link FSM Description ............... 36
13 LMP Message Formats ......................................... 35 12 LMP Message Formats ......................................... 37
13.1 Common Header .......................................... 35 12.1 Common Header .......................................... 37
13.2 LMP Object Format ...................................... 36 12.2 LMP Object Format ...................................... 38
13.3 Parameter Negotiation .................................. 37 12.3 Parameter Negotiation Messages ......................... 39
13.4 Hello .................................................. 39 12.4 Hello Message .......................................... 41
13.5 Link Verification ...................................... 39 12.5 Link Verification Messages ............................. 41
13.6 Link Summary ........................................... 43 12.6 Link Summary Messages .................................. 45
13.7 Fault Management ....................................... 44 12.7 Fault Management Messages .............................. 46
14 LMP Object Definitions ...................................... 45 13 LMP Object Definitions ...................................... 47
15 Security Conderations ....................................... 63 14 Intellectual Property Considerations ........................ 65
16 Intellectual Property Considerations ........................ 63 15 References .................................................. 65
17 References .................................................. 63 16 Security Considerations ..................................... 66
18 Acknowledgments ............................................. 64 16.1 Security Requirements .................................. 66
19 Contributors ................................................ 65 16.2 Security Mechanisms .................................... 67
20 Contact Address ............................................. 65 17 IANA Considerations ......................................... 68
18 Acknowledgements ............................................ 71
19 Contributors ................................................ 72
20 Contact Address ............................................. 72
21 Full Copyright Statement .................................... 73
[Editor's note: śśChanges from previous version∆∆ notes can be removed
prior to publication as an RFC.]
Changes from previous version: Changes from previous version:
o Editorial changes. o Editorial changes.
o Changed LMP from running directly over IP to running over UDP. o Added a terminology section
o Added Section describing exponential back-off procedures. o Added text to the Security Considerations section.
o Added suggested values for timers. o Removed discussion of the BeginVerifyTransport flags for specific
o Merged the LOCAL/REMOTE Id classes into single class. Encoding Types to a separate Internet Draft.
o Merged the MESSAGE_ID/MESSAGE_ID_ACK classes into single class. o Added a terminology section.
o Removed the MD5 security option. o Removed the LMP checksum.
o Clarified the IANA Considerations section with assignment rules
and suggested values.
1. Introduction 1. Introduction
Optical networks are being developed with photonic switches (PXCs), Networks are being developed with routers, switches, crossconnects,
optical crossconnects (OXCs), routers, switches, DWDM systems, and DWDM systems, and add-drop multiplexors (ADMs) that use a common
add-drop multiplexors (ADMs) that use a common control plane [e.g., control plane [e.g., Generalized MPLS (GMPLS)] to dynamically
Generalized MPLS (GMPLS)] to dynamically allocate resources and to allocate resources and to provide network survivability using
provide network survivability using protection and restoration protection and restoration techniques. A pair of nodes may have
techniques. A pair of nodes (e.g., two PXCs) may be connected by thousands of interconnects, where each interconnect may consist of
thousands of fibers, and each fiber may be used to transmit multiple multiple data links when multiplexing (e.g., Frame Relay DLCIs at
wavelengths if DWDM is used. Furthermore, multiple fibers and/or Layer 2, or TDM slots or WDM wavelengths at Layer 1) is used. For
multiple wavelengths may be combined into a single traffic- scalability purposes, multiple data links may be combined into a
engineering (TE) link for routing purposes. To enable communication single traffic-engineering (TE) link.
between nodes for routing, signaling, and link management, control
channels must be established between the node pair; however, the
interface over which the control messages are sent/received may not
be the same interface over which the data flows. This draft
specifies a link management protocol (LMP) that runs between
neighboring nodes and is used to manage TE links.
In this draft, OXC is used to refer to all categories of optical To enable communication between nodes for routing, signaling, and
crossconnects irrespective of the internal switching fabric. link management, there must be a pair of IP interfaces that are
Furthermore, a distinction is made between crossconnects that mutually reachable. We call such a pair of interfaces a control
require opto-electronic conversion, called digital crossconnects channel. Note that "mutually reachable" does not imply that these
(DXCs), and those that are all-optical, called photonic switches or two interfaces are (directly) connected by an IP link; there may be
photonic crossconnects (PXCs) Ż often referred to as pure an IP network between the two. Furthermore, the interface over
crossconnects [LAMBDA] because their transparent nature introduces which the control messages are sent/received may not be the same
new restrictions for monitoring and managing the data links. LMP can interface over which the data flows. This document specifies a link
be used for any type of node, enhancing the functionality of management protocol (LMP) that runs between neighboring nodes and is
traditional DXCs and routers, while enabling PXCs and DWDMs to used to manage TE links and verify reachability of the control
intelligently interoperate in heterogeneous optical networks. channel.
In GMPLS, the control channels between two adjacent nodes are no In GMPLS, the control channels between two adjacent nodes are no
longer required to use the same physical medium as the data-bearing longer required to use the same physical medium as the data links
links between those nodes. For example, a control channel could use between those nodes. For example, a control channel could use a
a separate wavelength or fiber, an Ethernet link, an IP tunnel separate virtual circuit, wavelength, fiber, Ethernet link, an IP
through a separate management network, or a multi-hop IP network. A tunnel routed over a separate management network, or a multi-hop IP
consequence of allowing the control channel(s) between two nodes to network. A consequence of allowing the control channel(s) between
be physically diverse from the associated data links is that the two nodes to be logically or physically diverse from the associated
health of a control channel does not necessarily correlate to the data links is that the health of a control channel does not
health of the data links, and vice-versa. Therefore, a clean necessarily correlate to the health of the data links, and vice-
separation between the fate of the control channel and data-bearing versa. Therefore, a clean separation between the fate of the
links must be made. New mechanisms must be developed to manage the control channel and data links must be made. New mechanisms must be
data-bearing links, both in terms of link provisioning and fault developed to manage the data links, both in terms of link
management. provisioning and fault management.
For the purposes of this document, a data-bearing link may be either Among the tasks that LMP accomplishes is checking that the grouping
a "port" or a "component link" depending on its multiplexing of links into TE links as well as the properties of those links are
capability; component links are multiplex capable, whereas ports are the same at both end points of the links -- this is called "link
property correlation". Also, LMP can communicate these link
properties to the IGP module, which can then announce them to other
nodes in the network. LMP can also tell the signaling module the
mapping between TE links and control channels. Thus, LMP performs a
valuable "glue" function in the control plane.
Note that while the existence of the control network (single or
multi-hop) is necessary for enabling communication, it is by no
means sufficient. For example, if the two interfaces are separated
by an IP network, faults in the IP network may result in the lack of
an IP path from one interface to another, and therefore in an
interruption of communication between the two interfaces. On the
other hand, not every failure in the control network affects a given
control channel, hence the need for establishing and managing
control channels.
For the purposes of this document, a data link may be considered by
each node that it terminates on as either a 'port' or a 'component
link' depending on the multiplexing capability of the endpoint on
that link; component links are multiplex capable, whereas ports are
not multiplex capable. This distinction is important since the not multiplex capable. This distinction is important since the
management of such links (including, for example, resource management of such links (including, for example, resource
allocation, label assignment, and their physical verification) is allocation, label assignment, and their physical verification) is
different based on their multiplexing capability. For example, a different based on their multiplexing capability. For example, a
SONET crossconnect with OC-192 interfaces may be able to demultiplex Frame Relay switch is able to demultiplex an interface into virtual
the OC-192 stream into four OC-48 streams. If multiple interfaces circuits based on DLCIs; similarly, a SONET crossconnect with OC-192
are grouped together into a single TE link using link bundling interfaces may be able to demultiplex the OC-192 stream into four
[BUNDLE], then the link resources must be identified using three OC-48 streams. If multiple interfaces are grouped together into a
levels: TE link Id, component interface Id, and timeslot label. single TE link using link bundling [BUNDLE], then the link resources
Resource allocation happens at the lowest level (timeslots), but must be identified using three levels: Link_Id, component interface
physical connectivity happens at the component link level. As Id, and label identifying virtual circuit, timeslot, etc. Resource
another example, consider the case where a PXC transparently allocation happens at the lowest level (labels), but physical
switches OC-192 lightpaths. If multiple interfaces are once again connectivity happens at the component link level. As another
grouped together into a single TE link, then link bundling [BUNDLE] example, consider the case where an optical switch (e.g., PXC)
is not required and only two levels of identification are required: transparently switches OC-192 lightpaths. If multiple interfaces
TE link Id and port Id. In this case, both resource allocation and are once again grouped together into a single TE link, then link
physical connectivity happen at the lowest level (i.e. port level). bundling [BUNDLE] is not required and only two levels of
identification are required: Link_Id and Port_Id. In this case,
both resource allocation and physical connectivity happen at the
lowest level (i.e. port level).
To ensure interworking between data links with different To ensure interworking between data links with different
multiplexing capabilities, LMP capable devices SHOULD allow sub- multiplexing capabilities, LMP capable devices SHOULD allow sub-
channels of a component link to be locally configured as (logical) channels of a component link to be locally configured as (logical)
data links. For example, if a Router with 4 OC-48 interfaces is data links. For example, if a Router with 4 OC-48 interfaces is
connected through a 4:1 MUX to an OXC with OC-192c interfaces, the connected through a 4:1 MUX to an OXC with OC-192c interfaces, the
OXC SHOULD be able to configure each OC-48 sub-channel as a data OXC SHOULD be able to configure each OC-48 sub-channel as a data
link. link.
LMP is designed to support aggregation of one or more data-bearing LMP is designed to support aggregation of one or more data links
links into a TE link (either ports into TE links, or component links into a TE link (either ports into TE links, or component links into
into TE links). The purpose of forming a TE link is to group/map the TE links). The purpose of forming a TE link is to group/map the
information about certain physical resources (and their properties) information about certain physical resources (and their properties)
into the information that is used by Constrained SPF for the purpose into the information that is used by Constrained SPF for the purpose
of path computation, and by GMPLS signaling. of path computation, and by GMPLS signaling.
1.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
The reader is assumed to be familiar with the terminology in [GMPLS-
SIG], [GMPLS-RTG], and [BUNDLE].
Bundled Link:
As defined in [BUNDLE], a bundled link is a TE link such that for
the purpose of GMPLS signaling a combination of <link identifier,
label> is not sufficient to unambiguously identify the
appropriate resources used by an LSP. A bundled link is composed
of two or more component links.
Control Channel:
A control channel is a pair of mutually reachable interfaces that
are used to enable communication between nodes for routing,
signaling, and link management.
Component Link:
As defined in [BUNDLE], a component link is a subset of resources
of a TE Link such that (a) the partition is minimal, and (b)
within each subset a label is sufficient to unambiguously
identify the appropriate resources used by an LSP.
Data Link:
A data link is a pair of interfaces that are used to transfer
user data. Note that in GMPLS, the control channel(s) between
two adjacent nodes are no longer required to use the same
physical medium as the data links between those nodes.
Link Property Correlation:
This is a procedure to correlate the local and remote properties
of a TE link.
Multiplex Capability:
The ability to multiplex/demultiplex a data stream into sub-rate
streams for switching purposes.
Port:
An interface that terminates a data link.
TE Link:
As defined in [GMPLS-RTG], a TE link is a logical construct that
represents a way to group/map the information about certain
physical resources (and their properties) that interconnect LSRs
into the information that is used by Constrained SPF for the
purpose of path computation, and by GMPLS signaling.
Transparent:
A device is called X-transparent if it forwards incoming signals
from input to output without examining or modifying the X aspect
of the signal. For example, a Frame Relay switch is network-
layer transparent; an all-optical switch is electrically
transparent.
2. LMP Overview 2. LMP Overview
The two core procedures of LMP are control channel management and The two core procedures of LMP are control channel management and
link property correlation. Control channel management is used to link property correlation. Control channel management is used to
establish and maintain control channels between adjacent nodes. This establish and maintain control channels between adjacent nodes.
is done using a Config message exchange and a fast keep-alive This is done using a Config message exchange and a fast keep-alive
mechanism between the nodes. The latter is required if lower-level mechanism between the nodes. The latter is required if lower-level
mechanisms are not available to detect control channel failures. mechanisms are not available to detect control channel failures.
Link property correlation is used to synchronize the TE link Link property correlation is used to synchronize the TE link
properties and verify the TE link configuration. properties and verify the TE link configuration.
LMP requires that a pair of nodes have at least one active bi- LMP requires that a pair of nodes have at least one active bi-
directional control channel between them. Each direction of the directional control channel between them. Each direction of the
control channel is identified by a control channel id (CCId), and control channel is identified by a Control Channel Id (CC_Id), and
the two directions are coupled together using the LMP Config message the two directions are coupled together using the LMP Config message
exchange. All LMP messages are IP encoded [except in some cases, the exchange. All LMP packets are run over UDP with an LMP port number
Test Message which may be limited by the transport mechanism for in- [except in some cases, the Test Message which may be limited by the
band messaging]. The link level encoding of the control channel is transport mechanism for in-band messaging]. The link level encoding
outside the scope of this document. of the control channel is outside the scope of this document.
An "LMP adjacency" is formed between two nodes when at least one bi- An "LMP adjacency" is formed between two nodes when at least one bi-
directional control channel is established between them. Multiple directional control channel is established between them. Multiple
control channels may be active simultaneously for each adjacency; control channels may be active simultaneously for each adjacency;
control channel parameters, however, MUST be individually negotiated control channel parameters, however, MUST be individually negotiated
for each control channel. If the LMP fast keep-alive is used over a for each control channel. If the LMP fast keep-alive is used over a
control channel, LMP Hello messages MUST be exchanged over the control channel, LMP Hello messages MUST be exchanged over the
control channel. Other LMP messages MAY be transmitted over any of control channel. Other LMP messages MAY be transmitted over any of
the active control channels between a pair of adjacent nodes. One or the active control channels between a pair of adjacent nodes. One
more active control channels may be grouped into a logical control or more active control channels may be grouped into a logical
channel for signaling, routing, and link property correlation control channel for signaling, routing, and link property
purposes. correlation purposes.
The link property correlation function of LMP is designed to The link property correlation function of LMP is designed to
aggregate multiple data links (ports or component links) into a TE aggregate multiple data links (ports or component links) into a TE
link and to synchronize the properties of the TE link. As part of link and to synchronize the properties of the TE link. As part of
the link property correlation function, a LinkSummary message the link property correlation function, a LinkSummary message
exchange is defined. The LinkSummary message includes the local and exchange is defined. The LinkSummary message includes the local and
remote TE Link Ids, a list of all data links that comprise the TE remote Link_Ids, a list of all data links that comprise the TE link,
link, and various link properties. A LinkSummaryAck or and various link properties. A LinkSummaryAck or LinkSummaryNack
LinkSummaryNack message MUST be sent in response to the receipt of a message MUST be sent in response to the receipt of a LinkSummary
LinkSummary message indicating agreement or disagreement on the link message indicating agreement or disagreement on the link properties.
properties.
LMP messages are transmitted reliably using Message Ids and LMP messages are transmitted reliably using Message_Ids and
retransmissions. Message Ids are carried in MESSAGE_ID objects. No retransmissions. Message_Ids are carried in MESSAGE_ID objects. No
more than one MESSAGE_ID object may be included in an LMP message. more than one MESSAGE_ID object may be included in an LMP message.
For control channel specific messages, the Message Id is within the For control channel specific messages, the Message_Id is within the
scope of the control channel over which the message is sent. For TE scope of the control channel over which the message is sent. For TE
link specific messages, the Message Id is within the scope of the link specific messages, the Message_Id is within the scope of the
LMP adjacency. The value of the Message Id is monotonically LMP adjacency. The value of the Message_Id is monotonically
increasing and only decreases when the value wraps. increasing and only decreases when the value wraps.
In this draft, two additional LMP procedures are defined: link In this document, two additional LMP procedures are defined: link
connectivity verification and fault management. These procedures are connectivity verification and fault management. These procedures
particularly useful when the control channels are physically diverse are particularly useful when the control channels are physically
from the data-bearing links. Link connectivity verification is used diverse from the data links. Link connectivity verification is used
for data plane discovery, Interface Id exchange (Interface Ids are for data plane discovery, Interface_Id exchange (Interface_Ids are
used in GMPLS signaling, either as Port labels or Component used in GMPLS signaling, either as port labels or component link
Interface Ids, depending on the configuration), and physical identifiers, depending on the configuration), and physical
connectivity verification. This is done by sending Test messages in- connectivity verification. This is done by sending Test messages
band over the data-bearing links and TestStatus messages back over over the data links and TestStatus messages back over the control
the control channel. Note that the Test message is the only LMP channel. Note that the Test message is the only LMP message that
message that must be transmitted over the data-bearing link. The must be transmitted over the data link. The ChannelStatus message
ChannelStatus message exchange is used between adjacent nodes for exchange is used between adjacent nodes for both the suppression of
both the suppression of downstream alarms and the localization of downstream alarms and the localization of faults for protection and
faults for protection and restoration. restoration.
For LMP link connectivity verification using a PXC, the Test message For LMP link connectivity verification, the Test message is
is generated and terminated by opaque test units that may be shared transmitted over the data links. For X-transparent devices, this
among multiple ports. Opaque test units are needed since the PXC requires examining and modifying the X aspect of the signal. The
ports are transparent. The LMP link connectivity verification LMP link connectivity verification procedure is coordinated using a
procedure is coordinated using a BeginVerify message exchange over a BeginVerify message exchange over a control channel. To support
control channel. To support various degrees of transparency (e.g., various aspects of transparency, a Verify Transport Mechanism is
examining overhead bytes, terminating the payload, etc.), and hence, included in the BeginVerify and BeginVerifyAck messages. Note that
different mechanisms to transport the Test messages, a Verify there is no requirement that all data links must lose their
Transport Mechanism is included in the BeginVerify and transparency simultaneously, but at a minimum, it must be possible
BeginVerifyAck messages. Note that there is no requirement that all to terminate them one at a time. There is also no requirement that
data-bearing links must be terminated simultaneously, but at a the control channel and TE link use the same physical medium;
minimum, it must be possible to terminate them one at a time. There however, the control channel MUST terminate on the same two nodes
is also no requirement that the control channel and TE link use the that the TE link spans. Since the BeginVerify message exchange
same physical medium; however, the control channel MUST terminate on coordinates the Test procedure, it also naturally coordinates the
the same two nodes that the TE link spans. Since the BeginVerify transition of the data links in and out of the transparent mode.
message exchange coordinates the Test procedure, it also naturally
coordinates the transition of the data links between opaque and
transparent mode.
The LMP fault management procedure is based on a ChannelStatus The LMP fault management procedure is based on a ChannelStatus
exchange using the following messages: ChannelStatus, message exchange using the following messages: ChannelStatus,
ChannelStatusAck, ChannelStatusRequest, and ChannelStatusResponse. ChannelStatusAck, ChannelStatusRequest, and ChannelStatusResponse.
The ChannelStatus message is sent unsolicitated and is used to The ChannelStatus message is sent unsolicited and is used to notify
notify an LMP neighbor about the status of one or more data channels an LMP neighbor about the status of one or more data channels of a
of a TE link. The ChannelStatusAck message is used to acknowledge TE link. The ChannelStatusAck message is used to acknowledge
receipt of the ChannelStatus message. The ChannelStatusRequest receipt of the ChannelStatus message. The ChannelStatusRequest
message is used to query an LMP neighbor for the status of one or message is used to query an LMP neighbor for the status of one or
more data channels of a TE Link. The ChannelStatusResponse message more data channels of a TE Link. The ChannelStatusResponse message
is used to acknowledge receipt of the ChannelStatusRequest message is used to acknowledge receipt of the ChannelStatusRequest message
and indicate the states of the queried data links. and indicate the states of the queried data links.
3. Control Channel Management 3. Control Channel Management
To initiate an LMP adjacency between two nodes, one or more bi- To initiate an LMP adjacency between two nodes, one or more bi-
directional control channels MUST be activated. The control channels directional control channels MUST be activated. The control
can be used to exchange control-plane information such as link channels can be used to exchange control-plane information such as
provisioning and fault management information (implemented using a link provisioning and fault management information (implemented
messaging protocol such as LMP, proposed in this draft), path using a messaging protocol such as LMP, proposed in this document),
management and label distribution information (implemented using a path management and label distribution information (implemented
signaling protocol such as RSVP-TE [RFC3209] or CR-LDP [RFC3219]), using a signaling protocol such as RSVP-TE [RFC3209]), and network
and network topology and state distribution information (implemented topology and state distribution information (implemented using
using traffic engineering extensions of protocols such as OSPF traffic engineering extensions of protocols such as OSPF [OSPF-TE]
[OSPF-TE] and IS-IS [ISIS-TE]). and IS-IS [ISIS-TE]).
For the purposes of LMP, the exact implementation of the control For the purposes of LMP, the exact implementation of the control
channel is not specified; it could be, for example, a separate channel is not specified; it could be, for example, a separate
wavelength or fiber, an Ethernet link, an IP tunnel through a wavelength or fiber, an Ethernet link, an IP tunnel through a
separate management network, or the overhead bytes of a data-bearing separate management network, or the overhead bytes of a data link.
link. Rather, a node-wide unique 32-bit non-zero integer control Rather, a node-wide unique 32-bit non-zero integer control channel
channel identifier (CCId) is assigned at each end of the control identifier (CC_Id) is assigned at each end of the control channel.
channel. This identifier comes from the same space as the unnumbered This identifier comes from the same space as the unnumbered
interface Id. Furthermore, LMP packets are run over UDP with an LMP interface Id. Furthermore, LMP packets are run over UDP with an LMP
port number. Thus, the link level encoding of the control channel is port number. Thus, the link level encoding of the control channel
not part of the LMP specification. is not part of the LMP specification.
To establish a control channel, the destination IP address on the To establish a control channel, the destination IP address on the
far end of the control channel must be known. This knowledge may be far end of the control channel must be known. This knowledge may be
manually configured or automatically discovered. Note that for in- manually configured or automatically discovered. Note that for in-
band signaling, a control channel could be explicitly configured on band signaling, a control channel could be explicitly configured on
a particular data-bearing link. In this case, the Config message a particular data link. In this case, the Config message exchange
exchange can be used to dynamically learn the IP address on the far can be used to dynamically learn the IP address on the far end of
end of the control channel. This is done by sending the Config the control channel. This is done by sending the Config message to
message to the Multicast address (224.0.0.1). The ConfigAck and the Multicast address (224.0.0.1). The ConfigAck and ConfigNack
ConfigNack messages MUST be sent to the source IP address found in messages MUST be sent to the source IP address found in the IP
the IP header of the received Config message. header of the received Config message.
Control channels exist independently of TE links and multiple Control channels exist independently of TE links and multiple
control channels may be active simultaneously between a pair of control channels may be active simultaneously between a pair of
nodes. Individual control channels can be realized in different nodes. Individual control channels can be realized in different
ways; one might be implemented in-fiber while another one may be ways; one might be implemented in-fiber while another one may be
implemented out-of-fiber. As such, control channel parameters MUST implemented out-of-fiber. As such, control channel parameters MUST
be negotiated over each individual control channel, and LMP Hello be negotiated over each individual control channel, and LMP Hello
packets MUST be exchanged over each control channel to maintain LMP packets MUST be exchanged over each control channel to maintain LMP
connectivity if other mechanisms are not available. Since control connectivity if other mechanisms are not available. Since control
channels are electrically terminated at each node, it may be channels are electrically terminated at each node, it may be
possible to detect control channel failures using lower layers possible to detect control channel failures using lower layers
(e.g., SONET/SDH). (e.g., SONET/SDH).
There are four LMP messages that are used to manage individual There are four LMP messages that are used to manage individual
control channels. They are the Config, ConfigAck, ConfigNack, and control channels. They are the Config, ConfigAck, ConfigNack, and
Hello messages. These messages MUST be transmitted on the channel to Hello messages. These messages MUST be transmitted on the channel
which they refer. All other LMP messages may be transmitted over any to which they refer. All other LMP messages may be transmitted over
of the active control channels between a pair of LMP adjacent nodes. any of the active control channels between a pair of LMP adjacent
nodes.
In order to maintain an LMP adjacency, it is necessary to have at In order to maintain an LMP adjacency, it is necessary to have at
least one active control channel between a pair of adjacent nodes least one active control channel between a pair of adjacent nodes
(recall that multiple control channels can be active simultaneously (recall that multiple control channels can be active simultaneously
between a pair of nodes). In the event of a control channel failure, between a pair of nodes). In the event of a control channel
alternate active control channels can be used and it may be possible failure, alternate active control channels can be used and it may be
to activate additional control channels as described below. possible to activate additional control channels as described below.
3.1. Parameter Negotiation 3.1. Parameter Negotiation
Control channel activation begins with a parameter negotiation Control channel activation begins with a parameter negotiation
exchange using Config, ConfigAck, and ConfigNack messages. The exchange using Config, ConfigAck, and ConfigNack messages. The
contents of these messages are built using LMP objects, which can be contents of these messages are built using LMP objects, which can be
either negotiable or non-negotiable (identified by the N bit in the either negotiable or non-negotiable (identified by the N bit in the
object header). Negotiable objects can be used to let LMP peers object header). Negotiable objects can be used to let LMP peers
agree on certain values. Non-negotiable objects are used for the agree on certain values. Non-negotiable objects are used for the
announcement of specific values that do not need, or do not allow, announcement of specific values that do not need, or do not allow,
negotiation. negotiation.
To activate a control channel, a Config message MUST be transmitted To activate a control channel, a Config message MUST be transmitted
to the remote node, and in response, a ConfigAck message MUST be to the remote node, and in response, a ConfigAck message MUST be
received at the local node. The Config message contains the Local received at the local node. The Config message contains the Local
Control Channel ID (CC_ID), the sender∆s Node ID, a MessageId for Control Channel Id (CC_Id), the sender's Node_Id, a Message_Id for
reliable messaging, and a CONFIG object. It is possible that both reliable messaging, and a CONFIG object. It is possible that both
the local and remote nodes initiate the configuration procedure at the local and remote nodes initiate the configuration procedure at
the same time. To avoid ambiguities, the node with the higher Node the same time. To avoid ambiguities, the node with the higher
Id wins the contention; the node with the lower Node Id MUST stop Node_Id wins the contention; the node with the lower Node_Id MUST
transmitting the Config message and respond to the Config message it stop transmitting the Config message and respond to the Config
received. message it received.
The ConfigAck message is used to acknowledge receipt of the Config The ConfigAck message is used to acknowledge receipt of the Config
message and express agreement on ALL of the configured parameters message and express agreement on ALL of the configured parameters
(both negotiable and non-negotiable). (both negotiable and non-negotiable).
The ConfigNack message is used to acknowledge receipt of the Config The ConfigNack message is used to acknowledge receipt of the Config
message, indicate which (if any) non-negotiable CONFIG objects are message, indicate which (if any) non-negotiable CONFIG objects are
unacceptable, and propose alternate values for the negotiable unacceptable, and propose alternate values for the negotiable
parameters. parameters.
skipping to change at page 9, line 37 skipping to change at page 12, line 9
message using these values for those parameters. message using these values for those parameters.
If a node receives a ConfigNack message with unacceptable alternate If a node receives a ConfigNack message with unacceptable alternate
values, the node MAY continue to retransmit Config messages. Note values, the node MAY continue to retransmit Config messages. Note
that the problem may be solved by an operator changing parameters. that the problem may be solved by an operator changing parameters.
In the case where multiple control channels use the same physical In the case where multiple control channels use the same physical
interface, the parameter negotiation exchange is performed for each interface, the parameter negotiation exchange is performed for each
control channel. The various LMP parameter negotiation messages are control channel. The various LMP parameter negotiation messages are
associated with their corresponding control channels by their node- associated with their corresponding control channels by their node-
wide unique identifiers (CCIds). wide unique identifiers (CC_Ids).
3.2. Hello Protocol 3.2. Hello Protocol
Once a control channel is activated between two adjacent nodes, the Once a control channel is activated between two adjacent nodes, the
LMP Hello protocol can be used to maintain control channel LMP Hello protocol can be used to maintain control channel
connectivity between the nodes and to detect control channel connectivity between the nodes and to detect control channel
failures. The LMP Hello protocol is intended to be a lightweight failures. The LMP Hello protocol is intended to be a lightweight
keep-alive mechanism that will react to control channel failures keep-alive mechanism that will react to control channel failures
rapidly so that IGP Hellos are not lost and the associated link- rapidly so that IGP Hellos are not lost and the associated link-
state adjacencies are not removed unnecessarily. state adjacencies are not removed unnecessarily.
skipping to change at page 10, line 8 skipping to change at page 12, line 32
Before sending Hello messages, the HelloInterval and Before sending Hello messages, the HelloInterval and
HelloDeadInterval parameters MUST be agreed upon by the local and HelloDeadInterval parameters MUST be agreed upon by the local and
remote nodes. These parameters are exchanged in the Config message. remote nodes. These parameters are exchanged in the Config message.
The HelloInterval indicates how frequently LMP Hello messages will The HelloInterval indicates how frequently LMP Hello messages will
be sent, and is measured in milliseconds (ms). For example, if the be sent, and is measured in milliseconds (ms). For example, if the
value were 150, then the transmitting node would send the Hello value were 150, then the transmitting node would send the Hello
message at least every 150ms. The HelloDeadInterval indicates how message at least every 150ms. The HelloDeadInterval indicates how
long a device should wait to receive a Hello message before long a device should wait to receive a Hello message before
declaring a control channel dead, and is measured in milliseconds declaring a control channel dead, and is measured in milliseconds
(ms). The HelloDeadInterval MUST be greater than the HelloInterval, (ms).
and SHOULD be at least 3 times the value of HelloInterval.
The HelloDeadInterval MUST be greater than the HelloInterval, and
SHOULD be at least 3 times the value of HelloInterval. If the fast
keep-alive mechanism of LMP is not used, the HelloInterval and
HelloDeadInterval parameters MUST be set to zero.
Suggested default values for the HelloInterval is 5 ms and for the Suggested default values for the HelloInterval is 5 ms and for the
HelloDeadInterval is 18 ms. HelloDeadInterval is 18 ms.
If the fast keep-alive mechanism of LMP is not used, the
HelloInterval and HelloDeadInterval parameters MUST be set to zero.
When a node has either sent or received a ConfigAck message, it may When a node has either sent or received a ConfigAck message, it may
begin sending Hello messages. Once it has sent a Hello message and begin sending Hello messages. Once it has sent a Hello message and
received a valid Hello message (i.e., with expected sequence received a valid Hello message (i.e., with expected sequence
numbers; see Section 3.2.2), the control channel moves to the UP numbers; see Section 3.2.2), the control channel moves to the up
state. (It is also possible to move to the UP state without sending state. (It is also possible to move to the up state without sending
Hellos if other methods are used to indicate bi-directional control- Hellos if other methods are used to indicate bi-directional control-
channel connectivity.) If, however, a node receives a ConfigNack channel connectivity.) If, however, a node receives a ConfigNack
message instead of a ConfigAck message, the node MUST not send Hello message instead of a ConfigAck message, the node MUST not send Hello
messages and the control channel SHOULD NOT move to the UP state. messages and the control channel SHOULD NOT move to the up state.
See Section 12.1 for the complete control channel FSM. See Section 11.1 for the complete control channel FSM.
3.2.2. Fast Keep-alive 3.2.2. Fast Keep-alive
Each Hello message contains two sequence numbers: the first sequence Each Hello message contains two sequence numbers: the first sequence
number (TxSeqNum) is the sequence number for the Hello message being number (TxSeqNum) is the sequence number for the Hello message being
sent and the second sequence number (RcvSeqNum) is the sequence sent and the second sequence number (RcvSeqNum) is the sequence
number of the last Hello message received from the adjacent node number of the last Hello message received from the adjacent node
over this control channel. Each node increments its sequence number over this control channel.
when it sees its current sequence number reflected in Hellos
received from its peer. The sequence numbers start at 1 and wrap There are two special sequence numbers. TxSeqNum MUST NOT ever be
around back to 2; 0 is used in the RcvSeqNum to indicate that a 0. TxSeqNum = 1 is used to indicate that the sender has just
Hello has not yet been seen. started or has restarted and has no recollection of the last
TxSeqNum that was sent. Thus, the first Hello sent has a TxSeqNum
of 1 and an RxSeqNum of 0. When TxSeqNum reaches 2^32 -1, the next
sequence number used is 2, not 0 or 1, as these have special
meanings.
Under normal operation, the difference between the RcvSeqNum in a Under normal operation, the difference between the RcvSeqNum in a
Hello message that is received and the local TxSeqNum that is Hello message that is received and the local TxSeqNum that is
generated will be at most 1. This difference can be more than one generated will be at most 1. This difference can be more than one
only when a control channel restarts or when the values wrap. only when a control channel restarts or when the values wrap.
Note that the 32-bit sequence numbers MAY wrap. The following Since the 32-bit sequence numbers may wrap, the following expression
expression may be used to test if a newly received TxSeqNum value is may be used to test if a newly received TxSeqNum value is less than
less than a previously received value: a previously received value:
If ((int) old_id Ż (int) new_id > 0) { If ((int) old_id - (int) new_id > 0) {
New value is less than old value; New value is less than old value;
} }
Having sequence numbers in the Hello messages allows each node to Having sequence numbers in the Hello messages allows each node to
verify that its peer is receiving its Hello messages. By including verify that its peer is receiving its Hello messages. By including
the RcvSeqNum in Hello packets, the local node will know which Hello the RcvSeqNum in Hello packets, the local node will know which Hello
packets the remote node has received. packets the remote node has received.
The following example illustrates how the sequence numbers operate. The following example illustrates how the sequence numbers operate.
Note that only the operation at one node is shown, and alternative Note that only the operation at one node is shown, and alternative
skipping to change at page 11, line 22 skipping to change at page 13, line 54
messages to Node B with {TxSeqNum=1;RcvSeqNum=0}. messages to Node B with {TxSeqNum=1;RcvSeqNum=0}.
2) When Node A receives a Hello from Node B with 2) When Node A receives a Hello from Node B with
{TxSeqNum=1;RcvSeqNum=1}, it sends Hellos to Node B with {TxSeqNum=1;RcvSeqNum=1}, it sends Hellos to Node B with
{TxSeqNum=2;RcvSeqNum=1}. {TxSeqNum=2;RcvSeqNum=1}.
3) When Node A receives a Hello from Node B with 3) When Node A receives a Hello from Node B with
{TxSeqNum=2;RcvSeqNum=2}, it sends Hellos to Node B with {TxSeqNum=2;RcvSeqNum=2}, it sends Hellos to Node B with
{TxSeqNum=3;RcvSeqNum=2}. {TxSeqNum=3;RcvSeqNum=2}.
3.2.3. Control Channel Down 3.2.3. Control Channel Down
To allow bringing a control channel DOWN gracefully for To allow bringing a control channel down gracefully for
administration purposes, a ControlChannelDown flag is available in administration purposes, a ControlChannelDown flag is available in
the Common Header of LMP packets. When data links are still in use the Common Header of LMP packets. When data links are still in use
between a pair of nodes, a control channel SHOULD only be taken down between a pair of nodes, a control channel SHOULD only be taken down
administratively when there are other active control channels that administratively when there are other active control channels that
can be used to manage the data links. can be used to manage the data links.
When bringing a control channel DOWN administratively, a node MUST When bringing a control channel down administratively, a node MUST
set the ControlChannelDown flag in all LMP messages sent over the set the ControlChannelDown flag in all LMP messages sent over the
control channel. The node that initiated the control channel DOWN control channel. The node that initiated the control channel down
procedure may stop sending Hello messages after HelloDeadInterval procedure may stop sending Hello messages after HelloDeadInterval
seconds have passed, or if it receives an LMP message over the same seconds have passed, or if it receives an LMP message over the same
control channel with the ControlChannelDown flag set. control channel with the ControlChannelDown flag set.
When a node receives an LMP packet with the ControlChannelDown flag When a node receives an LMP packet with the ControlChannelDown flag
set, it SHOULD send a Hello message with the ControlChannelDown flag set, it SHOULD send a Hello message with the ControlChannelDown flag
set and move the control channel to the Down state. set and move the control channel to the down state.
3.2.4. Degraded State 3.2.4. Degraded State
A consequence of allowing the control channels to be physically A consequence of allowing the control channels to be physically
diverse from the associated data links is that there may not be any diverse from the associated data links is that there may not be any
active control channels available while the data links are still in active control channels available while the data links are still in
use. For many applications, it is unacceptable to tear down a link use. For many applications, it is unacceptable to tear down a link
that is carrying user traffic simply because the control channel is that is carrying user traffic simply because the control channel is
no longer available; however, the traffic that is using the data no longer available; however, the traffic that is using the data
links may no longer be guaranteed the same level of service. Hence links may no longer be guaranteed the same level of service. Hence
skipping to change at page 12, line 4 skipping to change at page 14, line 35
that is carrying user traffic simply because the control channel is that is carrying user traffic simply because the control channel is
no longer available; however, the traffic that is using the data no longer available; however, the traffic that is using the data
links may no longer be guaranteed the same level of service. Hence links may no longer be guaranteed the same level of service. Hence
the TE link is in a Degraded state. the TE link is in a Degraded state.
When a TE link is in the Degraded state, routing and signaling When a TE link is in the Degraded state, routing and signaling
SHOULD be notified so that new connections are not accepted and the SHOULD be notified so that new connections are not accepted and the
TE link is advertised with no unreserved resources. TE link is advertised with no unreserved resources.
4. Link Property Correlation 4. Link Property Correlation
As part of LMP, a link property correlation exchange is defined for As part of LMP, a link property correlation exchange is defined for
TE links using the LinkSummary, LinkSummaryAck, and LinkSummaryNack TE links using the LinkSummary, LinkSummaryAck, and LinkSummaryNack
messages. The contents of these messages are built using LMP messages. The contents of these messages are built using LMP
objects, which can be either negotiable or non-negotiable objects, which can be either negotiable or non-negotiable
(identified by the N flag in the object header). Negotiable objects (identified by the N flag in the object header). Negotiable objects
can be used to let both sides agree on certain link parameters. Non- can be used to let both sides agree on certain link parameters.
negotiable objects are used for announcement of specific values that Non-negotiable objects are used for announcement of specific values
do not need, or do not allow, negotiation. that do not need, or do not allow, negotiation.
Each TE link has an identifier (Link_Id) that is assigned at each Each TE link has an identifier (Link_Id) that is assigned at each
end of the link. These identifiers MUST be the same type (i.e, IPv4, end of the link. These identifiers MUST be the same type (i.e,
IPv6, unnumbered) at both ends. If a LinkSummary message is received IPv4, IPv6, unnumbered) at both ends. If a LinkSummary message is
with different local and remote TE link types, then a received with different local and remote TE link types, then a
LinkSummaryNack message MUST be sent with Error Code "Bad TE Link LinkSummaryNack message MUST be sent with Error Code "Bad TE Link
Object". Similarly, each data link is assigned an identifier Object". Similarly, each data link is assigned an identifier
(Interface_Id) at each end. These identifiers MUST also be the same (Interface_Id) at each end. These identifiers MUST also be the same
type at both ends. If a LinkSummary message is received with type at both ends. If a LinkSummary message is received with
different local and remote Interface Id types then a LinkSummaryNack different local and remote Interface_Id types then a LinkSummaryNack
message MUST be sent with Error Code "Bad Data Link Object". message MUST be sent with Error Code "Bad Data Link Object".
Link property correlation SHOULD be done before the link is brought Link property correlation SHOULD be done before the link is brought
up and MAY be done at any time a link is UP and not in the up and MAY be done at any time a link is up and not in the
Verification process. Verification process.
The LinkSummary message is used to verify for consistency the TE and The LinkSummary message is used to verify for consistency the TE and
data bearing link information on both sides. Link Summary messages data link information on both sides. Link Summary messages are also
are also used to aggregate multiple data links (either ports or used to aggregate multiple data links (either ports or component
component links) into a TE link; exchange, correlate (to determine links) into a TE link; exchange, correlate (to determine
inconsistencies), or change TE link parameters; and exchange, inconsistencies), or change TE link parameters; and exchange,
correlate (to determine inconsistencies), or change Interface Ids correlate (to determine inconsistencies), or change Interface_Ids
(used either Port Ids or Component Interface Ids). (used either Port_Ids or component link identifiers).
The LinkSummary message includes a TE_LINK object followed by one or The LinkSummary message includes a TE_LINK object followed by one or
more DATA_LINK objects. The TE_LINK object identifies the TE link's more DATA_LINK objects. The TE_LINK object identifies the TE link's
local and remote Link Id and indicates support for fault management local and remote Link_Id and indicates support for fault management
and link verification procedures for that TE link. The DATA_LINK and link verification procedures for that TE link. The DATA_LINK
objects are used to characterize the data links that comprise the TE objects are used to characterize the data links that comprise the TE
link. These objects include the local and remote Interface Ids, and link. These objects include the local and remote Interface_Ids, and
may include one or more sub-objects further describing the may include one or more sub-objects further describing the
properties of the data links. properties of the data links.
If the LinkSummary message is received from a remote node and the If the LinkSummary message is received from a remote node and the
Interface Id mappings match those that are stored locally, then the Interface_Id mappings match those that are stored locally, then the
two nodes have agreement on the Verification procedure (see Section two nodes have agreement on the Verification procedure (see Section
5) and data link configuration. If the verification procedure is not 5) and data link identification configuration. If the verification
used, the LinkSummary message can be used to verify agreement on procedure is not used, the LinkSummary message can be used to verify
manual configuration. agreement on manual configuration.
The LinkSummaryAck message is used to signal agreement on the The LinkSummaryAck message is used to signal agreement on the
Interface Id mappings and link property definitions. Otherwise, a Interface_Id mappings and link property definitions. Otherwise, a
LinkSummaryNack message MUST be transmitted, indicating which LinkSummaryNack message MUST be transmitted, indicating which
Interface mappings are not correct and/or which link properties are Interface mappings are not correct and/or which link properties are
not accepted. If a LinkSummaryNack message indicates that the not accepted. If a LinkSummaryNack message indicates that the
Interface Id mappings are not correct and the link verification Interface_Id mappings are not correct and the link verification
procedure is enabled, the link verification process SHOULD be procedure is enabled, the link verification process SHOULD be
repeated for all mismatched free data links; if an allocated data repeated for all mismatched free data links; if an allocated data
link has a mapping mismatch, it SHOULD be flagged and verified when link has a mapping mismatch, it SHOULD be flagged and verified when
it becomes free. If a LinkSummaryNack message includes negotiable it becomes free. If a LinkSummaryNack message includes negotiable
parameters, then acceptable values for those parameters MUST be parameters, then acceptable values for those parameters MUST be
included. If a LinkSummaryNack message is received and includes included. If a LinkSummaryNack message is received and includes
negotiable parameters, then the initiator of the LinkSummary message negotiable parameters, then the initiator of the LinkSummary message
SHOULD send a new LinkSummary message. The new LinkSummary message SHOULD send a new LinkSummary message. The new LinkSummary message
SHOULD include new values for the negotiable parameters. These SHOULD include new values for the negotiable parameters. These
values SHOULD take into account the acceptable values received in values SHOULD take into account the acceptable values received in
the LinkSummaryNack message. the LinkSummaryNack message.
It is possible that the LinkSummary message could grow quite large It is possible that the LinkSummary message could grow quite large
due to the number of DATA LINK objects. Since the LinkSummary due to the number of DATA LINK objects. An LMP implementation
message is IP encoded, normal IP fragmentation should be used if the SHOULD be able to fragment when transmitting LMP messages, and MUST
resulting PDU exceeds the MTU. be able to re-assemble IP fragments when receiving LMP messages.
5. Verifying Link Connectivity 5. Verifying Link Connectivity
In this section, an optional procedure is described that may be used In this section, an optional procedure is described that may be used
to verify the physical connectivity of the data-bearing links and to verify the physical connectivity of the data links and
dynamically learn (i.e., discover) the TE link and Interface ID dynamically learn (i.e., discover) the TE link and Interface_Id
associations. The procedure SHOULD be done when establishing a TE associations. The procedure SHOULD be done when establishing a TE
link, and subsequently, on a periodic basis for all unallocated link, and subsequently, on a periodic basis for all unallocated
(free) data links of the TE link. (free) data links of the TE link.
Support for this procedure is indicated by setting the "Link Support for this procedure is indicated by setting the "Link
Verification Supported" flag in the TE_LINK object of the Verification Supported" flag in the TE_LINK object of the
LinkSummary message. LinkSummary message.
If a BeginVerify message is received and link verification is not If a BeginVerify message is received and link verification is not
supported for the TE link, then a BeginVerifyNack message MUST be supported for the TE link, then a BeginVerifyNack message MUST be
transmitted with Error Code indicating "Link Verification Procedure transmitted with Error Code indicating, "Link Verification Procedure
not supported for this TE Link." not supported for this TE Link."
A unique characteristic of all-optical switches is that the data- A unique characteristic of transparent devices is that the data is
bearing links are transparent when allocated to user traffic. This not modified or examined in normal operation. This characteristic
characteristic poses a challenge for validating the connectivity of poses a challenge for validating the connectivity of the data links
the data links. For example, shining unmodulated light through a and establish the label mappings. Therefore, to ensure proper
link may not result in received light at the next switch because
there may be terminating (or opaque) elements, such as DWDM
equipment, between the PXCs. Therefore, to ensure proper
verification of data link connectivity, it is required that until verification of data link connectivity, it is required that until
the links are allocated for user traffic, they must be opaque. To the data links are allocated for user traffic, they must be opaque
support various degrees of opaqueness (e.g., examining overhead (i.e., lose their transparency). To support various degrees of
bytes, terminating the payload, etc.), and hence different opaqueness (e.g., examining overhead bytes, terminating the IP
mechanisms to transport the Test messages, a Verify Transport payload, etc.), and hence different mechanisms to transport the Test
Mechanism field is included in the BeginVerify and BeginVerifyAck messages, a Verify Transport Mechanism field is included in the
messages. BeginVerify and BeginVerifyAck messages.
There is no requirement that all data links be terminated There is no requirement that all data links be terminated
simultaneously, but at a minimum, the data links MUST be able to be simultaneously, but at a minimum, the data links MUST be able to be
terminated one at a time. Furthermore, for the link verification terminated one at a time. Furthermore, for the link verification
procedure it is assumed that the nodal architecture is designed so procedure it is assumed that the nodal architecture is designed so
that messages can be sent and received over any data link. Note that that messages can be sent and received over any data link. Note
this requirement is trivial for DXCs (and OEO devices in general) that this requirement is trivial for opaque devices since each data
since each data link is terminated and processed electronically link is electrically terminated and processed before being forwarded
before being forwarded to the next OEO device, but that in PXCs (and to the next opaque device, but that in transparent devices this is
transparent devices in general) this is an additional requirement. an additional requirement.
To interconnect two nodes, a TE link is defined between them, and at To interconnect two nodes, a TE link is defined between them, and at
a minimum, there MUST be at least one active control channel between a minimum, there MUST be at least one active control channel between
the nodes. For link verification, a TE link MUST include at least the nodes. For link verification, a TE link MUST include at least
one data link. one data link.
Once a control channel has been established between the two nodes, Once a control channel has been established between the two nodes,
data link connectivity can be verified by exchanging Test messages data link connectivity can be verified by exchanging Test messages
over each of the data links specified in the TE link. It should be over each of the data links specified in the TE link. It should be
noted that all LMP messages except the Test message are exchanged noted that all LMP messages except the Test message are exchanged
over the control channels and that Hello messages continue to be over the control channels and that Hello messages continue to be
exchanged over each control channel during the data link exchanged over each control channel during the data link
verification process. The Test message is sent over the data link verification process. The Test message is sent over the data link
that is being verified. Data links are tested in the transmit that is being verified. Data links are tested in the transmit
direction as they are unidirectional, and therefore, it may be direction as they are unidirectional, and therefore, it may be
possible for both nodes to (independently) exchange the Test possible for both nodes to (independently) exchange the Test
messages simultaneously. messages simultaneously.
To initiate the link verification procedure, the local node MUST To initiate the link verification procedure, the local node MUST
send a BeginVerify message over a control channel. To limit the send a BeginVerify message over a control channel. To limit the
scope of Link Verification to a particular TE Link, the scope of Link Verification to a particular TE Link, the local
LOCAL_LINK_ID MUST be non-zero. If this field is zero, the data Link_Id MUST be non-zero. If this field is zero, the data links can
links can span multiple TE links and/or they may comprise a TE link span multiple TE links and/or they may comprise a TE link that is
that is yet to be configured. For the case where the LOCAL_LINK_ID yet to be configured. For the case where the local Link_Id field is
field is zero, the "Verify all Links" flag of the BEGIN_VERIFY zero, the "Verify all Links" flag of the BEGIN_VERIFY object is used
object is used to distinguish between data links that span multiple to distinguish between data links that span multiple TE links and
TE links and those that have not yet been assigned to a TE link. those that have not yet been assigned to a TE link. Specifically,
Specifically, verification of data links that span multiple TE links verification of data links that span multiple TE links is indicated
is indicated by setting the LOCAL_LINK_ID field to zero and setting by setting the local Link_Id field to zero and setting the "Verify
the "Verify all Links" flag. Verification of data links that have all Links" flag. Verification of data links that have not yet been
not yet been assigned to a TE link is indicated by setting the assigned to a TE link is indicated by setting the local Link_Id
LOCAL_LINK_ID field to zero and clearing the "Verify all Links" field to zero and clearing the "Verify all Links" flag.
flag.
The BeginVerify message also contains the number of data links that The BeginVerify message also contains the number of data links that
are to be verified; the interval (called VerifyInterval) at which are to be verified; the interval (called VerifyInterval) at which
the Test messages will be sent; the encoding scheme and transport the Test messages will be sent; the encoding scheme and transport
mechanisms that are supported; the data rate for Test messages; and, mechanisms that are supported; the data rate for Test messages; and,
when the data links correspond to fibers, the wavelength identifier when the data links correspond to fibers, the wavelength identifier
over which the Test messages will be transmitted. over which the Test messages will be transmitted.
If the remote node receives a BeginVerify message and it is ready to If the remote node receives a BeginVerify message and it is ready to
process Test messages, it MUST send a BeginVerifyAck message back to process Test messages, it MUST send a BeginVerifyAck message back to
the local node specifying the desired transport mechanism for the the local node specifying the desired transport mechanism for the
TEST messages. The remote node includes a 32-bit node unique TEST messages. The remote node includes a 32-bit node unique
VerifyId in the BeginVerifyAck message. The VerifyId is then used in Verify_Id in the BeginVerifyAck message. The Verify_Id is then used
all corresponding verification messages to differentiate them from in all corresponding verification messages to differentiate them
different LMP peers and/or parallel Test procedures. When the local from different LMP peers and/or parallel Test procedures. When the
node receives a BeginVerifyAck message from the remote node, it may local node receives a BeginVerifyAck message from the remote node,
begin testing the data links by transmitting periodic Test messages it may begin testing the data links by transmitting periodic Test
over each data link. The Test message includes the VerifyId and the messages over each data link. The Test message includes the
local Interface Id for the associated data link. The remote node Verify_Id and the local Interface_Id for the associated data link.
MUST send either a TestStatusSuccess or a TestStatusFailure message The remote node MUST send either a TestStatusSuccess or a
in response for each data link. A TestStatusAck message MUST be sent TestStatusFailure message in response for each data link. A
to confirm receipt of the TestStatusSuccess and TestStatusFailure TestStatusAck message MUST be sent to confirm receipt of the
messages. TestStatusSuccess and TestStatusFailure messages.
It is also permissible for the sender to terminate the Test It is also permissible for the sender to terminate the Test
procedure anytime after sending the BeginVerify message. An procedure anytime after sending the BeginVerify message. An
EndVerify message SHOULD be sent for this purpose. EndVerify message SHOULD be sent for this purpose.
Message correlation is done using message identifiers and the Verify Message correlation is done using message identifiers and the
Id; this enables verification of data links, belonging to different Verify_Id; this enables verification of data links, belonging to
link bundles or LMP sessions, in parallel. different link bundles or LMP sessions, in parallel.
When the Test message is received, the received Interface Id (used When the Test message is received, the received Interface_Id (used
in GMPLS as either a Port/Wavelength label or Component Interface in GMPLS as either a Port label or component link identifier
Identifier depending on the configuration) is recorded and mapped to depending on the configuration) is recorded and mapped to the local
the local Interface Id for that data link, and a TestStatusSuccess Interface_Id for that data link, and a TestStatusSuccess message
message MUST be sent. The TestStatusSuccess message includes the MUST be sent. The TestStatusSuccess message includes the local
local Interface Id and the remote Interface Id (received in the Test Interface_Id along with the Interface_Id and Verify_Id received in
message), along with the VerifyId received in the Test message. The the Test message. The receipt of a TestStatusSuccess message
receipt of a TestStatusSuccess message indicates that the Test indicates that the Test message was detected at the remote node and
message was detected at the remote node and the physical the physical connectivity of the data link has been verified. When
connectivity of the data link has been verified. When the the TestStatusSuccess message is received, the local node SHOULD
TestStatusSuccess message is received, the local node SHOULD mark mark the data link as up and send a TestStatusAck message to the
the data link as UP and send a TestStatusAck message to the remote remote node. If, however, the Test message is not detected at the
node. If, however, the Test message is not detected at the remote remote node within an observation period (specified by the
node within an observation period (specified by the VerifyDeadInterval), the remote node MUST send a TestStatusFailure
VerifyDeadInterval), the remote node will send a TestStatusFailure
message over the control channel indicating that the verification of message over the control channel indicating that the verification of
the physical connectivity of the data link has failed. When the the physical connectivity of the data link has failed. When the
local node receives a TestStatusFailure message, it SHOULD mark the local node receives a TestStatusFailure message, it SHOULD mark the
data link as FAILED and send a TestStatusAck message to the remote data link as FAILED and send a TestStatusAck message to the remote
node. When all the data links on the list have been tested, the node. When all the data links on the list have been tested, the
local node SHOULD send an EndVerify message to indicate that testing local node SHOULD send an EndVerify message to indicate that testing
is complete on this link. is complete on this link.
If the local/remote data link mappings are known, then the link If the local/remote data link mappings are known, then the link
verification procedure can be optimized by testing the data links in verification procedure can be optimized by testing the data links in
a defined order known to both nodes. The suggested criteria for this a defined order known to both nodes. The suggested criterion for
ordering is in increasing value of the Remote_Interface_ID. this ordering is in increasing value of the remote Interface_Id.
Both the local and remote nodes SHOULD maintain the complete list of Both the local and remote nodes SHOULD maintain the complete list of
Interface Id mappings for correlation purposes. Interface_Id mappings for correlation purposes.
5.1. Example of Link Connectivity Verification 5.1. Example of Link Connectivity Verification
Figure 1 shows an example of the link verification scenario that is Figure 1 shows an example of the link verification scenario that is
executed when a link between Node A and Node B is added. In this executed when a link between Node A and Node B is added. In this
example, the TE link consists of three free ports (each transmitted example, the TE link consists of three free ports (each transmitted
along a separate fiber) and is associated with a bi-directional along a separate fiber) and is associated with a bi-directional
control channel (indicated by a "c"). The verification process is as control channel (indicated by a "c"). The verification process is
follows: as follows:
o A sends a BeginVerify message over the control channel to B o A sends a BeginVerify message over the control channel to B
indicating it will begin verifying the ports that form the TE indicating it will begin verifying the ports that form the TE
link. The LOCAL_LINK_ID object carried in the BeginVerify link. The LOCAL_LINK_ID object carried in the BeginVerify
message carries the identifier (IP address or interface index) message carries the identifier (IP address or interface index)
that A assigns to the link. that A assigns to the link.
o Upon receipt of the BeginVerify message, B creates a VerifyId o Upon receipt of the BeginVerify message, B creates a Verify_Id
and binds it to the TE Link from A. This binding is used later and binds it to the TE Link from A. This binding is used later
when B receives the Test messages from A, and these messages when B receives the Test messages from A, and these messages
carry the VerifyId. B discovers the identifier (IP address or carry the Verify_Id. B discovers the identifier (IP address or
interface index) that A assigns to the TE link by examining the interface index) that A assigns to the TE link by examining the
LOCAL_LINK_ID object carried in the received BeginVerify LOCAL_LINK_ID object carried in the received BeginVerify
message. (If the data ports are not yet assigned to the TE message. (If the data ports are not yet assigned to the TE
Link, the binding is limited to the Node Id of A.) In response Link, the binding is limited to the Node_Id of A.) In response
to the BeginVerify message, B sends to A the BeginVerifyAck to the BeginVerify message, B sends to A the BeginVerifyAck
message. The LOCAL_LINK_ID object carried in the BeginVerifyAck message. The LOCAL_LINK_ID object carried in the
message is used to carry the identifier (IP address or BeginVerifyAck message is used to carry the identifier (IP
interface index) that B assigns to the TE link. The address or interface index) that B assigns to the TE link. The
REMOTE_LINK_ID object carried in the BeginVerifyAck message is REMOTE_LINK_ID object carried in the BeginVerifyAck message is
used to bind the TE link Ids assigned by both A and B. The used to bind the Link_Ids assigned by both A and B. The
VerifyId is returned to A in the BeginVerifyAck message over Verify_Id is returned to A in the BeginVerifyAck message over
the control channel. the control channel.
o When A receives the BeginVerifyAck message, it begins o When A receives the BeginVerifyAck message, it begins
transmitting periodic Test messages over the first port transmitting periodic Test messages over the first port
(Interface Id=1). The Test message includes the Interface Id (Interface Id=1). The Test message includes the Interface_Id
for the port and the VerifyId that was assigned by B. for the port and the Verify_Id that was assigned by B.
o When B receives the Test messages, it maps the received o When B receives the Test messages, it maps the received
Interface Id to its own local Interface Id = 10 and transmits a Interface_Id to its own local Interface_Id = 10 and transmits a
TestStatusSuccess message over the control channel back to PXC TestStatusSuccess message over the control channel back to Node
A. The TestStatusSuccess message includes both the local and A. The TestStatusSuccess message includes both the local and
received Interface Ids for the port as well as the VerifyId. received Interface_Ids for the port as well as the Verify_Id.
The VerifyId is used to determine the local/remote TE link The Verify_Id is used to determine the local/remote TE link
identifiers (IP addresses or interface indices) for which the identifiers (IP addresses or interface indices) for which the
data links belong. data links belong.
o A will send a TestStatusAck message over the control channel o A will send a TestStatusAck message over the control channel
back to B indicating it received the TestStatusSuccess message. back to B indicating it received the TestStatusSuccess message.
o The process is repeated until all of the ports are verified. o The process is repeated until all of the ports are verified.
o At this point, A will send an EndVerify message over the o At this point, A will send an EndVerify message over the
control channel to B to indicate that testing is complete. control channel to B to indicate that testing is complete.
o B will respond by sending an EndVerifyAck message over the o B will respond by sending an EndVerifyAck message over the
control channel back to A. control channel back to A.
Note that this procedure can be used to "discover" the Note that this procedure can be used to "discover" the
connectivity of the data ports. connectivity of the data ports.
+---------------------+ +---------------------+ +---------------------+ +---------------------+
+ + + + + + + +
+ PXC A +<-------- c --------->+ PXC B + + Node A +<-------- c --------->+ Node B +
+ + + + + + + +
+ + + + + + + +
+ 1 +--------------------->+ 10 + + 1 +--------------------->+ 10 +
+ + + + + + + +
+ + + + + + + +
+ 2 + /---->+ 11 + + 2 + /---->+ 11 +
+ + /----/ + + + + /----/ + +
+ + /---/ + + + + /---/ + +
+ 3 +----/ + 12 + + 3 +----/ + 12 +
+ + + + + + + +
+ + + + + + + +
+ 4 +--------------------->+ 14 + + 4 +--------------------->+ 14 +
+ + + + + + + +
+---------------------+ +---------------------+ +---------------------+ +---------------------+
Figure 1: Example of link connectivity between PXC A and PXC B. Figure 1: Example of link connectivity between Node A and Node B.
6. Fault Management 6. Fault Management
In this section, an optional LMP procedure is described that is used In this section, an optional LMP procedure is described that is used
to manage failures by rapid notification of the status of one or to manage failures by rapid notification of the status of one or
more data channels of a TE Link. The scope of this procedure is more data channels of a TE Link. The scope of this procedure is
within a TE link, and as such, the use of this procedure is within a TE link, and as such, the use of this procedure is
negotiated as part of the LinkSummary exchange. The procedure can be negotiated as part of the LinkSummary exchange. The procedure can
used to rapidly isolate link failures and is designed to work for be used to rapidly isolate link failures and is designed to work for
both unidirectional and bi-directional LSPs. both unidirectional and bi-directional LSPs.
An important implication of using PXCs is that traditional methods An important implication of using transparent devices is that
that are used to monitor the health of allocated data links in OEO traditional methods that are used to monitor the health of allocated
nodes (e.g., DXCs) may no longer be appropriate, since PXCs are data links in may no longer be appropriate. Instead, fault
transparent to the bit-rate, format, and wavelength. Instead, fault
detection is delegated to the physical layer (i.e., loss of light or detection is delegated to the physical layer (i.e., loss of light or
optical monitoring of the data) instead of layer 2 or layer 3. optical monitoring of the data) instead of layer 2 or layer 3.
Recall that a TE link connecting two nodes may consist of a number Recall that a TE link connecting two nodes may consist of a number
of data links. If one or more data links fail between two nodes, a of data links. If one or more data links fail between two nodes, a
mechanism must be used for rapid failure notification so that mechanism must be used for rapid failure notification so that
appropriate protection/restoration mechanisms can be initiated. If appropriate protection/restoration mechanisms can be initiated. If
the failure is subsequently cleared, then a mechanism must be used the failure is subsequently cleared, then a mechanism must be used
to notify that the failure is clear and the channel status is OK. to notify that the failure is clear and the channel status is OK.
6.1. Fault Detection 6.1. Fault Detection
Fault detection should be handled at the layer closest to the Fault detection should be handled at the layer closest to the
failure; for optical networks, this is the physical (optical) layer. failure; for optical networks, this is the physical (optical) layer.
One measure of fault detection at the physical layer is detecting One measure of fault detection at the physical layer is detecting
loss of light (LOL). Other techniques for monitoring optical signals loss of light (LOL). Other techniques for monitoring optical
are still being developed and will not be further considered in this signals are still being developed and will not be further considered
document. However, it should be clear that the mechanism used for in this document. However, it should be clear that the mechanism
fault notification in LMP is independent of the mechanism used to used for fault notification in LMP is independent of the mechanism
detect the failure, but simply relies on the fact that a failure is used to detect the failure, but simply relies on the fact that a
detected. failure is detected.
6.2. Fault Localization Procedure 6.2. Fault Localization Procedure
If data links fail between two PXCs, the power monitoring system in In some situations, a data link failure between two nodes is
all of the downstream nodes may detect LOL and indicate a failure. propagated downstream such that all the downstream nodes detect the
To avoid multiple alarms stemming from the same failure, LMP failure without localizing the failure. To avoid multiple alarms
provides a failure notification through the ChannelStatus message. stemming from the same failure, LMP provides failure notification
This message may be used to indicate that a single data channel has through the ChannelStatus message. This message may be used to
failed, multiple data channels have failed, or an entire TE link has indicate that a single data channel has failed, multiple data
failed. Failure correlation is done locally at each node upon channels have failed, or an entire TE link has failed. Failure
receipt of the failure notification. correlation is done locally at each node upon receipt of the failure
notification.
To localize a fault to a particular link between adjacent OXCs, a To localize a fault to a particular link between adjacent nodes, a
downstream node (downstream in terms of data flow) that detects data downstream node (downstream in terms of data flow) that detects data
link failures will send a ChannelStatus message to its upstream link failures will send a ChannelStatus message to its upstream
neighbor indicating that a failure has occurred (bundling together neighbor indicating that a failure has been detected (bundling
the notification of all of the failed data links). An upstream node together the notification of all of the failed data links). An
that receives the ChannelStatus message MUST send a ChannelStatusAck upstream node that receives the ChannelStatus message MUST send a
message to the downstream node indicating it has received the ChannelStatusAck message to the downstream node indicating it has
ChannelStatus message. The upstream node should correlate the received the ChannelStatus message. The upstream node should
failure to see if the failure is also detected locally (including correlate the failure to see if the failure is also detected locally
ingress side) for the corresponding LSP(s). If, for example, the for the corresponding LSP(s). If, for example, the failure is clear
failure is clear on the input of the upstream node or internally, on the input of the upstream node or internally, then the upstream
then the upstream node will have localized the failure. Once the node will have localized the failure. Once the failure is
failure is correlated, the upstream node SHOULD send a ChannelStatus correlated, the upstream node SHOULD send a ChannelStatus message to
message to the downstream node indicating that the channel is failed the downstream node indicating that the channel is failed or is ok.
or is ok. If a ChannelStatus message is not received by the If a ChannelStatus message is not received by the downstream node,
downstream node, it SHOULD send a ChannelStatusRequest message for it SHOULD send a ChannelStatusRequest message for the channel in
the channel in question. Once the failure has been localized, the question. Once the failure has been localized, the signaling
signaling protocols may be used to initiate span or path protection protocols may be used to initiate span or path protection and
and restoration procedures. restoration procedures.
If all of the data links of a TE link have failed, then the upstream If all of the data links of a TE link have failed, then the upstream
node MAY be notified of the TE link failure without specifying each node MAY be notified of the TE link failure without specifying each
data link of the failed TE link. This is done by sending failure data link of the failed TE link. This is done by sending failure
notification in a ChannelStatus message identifying the TE Link notification in a ChannelStatus message identifying the TE Link
without including the Interface Ids in the CHANNEL_STATUS object. without including the Interface_Ids in the CHANNEL_STATUS object.
6.3. Examples of Fault Localization 6.3. Examples of Fault Localization
In Fig. 2, a sample network is shown where four nodes are connected In Fig. 2, a sample network is shown where four nodes are connected
in a linear array configuration. The control channels are bi- in a linear array configuration. The control channels are bi-
directional and are labeled with a "c". All LSPs are also bi- directional and are labeled with a "c". All LSPs are also bi-
directional. directional.
In the first example [see Fig. 2(a)], there is a failure on one In the first example [see Fig. 2(a)], there is a failure on one
direction of the bi-directional LSP. Node 4 will detect the failure direction of the bi-directional LSP. Node 4 will detect the failure
and will send a ChannelStatus message to Node 3 indicating the and will send a ChannelStatus message to Node 3 indicating the
failure (e.g., LOL) to the corresponding upstream node. When Node 3 failure (e.g., LOL) to the corresponding upstream node. When Node 3
receives the ChannelStatus message from Node 4, it returns a receives the ChannelStatus message from Node 4, it returns a
ChannelStatusAck message back to Node 4 and correlates the failure ChannelStatusAck message back to Node 4 and correlates the failure
locally. When Node 3 correlates the failure and verifies that it is locally. When Node 3 correlates the failure and verifies that the
CLEAR, it has localized the failure to the data link between Node 3 failure is clear, it has localized the failure to the data link
and Node 4. At that time, Node 3 should send a ChannelStatus message between Node 3 and Node 4. At that time, Node 3 should send a
to Node 4 indicating that the failure has been localized. ChannelStatus message to Node 4 indicating that the failure has been
localized.
In the second example [see Fig. 2(b)], a single failure (e.g., fiber In the second example [see Fig. 2(b)], a single failure (e.g., fiber
cut) affects both directions of the bi-directional LSP. Node 2 (Node cut) affects both directions of the bi-directional LSP. Node 2
3) will detect the failure of the upstream (downstream) direction (Node 3) will detect the failure of the upstream (downstream)
and send a ChannelStatus message to the upstream (in terms of data direction and send a ChannelStatus message to the upstream (in terms
flow) node indicating the failure (e.g., LOL). Simultaneously of data flow) node indicating the failure (e.g., LOL).
(ignoring propagation delays), Node 1 (Node 4) will detect the Simultaneously (ignoring propagation delays), Node 1 (Node 4) will
failure on the upstream (downstream) direction, and will send a detect the failure on the upstream (downstream) direction, and will
ChannelStatus message to the corresponding upstream (in terms of send a ChannelStatus message to the corresponding upstream (in terms
data flow) node indicating the failure. Node 2 and Node 3 will have of data flow) node indicating the failure. Node 2 and Node 3 will
localized the two directions of the failure. have localized the two directions of the failure.
+-------+ +-------+ +-------+ +-------+ +-------+ +-------+ +-------+ +-------+
+ Node1 + + Node2 + + Node3 + + Node4 + + Node1 + + Node2 + + Node3 + + Node4 +
+ +-- c ---+ +-- c ---+ +-- c ---+ + + +-- c ---+ +-- c ---+ +-- c ---+ +
----+---\ + + + + + + + ----+---\ + + + + + + +
<---+---\\--+--------+-------+---\ + + + /--+---> <---+---\\--+--------+-------+---\ + + + /--+--->
+ \--+--------+-------+---\\---+-------+---##---+---//--+---- + \--+--------+-------+---\\---+-------+---##---+---//--+----
+ + + + \---+-------+--------+---/ + + + + + \---+-------+--------+---/ +
+ + + + + + (a) + + + + + + + + (a) + +
----+-------+--------+---\ + + + + + ----+-------+--------+---\ + + + + +
skipping to change at page 20, line 4 skipping to change at page 22, line 34
LSP fails, (B) two data links corresponding to both LSP fails, (B) two data links corresponding to both
directions of a bi-directional LSP fail. The control channel directions of a bi-directional LSP fail. The control channel
connecting two nodes is indicated with a "c". connecting two nodes is indicated with a "c".
6.4. Channel Activation Indication 6.4. Channel Activation Indication
The ChannelStatus message may also be used to notify an LMP neighbor The ChannelStatus message may also be used to notify an LMP neighbor
that the data link should be actively monitored. This is called that the data link should be actively monitored. This is called
Channel Activation Indication. This is particularly useful in Channel Activation Indication. This is particularly useful in
networks with transparent nodes where the status of data links may networks with transparent nodes where the status of data links may
need to be triggered using control channel messages. For example, if need to be triggered using control channel messages. For example,
a data link is pre-provisioned and the physical link fails after if a data link is pre-provisioned and the physical link fails after
verification and before inserting user traffic, a mechanism is verification and before inserting user traffic, a mechanism is
needed to indicate the data link should be active or the failure may needed to indicate the data link should be active or the failure may
not be able to be detected. not be able to be detected.
The ChannelStatus message is used to indicate that a channel or The ChannelStatus message is used to indicate that a channel or
group of channels are now active. The ChannelStatusAck message MUST group of channels are now active. The ChannelStatusAck message MUST
be transmitted upon receipt of a ChannelStatus message. When a be transmitted upon receipt of a ChannelStatus message. When a
ChannelStatus message is received, the corresponding data link(s) ChannelStatus message is received, the corresponding data link(s)
MUST be put into the Active state. If upon putting them into the MUST be put into the Active state. If upon putting them into the
Active state, a failure is detected, the ChannelStatus message Active state, a failure is detected, the ChannelStatus message
SHOULD be transmitted as described in Section 6.2. SHOULD be transmitted as described in Section 6.2.
6.5. Channel Deactivation Indication 6.5. Channel Deactivation Indication
The ChannelStatus message may also be used to notify an LMP neighbor The ChannelStatus message may also be used to notify an LMP neighbor
that the data link no longer needs to be actively monitored. This is that the data link no longer needs to be actively monitored. This
the counterpart to the Channel Active Indication. is the counterpart to the Channel Active Indication.
When a ChannelStatus message is received with Channel Deactive When a ChannelStatus message is received with Channel Deactive
Indication, the corresponding data link(s) MUST be taken out of the Indication, the corresponding data link(s) MUST be taken out of the
Active state. Active state.
7. Message_Id Usage 7. Message_Id Usage
The MESSAGE_ID and MESSAGE_ID_ACK objects are included in LMP The MESSAGE_ID and MESSAGE_ID_ACK objects are included in LMP
messages to support reliable message delivery. This section messages to support reliable message delivery. This section
describes the usage of these objects. The MESSAGE_ID and describes the usage of these objects. The MESSAGE_ID and
MESSAGE_ID_ACK objects contain a Message_Id field. Only one MESSAGE_ID_ACK objects contain a Message_Id field.
MESSAGE_ID/MESSAGE_ID_ACK object may be included in any LMP message.
Only one MESSAGE_ID/MESSAGE_ID_ACK object may be included in any LMP
message.
For control channel specific messages, the Message_Id field is For control channel specific messages, the Message_Id field is
within the scope of the CCID. For TE link specific messages, the within the scope of the CC_Id. For TE link specific messages, the
Message_Id field is within the scope of the LMP adjacency. Message_Id field is within the scope of the LMP adjacency.
The Message_Id field of the MESSAGE_ID object contains a generator The Message_Id field of the MESSAGE_ID object contains a generator-
selected value. This value MUST be monotonically increasing. A value selected value. This value MUST be monotonically increasing. A
is considered to be previously used when it has been sent in an LMP value is considered to be previously used when it has been sent in
message with the same CCID (for control channel specific messages) an LMP message with the same CC_Id (for control channel specific
or LMP adjacency (for TE Link specific messages). The Message_Id messages) or LMP adjacency (for TE Link specific messages). The
field of the MESSAGE_ID_ACK object contains the Message_Id field of Message_Id field of the MESSAGE_ID_ACK object contains the
the message being acknowledged. Message_Id field of the message being acknowledged.
Unacknowledged messages sent with the MESSAGE_ID object SHOULD be Unacknowledged messages sent with the MESSAGE_ID object SHOULD be
retransmitted until the message is acknowledged or until a retry retransmitted until the message is acknowledged or until a retry
limit is reached (see also Section 10). limit is reached (see also Section 10).
Note that the 32-bit Message_Id value MAY wrap. The following Note that the 32-bit Message_Id value MAY wrap. The following
expression may be used to test if a newly received Message_Id value expression may be used to test if a newly received Message_Id value
is less than a previously received value: is less than a previously received value:
If ((int) old_id Ż (int) new_id > 0) { If ((int) old_id - (int) new_id > 0) {
New value is less than old value; New value is less than old value;
} }
Nodes processing incoming messages SHOULD check to see if a newly Nodes processing incoming messages SHOULD check to see if a newly
received message is out of order and can be ignored. Out-of-order received message is out of order and can be ignored. Out-of-order
messages can be identified by examining the value in the Message_Id messages can be identified by examining the value in the Message_Id
field. field. If a message is determined to be out-of-order, that message
should be silently dropped.
If the message is a Config message, and the Message_Id value is less If the message is a Config message, and the Message_Id value is less
than the largest Message_Id value previously received from the than the largest Message_Id value previously received from the
sender for the CCID, then the message SHOULD be treated as being out sender for the CC_Id, then the message SHOULD be treated as being
of order. out-of-order.
If the message is a LinkSummary message and the Message_Id value is If the message is a LinkSummary message and the Message_Id value is
less than the largest Message_Id value previously received from the less than the largest Message_Id value previously received from the
sender for the TE Link, then the message SHOULD be treated as being sender for the TE Link, then the message SHOULD be treated as being
out of order. out-of-order.
If the message is a ChannelStatus message and the Message_Id value If the message is a ChannelStatus message and the Message_Id value
is less than the largest Message_Id value previously received from is less than the largest Message_Id value previously received from
the sender for the specified TE link, then the receiver SHOULD check the sender for the specified TE link, then the receiver SHOULD check
the Message_Id value previously received for the state of each data the Message_Id value previously received for the state of each data
channel included in the ChannelStatus message. If the Message_Id channel included in the ChannelStatus message. If the Message_Id
value is greater than the most recently received Message_Id value value is greater than the most recently received Message_Id value
associated with at least one of the data channels included in the associated with at least one of the data channels included in the
message, the message MUST NOT be treated as out of order; otherwise message, the message MUST NOT be treated as out of order; otherwise
the message SHOULD be treated as being out of order. However, the the message SHOULD be treated as being out of order. However, the
state of any data channel MUST NOT be updated if the Message_Id state of any data channel MUST NOT be updated if the Message_Id
value is less than the most recently received Message_Id value value is less than the most recently received Message_Id value
associated with the data channel. associated with the data channel.
All other messages MUST NOT be treated as out-of-order. All other messages MUST NOT be treated as out-of-order.
8. Graceful Restart 8. Graceful Restart
This section describes the mechanism to resynchronize the LMP state This section describes the mechanism to resynchronize the LMP state
after a control plane restart. A control plane restart may occur after a control plane restart. A control plane restart may occur
when bringing up the first control channel after an LMP adjacency when bringing up the first control channel after a control
has failed, or as a result of an LMP component restart. The latter communications failure. A control communications failure may be the
is detected by setting the "LMP Restart" bit in the Common Header of result of an LMP adjacency failure or a nodal failure wherein the
the LMP messages. When the control plane fails due to the loss of LMP control state is lost, but the data plane is unaffected. The
the control channel (rather than an LMP component restart), the LMP latter is detected by setting the "LMP Restart" bit in the Common
Link information should be retained. It is possible that a node may Header of the LMP messages. When the control plane fails due to the
be capable of retaining the LMP Link information across an LMP loss of the control channel, the LMP link information should be
component restart. However, in both cases the status of the data retained. It is possible that a node may be capable of retaining
channels MUST be synchronized. the LMP link information across a nodal failure. However, in both
cases the status of the data channels MUST be synchronized.
It is assumed the Local Interface Ids remain stable across a control It is assumed the Local Interface_Ids remain stable across a control
plane restart. plane restart.
After the control plane of a node restarts, the control channel(s) After the control plane of a node restarts, the control channel(s)
must be re-established using the procedures of Section 3.1. must be re-established using the procedures of Section 3.1.
If the control plane failure was the result of an LMP component If the control plane failure was the result of a nodal failure where
restart, then the "LMP Restart" flag MUST be set in LMP messages the LMP control state is lost, then the "LMP Restart" flag MUST be
until a Hello message is received with the RcvSeqNum equal to the set in LMP messages until a Hello message is received with the
local TxSeqNum. This indicates that the control channel is UP and RcvSeqNum equal to the local TxSeqNum. This indicates that the
the LMP neighbor has detected the restart. control channel is up and the LMP neighbor has detected the restart.
The following assumes that the LMP component restart only occurred The following assumes that the LMP component restart only occurred
on one end of the TE Link. If the LMP component restart occurred on on one end of the TE Link. If the LMP component restart occurred on
both ends of the TE Link, the normal procedures for LinkSummary both ends of the TE Link, the normal procedures for LinkSummary
should be used, as described in Section 4. should be used, as described in Section 4.
Once a control channel is UP, the LMP neighbor MUST send a Once a control channel is up, the LMP neighbor MUST send a
LinkSummary message for each TE Link across the adjacency. All the LinkSummary message for each TE Link across the adjacency. All the
objects of the LinkSummary message MUST have the N-bit set to 0 objects of the LinkSummary message MUST have the N-bit set to 0
indicating that the parameters are non-negotiable. This provides the indicating that the parameters are non-negotiable. This provides
local/remote Link Id and Interace Id mappings, the associated the local/remote Link_Id and Interface_Id mappings, the associated
Link/Data channel parameters, and indication of which data links are data link parameters, and indication of which data links are
currently allocated to user traffic. When a node receives the currently allocated to user traffic. When a node receives the
LinkSummary message, it checks its local configuration. If the node LinkSummary message, it checks its local configuration. If the node
is capable of retaining the LMP Link information across a restart, is capable of retaining the LMP link information across a restart,
it must process the LinkSummary message as described in Section 4 it must process the LinkSummary message as described in Section 4
with the exception that the allocated/deallocated flag of the with the exception that the allocated/de-allocated flag of the
DATA_LINK object received in the LinkSummary message MUST take DATA_LINK object received in the LinkSummary message MUST take
precedence over any local value. If, however, the node was not precedence over any local value. If, however, the node was not
capable of retaining the LMP Link information across a restart, the capable of retaining the LMP link information across a restart, the
node MUST accept the Link/Data channel parameters of the received node MUST accept the data link parameters of the received
LinkSummary message and respond with a LinkSummaryAck message. LinkSummary message and respond with a LinkSummaryAck message.
Upon completion of the LinkSummary exchange, the node that has Upon completion of the LinkSummary exchange, the node that has
restarted the control plane SHOULD send a ChannelStatusRequest restarted the control plane SHOULD send a ChannelStatusRequest
message for that TE link. The node SHOULD also verify the message for that TE link. The node SHOULD also verify the
connectivity of all unallocated data channels. connectivity of all unallocated data channels.
9. Addressing 9. Addressing
All LMP messages are sent directly over IP (except, in some cases, All LMP messages are run over UDP with an LMP port number (except,
the Test messages are limited by the transport mechanism for in-band in some cases, the Test messages which may be limited by the
messaging). The destination address of the IP packet MAY be either transport mechanism for in-band messaging). The destination address
the address learned in the Configuration procedure (i.e., the Source of the IP packet MAY be either the address learned in the
IP address found in the IP header of the received Config message), Configuration procedure (i.e., the Source IP address found in the IP
an IP address configured on the remote node, or the node ID. The header of the received Config message), an IP address configured on
Config message is an exception as described below. the remote node, or the Node_Id. The Config message is an exception
as described below.
The manner in which a Config message is addressed may depend on the The manner in which a Config message is addressed may depend on the
signaling transport mechanism. When the transport mechanism is a signaling transport mechanism. When the transport mechanism is a
point-to-point link, Config messages SHOULD be sent to the Multicast point-to-point link, Config messages SHOULD be sent to the Multicast
address (224.0.0.1). Otherwise, Config messages MUST be sent to an address (224.0.0.1). Otherwise, Config messages MUST be sent to an
IP address on the neighboring node. This may be configured at both IP address on the neighboring node. This may be configured at both
ends of the control channel or may be automatically discovered. ends of the control channel or may be automatically discovered.
10. Exponential Back-off Procedures 10. Exponential Back-off Procedures
This section is based on [RFC2961] and provides exponential backup This section is based on [RFC2961] and provides exponential back-off
procedures for message retransmission. Implementations MUST use the procedures for message retransmission. Implementations MUST use the
described procedures or their equivalent. described procedures or their equivalent.
10.1. Operation 10.1. Operation
The following operation is one possible mechanism for exponential The following operation is one possible mechanism for exponential
back-off retransmission of unacknowledged LMP messages. The sending back-off retransmission of unacknowledged LMP messages. The sending
node retransmits the message until an acknowledgement message is node retransmits the message until an acknowledgement message is
received or until a retry limit is reached. When the sending node received or until a retry limit is reached. When the sending node
receives the acknowledgement, retransmission of the message is receives the acknowledgement, retransmission of the message is
skipping to change at page 24, line 21 skipping to change at page 27, line 4
while (Rn++ < Rl) { while (Rn++ < Rl) {
transmit the message; transmit the message;
wake up after Rk milliseconds; wake up after Rk milliseconds;
Rk = Rk * (1 + Delta); Rk = Rk * (1 + Delta);
} }
/* acknowledged message or no reply from receiver and Rl /* acknowledged message or no reply from receiver and Rl
reached*/ reached*/
do any needed clean up; do any needed clean up;
exit; exit;
Asynchronously, when a sending node receives a corresponding Asynchronously, when a sending node receives a corresponding
acknowledgment message, it will change the retry count, Rn, to Rl. acknowledgment message, it will change the retry count, Rn, to Rl.
Note that the transmitting node does not advertise or negotiate the Note that the transmitting node does not advertise or negotiate the
use of the described exponential back-off procedures in the Config use of the described exponential back-off procedures in the Config
or LinkSummary messages. or LinkSummary messages.
11. IANA Considerations 11. LMP Finite State Machines
LMP defines the following name spaces that require management:
- Msg Type Name Space.
- LMP Object Class name space.
- LMP Object Class type (C-Type). These are unique within the Object
Class.
Following the policies outlined in [IANA], Msg Type, Object Class,
and Class type are allocated through an IETF Consensus action.
12. LMP Finite State Machines
12.1. Control Channel FSM 11.1. Control Channel FSM
The control channel FSM defines the states and logics of operation The control channel FSM defines the states and logics of operation
of an LMP control channel. The description of FSM state transitions of an LMP control channel.
and associated actions is given in Section 3.
12.1.1. Control Channel States 11.1.1. Control Channel States
A control channel can be in one of the states described below. Every A control channel can be in one of the states described below.
state corresponds to a certain condition of the control channel and Every state corresponds to a certain condition of the control
is usually associated with a specific type of LMP message that is channel and is usually associated with a specific type of LMP
periodically transmitted to the far end. message that is periodically transmitted to the far end.
Down: This is the initial control channel state. In this Down: This is the initial control channel state. In this
state, no attempt is being made to bring the control state, no attempt is being made to bring the control
channel up and no LMP messages are sent. The control channel up and no LMP messages are sent. The control
channel parameters should be set to the initial values. channel parameters should be set to the initial values.
ConfigSnd: The control channel is in the parameter negotiation ConfSnd: The control channel is in the parameter negotiation
state. In this state the node periodically sends a state. In this state the node periodically sends a
Config message, and is expecting the other side to Config message, and is expecting the other side to
reply with either a ConfigAck or ConfigNack message. reply with either a ConfigAck or ConfigNack message.
The FSM does not transition into the Active state until The FSM does not transition into the Active state until
the remote side positively acknowledges the parameters. the remote side positively acknowledges the parameters.
ConfRcv: The control channel is in the parameter negotiation ConfRcv: The control channel is in the parameter negotiation
state. In this state, the node is waiting for state. In this state, the node is waiting for
acceptable configuration parameters from the remote acceptable configuration parameters from the remote
side. Once such parameters are received and side. Once such parameters are received and
acknowledged, the FSM can transition to the Active acknowledged, the FSM can transition to the Active
state. state.
Active: In this state the node periodically sends a Hello Active: In this state the node periodically sends a Hello
message and is waiting to receive a valid Hello message and is waiting to receive a valid Hello
message. Once a valid Hello message is received, it can message. Once a valid Hello message is received, it
transition to the UP state. can transition to the up state.
Up: The CC is in an operational state. The node receives Up: The CC is in an operational state. The node receives
valid Hello messages and sends Hello messages. valid Hello messages and sends Hello messages.
GoingDown: A CC may go into this state because of administrative GoingDown: A CC may go into this state because of administrative
action. While a CC is in this state, the node sets the action. While a CC is in this state, the node sets the
ControlChannelDown bit in all the messages it sends. ControlChannelDown bit in all the messages it sends.
12.1.2. Control Channel Events 11.1.2. Control Channel Events
Operation of the LMP control channel is described in terms of FSM Operation of the LMP control channel is described in terms of FSM
states and events. Control channel Events are generated by the states and events. Control channel events are generated by the
underlying protocols and software modules, as well as by the packet underlying protocols and software modules, as well as by the packet
processing routines and FSMs of associated TE links. Every event has processing routines and FSMs of associated TE links. Every event
its number and a symbolic name. Description of possible control has its number and a symbolic name. Description of possible control
channel events is given below. channel events is given below.
1 : evBringUp: This is an externally triggered event indicating 1 : evBringUp: This is an externally triggered event indicating
that the control channel negotiation should begin. that the control channel negotiation should begin.
This event, for example, may be triggered by an This event, for example, may be triggered by an
operator command, by the successful completion of operator command, by the successful completion of
a control channel bootstrap procedure, or by a control channel bootstrap procedure, or by
configuration. Depending on the configuration, configuration. Depending on the configuration,
this will trigger either this will trigger either
1a) the sending of a Config message, 1a) the sending of a Config message,
skipping to change at page 26, line 15 skipping to change at page 28, line 35
2 : evCCDn: This event is generated when there is indication 2 : evCCDn: This event is generated when there is indication
that the control channel is no longer available. that the control channel is no longer available.
3 : evConfDone: This event indicates a ConfigAck message has been 3 : evConfDone: This event indicates a ConfigAck message has been
received, acknowledging the Config parameters. received, acknowledging the Config parameters.
4 : evConfErr: This event indicates a ConfigNack message has been 4 : evConfErr: This event indicates a ConfigNack message has been
received, rejecting the Config parameters. received, rejecting the Config parameters.
5 : evNewConfOK: New Config message was received from neighbor and 5 : evNewConfOK: New Config message was received from neighbor and
positively Acknowledged. positively acknowledged.
6 : evNewConfErr: New Config message was received from neighbor and 6 : evNewConfErr: New Config message was received from neighbor and
rejected with a ConfigNack message. rejected with a ConfigNack message.
7 : evContenWin: New Config message was received from neighbor at 7 : evContenWin: New Config message was received from neighbor at
the same time a Config message was sent to the the same time a Config message was sent to the
neighbor. The Local node wins the contention. As a neighbor. The local node wins the contention. As
result, the received Config message is ignored. a result, the received Config message is ignored.
8 : evContenLost: New Config message was received from neighbor at 8 : evContenLost: New Config message was received from neighbor at
the same time a Config message was sent to the the same time a Config message was sent to the
neighbor. The Local node loses the contention. neighbor. The local node loses the contention.
8a) The Config message is positively 8a) The Config message is positively
Acknowledged. acknowledged.
8b) The Config message is negatively 8b) The Config message is negatively
Acknowledged. acknowledged.
9 : evAdminDown: The administrator has requested that the control 9 : evAdminDown: The administrator has requested that the control
channel is brought down administratively. Hello channel is brought down administratively.
messages (with ControlChannelDown flag set) SHOULD
be sent for HelloDeadInterval seconds or until an
LMP message is received over the control channel
with the ControlChannelDown flag set.
10: evNbrGoesDn: A packet with ControlChannelDown flag is received 10: evNbrGoesDn: A packet with ControlChannelDown flag is received
from the neighbor. from the neighbor.
11: evHelloRcvd: A Hello packet with expected SeqNum has been 11: evHelloRcvd: A Hello packet with expected SeqNum has been
received. received.
12: evHoldTimer: The HelloDeadInterval timer has expired indicating 12: evHoldTimer: The HelloDeadInterval timer has expired indicating
that no Hello packet has been received. This moves that no Hello packet has been received. This
the control channel back into the Negotiation moves the control channel back into the
state, and depending on the local configuration, Negotiation state, and depending on the local
this will trigger either configuration, this will trigger either
12a) the sending of periodic Config messages, 12a) the sending of periodic Config messages,
12b) a period of waiting to receive Config 12b) a period of waiting to receive Config
messages from the remote node. messages from the remote node.
13: evSeqNumErr: A Hello with unexpected SeqNum received and 13: evSeqNumErr: A Hello with unexpected SeqNum received and
discarded. discarded.
14: evReconfig: Control channel parameters have been reconfigured 14: evReconfig: Control channel parameters have been reconfigured
and require renegotiation. and require renegotiation.
15: evConfRet: A retransmission timer has expired and a Config 15: evConfRet: A retransmission timer has expired and a Config
message is resent. message is resent.
16: evHelloRet: The HelloInterval timer has expired and a Hello 16: evHelloRet: The HelloInterval timer has expired and a Hello
packet is sent. packet is sent.
17: evDownTimer: A timer has expired and no messages have been 17: evDownTimer: A timer has expired and no messages have been
received with the ControlChannelDown flag set. received with the ControlChannelDown flag set.
12.1.3. Control Channel FSM Description 11.1.3. Control Channel FSM Description
Figure 3 illustrates operation of the control channel FSM Figure 3 illustrates operation of the control channel FSM
in a form of FSM state transition diagram. in a form of FSM state transition diagram.
+--------+ +--------+
+----------------->| |<--------------+ +----------------->| |<--------------+
| +--------->| Down |<----------+ | | +--------->| Down |<----------+ |
| |+---------| |<-------+ | | | |+---------| |<-------+ | |
| || +--------+ | | | | || +--------+ | | |
| || | ^ 2,9| 2| 2| | || | ^ 2,9| 2| 2|
skipping to change at page 29, line 4 skipping to change at page 31, line 4
|9 |10 +--------+ | |12a,14 | |9 |10 +--------+ | |12a,14 |
| +----------| |---+ | | | +----------| |---+ | |
| | Up |-------+ | | | Up |-------+ |
+------------------| |---------------+ +------------------| |---------------+
+--------+ +--------+
| ^ | ^
| | | |
+---+ +---+
11,13,16 11,13,16
Figure 3: Control Channel FSM Figure 3: Control Channel FSM
Event evCCDn always forces the FSM to the Down State. Events Event evCCDn always forces the FSM to the down state. Events
evHoldTimer evReconfig always force the FSM to the Negotiation state evHoldTimer evReconfig always force the FSM to the Negotiation state
(either ConfigSnd or ConfigRcv). (either ConfSnd or ConfRcv).
12.2. TE Link FSM 11.2. TE Link FSM
The TE Link FSM defines the states and logics of operation of an LMP The TE Link FSM defines the states and logics of operation of the
TE Link. LMP TE Link.
12.2.1. TE Link States 11.2.1. TE Link States
An LMP TE link can be in one of the states described below. Every An LMP TE link can be in one of the states described below. Every
state corresponds to a certain condition of the TE link and is state corresponds to a certain condition of the TE link and is
usually associated with a specific type of LMP message that is usually associated with a specific type of LMP message that is
periodically transmitted to the far end via the associated control periodically transmitted to the far end via the associated control
channel or in-band via the data links. channel or in-band via the data links.
Down: There are no data links allocated to the TE link. Down: There are no data links allocated to the TE link.
Init: Data links have been allocated to the TE link, but the Init: Data links have been allocated to the TE link, but the
configuration has not yet been synchronized with the LMP configuration has not yet been synchronized with the LMP
neighbor. neighbor.
Up: This is the normal operational state of the TE link. At Up: This is the normal operational state of the TE link. At
least one primary CC is required to be operational least one LMP control channel is required to be
between the nodes sharing the TE link. operational between the nodes sharing the TE link.
Degraded: In this state, all primary CCs are down, but the TE link Degraded: In this state, all LMP control channels are down, but
still includes some data links that are allocated to the TE link still includes some data links that are
data traffic. allocated to user traffic.
12.2.2. TE Link Events 11.2.2. TE Link Events
Operation of the LMP TE link is described in terms of FSM states and Operation of the LMP TE link is described in terms of FSM states and
events. TE Link events are generated by the packet processing events. TE Link events are generated by the packet processing
routines and by the FSMs of the associated primary control routines and by the FSMs of the associated control channel(s) and
channel(s) and the data links. Every event has its number and a the data links. Every event has its number and a symbolic name.
symbolic name. Description of possible control channel events is Description of possible events is given below.
given below.
1 : evDCUp: One or more data channels have been enabled and 1 : evDCUp: One or more data channels have been enabled and
assigned to the TE Link. assigned to the TE Link.
2 : evSumAck: LinkSummary message received and positively 2 : evSumAck: LinkSummary message received and positively
acknowledged. acknowledged.
3 : evSumNack: LinkSummary message received and negatively 3 : evSumNack: LinkSummary message received and negatively
acknowledged. acknowledged.
4 : evRcvAck: LinkSummaryAck message received acknowledging 4 : evRcvAck: LinkSummaryAck message received acknowledging
the TE Link Configuration. the TE Link Configuration.
5 : evRcvNack: LinkSummaryNack message received. 5 : evRcvNack: LinkSummaryNack message received.
skipping to change at page 30, line 4 skipping to change at page 31, line 55
2 : evSumAck: LinkSummary message received and positively 2 : evSumAck: LinkSummary message received and positively
acknowledged. acknowledged.
3 : evSumNack: LinkSummary message received and negatively 3 : evSumNack: LinkSummary message received and negatively
acknowledged. acknowledged.
4 : evRcvAck: LinkSummaryAck message received acknowledging 4 : evRcvAck: LinkSummaryAck message received acknowledging
the TE Link Configuration. the TE Link Configuration.
5 : evRcvNack: LinkSummaryNack message received. 5 : evRcvNack: LinkSummaryNack message received.
6 : evSumRet: Retransmission timer has expired and LinkSummary 6 : evSumRet: Retransmission timer has expired and LinkSummary
message is resent. message is resent.
7 : evCCUp: First active control channel goes up. 7 : evCCUp: First active control channel goes up.
8 : evCCDown: Last active control channel goes down. 8 : evCCDown: Last active control channel goes down.
9 : evDCDown: Last data channel of TE Link has been removed. 9 : evDCDown: Last data channel of TE Link has been removed.
12.2.3. TE Link FSM Description 11.2.3. TE Link FSM Description
Figure 4 illustrates operation of the LMP TE Link FSM in a form of Figure 4 illustrates operation of the LMP TE Link FSM in a form of
FSM state transition diagram. FSM state transition diagram.
3,7,8 3,7,8
+--+ +--+
| | | |
| v | v
+--------+ +--------+
| | | |
skipping to change at page 30, line 48 skipping to change at page 32, line 47
| ^ | ^
| | | |
+--+ +--+
2,3,4,5,6 2,3,4,5,6
Figure 4: LMP TE Link FSM Figure 4: LMP TE Link FSM
In the above FSM, the sub-states that may be implemented when the In the above FSM, the sub-states that may be implemented when the
link verification procedure is used have been omitted. link verification procedure is used have been omitted.
12.3. Data Link FSM 11.3. Data Link FSM
The data link FSM defines the states and logics of operation of a The data link FSM defines the states and logics of operation of a
port or component link within an LMP TE link. Operation of a data data link within an LMP TE link. Operation of a data link is
link is described in terms of FSM states and events. Data-bearing described in terms of FSM states and events. Data links can either
links can either be in the active (transmitting) mode, where Test be in the active (transmitting) mode, where Test messages are
messages are transmitted from them, or the passive (receiving) mode, transmitted from them, or the passive (receiving) mode, where Test
where Test messages are received through them. For clarity, separate messages are received through them. For clarity, separate FSMs are
FSMs are defined for the active/passive data-bearing links; however, defined for the active/passive data links; however, a single set of
a single set of data link states and events are defined. data link states and events are defined.
12.3.1. Data Link States 11.3.1. Data Link States
Any data link can be in one of the states described below. Every Any data link can be in one of the states described below. Every
state corresponds to a certain condition of the TE link. state corresponds to a certain condition of the data link.
Down: The data link has not been put in the resource pool Down: The data link has not been put in the resource pool
(i.e., the link is not śin service∆ (i.e., the link is not śin service∆)
Test: The data link is being tested. An LMP Test message is Test: The data link is being tested. An LMP Test message
periodically sent through the link. is periodically sent through the link.
PasvTest: The data link is being checked for incoming test PasvTest: The data link is being checked for incoming test
messages. messages.
Up/Free: The link has been successfully tested and is now put Up/Free: The link has been successfully tested and is now put
in the pool of resources (in-service). The link has in the pool of resources (in-service). The link has
not yet been allocated to data traffic. not yet been allocated to data traffic.
Up/Allocated: The link is UP and has been allocated for data Up/Alloc: The link is up and has been allocated for data
traffic. traffic.
12.3.2. Data Link Events 11.3.2. Data Link Events
Data bearing link events are generated by the packet processing Data link events are generated by the packet processing routines and
routines and by the FSMs of the associated control channel and the by the FSMs of the associated control channel and the TE link.
TE link. Every event has its number and a symbolic name. Description Every event has its number and a symbolic name. Description of
of possible data link events is given below: possible data link events is given below:
1 :evCCUp: CC has gone up. 1 :evCCUp: First active control channel goes up.
2 :evCCDown: LMP neighbor connectivity is lost. This indicates 2 :evCCDown: LMP neighbor connectivity is lost. This indicates
the last LMP control channel has failed between the last LMP control channel has failed between
neighboring nodes. neighboring nodes.
3 :evStartTst: This is an external event that triggers the sending 3 :evStartTst: This is an external event that triggers the sending
of Test messages over the data bearing link. of Test messages over the data link.
4 :evStartPsv: This is an external event that triggers the 4 :evStartPsv: This is an external event that triggers the
listening for Test messages over the data bearing listening for Test messages over the data link.
link.
5 :evTestOK: Link verification was successful and the link can 5 :evTestOK: Link verification was successful and the link can
be used for path establishment. be used for path establishment.
(a) This event indicates the Link Verification (a) This event indicates the Link Verification
procedure (see Section 5) was successful procedure (see Section 5) was successful
for this data link and a TestStatusSuccess for this data link and a TestStatusSuccess
message was received over the control message was received over the control
channel. channel.
(b) This event indicates the link is ready for (b) This event indicates the link is ready for
path establishment, but the Link path establishment, but the Link
skipping to change at page 32, line 21 skipping to change at page 34, line 20
could be because (a) a TestStatusFailure message could be because (a) a TestStatusFailure message
was received, or (b) the Verification procedure has was received, or (b) the Verification procedure has
ended without receiving a TestStatusSuccess or ended without receiving a TestStatusSuccess or
TestStatusFailure message for the data link. TestStatusFailure message for the data link.
8 :evPsvTestFail:Link verification returned negative results. This 8 :evPsvTestFail:Link verification returned negative results. This
indicates that a Test message was not detected and indicates that a Test message was not detected and
either (a) the VerifyDeadInterval has expired or either (a) the VerifyDeadInterval has expired or
(b) the Verification procedure has ended and the (b) the Verification procedure has ended and the
VerifyDeadInterval has not yet expired. VerifyDeadInterval has not yet expired.
9 :evLnkAlloc: The data link has been allocated. 9 :evLnkAlloc: The data link has been allocated.
10:evLnkDealloc: The data link has been deallocated. 10:evLnkDealloc: The data link has been de-allocated.
11:evTestRet: A retransmission timer has expired and the Test 11:evTestRet: A retransmission timer has expired and the Test
message is resent. message is resent.
12:evSummaryFail:The LinkSummary did not match for this data port. 12:evSummaryFail:The LinkSummary did not match for this data port.
13:evLocalizeFail:A Failure has been localized to this data link. 13:evLocalizeFail:A Failure has been localized to this data link.
14:evdcDown: The data channel is no longer available. 14:evdcDown: The data channel is no longer available.
12.3.3. Active Data Link FSM Description 11.3.3. Active Data Link FSM Description
Figure 5 illustrates operation of the LMP active data link FSM in a Figure 5 illustrates operation of the LMP active data link FSM in a
form of FSM state transition diagram. form of FSM state transition diagram.
+------+ +------+
| |<-------+ | |<-------+
+--------->| Down | | +--------->| Down | |
| +----| |<-----+ | | +----| |<-----+ |
| | +------+ | | | | +------+ | |
| |5b 3| ^ | | | |5b 3| ^ | |
skipping to change at page 34, line 5 skipping to change at page 36, line 5
| | | | | |
v |10 | v |10 |
+---------+ | +---------+ |
| |13 | | |13 |
|Up/Alloc |------+ |Up/Alloc |------+
| | | |
+---------+ +---------+
Figure 5: Active LMP Data Link FSM Figure 5: Active LMP Data Link FSM
12.3.4. Passive Data Link FSM Description 11.3.4. Passive Data Link FSM Description
Figure 6 illustrates operation of the LMP passive data link FSM in a Figure 6 illustrates operation of the LMP passive data link FSM in a
form of FSM state transition diagram. form of FSM state transition diagram.
+------+ +------+
| |<------+ | |<------+
+---------->| Down | | +---------->| Down | |
| +-----| |<----+ | | +-----| |<----+ |
| | +------+ | | | | +------+ | |
| |5b 4| ^ | | | |5b 4| ^ | |
skipping to change at page 35, line 5 skipping to change at page 37, line 5
| | | | | |
v |10 | v |10 |
+---------+ | +---------+ |
| |13 | | |13 |
|Up/Alloc |-----+ |Up/Alloc |-----+
| | | |
+---------+ +---------+
Figure 6: Passive LMP Data Link FSM Figure 6: Passive LMP Data Link FSM
13. LMP Message Formats 12. LMP Message Formats
All LMP messages are IP encoded (except, in some cases, the Test All LMP messages are run over UDP with an LMP port number (except,
messages are limited by the transport mechanism for in-band in some cases, the Test messages are limited by the transport
messaging) and run over UDP with port number xxx - TBA (to be mechanism for in-band messaging) and run over UDP with port number
assigned) by IANA. xxx - TBA (to be assigned) by IANA.
13.1. Common Header 12.1. Common Header
In addition to the standard IP header, all LMP messages (except, in In addition to the UDP header and standard IP header, all LMP
some cases, the Test messages which are limited by the transport messages (except, in some cases, the Test messages which may be
mechanism for in-band messaging) have the following common header: limited by the transport mechanism for in-band messaging) have the
following common header:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers | (Reserved) | Flags | Msg Type | | Vers | (Reserved) | Flags | Msg Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LMP Length | Checksum | | LMP Length | (Reserved) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Reserved field should be sent as zero and ignored on receipt.
All values are defined in network byte order (i.e., big-endian byte
order).
Vers: 4 bits Vers: 4 bits
Protocol version number. This is version 1. Protocol version number. This is version 1.
Flags: 8 bits. The following values are defined. All other values Flags: 8 bits. The following values are defined. All other values
are reserved. are reserved and should be sent as zero and ignored on
receipt.
0x01: ControlChannelDown 0x01: ControlChannelDown
0x02: LMP Restart 0x02: LMP Restart
This bit is set to indicate the LMP component has This bit is set to indicate that a nodal failure has
restarted. This flag may be reset to 0 when a Hello occured and the LMP control state has been lost. This
message is received with RcvSeqNum equal to the local flag may be reset to 0 when a Hello message is received
TxSeqNum. with RcvSeqNum equal to the local TxSeqNum.
Msg Type: 8 bits. The following values are defined. All other values Msg Type: 8 bits. The following values are defined. All other
are reserved. values are reserved and should be sent as zero and ignored
on receipt.
1 = Config 1 = Config
2 = ConfigAck 2 = ConfigAck
3 = ConfigNack 3 = ConfigNack
4 = Hello 4 = Hello
5 = BeginVerify 5 = BeginVerify
6 = BeginVerifyAck 6 = BeginVerifyAck
7 = BeginVerifyNack 7 = BeginVerifyNack
8 = EndVerify 8 = EndVerify
9 = EndVerifyAck 9 = EndVerifyAck
10 = Test 10 = Test
11 = TestStatusSuccess 11 = TestStatusSuccess
skipping to change at page 36, line 41 skipping to change at page 38, line 49
All of the messages are sent over the control channel EXCEPT All of the messages are sent over the control channel EXCEPT
the Test message, which is sent over the data link that is the Test message, which is sent over the data link that is
being tested. being tested.
LMP Length: 16 bits LMP Length: 16 bits
The total length of this LMP message in bytes, including the The total length of this LMP message in bytes, including the
common header and any variable-length objects that follow. common header and any variable-length objects that follow.
Checksum: 16 bits 12.2. LMP Object Format
The standard IP checksum of the entire contents of the LMP
message, starting with the LMP message header. This checksum is
calculated as the 16-bit one's complement of the one's
complement sum of all the 16-bit words in the packet. If the
packet's length is not an integral number of 16-bit words, the
packet is padded with a byte of zero before calculating the
checksum.
13.2. LMP Object Format
LMP messages are built using objects. Each object is identified by LMP messages are built using objects. Each object is identified by
its Object Class and Class-type. Each object has a name, which is its Object Class and Class-type. Each object has a name, which is
always capitalized in this document. LMP objects can be either always capitalized in this document. LMP objects can be either
negotiable or non-negotiable (identified by the N bit in the object negotiable or non-negotiable (identified by the N bit in the object
header). Negotiable objects can be used to let the devices agree on header). Negotiable objects can be used to let the devices agree on
certain values. Non-negotiable objects are used for announcement of certain values. Non-negotiable objects are used for announcement of
specific values that do not need or do not allow negotiation. specific values that do not need or do not allow negotiation.
All values are defined in network byte order (i.e., big-endian byte
order).
The format of the LMP object is as follows: The format of the LMP object is as follows:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|N| C-Type | Class | Length | |N| C-Type | Class | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
// (object contents) // // (object contents) //
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
N: 1 bit N: 1 bit
The N flag indicates if the object is negotiable (N=1) or non- The N flag indicates if the object is negotiable (N=1) or non-
negotiable (N=0). negotiable (N=0).
C-Type: 7 bits C-Type: 7 bits
Class-type, unique within an Object Class. Values are defined Class-type, unique within an Object Class. Values are defined
in Section 14. in Section 13.
Class: 8 bits Class: 8 bits
The Class indicates the object type. Each object has a name, The Class indicates the object type. Each object has a name,
which is always capitalized in this document. which is always capitalized in this document.
Length: 16 bits Length: 16 bits
The Length field indicates the length of the object in bytes, The Length field indicates the length of the object in bytes,
including the N, C-Type, Class, and Length fields. including the N, C-Type, Class, and Length fields.
13.3. Parameter Negotiation Messages 12.3. Parameter Negotiation Messages
13.3.1. Config Message (Msg Type = 1) 12.3.1. Config Message (Msg Type = 1)
The Config message is used in the control channel negotiation phase The Config message is used in the control channel negotiation phase
of LMP. The contents of the Config message are built using LMP of LMP. The contents of the Config message are built using LMP
objects. The format of the Config message is as follows: objects. The format of the Config message is as follows:
<Config Message> ::= <Common Header> <LOCAL_CCID> <MESSAGE_ID> <Config Message> ::= <Common Header> <LOCAL_CCID> <MESSAGE_ID>
<LOCAL_NODE_ID> <CONFIG> <LOCAL_NODE_ID> <CONFIG>
The above transmission order SHOULD be followed. The above transmission order SHOULD be followed.
The MESSAGE_ID is within the scope of the CCID. The MESSAGE_ID object is within the scope of the LOCAL_CCID object.
The Config message MUST be periodically transmitted until (1) it The Config message MUST be periodically transmitted until (1) it
receives a ConfigAck or ConfigNack message, (2) a timeout expires receives a ConfigAck or ConfigNack message, (2) a retry limit has
and no ConfigAck or ConfigNack message has been received, or (3) it been reached and no ConfigAck or ConfigNack message has been
receives a Config message from the remote node and has lost the received, or (3) it receives a Config message from the remote node
contention (e.g., the Node Id of the remote node is higher than the and has lost the contention (e.g., the Node_Id of the remote node is
Node Id of the local node). Both the retransmission interval and the higher than the Node_Id of the local node). Both the retransmission
timeout period are local configuration parameters. interval and the retry limit are local configuration parameters.
13.3.2. ConfigAck Message (Msg Type = 2) 12.3.2. ConfigAck Message (Msg Type = 2)
The ConfigAck message is used to acknowledge receipt of the Config The ConfigAck message is used to acknowledge receipt of the Config
message and indicate agreement on all parameters. message and indicate agreement on all parameters.
<ConfigAck Message> ::= <Common Header> <LOCAL_CCID> <LOCAL_NODE_ID> <ConfigAck Message> ::= <Common Header> <LOCAL_CCID> <LOCAL_NODE_ID>
<REMOTE_CCID> <MESSAGE_ID_ACK> <REMOTE_CCID> <MESSAGE_ID_ACK>
<REMOTE_NODE_ID> <REMOTE_NODE_ID>
The above transmission order SHOULD be followed. The above transmission order SHOULD be followed.
The contents of the REMOTE_CCID, MESSAGE_ID_ACK, and REMOTE_NODE_ID The contents of the REMOTE_CCID, MESSAGE_ID_ACK, and REMOTE_NODE_ID
objects MUST be obtained from the Config message being acknowledged. objects MUST be obtained from the Config message being acknowledged.
13.3.3. ConfigNack Message (Msg Type = 3) 12.3.3. ConfigNack Message (Msg Type = 3)
The ConfigNack message is used to acknowledge receipt of the Config The ConfigNack message is used to acknowledge receipt of the Config
message and indicate disagreement on non-negotiable parameters or message and indicate disagreement on non-negotiable parameters or
propose other values for negotiable parameters. Parameters where propose other values for negotiable parameters. Parameters where
agreement was reached MUST NOT be included in the ConfigNack agreement was reached MUST NOT be included in the ConfigNack
Message. The format of the ConfigNack message is as follows: Message. The format of the ConfigNack message is as follows:
<ConfigNack Message> ::= <Common Header> <LOCAL_CCID> <ConfigNack Message> ::= <Common Header> <LOCAL_CCID>
<LOCAL_NODE_ID> <REMOTE_CCID> <LOCAL_NODE_ID> <REMOTE_CCID>
<MESSAGE_ID_ACK> <REMOTE_NODE_ID> <CONFIG> <MESSAGE_ID_ACK> <REMOTE_NODE_ID> <CONFIG>
skipping to change at page 39, line 11 skipping to change at page 41, line 11
If the ConfigNack message includes CONFIG objects for non-negotiable If the ConfigNack message includes CONFIG objects for non-negotiable
parameters, they MUST be copied from the CONFIG objects received in parameters, they MUST be copied from the CONFIG objects received in
the Config message. the Config message.
If the ConfigNack message is received and only includes CONFIG If the ConfigNack message is received and only includes CONFIG
objects that are negotiable, then a new Config message SHOULD be objects that are negotiable, then a new Config message SHOULD be
sent. The values in the CONFIG object of the new Config message sent. The values in the CONFIG object of the new Config message
SHOULD take into account the acceptable values included in the SHOULD take into account the acceptable values included in the
ConfigNack message. ConfigNack message.
13.4. Hello Message (Msg Type = 4) 12.4. Hello Message (Msg Type = 4)
The format of the Hello message is as follows: The format of the Hello message is as follows:
<Hello Message> ::= <Common Header> <LOCAL_CCID> <HELLO> <Hello Message> ::= <Common Header> <LOCAL_CCID> <HELLO>
The above transmission order SHOULD be followed. The above transmission order SHOULD be followed.
The Hello message MUST be periodically transmitted at least once The Hello message MUST be periodically transmitted at least once
every HelloInterval msec. If no Hello message is received within the every HelloInterval msec. If no Hello message is received within
HelloDeadInterval, the control channel is assumed to have failed. the HelloDeadInterval, the control channel is assumed to have
failed.
13.5. Link Verification 12.5. Link Verification Messages
13.5.1. BeginVerify Message (Msg Type = 5) 12.5.1. BeginVerify Message (Msg Type = 5)
The BeginVerify message is sent over the control channel and is used The BeginVerify message is sent over the control channel and is used
to initiate the link verification process. The format is as follows: to initiate the link verification process. The format is as
follows:
<BeginVerify Message> ::= <Common Header> <LOCAL_LINK_ID> <BeginVerify Message> ::= <Common Header> <LOCAL_LINK_ID>
<MESSAGE_ID> [<REMOTE_LINK_ID>] <MESSAGE_ID> [<REMOTE_LINK_ID>]
<BEGIN_VERIFY> <BEGIN_VERIFY>
The above transmission order SHOULD be followed. The above transmission order SHOULD be followed.
To limit the scope of Link Verification to a particular TE Link, the To limit the scope of Link Verification to a particular TE Link, the
LOCAL_LINK_ID MUST be non-zero. If this field is zero, the data Link_Id field of the LOCAL_LINK_ID object MUST be non-zero. If this
links can span multiple TE links and/or they may comprise a TE link field is zero, the data links can span multiple TE links and/or they
that is yet to be configured. In the special case where the may comprise a TE link that is yet to be configured. In the special
LOCAL_LINK_ID field is zero, the "Verify all Links" flag of the case where the local Link_Id field is zero, the "Verify all Links"
BEGIN_VERIFY object is used to distinguish between data links that flag of the BEGIN_VERIFY object is used to distinguish between data
span multiple TE links and those that have not yet been assigned to links that span multiple TE links and those that have not yet been
a TE link. assigned to a TE link (see Section 5).
The REMOTE_LINK_ID may be included if the local/remote Link Id The REMOTE_LINK_ID object may be included if the local/remote
mapping is known. Link_Id mapping is known.
The REMOTE_LINK_ID MUST be non-zero if included. The Link_Id field of the REMOTE_LINK_ID object MUST be non-zero if
included.
The BeginVerify message MUST be periodically transmitted until (1) The BeginVerify message MUST be periodically transmitted until (1)
the node receives either a BeginVerifyAck or BeginVerifyNack message the node receives either a BeginVerifyAck or BeginVerifyNack message
to accept or reject the verify process or (2) a timeout expires and to accept or reject the verify process or (2) a retry limit has been
no BeginVerifyAck or BeginVerifyNack message has been received. Both reached and no BeginVerifyAck or BeginVerifyNack message has been
the retransmission interval and the timeout period are local received. Both the retransmission interval and the retry limit are
configuration parameters. local configuration parameters.
13.5.2. BeginVerifyAck Message (Msg Type = 6) 12.5.2. BeginVerifyAck Message (Msg Type = 6)
When a BeginVerify message is received and Test messages are ready When a BeginVerify message is received and Test messages are ready
to be processed, a BeginVerifyAck message MUST be transmitted. to be processed, a BeginVerifyAck message MUST be transmitted.
<BeginVerifyAck Message> ::= <Common Header> [<LOCAL_LINK_ID>] <BeginVerifyAck Message> ::= <Common Header> [<LOCAL_LINK_ID>]
<MESSAGE_ID_ACK> <BEGIN_VERIFY_ACK> <MESSAGE_ID_ACK> <BEGIN_VERIFY_ACK>
<VERIFY_ID> <VERIFY_ID>
The above transmission order SHOULD be followed. The above transmission order SHOULD be followed.
The LOCAL_LINK_ID may be included if the local/remote Link Id The LOCAL_LINK_ID object may be included if the local/remote Link_Id
mapping is known or learned through the BeginVerify message. mapping is known or learned through the BeginVerify message.
The LOCAL_LINK_ID MUST be non-zero if included. The Link_Id field of the LOCAL_LINK_ID MUST be non-zero if included.
The contents of the MESSAGE_ID_ACK object MUST be obtained from the The contents of the MESSAGE_ID_ACK object MUST be obtained from the
BeginVerify message being acknowledged. BeginVerify message being acknowledged.
The VERIFY_ID object contains a node-unique value that is assigned The VERIFY_ID object contains a node-unique value that is assigned
by the generator of the BeginVerifyAck message. This value is used by the generator of the BeginVerifyAck message. This value is used
to uniquely identify the Verification process from multiple LMP to uniquely identify the Verification process from multiple LMP
neighbors and/or parallel Test procedures between the same LMP neighbors and/or parallel Test procedures between the same LMP
neighbors. neighbors.
13.5.3. BeginVerifyNack Message (Msg Type = 7) 12.5.3. BeginVerifyNack Message (Msg Type = 7)
If a BeginVerify message is received and a node is unwilling or If a BeginVerify message is received and a node is unwilling or
unable to begin the Verification procedure, a BeginVerifyNack unable to begin the Verification procedure, a BeginVerifyNack
message MUST be transmitted. message MUST be transmitted.
<BeginVerifyNack Message> ::= <Common Header> [<LOCAL_LINK_ID>] <BeginVerifyNack Message> ::= <Common Header> [<LOCAL_LINK_ID>]
<MESSAGE_ID_ACK> <ERROR_CODE> <MESSAGE_ID_ACK> <ERROR_CODE>
The above transmission order SHOULD be followed. The above transmission order SHOULD be followed.
skipping to change at page 41, line 6 skipping to change at page 43, line 6
indicate "Link Verification Procedure not supported". indicate "Link Verification Procedure not supported".
If Verification is supported, but the node unable to begin the If Verification is supported, but the node unable to begin the
procedure, the ERROR_CODE MUST indicate "Unwilling to verify". If a procedure, the ERROR_CODE MUST indicate "Unwilling to verify". If a
BeginVerifyNack message is received with such an ERROR_CODE, the BeginVerifyNack message is received with such an ERROR_CODE, the
node that originated the BeginVerify SHOULD schedule a BeginVerify node that originated the BeginVerify SHOULD schedule a BeginVerify
retransmission after Rf seconds, where Rf is a locally defined retransmission after Rf seconds, where Rf is a locally defined
parameter. parameter.
If the Verification Transport mechanism is not supported, the If the Verification Transport mechanism is not supported, the
ERROR_CODE MUST indicate "Unsupported verification transport ERROR_CODE MUST indicate, "Unsupported verification transport
mechanism". mechanism".
If remote configuration of the TE Link Id is not supported and the If remote configuration of the Link_Id is not supported and the
REMOTE_LINK_ID object (included in the BeginVerify message) does not contents of the REMOTE_LINK_ID object (included in the BeginVerify
match any configured values, the ERROR_CODE MUST indicate "TE Link message) does not match any configured values, the ERROR_CODE MUST
Id configuration error". indicate "Link_Id configuration error".
The BeginVerifyNack uses BEGIN_VERIFY_ERROR_ C-Type 1.
13.5.4. EndVerify Message (Msg Type = 8) 12.5.4. EndVerify Message (Msg Type = 8)
The EndVerify message is sent over the control channel and is used The EndVerify message is sent over the control channel and is used
to terminate the link verification process. The EndVerify message to terminate the link verification process. The EndVerify message
may be sent at any time the initiating node desires to end the may be sent at any time the initiating node desires to end the
Verify procedure. The format is as follows: Verify procedure. The format is as follows:
<EndVerify Message> ::= <Common Header> <MESSAGE_ID> <VERIFY_ID> <EndVerify Message> ::= <Common Header> <MESSAGE_ID> <VERIFY_ID>
The above transmission order SHOULD be followed. The above transmission order SHOULD be followed.
The EndVerify message will be periodically transmitted until (1) an The EndVerify message will be periodically transmitted until (1) an
EndVerifyAck message has been received or (2) a timeout expires and EndVerifyAck message has been received or (2) a retry limit has been
no EndVerifyAck message has been received. Both the retransmission reached and no EndVerifyAck message has been received. Both the
interval and the timeout period are local configuration parameters. retransmission interval and the retry limit are local configuration
parameters.
13.5.5. EndVerifyAck Message (Msg Type =9) 12.5.5. EndVerifyAck Message (Msg Type =9)
The EndVerifyAck message is sent over the control channel and is The EndVerifyAck message is sent over the control channel and is
used to acknowledge the termination of the link verification used to acknowledge the termination of the link verification
process. The format is as follows: process. The format is as follows:
<EndVerifyAck Message> ::= <Common Header> <MESSAGE_ID_ACK> <EndVerifyAck Message> ::= <Common Header> <MESSAGE_ID_ACK>
<VERIFY_ID> <VERIFY_ID>
The above transmission order SHOULD be followed. The above transmission order SHOULD be followed.
The contents of the MESSAGE_ID_ACK object MUST be obtained from the The contents of the MESSAGE_ID_ACK object MUST be obtained from the
EndVerify message being acknowledged. EndVerify message being acknowledged.
13.5.6. Test Message (Msg Type = 10) 12.5.6. Test Message (Msg Type = 10)
The Test message is transmitted over the data link and is used to The Test message is transmitted over the data link and is used to
verify its physical connectivity. Unless explicitly stated in the verify its physical connectivity. Unless explicitly stated, these
Verify Transport Mechanism description for the BEGIN_VERIFY class, messages MUST be transmitted over UDP like all other LMP messages.
this is transmitted as an IP packet with payload format as follows: The format of the Test messages is as follows:
<Test Message> ::= <Common Header> <LOCAL_INTERFACE_ID> <VERIFY_ID> <Test Message> ::= <Common Header> <LOCAL_INTERFACE_ID> <VERIFY_ID>
The above transmission order SHOULD be followed. The above transmission order SHOULD be followed.
Note that this message is sent over a data link and NOT over the Note that this message is sent over a data link and NOT over the
control channel. The transport mechanism for the Test message is control channel. The transport mechanism for the Test message is
negotiated using Verify Transport Mechanism field of the negotiated using Verify Transport Mechanism field of the
BEGIN_VERIFY object and the Verify Transport Response field of the BEGIN_VERIFY object and the Verify Transport Response field of the
BEGIN_VERIFY_ACK object (see Sections 14.8 and 14.9). BEGIN_VERIFY_ACK object (see Sections 13.8 and 13.9).
The local (transmitting) node sends a given Test message The local (transmitting) node sends a given Test message
periodically (at least once every VerifyInterval ms) on the periodically (at least once every VerifyInterval ms) on the
corresponding data link until (1) it receives a correlating corresponding data link until (1) it receives a correlating
TestStatusSuccess or TestStatusFailure message on the control TestStatusSuccess or TestStatusFailure message on the control
channel from the remote (receiving) node or (2) all active control channel from the remote (receiving) node or (2) all active control
channels between the two nodes have failed. The remote node will channels between the two nodes have failed. The remote node will
send a given TestStatus message periodically over the control send a given TestStatus message periodically over the control
channel until it receives either a correlating TestStatusAck message channel until it receives either a correlating TestStatusAck message
or an EndVerify message is received over the control channel. or an EndVerify message is received over the control channel.
13.5.7. TestStatusSuccess Message (Msg Type = 11) 12.5.7. TestStatusSuccess Message (Msg Type = 11)
The TestStatusSuccess message is transmitted over the control The TestStatusSuccess message is transmitted over the control
channel and is used to transmit the mapping between the local channel and is used to transmit the mapping between the local
Interface Id and the Interface Id that was received in the Test Interface_Id and the Interface_Id that was received in the Test
message. message.
<TestStatusSuccess Message> ::= <Common Header> <LOCAL_LINK_ID> <TestStatusSuccess Message> ::= <Common Header> <LOCAL_LINK_ID>
<MESSAGE_ID> <LOCAL_INTERFACE_ID> <MESSAGE_ID> <LOCAL_INTERFACE_ID>
<REMOTE_INTERFACE_ID> <VERIFY_ID> <REMOTE_INTERFACE_ID> <VERIFY_ID>
The above transmission order SHOULD be followed. The above transmission order SHOULD be followed.
The contents of the REMOTE_INTERFACE_ID object MUST be obtained from The contents of the REMOTE_INTERFACE_ID object MUST be obtained from
the corresponding Test message being positively acknowledged. the corresponding Test message being positively acknowledged.
13.5.8. TestStatusFailure Message (Msg Type = 12) 12.5.8. TestStatusFailure Message (Msg Type = 12)
The TestStatusFailure message is transmitted over the control The TestStatusFailure message is transmitted over the control
channel and is used to indicate that the Test message was not channel and is used to indicate that the Test message was not
received. received.
<TestStatusFailure Message> ::= <Common Header> <MESSAGE_ID> <TestStatusFailure Message> ::= <Common Header> <MESSAGE_ID>
<VERIFY_ID> <VERIFY_ID>
The above transmission order SHOULD be followed. The above transmission order SHOULD be followed.
13.5.9. TestStatusAck Message (Msg Type = 13) 12.5.9. TestStatusAck Message (Msg Type = 13)
The TestStatusAck message is used to acknowledge receipt of the The TestStatusAck message is used to acknowledge receipt of the
TestStatusSuccess or TestStatusFailure messages. TestStatusSuccess or TestStatusFailure messages.
<TestStatusAck Message> ::= <Common Header> <MESSAGE_ID_ACK> <TestStatusAck Message> ::= <Common Header> <MESSAGE_ID_ACK>
<VERIFY_ID> <VERIFY_ID>
The above transmission order SHOULD be followed. The above transmission order SHOULD be followed.
The contents of the MESSAGE_ID_ACK object MUST be obtained from the The contents of the MESSAGE_ID_ACK object MUST be obtained from the
TestStatusSuccess or TestStatusFailure message being acknowledged. TestStatusSuccess or TestStatusFailure message being acknowledged.
13.6. Link Summary Messages 12.6. Link Summary Messages
13.6.1. LinkSummary Message (Msg Type = 14) 12.6.1. LinkSummary Message (Msg Type = 14)
The LinkSummary message is used to synchronize the Interface Ids and The LinkSummary message is used to synchronize the Interface_Ids and
correlate the properties of the TE link. The format of the correlate the properties of the TE link. The format of the
LinkSummary message is as follows: LinkSummary message is as follows:
<LinkSummary Message> ::= <Common Header> <MESSAGE_ID> <TE_LINK> <LinkSummary Message> ::= <Common Header> <MESSAGE_ID> <TE_LINK>
<DATA_LINK> [<DATA_LINK>...] <DATA_LINK> [<DATA_LINK>...]
The above transmission order SHOULD be followed. The above transmission order SHOULD be followed.
The LinkSummary message can be exchanged at any time a link is not The LinkSummary message can be exchanged at any time a link is not
in the Verification process. The LinkSummary message MUST be in the Verification process. The LinkSummary message MUST be
periodically transmitted until (1) the node receives a periodically transmitted until (1) the node receives a
LinkSummaryAck or LinkSummaryNack message or (2) a timeout expires LinkSummaryAck or LinkSummaryNack message or (2) a retry limit has
and no LinkSummaryAck or LinkSummaryNack message has been received. been reached and no LinkSummaryAck or LinkSummaryNack message has
Both the retransmission interval and the timeout period are local been received. Both the retransmission interval and the retry limit
configuration parameters. are local configuration parameters.
13.6.2. LinkSummaryAck Message (Msg Type = 15) 12.6.2. LinkSummaryAck Message (Msg Type = 15)
The LinkSummaryAck message is used to indicate agreement on the The LinkSummaryAck message is used to indicate agreement on the
Interface Id synchronization and acceptance/agreement on all the Interface_Id synchronization and acceptance/agreement on all the
link parameters. It is on the reception of this message that the link parameters. It is on the reception of this message that the
local node makes the TE Link Id associations. local node makes the Link_Id associations.
<LinkSummaryAck Message> ::= <Common Header> <MESSAGE_ID_ACK> <LinkSummaryAck Message> ::= <Common Header> <MESSAGE_ID_ACK>
The above transmission order SHOULD be followed. The above transmission order SHOULD be followed.
13.6.3. LinkSummaryNack Message (Msg Type = 16) 12.6.3. LinkSummaryNack Message (Msg Type = 16)
The LinkSummaryNack message is used to indicate disagreement on non- The LinkSummaryNack message is used to indicate disagreement on non-
negotiated parameters or propose other values for negotiable negotiated parameters or propose other values for negotiable
parameters. Parameters where agreement was reached MUST NOT be parameters. Parameters where agreement was reached MUST NOT be
included in the LinkSummaryNack message. included in the LinkSummaryNack message.
<LinkSummaryNack Message> ::= <Common Header> <MESSAGE_ID_ACK> <LinkSummaryNack Message> ::= <Common Header> <MESSAGE_ID_ACK>
<ERROR_CODE> [<DATA_LINK>...] <ERROR_CODE> [<DATA_LINK>...]
The above transmission order SHOULD be followed. The above transmission order SHOULD be followed.
The DATA_LINK objects MUST include acceptable values for all The DATA_LINK objects MUST include acceptable values for all
negotiable parameters. If the LinkSummaryNack includes DATA_LINK negotiable parameters. If the LinkSummaryNack includes DATA_LINK
objects for non-negotiable parameters, they MUST be copied from the objects for non-negotiable parameters, they MUST be copied from the
DATA_LINK objects received in the LinkSummary message. DATA_LINK objects received in the LinkSummary message.
If the LinkSummaryNack message is received and only includes If the LinkSummaryNack message is received and only includes
negotiable parameters, then a new LinkSummary message SHOULD be negotiable parameters, then a new LinkSummary message SHOULD be
sent. The values received in the new LinkSummary message SHOULD take sent. The values received in the new LinkSummary message SHOULD
into account the acceptable parameters included in the take into account the acceptable parameters included in the
LinkSummaryNack message. LinkSummaryNack message.
The LinkSummaryNack message uses LINK_SUMMARY_ERROR C-Type 2. 12.7. Fault Management Messages
13.7. Fault Management Messages
13.7.1. ChannelStatus Message (Msg Type = 17) 12.7.1. ChannelStatus Message (Msg Type = 17)
The ChannelStatus message is sent over the control channel and is The ChannelStatus message is sent over the control channel and is
used to notify an LMP neighbor of the status of a data link. A node used to notify an LMP neighbor of the status of a data link. A node
that receives a ChannelStatus message MUST respond with a that receives a ChannelStatus message MUST respond with a
ChannelStatusAck message. The format is as follows: ChannelStatusAck message. The format is as follows:
<ChannelStatus Message> ::= <Common Header> <LOCAL_LINK_ID> <ChannelStatus Message> ::= <Common Header> <LOCAL_LINK_ID>
<MESSAGE_ID> <CHANNEL_STATUS> <MESSAGE_ID> <CHANNEL_STATUS>
The above transmission order SHOULD be followed. The above transmission order SHOULD be followed.
If the CHANNEL_STATUS object does not include any Interface Ids, If the CHANNEL_STATUS object does not include any Interface_Ids,
then this indicates the entire TE Link has failed. then this indicates the entire TE Link has failed.
13.7.2. ChannelStatusAck Message (Msg Type = 18) 12.7.2. ChannelStatusAck Message (Msg Type = 18)
The ChannelStatusAck message is used to acknowledge receipt of the The ChannelStatusAck message is used to acknowledge receipt of the
ChannelStatus Message. The format is as follows: ChannelStatus Message. The format is as follows:
<ChannelStatusAck Message> ::= <Common Header> <MESSAGE_ID_ACK> <ChannelStatusAck Message> ::= <Common Header> <MESSAGE_ID_ACK>
The above transmission order SHOULD be followed. The above transmission order SHOULD be followed.
The contents of the MESSAGE_ID_ACK object MUST be obtained from the The contents of the MESSAGE_ID_ACK object MUST be obtained from the
ChannelStatus message being acknowledged. ChannelStatus message being acknowledged.
13.7.3. ChannelStatusRequest Message (Msg Type = 19) 12.7.3. ChannelStatusRequest Message (Msg Type = 19)
The ChannelStatusRequest message is sent over the control channel The ChannelStatusRequest message is sent over the control channel
and is used to request the status of one or more data link(s). A and is used to request the status of one or more data link(s). A
node that receives a ChannelStatusRequest message MUST respond with node that receives a ChannelStatusRequest message MUST respond with
a ChannelStatusResponse message. The format is as follows: a ChannelStatusResponse message. The format is as follows:
<ChannelStatusRequest Message> ::= <Common Header> <LOCAL_LINK_ID> <ChannelStatusRequest Message> ::= <Common Header> <LOCAL_LINK_ID>
<MESSAGE_ID> <MESSAGE_ID>
[<CHANNEL_STATUS_REQUEST>] [<CHANNEL_STATUS_REQUEST>]
The above transmission order SHOULD be followed. The above transmission order SHOULD be followed.
If the CHANNEL_STATUS_REQUEST object is not included, then the If the CHANNEL_STATUS_REQUEST object is not included, then the
ChannelStatusRequest is being used to request the status of ALL of ChannelStatusRequest is being used to request the status of ALL of
the data link(s) of the TE Link. the data link(s) of the TE Link.
13.7.4. ChannelStatusResponse Message (Msg Type = 20) 12.7.4. ChannelStatusResponse Message (Msg Type = 20)
The ChannelStatusResponse message is used to acknowledge receipt of The ChannelStatusResponse message is used to acknowledge receipt of
the ChannelStatusRequest Message and notify the LMP neighbor of the the ChannelStatusRequest Message and notify the LMP neighbor of the
status of the data channel(s). The format is as follows: status of the data channel(s). The format is as follows:
<ChannelStatusResponse Message> ::= <Common Header> <MESSAGE_ID_ACK> <ChannelStatusResponse Message> ::= <Common Header> <MESSAGE_ID_ACK>
<CHANNEL_STATUS> <CHANNEL_STATUS>
The above transmission order SHOULD be followed. The above transmission order SHOULD be followed.
The contents of the MESSAGE_ID_ACK objects MUST be obtained from the The contents of the MESSAGE_ID_ACK objects MUST be obtained from the
ChannelStatusRequest message being acknowledged. ChannelStatusRequest message being acknowledged.
14. LMP Object Definitions 13. LMP Object Definitions
14.1. CCID (Control Channel ID) Class 13.1. CCID (Control Channel ID) Class
Class = 1. Class = 1.
o C-Type = 1, LOCAL_CCID o C-Type = 1, LOCAL_CCID
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CC_Id | | CC_Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 46, line 7 skipping to change at page 48, line 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CC_Id | | CC_Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
CC_Id: 32 bits CC_Id: 32 bits
This identifies the remote node∆s CC_Id and MUST be non-zero. This identifies the remote node∆s CC_Id and MUST be non-zero.
This object is non-negotiable. This object is non-negotiable.
14.2. NODE_ID Classes 13.2. NODE_ID Class
Class = 2. Class = 2.
o C-Type = 1, LOCAL_NODE_ID Class o C-Type = 1, LOCAL_NODE_ID
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Node_Id (4 bytes) | | Node_Id (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Node_Id: Node_Id:
This identities the node that originated the LMP packet. This identities the node that originated the LMP packet.
This object is non-negotiable. This object is non-negotiable.
o C-Type = 2, REMOTE_NODE_ID Class o C-Type = 2, REMOTE_NODE_ID
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Node_Id (4 bytes) | | Node_Id (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Node_Id: Node_Id:
This identities the remote node. This identities the remote node.
This object is non-negotiable. This object is non-negotiable.
14.3. LINK _ID Class 13.3. LINK_ID Class
Class = 3 Class = 3
o C-Type = 1, IPv4 LOCAL_LINK_ID o C-Type = 1, IPv4 LOCAL_LINK_ID
o C-Type = 2, IPv4 REMOTE_LINK_ID o C-Type = 2, IPv4 REMOTE_LINK_ID
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 47, line 26 skipping to change at page 49, line 26
o C-Type = 5, Unnumbered LOCAL_LINK_ID o C-Type = 5, Unnumbered LOCAL_LINK_ID
o C-Type = 6, Unnumbered REMOTE_LINK_ID o C-Type = 6, Unnumbered REMOTE_LINK_ID
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link_Id (4 bytes) | | Link_Id (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o C-Type = 7, Reserved for OIF
o C-Type = 8, Reserved for OIF
Link_Id: Link_Id:
For LOCAL_LINK_ID, this identifies the sender∆s Link associated For LOCAL_LINK_ID, this identifies the sender∆s Link associated
with the message. with the message. This value MUST be non-zero.
For REMOTE_LINK_ID, this identifies the remote node∆s Link Id For REMOTE_LINK_ID, this identifies the remote node∆s Link_Id
and MUST be non-zero. and MUST be non-zero.
This object is non-negotiable. This object is non-negotiable.
14.4. INTERFACE_ID Class 13.4. INTERFACE_ID Class
Class = 4 Class = 4
o C-Type = 1, IPv4 LOCAL_INTERFACE_ID o C-Type = 1, IPv4 LOCAL_INTERFACE_ID
o C-Type = 2, IPv4 REMOTE_INTERFACE_ID o C-Type = 2, IPv4 REMOTE_INTERFACE_ID
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface_Id (4 bytes) | | Interface_Id (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o C-Type = 3, IPv6 LOCAL_INTERFACE_ID o C-Type = 3, IPv6 LOCAL_INTERFACE_ID
o C-Type = 4, IPv6 REMOTE_INTERFACE_ID
o C-Type = 4, IPv6 REMOTE_INTERFACE_ID
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ + + +
| | | |
+ Interface_Id (16 bytes) + + Interface_Id (16 bytes) +
| | | |
+ + + +
| | | |
skipping to change at page 48, line 30 skipping to change at page 50, line 28
o C-Type = 6, Unnumbered REMOTE_INTERFACE_ID o C-Type = 6, Unnumbered REMOTE_INTERFACE_ID
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface_Id (4 bytes) | | Interface_Id (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Interface_Id: Interface_Id:
For the LOCAL_INTERFACE_ID, this identifies the data link For the LOCAL_INTERFACE_ID, this identifies the data link.
(either port or component link). This value MUST be node-wide This value MUST be node-wide unique and non-zero.
unique and non-zero.
For the REMOTE_INTERFACE_ID, this identifies the remote node∆s For the REMOTE_INTERFACE_ID, this identifies the remote node∆s
data link (either port or component link). The Interface Id data link. The Interface_Id MUST be non-zero.
MUST be non-zero.
This object is non-negotiable. This object is non-negotiable.
14.5. MESSAGE_ID Class 13.5. MESSAGE_ID Class
Class = 5. Class = 5.
o C-Type=1, MessageId o C-Type=1, MessageId
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message_Id | | Message_Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Message_Id: Message_Id:
The Message_Id field is used to identify a message. This value The Message_Id field is used to identify a message. This value
is incremented and only decreases when the value wraps. This is is incremented and only decreases when the value wraps. This
used for message acknowledgment. is used for message acknowledgment.
This object is non-negotiable. This object is non-negotiable.
o C-Type = 2, MessageIdAck o C-Type = 2, MessageIdAck
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message_Id | | Message_Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Message_Id: Message_Id:
The Message_Id field is used to identify the message being The Message_Id field is used to identify the message being
acknowledged. This value is copied from the MESSAGE_ID object acknowledged. This value is copied from the MESSAGE_ID object
of the message being acknowledged. of the message being acknowledged.
This object is non-negotiable. This object is non-negotiable.
14.6. CONFIG Class 13.6. CONFIG Class
Class = 6. Class = 6.
o C-Type = 1, HelloConfig o C-Type = 1, HelloConfig
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| HelloInterval | HelloDeadInterval | | HelloInterval | HelloDeadInterval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 49, line 55 skipping to change at page 51, line 49
If no Hello packets are received within the HelloDeadInterval, If no Hello packets are received within the HelloDeadInterval,
the control channel is assumed to have failed. The the control channel is assumed to have failed. The
HelloDeadInterval is measured in milliseconds (ms). The HelloDeadInterval is measured in milliseconds (ms). The
HelloDeadInterval MUST be greater than the HelloInterval, and HelloDeadInterval MUST be greater than the HelloInterval, and
SHOULD be at least 3 times the value of HelloInterval. SHOULD be at least 3 times the value of HelloInterval.
If the fast keep-alive mechanism of LMP is not used, the If the fast keep-alive mechanism of LMP is not used, the
HelloInterval and HelloDeadInterval MUST be set to zero. HelloInterval and HelloDeadInterval MUST be set to zero.
14.7. HELLO Class 13.7. HELLO Class
Class = 7 Class = 7
o C-Type = 1, Hello o C-Type = 1, Hello
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TxSeqNum | | TxSeqNum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RcvSeqNum | | RcvSeqNum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TxSeqNum: 32 bits TxSeqNum: 32 bits
skipping to change at page 50, line 25 skipping to change at page 52, line 21
TxSeqNum: 32 bits TxSeqNum: 32 bits
This is the current sequence number for this Hello message. This is the current sequence number for this Hello message.
This sequence number will be incremented when the sequence This sequence number will be incremented when the sequence
number is reflected in the RcvSeqNum of a Hello packet that is number is reflected in the RcvSeqNum of a Hello packet that is
received over the control channel. received over the control channel.
TxSeqNum=0 is not allowed. TxSeqNum=0 is not allowed.
TxSeqNum=1 is reserved to indicate that the control channel has TxSeqNum=1 is used to indicate that the this is the first Hello
booted or restarted. message sent over the control channel.
RcvSeqNum: 32 bits RcvSeqNum: 32 bits
This is the sequence number of the last Hello message received This is the sequence number of the last Hello message received
over the control channel. RcvSeqNum=0 is reserved to indicate over the control channel. RcvSeqNum=0 is used to indicate that
that a Hello message has not yet been received. a Hello message has not yet been received.
This object is non-negotiable. This object is non-negotiable.
14.8. BEGIN_VERIFY Class 13.8. BEGIN_VERIFY Class
Class = 8. Class = 8.
o C-Type = 1 o C-Type = 1
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | VerifyInterval | | Flags | VerifyInterval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of Data Links | | Number of Data Links |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| EncType | (Reserved) | Verify Transport Mechanism | | EncType | (Reserved) | Verify Transport Mechanism |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TransmissionRate | | TransmissionRate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Wavelength | | Wavelength |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Reserved field should be sent as zero and ignored on receipt.
Flags: 16 bits Flags: 16 bits
The following flags are defined: The following flags are defined:
0x01 Verify all Links 0x01 Verify all Links
If this bit is set, the verification process checks all If this bit is set, the verification process checks all
unallocated links; else it only verifies new ports or unallocated links; else it only verifies new ports or
component links that are to be added to this TE link. component links that are to be added to this TE link.
0x02 Data Link Type 0x02 Data Link Type
If set, the data links to be verified are ports, If set, the data links to be verified are ports,
skipping to change at page 51, line 27 skipping to change at page 53, line 28
This is the interval between successive Test messages and is This is the interval between successive Test messages and is
measured in milliseconds (ms). measured in milliseconds (ms).
Number of Data Links: 32 bits Number of Data Links: 32 bits
This is the number of data links that will be verified. This is the number of data links that will be verified.
EncType: 8 bits EncType: 8 bits
This is the encoding type of the data link. The defined EncType This is the encoding type of the data link. The defined
values are consistent with the Link Encoding Type values of EncType values are consistent with the LSP Encoding Type values
[GMPLS-SIG] of [GMPLS-SIG].
Verify Transport Mechanism: 16 bits Verify Transport Mechanism: 16 bits
This defines the transport mechanism for the Test Messages. The This defines the transport mechanism for the Test Messages.
scope of this bit mask is restricted to each link encoding The scope of this bit mask is restricted to each LSP encoding
type. The local node will set the bits corresponding to the type. The local node will set the bits corresponding to the
various mechanisms it can support for transmitting LMP test various mechanisms it can support for transmitting LMP test
messages. The receiver chooses the appropriate mechanism in the messages. The receiver chooses the appropriate mechanism in
BeginVerifyAck message. the BeginVerifyAck message.
For SONET/SDH Encoding Type, the following flags are defined:
0x01 J0-16: 16 byte J0 Test Message
Capable of transmitting Test messages using J0 overhead
bytes with string length of 16 bytes (with CRC-7). See
table 4 of ITU G.707 [G707] for the 16-byte J0
definition. The definition of CRC-7 is found in Annex B
of ITU G.707.
Note that Due to the byte limitation, the Test message
is NOT sent as an IP packet and as such, no L2
encapsulation is used. A special Test message format is
defined as follows:
The Test message is a 15-byte message, where the 7 most
significant bits (MSb) of each byte are usable. Due to
the byte limitation, the LMP Header is not included.
The first usable 32 bits MUST be the VerifyId that was
received in the VERIFY_ID object of the BeginVerifyAck
message. The second usable 32 bits MUST be the
Interface_Id. The next usable 8 bits are used to
determine the address type of the Interface_Id. For
IPv4, this value is 1. For unnumbered, this value is 3.
The remaining bits are Reserved.
Note that this Test Message format is only valid when
the Interface_Id is either IPv4 or unnumbered.
0x02 J0-64: 64 byte J0 Test Message
Capable of transmitting Test messages using J0
overhead bytes with string length of 64 bytes (see GR-
253-CORE [GR253]). Note that this is only appropriate
for SONET encoding and not SDH encoding.
The Test message is sent as an IP packet as defined
above.
0x04 DCCS: Test Message over the Section DCC
Capable of transmitting Test messages using the DCC
Section Overhead bytes with bit-oriented HDLC framing
format.
The Test message is sent as an IP packet as defined
above.
0x08 DCCL: Test Message over the Line DCC
Capable of transmitting Test messages using the DCC
Line Overhead bytes with bit-oriented HDLC framing
format.
The Test message is sent as an IP packet as defined
above.
0x10 Payload: Test Message transmitted in the payload The following flag is defined across all LSP Encoding Types.
All other flags are dependent on the LSP Encoding Type.
Capable of transmitting Test messages in the payload 0x8000 Payload: Test Message transmitted in the payload
using Packet over SONET framing using the encoding type
specified in the EncType field.
Capable of transmitting Test messages in the payload.
The Test message is sent as an IP packet as defined The Test message is sent as an IP packet as defined
above. above.
0x20 GigE:
Capable of transmitting Test messages in the payload
TransmissionRate: 32 bits TransmissionRate: 32 bits
This is the transmission rate of the data link over which the This is the transmission rate of the data link over which the
Test messages will be transmitted. This is expressed in bytes Test messages will be transmitted. This is expressed in bytes
per second and represented in IEEE floating point format. per second and represented in IEEE floating-point format.
Wavelength: 32 bits Wavelength: 32 bits
When a data link is assigned to a port or component link that When a data link is assigned to a port or component link that
is capable of transmitting multiple wavelengths (e.g., a fiber is capable of transmitting multiple wavelengths (e.g., a fiber
or waveband-capable port), it is essential to know which or waveband-capable port), it is essential to know which
wavelength the test messages will be transmitted over. This wavelength the test messages will be transmitted over. This
value corresponds to the wavelength at which the Test messages value corresponds to the wavelength at which the Test messages
will be transmitted over and has local significance. If there will be transmitted over and has local significance. If there
is no ambiguity as to the wavelength over which the message is no ambiguity as to the wavelength over which the message
will be sent, then this value SHOULD be set to 0. will be sent, then this value SHOULD be set to 0.
14.9. BEGIN_VERIFY_ACK Class 13.9. BEGIN_VERIFY_ACK Class
Class = 9. Class = 9.
o C-Type = 1 o C-Type = 1
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VerifyDeadInterval | Verify_Transport_Response | | VerifyDeadInterval | Verify_Transport_Response |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 53, line 54 skipping to change at page 54, line 44
Verify_Transport_Response: 16 bits Verify_Transport_Response: 16 bits
The recipient of the BeginVerify message (and the future The recipient of the BeginVerify message (and the future
recipient of the TEST messages) chooses the transport mechanism recipient of the TEST messages) chooses the transport mechanism
from the various types that are offered by the transmitter of from the various types that are offered by the transmitter of
the Test messages. One and only one bit MUST be set in the the Test messages. One and only one bit MUST be set in the
verification transport response. verification transport response.
This object is non-negotiable. This object is non-negotiable.
14.10. VERIFY_ID Class 13.10. VERIFY_ID Class
Class = 10. Class = 10.
o C-Type = 1 o C-Type = 1
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VerifyId | | Verify_Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Verify_Id: 32 bits
VerifyId: 32 bits
This is used to differentiate Test messages from different TE This is used to differentiate Test messages from different TE
links and/or LMP peers. This is a node-unique value that is links and/or LMP peers. This is a node-unique value that is
assigned by the recipient of the BeginVerify message. assigned by the recipient of the BeginVerify message.
This object is non-negotiable. This object is non-negotiable.
14.11. TE_LINK Class 13.11. TE_LINK Class
Class = 11. Class = 11.
o C-Type = 1, IPv4 TE_LINK o C-Type = 1, IPv4 TE_LINK
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | (Reserved) | | Flags | (Reserved) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 55, line 21 skipping to change at page 56, line 14
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | (Reserved) | | Flags | (Reserved) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local_Link_Id (4 bytes) | | Local_Link_Id (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remote_Link_Id (4 bytes) | | Remote_Link_Id (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o C-Type = 4, Reserved for OIF The Reserved field should be sent as zero and ignored on receipt.
Flags: 8 bits Flags: 8 bits
The following flags are defined. All other values are reserved. The following flags are defined. All other values are reserved
and should be sent as zero and ignored on receipt.
0x01 Fault Management Supported. 0x01 Fault Management Supported.
0x02 Link Verification Supported. 0x02 Link Verification Supported.
Local_Link_Id: Local_Link_Id:
This identifies the node∆s local Link Id and MUST be non-zero. This identifies the node∆s local Link_Id and MUST be non-zero.
Remote_Link_Id: Remote_Link_Id:
This identifies the remote node∆s Link Id and MUST be non-zero. This identifies the remote node∆s Link_Id and MUST be non-zero.
14.12. DATA_LINK Class 13.12. DATA_LINK Class
Class = 12. Class = 12.
o C-Type = 1, IPv4 DATA_LINK o C-Type = 1, IPv4 DATA_LINK
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | (Reserved) | | Flags | (Reserved) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 56, line 50 skipping to change at page 57, line 46
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local_Interface_Id (4 bytes) | | Local_Interface_Id (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remote_Interface_Id (4 bytes) | | Remote_Interface_Id (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
// (Subobjects) // // (Subobjects) //
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Reserved field should be sent as zero and ignored on receipt.
Flags: 8 bits Flags: 8 bits
The following flags are defined. All other values are reserved. The following flags are defined. All other values are reserved
and should be sent as zero and ignored on receipt.
0x01 Interface Type: If set, the data link is a port, 0x01 Interface Type: If set, the data link is a port,
otherwise it is a component link. otherwise it is a component link.
0x02 Allocated Link: If set, the data link is currently 0x02 Allocated Link: If set, the data link is currently
allocated for user traffic. If a single allocated for user traffic. If a single
Interface_Id is used for both the Interface_Id is used for both the
transmit and receive data links, then transmit and receive data links, then
this bit only applies to the transmit this bit only applies to the transmit
interface. interface.
skipping to change at page 57, line 28 skipping to change at page 58, line 28
Remote_Interface_Id: Remote_Interface_Id:
This is the remote identifier of the data link. This MUST be This is the remote identifier of the data link. This MUST be
non-zero. non-zero.
Subobjects Subobjects
The contents of the DATA_LINK object consist of a series of The contents of the DATA_LINK object consist of a series of
variable-length data items called subobjects. The subobjects variable-length data items called subobjects. The subobjects
are defined in section 14.12.1 below. are defined in section 13.12.1 below.
A DATA_LINK object may contain more than one subobject. More than A DATA_LINK object may contain more than one subobject. More than
one subobject of the same Type may appear if multiple capabilities one subobject of the same Type may appear if multiple capabilities
are supported over the data link. are supported over the data link.
14.12.1. Data Link Subobjects 13.12.1. Data Link Subobjects
The contents of the DATA_LINK object include a series of variable- The contents of the DATA_LINK object include a series of variable-
length data items called subobjects. Each subobject has the form: length data items called subobjects. Each subobject has the form:
0 1 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+---------------//------------ -+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+---------------//------------ -+
| Type | Length | (Subobject contents) | | Type | Length | (Subobject contents) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--------------//---------------+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--------------//---------------+
Type: 8 bits Type: 8 bits
The Type indicates the type of contents of the subobject. The Type indicates the type of contents of the subobject.
Currently defined values are: Currently defined values are:
Type = 1, Interface Switching Capability Type = 1, Interface Switching Capability
Type = 2, Wavelength
Length: 8 bits Length: 8 bits
The Length contains the total length of the subobject in bytes, The Length contains the total length of the subobject in bytes,
including the Type and Length fields. The Length MUST be at including the Type and Length fields. The Length MUST be at
least 4, and MUST be a multiple of 4. least 4, and MUST be a multiple of 4.
14.12.1.1. Subobject Type 1: Interface Switching Capability 13.12.1.1. Subobject Type 1: Interface Switching Capability
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 | Length | Switching Cap | EncType | | Type | Length | Switching Cap | EncType |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Minimum Reservable Bandwidth | | Minimum Reservable Bandwidth |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Maximum Reservable Bandwidth | | Maximum Reservable Bandwidth |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Switching Capability: 8 bits Switching Capability: 8 bits
This is used to identify the local Interface Switching This is used to identify the local Interface Switching
Capability of the TE link as defined in [GMPLS-SIG]. Capability of the TE link as defined in [GMPLS-SIG].
EncType: 8 bits EncType: 8 bits
This is the encoding type of the data link. The defined EncType This is the encoding type of the data link. The defined
values are consistent with the Link Encoding Type values of EncType values are consistent with the Link Encoding Type
[GMPLS-SIG]. values of [GMPLS-SIG].
Minimum Reservable Bandwidth: 32 bits Minimum Reservable Bandwidth: 32 bits
This is measured in bytes per second and represented in IEEE This is measured in bytes per second and represented in IEEE
floating point format. floating point format.
Maximum Reservable Bandwidth: 32 bits Maximum Reservable Bandwidth: 32 bits
This is measured in bytes per second and represented in IEEE This is measured in bytes per second and represented in IEEE
floating point format. floating point format.
If the interface only supports a fixed rate, the minimum and maximum If the interface only supports a fixed rate, the minimum and maximum
bandwidth fields are set to the same value. bandwidth fields are set to the same value.
14.12.1.2. Subobject Type 2: Wavelength 13.12.1.2. Subobject Type 2: Wavelength
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 | Length | (Reserved) | | Type | Length | (Reserved) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Wavelength | | Wavelength |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Reserved field should be sent as zero and ignored on receipt.
Wavelength: 32 bits Wavelength: 32 bits
This value indicates the wavelength carried over the port. This value indicates the wavelength carried over the port.
Values used in this field only have significance between two Values used in this field only have significance between two
neighbors. neighbors.
14.13. CHANNEL_STATUS Class 13.13. CHANNEL_STATUS Class
Class = 13 Class = 13
o C-Type = 1, IPv4 INTERFACE_ID o C-Type = 1, IPv4 INTERFACE_ID
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Id (4 bytes) | | Interface_Id (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A| Channel Status | |A|D| Channel Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| : | | : |
// : // // : //
| : | | : |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Id (4 bytes) | | Interface_Id (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A| Channel Status | |A|D| Channel Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o C-Type = 2, IPv6 INTERFACE_ID o C-Type = 2, IPv6 INTERFACE_ID
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ + + +
| | | |
+ Interface Id (16 bytes) + + Interface_Id (16 bytes) +
| | | |
+ + + +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A| Channel Status | |A|D| Channel Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| : | | : |
// : // // : //
| : | | : |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ + + +
| | | |
+ Interface Id (16 bytes) + + Interface_Id (16 bytes) +
| | | |
+ + + +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A| Channel Status | |A|D| Channel Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o C-Type = 3, Unnumbered INTERFACE_ID o C-Type = 3, Unnumbered INTERFACE_ID
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Id (4 bytes) | | Interface_Id (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A| Channel Status | |A|D| Channel Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| : | | : |
// : // // : //
| : | | : |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Id (4 bytes) | | Interface_Id (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A|D| Channel Status | |A|D| Channel_Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Active bit: 1 bit Active bit: 1 bit
This indicates that the Channel is allocated to user traffic and the This indicates that the Channel is allocated to user traffic and the
data link should be actively monitored. data link should be actively monitored.
Direction bit: 1 bit Direction bit: 1 bit
This indicates the direction (transmit/receive) of the data channel This indicates the direction (transmit/receive) of the data channel
referred to in the CHANNEL_STATUS object. If set, this indicates the referred to in the CHANNEL_STATUS object. If set, this indicates
data channel is in the transmit direction. the data channel is in the transmit direction.
Channel_Status: 30 bits Channel_Status: 30 bits
This indicates the status condition of a data channel. The This indicates the status condition of a data channel. The
following values are defined. All other values are reserved. following values are defined. All other values are reserved
and should be sent as zero and ignored on receipt.
1 Signal Okay (OK): Channel is operational 1 Signal Okay (OK): Channel is operational
2 Signal Degrade (SD): A soft failure caused by a BER 2 Signal Degrade (SD): A soft failure caused by a BER
exceeding a preselected threshold. The specific BER exceeding a preselected threshold. The specific
used to define the threshold is configured. BER used to define the threshold is configured.
3 Signal Fail (SF): A hard signal failure including (but not 3 Signal Fail (SF): A hard signal failure including (but not
limited to) loss of signal (LOS), loss of frame limited to) loss of signal (LOS), loss of frame
(LOF), or Line AIS. (LOF), or Line AIS.
This object contains one or more Interface Ids followed by a This object contains one or more Interface_Ids followed by a
Channel_Status field. Channel_Status field.
To indicate the status of the entire TE Link, there MUST only be one To indicate the status of the entire TE Link, there MUST only be one
Interface Id and it MUST be zero. Interface_Id and it MUST be zero.
This object is non-negotiable. This object is non-negotiable.
14.14. CHANNEL_STATUS_REQUEST Class 13.14. CHANNEL_STATUS_REQUEST Class
Class = 14 Class = 14
o C-Type = 1, IPv4 INTERFACE_ID o C-Type = 1, IPv4 INTERFACE_ID
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Id (4 bytes) | | Interface_Id (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| : | | : |
// : // // : //
| : | | : |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Id (4 bytes) | | Interface_Id (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This object contains one or more Interface Ids. This object contains one or more Interface_Ids.
The Length of this object is 4 + 4N in bytes, where N is the number The Length of this object is 4 + 4N in bytes, where N is the number
of Interface Ids. of Interface_Ids.
o C-Type = 2, IPv4 INTERFACE_ID
o C-Type = 2, IPv6 INTERFACE_ID
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ + + +
| | | |
+ Interface Id (16 bytes) + + Interface_Id (16 bytes) +
| | | |
+ + + +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| : | | : |
// : // // : //
| : | | : |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ + + +
| | | |
+ Interface Id (16 bytes) + + Interface_Id (16 bytes) +
| | | |
+ + + +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This object contains one or more Interface Ids. This object contains one or more Interface_Ids.
The Length of this object is 4 + 16N in bytes, where N is the number The Length of this object is 4 + 16N in bytes, where N is the number
of Interface Ids. of Interface_Ids.
o C-Type = 3, Unnumbered INTERFACE_ID o C-Type = 3, Unnumbered INTERFACE_ID
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Id (4 bytes) | | Interface_Id (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| : | | : |
// : // // : //
| : | | : |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Id (4 bytes) | | Interface_Id (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This object contains one or more Interface Ids. This object contains one or more Interface_Ids.
The Length of this object is 4 + 4N in bytes, where N is the number The Length of this object is 4 + 4N in bytes, where N is the number
of Interface Ids. of Interface_Ids.
This object is non-negotiable. This object is non-negotiable.
14.15. ERROR_CODE Class 13.15. ERROR_CODE Class
Class = 20. Class = 20.
o C-Type = 1, BEGIN_VERIFY_ERROR o C-Type = 1, BEGIN_VERIFY_ERROR
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ERROR CODE | | ERROR CODE |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The following bit-values are defined: The following bit-values are defined in network byte order
(i.e., big-endian byte order):
0x01 = Link Verification Procedure not supported for this TE 0x01 = Link Verification Procedure not supported.
Link. 0x02 = Unwilling to verify.
0x02 = Unwilling to verify at this time 0x04 = Unsupported verification transport mechanism.
0x04 = Unsupported verification transport mechanism 0x08 = Link_Id configuration error.
0x08 = TE Link Id configuration error
All other values are Reserved. All other values are reserved and should be sent as zero and
ignored on receipt.
Multiple bits may be set to indicate multiple errors. Multiple bits may be set to indicate multiple errors.
This object is non-negotiable. This object is non-negotiable.
If a BeginVerifyNack message is received with Error Code 2, the node If a BeginVerifyNack message is received with Error Code 2, the node
that originated the BeginVerify SHOULD schedule a BeginVerify that originated the BeginVerify SHOULD schedule a BeginVerify
retransmission after Rf seconds, where Rf is a locally defined retransmission after Rf seconds, where Rf is a locally defined
parameter. parameter.
o C-Type = 2, LINK_SUMMARY_ERROR o C-Type = 2, LINK_SUMMARY_ERROR
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ERROR CODE | | ERROR CODE |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The following bit-values are defined: The following bit-values are defined in network byte order
(i.e., big-endian byte order):
0x01 = Unacceptable non-negotiable LINK_SUMMARY parameters 0x01 = Unacceptable non-negotiable LINK_SUMMARY parameters
0x02 = Renegotiate LINK_SUMMARY parameters 0x02 = Renegotiate LINK_SUMMARY parameters
0x04 = Bad Received Remote_Link_Id 0x04 = Bad Received Remote_Link_Id
0x08 = Bad TE Link Object 0x08 = Bad TE Link Object
0x10 = Bad Data Link Object 0x10 = Bad Data Link Object
All other values are Reserved. All other values are reserved and should be sent as zero and
ignored on receipt.
Multiple bits may be set to indicate multiple errors. Multiple bits may be set to indicate multiple errors.
This object is non-negotiable. This object is non-negotiable.
15. Security Considerations 14. Intellectual Property Considerations
Security is discussed in [LMP-SEC].
16. Intellectual Property Considerations
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances claims of rights made available for publication and any assurances
skipping to change at page 63, line 53 skipping to change at page 65, line 31
to obtain a general license or permission for the use of such to obtain a general license or permission for the use of such
proprietary rights by implementers or users of this specification proprietary rights by implementers or users of this specification
can be obtained from the IETF Secretariat. can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
17. References 15. References
17.1. Normative References 15.1. Normative References
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3," BCP 9, RFC 2026, October 1996. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[BUNDLE] Kompella, K., Rekhter, Y., Berger, L., "Link Bundling in [BUNDLE] Kompella, K., Rekhter, Y., Berger, L., "Link Bundling in
MPLS Traffic Engineering," Internet Draft, draft- MPLS Traffic Engineering," (work in progress).
kompella-mpls-bundle-05.txt, (work in progress), February [GMPLS-SIG] Ashwood-Smith, P., Banerjee, A., et al, "Generalized
2001. MPLS - Signaling Functional Description," (work in
progress).
[GMPLS-RTG] Kompella, K., Rekhter, Y. et al, "Routing Extensions in
Support of Generalized MPLS", (work in progress).
[RFC2961] Berger, L., Gan, D., et al, "RSVP Refresh Overhead [RFC2961] Berger, L., Gan, D., et al, "RSVP Refresh Overhead
Reduction Extensions," RFC 2961, April 2001. Reduction Extensions," RFC 2961, April 2001.
[GMPLS-SIG] Ashwood-Smith, P., Banerjee, A., et al, "Generalized [RFC2402] Kent, S., Atkinson, R., "IP Authentication Header", RFC
MPLS - Signaling Functional Description," Internet Draft, 2402, November 1998
draft-ietf-mpls-generalized-signaling-06.txt, (work in [RFC2406] Kent, S., Atkinson, R., "IP Encapsulating Security
progress), October 2001. Payload (ESP)", RFC 2406, November 1998
[G707] ITU-T G.707, "Network node interface for the synchronous [RFC2407] Piper, D., "The Internet IP Security Domain of
digital hierarchy (SDH)," March 1996. Interpretation for ISAKMP", RFC 2407, November 1998
[GR253] GR-253-CORE, "Synchronous Optical Network (SONET) [RFC2409] Harkins, D., Carrel, D., "The Internet Key Exchange
Transport Systems: Common Generic Criteria," Telcordia (IKE)", RFC 2409, November 1998
Technologies, Issue 3, September 2000.
[LMP-SEC] Ramamoorthi,S. and Zinin, A., "LMP Security Mechanism,"
Internet Draft, draft-sankar-lmp-sec-00.txt, (work in
progress), Internet Draft, February 2002.
17.2. Informative References 15.2. Informative References
[LAMBDA] Awduche, D. O., Rekhter, Y., Drake, J., Coltun, R.,
"Multi-Protocol Lambda Switching: Combining MPLS Traffic
Engineering Control with Optical Crossconnects,"
Internet Draft, draft-awduche-mpls-te-optical-03.txt,
(work in progress), April 2001.
[RFC3209] Awduche, D. O., Berger, L, et al, "Extensions to RSVP [RFC3209] Awduche, D. O., Berger, L, et al, "Extensions to RSVP
for LSP Tunnels," Internet Draft, RFC3209 December 2001. for LSP Tunnels," Internet Draft, RFC3209 December 2001.
[RFC3219] Jamoussi, B., ed., "Constraint-Based LSP Setup using
LDP," RFC3219, January 2002.
[OSPF-TE] Katz, D., Yeung, D., Kompella, K., "Traffic Engineering [OSPF-TE] Katz, D., Yeung, D., Kompella, K., "Traffic Engineering
Extensions to OSPF," Internet Draft, draft-katz-yeung- Extensions to OSPF," (work in progress).
ospf-traffic-04.txt, (work in progress), February 2001.
[ISIS-TE] Li, T., Smit, H., "IS-IS extensions for Traffic [ISIS-TE] Li, T., Smit, H., "IS-IS extensions for Traffic
Engineering," Internet Draft,draft-ietf-isis-traffic- Engineering," (work in progress).
02.txt, (work in progress), September 2000. [RFC2401] Kent, S., Atkinson, R., "Security Architecture for the
Internet Protocol", RFC 2401, November 1998
[RFC2434] Narten, T. and Alvestrand, H., "Guidelines for Writing
an IANA Considerations Section in RFCs," RFC 2434,
October 1998.
16. Security Considerations
There are number of attacks that an LMP protocol session can
potentially experience. Some examples include:
o an adversary may spoof control packets
o an adversary may modify the control packets in transit
o an adversary may replay control packets
o an adversary may study a number of control packets and try to
break the key using cryptographic tools. If the
hash/encryption algorithm used has known weaknesses than it
becomes easy for the adversary to discover the key using
simple tools.
This section specifies an IPsec-based security mechanism for LMP.
16.1. Security Requirements
The following requirements are applied to the mechanism described in
this section.
o LMP security MUST be able to provide authentication, integrity
and replay protection.
o For LMP traffic, confidentiality is not needed. Only
authentication is needed to ensure the control packets
(packets sent along the LMP Control Channel) are originating
from the right place and have not been modified in transit.
LMP Test packets exchanged through the data links do not need
to be protected.
o Security mechanism should provide for well defined key
management schemes. The key management schemes should be well
analyzed to be cryptographically secure. The key management
schemes should be scalable.
o The algorithms used for authentication MUST be
cryptographically sound. Also the security protocol MUST
allow for negotiating and using different authentication
algorithms.
16.2. Security Mechanisms
IPsec is a protocol suite that is used to secure communication at the
network layer between two peers. This protocol is comprised of IP
Security architecture document [RFC2401], IKE [RFC2409], IPsec AH
[RFC2402], and IPsec ESP [RFC2406]. IKE is the key management
protocol for IP networks while AH and ESP are used to protect IP
traffic. IKE is defined specific to IP domain of interpretation.
Considering the requirements described in Section 16.1, it is
recommended that where security is needed for LMP, implementations
use IPsec as described below:
1. IPsec AH, tunnel mode SHOULD be used for packet authentication.
2. IKE [RFC2409] SHOULD be used as the key exchange mechanism.
Implementations of LMP over IPsec protocol MUST support manual keying
mode and dynamic key exchange protocol using IKE. IKE implementation
SHOULD use the IPsec DOI [RFC2407].
For IKE protocol, the identities of the SAs negotiated in Quick Mode
represent the traffic that the peers agree to protect and are
comprised of address space, protocol and port information. For LMP
over IPsec, it is recommended that the identity payload contain the
following information. The identities SHOULD be of type IP
addresses and the value of the identities SHOULD be the IP addresses
of the communicating peers. The protocol field SHOULD be IP protocol
UDP (17). The port field SHOULD be set to zero to indicate port
fields should be ignored. In LMP exchanges, the channel identifier
user by the peer is not known beforehand, and hence cannot be used in
the SA. This restriction implies that LMP authentication is
performed on a per LMP neighbor basis rather than on a per LMP
control channel basis between two neighbors.
All LMP messages are expected to be sent over the IPsec channel. The
crypto channel (IKE SA and IPsec SAs) may be established on need
basis or earlier. However, all LMP messages should be sent through
the crypto channel.
A set of control channels can share the same crypto channel. When
LMP Hellos are used to monitor the status of the control channel, it
is important to keep in mind that the keep-alive failure in a control
channel may also be due to failure in the crypto channel. The
following method is recommended to ensure LMP communication path
between two peers is working properly.
- If LMP Hellos detect a failure on a control channel, switch to an
alternate (backup) control channel and/or try to bring up a new
control channel.
- Ensure the health of the control channels using LMP Hellos. If
all control channels indicate a failure and it is not possible to
bring up a new control channel, tear down all existing control
channels. Also tear down the crypto channel (both the IKE SA and
IPsec SAs).
- Reestablish the crypto channel. Failure to establish a crypto
channel indicates a fatal failure for LMP communication.
- Bring up the control channel. Failure to bring up the control
channel indicates a fatal failure for LMP communication.
o When LMP peers are dynamically discovered (particularly the
initiator), the following points should be noted if pre-shared
key based authentication is used for setting up the crypto
channels. When using pre-shared key based authentication, the
pre-shared key is required to compute the value of SKEYID
(used for deriving keys to encrypt messages during key
exchange). In main mode, pre-shared key to be used has to be
identified from information in the IP header since SKEYID is
calculated prior to the receipt of identification payloads.
This is not possible if the IP addresses of the peer are
discovered dynamically. Aggressive mode of key exchange can
be used since identification payloads are sent in the first
message.
Note however that aggressive mode is prone to passive denial of
service attacks. We also strongly discourage using a shared secret
(group shared secret) among a number of peers as this opens up the
solution to man-in-the middle attacks.
Digital signature based authentication is not prone to such problems.
It is recommended using digital signature based authentication
mechanism where possible. If pre-shared key based authentication is
required, then aggressive mode SHOULD be used. IKE pre-shared
authentication key values SHOULD be protected in a manner similar to
the user's account password.
17. IANA Considerations
LMP requires that a UDP port number be assigned.
LMP defines the following name spaces that require management:
- LMP Message Type.
- LMP Object Class.
- LMP Object Class type (C-Type). These are unique within the
Object Class.
- LMP Sub-object Class type (Type). These are unique within the
Object Class.
The LMP Message Type name space should be allocated as follows:
pursuant to the policies outlined in [RFC2434], the numbers in the
range 0-127 are allocated by Expert Review, 128-240 are allocated
through an IETF Consensus action, and 241-255 are reserved for
Private Use.
The LMP Object Class name space should be allocated as follows:
pursuant to the policies outlined in [RFC2434], the numbers in the
range of 0-127 are allocated by Expert Review, 128-247 are allocated
through an IETF Consensus action, and 248-255 are reserved for
Private Use.
The LMP Sub-object Class name space should be allocated as follows:
pursuant to the policies outlined in [RFC2434], the numbers in the
range of 0-127 are allocated by Expert Review, 128-247 are allocated
through an IETF Consensus action, and 248-255 are reserved for
Private Use.
The LMP Object Class type name space should be allocated as follows:
pursuant to the policies outlined in [RFC2434], the numbers in the
range 0-111 are allocated by Expert Review, 112-119 are allocated
through an IETF Consensus action, and 120-127 are reserved for
Private Use.
The following name spaces need to be assigned initially:
[Note to RFC Editor: Please drop all text enclosed in parentheses in
this section once the IANA assignments are made. The values are
included for reference only and should be considered unassigned.]
------------------------------------------------------------------
LMP Message Type name space
o Config message (suggested Message type = 1)
o ConfigAck message (suggested Message type = 2)
o ConfigNack message (suggested Message type = 3)
o Hello message (suggested Message type = 4)
o BeginVerify message (suggested Message type = 5)
o BeginVerifyAck message (suggested Message type = 6)
o BeginVerifyNack message (suggested Message type = 7)
o EndVerify message (suggested Message type = 8)
o EndVerifyAck message (suggested Message type = 9)
o Test message (suggested Message type = 10)
o TestStatusSuccess message (suggested Message type = 11)
o TestStatusFailure message (suggested Message type = 12)
o TestStatusAck message (suggested Message type = 13)
o LinkSummary message (suggested Message type = 14)
o LinkSummaryAck message (suggested Message type = 15)
o LinkSummaryNack message (suggested Message type = 16)
o ChannelStatus message (suggested Message type = 17)
o ChannelStatusAck message (suggested Message type = 18)
o ChannelStatusRequest message (suggested Message type = 19)
o ChannelStatusResponse message (suggested Message type = 20)
------------------------------------------------------------------
LMP Object Class name space and Class type (C-Type)
o CCID Class name (suggested = 1)
- LOCAL_CCID (suggested C-Type = 1)
- REMOTE_CCID (suggested C-Type = 2)
o NODE_ID Class name (suggested = 2)
- LOCAL_NODE_ID (suggested C-Type = 1)
- REMOTE_NODE_ID (suggested C-Type = 2)
o LINK_ID Class name (suggested = 3)
- IPv4 LOCAL_LINK_ID (suggested C-Type = 1)
- IPv4 REMOTE_LINK_ID (suggested C-Type = 2)
- IPv6 LOCAL_LINK_ID (suggested C-Type = 3)
- IPv6 REMOTE_LINK_ID (suggested C-Type = 4)
- unnumbered LOCAL_LINK_ID (suggested C-Type = 5)
- unnumbered REMOTE_LINK_ID (suggested C-Type = 6)
o INTERFACE_ID Class name (suggested = 4)
- IPv4 LOCAL_INTERFACE_ID (suggested C-Type = 1)
- IPv4 REMOTE_INTERFACE_ID (suggested C-Type = 2)
- IPv6 LOCAL_INTERFACE_ID (suggested C-Type = 3)
- IPv6 REMOTE_INTERFACE_ID (suggested C-Type = 4)
- unnumbered LOCAL_INTERFACE_ID (suggested C-Type = 5)
- unnumbered REMOTE_INTERFACE_ID (suggested C-Type = 6)
o MESSAGE_ID Class name (suggested = 5)
- MESSAGE_ID (suggested C-Type = 1)
- MESSAGE_ID_ACK (suggested C-Type = 2)
o CONFIG_ID Class name (suggested = 6)
- HELLO_CONFIG (suggested C-Type = 1)
o HELLO Class name (suggested = 7)
- HELLO (suggested C-Type = 1)
o BEGIN_VERIFY Class name (suggested = 8)
- Type 1 (suggested C-Type = 1)
o BEGIN_VERIFY_ACK Class name (suggested = 9)
- Type 1 (suggested C-Type = 1)
o VERIFY_ID Class name (suggested = 10)
- Type 1 (suggested C-Type = 1)
o TE_LINK_ID Class name (suggested = 11)
- IPv4 TE_LINK_ID (suggested C-Type = 1)
- IPv6 TE_LINK_ID (suggested C-Type = 2)
- unnumbered TE_LINK_ID (suggested C-Type = 3)
o DATA_LINK_ID Class name (suggested = 12)
- IPv4 DATA_LINK_ID (suggested C-Type = 1)
- IPv6 DATA_LINK_ID (suggested C-Type = 2)
- unnumbered DATA_LINK_ID (suggested C-Type = 3)
- Interface Switching Capability (suggested sub-object Type = 1)
- Wavelength (suggested sub-object Type = 2)
o CHANNEL_STATUS Class name (suggested = 13)
- IPv4 INTERFACE_ID (suggested C-Type = 1)
- IPv6 INTERFACE_ID (suggested C-Type = 2)
- unnumbered INTERFACE_ID (suggested C-Type = 3)
o CHANNEL_STATUS_REQUEST Class name (suggested = 14)
- IPv4 INTERFACE_ID (suggested C-Type = 1)
- IPv6 INTERFACE_ID (suggested C-Type = 2)
- unnumbered INTERFACE_ID (suggested C-Type = 3)
o ERROR_CODE Class name (suggested = 20)
- BEGIN_VERIFY_ERROR (suggested C-Type = 1)
- LINK_SUMMARY_ERROR (suggested C-Type = 2)
18. Acknowledgements 18. Acknowledgements
The authors would like to thank Andre Fredette for his many The authors would like to thank Andre Fredette for his many
contributions to this draft. We would also like to thank Ayan contributions to this document. We would also like to thank Ayan
Banerjee, George Swallow, Andre Fredette, Adrian Farrel, Vinay Banerjee, George Swallow, Andre Fredette, Adrian Farrel, Vinay
Ravuri, and David Drysdale for their insightful comments and Ravuri, and David Drysdale for their insightful comments and
suggestions. We would also like to thank John Yu, Suresh Katukam, suggestions. We would also like to thank John Yu, Suresh Katukam,
and Greg Bernstein for their helpful suggestions for the in-band and Greg Bernstein for their helpful suggestions for the in-band
control channel applicability. Finally, we would like to thank control channel applicability. Finally, we would like to thank
Dimitri Papadimitriou for his contributions to the SONET/SDH test Dimitri Papadimitriou for his contributions to the SONET/SDH test
procedures. procedures.
19. Contributors 19. Contributors
Jonathan P. Lang Krishna Mitra Jonathan P. Lang Krishna Mitra
Calient Networks Calient Networks Calient Networks Calient Networks
25 Castilian Drive 5853 Rue Ferrari 25 Castilian Drive 5853 Rue Ferrari
Goleta, CA 93117 San Jose, CA 95138 Goleta, CA 93117 San Jose, CA 95138
Email: jplang@calient.net email: krishna@calient.net Email: jplang@calient.net email: krishna@calient.net
John Drake Kireeti Kompella John Drake Kireeti Kompella
Calient Networks Juniper Networks, Inc. Calient Networks Juniper Networks, Inc.
5853 Rue Ferrari 385 Ravendale Drive 5853 Rue Ferrari 1194 North Mathilda Avenue
San Jose, CA 95138 Mountain View, CA 94043 San Jose, CA 95138 Sunnyvale, CA 94089
email: jdrake@calient.net email: kireeti@juniper.net email: jdrake@calient.net email: kireeti@juniper.net
Yakov Rekhter Lou Berger Yakov Rekhter Lou Berger
Juniper Networks, Inc. Movaz Networks Juniper Networks, Inc. Movaz Networks
385 Ravendale Drive email: lberger@movaz.com 1194 North Mathilda Avenue email: lberger@movaz.com
Mountain View, CA 94043 Sunnyvale, CA 94089
email: yakov@juniper.net email: yakov@juniper.net
Debanjan Saha Debashis Basak Debanjan Saha Debashis Basak
Tellium Optical Systems Accelight Networks Tellium Optical Systems Accelight Networks
2 Crescent Place 70 Abele Road, Suite 1201 2 Crescent Place 70 Abele Road, Suite 1201
Oceanport, NJ 07757-0901 Bridgeville, PA 15017-3470 Oceanport, NJ 07757-0901 Bridgeville, PA 15017-3470
email: dsaha@tellium.com email: dbasak@accelight.com email: dsaha@tellium.com email: dbasak@accelight.com
Hal Sandick Alex Zinin Hal Sandick Alex Zinin
Shepard M.S. Alcatel Shepard M.S. Alcatel
2401 Dakota Street email: zinin@psg.com 2401 Dakota Street email: zinin@psg.com
Durham, NC 27705 Durham, NC 27705
email: sandick@nc.rr.com email: sandick@nc.rr.com
Bala Rajagopalan Bala Rajagopalan Sankar Ramamoorthi
Tellium Optical Systems Tellium Optical Systems Juniper Networks, Inc.
2 Crescent Place 2 Crescent Place 1194 North Mathilda Avenue
Oceanport, NJ 07757-0901 Oceanport, NJ 07757-0901 Sunnyvale, CA 94089
email: braja@tellium.com email: braja@tellium.com email: sankarr@juniper.net
20. Contact Address 20. Contact Address
Jonathan P. Lang Jonathan P. Lang
Calient Networks Calient Networks
25 Castilian Drive 25 Castilian Drive
Goleta, CA 93117 Goleta, CA 93117
Email: jplang@calient.net Email: jplang@calient.net
21. Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/