draft-ietf-mpls-vcid-atm-02.txt   draft-ietf-mpls-vcid-atm-03.txt 
MPLS Working Group Ken-ichi Nagami (Toshiba Corp.) MPLS Working Group Ken-ichi Nagami (Toshiba Corp.)
INTERNET DRAFT Noritoshi Demizu (NAIST) INTERNET DRAFT Noritoshi Demizu (NAIST)
Hiroshi Esaki (Univ. Tokyo) Hiroshi Esaki (Univ. Tokyo)
Yasuhiro Katsube (Toshiba Corp.) Yasuhiro Katsube (Toshiba Corp.)
Paul Doolan (Ennovate Networks) Paul Doolan (Ennovate Networks)
December 1998 April 1999
Expires June 1999 Expires October 1999
VCID Notification over ATM link VCID Notification over ATM link
<draft-ietf-mpls-vcid-atm-02.txt> <draft-ietf-mpls-vcid-atm-03.txt>
Status of this memo Status of this memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft and is in full conformance with
documents of the Internet Engineering Task Force (IETF), its areas, all provisions of Section 10 of RFC2026.
and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as ``work in progress.'' material or to cite them other than as "work in progress."
To view the entire list of current Internet-Drafts, please check the The list of current Internet-Drafrts can be accessed at
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow http://www.ietf.org/ietf/1id-abstracts.txt
Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern
Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific The list of Internet-Draft Shadow Directories can be accessed at
Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). http://www.ietf.org/shadow.html.
Abstract Abstract
The ATM Label Switching Router (ATM-LSR) is one of the major The ATM Label Switching Router (ATM-LSR) is one of the major
applications of label switching. Because the ATM layer labels (VPI applications of label switching. Because the ATM layer labels (VPI
and VCI) associated with a VC rewritten with new value at every ATM and VCI) associated with a VC rewritten with new value at every ATM
switch nodes, it is not possible to use them to identify a VC in switch nodes, it is not possible to use them to identify a VC in
label mapping messages. The concept of Virtual Connection Identifier label mapping messages. The concept of Virtual Connection Identifier
(VCID) is introduced to solve this problem. VCID has the same value (VCID) is introduced to solve this problem. VCID has the same value
at both ends of a VC. This document specifies the procedures for the at both ends of a VC. This document specifies the procedures for the
skipping to change at page 2, line 47 skipping to change at page 2, line 49
We list below the various types of link and briefly mention the VCID We list below the various types of link and briefly mention the VCID
notification procedures employed and the rational for that notification procedures employed and the rational for that
choice. The procedures themselves are discussed in detail in later choice. The procedures themselves are discussed in detail in later
sections. sections.
Transparent point-to-point link : no VCID notification Transparent point-to-point link : no VCID notification
VCID notification procedure is not necessary because the label VCID notification procedure is not necessary because the label
(i.e., VPI/VCI) is the same at each end of the VC. (i.e., VPI/VCI) is the same at each end of the VC.
VP : inband notification or no notification VP : inband notification or VPID notification or no notification
- Inband notification - Inband notification
VCID notification is needed because the VPI at each end of the VC VCID notification is needed because the VPI at each end of the VC
may not be the same. Inband VCID notification [VCID] is used in may not be the same. Inband VCID notification is used in this
this case. case.
- VPID notification
VCID notification is needed because the VPI at each end of the VC
may not be the same. VPID notification is used in this case.
- No notification - No notification
If a node has only one VP to a neighboring node, VCID notification If a node has only one VP to a neighboring node, VCID notification
procedure is not mandatory. The VCI can be used as the VCID. This procedure is not mandatory. The VCI can be used as the VCID. This
is because the VCI value is the same at each end of the VP. is because the VCI value is the same at each end of the VP.
PVC : inband notification PVC : inband notification
Inband VCID notification [VCID] is used in this case because the Inband VCID notification is used in this case because the labels
labels at each end of the VC may not be the same. at each end of the VC may not be the same.
SVC : there are three possibilities SVC : there are three possibilities
- Outband notification - Outband notification
If a signaling message has a field which is large enough to carry If a signaling message has a field which is large enough to carry
a VCID value (e.g., GIT [GIT]), then the VCID is carried directly a VCID value (e.g., GIT [GIT]), then the VCID is carried directly
in it. in it.
- Outband notification using a small-sized field - Outband notification using a small-sized field
If a signaling message has a field which is not large enough to If a signaling message has a field which is not large enough to
carry a VCID value, this procedure is used. carry a VCID value, this procedure is used.
skipping to change at page 3, line 29 skipping to change at page 3, line 36
- Inband notification - Inband notification
If a signaling message can not carry user information, this If a signaling message can not carry user information, this
procedure is used. procedure is used.
When an LSP is a point-to-multipoint VC and an ATM switch in an When an LSP is a point-to-multipoint VC and an ATM switch in an
LSR is not capable of VC merge, it may cause problems in LSR is not capable of VC merge, it may cause problems in
performance and quality of service. When the LSR wants to add a performance and quality of service. When the LSR wants to add a
new leaf to the LSP, it needs to split the active LSP temporarily new leaf to the LSP, it needs to split the active LSP temporarily
to send an inband notification message. to send an inband notification message.
2.2 VC direction
A VC has a directionality. The VCID procedure for a VC is always
triggered from the upstream node of the VC, i.e., the upstream node
notifies the downstream node of the VCID.
If bidirectional use of a label switched VC is allowed, the label
switched VC is said to be bidirectional. In this case, two VCID
procedures are taken, one for each direction.
If bidirectional use of a label switched VC is not allowed, the label
switched VC is said to be unidirectional. In this case, only one
VCID procedure is taken for the allowed direction.
VC directionality is communicated through LDP.
3. VCID Notification Procedures 3. VCID Notification Procedures
3.1 Inband Notification Procedures 3.1 Inband Notification Procedures
3.1.1 Inband Notification for Point-to-point VC 3.1.1 Inband Notification for Point-to-point VC
VCID notification is performed by transmitting a control message VCID notification is performed by transmitting a control message
through the VC newly established (by signalling or management) for through the VC newly established (by signalling or management) for
use as an label switched path (LSP) [FRAME]. The procedure for VCID use as an label switched path (LSP) [FRAME]. The procedure for VCID
notification between two nodes A and B is detailed below. notification between two nodes A and B is detailed below.
0. The node A establishes a VC to the destination node B. (by signalling 0. The node A establishes a VC to the destination node B. (by signalling
or management) or management)
1. The node A selects a VCID value. 1. The node A selects a VCID value.
skipping to change at page 8, line 34 skipping to change at page 9, line 5
Node A Node B Node A Node B
| | | |
|--------------->| ATM signaling with VCID |--------------->| ATM signaling with VCID
|<---------------| |<---------------|
| | | |
|--------------->| LDP Label Request |--------------->| LDP Label Request
| | | |
|<---------------| LDP Label Mapping |<---------------| LDP Label Mapping
4 VCID Message Format 4 VPID Notification Procedure
4.1 VCID Messages
The approach that is used for the VCID notification procedure is also
applicable to share the same identifier between both ends for a VP.
VPID notification procedure is defined for this purpose.
A distinct VPID notification procedure is performed for each
direction of each VP.
After the VPID notification is finished for a VP, a VCID of a VC in
the VP is constructed with the VPID(MSB) and VCI(LSB) of the VC. The
VCID can be used by LDP without performing VCID notification
procedure. The message sequence is given below.
1. An upstream node sends the VPID PROPOSE message.
In the case of bidirectional label switched VC, both the upstream
and downstream nodes use VCI=33. In the case of unidirectional
label switched VC, the node which has larger LDP Identifier uses
VCI=33 and the other node uses VCI=34. Note that VCI=32, which is
used for unlabeled packet transfer, is not used for VPID
notification procedure so that the same encapsulation method can
be applied for both VPID procedure and inband VCID procedure.
2. The downstream node sends the VPID ACK message.
3. The upstream node sends the LDP Label Request message.
4. The downstream node sends the LDP Label Mapping message.
5 VCID Message Format
5.1 VCID Messages
An LDP VCID message consists of the LDP [LDP] fixed header followed An LDP VCID message consists of the LDP [LDP] fixed header followed
by one or more VCID TLV. VCID PROPOSE inband message is sent as a by one or more TLV. A VCID PROPOSE inband message and a VPID PROPOSE
null encapsulation packet through a VC to be used as an LSP. There is message are sent as a null encapsulation packet through a VC to be
only the label stack header before the LDP VCID PDU. A label value in used as an LSP. There is only the label stack header before the LDP
the label stack entry [ENCAPS] for VCID PROPOSE inband message is 4. VCID PDU. A label value in the label stack entry [ENCAPS] for the
VCID PROPOSE inband message and the VPID PROPOSE message are 4.
Other messages are sent as TCP packets. This is the same as LDP. Other messages are sent as TCP packets. This is the same as LDP.
The VCID message type field is as follows: The VCID message type field is as follows:
VCID Propose inband Message = 0x0501 VCID Propose inband Message = 0x0501
VCID Propose Message = 0x0502 VCID Propose Message = 0x0502
VCID ACK Message = 0x0503 VCID ACK Message = 0x0503
VCID NACK Message = 0x0504 VCID NACK Message = 0x0504
VPID Propose inband Message = 0x0505
VPID ACK Message = 0x0506
VPID NACK Message = 0x0507
4.1.1 VCID Propose inband Message 5.1.1 VCID Propose inband Message
This message is sent as a null encapsulation packet with LDP header This message is sent as a null encapsulation packet with LDP header
and label stack header through a VC to be used as an LSP. The label and label stack header through a VC to be used as an LSP. The label
value is 4. The reserved label value is required because the value is 4. The reserved label value is required because the
downstream node may receive this message after receiving the LDP downstream node may receive this message after receiving the LDP
Label Request message in the case of point-to-multipoint VC. The Label Request message in the case of point-to-multipoint VC. The
downstream node must distinguish the VCID PROPOSE message from other downstream node must distinguish the VCID PROPOSE message from other
messages and ignore the VCID PROPOSE message when the node already messages and ignore the VCID PROPOSE message when the node already
received the LDP Label Request message for the VC. received the LDP Label Request message for the VC.
0 1 2 3 0 1 2 3
skipping to change at page 9, line 28 skipping to change at page 10, line 31
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optional Parameters | | Optional Parameters |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Message Id Message Id
Four octet integer used to identify this message. Four octet integer used to identify this message.
Label TLV Label TLV
Label TLV contains VCID value. Type of label TLV is VCID(0x0203). Label TLV contains VCID value. Type of label TLV is VCID(0x0203).
4.1.2 VCID Propose Message 5.1.2 VCID Propose Message
An LSR uses the VCID PROPOSE message for the VCID notification An LSR uses the VCID PROPOSE message for the VCID notification
procedure of the outband notification using a small-sized field. procedure of the outband notification using a small-sized field.
This message is sent through the VC for the LDP. This message is sent through the VC for the LDP.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U| VCID Propose (0x0502) | Message Length | |U| VCID Propose (0x0502) | Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message ID | | Message ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Label TLV | | Label TLV |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Temporary ID TLV | | Temporary ID TLV |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optional Parameters | | Optional Parameters |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Message Id Message ID
Four octet integer used to identify this message. Four octet integer used to identify this message.
Label TLV Label TLV
Label TLV contains VCID value. Type of label TLV is VCID(0x0203). Label TLV contains VCID value. Type of label TLV is VCID(0x0203).
Temporary ID TLV Temporary ID TLV
The value carried in the user specific field in the layer 3 The value carried in the user specific field in the layer 3
protocol field in the BLLI ID in the ATM Forum UNI 3.1/4.0 protocol field in the BLLI ID in the ATM Forum UNI 3.1/4.0
Type of label TLV is VCID temporary ID(0x0902). Type of label TLV is VCID temporary ID(0x0702).
4.1.3 VCID ACK Message 5.1.3 VCID ACK Message
An LSR send the VCID ACK message when the LSR accepts the VCID An LSR send the VCID ACK message when the LSR accepts the VCID
PROPOSE message. PROPOSE message.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U| VCID ACK (0x0503) | Message Length | |U| VCID ACK (0x0503) | Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message ID | | Message ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Label TLV | | Label TLV |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VCID Message ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optional Parameters | | Optional Parameters |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Message Id Message ID
Four octet integer used to identify this message. This value is the Four octet integer used to identify this message.
same as that of received VCID PROPOSE message.
Label TLV Label TLV
The label TLV contains the VCID value of the received VCID PROPOSE The label TLV contains the VCID value of the received VCID PROPOSE
message. Type of label TLV is VCID(0x0203). message. Type of label TLV is VCID(0x0203).
4.1.4 VCID NACK Message VCID Message ID
This value is the same as that of received VCID PROPOSE message.
5.1.4 VCID NACK Message
An LSR send the VCID NACK message when the LSR does not accept the An LSR send the VCID NACK message when the LSR does not accept the
VCID PROPOSE message. VCID PROPOSE message.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U| VCID NACK (0x0504) | Message Length | |U| VCID NACK (0x0504) | Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message ID | | Message ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Label TLV | | Label TLV |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VCID Message ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optional Parameters | | Optional Parameters |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Message ID
Message Id Four octet integer used to identify this message.
Four octet integer used to identify this message. This value is the
same as that of received VCID PROPOSE message.
Label TLV Label TLV
The label TLV contains the VCID value of the received VCID PROPOSE The label TLV contains the VCID value of the received VCID PROPOSE
message. Type of label TLV is VCID(0x0203). message. Type of label TLV is VCID(0x0203).
4.2 Objects VCID Message ID
4.2.1 VCID Label TLV This value is the same as that of received VCID PROPOSE message.
5.1.5 VPID Propose inband Message
This message is sent as a null encapsulation packet with LDP header
and label stack header through a VC to be used as an LSP. The label
value is 4. The downstream node must distinguish the VPID PROPOSE
message from other messages and ignore the VPID PROPOSE message when
the node already received the LDP Label Request message for the VC.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|VPID Inband Propose (0x0505) | Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VPID TLV |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optional Parameters |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Message Id
Four octet integer used to identify this message.
VPID TLV
VPID TLV contains VPID value. Type of label TLV is VPID(0x0703).
5.1.6 VPID ACK Message
An LSR send the VPID ACK message when the LSR accepts the VPID
PROPOSE message.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U| VPID ACK (0x0506) | Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VPID TLV |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VCID Message ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optional Parameters |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Message ID
Four octet integer used to identify this message.
VPID TLV
The VPID TLV contains the VPID value of the received VPID PROPOSE
message.
VCID Message ID
This value is the same as that of received VCID PROPOSE message.
5.1.7 VPID NACK Message
An LSR send the VPID NACK message when the LSR accepts the VPID
PROPOSE message.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U| VPID NACK (0x0507) | Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VPID TLV |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VCID Message ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optional Parameters |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Message ID
Four octet integer used to identify this message.
VPID TLV
The VPID TLV contains the VPID value of the received VPID PROPOSE
message.
VCID Message ID
This value is the same as that of received VCID PROPOSE message.
5.2 Objects
5.2.1 VCID Label TLV
An LSR uses VCID Label TLV to encode labels for use on the link which An LSR uses VCID Label TLV to encode labels for use on the link which
does not have the same data link label at both ends of a VC. does not have the same data link label at both ends of a VC.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|F|VCID Label (0x0203) | Length | |U|F|VCID Label (0x0203) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VCID | | VCID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
VCID VCID
This is 4 byte VCID value. This is 4 byte VCID value.
4.2.2 VCID Temporary ID TLV 5.2.2 VCID Message ID TLV
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|F|VCID Message ID(0x0701) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VCID Message ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
VCID Message ID
This is 4 byte VCID Message ID
5.2.3 VCID Temporary ID TLV
An LSR uses the VCID temporary ID TLV for the VCID notification An LSR uses the VCID temporary ID TLV for the VCID notification
procedure of the outband notification using a small-sized field. procedure of the outband notification using a small-sized field.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|F| VCID Temporary ID (0x0601)| Length | |U|F| VCID Temporary ID (0x0702)| Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Temporary ID | | Temporary ID |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Temporary ID: Temporary ID:
The value carried in the user specific field in the layer 3 The value carried in the user specific field in the layer 3
protocol field in the BLLI ID in the ATM Forum UNI 3.1/4.0 protocol field in the BLLI ID in the ATM Forum UNI 3.1/4.0
Security Considerations 5.2.4 VPID Label TLV
Security issues are not discussed in this document. An LSR uses VPID TLV for the VPID notification procedure.
Intellectual Property Considerations 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|F| VPID (0x0703) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VPID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
VPID
This is 2 byte VPID value.
Toshiba Corporation and Ennovate Networks may seek patent or other Security Considerations
intellectual property protection for some of the aspects of the
technology discussed in this document. If any standards arising from Security issues are not discussed in this document.
this document are or become protected by one or more patents assigned
to Toshiba Corporation, Toshiba intends to license them on reasonable
and non- discriminatory terms.
Acknowledgments Acknowledgments
The authors would like to acknowledge the valuable technical comments The authors would like to acknowledge the valuable technical comments
of Shigeo Matsuzawa, Akiyoshi Mogi, Muneyoshi Suzuki, George Swallow of Yoshihiro Ohba, Shigeo Matsuzawa, Akiyoshi Mogi, Muneyoshi Suzuki,
and members of the LAST-WG of the WIDE Project. George Swallow and members of the LAST-WG of the WIDE Project.
References References
[VCID] N. Demizu, et al., "VCID: Virtual Connection Identifier", [VCID] N. Demizu, et al., "VCID: Virtual Connection Identifier",
draft-demizu-mpls-vcid-01.txt, Oct. 1997 draft-demizu-mpls-vcid-01.txt, Oct. 1997
[VCPOOL] N. Demizu, et al., "VC pool", [VCPOOL] N. Demizu, et al., "VC pool",
draft-demizu-mpls-vcpool-00.txt, Oct. 1997 draft-demizu-mpls-vcpool-00.txt, Oct. 1997
[LDP] L. Andersson, et al., "LDP Specification", [LDP] L. Andersson, et al., "LDP Specification",
draft-ietf-mpls-ldp-02.txt, Nov. 1998 draft-ietf-mpls-ldp-03.txt, Jan. 1999
[FRAME] R. Callon, et al., "A Framework for Multiprotocol Label [FRAME] R. Callon, et al., "A Framework for Multiprotocol Label
Switching", draft-ietf-mpls-framework-02.txt, Nov. 1997 Switching", draft-ietf-mpls-framework-02.txt, Nov. 1997
[GIT] M. Suzuki, "The Assignment of the Information Field and [GIT] M. Suzuki, "The Assignment of the Information Field and
Protocol Identifier in the Q.2941 Generic Identifier and Q.2957 Protocol Identifier in the Q.2941 Generic Identifier and Q.2957
User-to-user Signaling for the Internet Protocol", User-to-user Signaling for the Internet Protocol",
draft-ietf-mpls-git-uus-01.txt, Dec. 1998 draft-ietf-mpls-git-uus-02.txt, March 1999
[ENCAPS] E. Rosen, et al., "MPLS Label Stack Encoding", [ENCAPS] E. Rosen, et al., "MPLS Label Stack Encoding",
draft-ietf-mpls-label-encaps-03.txt, Sep. 1998 draft-ietf-mpls-label-encaps-03.txt, Sep. 1998
Authors Information Authors Information
Ken-ichi Nagami Ken-ichi Nagami
Infomation & Communication Lab., Toshiba Corporation, Infomation & Communication Lab., Toshiba Corporation,
3-1-1 Asahigaoka, Hino, 3-1-1 Asahigaoka, Hino,
Tokyo, 191-8555, Japan Tokyo, 191-8555, Japan
 End of changes. 

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