The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2003-Jan> msg00156



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

draft-yasukawa-mpls-rsvp-p2mp-00.txt

  • From: Kunihiro Ishiguro <kunihiro@ipinfusion.com>
  • Date: Wed, 29 Jan 2003 09:12:36 -0800
  • Cc: "Seisho Yasukawa" <yasukawa.seisho@lab.ntt.co.jp>, <mpls@UU.NET>, "LARREUR-HEMON Elodie FTRD/DAC/LAN" <elodie.larreur@rd.francetelecom.com>, <akullber@netplane.com>, <DCheng@PolarisNetworks.com>, <Dimitri.Papadimitriou@alcatel.be>, <mjork@avici.com>
  • User-Agent: Wanderlust/2.10.0 (Venus) SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.3 Emacs/21.2.92 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI)

>I agree with you. It is important to well separate mutlicast service
>from P2MP LSP setup / 
>modification, as P2MP tree can support non-IP Mcast traffic.

This is good point.  We should separate P2MP LSP setup and multicast
traffic mapping.  I think Yasukawa's main motivation of changing draft
name from old 'rsvp-multicast' to 'rsvp-p2mp' resides in it.

Actually we can use any kind of P2MP LSP for multicast traffic
mapping.  At the same time P2MP LSP is not limited to use for
multicast traffic.  I believe this topic should be discussed at here.
-- 
Kunihiro Ishiguro