@techreport{demizu-mpls-vcid-01,
    number =    {draft-demizu-mpls-vcid-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-demizu-mpls-vcid/01/},
    author =    {Noritoshi Demizu and Hiroshi Esaki and Ken-ichi Nagami and Paul Doolan},
    title =     {{VCID: Virtual Connection Identifier}},
    pagetotal = 6,
    year =      1997,
    month =     oct,
    day =       7,
    abstract =  {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.},
}