draft-ietf-ccamp-lmp-06.txt   draft-ietf-ccamp-lmp-07.txt 
Network Working Group J. Lang, Editor Network Working Group J. Lang, Editor
Internet Draft Calient Networks Internet Draft Calient Networks
Category: Standards Track September 2002 Category: Standards Track November 2002
Expires: March 2003 Expires: May 2003
Link Management Protocol (LMP) Link Management Protocol (LMP)
draft-ietf-ccamp-lmp-06.txt draft-ietf-ccamp-lmp-07.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
0 Introduction ................................................ 4 1 Introduction ................................................ 5
1.1 Terminology ............................................. 4 1.1 Terminology ............................................. 5
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 2, line 53 skipping to change at page 2, line 53
11.3.3 Active Data Link FSM Description ................ 35 11.3.3 Active Data Link FSM Description ................ 35
11.3.4 Passive Data Link FSM Description ............... 36 11.3.4 Passive Data Link FSM Description ............... 36
12 LMP Message Formats ......................................... 37 12 LMP Message Formats ......................................... 37
12.1 Common Header .......................................... 37 12.1 Common Header .......................................... 37
12.2 LMP Object Format ...................................... 38 12.2 LMP Object Format ...................................... 38
12.3 Parameter Negotiation Messages ......................... 39 12.3 Parameter Negotiation Messages ......................... 39
12.4 Hello Message .......................................... 41 12.4 Hello Message .......................................... 41
12.5 Link Verification Messages ............................. 41 12.5 Link Verification Messages ............................. 41
12.6 Link Summary Messages .................................. 45 12.6 Link Summary Messages .................................. 45
12.7 Fault Management Messages .............................. 46 12.7 Fault Management Messages .............................. 46
13 LMP Object Definitions ...................................... 47 13 LMP Object Definitions ...................................... 48
14 Intellectual Property Considerations ........................ 65 14 Intellectual Property Considerations ........................ 66
15 References .................................................. 65 15 References .................................................. 66
16 Security Considerations ..................................... 66 16 Security Considerations ..................................... 67
16.1 Security Requirements .................................. 66 16.1 Security Requirements .................................. 67
16.2 Security Mechanisms .................................... 67 16.2 Security Mechanisms .................................... 68
17 IANA Considerations ......................................... 68 17 IANA Considerations ......................................... 69
18 Acknowledgements ............................................ 71 18 Acknowledgements ............................................ 72
19 Contributors ................................................ 72 19 Contributors ................................................ 73
20 Contact Address ............................................. 72 20 Contact Address ............................................. 73
21 Full Copyright Statement .................................... 73 21 Full Copyright Statement .................................... 74
[Editor's note: ˘Changes from -0x version÷ notes can be removed prior [Editor's note: "Changes from previous version" notes can be removed
to publication as an RFC.] prior to publication as an RFC.]
Changes from -05 version:
o Clarified Node_Id in terminology section.
o Modified default values for HelloInterval and HelloDeadInterval.
Changes from -04 version: Changes from previous version:
o Editorial changes. o Editorial changes.
o Added a terminology section o Updated Error Codes.
o Added text to the Security Considerations section.
o Removed discussion of the BeginVerifyTransport flags for specific
Encoding Types to a separate Internet Draft.
o Removed the LMP checksum.
o Clarified the IANA Considerations section with assignment rules
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
protection and restoration techniques. A pair of nodes may have protection and restoration techniques. A pair of nodes may have
thousands of interconnects, where each interconnect may consist of thousands of interconnects, where each interconnect may consist of
multiple data links when multiplexing (e.g., Frame Relay DLCIs at multiple data links when multiplexing (e.g., Frame Relay DLCIs at
skipping to change at page 6, line 39 skipping to change at page 6, line 39
are once again grouped together into a single TE link, then link are once again grouped together into a single TE link, then link
bundling [BUNDLE] is not required and only two levels of bundling [BUNDLE] is not required and only two levels of
identification are required: Link_Id and Port_Id. In this case, identification are required: Link_Id and Port_Id. In this case,
both resource allocation and physical connectivity happen at the both resource allocation and physical connectivity happen at the
lowest level (i.e. port level). 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 a cross-connect with OC-192
OXC SHOULD be able to configure each OC-48 sub-channel as a data interfaces, the cross-connect SHOULD be able to configure each sub-
channel (e.g., STS-48c SPE if the 4:1 MUX is a SONET MUX) as a data
link. link.
LMP is designed to support aggregation of one or more data links LMP is designed to support aggregation of one or more data links
into a TE link (either ports into TE links, or component links into into a TE link (either ports into TE links, or component links 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 1.1. Terminology
skipping to change at page 41, 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.
If a node receives a Config message and recognizes the CONFIG object
but does not recognize the C-Type, a ConfigNack message including
the unknown CONFIG object MUST be sent.
12.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 every HelloInterval msec. If no Hello message is received within
skipping to change at page 42, line 49 skipping to change at page 42, line 54
<MESSAGE_ID_ACK> <ERROR_CODE> <MESSAGE_ID_ACK> <ERROR_CODE>
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
BeginVerify message being negatively acknowledged. BeginVerify message being negatively acknowledged.
If the Verification process is not supported, the ERROR_CODE MUST If the Verification process is not supported, the ERROR_CODE MUST
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 is 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 Link_Id is not supported and the If remote configuration of the Link_Id is not supported and the
contents of the REMOTE_LINK_ID object (included in the BeginVerify contents of the REMOTE_LINK_ID object (included in the BeginVerify
message) does not match any configured values, the ERROR_CODE MUST message) does not match any configured values, the ERROR_CODE MUST
indicate "Link_Id configuration error". indicate "Link_Id configuration error".
If a node receives a BeginVerify message and recognizes the
BEGIN_VERIFY object but does not recognize the C-Type, the
ERROR_CODE MUST indicate, "Unknown object C-Type".
12.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.
skipping to change at page 46, line 11 skipping to change at page 46, line 21
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 sent. The values received in the new LinkSummary message SHOULD
take into account the acceptable parameters included in the take into account the acceptable parameters included in the
LinkSummaryNack message. LinkSummaryNack message.
If the LinkSummary message is received with unacceptable non-
negotiable parameters, the ERROR_CODE MUST indicate "Unacceptable
non-netotiable LINK_SUMMARY parameters."
If the LinkSummary message is received with unacceptable negotiable
parameters, the ERROR_CODE MUST indicate "Renegotiate LINK_SUMMARY
parameters."
If the LinkSummary message is received with an invalid TE_LINK
object, the ERROR_CODE MUST indicate "Invalid TE_LINK object."
If the LinkSummary message is received with an invalid DATA_LINK
object, the ERROR_CODE MUST indicate "Invalid DATA_LINK object."
If the LinkSummary message is received with a TE_LINK object but the
C-Type is unknown, the ERROR_CODE MUST indicate, "Unknown TE_LINK
object C-Type."
If the LinkSummary message is received with a DATA_LINK object but
the C-Type is unknown, the ERROR_CODE MUST indicate, "Unknown
DATA_LINK object C-Type."
12.7. Fault Management Messages 12.7. Fault Management Messages
12.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>
skipping to change at page 48, line 19 skipping to change at page 48, line 55
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 identifies 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 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 identifies the remote node. This identities 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 51, line 28
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, MESSAGE_ID 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 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, MESSAGE_ID_ACK 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.
13.6. CONFIG Class 13.6. CONFIG Class
skipping to change at page 51, line 25 skipping to change at page 52, line 16
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, HELLO_CONFIG 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 52, line 44
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
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 used to indicate that the this is the first Hello TxSeqNum=1 is used to indicate that the this is the first Hello
skipping to change at page 53, line 35 skipping to change at page 54, line 27
EncType: 8 bits EncType: 8 bits
This is the encoding type of the data link. The defined This is the encoding type of the data link. The defined
EncType values are consistent with the LSP Encoding Type values EncType values are consistent with the LSP Encoding Type values
of [GMPLS-SIG]. of [GMPLS-SIG].
Verify Transport Mechanism: 16 bits Verify Transport Mechanism: 16 bits
This defines the transport mechanism for the Test Messages. This defines the transport mechanism for the Test Messages.
The scope of this bit mask is restricted to each LSP encoding The scope of this bit mask is restricted to each encoding type.
type. The local node will set the bits corresponding to the The local node will set the bits corresponding to the various
various mechanisms it can support for transmitting LMP test mechanisms it can support for transmitting LMP test messages.
messages. The receiver chooses the appropriate mechanism in The receiver chooses the appropriate mechanism in the
the BeginVerifyAck message. BeginVerifyAck message.
The following flag is defined across all LSP Encoding Types. The following flag is defined across all Encoding Types. All
All other flags are dependent on the LSP Encoding Type. other flags are dependent on the Encoding Type.
0x8000 Payload: Test Message transmitted in the payload 0x8000 Payload: Test Message transmitted in the payload
Capable of transmitting Test messages in the payload. 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.
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
skipping to change at page 56, line 48 skipping to change at page 57, line 38
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) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
// (Sub-objects) // // (Subobjects) //
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ + + +
| | | |
+ Local_Interface_Id (16 bytes) + + Local_Interface_Id (16 bytes) +
| | | |
skipping to change at page 57, line 26 skipping to change at page 58, line 28
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ + + +
| | | |
+ Remote_Interface_Id (16 bytes) + + Remote_Interface_Id (16 bytes) +
| | | |
+ + + +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
// (Sub-objects) // // (Subobjects) //
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
// (Sub-objects) // // (Subobjects) //
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 59, line 26
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.
Sub-objects 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 sub-objects. The sub-objects variable-length data items called subobjects. The subobjects
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 sub-object. More than A DATA_LINK object may contain more than one subobject. More than
one sub-object 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.
13.12.1. Data Link Sub-objects 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 sub-objects. Each sub-object 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 | (Sub-object contents) | | Type | Length | (Subobject contents) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--------------//---------------+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--------------//---------------+
Type: 8 bits Type: 8 bits
The Type indicates the type of contents of the sub-object. 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 Type
Type = 2, Wavelength Type = 2, Wavelength
Length: 8 bits Length: 8 bits
The Length contains the total length of the sub-object in The Length contains the total length of the subobject in bytes,
bytes, including the Type and Length fields. The Length MUST including the Type and Length fields. The Length MUST be at
be at least 4, and MUST be a multiple of 4. least 4, and MUST be a multiple of 4.
13.12.1.1. Sub-object Type 1: Interface Switching Capability 13.12.1.1. Subobject Type 1: Interface Switching Type
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 Type| EncType |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Minimum Reservable Bandwidth | | Minimum Reservable Bandwidth |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Maximum Reservable Bandwidth | | Maximum Reservable Bandwidth |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Switching Capability: 8 bits Switching Type: 8 bits
This is used to identify the local Interface Switching This is used to identify the local Interface Switching Type of
Capability of the TE link as defined in [GMPLS-SIG]. 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 This is the encoding type of the data link. The defined
EncType values are consistent with the Link Encoding Type EncType values are consistent with the LSP Encoding Type values
values of [GMPLS-SIG]. 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.
13.12.1.2. Sub-object 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. The Reserved field should be sent as zero and ignored on receipt.
skipping to change at page 64, line 24 skipping to change at page 65, line 24
| ERROR CODE | | ERROR CODE |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The following bit-values are defined in network byte order The following bit-values are defined in network byte order
(i.e., big-endian byte order): (i.e., big-endian byte order):
0x01 = Link Verification Procedure not supported. 0x01 = Link Verification Procedure not supported.
0x02 = Unwilling to verify. 0x02 = Unwilling to verify.
0x04 = Unsupported verification transport mechanism. 0x04 = Unsupported verification transport mechanism.
0x08 = Link_Id configuration error. 0x08 = Link_Id configuration error.
0x10 = Unknown object C-Type.
All other values are reserved and should be sent as zero and All other values are reserved and should be sent as zero and
ignored on receipt. 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
skipping to change at page 64, line 48 skipping to change at page 65, line 49
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 in network byte order The following bit-values are defined in network byte order
(i.e., big-endian 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 = Invalid TE_LINK Object.
0x08 = Bad TE Link Object 0x08 = Invalid DATA_LINK Object.
0x10 = Bad Data Link Object 0x10 = Unknown TE_LINK object C-Type.
0x20 = Unknown DATA_LINK object C-Type.
All other values are reserved and should be sent as zero and All other values are reserved and should be sent as zero and
ignored on receipt. 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.
14. Intellectual Property Considerations 14. Intellectual Property Considerations
skipping to change at page 71, line 8 skipping to change at page 72, 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 Class name (suggested = 6) o CONFIG_ID 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)
o VERIFY_ID Class name (suggested = 10) o VERIFY_ID Class name (suggested = 10)
- Type 1 (suggested C-Type = 1) - Type 1 (suggested C-Type = 1)
o TE_LINK_ID Class name (suggested = 11) o TE_LINK Class name (suggested = 11)
- IPv4 TE_LINK_ID (suggested C-Type = 1) - IPv4 TE_LINK (suggested C-Type = 1)
- IPv6 TE_LINK_ID (suggested C-Type = 2) - IPv6 TE_LINK (suggested C-Type = 2)
- unnumbered TE_LINK_ID (suggested C-Type = 3) - unnumbered TE_LINK (suggested C-Type = 3)
o DATA_LINK_ID Class name (suggested = 12) o DATA_LINK Class name (suggested = 12)
- IPv4 DATA_LINK_ID (suggested C-Type = 1) - IPv4 DATA_LINK (suggested C-Type = 1)
- IPv6 DATA_LINK_ID (suggested C-Type = 2) - IPv6 DATA_LINK (suggested C-Type = 2)
- unnumbered DATA_LINK_ID (suggested C-Type = 3) - unnumbered DATA_LINK (suggested C-Type = 3)
- Interface Switching Capability (suggested sub-object Type = 1) - Interface Switching Type (suggested sub-object Type = 1)
- Wavelength (suggested sub-object Type = 2) - Wavelength (suggested sub-object Type = 2)
o CHANNEL_STATUS Class name (suggested = 13) o CHANNEL_STATUS Class name (suggested = 13)
- IPv4 INTERFACE_ID (suggested C-Type = 1) - IPv4 INTERFACE_ID (suggested C-Type = 1)
- IPv6 INTERFACE_ID (suggested C-Type = 2) - IPv6 INTERFACE_ID (suggested C-Type = 2)
- unnumbered INTERFACE_ID (suggested C-Type = 3) - unnumbered INTERFACE_ID (suggested C-Type = 3)
o CHANNEL_STATUS_REQUEST Class name (suggested = 14) o CHANNEL_STATUS_REQUEST Class name (suggested = 14)
- IPv4 INTERFACE_ID (suggested C-Type = 1) - IPv4 INTERFACE_ID (suggested C-Type = 1)
- IPv6 INTERFACE_ID (suggested C-Type = 2) - IPv6 INTERFACE_ID (suggested C-Type = 2)
 End of changes. 

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