Re: [pim] New PIM Charter and milestones

[Yakov Rekhter <yakov at juniper.net>]

John,

> > -----Original Message-----
> > From: Rahul Aggarwal [mailto:rahul at juniper.net] 
> > Sent: Sunday, January 28, 2007 11:36 AM
> > To: Michael McBride (mmcbride)
> > Cc: pim at ietf.org
> > Subject: Re: [pim] New PIM Charter and milestones
> > 
> > 
> > Hi Mike,
> > 
> > Please see below:
> > 
> > On Fri, 26 Jan 2007, Mike McBride wrote:
> > 
> > > Here is a second pass at pimwg rechartering text. Please review. I 
> > > added a 'may' with BSR which 'may' satisfy Lenny's previous concern.
> > >
> > > Description of Working Group:
> > >
> > > The Protocol Independent Multicast (PIM) Working Group has 
> > completed 
> > > the standardization of PIM with RFC 4601. The WG has 
> > determined there 
> > > is additional work to be accomplished and is chartered to 
> > standardize 
> > > extensions to RFC 4601 - Protocol Independent Multicast Version 2 - 
> > > Sparse Mode. These PIM extensions could involve multipoint label 
> > > switching,
> > 
> > "multipoint label switching" is within the charter of the 
> > MPLS WG. This shouldn't be a charter item in the PIM WG.
> 
> PIM WG should address any/all pim enhancement
> work necessary to support ongoing multipoint label switching
> 
> btw, its logical to expect that a system effecting several protocols
> has work in more than one working group
> 
> > > reliability, resiliency, scalability, management, security and VPNs.
> > 
> > Multicast in L2VPNs is in the charter of L2VPN WG, and 
> > multicast in L3VPNs is in the charter of L3VPN WG. VPNs 
> > shouldn't be a charter item in the PIM WG.
> 
> again, PIM WG should address PIM related components of *VPN
> systems.  

Yes, assuming that multicast in L2VPNs and L3VPNs require extensions
to PIM. Whether such extensions are required is to be determined
by L2VPN and L3VPN WGs. With this in mind the charter instead of
saying that "These PIM extensions could involved... VPNs" should
say the following:

   If L2VPN or L3VPN WGs determine that support for multicast
   in L2VPNs and/or L3VPNs requires extensions to PIM, then such 
   extensions could be developed within the PIM WG.

Yakov.

_______________________________________________
pim mailing list
pim at ietf.org
https://www1.ietf.org/mailman/listinfo/pim