Tue, 07 August 2007 02:33 UTC
Return-path: <pim-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IIEtF-0001lz-8k; Mon, 06 Aug 2007 22:33:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IIEtD-0001lc-N6; Mon, 06 Aug 2007 22:33:43 -0400
Received: from [202.99.23.227] (helo=people.com.cn) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IIEtC-000172-Ei; Mon, 06 Aug 2007 22:33:43 -0400
Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm5e46b80a1b; Tue, 07 Aug 2007 10:45:26 +0800
Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jma746b33ce1; Fri, 03 Aug 2007 16:44:30 +0800
Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm1246adb688; Mon, 30 Jul 2007 17:19:07 +0800
Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm046a78a41; Wed, 25 Jul 2007 20:00:39 +0800
Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id AISP action; Wed, 25 Jul 2007 20:00:38 +0800
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ID1Uy-0005bm-4E; Mon, 23 Jul 2007 13:15:08 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ID1Us-0005Gt-Hw; Mon, 23 Jul 2007 13:15:02 -0400
Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ID1Us-0002qn-4C; Mon, 23 Jul 2007 13:15:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com Multicast (PIM) Working Group has completed the
X-Message-ID:
Message-ID: <20140418084536.2560.83460.ARCHIVE@ietfa.amsl.com>
X-Date: (the original message had no date)
Date: Tue, 07 Aug 2007 09:33:45 -0000
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 will involve reliability, resiliency, scalability, management, and security. The PIM WG will consider implications of VPN service on PIM when it's a component of that service or when PIM interfaces with that service at a VPN edge. 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. Additional work on the PIM-BIDIR and BSR drafts may also be necessary by the WG as these drafts progress through Standards Track. The working group will continue to specify the MIB modules required for PIM and its enhancements. The PIM WG will further enhance RFC4601 as an even more scalable, efficient and robust multicast routing protocol, which is capable of supporting thousands of groups, different types of multicast applications, and all major underlying layer-2 subnetwork technologies. We will accomplish these enhancements by submitting drafts, to the IESG, involving reliable pim, pim join attributes and pim authentication. The working group will initiate a new re-chartering effort if it is determined that a Version 3 of PIM is required. Goals and Milestones: Jul 2007 Ratify new WG charter and milestones Dec 2007 Submit the BSR spec as a Proposed Standard to the IESG Dec 2007 Submit the BSR MIB as a Proposed Standard to the IESG Mar 2008 Submit a more reliable pim solution (refresh reduction) to the IESG Mar 2008 Submit a generic TLV PIM Join Attribute PS draft to the IESG Mar 2008 Submit RPF Vector (use of PIM Join Attribute) as PS to the IESG Mar 2008 Submit a way to authenticate PIM link local messages as PS to the IESG Mar 2008 Submit an Informational PIM last hop threats document to the IESG _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ pim mailing list pim@ietf.org https://www1.ietf.org/mailman/listinfo/pim