--- 1/draft-ietf-mpls-multicast-05.txt 2006-02-05 00:41:54.000000000 +0100 +++ 2/draft-ietf-mpls-multicast-06.txt 2006-02-05 00:41:54.000000000 +0100 @@ -1,25 +1,26 @@ + Network Working Group D. Ooms, B. Sales Internet Draft Alcatel -Expiration Date: July 2001 W. Livens +Expiration Date: May 2002 W. Livens Colt Telecom A. Acharya IBM F. Griffoul Ulticom F. Ansari Bell Labs - January 2001 + November 2001 Framework for IP Multicast in MPLS - draft-ietf-mpls-multicast-05.txt + draft-ietf-mpls-multicast-06.txt Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. 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. @@ -114,20 +115,24 @@ RSVP Resource reSerVation Protocol SPT-bit Shortest Path Tree [DEER] SSM Source Specific Multicast TCP Transmission Control Protocol UDP User Datagram Protocol VC Virtual Circuit VCI Virtual Circuit Identifier VP Virtual Path VPI Virtual Path Identifier + Changes: + 02->05 (problem in IETF db): incorporate WG last call comments + 05->06: no changes + 1. Introduction In an MPLS cloud the routes are determined by a L3 routing protocol. These routes can then be mapped onto L2 paths to enhance network performance. Besides this, MPLS offers a vehicle for enhanced network services such as QoS/CoS, traffic engineering, etc. Current unicast routing protocols generate a same (optimal) shortest path in steady state for a certain (source, destination)-pair. Remark that unicast protocols can behave slightly different with regard to