<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-ccamp-gmpls-rsvp-te-call" target="https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-gmpls-rsvp-te-call-04">
   <front>
      <title>Generalized MPLS (GMPLS) RSVP-TE Signaling Extensions in Support of Calls</title>
      <author initials="A." surname="Farrel" fullname="Adrian Farrel">
         <organization>Old Dog Consulting</organization>
      </author>
      <author initials="D." surname="Papadimitriou" fullname="Dimitri Papadimitriou">
         <organization>Alcatel</organization>
      </author>
      <date month="January" day="23" year="2007" />
      <abstract>
	 <t>In certain networking topologies, it may be advantageous to maintain associations between endpoints and key transit points to support an instance of a service. Such associations are known as Calls.

 A Call does not provide the actual connectivity for transmitting user traffic, but only builds a relationship by which subsequent Connections may be made. In Generalized MPLS (GMPLS) such Connections are known as Label Switched Paths (LSPs).

 This document specifies how GMPLS Resource Reservation Protocol - Traffic Engineering (RSVP-TE) signaling may be used and extended to support Calls. These mechanisms provide full and logical Call/Connection separation.

 The mechanisms proposed in this document are applicable to any environment (including multi-area), and for any type of interface: packet, layer-2, time-division multiplexed, lambda, or fiber switching. [STANDARDS-TRACK]
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-ccamp-gmpls-rsvp-te-call-04" />
   
</reference>
