draft-ietf-ccamp-lmp-05.txt   draft-ietf-ccamp-lmp-06.txt 
Network Working Group J. Lang, Editor Network Working Group J. Lang, Editor
Internet Draft Calient Networks Internet Draft Calient Networks
Category: Standards Track August 2002 Category: Standards Track September 2002
Expires: February 2003 Expires: March 2003
Link Management Protocol (LMP) Link Management Protocol (LMP)
draft-ietf-ccamp-lmp-05.txt draft-ietf-ccamp-lmp-06.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. 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.
skipping to change at page 2, line 6 skipping to change at page 2, line 6
management of TE links is not restricted to in-band messaging, but management of TE links is not restricted to in-band messaging, but
instead can be done using out-of-band techniques. This document instead can be done using out-of-band techniques. This document
specifies a link management protocol (LMP) that runs between specifies a link management protocol (LMP) that runs between
neighboring nodes and is used to manage TE links. Specifically, LMP neighboring nodes and is used to manage TE links. Specifically, LMP
will be used to maintain control channel connectivity, verify the will be used to maintain control channel connectivity, verify the
physical connectivity of the data links, correlate the link property physical connectivity of the data links, correlate the link property
information, suppress downstream alarms, and localize link failures information, suppress downstream alarms, and localize link failures
for protection/restoration purposes in multiple kinds of networks. for protection/restoration purposes in multiple kinds of networks.
Table of Contents Table of Contents
1 Introduction ................................................ 5 0 Introduction ................................................ 4
1.1 Terminology ............................................. 5 1.1 Terminology ............................................. 4
2 LMP Overview ................................................ 8 2 LMP Overview ................................................ 8
3 Control Channel Management .................................. 10 3 Control Channel Management .................................. 10
3.1 Parameter Negotiation ................................... 11 3.1 Parameter Negotiation ................................... 11
3.2 Hello Protocol .......................................... 12 3.2 Hello Protocol .......................................... 12
3.2.1 Hello Parameter Negotiation ...................... 12 3.2.1 Hello Parameter Negotiation ...................... 12
3.2.2 Fast Keep-alive .................................. 13 3.2.2 Fast Keep-alive .................................. 13
3.2.3 Control Channel Down ............................. 13 3.2.3 Control Channel Down ............................. 13
3.2.4 Degraded State ................................... 14 3.2.4 Degraded State ................................... 14
4 Link Property Correlation ................................... 14 4 Link Property Correlation ................................... 14
5 Verifying Link Connectivity ................................. 16 5 Verifying Link Connectivity ................................. 16
skipping to change at page 4, line 4 skipping to change at page 4, line 4
14 Intellectual Property Considerations ........................ 65 14 Intellectual Property Considerations ........................ 65
15 References .................................................. 65 15 References .................................................. 65
16 Security Considerations ..................................... 66 16 Security Considerations ..................................... 66
16.1 Security Requirements .................................. 66 16.1 Security Requirements .................................. 66
16.2 Security Mechanisms .................................... 67 16.2 Security Mechanisms .................................... 67
17 IANA Considerations ......................................... 68 17 IANA Considerations ......................................... 68
18 Acknowledgements ............................................ 71 18 Acknowledgements ............................................ 71
19 Contributors ................................................ 72 19 Contributors ................................................ 72
20 Contact Address ............................................. 72 20 Contact Address ............................................. 72
21 Full Copyright Statement .................................... 73 21 Full Copyright Statement .................................... 73
[Editor's note: ŠŠChanges from previous versionĂĂ notes can be removed [Editor's note: ˘Changes from -0x version÷ notes can be removed prior
prior to publication as an RFC.] to publication as an RFC.]
Changes from previous version: Changes from -05 version:
o Clarified Node_Id in terminology section.
o Modified default values for HelloInterval and HelloDeadInterval.
Changes from -04 version:
o Editorial changes. o Editorial changes.
o Added a terminology section o Added a terminology section
o Added text to the Security Considerations section. o Added text to the Security Considerations section.
o Removed discussion of the BeginVerifyTransport flags for specific o Removed discussion of the BeginVerifyTransport flags for specific
Encoding Types to a separate Internet Draft. Encoding Types to a separate Internet Draft.
o Added a terminology section.
o Removed the LMP checksum. o Removed the LMP checksum.
o Clarified the IANA Considerations section with assignment rules o Clarified the IANA Considerations section with assignment rules
and suggested values. and suggested values.
1. Introduction 1. Introduction
Networks are being developed with routers, switches, crossconnects, Networks are being developed with routers, switches, crossconnects,
DWDM systems, and add-drop multiplexors (ADMs) that use a common DWDM systems, and add-drop multiplexors (ADMs) that use a common
control plane [e.g., Generalized MPLS (GMPLS)] to dynamically control plane [e.g., Generalized MPLS (GMPLS)] to dynamically
allocate resources and to provide network survivability using allocate resources and to provide network survivability using
skipping to change at page 7, line 46 skipping to change at page 7, line 46
Link Property Correlation: Link Property Correlation:
This is a procedure to correlate the local and remote properties This is a procedure to correlate the local and remote properties
of a TE link. of a TE link.
Multiplex Capability: Multiplex Capability:
The ability to multiplex/demultiplex a data stream into sub-rate The ability to multiplex/demultiplex a data stream into sub-rate
streams for switching purposes. streams for switching purposes.
Node_Id:
For a node running OSPF, the LMP Node_Id is the same as the
address contained in the OSPF Router Address TLV. For a node
running IS-IS and advertising the TE Router ID TLV, the Node_Id
is the same as the advertised Router ID.
Port: Port:
An interface that terminates a data link. An interface that terminates a data link.
TE Link: TE Link:
As defined in [GMPLS-RTG], a TE link is a logical construct that As defined in [GMPLS-RTG], a TE link is a logical construct that
represents a way to group/map the information about certain represents a way to group/map the information about certain
physical resources (and their properties) that interconnect LSRs physical resources (and their properties) that interconnect LSRs
into the information that is used by Constrained SPF for the into the information that is used by Constrained SPF for the
purpose of path computation, and by GMPLS signaling. purpose of path computation, and by GMPLS signaling.
skipping to change at page 12, line 39 skipping to change at page 12, line 39
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). (ms).
The HelloDeadInterval MUST be greater than the HelloInterval, and The HelloDeadInterval MUST be greater than the HelloInterval, and
SHOULD be at least 3 times the value of HelloInterval. If the fast SHOULD be at least 3 times the value of HelloInterval. If the fast
keep-alive mechanism of LMP is not used, the HelloInterval and keep-alive mechanism of LMP is not used, the HelloInterval and
HelloDeadInterval parameters MUST be set to zero. 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 150 ms and for the
HelloDeadInterval is 18 ms. HelloDeadInterval is 500 ms.
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.
skipping to change at page 48, line 19 skipping to change at page 48, line 19
o C-Type = 1, LOCAL_NODE_ID 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 identifies the node that originated the LMP packet.
This object is non-negotiable. This object is non-negotiable.
o C-Type = 2, REMOTE_NODE_ID 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 identifies the remote node.
This object is non-negotiable. This object is non-negotiable.
13.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
skipping to change at page 50, line 40 skipping to change at page 50, line 40
For the REMOTE_INTERFACE_ID, this identifies the remote nodeĂs For the REMOTE_INTERFACE_ID, this identifies the remote nodeĂs
data link. The Interface_Id MUST be non-zero. data link. The Interface_Id MUST be non-zero.
This object is non-negotiable. This object is non-negotiable.
13.5. MESSAGE_ID Class 13.5. MESSAGE_ID Class
Class = 5. Class = 5.
o C-Type=1, MessageId o C-Type=1, MESSAGE_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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 incremented and only decreases when the value wraps. This
is 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, MESSAGE_ID_ACK
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.
13.6. CONFIG Class 13.6. CONFIG Class
Class = 6. Class = 6.
o C-Type = 1, HelloConfig o C-Type = 1, HELLO_CONFIG
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
HelloInterval: 16 bits. HelloInterval: 16 bits.
Indicates how frequently the Hello packets will be sent and is Indicates how frequently the Hello packets will be sent and is
skipping to change at page 51, line 53 skipping to change at page 51, line 53
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.
13.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 56, line 48 skipping to change at page 56, line 48
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_Interface_Id (4 bytes) | | Local_Interface_Id (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remote_Interface_Id (4 bytes) | | Remote_Interface_Id (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
// (Subobjects) // // (Sub-objects) //
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o C-Type = 2, IPv6 DATA_LINK o C-Type = 2, IPv6 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 57, line 26 skipping to change at page 57, line 26
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ + + +
| | | |
+ Remote_Interface_Id (16 bytes) + + Remote_Interface_Id (16 bytes) +
| | | |
+ + + +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
// (Subobjects) // // (Sub-objects) //
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o C-Type = 3, Unnumbered DATA_LINK o C-Type = 3, Unnumbered 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) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local_Interface_Id (4 bytes) | | Local_Interface_Id (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remote_Interface_Id (4 bytes) | | Remote_Interface_Id (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
// (Subobjects) // // (Sub-objects) //
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Reserved field should be sent as zero and ignored on receipt. 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. and should be sent as zero and ignored on receipt.
skipping to change at page 58, line 24 skipping to change at page 58, line 24
Local_Interface_Id: Local_Interface_Id:
This is the local identifier of the data link. This MUST be This is the local identifier of the data link. This MUST be
node-wide unique and non-zero. node-wide unique and non-zero.
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 Sub-objects
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 sub-objects. The sub-objects
are defined in section 13.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 sub-object. More than
one subobject of the same Type may appear if multiple capabilities one sub-object of the same Type may appear if multiple capabilities
are supported over the data link. are supported over the data link.
13.12.1. Data Link Subobjects 13.12.1. Data Link Sub-objects
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 sub-objects. Each sub-object 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 | (Sub-object 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 sub-object.
Currently defined values are: Currently defined values are:
Type = 1, Interface Switching Capability Type = 1, Interface Switching Capability
Type = 2, Wavelength 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 sub-object in
including the Type and Length fields. The Length MUST be at bytes, including the Type and Length fields. The Length MUST
least 4, and MUST be a multiple of 4. be at least 4, and MUST be a multiple of 4.
13.12.1.1. Subobject Type 1: Interface Switching Capability 13.12.1.1. Sub-object 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 59, line 46 skipping to change at page 59, line 46
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.
13.12.1.2. Subobject Type 2: Wavelength 13.12.1.2. Sub-object 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. The Reserved field should be sent as zero and ignored on receipt.
skipping to change at page 71, line 8 skipping to change at page 71, line 8
- IPv4 LOCAL_INTERFACE_ID (suggested C-Type = 1) - IPv4 LOCAL_INTERFACE_ID (suggested C-Type = 1)
- IPv4 REMOTE_INTERFACE_ID (suggested C-Type = 2) - IPv4 REMOTE_INTERFACE_ID (suggested C-Type = 2)
- IPv6 LOCAL_INTERFACE_ID (suggested C-Type = 3) - IPv6 LOCAL_INTERFACE_ID (suggested C-Type = 3)
- IPv6 REMOTE_INTERFACE_ID (suggested C-Type = 4) - IPv6 REMOTE_INTERFACE_ID (suggested C-Type = 4)
- unnumbered LOCAL_INTERFACE_ID (suggested C-Type = 5) - unnumbered LOCAL_INTERFACE_ID (suggested C-Type = 5)
- unnumbered REMOTE_INTERFACE_ID (suggested C-Type = 6) - unnumbered REMOTE_INTERFACE_ID (suggested C-Type = 6)
o MESSAGE_ID Class name (suggested = 5) o MESSAGE_ID Class name (suggested = 5)
- MESSAGE_ID (suggested C-Type = 1) - MESSAGE_ID (suggested C-Type = 1)
- MESSAGE_ID_ACK (suggested C-Type = 2) - MESSAGE_ID_ACK (suggested C-Type = 2)
o CONFIG_ID Class name (suggested = 6) o CONFIG Class name (suggested = 6)
- HELLO_CONFIG (suggested C-Type = 1) - HELLO_CONFIG (suggested C-Type = 1)
o HELLO Class name (suggested = 7) o HELLO Class name (suggested = 7)
- HELLO (suggested C-Type = 1) - HELLO (suggested C-Type = 1)
o BEGIN_VERIFY Class name (suggested = 8) o BEGIN_VERIFY Class name (suggested = 8)
- Type 1 (suggested C-Type = 1) - Type 1 (suggested C-Type = 1)
o BEGIN_VERIFY_ACK Class name (suggested = 9) o BEGIN_VERIFY_ACK Class name (suggested = 9)
- Type 1 (suggested C-Type = 1) - Type 1 (suggested C-Type = 1)
skipping to change at page 72, line 14 skipping to change at page 72, line 14
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 Independent Consultant
25 Castilian Drive 5853 Rue Ferrari 25 Castilian Drive email: kmitra@earthlink.net
Goleta, CA 93117 San Jose, CA 95138 Goleta, CA 93117
Email: jplang@calient.net email: krishna@calient.net Email: jplang@calient.net
John Drake Kireeti Kompella John Drake Kireeti Kompella
Calient Networks Juniper Networks, Inc. Calient Networks Juniper Networks, Inc.
5853 Rue Ferrari 1194 North Mathilda Avenue 5853 Rue Ferrari 1194 North Mathilda Avenue
San Jose, CA 95138 Sunnyvale, CA 94089 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
1194 North Mathilda Avenue email: lberger@movaz.com 1194 North Mathilda Avenue email: lberger@movaz.com
 End of changes. 

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