Skip to main content

VCID: Virtual Connection Identifier

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Noritoshi Demizu , Hiroshi Esaki , Ken-ichi Nagami , Paul Doolan
Last updated 1997-10-07
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Several label switching schemes have been proposed to fuse and integrate the cost-performance and QoS assurance of Layer 2 devices and the flexibility and functionality of Layer 3 protocols. Some of these proposals assume that Label Switching Routers (LSRs) are placed in a homogeneous LSR cloud in a campus area network or a backbone network, and they are connected directly to each other. However, this assumption sometimes does not hold true in the real situation. For example, some campuses will be connected via ATM SVC service, and LSR networks will be constructed hierarchically. To deal with Virtual Connections (VCs) in these environments, this document proposes to identify a VC with a VCID instead of a label.


Noritoshi Demizu
Hiroshi Esaki
Ken-ichi Nagami
Paul Doolan

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)