
From internet-drafts@ietf.org  Mon Oct  3 14:45:33 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CCC321F8EE7; Mon,  3 Oct 2011 14:45:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.586
X-Spam-Level: 
X-Spam-Status: No, score=-102.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9GujrOHhcpbF; Mon,  3 Oct 2011 14:45:32 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92AB721F8EF1; Mon,  3 Oct 2011 14:45:32 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.60
Message-ID: <20111003214532.25066.68116.idtracker@ietfa.amsl.com>
Date: Mon, 03 Oct 2011 14:45:32 -0700
Cc: pim@ietf.org
Subject: [pim] I-D Action: draft-ietf-pim-rfc4601bis-00.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Oct 2011 21:45:33 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Protocol Independent Multicast Workin=
g Group of the IETF.

	Title           : Protocol Independent Multicast - Sparse Mode (PIM-SM): P=
rotocol Specification (Revised)
	Author(s)       : Bill Fenner
                          Mark Handley
                          Hugh Holbrook
                          Isidor Kouvelas
                          Rishabh Parekh
                          Zhaohui (Jeffrey) Zhang
                          Lianshu Zheng
	Filename        : draft-ietf-pim-rfc4601bis-00.txt
	Pages           : 132
	Date            : 2011-09-29

   This document specifies Protocol Independent Multicast - Sparse Mode
   (PIM-SM).  PIM-SM is a multicast routing protocol that can use the
   underlying unicast routing information base or a separate multicast-
   capable routing information base.  It builds unidirectional shared
   trees rooted at a Rendezvous Point (RP) per group, and optionally
   creates shortest-path trees per source.

   This document addresses errata filed against RFC 4601, and removes
   the optional (*,*,RP) feature that lacks sufficient deployment
   experience.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pim-rfc4601bis-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-pim-rfc4601bis-00.txt

From zzhang@juniper.net  Wed Oct  5 03:33:24 2011
Return-Path: <zzhang@juniper.net>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BC4621F8C30 for <pim@ietfa.amsl.com>; Wed,  5 Oct 2011 03:33:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aJ1k3EQk7b5g for <pim@ietfa.amsl.com>; Wed,  5 Oct 2011 03:33:23 -0700 (PDT)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by ietfa.amsl.com (Postfix) with ESMTP id 894FD21F8A95 for <pim@ietf.org>; Wed,  5 Oct 2011 03:33:23 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP;  Wed, 05 Oct 2011 03:36:31 PDT
Received: from P-EMHUB11-HQ.jnpr.net (172.24.192.58) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.83.0; Wed, 5 Oct 2011 03:35:00 -0700
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB11-HQ.jnpr.net (172.24.192.58) with Microsoft SMTP Server (TLS) id 8.3.83.0; Wed, 5 Oct 2011 03:34:59 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Wed, 5 Oct 2011 06:34:59 -0400
From: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
To: Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Date: Wed, 5 Oct 2011 06:34:57 -0400
Thread-Topic: [pim] Adoption of draft-asaeda-mboned-explicit-tracking-02 as a	pim wg doc
Thread-Index: Acx+SCIhzJDxd0ZfS7SnuVxypY4g0AFAj0ng
Message-ID: <13205C286662DE4387D9AF3AC30EF456D74606E034@EMBX01-WF.jnpr.net>
References: <8999C52267AF8844B77A280D0CD584C13B46CE2CB9@FTI2K3CMSMBX1.forsythe.com> <CAL3FGfzY9RerhyeaWFsxBCx51D7=MeWsh6-ZuKM5uBNJ2Y9WAw@mail.gmail.com>
In-Reply-To: <CAL3FGfzY9RerhyeaWFsxBCx51D7=MeWsh6-ZuKM5uBNJ2Y9WAw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pim] Adoption of draft-asaeda-mboned-explicit-tracking-02 as a	pim wg doc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Oct 2011 10:33:24 -0000

Support.

> -----Original Message-----
> From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On=20
> Behalf Of Mike McBride
> Sent: Wednesday, September 28, 2011 9:35 PM
> To: pim@ietf.org
> Subject: Re: [pim] Adoption of=20
> draft-asaeda-mboned-explicit-tracking-02 as a pim wg doc
>=20
> An informational pim-explicit-tracking document seems most appropriate
> to me (and, at this point, the only apparent way to have consensus for
> adoption in pim).
>=20
> Please consider adopting the document as informational and=20
> speak up either way.
>=20
> mike=

From mmcbride@forsythe.com  Fri Oct  7 15:52:08 2011
Return-Path: <mmcbride@forsythe.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0DE321F8888 for <pim@ietfa.amsl.com>; Fri,  7 Oct 2011 15:52:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.349
X-Spam-Level: 
X-Spam-Status: No, score=-3.349 tagged_above=-999 required=5 tests=[AWL=0.251,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r+v3I8HgPn6h for <pim@ietfa.amsl.com>; Fri,  7 Oct 2011 15:52:08 -0700 (PDT)
Received: from ftiironport2.forsythe.com (smtp2.forsythe.com [12.171.5.20]) by ietfa.amsl.com (Postfix) with ESMTP id 2581621F88B6 for <pim@ietf.org>; Fri,  7 Oct 2011 15:52:08 -0700 (PDT)
From: Mike McBride <mmcbride@forsythe.com>
To: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
Date: Fri, 7 Oct 2011 17:55:17 -0500
Thread-Topic: [pim] Adoption of draft-asaeda-mboned-explicit-tracking-02 as a pim wg doc
Thread-Index: Acx+SCIhzJDxd0ZfS7SnuVxypY4g0AFAj0ngAH3juEA=
Message-ID: <8999C52267AF8844B77A280D0CD584C13B46DB9F2B@FTI2K3CMSMBX1.forsythe.com>
References: <8999C52267AF8844B77A280D0CD584C13B46CE2CB9@FTI2K3CMSMBX1.forsythe.com> <CAL3FGfzY9RerhyeaWFsxBCx51D7=MeWsh6-ZuKM5uBNJ2Y9WAw@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D74606E034@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D74606E034@EMBX01-WF.jnpr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] Adoption of draft-asaeda-mboned-explicit-tracking-02 as a pim wg doc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Oct 2011 22:52:08 -0000

And with that we have rough consensus. Hitoshi, please resubmit as an infor=
mational pim document (pim-explicit-tracking-00).

thanks,
mike

> -----Original Message-----
> From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of
> Jeffrey (Zhaohui) Zhang
> Sent: Wednesday, October 05, 2011 3:35 AM
> To: Mike McBride; pim@ietf.org
> Subject: Re: [pim] Adoption of draft-asaeda-mboned-explicit-tracking-02
> as a pim wg doc
>=20
> Support.
>=20
> > -----Original Message-----
> > From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On
> > Behalf Of Mike McBride
> > Sent: Wednesday, September 28, 2011 9:35 PM
> > To: pim@ietf.org
> > Subject: Re: [pim] Adoption of
> > draft-asaeda-mboned-explicit-tracking-02 as a pim wg doc
> >
> > An informational pim-explicit-tracking document seems most
> appropriate
> > to me (and, at this point, the only apparent way to have consensus
> for
> > adoption in pim).
> >
> > Please consider adopting the document as informational and
> > speak up either way.
> >
> > mike
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim
NOTICE OF CONFIDENTIALITY: =20
The information contained in this email transmission is confidential inform=
ation which may contain information that is legally privileged and prohibit=
ed from disclosure under applicable law or by contractual agreement.  The i=
nformation is intended solely for the use of the individual or entity named=
 above. =20
If you are not the intended recipient, you are hereby notified that any dis=
closure, copying, distribution or taking of any action in reliance on the c=
ontents of this email transmission is strictly prohibited. =20
If you have received this email transmission in error, please notify us imm=
ediately by telephone to arrange for the return of the original transmissio=
n to us.


From prvs=257d2e97d=Jonathan.Nicholas@itt.com  Mon Oct 10 08:05:12 2011
Return-Path: <prvs=257d2e97d=Jonathan.Nicholas@itt.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDBE221F8C3E for <pim@ietfa.amsl.com>; Mon, 10 Oct 2011 08:05:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LDC9c6u5-X+Q for <pim@ietfa.amsl.com>; Mon, 10 Oct 2011 08:05:11 -0700 (PDT)
Received: from cip-fwa-c1.itt.com (cip-fwa-c1.itt.com [151.190.252.21]) by ietfa.amsl.com (Postfix) with ESMTP id AA89021F8C3D for <pim@ietf.org>; Mon, 10 Oct 2011 08:05:11 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: At4AAE8Ik04KHOwH/2dsb2JhbABDmG+QJgeBUwEBAQEDAQEBaxcEAgEIEQQBASgHJwsUCQgBAQQTCAGHfLhahmJhBI5XAQGXDA
X-IronPort-AV: E=Sophos;i="4.68,517,1312156800"; d="scan'208";a="149690171"
Received: from usfwa1exhub3.itt.net ([10.28.236.7]) by cip-fwa-c1.itt.com with ESMTP/TLS/AES128-SHA; 10 Oct 2011 15:05:01 +0000
Received: from usfwa1exmbx3.itt.net ([fe80::b9c6:1df5:8949:cb49]) by USFWA1EXHUB3.itt.net ([fe80::11ef:445a:acf4:8c48%10]) with mapi; Mon, 10 Oct 2011 11:05:01 -0400
From: "Nicholas, Jonathan - ES" <Jonathan.Nicholas@itt.com>
To: "pim@ietf.org" <pim@ietf.org>
Date: Mon, 10 Oct 2011 11:04:58 -0400
Thread-Topic: [pim] I-D Action: draft-ietf-pim-rfc4601bis-00.txt
Thread-Index: AcyCFmQEfCq0oKi/Q1iq4gfPCL3t/AFRxjfA
Message-ID: <6C565C0133EA3F478AEC8F5ADB52726A0ACE143F5F@USFWA1EXMBX3.itt.net>
References: <20111003214532.25066.68116.idtracker@ietfa.amsl.com>
In-Reply-To: <20111003214532.25066.68116.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pim] I-D Action: draft-ietf-pim-rfc4601bis-00.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Oct 2011 15:05:12 -0000

All,

In reviewing this draft, I notice that Appendix A has been removed.

While I can understand removing the (*,*,RP) due to lack of deployment expe=
rience, there was a fair amount of useful information that did not involve =
(*,*,RP) in Appendix A.

Is this also due to lack of deployment experience, or is there another reas=
on?

Thank you.

Jonathan Nicholas

> -----Original Message-----
> From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of
> internet-drafts@ietf.org
> Sent: Monday, October 03, 2011 5:46 PM
> To: i-d-announce@ietf.org
> Cc: pim@ietf.org
> Subject: [pim] I-D Action: draft-ietf-pim-rfc4601bis-00.txt
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This draft is a work item of the Protocol Independent
> Multicast Working Group of the IETF.
>
>       Title           : Protocol Independent Multicast - Sparse Mode
> (PIM-SM): Protocol Specification (Revised)
>       Author(s)       : Bill Fenner
>                           Mark Handley
>                           Hugh Holbrook
>                           Isidor Kouvelas
>                           Rishabh Parekh
>                           Zhaohui (Jeffrey) Zhang
>                           Lianshu Zheng
>       Filename        : draft-ietf-pim-rfc4601bis-00.txt
>       Pages           : 132
>       Date            : 2011-09-29
>
>    This document specifies Protocol Independent Multicast - Sparse Mode
>    (PIM-SM).  PIM-SM is a multicast routing protocol that can use the
>    underlying unicast routing information base or a separate multicast-
>    capable routing information base.  It builds unidirectional shared
>    trees rooted at a Rendezvous Point (RP) per group, and optionally
>    creates shortest-path trees per source.
>
>    This document addresses errata filed against RFC 4601, and removes
>    the optional (*,*,RP) feature that lacks sufficient deployment
>    experience.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-pim-rfc4601bis-00.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-pim-rfc4601bis-00.txt
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim

This e-mail and any files transmitted with it may be proprietary and are in=
tended solely for the use of the individual or entity to whom they are addr=
essed. If you have received this e-mail in error please notify the sender.
Please note that any views or opinions presented in this e-mail are solely =
those of the author and do not necessarily represent those of ITT Corporati=
on. The recipient should check this e-mail and any attachments for the pres=
ence of viruses. ITT accepts no liability for any damage caused by any viru=
s transmitted by this e-mail.

From internet-drafts@ietf.org  Mon Oct 10 10:59:01 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED36D21F8C41; Mon, 10 Oct 2011 10:59:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SoAhDmkzr95c; Mon, 10 Oct 2011 10:59:01 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 959CB21F8C19; Mon, 10 Oct 2011 10:59:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.60
Message-ID: <20111010175901.19184.69896.idtracker@ietfa.amsl.com>
Date: Mon, 10 Oct 2011 10:59:01 -0700
Cc: pim@ietf.org
Subject: [pim] I-D Action: draft-ietf-pim-explicit-tracking-00.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Oct 2011 17:59:02 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Protocol Independent Multicast Workin=
g Group of the IETF.

	Title           : IGMP/MLD-Based Explicit Membership Tracking Function for=
 Multicast Routers
	Author(s)       : Hitoshi Asaeda
                          Nicolai Leymann
	Filename        : draft-ietf-pim-explicit-tracking-00.txt
	Pages           : 15
	Date            : 2011-10-10

   This document describes the IGMP/MLD-based explicit membership
   tracking function for multicast routers.  The explicit tracking
   function is useful for accounting and contributes to saving network
   resource and fast leaves (i.e. shortened leave latency).


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pim-explicit-tracking-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-pim-explicit-tracking-00.txt

From mmcbride@forsythe.com  Mon Oct 10 14:17:38 2011
Return-Path: <mmcbride@forsythe.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D431121F8CB2 for <pim@ietfa.amsl.com>; Mon, 10 Oct 2011 14:17:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cDn2Djlt63oX for <pim@ietfa.amsl.com>; Mon, 10 Oct 2011 14:17:38 -0700 (PDT)
Received: from ftiironport2.forsythe.com (smtp2.forsythe.com [12.171.5.20]) by ietfa.amsl.com (Postfix) with ESMTP id 50BA321F8CB0 for <pim@ietf.org>; Mon, 10 Oct 2011 14:17:38 -0700 (PDT)
From: Mike McBride <mmcbride@forsythe.com>
To: "pim@ietf.org" <pim@ietf.org>
Date: Mon, 10 Oct 2011 16:17:36 -0500
Thread-Topic: pop-count ready for wglc?
Thread-Index: AcyHkW9t+ESh7iedTMyCbVD4W1LtJQAZIZVw
Message-ID: <8999C52267AF8844B77A280D0CD584C13B4832FDED@FTI2K3CMSMBX1.forsythe.com>
References: <Acx9gzc1HGUVzzTdSpuDJFMYU7DXugAwxdaA> <8999C52267AF8844B77A280D0CD584C13B46CE2CBA@FTI2K3CMSMBX1.forsythe.com> <CAL3FGfxjXDq682Gp5WN0c2SvJed-qFhjn0tQWe_cs1XpTC0iGw@mail.gmail.com>
In-Reply-To: <CAL3FGfxjXDq682Gp5WN0c2SvJed-qFhjn0tQWe_cs1XpTC0iGw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Subject: Re: [pim] pop-count ready for wglc?
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Oct 2011 21:17:38 -0000

Today begins a two week wglc for draft-ietf-pim-pop-count-04. Please review=
 the draft. Please then comment, on the list, with a thumbs up or a thumbs =
down.

thanks,
mike

http://www.ietf.org/id/draft-ietf-pim-pop-count-04.txt

> -----Original Message-----
> From: Mike McBride
> Sent: Tuesday, September 27, 2011 8:06 PM
> To: pim@ietf.org
> Subject: pop-count ready for wglc?
>=20
> We had consensus (5-0) in the Quebec pimwg meeting to issue a wglc for
> the pim-pop-count draft:
>=20
> http://www.ietf.org/id/draft-ietf-pim-pop-count-04.txt
>=20
>=20
> Before doing so we'd like to bring it to the list. If you feel this
> draft is not ready for wglc please speak up. Otherwise we will begin a
> wglc next week.
>=20
> thanks,
> mike
NOTICE OF CONFIDENTIALITY: =20
The information contained in this email transmission is confidential inform=
ation which may contain information that is legally privileged and prohibit=
ed from disclosure under applicable law or by contractual agreement.  The i=
nformation is intended solely for the use of the individual or entity named=
 above. =20
If you are not the intended recipient, you are hereby notified that any dis=
closure, copying, distribution or taking of any action in reliance on the c=
ontents of this email transmission is strictly prohibited. =20
If you have received this email transmission in error, please notify us imm=
ediately by telephone to arrange for the return of the original transmissio=
n to us.


From wwwrun@rfc-editor.org  Mon Oct 10 17:17:03 2011
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91FD621F8C79; Mon, 10 Oct 2011 17:17:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AUf8axQuSace; Mon, 10 Oct 2011 17:17:03 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 3F04121F8C78; Mon, 10 Oct 2011 17:17:03 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 19C3E98C272; Mon, 10 Oct 2011 17:17:03 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20111011001703.19C3E98C272@rfc-editor.org>
Date: Mon, 10 Oct 2011 17:17:03 -0700 (PDT)
Cc: pim@ietf.org, rfc-editor@rfc-editor.org
Subject: [pim] RFC 6395 on An Interface Identifier (ID) Hello Option for PIM
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Oct 2011 00:17:03 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6395

        Title:      An Interface Identifier (ID) Hello 
                    Option for PIM 
        Author:     S. Gulrajani, S. Venaas
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2011
        Mailbox:    sameerg@cisco.com, 
                    stig@cisco.com
        Pages:      6
        Characters: 11469
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pim-hello-intid-01.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6395.txt

This document defines a new PIM Hello option to advertise an
Interface Identifier that can be used by PIM protocols to uniquely
identify an interface of a neighboring router.  [STANDARDS-TRACK]

This document is a product of the Protocol Independent Multicast Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From rishabhp@gmail.com  Tue Oct 11 10:06:57 2011
Return-Path: <rishabhp@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F139821F8CC0 for <pim@ietfa.amsl.com>; Tue, 11 Oct 2011 10:06:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3+fmKyrzdYSq for <pim@ietfa.amsl.com>; Tue, 11 Oct 2011 10:06:56 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id DBA8521F8E82 for <pim@ietf.org>; Tue, 11 Oct 2011 10:06:55 -0700 (PDT)
Received: by iaby26 with SMTP id y26so10893577iab.31 for <pim@ietf.org>; Tue, 11 Oct 2011 10:06:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/ichWXCjzjrkPBnBtQ2ExuMH+wsyTY+M/mDSVS0fhO0=; b=aNnO1UMHryf5h3mlNmhcj9GXIcuUX1hFz4nfbI0O5J5XkKOH7I80ZbV8KHtYH6k/gD 8NeDHRnl8REh314sfTzvudcjScCNi0alP4I7wdQTj0EyNgdcPdL6aUN2HR8T7y+XXhgR KpEVSTJjLxBgN8wy2wODugNE8wk0oYfEkCe4I=
MIME-Version: 1.0
Received: by 10.231.8.78 with SMTP id g14mr10590957ibg.85.1318352815475; Tue, 11 Oct 2011 10:06:55 -0700 (PDT)
Received: by 10.231.200.194 with HTTP; Tue, 11 Oct 2011 10:06:55 -0700 (PDT)
In-Reply-To: <6C565C0133EA3F478AEC8F5ADB52726A0ACE143F5F@USFWA1EXMBX3.itt.net>
References: <20111003214532.25066.68116.idtracker@ietfa.amsl.com> <6C565C0133EA3F478AEC8F5ADB52726A0ACE143F5F@USFWA1EXMBX3.itt.net>
Date: Tue, 11 Oct 2011 10:06:55 -0700
Message-ID: <CABjMoXZh7M13oEQVkuCfD-v4ReGUPQHj4x6d8ttcoqg4BUj6GQ@mail.gmail.com>
From: Rishabh Parekh <rishabhp@gmail.com>
To: "Nicholas, Jonathan - ES" <Jonathan.Nicholas@itt.com>
Content-Type: multipart/alternative; boundary=001517740d16414e3b04af08ef95
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] I-D Action: draft-ietf-pim-rfc4601bis-00.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Oct 2011 17:06:57 -0000

--001517740d16414e3b04af08ef95
Content-Type: text/plain; charset=ISO-8859-1

Jonathan,
When we decided to remove (*,*,RP), we realized that PMBR functionality as
specified in 4601 would not work without (*,*,RP) state. Hence, we decided
to remove Appendix A.

Regards,
-Rishabh.

On Mon, Oct 10, 2011 at 8:04 AM, Nicholas, Jonathan - ES <
Jonathan.Nicholas@itt.com> wrote:

> All,
>
> In reviewing this draft, I notice that Appendix A has been removed.
>
> While I can understand removing the (*,*,RP) due to lack of deployment
> experience, there was a fair amount of useful information that did not
> involve (*,*,RP) in Appendix A.
>
> Is this also due to lack of deployment experience, or is there another
> reason?
>
> Thank you.
>
> Jonathan Nicholas
>
> > -----Original Message-----
> > From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of
> > internet-drafts@ietf.org
> > Sent: Monday, October 03, 2011 5:46 PM
> > To: i-d-announce@ietf.org
> > Cc: pim@ietf.org
> > Subject: [pim] I-D Action: draft-ietf-pim-rfc4601bis-00.txt
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories. This draft is a work item of the Protocol Independent
> > Multicast Working Group of the IETF.
> >
> >       Title           : Protocol Independent Multicast - Sparse Mode
> > (PIM-SM): Protocol Specification (Revised)
> >       Author(s)       : Bill Fenner
> >                           Mark Handley
> >                           Hugh Holbrook
> >                           Isidor Kouvelas
> >                           Rishabh Parekh
> >                           Zhaohui (Jeffrey) Zhang
> >                           Lianshu Zheng
> >       Filename        : draft-ietf-pim-rfc4601bis-00.txt
> >       Pages           : 132
> >       Date            : 2011-09-29
> >
> >    This document specifies Protocol Independent Multicast - Sparse Mode
> >    (PIM-SM).  PIM-SM is a multicast routing protocol that can use the
> >    underlying unicast routing information base or a separate multicast-
> >    capable routing information base.  It builds unidirectional shared
> >    trees rooted at a Rendezvous Point (RP) per group, and optionally
> >    creates shortest-path trees per source.
> >
> >    This document addresses errata filed against RFC 4601, and removes
> >    the optional (*,*,RP) feature that lacks sufficient deployment
> >    experience.
> >
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-pim-rfc4601bis-00.txt
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > This Internet-Draft can be retrieved at:
> > ftp://ftp.ietf.org/internet-drafts/draft-ietf-pim-rfc4601bis-00.txt
> > _______________________________________________
> > pim mailing list
> > pim@ietf.org
> > https://www.ietf.org/mailman/listinfo/pim
>
> This e-mail and any files transmitted with it may be proprietary and are
> intended solely for the use of the individual or entity to whom they are
> addressed. If you have received this e-mail in error please notify the
> sender.
> Please note that any views or opinions presented in this e-mail are solely
> those of the author and do not necessarily represent those of ITT
> Corporation. The recipient should check this e-mail and any attachments for
> the presence of viruses. ITT accepts no liability for any damage caused by
> any virus transmitted by this e-mail.
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim
>

--001517740d16414e3b04af08ef95
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Jonathan,<br>When we decided to remove (*,*,RP), we realized that PMBR func=
tionality as specified in 4601 would not work without (*,*,RP) state. Hence=
, we decided to remove Appendix A. <br><br>Regards,<br>-Rishabh.<br><br>
<div class=3D"gmail_quote">On Mon, Oct 10, 2011 at 8:04 AM, Nicholas, Jonat=
han - ES <span dir=3D"ltr">&lt;<a href=3D"mailto:Jonathan.Nicholas@itt.com"=
>Jonathan.Nicholas@itt.com</a>&gt;</span> wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex;">
All,<br>
<br>
In reviewing this draft, I notice that Appendix A has been removed.<br>
<br>
While I can understand removing the (*,*,RP) due to lack of deployment expe=
rience, there was a fair amount of useful information that did not involve =
(*,*,RP) in Appendix A.<br>
<br>
Is this also due to lack of deployment experience, or is there another reas=
on?<br>
<br>
Thank you.<br>
<br>
Jonathan Nicholas<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:pim-bounces@ietf.org">pim-bounces@ietf.org</a>=
 [mailto:<a href=3D"mailto:pim-bounces@ietf.org">pim-bounces@ietf.org</a>] =
On Behalf Of<br>
&gt; <a href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</=
a><br>
&gt; Sent: Monday, October 03, 2011 5:46 PM<br>
&gt; To: <a href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a>=
<br>
&gt; Cc: <a href=3D"mailto:pim@ietf.org">pim@ietf.org</a><br>
&gt; Subject: [pim] I-D Action: draft-ietf-pim-rfc4601bis-00.txt<br>
<div><div></div><div class=3D"h5">&gt;<br>
&gt; A New Internet-Draft is available from the on-line Internet-Drafts<br>
&gt; directories. This draft is a work item of the Protocol Independent<br>
&gt; Multicast Working Group of the IETF.<br>
&gt;<br>
&gt; =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : Protocol Independent Multicast=
 - Sparse Mode<br>
&gt; (PIM-SM): Protocol Specification (Revised)<br>
&gt; =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : Bill Fenner<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Mark Handley<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Hugh Holbrook<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Isidor Kouvelas<br=
>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Rishabh Parekh<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Zhaohui (Jeffrey) =
Zhang<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Lianshu Zheng<br>
&gt; =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-ietf-pim-rfc4601bis-00.txt=
<br>
&gt; =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 132<br>
&gt; =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2011-09-29<br>
&gt;<br>
&gt; =A0 =A0This document specifies Protocol Independent Multicast - Sparse=
 Mode<br>
&gt; =A0 =A0(PIM-SM). =A0PIM-SM is a multicast routing protocol that can us=
e the<br>
&gt; =A0 =A0underlying unicast routing information base or a separate multi=
cast-<br>
&gt; =A0 =A0capable routing information base. =A0It builds unidirectional s=
hared<br>
&gt; =A0 =A0trees rooted at a Rendezvous Point (RP) per group, and optional=
ly<br>
&gt; =A0 =A0creates shortest-path trees per source.<br>
&gt;<br>
&gt; =A0 =A0This document addresses errata filed against RFC 4601, and remo=
ves<br>
&gt; =A0 =A0the optional (*,*,RP) feature that lacks sufficient deployment<=
br>
&gt; =A0 =A0experience.<br>
&gt;<br>
&gt;<br>
&gt; A URL for this Internet-Draft is:<br>
&gt; <a href=3D"http://www.ietf.org/internet-drafts/draft-ietf-pim-rfc4601b=
is-00.txt" target=3D"_blank">http://www.ietf.org/internet-drafts/draft-ietf=
-pim-rfc4601bis-00.txt</a><br>
&gt;<br>
&gt; Internet-Drafts are also available by anonymous FTP at:<br>
&gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp:=
//ftp.ietf.org/internet-drafts/</a><br>
&gt;<br>
&gt; This Internet-Draft can be retrieved at:<br>
&gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/draft-ietf-pim-rfc4601bi=
s-00.txt" target=3D"_blank">ftp://ftp.ietf.org/internet-drafts/draft-ietf-p=
im-rfc4601bis-00.txt</a><br>
&gt; _______________________________________________<br>
&gt; pim mailing list<br>
&gt; <a href=3D"mailto:pim@ietf.org">pim@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/pim" target=3D"_blank=
">https://www.ietf.org/mailman/listinfo/pim</a><br>
<br>
</div></div>This e-mail and any files transmitted with it may be proprietar=
y and are intended solely for the use of the individual or entity to whom t=
hey are addressed. If you have received this e-mail in error please notify =
the sender.<br>

Please note that any views or opinions presented in this e-mail are solely =
those of the author and do not necessarily represent those of ITT Corporati=
on. The recipient should check this e-mail and any attachments for the pres=
ence of viruses. ITT accepts no liability for any damage caused by any viru=
s transmitted by this e-mail.<br>

<div><div></div><div class=3D"h5">_________________________________________=
______<br>
pim mailing list<br>
<a href=3D"mailto:pim@ietf.org">pim@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pim" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/pim</a><br>
</div></div></blockquote></div><br>

--001517740d16414e3b04af08ef95--

From vero.zheng@huawei.com  Fri Oct 14 01:33:50 2011
Return-Path: <vero.zheng@huawei.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6622121F8B27 for <pim@ietfa.amsl.com>; Fri, 14 Oct 2011 01:33:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g218m4kJyKKb for <pim@ietfa.amsl.com>; Fri, 14 Oct 2011 01:33:49 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 16BCC21F8B1E for <pim@ietf.org>; Fri, 14 Oct 2011 01:33:49 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LT1005CXROZBE@szxga05-in.huawei.com> for pim@ietf.org; Fri, 14 Oct 2011 16:31:48 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LT100APRROYRN@szxga05-in.huawei.com> for pim@ietf.org; Fri, 14 Oct 2011 16:31:47 +0800 (CST)
Received: from szxeml206-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEL47982; Fri, 14 Oct 2011 16:31:46 +0800
Received: from SZXEML402-HUB.china.huawei.com (10.82.67.32) by szxeml206-edg.china.huawei.com (172.24.2.58) with Microsoft SMTP Server (TLS) id 14.1.270.1; Fri, 14 Oct 2011 16:31:38 +0800
Received: from Z50128Z (10.108.4.67) by smtpscn.huawei.com (10.82.67.32) with Microsoft SMTP Server (TLS) id 14.1.270.1; Fri, 14 Oct 2011 16:31:37 +0800
Date: Fri, 14 Oct 2011 16:31:37 +0800
From: Vero Zheng <vero.zheng@huawei.com>
X-Originating-IP: [10.108.4.67]
To: pim@ietf.org
Message-id: <012a01cc8a4b$b0ab0500$12010f00$%zheng@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_FZzdoZcHIPoZwFijnmC9sA)"
Content-language: zh-cn
Thread-index: AcyKS7Axy4CFiYJHRzGoULmDHIVO6w==
X-CFilter-Loop: Reflected
Cc: "'Rishabh Parekh \(riparekh\)'" <riparekh@cisco.com>, "'Stig Venaas \(svenaas\)'" <svenaas@cisco.com>
Subject: [pim] Collect comments on RFC4601 implementation and deployment survey questionnaire
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Oct 2011 08:33:50 -0000

--Boundary_(ID_FZzdoZcHIPoZwFijnmC9sA)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Dear WG,

 

This email is to collect comments on RFC4601 implementations and deployments
survey questionnaire.

 

We have addressed all the errata (about 110) of RFC4601.  Optional features
which do not meet RFC2026 requirement have also been identified and removed
in the draft-ietf-pim-rfc4601bis-00.

We are now planning a survey on RFC4601 implementation and deployment. This
survey intends to provide supporting documentation to advance the RFC4601 to
Draft Standard as required by IESG. 

Our survey report will be based on the replies of the questionnaire, which
targeting various vendors and operators.

We have prepared the questionnaire (as follows),  Stig & Mike will send it
out to wider communities on behalf of PIM WG later on.

 

Please send your questions or comments on the questionnaire to the list.

 

BR,

Jeffery, Rishabh and Vero

 

Questionnaire

 

Introduction:

PIM-SM was first published as RFC 2117 in 1997 and then again as RFC 2362 in
1998. The protocol was classified as Experimental in both of these
documents. The PIM-SM protocol specification was then rewritten in whole and
advanced to Proposed Standard as RFC4601 in 2006. Considering its multiple
independent implementations developed and sufficient successful operational
experience gained, the IETF has decided to advance the PIM-SM routing
protocol to Draft Standard. This survey intends to provide supporting
documentation to advance the Protocol Independent Multicast - Sparse Mode
(PIM-SM) routing protocol from IETF Proposed Standard to Draft Standard.
This survey is issued on behalf of the IETF PIM Working Group.

 

Questions for operators:

1       Have you deployed PIM-SM in your network? 

2       Are you aware that the PIM-SM deployed is RFC2632 based or RFC4601
based?

3       Are you using equipment with different (multi-vendor) PIM-SM
implementations for your deployment?

4       Have you encountered any inter-operability or backward-compatibility
issues amongst differing implementations? If yes, what are your concerns
about these issues?

5       Have you deployed different multicast protocols in different parts
of your network, such as dense mode and sparse mode, where you have
multicast routed between the two parts? If yes, do you know if this is done
using features such as (*,*,RP) and PMBR?

6       To what extent have you deployed ancillary PIM functionality, like
e.g. BSR, SSM, and Explicit Tracking?

7       Do you have any other comments on PIM-SM deployment in your network?

 

Questions for implementers: 

1       Have you implemented PIM-SM?

2       Is the PIM-SM implementation based on RFC 2632 or RFC 4601?

3       Have you implemented (*,*, RP) state of RFC 4601? What is the
rationale behind implementing or omitting (*,*,RP)?

4       Have you implemented the PMBR as specified in RFC 4601 and RFC 2715?
What is the rationale behind implementing or omitting PMBR?

5       Have you implemented other features and functions of RFC 4601, e.g.
Border bit for PIM registers, Explicit tracking, Hashing of group to RP
mappings, IPv6 register PMTUD and Register DSCP/ECN bits?

6       Have you done any inter-operatibility trials with other PIM-SM
implementations based on RFC 4601 or RFC 2362? If yes, have you encountered
any issues during these trials?

7       Do you have any other comments or concerns about PIM-SM as specified
in RFC4601?

 


--Boundary_(ID_FZzdoZcHIPoZwFijnmC9sA)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:\5B8B\4F53;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@\5B8B\4F53";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
/* Page Definitions */
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DZH-CN link=3Dblue =
vlink=3Dpurple style=3D'text-justify-trim:punctuation'><div =
class=3DWordSection1><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif";color:black'>De=
ar WG,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif";color:black'><o=
:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif"'>This email is =
to collect comments on RFC4601 implementations and deployments survey =
questionnaire.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif"'><o:p>&nbsp;</o=
:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif"'>We have =
addressed all the errata (about 110) of RFC4601.&nbsp; Optional features =
which do not meet RFC2026 requirement have also been identified and =
removed in the draft-ietf-pim-rfc4601bis-00.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif"'>We are now =
planning a survey on RFC4601 implementation and deployment. This survey =
intends to provide supporting documentation to advance the RFC4601 to =
Draft Standard as required by IESG. <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif"'>Our survey =
report will be based on the replies of the <span =
style=3D'color:black'>questionnaire, which targeting various vendors and =
operators.<o:p></o:p></span></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif";color:black'>We=
 have prepared the questionnaire (as follows), &nbsp;Stig &amp; Mike =
will send it out to wider communities on behalf of PIM WG later =
on.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif";color:black'><o=
:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif";color:black'>Pl=
ease send your questions or comments on the questionnaire to the =
list.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif";color:black'><o=
:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif";color:black'>BR=
,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif";color:black'>Je=
ffery, Rishabh and Vero<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.5pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'>Questionnaire<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'>Introduction:<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:10.5pt'>PIM-SM =
was first published as RFC 2117 in 1997 and then again as RFC 2362 in =
1998. The protocol was classified as Experimental in both of these =
documents. The PIM-SM protocol specification was then rewritten in whole =
and advanced to Proposed Standard as RFC4601 in 2006. Considering its =
multiple independent implementations developed and sufficient successful =
operational experience gained, the IETF has decided to advance the =
PIM-SM routing protocol to Draft Standard. This survey intends to =
provide supporting documentation to advance the Protocol Independent =
Multicast - Sparse Mode (PIM-SM) routing protocol from IETF Proposed =
Standard to Draft Standard. This survey is issued on behalf of the IETF =
PIM Working Group.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.5pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'>Questions for =
operators:<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'>1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Have =
you deployed PIM-SM in your network? <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'>2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Are you =
aware that the PIM-SM deployed is RFC2632 based or RFC4601 =
based?<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'>3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Are you =
using equipment with different (multi-vendor) PIM-SM implementations for =
your deployment?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt'>4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Have =
you encountered any inter-operability or backward-compatibility issues =
amongst differing implementations? If yes, what are your concerns about =
these issues?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt'>5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Have =
you deployed different multicast protocols in different parts of your =
network, such as dense mode and sparse mode, where you have multicast =
routed between the two parts? If yes, do you know if this is done using =
features such as (*,*,RP) and PMBR?<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'>6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To what =
extent have you deployed ancillary PIM functionality, like e.g. BSR, =
SSM, and Explicit Tracking?<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'>7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Do you =
have any other comments on PIM-SM deployment in your =
network?<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'>Questions for implementers: =
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'>1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Have =
you implemented PIM-SM?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt'>2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Is the =
PIM-SM implementation based on RFC 2632 or RFC =
4601?<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'>3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Have =
you implemented (*,*, RP) state of RFC 4601? What is the rationale =
behind implementing or omitting (*,*,RP)?<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'>4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Have =
you implemented the PMBR as specified in RFC 4601 and RFC 2715? What is =
the rationale behind implementing or omitting =
PMBR?<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'>5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Have =
you implemented other features and functions of RFC 4601, e.g. Border =
bit for PIM registers, Explicit tracking, Hashing of group to RP =
mappings, IPv6 register PMTUD and Register DSCP/ECN =
bits?<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'>6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Have =
you done any inter-operatibility trials with other PIM-SM =
implementations based on RFC 4601 or RFC 2362? If yes, have you =
encountered any issues during these trials?<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'>7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Do you =
have any other comments or concerns about PIM-SM as specified in =
RFC4601?<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'><o:p>&nbsp;</o:p></span></p></div></body></htm=
l>=

--Boundary_(ID_FZzdoZcHIPoZwFijnmC9sA)--

From myselfindranil@gmail.com  Fri Oct 14 05:07:27 2011
Return-Path: <myselfindranil@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C338121F8B6F for <pim@ietfa.amsl.com>; Fri, 14 Oct 2011 05:07:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.093
X-Spam-Level: 
X-Spam-Status: No, score=-3.093 tagged_above=-999 required=5 tests=[AWL=-0.095, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jwpdVDpSyBCT for <pim@ietfa.amsl.com>; Fri, 14 Oct 2011 05:07:27 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2143321F8B59 for <pim@ietf.org>; Fri, 14 Oct 2011 05:07:26 -0700 (PDT)
Received: by wwf22 with SMTP id 22so2294800wwf.13 for <pim@ietf.org>; Fri, 14 Oct 2011 05:07:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=rWa2ZwB4ToqnsW0NfMgiu2LbGQ8X8mkAlg3v/+rA5HY=; b=rU2cZo+9HgizDbyCFXfhYciXngmH4N4hugolWjQ0fO0nmsiqQ/8Or/TXSR83DvhRQb ueTN6rJyFU0XqmfH/VC9q6RiF1ORtGnAAPlS+LfnjdDysDeOwNLcddJy1wbMqMbfFLvk KMqg4nGYFl7cD5K60f/xsb2MBPRSvP8e0QSvs=
MIME-Version: 1.0
Received: by 10.216.230.37 with SMTP id i37mr2818425weq.34.1318594046093; Fri, 14 Oct 2011 05:07:26 -0700 (PDT)
Received: by 10.216.39.80 with HTTP; Fri, 14 Oct 2011 05:07:26 -0700 (PDT)
Date: Fri, 14 Oct 2011 17:37:26 +0530
Message-ID: <CAAaur97MKFDMp1mkZhNZxP=tcrB=DvwXEHUfiJ3vjLwi7Ou+OA@mail.gmail.com>
From: Indranil Bhattacharya <myselfindranil@gmail.com>
To: pim@ietf.org
Content-Type: multipart/alternative; boundary=0016e643452cb86c1204af411905
Subject: [pim] Example of inconsistent mrib state
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Oct 2011 12:07:27 -0000

--0016e643452cb86c1204af411905
Content-Type: text/plain; charset=ISO-8859-1

Hi,

   Can anyone please give an example of inconsistent mrib state where mribs
in two routers on the same lan are pointing to different upstream routers(on
the same lan) to reach the rp? How to configure unicast protocols to
reproduce this? I am referring to second and third assert scenarios. I can
do this by configuring static mroute or by static route but is it possible
to reproduce this while no static route is configured and only protocols
like eigrp, ospf are populating the routing tables?.If yes then what will be
the configuration?

Thanks,
Indranil

--0016e643452cb86c1204af411905
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Hi,</div>
<div>=A0</div>
<div>=A0=A0=A0Can anyone please give an example of inconsistent mrib state =
where mribs in two routers on the same lan=A0are pointing to different upst=
ream routers(on the same lan) to reach the rp? How to configure unicast pro=
tocols to reproduce this? I am referring to second and third assert scenari=
os. I can do this by configuring static mroute or by static route but is it=
 possible to reproduce this=A0while no static route is configured and only =
protocols like eigrp, ospf are populating the routing tables?.If yes then w=
hat will be the configuration?</div>

<div>=A0</div>
<div>Thanks,</div>
<div>Indranil=A0=A0</div>

--0016e643452cb86c1204af411905--

From stig@venaas.com  Fri Oct 14 14:03:21 2011
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3CDB21F8CF8 for <pim@ietfa.amsl.com>; Fri, 14 Oct 2011 14:03:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qID4rR5xb3NJ for <pim@ietfa.amsl.com>; Fri, 14 Oct 2011 14:03:21 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id 106CF21F8CF1 for <pim@ietf.org>; Fri, 14 Oct 2011 14:03:21 -0700 (PDT)
Received: from [10.33.12.90] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id CFF3A7FD4 for <pim@ietf.org>; Fri, 14 Oct 2011 23:03:18 +0200 (CEST)
Message-ID: <4E98A393.20502@venaas.com>
Date: Fri, 14 Oct 2011 14:03:15 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: pim@ietf.org
References: <012a01cc8a4b$b0ab0500$12010f00$%zheng@huawei.com>
In-Reply-To: <012a01cc8a4b$b0ab0500$12010f00$%zheng@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [pim] Collect comments on RFC4601 implementation and deployment survey questionnaire
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Oct 2011 21:03:21 -0000

On 10/14/2011 1:31 AM, Vero Zheng wrote:
> Dear WG,
>
> This email is to collect comments on RFC4601 implementations and
> deployments survey questionnaire.

Just to be clear. At this point we only want to solicit comments on
the questionnaire itself. Are we asking the right sort of questions?
Are any of them unclear, is there anything else we should ask about?

So for now, please review the questionnaire itself, and let us know
what you think. Do not try to answer the questions at this point.

Stig



From hou@cisco.com  Fri Oct 14 18:02:39 2011
Return-Path: <hou@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 629A621F8CE1 for <pim@ietfa.amsl.com>; Fri, 14 Oct 2011 18:02:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.532
X-Spam-Level: 
X-Spam-Status: No, score=-4.532 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VneS4+u7FJG9 for <pim@ietfa.amsl.com>; Fri, 14 Oct 2011 18:02:36 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 44C7F21F8CDE for <pim@ietf.org>; Fri, 14 Oct 2011 18:02:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=hou@cisco.com; l=1744; q=dns/txt; s=iport; t=1318640556; x=1319850156; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version:content-transfer-encoding; bh=miTZ/CDSN8N0qmafJbXFBZdgpXV8VXXwavhGDrNxTts=; b=XWqGeWyW1pDEZUqxLVSn71UrFHbypebUru5g+GWwLQ09NPwVRLXWGRQ9 cpXvRKXQWnhB0ns4zYYPGfEPy9/q0lDEVX0YAcml5QVFa3RqsXUZJML50 w/IT5lYmN+w+bHnMfZApEvSuc7nsxqvDuocbFgOGiQFsk2ajymPh2ce+o c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvAIAL7amE6rRDoI/2dsb2JhbABDiT6QRI5jAoEFgW4BAQEBAxIBJwIBOgISAQgRAwECfAEBBQMBAQQOBSKgagGeQYd5BIgBi3aFMYgWhC4
X-IronPort-AV: E=Sophos;i="4.69,349,1315180800";  d="scan'208";a="8015591"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-2.cisco.com with ESMTP; 15 Oct 2011 01:02:36 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p9F12Zai029992; Sat, 15 Oct 2011 01:02:36 GMT
Received: from xmb-sjc-231.amer.cisco.com ([128.107.191.73]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 14 Oct 2011 18:02:35 -0700
Received: from 128.107.112.196 ([128.107.112.196]) by xmb-sjc-231.amer.cisco.com ([128.107.191.73]) with Microsoft Exchange Server HTTP-DAV ; Sat, 15 Oct 2011 01:02:35 +0000
User-Agent: Microsoft-Entourage/12.26.0.100708
Date: Fri, 14 Oct 2011 18:02:34 -0700
From: Heidi Ou <hou@cisco.com>
To: <pim@ietf.org>
Message-ID: <CABE29BA.15C74%hou@cisco.com>
Thread-Topic: New Version Notification for draft-hou-pim-drlb-00.txt
Thread-Index: AcyK1h9R37OaS5GoN0OWk2130N6OHw==
In-Reply-To: <20111015004805.30882.60471.idtracker@ietfa.amsl.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 15 Oct 2011 01:02:35.0687 (UTC) FILETIME=[20535B70:01CC8AD6]
Cc: "Yiqun Cai \(ycai\)" <ycai@cisco.com>, "Sri Vallepalli \(svallepa\)" <svallepa@cisco.com>, "andy.da.green@bt.com" <andy.da.green@bt.com>
Subject: [pim] FW: New Version Notification for draft-hou-pim-drlb-00.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Oct 2011 01:02:39 -0000

Greetings, 

We plan to present the following draft at PIM WG meeting in Taipei IETF.
Please review and comment.


Thanks!
- Heidi



------ Forwarded Message
> From: <internet-drafts@ietf.org>
> Date: Fri, 14 Oct 2011 17:48:05 -0700
> To: Heidi Ou <hou@cisco.com>
> Cc: Heidi Ou <hou@cisco.com>, <ycai@cisco.com>, <svallepa@cisco.com>,
> <andy.da.green@bt.com>
> Subject: New Version Notification for draft-hou-pim-drlb-00.txt
> 
> A new version of I-D, draft-hou-pim-drlb-00.txt has been successfully
> submitted by Heidi Ou and posted to the IETF repository.
> 
> Filename:  draft-hou-pim-drlb
> Revision:  00
> Title:   Protocol Independent Multicast DR Load Balancing
> Creation date:  2011-10-15
> WG ID:   Individual Submission
> Number of pages: 13
> 
> Abstract:
>    On a multi-access network such as an Ethernet, one of the PIM routers
>    is elected as a Designated Routers (DR).  The PIM DR has two roles in
>    the PIM protocol.  On the first hop network, the PIM DR is
>    responsible for registering an active source to the RP if the group
>    is operated in PIM SM.  On the last hop network, the PIM DR is
>    responsible for tracking local multicast listeners and forwarding
>    traffic to these listeners if the group is operated in PIM SM/SSM/DM.
>    In this document, we propose a modification to the PIM protocol that
>    allows multiple of these last hop routers to be selected so that the
>    forwarding load can be distributed to and handled among these
>    routers.  A router responsible for forwarding for a particular group
>    is called a Group Designated Router (GDR).
> 
>                  
> 
> 
> The IETF Secretariat

------ End of Forwarded Message


From alexpro@homelan.lg.ua  Thu Oct 20 06:39:28 2011
Return-Path: <alexpro@homelan.lg.ua>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F08921F8BB2 for <pim@ietfa.amsl.com>; Thu, 20 Oct 2011 06:39:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vg1rCe90D2JD for <pim@ietfa.amsl.com>; Thu, 20 Oct 2011 06:39:27 -0700 (PDT)
Received: from homelan.lg.ua (mail.homelan.lg.ua [194.0.206.3]) by ietfa.amsl.com (Postfix) with ESMTP id 6DBC421F8BB0 for <pim@ietf.org>; Thu, 20 Oct 2011 06:39:27 -0700 (PDT)
Received: from homelan.lg.ua (mail.homelan.lg.ua [127.0.0.1]) by homelan.lg.ua (Postfix) with ESMTP id 2D7DF48A7F8 for <pim@ietf.org>; Thu, 20 Oct 2011 16:39:26 +0300 (EEST)
Received: from [192.168.200.55] (unknown [192.168.200.55]) by homelan.lg.ua (Postfix) with ESMTP id 12B0648A7FD for <pim@ietf.org>; Thu, 20 Oct 2011 16:39:26 +0300 (EEST)
Message-ID: <4EA0248D.1030804@homelan.lg.ua>
Date: Thu, 20 Oct 2011 16:39:25 +0300
From: =?UTF-8?B?0JDQu9C10LrRgdC10Lkg0J/RgNC+0LrQvtC/0YfRg9C6?= <alexpro@homelan.lg.ua>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20111007 Lightning/1.0b3pre Thunderbird/3.1.12
MIME-Version: 1.0
To: pim@ietf.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: [pim] pimd under Linux 2.6: very long time between join request and activation of multicast route.
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Oct 2011 13:44:42 -0000

Hi all!

My English is not very good, excuse me if I said something wrong.
Two months ago I got several IPTV channels from my upstream provider.
All users in my network are connected through Linux routers, so I
decided to use pimd for multicast routing.
All works well with pimd, but between IGMP join request and actual
activation of multicast route to end user takes very long time: up to
30-40 seconds. I tried to test multicast routing with my Cisco Catalyst
6509 (sup2), in this case actual multicast route activation takes less
than a second, sometimes one second, no more.
Now for some reasons is impossible to use my Catalyst for multicast
routing for all users, and I would like to solve the problem of a long
delay between join and route activation.
Could you give me a hint where to find the cause of this behavior? If
necessary, I can try to edit the source code to achieve the result. So
far I'm not quite sure where exactly to look for the causes of such
behavior.
Now all the pimd are configured with a static rendezvous point and with
no cand-rp and cand-bsr option. Totally three routers present, all in
one segment, and one of them has upstream interface.

Thanks in advance, with best regards, Alexey Prokopchuk (AP8686-RIPE).


From magesh.v@alcatel-lucent.com  Fri Oct 21 00:39:53 2011
Return-Path: <magesh.v@alcatel-lucent.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C330221F850B for <pim@ietfa.amsl.com>; Fri, 21 Oct 2011 00:39:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=-0.149, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XAWvqPEvtoLc for <pim@ietfa.amsl.com>; Fri, 21 Oct 2011 00:39:53 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 21E1621F84DD for <pim@ietf.org>; Fri, 21 Oct 2011 00:39:53 -0700 (PDT)
Received: from inbansmailrelay1.in.alcatel-lucent.com (h135-250-11-31.lucent.com [135.250.11.31]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id p9L7dlkC029987 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 21 Oct 2011 02:39:49 -0500 (CDT)
Received: from INBANSXCHHUB01.in.alcatel-lucent.com (inbansxchhub01.in.alcatel-lucent.com [135.250.12.32]) by inbansmailrelay1.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p9L7dOFg013096 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 21 Oct 2011 13:09:44 +0530
Received: from INBANSXCHMBSA2.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB01.in.alcatel-lucent.com ([135.250.12.32]) with mapi; Fri, 21 Oct 2011 13:09:37 +0530
From: "V, Magesh (Magesh)" <magesh.v@alcatel-lucent.com>
To: =?koi8-r?B?4czFy9PFyiDw0s/Lz9De1cv=?= <alexpro@homelan.lg.ua>, "pim@ietf.org" <pim@ietf.org>
Date: Fri, 21 Oct 2011 13:09:36 +0530
Thread-Topic: [pim] pimd under Linux 2.6: very long time between join request and activation of multicast route.
Thread-Index: AcyPLo11DDR41rgdTfeusYYS1OKahAAlZhHg
Message-ID: <05D3B4AA7527D74EBF4921238463575321641FEA1F@INBANSXCHMBSA2.in.alcatel-lucent.com>
References: <4EA0248D.1030804@homelan.lg.ua>
In-Reply-To: <4EA0248D.1030804@homelan.lg.ua>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Subject: Re: [pim] pimd under Linux 2.6: very long time between join request and activation of multicast route.
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Oct 2011 07:39:53 -0000

'igmp-fast-leave' is one quick thing I can think of. Is that option already=
 turned ON? This should help improving response times during Channel zappin=
g.

Thanks,
Magesh.

-----Original Message-----
From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of ?????=
?? ?????????
Sent: Thursday, October 20, 2011 7:09 PM
To: pim@ietf.org
Subject: [pim] pimd under Linux 2.6: very long time between join request an=
d activation of multicast route.

Hi all!

My English is not very good, excuse me if I said something wrong.
Two months ago I got several IPTV channels from my upstream provider.
All users in my network are connected through Linux routers, so I
decided to use pimd for multicast routing.
All works well with pimd, but between IGMP join request and actual
activation of multicast route to end user takes very long time: up to
30-40 seconds. I tried to test multicast routing with my Cisco Catalyst
6509 (sup2), in this case actual multicast route activation takes less
than a second, sometimes one second, no more.
Now for some reasons is impossible to use my Catalyst for multicast
routing for all users, and I would like to solve the problem of a long
delay between join and route activation.
Could you give me a hint where to find the cause of this behavior? If
necessary, I can try to edit the source code to achieve the result. So
far I'm not quite sure where exactly to look for the causes of such
behavior.
Now all the pimd are configured with a static rendezvous point and with
no cand-rp and cand-bsr option. Totally three routers present, all in
one segment, and one of them has upstream interface.

Thanks in advance, with best regards, Alexey Prokopchuk (AP8686-RIPE).

_______________________________________________
pim mailing list
pim@ietf.org
https://www.ietf.org/mailman/listinfo/pim

From alexpro@homelan.lg.ua  Mon Oct 24 09:57:27 2011
Return-Path: <alexpro@homelan.lg.ua>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5995421F8B66 for <pim@ietfa.amsl.com>; Mon, 24 Oct 2011 09:57:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.306
X-Spam-Level: 
X-Spam-Status: No, score=0.306 tagged_above=-999 required=5 tests=[AWL=-2.454,  BAYES_20=-0.74, CHARSET_FARAWAY_HEADER=3.2, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jPK36ptDJO2f for <pim@ietfa.amsl.com>; Mon, 24 Oct 2011 09:57:26 -0700 (PDT)
Received: from homelan.lg.ua (mail.homelan.lg.ua [194.0.206.3]) by ietfa.amsl.com (Postfix) with ESMTP id 882E221F8B26 for <pim@ietf.org>; Mon, 24 Oct 2011 09:57:26 -0700 (PDT)
Received: from homelan.lg.ua (mail.homelan.lg.ua [127.0.0.1]) by homelan.lg.ua (Postfix) with ESMTP id 6EDE7485F06 for <pim@ietf.org>; Mon, 24 Oct 2011 19:57:24 +0300 (EEST)
Received: from [192.168.200.55] (unknown [192.168.200.55]) by homelan.lg.ua (Postfix) with ESMTP id 5EACA486172 for <pim@ietf.org>; Mon, 24 Oct 2011 19:57:23 +0300 (EEST)
Message-ID: <4EA598F3.7060204@homelan.lg.ua>
Date: Mon, 24 Oct 2011 19:57:23 +0300
From: =?KOI8-R?Q?=E1=CC=C5=CB=D3=C5=CA_=F0=D2=CF=CB=CF=D0=DE=D5=CB?= <alexpro@homelan.lg.ua>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20111007 Lightning/1.0b3pre Thunderbird/3.1.12
MIME-Version: 1.0
To: pim@ietf.org
References: <4EA0248D.1030804@homelan.lg.ua> <05D3B4AA7527D74EBF4921238463575321641FEA1F@INBANSXCHMBSA2.in.alcatel-lucent.com>
In-Reply-To: <05D3B4AA7527D74EBF4921238463575321641FEA1F@INBANSXCHMBSA2.in.alcatel-lucent.com>
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: Re: [pim] pimd under Linux 2.6: very long time between join request and activation of multicast route.
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Oct 2011 16:57:27 -0000

21.10.2011 10:39, V, Magesh (Magesh) wrote:
> 'igmp-fast-leave' is one quick thing I can think of. Is that option already turned ON? This should help improving response times during Channel zapping.
>
> Thanks,
> Magesh.
Which version of pimd you are bear in mind? pimd-2.1.7 which I currently
using, has no 'igmp-fast-leave' option, nor in configuration nor in
command line parameters... As far as I know, this version is the latest...

With best regards, Alexey Prokopchuk (AP8686-RIPE).


From stig@venaas.com  Mon Oct 24 10:12:59 2011
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90B7621F8D6D for <pim@ietfa.amsl.com>; Mon, 24 Oct 2011 10:12:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WIfDqzwsPkNP for <pim@ietfa.amsl.com>; Mon, 24 Oct 2011 10:12:58 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id 5EEBC21F8D60 for <pim@ietf.org>; Mon, 24 Oct 2011 10:12:53 -0700 (PDT)
Received: from [10.33.12.70] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id 7244C8000; Mon, 24 Oct 2011 19:12:50 +0200 (CEST)
Message-ID: <4EA59C83.3010103@venaas.com>
Date: Mon, 24 Oct 2011 10:12:35 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Mike McBride <mmcbride@forsythe.com>
References: <Acx9gzc1HGUVzzTdSpuDJFMYU7DXugAwxdaA> <8999C52267AF8844B77A280D0CD584C13B46CE2CBA@FTI2K3CMSMBX1.forsythe.com> <CAL3FGfxjXDq682Gp5WN0c2SvJed-qFhjn0tQWe_cs1XpTC0iGw@mail.gmail.com> <8999C52267AF8844B77A280D0CD584C13B4832FDED@FTI2K3CMSMBX1.forsythe.com>
In-Reply-To: <8999C52267AF8844B77A280D0CD584C13B4832FDED@FTI2K3CMSMBX1.forsythe.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] pop-count ready for wglc?
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Oct 2011 17:12:59 -0000

On 10/10/2011 2:17 PM, Mike McBride wrote:
> Today begins a two week wglc for draft-ietf-pim-pop-count-04. Please review the draft. Please then comment, on the list, with a thumbs up or a thumbs down.

I haven't seen any comments on the list, and the WGLC is about to end.
Please provide your comments and whether you support the draft or not.

Since I'm now an author of the draft, please regard this request as
coming from an author and not a chair.

I'll leave to Mike to figure out what to do with the draft, I'm just
urging you to provide comments.

Stig

> thanks,
> mike
>
> http://www.ietf.org/id/draft-ietf-pim-pop-count-04.txt
>
>> -----Original Message-----
>> From: Mike McBride
>> Sent: Tuesday, September 27, 2011 8:06 PM
>> To: pim@ietf.org
>> Subject: pop-count ready for wglc?
>>
>> We had consensus (5-0) in the Quebec pimwg meeting to issue a wglc for
>> the pim-pop-count draft:
>>
>> http://www.ietf.org/id/draft-ietf-pim-pop-count-04.txt
>>
>>
>> Before doing so we'd like to bring it to the list. If you feel this
>> draft is not ready for wglc please speak up. Otherwise we will begin a
>> wglc next week.
>>
>> thanks,
>> mike
> NOTICE OF CONFIDENTIALITY:
> The information contained in this email transmission is confidential information which may contain information that is legally privileged and prohibited from disclosure under applicable law or by contractual agreement.  The information is intended solely for the use of the individual or entity named above.
> If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking of any action in reliance on the contents of this email transmission is strictly prohibited.
> If you have received this email transmission in error, please notify us immediately by telephone to arrange for the return of the original transmission to us.
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim


From stig@venaas.com  Mon Oct 24 10:53:00 2011
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7625F21F86A4; Mon, 24 Oct 2011 10:53:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ko2WvfHL9xDT; Mon, 24 Oct 2011 10:53:00 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id 8B80421F84AF; Mon, 24 Oct 2011 10:52:59 -0700 (PDT)
Received: from [10.33.12.70] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id 264C98000; Mon, 24 Oct 2011 19:52:56 +0200 (CEST)
Message-ID: <4EA5A5F5.20508@venaas.com>
Date: Mon, 24 Oct 2011 10:52:53 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
References: <20110926194028.7741.46979.idtracker@ietfa.amsl.com> <025701cc7cf2$6dd35cc0$4001a8c0@gateway.2wire.net> <4E82695F.9070706@isi.edu>
In-Reply-To: <4E82695F.9070706@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pim@ietf.org, ietf@ietf.org, "t.petch" <daedulus@btconnect.com>
Subject: Re: [pim] Last Call: <draft-ietf-pim-port-08.txt> (A Reliable TransportMechanism for PIM) to Experimental RFC
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Oct 2011 17:53:00 -0000

On 9/27/2011 5:25 PM, Joe Touch wrote:
> Hi, all,
>
> The IANA considerations in this doc are in error and need updating as
> follows. I agree that "PORT" is a poor acronym choice, FWIW.

Thanks Joe/Tom. I'm changing this per your suggestions.

Stig

> Joe
>
> 11. IANA Considerations
>
> This specification makes use of a TCP port number and a SCTP port
> number for the use of PIM-Over-Reliable-Transport that has been
> allocated by IANA. It also makes use of IANA PIM Hello Options
> allocations that should be made permanent.
>
> The current IANA allocation is called "pim-port", not
> "PIM-Over-Reliable-Transport". The long name (description) is "PIM over
> Reliable-Transport", but that's not the authoritative name of the
> service - also, IANA does "assignments" (as per RFC 6335); this section
> should read as follows.
>
> This specification makes use of a TCP port number and a SCTP port
> number for the use of pim-port service that has been
> assigned by IANA. It also makes use of IANA PIM Hello Options
> assignments that should be made permanent.
>
> 11.1. PORT Port Number
>
> IANA has assigned a port number that is used as a destination port
> for PORT TCP and SCTP transports. The assigned number is 8471.
> References to this document should be added to the Service Name and
> Transport Protocol Port Number Registry.
>
> This should read:
>
> IANA has already assigned a port number that is used as
> a destination port
> for pim-port TCP and SCTP transports. The assigned number is 8471.
> References to this document should be added to the Service Name and
> Transport Protocol Port Number Registry for pim-port.
> ----
>
> On 9/27/2011 1:46 AM, t.petch wrote:
>> The choice of service name for this transport seems unfortunate;
>> having a port
>> number registry with a service in it called 'port' may be witty but
>> seems like a
>> source of future confusion.
>>
>> I notice that IANA currently have a service name of 'pim-port' which
>> seems a
>> better idea and one that I think that this I-D should adopt.
>>
>> Tom Petch
>>
>>
>> ----- Original Message -----
>> From: "The IESG"<iesg-secretary@ietf.org>
>> To: "IETF-Announce"<ietf-announce@ietf.org>
>> Cc:<pim@ietf.org>
>> Sent: Monday, September 26, 2011 9:40 PM
>> Subject: Last Call:<draft-ietf-pim-port-08.txt> (A Reliable
>> TransportMechanism
>> for PIM) to Experimental RFC
>>
>>
>>>
>>> The IESG has received a request from the Protocol Independent Multicast
>>> WG (pim) to consider the following document:
>>> - 'A Reliable Transport Mechanism for PIM'
>>> <draft-ietf-pim-port-08.txt> as an Experimental RFC
>>>
>>> The IESG plans to make a decision in the next few weeks, and solicits
>>> final comments on this action. Please send substantive comments to the
>>> ietf@ietf.org mailing lists by 2011-10-10. Exceptionally, comments
>>> may be
>>> sent to iesg@ietf.org instead. In either case, please retain the
>>> beginning of the Subject line to allow automated sorting.
>>>
>>> Abstract
>>>
>>>
>>> This document defines a reliable transport mechanism for the PIM
>>> protocol for transmission of Join/Prune messages. This eliminates
>>> the need for periodic Join/Prune message transmission and processing.
>>> The reliable transport mechanism can use either TCP or SCTP as the
>>> transport protocol.
>>>
>>>
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-ietf-pim-port/
>>>
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-ietf-pim-port/
>>>
>>>
>>> No IPR declarations have been submitted directly on this I-D.
>>> _______________________________________________
>>> IETF-Announce mailing list
>>> IETF-Announce@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim


From stig@venaas.com  Mon Oct 24 11:06:15 2011
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 843F121F8BA6 for <pim@ietfa.amsl.com>; Mon, 24 Oct 2011 11:06:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.539
X-Spam-Level: 
X-Spam-Status: No, score=-102.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j+P7SRGLORkY for <pim@ietfa.amsl.com>; Mon, 24 Oct 2011 11:06:15 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id D722121F8B9D for <pim@ietf.org>; Mon, 24 Oct 2011 11:06:14 -0700 (PDT)
Received: from [10.33.12.70] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id 4214D8000; Mon, 24 Oct 2011 20:06:13 +0200 (CEST)
Message-ID: <4EA5A912.2000202@venaas.com>
Date: Mon, 24 Oct 2011 11:06:10 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: "pim@ietf.org" <pim@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gorry@erg.abdn.ac.uk
Subject: [pim] PORT checksum issue
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Oct 2011 18:06:15 -0000

Hi

Upon reading Gorry's transport directorate review of PORT, I realised
that we have an issue with the checksums.

According to the draft, checksums are calculated as usual for the PIM
Join/Prune messages. However, for IPv6, the checksum includes a
pseudo-header, including the source and destination address of the
message. It's however not clear what these addresses should be. I need
to explain this in detail in the draft.

I'm proposing we simply say that the addresses should be set to 0 in
the pseudo-header.

We could consider other alternatives, but I think this is the simplest
solution.

First of all, the pseudo-header does not need to include the source and
the destination. They are there to protect against bits in the source or
destination address being changed during transport so that the wrong
host may accept the packet. However, since they are part of a TCP
connection which has its own checksum, we are still protected against
this.

I can think of two other alternatives.

1. Use the source and destination addresses the PIM J/P would have had.

2. Use the source and destination addresses of the PORT connection.

Alternative 1 would work, but I don't see what it buys us. Alternative 2
is difficult for two reasons. One is that the addresses for the PORT
connection may not be the same address family as the PORT message.
Also, depending on how the code is structured, it may be nice to compute
the checksum of the message itself, without having to pass information
about the PORT connection.

I'm about to update the draft now, saying that the addresses should be
0. But please speak up if you disagree with this choice. Please let me
know ASAP if you do, although we should still have a couple of weeks to
update the draft if needed.

Stig

From stig@venaas.com  Mon Oct 24 11:53:37 2011
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39C6F11E80B7 for <pim@ietfa.amsl.com>; Mon, 24 Oct 2011 11:53:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6FD5vHLvk6w5 for <pim@ietfa.amsl.com>; Mon, 24 Oct 2011 11:53:36 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id 931E411E809C for <pim@ietf.org>; Mon, 24 Oct 2011 11:53:36 -0700 (PDT)
Received: from [10.33.12.70] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id 7C8C58000; Mon, 24 Oct 2011 20:53:34 +0200 (CEST)
Message-ID: <4EA5B42A.7060900@venaas.com>
Date: Mon, 24 Oct 2011 11:53:30 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: "pim@ietf.org" <pim@ietf.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pim-chairs@tools.ietf.org
Subject: [pim] Request for agenda items for pim at IETF 82
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Oct 2011 18:53:37 -0000

If you would like to be on the pim agenda for IETF 82 in Taipei, please
send an email to us chairs with your request.

The IETF agenda is available at
https://datatracker.ietf.org/meeting/82/agenda.html
We got the Tuesday morning 0900-1130 slot. AFAIK this
is the final agenda, but please check the IETF agenda
yourself.

Below are the cut-off dates for draft submissions. At
the time of writing this, the initial submission deadline
is just a few hours ahead.

2011-10-24 (Monday): Internet Draft Cut-off for initial document (-00)
submission by 17:00 PT (00:00 UTC), upload using IETF ID Submission
Tool.

2011-10-31 (Monday): Internet Draft final submission cut-off by 17:00
PT (00:00 UTC), upload using IETF ID Submission Tool.

Stig

From internet-drafts@ietf.org  Mon Oct 24 14:49:47 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6256511E818D; Mon, 24 Oct 2011 14:49:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.576
X-Spam-Level: 
X-Spam-Status: No, score=-102.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fmvyine8FqfW; Mon, 24 Oct 2011 14:49:46 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8824611E8183; Mon, 24 Oct 2011 14:49:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.61
Message-ID: <20111024214946.9196.18363.idtracker@ietfa.amsl.com>
Date: Mon, 24 Oct 2011 14:49:46 -0700
Cc: pim@ietf.org
Subject: [pim] I-D Action: draft-ietf-pim-port-09.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Oct 2011 21:49:47 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Protocol Independent Multicast Workin=
g Group of the IETF.

	Title           : A Reliable Transport Mechanism for PIM
	Author(s)       : Dino Farinacci
                          IJsbrand Wijnands
                          Stig Venaas
                          Maria Napierala
	Filename        : draft-ietf-pim-port-09.txt
	Pages           : 36
	Date            : 2011-10-24

   This document defines a reliable transport mechanism for the PIM
   protocol for transmission of Join/Prune messages.  This eliminates
   the need for periodic Join/Prune message transmission and processing.
   The reliable transport mechanism can use either TCP or SCTP as the
   transport protocol.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pim-port-09.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-pim-port-09.txt

From mmcbride@forsythe.com  Tue Oct 25 14:27:38 2011
Return-Path: <mmcbride@forsythe.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5249A21F8AF0 for <pim@ietfa.amsl.com>; Tue, 25 Oct 2011 14:27:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tBa2WZZHjo96 for <pim@ietfa.amsl.com>; Tue, 25 Oct 2011 14:27:37 -0700 (PDT)
Received: from ftiironport2.forsythe.com (smtp2.forsythe.com [12.171.5.20]) by ietfa.amsl.com (Postfix) with ESMTP id A583D21F886A for <pim@ietf.org>; Tue, 25 Oct 2011 14:27:37 -0700 (PDT)
From: Mike McBride <mmcbride@forsythe.com>
To: Stig Venaas <stig@venaas.com>
Date: Tue, 25 Oct 2011 16:27:31 -0500
Thread-Topic: [pim] pop-count ready for wglc?
Thread-Index: AcyScC5C/mnQLKVQQNqHun5KzaqyoAA6Kc8w
Message-ID: <8999C52267AF8844B77A280D0CD584C13B4985B9B7@FTI2K3CMSMBX1.forsythe.com>
References: <Acx9gzc1HGUVzzTdSpuDJFMYU7DXugAwxdaA> <8999C52267AF8844B77A280D0CD584C13B46CE2CBA@FTI2K3CMSMBX1.forsythe.com> <CAL3FGfxjXDq682Gp5WN0c2SvJed-qFhjn0tQWe_cs1XpTC0iGw@mail.gmail.com> <8999C52267AF8844B77A280D0CD584C13B4832FDED@FTI2K3CMSMBX1.forsythe.com> <4EA59C83.3010103@venaas.com>
In-Reply-To: <4EA59C83.3010103@venaas.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] pop-count ready for wglc?
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Oct 2011 21:27:38 -0000

We need to hear something. Anything. It's difficult to justify, to the IESG=
, that the wg is rallying behind the draft when there is zero response duri=
ng the wglc. So I'm going to extend this wglc for another 2 weeks. Please s=
peak up. If there continues to be zero response, we will assume there is no=
 interest in progressing the draft and will shelve the wglc for the time be=
ing.

thanks,
mike

> -----Original Message-----
> From: Stig Venaas [mailto:stig@venaas.com]
> Sent: Monday, October 24, 2011 10:13 AM
> To: Mike McBride
> Cc: pim@ietf.org
> Subject: Re: [pim] pop-count ready for wglc?
>=20
> On 10/10/2011 2:17 PM, Mike McBride wrote:
> > Today begins a two week wglc for draft-ietf-pim-pop-count-04. Please
> review the draft. Please then comment, on the list, with a thumbs up or
> a thumbs down.
>=20
> I haven't seen any comments on the list, and the WGLC is about to end.
> Please provide your comments and whether you support the draft or not.
>=20
> Since I'm now an author of the draft, please regard this request as
> coming from an author and not a chair.
>=20
> I'll leave to Mike to figure out what to do with the draft, I'm just
> urging you to provide comments.
>=20
> Stig
>=20
> > thanks,
> > mike
> >
> > http://www.ietf.org/id/draft-ietf-pim-pop-count-04.txt
> >
> >> -----Original Message-----
> >> From: Mike McBride
> >> Sent: Tuesday, September 27, 2011 8:06 PM
> >> To: pim@ietf.org
> >> Subject: pop-count ready for wglc?
> >>
> >> We had consensus (5-0) in the Quebec pimwg meeting to issue a wglc
> for
> >> the pim-pop-count draft:
> >>
> >> http://www.ietf.org/id/draft-ietf-pim-pop-count-04.txt
> >>
> >>
> >> Before doing so we'd like to bring it to the list. If you feel this
> >> draft is not ready for wglc please speak up. Otherwise we will begin
> a
> >> wglc next week.
> >>
> >> thanks,
> >> mike
> > NOTICE OF CONFIDENTIALITY:
> > The information contained in this email transmission is confidential
> information which may contain information that is legally privileged
> and prohibited from disclosure under applicable law or by contractual
> agreement.  The information is intended solely for the use of the
> individual or entity named above.
> > If you are not the intended recipient, you are hereby notified that
> any disclosure, copying, distribution or taking of any action in
> reliance on the contents of this email transmission is strictly
> prohibited.
> > If you have received this email transmission in error, please notify
> us immediately by telephone to arrange for the return of the original
> transmission to us.
> >
> > _______________________________________________
> > pim mailing list
> > pim@ietf.org
> > https://www.ietf.org/mailman/listinfo/pim

NOTICE OF CONFIDENTIALITY: =20
The information contained in this email transmission is confidential inform=
ation which may contain information that is legally privileged and prohibit=
ed from disclosure under applicable law or by contractual agreement.  The i=
nformation is intended solely for the use of the individual or entity named=
 above. =20
If you are not the intended recipient, you are hereby notified that any dis=
closure, copying, distribution or taking of any action in reliance on the c=
ontents of this email transmission is strictly prohibited. =20
If you have received this email transmission in error, please notify us imm=
ediately by telephone to arrange for the return of the original transmissio=
n to us.


From lenny@juniper.net  Wed Oct 26 14:54:21 2011
Return-Path: <lenny@juniper.net>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 182091F0C3D for <pim@ietfa.amsl.com>; Wed, 26 Oct 2011 14:54:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g+LV0Or+ix0e for <pim@ietfa.amsl.com>; Wed, 26 Oct 2011 14:54:20 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by ietfa.amsl.com (Postfix) with ESMTP id 86A8F1F0C35 for <pim@ietf.org>; Wed, 26 Oct 2011 14:54:17 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP;  Wed, 26 Oct 2011 14:54:20 PDT
Received: from magenta.juniper.net (172.17.27.123) by P-EMHUB01-HQ.jnpr.net (172.24.192.33) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 26 Oct 2011 14:52:20 -0700
Received: from eng-mail01.juniper.net (eng-mail01.juniper.net [172.17.28.114]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id p9QLqKh83154; Wed, 26 Oct 2011 14:52:20 -0700 (PDT)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id 240141149B;  Wed, 26 Oct 2011 14:52:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id 19DB41141B; Wed, 26 Oct 2011 14:52:20 -0700 (PDT)
Date: Wed, 26 Oct 2011 14:52:20 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: Mike McBride <mmcbride@forsythe.com>
In-Reply-To: <8999C52267AF8844B77A280D0CD584C13B4985B9B7@FTI2K3CMSMBX1.forsythe.com>
Message-ID: <20111026144807.X86913@eng-mail01.juniper.net>
References: <Acx9gzc1HGUVzzTdSpuDJFMYU7DXugAwxdaA> <8999C52267AF8844B77A280D0CD584C13B46CE2CBA@FTI2K3CMSMBX1.forsythe.com> <CAL3FGfxjXDq682Gp5WN0c2SvJed-qFhjn0tQWe_cs1XpTC0iGw@mail.gmail.com> <8999C52267AF8844B77A280D0CD584C13B4832FDED@FTI2K3CMSMBX1.forsythe.com> <4EA59C83.3010103@venaas.com> <8999C52267AF8844B77A280D0CD584C13B4985B9B7@FTI2K3CMSMBX1.forsythe.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] pop-count ready for wglc?
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Oct 2011 21:54:21 -0000

I would support shelving the work.  We would never use OSPF/ISIS to carry 
unicast accounting info, so why do so in mcast?  Better to leave this up 
to the application layer.

-Lenny

On Tue, 25 Oct 2011, Mike McBride wrote:

-) We need to hear something. Anything. It's difficult to justify, to the 
-) IESG, that the wg is rallying behind the draft when there is zero 
-) response during the wglc. So I'm going to extend this wglc for another 
-) 2 weeks. Please speak up. If there continues to be zero response, we 
-) will assume there is no interest in progressing the draft and will 
-) shelve the wglc for the time being.
-) 
-) thanks,
-) mike
-) 
-) > -----Original Message-----
-) > From: Stig Venaas [mailto:stig@venaas.com]
-) > Sent: Monday, October 24, 2011 10:13 AM
-) > To: Mike McBride
-) > Cc: pim@ietf.org
-) > Subject: Re: [pim] pop-count ready for wglc?
-) > 
-) > On 10/10/2011 2:17 PM, Mike McBride wrote:
-) > > Today begins a two week wglc for draft-ietf-pim-pop-count-04. Please
-) > review the draft. Please then comment, on the list, with a thumbs up or
-) > a thumbs down.
-) > 
-) > I haven't seen any comments on the list, and the WGLC is about to end.
-) > Please provide your comments and whether you support the draft or not.
-) > 
-) > Since I'm now an author of the draft, please regard this request as
-) > coming from an author and not a chair.
-) > 
-) > I'll leave to Mike to figure out what to do with the draft, I'm just
-) > urging you to provide comments.
-) > 
-) > Stig
-) > 
-) > > thanks,
-) > > mike
-) > >
-) > > http://www.ietf.org/id/draft-ietf-pim-pop-count-04.txt
-) > >
-) > >> -----Original Message-----
-) > >> From: Mike McBride
-) > >> Sent: Tuesday, September 27, 2011 8:06 PM
-) > >> To: pim@ietf.org
-) > >> Subject: pop-count ready for wglc?
-) > >>
-) > >> We had consensus (5-0) in the Quebec pimwg meeting to issue a wglc
-) > for
-) > >> the pim-pop-count draft:
-) > >>
-) > >> http://www.ietf.org/id/draft-ietf-pim-pop-count-04.txt
-) > >>
-) > >>
-) > >> Before doing so we'd like to bring it to the list. If you feel this
-) > >> draft is not ready for wglc please speak up. Otherwise we will begin
-) > a
-) > >> wglc next week.
-) > >>
-) > >> thanks,
-) > >> mike
-) > > NOTICE OF CONFIDENTIALITY:
-) > > The information contained in this email transmission is confidential
-) > information which may contain information that is legally privileged
-) > and prohibited from disclosure under applicable law or by contractual
-) > agreement.  The information is intended solely for the use of the
-) > individual or entity named above.
-) > > If you are not the intended recipient, you are hereby notified that
-) > any disclosure, copying, distribution or taking of any action in
-) > reliance on the contents of this email transmission is strictly
-) > prohibited.
-) > > If you have received this email transmission in error, please notify
-) > us immediately by telephone to arrange for the return of the original
-) > transmission to us.
-) > >
-) > > _______________________________________________
-) > > pim mailing list
-) > > pim@ietf.org
-) > > https://www.ietf.org/mailman/listinfo/pim
-) 
-) NOTICE OF CONFIDENTIALITY:  
-) The information contained in this email transmission is confidential information which may contain information that is legally privileged and prohibited from disclosure under applicable law or by contractual agreement.  The information is intended solely for the use of the individual or entity named above.  
-) If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking of any action in reliance on the contents of this email transmission is strictly prohibited.  
-) If you have received this email transmission in error, please notify us immediately by telephone to arrange for the return of the original transmission to us.
-) 
-) _______________________________________________
-) pim mailing list
-) pim@ietf.org
-) https://www.ietf.org/mailman/listinfo/pim
-) 

From jeff.tantsura@ericsson.com  Wed Oct 26 14:58:27 2011
Return-Path: <jeff.tantsura@ericsson.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5808B21F8A62 for <pim@ietfa.amsl.com>; Wed, 26 Oct 2011 14:58:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0VZ5qb6vdVmk for <pim@ietfa.amsl.com>; Wed, 26 Oct 2011 14:58:26 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 9F0E221F8A58 for <pim@ietf.org>; Wed, 26 Oct 2011 14:58:26 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p9QLwNf2011395; Wed, 26 Oct 2011 16:58:24 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.232]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Wed, 26 Oct 2011 17:58:17 -0400
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: Leonard Giuliano <lenny@juniper.net>, Mike McBride <mmcbride@forsythe.com>
Date: Wed, 26 Oct 2011 17:58:14 -0400
Thread-Topic: [pim] pop-count ready for wglc?
Thread-Index: AcyUKl3v1kdV01laTN+yR5Afzm5kMQ==
Message-ID: <CACDD06F.6965%jeff.tantsura@ericsson.com>
In-Reply-To: <20111026144807.X86913@eng-mail01.juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.13.0.110805
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] pop-count ready for wglc?
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Oct 2011 21:58:27 -0000

+1
--=20
Regards,
Jeff



On 10/26/11 2:52 PM, "Leonard Giuliano" <lenny@juniper.net> wrote:

>
>I would support shelving the work.  We would never use OSPF/ISIS to carry
>unicast accounting info, so why do so in mcast?  Better to leave this up
>to the application layer.
>
>-Lenny
>
>On Tue, 25 Oct 2011, Mike McBride wrote:
>
>-) We need to hear something. Anything. It's difficult to justify, to the
>-) IESG, that the wg is rallying behind the draft when there is zero
>-) response during the wglc. So I'm going to extend this wglc for another
>-) 2 weeks. Please speak up. If there continues to be zero response, we
>-) will assume there is no interest in progressing the draft and will
>-) shelve the wglc for the time being.
>-)=20
>-) thanks,
>-) mike
>-)=20
>-) > -----Original Message-----
>-) > From: Stig Venaas [mailto:stig@venaas.com]
>-) > Sent: Monday, October 24, 2011 10:13 AM
>-) > To: Mike McBride
>-) > Cc: pim@ietf.org
>-) > Subject: Re: [pim] pop-count ready for wglc?
>-) >=20
>-) > On 10/10/2011 2:17 PM, Mike McBride wrote:
>-) > > Today begins a two week wglc for draft-ietf-pim-pop-count-04.
>Please
>-) > review the draft. Please then comment, on the list, with a thumbs up
>or
>-) > a thumbs down.
>-) >=20
>-) > I haven't seen any comments on the list, and the WGLC is about to
>end.
>-) > Please provide your comments and whether you support the draft or
>not.
>-) >=20
>-) > Since I'm now an author of the draft, please regard this request as
>-) > coming from an author and not a chair.
>-) >=20
>-) > I'll leave to Mike to figure out what to do with the draft, I'm just
>-) > urging you to provide comments.
>-) >=20
>-) > Stig
>-) >=20
>-) > > thanks,
>-) > > mike
>-) > >
>-) > > http://www.ietf.org/id/draft-ietf-pim-pop-count-04.txt
>-) > >
>-) > >> -----Original Message-----
>-) > >> From: Mike McBride
>-) > >> Sent: Tuesday, September 27, 2011 8:06 PM
>-) > >> To: pim@ietf.org
>-) > >> Subject: pop-count ready for wglc?
>-) > >>
>-) > >> We had consensus (5-0) in the Quebec pimwg meeting to issue a wglc
>-) > for
>-) > >> the pim-pop-count draft:
>-) > >>
>-) > >> http://www.ietf.org/id/draft-ietf-pim-pop-count-04.txt
>-) > >>
>-) > >>
>-) > >> Before doing so we'd like to bring it to the list. If you feel
>this
>-) > >> draft is not ready for wglc please speak up. Otherwise we will
>begin
>-) > a
>-) > >> wglc next week.
>-) > >>
>-) > >> thanks,
>-) > >> mike
>-) > > NOTICE OF CONFIDENTIALITY:
>-) > > The information contained in this email transmission is
>confidential
>-) > information which may contain information that is legally privileged
>-) > and prohibited from disclosure under applicable law or by contractual
>-) > agreement.  The information is intended solely for the use of the
>-) > individual or entity named above.
>-) > > If you are not the intended recipient, you are hereby notified that
>-) > any disclosure, copying, distribution or taking of any action in
>-) > reliance on the contents of this email transmission is strictly
>-) > prohibited.
>-) > > If you have received this email transmission in error, please
>notify
>-) > us immediately by telephone to arrange for the return of the original
>-) > transmission to us.
>-) > >
>-) > > _______________________________________________
>-) > > pim mailing list
>-) > > pim@ietf.org
>-) > > https://www.ietf.org/mailman/listinfo/pim
>-)=20
>-) NOTICE OF CONFIDENTIALITY:
>-) The information contained in this email transmission is confidential
>information which may contain information that is legally privileged and
>prohibited from disclosure under applicable law or by contractual
>agreement.  The information is intended solely for the use of the
>individual or entity named above.
>-) If you are not the intended recipient, you are hereby notified that
>any disclosure, copying, distribution or taking of any action in reliance
>on the contents of this email transmission is strictly prohibited.
>-) If you have received this email transmission in error, please notify
>us immediately by telephone to arrange for the return of the original
>transmission to us.
>-)=20
>-) _______________________________________________
>-) pim mailing list
>-) pim@ietf.org
>-) https://www.ietf.org/mailman/listinfo/pim
>-)=20
>_______________________________________________
>pim mailing list
>pim@ietf.org
>https://www.ietf.org/mailman/listinfo/pim


From jeff.tantsura@ericsson.com  Wed Oct 26 15:02:46 2011
Return-Path: <jeff.tantsura@ericsson.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA99221F8B56 for <pim@ietfa.amsl.com>; Wed, 26 Oct 2011 15:02:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R-1yNBr-4kYR for <pim@ietfa.amsl.com>; Wed, 26 Oct 2011 15:02:46 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 3591821F85F1 for <pim@ietf.org>; Wed, 26 Oct 2011 15:02:46 -0700 (PDT)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id p9QM2h9R019069 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 26 Oct 2011 17:02:44 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.232]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Wed, 26 Oct 2011 18:02:43 -0400
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: Mike McBride <mmcbride@forsythe.com>
Date: Wed, 26 Oct 2011 18:02:41 -0400
Thread-Topic: [pim] pop-count ready for wglc?
Thread-Index: AcyUKvyCrRHJhkCFQK6YGBmtZXPbaw==
Message-ID: <CACDD11A.6968%jeff.tantsura@ericsson.com>
In-Reply-To: <CACDD06F.6965%jeff.tantsura@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.13.0.110805
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] pop-count ready for wglc?
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Oct 2011 22:02:47 -0000

Given the Experimental Intended status I'd like to withdraw my previous
comment.=20
--=20
Regards,
Jeff






On 10/26/11 2:58 PM, "Jeff Tantsura" <jeff.tantsura@ericsson.com> wrote:

>+1
>--=20
>Regards,
>Jeff
>
>
>
>On 10/26/11 2:52 PM, "Leonard Giuliano" <lenny@juniper.net> wrote:
>
>>
>>I would support shelving the work.  We would never use OSPF/ISIS to carry
>>unicast accounting info, so why do so in mcast?  Better to leave this up
>>to the application layer.
>>
>>-Lenny
>>
>>On Tue, 25 Oct 2011, Mike McBride wrote:
>>
>>-) We need to hear something. Anything. It's difficult to justify, to the
>>-) IESG, that the wg is rallying behind the draft when there is zero
>>-) response during the wglc. So I'm going to extend this wglc for another
>>-) 2 weeks. Please speak up. If there continues to be zero response, we
>>-) will assume there is no interest in progressing the draft and will
>>-) shelve the wglc for the time being.
>>-)=20
>>-) thanks,
>>-) mike
>>-)=20
>>-) > -----Original Message-----
>>-) > From: Stig Venaas [mailto:stig@venaas.com]
>>-) > Sent: Monday, October 24, 2011 10:13 AM
>>-) > To: Mike McBride
>>-) > Cc: pim@ietf.org
>>-) > Subject: Re: [pim] pop-count ready for wglc?
>>-) >=20
>>-) > On 10/10/2011 2:17 PM, Mike McBride wrote:
>>-) > > Today begins a two week wglc for draft-ietf-pim-pop-count-04.
>>Please
>>-) > review the draft. Please then comment, on the list, with a thumbs up
>>or
>>-) > a thumbs down.
>>-) >=20
>>-) > I haven't seen any comments on the list, and the WGLC is about to
>>end.
>>-) > Please provide your comments and whether you support the draft or
>>not.
>>-) >=20
>>-) > Since I'm now an author of the draft, please regard this request as
>>-) > coming from an author and not a chair.
>>-) >=20
>>-) > I'll leave to Mike to figure out what to do with the draft, I'm just
>>-) > urging you to provide comments.
>>-) >=20
>>-) > Stig
>>-) >=20
>>-) > > thanks,
>>-) > > mike
>>-) > >
>>-) > > http://www.ietf.org/id/draft-ietf-pim-pop-count-04.txt
>>-) > >
>>-) > >> -----Original Message-----
>>-) > >> From: Mike McBride
>>-) > >> Sent: Tuesday, September 27, 2011 8:06 PM
>>-) > >> To: pim@ietf.org
>>-) > >> Subject: pop-count ready for wglc?
>>-) > >>
>>-) > >> We had consensus (5-0) in the Quebec pimwg meeting to issue a
>>wglc
>>-) > for
>>-) > >> the pim-pop-count draft:
>>-) > >>
>>-) > >> http://www.ietf.org/id/draft-ietf-pim-pop-count-04.txt
>>-) > >>
>>-) > >>
>>-) > >> Before doing so we'd like to bring it to the list. If you feel
>>this
>>-) > >> draft is not ready for wglc please speak up. Otherwise we will
>>begin
>>-) > a
>>-) > >> wglc next week.
>>-) > >>
>>-) > >> thanks,
>>-) > >> mike
>>-) > > NOTICE OF CONFIDENTIALITY:
>>-) > > The information contained in this email transmission is
>>confidential
>>-) > information which may contain information that is legally privileged
>>-) > and prohibited from disclosure under applicable law or by
>>contractual
>>-) > agreement.  The information is intended solely for the use of the
>>-) > individual or entity named above.
>>-) > > If you are not the intended recipient, you are hereby notified
>>that
>>-) > any disclosure, copying, distribution or taking of any action in
>>-) > reliance on the contents of this email transmission is strictly
>>-) > prohibited.
>>-) > > If you have received this email transmission in error, please
>>notify
>>-) > us immediately by telephone to arrange for the return of the
>>original
>>-) > transmission to us.
>>-) > >
>>-) > > _______________________________________________
>>-) > > pim mailing list
>>-) > > pim@ietf.org
>>-) > > https://www.ietf.org/mailman/listinfo/pim
>>-)=20
>>-) NOTICE OF CONFIDENTIALITY:
>>-) The information contained in this email transmission is confidential
>>information which may contain information that is legally privileged and
>>prohibited from disclosure under applicable law or by contractual
>>agreement.  The information is intended solely for the use of the
>>individual or entity named above.
>>-) If you are not the intended recipient, you are hereby notified that
>>any disclosure, copying, distribution or taking of any action in reliance
>>on the contents of this email transmission is strictly prohibited.
>>-) If you have received this email transmission in error, please notify
>>us immediately by telephone to arrange for the return of the original
>>transmission to us.
>>-)=20
>>-) _______________________________________________
>>-) pim mailing list
>>-) pim@ietf.org
>>-) https://www.ietf.org/mailman/listinfo/pim
>>-)=20
>>_______________________________________________
>>pim mailing list
>>pim@ietf.org
>>https://www.ietf.org/mailman/listinfo/pim
>
>_______________________________________________
>pim mailing list
>pim@ietf.org
>https://www.ietf.org/mailman/listinfo/pim


From gjshep@gmail.com  Thu Oct 27 08:30:36 2011
Return-Path: <gjshep@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A74B521F8880 for <pim@ietfa.amsl.com>; Thu, 27 Oct 2011 08:30:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.549
X-Spam-Level: 
X-Spam-Status: No, score=-103.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M082wnE1dTIm for <pim@ietfa.amsl.com>; Thu, 27 Oct 2011 08:30:36 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id CE9C221F847D for <pim@ietf.org>; Thu, 27 Oct 2011 08:30:35 -0700 (PDT)
Received: by qyk34 with SMTP id 34so862728qyk.10 for <pim@ietf.org>; Thu, 27 Oct 2011 08:30:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=4zbXYk5buaK31NDl2XlwvXThy5Zxdy4VAIRUqCShYis=; b=WM6zWd5piVToAy0q6JqOQv7QEP6SPTdgHThCOm4GcwPW9cfLjejXyDPu6l94XsLrT9 3+UIhsr3UCslIBPnt3VbFSf7gkTHZ/lccRuMuJlm/AQdE7T0iKBPmTtiRVimjgkJ4T8f NCOFsfHtbgPi35PyeaswoGuNOo3amMyiWSuWA=
MIME-Version: 1.0
Received: by 10.68.1.229 with SMTP id 5mr30608521pbp.88.1319729434979; Thu, 27 Oct 2011 08:30:34 -0700 (PDT)
Received: by 10.142.140.6 with HTTP; Thu, 27 Oct 2011 08:30:34 -0700 (PDT)
In-Reply-To: <20111026144807.X86913@eng-mail01.juniper.net>
References: <8999C52267AF8844B77A280D0CD584C13B46CE2CBA@FTI2K3CMSMBX1.forsythe.com> <CAL3FGfxjXDq682Gp5WN0c2SvJed-qFhjn0tQWe_cs1XpTC0iGw@mail.gmail.com> <8999C52267AF8844B77A280D0CD584C13B4832FDED@FTI2K3CMSMBX1.forsythe.com> <4EA59C83.3010103@venaas.com> <8999C52267AF8844B77A280D0CD584C13B4985B9B7@FTI2K3CMSMBX1.forsythe.com> <20111026144807.X86913@eng-mail01.juniper.net>
Date: Thu, 27 Oct 2011 08:30:34 -0700
Message-ID: <CABFReBo5yrYwqs-U-yyT=UbdGYuH3hqH5QT5_oJ3Uv2JYLeZKw@mail.gmail.com>
From: Greg Shepherd <gjshep@gmail.com>
To: Leonard Giuliano <lenny@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] pop-count ready for wglc?
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: gjshep@gmail.com
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Oct 2011 15:30:36 -0000

Lenny,

I have to disagree with you this time. Pop-count isn't about PIM
carrying accounting information, it's more about PIM distributing
topology (tree) information upstream. And in this case, it IS much
like OSPF and ISIS where every router has a full topology DB which can
be poled out of band if desired. We're just trying to give
PIM/multicast some parity where it's lacking.

I do support this work, if it wasn't already clear. :)

Greg

On Wed, Oct 26, 2011 at 2:52 PM, Leonard Giuliano <lenny@juniper.net> wrote=
:
>
> I would support shelving the work. =A0We would never use OSPF/ISIS to car=
ry
> unicast accounting info, so why do so in mcast? =A0Better to leave this u=
p
> to the application layer.
>
> -Lenny
>
> On Tue, 25 Oct 2011, Mike McBride wrote:
>
> -) We need to hear something. Anything. It's difficult to justify, to the
> -) IESG, that the wg is rallying behind the draft when there is zero
> -) response during the wglc. So I'm going to extend this wglc for another
> -) 2 weeks. Please speak up. If there continues to be zero response, we
> -) will assume there is no interest in progressing the draft and will
> -) shelve the wglc for the time being.
> -)
> -) thanks,
> -) mike
> -)
> -) > -----Original Message-----
> -) > From: Stig Venaas [mailto:stig@venaas.com]
> -) > Sent: Monday, October 24, 2011 10:13 AM
> -) > To: Mike McBride
> -) > Cc: pim@ietf.org
> -) > Subject: Re: [pim] pop-count ready for wglc?
> -) >
> -) > On 10/10/2011 2:17 PM, Mike McBride wrote:
> -) > > Today begins a two week wglc for draft-ietf-pim-pop-count-04. Plea=
se
> -) > review the draft. Please then comment, on the list, with a thumbs up=
 or
> -) > a thumbs down.
> -) >
> -) > I haven't seen any comments on the list, and the WGLC is about to en=
d.
> -) > Please provide your comments and whether you support the draft or no=
t.
> -) >
> -) > Since I'm now an author of the draft, please regard this request as
> -) > coming from an author and not a chair.
> -) >
> -) > I'll leave to Mike to figure out what to do with the draft, I'm just
> -) > urging you to provide comments.
> -) >
> -) > Stig
> -) >
> -) > > thanks,
> -) > > mike
> -) > >
> -) > > http://www.ietf.org/id/draft-ietf-pim-pop-count-04.txt
> -) > >
> -) > >> -----Original Message-----
> -) > >> From: Mike McBride
> -) > >> Sent: Tuesday, September 27, 2011 8:06 PM
> -) > >> To: pim@ietf.org
> -) > >> Subject: pop-count ready for wglc?
> -) > >>
> -) > >> We had consensus (5-0) in the Quebec pimwg meeting to issue a wgl=
c
> -) > for
> -) > >> the pim-pop-count draft:
> -) > >>
> -) > >> http://www.ietf.org/id/draft-ietf-pim-pop-count-04.txt
> -) > >>
> -) > >>
> -) > >> Before doing so we'd like to bring it to the list. If you feel th=
is
> -) > >> draft is not ready for wglc please speak up. Otherwise we will be=
gin
> -) > a
> -) > >> wglc next week.
> -) > >>
> -) > >> thanks,
> -) > >> mike
> -) > > NOTICE OF CONFIDENTIALITY:
> -) > > The information contained in this email transmission is confidenti=
al
> -) > information which may contain information that is legally privileged
> -) > and prohibited from disclosure under applicable law or by contractua=
l
> -) > agreement. =A0The information is intended solely for the use of the
> -) > individual or entity named above.
> -) > > If you are not the intended recipient, you are hereby notified tha=
t
> -) > any disclosure, copying, distribution or taking of any action in
> -) > reliance on the contents of this email transmission is strictly
> -) > prohibited.
> -) > > If you have received this email transmission in error, please noti=
fy
> -) > us immediately by telephone to arrange for the return of the origina=
l
> -) > transmission to us.
> -) > >
> -) > > _______________________________________________
> -) > > pim mailing list
> -) > > pim@ietf.org
> -) > > https://www.ietf.org/mailman/listinfo/pim
> -)
> -) NOTICE OF CONFIDENTIALITY:
> -) The information contained in this email transmission is confidential i=
nformation which may contain information that is legally privileged and pro=
hibited from disclosure under applicable law or by contractual agreement. =
=A0The information is intended solely for the use of the individual or enti=
ty named above.
> -) If you are not the intended recipient, you are hereby notified that an=
y disclosure, copying, distribution or taking of any action in reliance on =
the contents of this email transmission is strictly prohibited.
> -) If you have received this email transmission in error, please notify u=
s immediately by telephone to arrange for the return of the original transm=
ission to us.
> -)
> -) _______________________________________________
> -) pim mailing list
> -) pim@ietf.org
> -) https://www.ietf.org/mailman/listinfo/pim
> -)
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim
>

From eckert@cisco.com  Thu Oct 27 10:57:35 2011
Return-Path: <eckert@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE4E211E807F for <pim@ietfa.amsl.com>; Thu, 27 Oct 2011 10:57:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mu0Ub+FcNNzK for <pim@ietfa.amsl.com>; Thu, 27 Oct 2011 10:57:34 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id AC9F721F8AFF for <pim@ietf.org>; Thu, 27 Oct 2011 10:57:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckert@cisco.com; l=8130; q=dns/txt; s=iport; t=1319738254; x=1320947854; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=pK0lnisdWFf9RhRXzXS5XjsyVrdhMAHw2mxoageHl2k=; b=IEyd34uzDT+aTNT41hS8hCYwiNJpiCLyB5ReHQEzaDiqvMmBWU1xYX8A lMJaO4evLycMnfkqCZ+Z5C41f9oklQR8MFDsWtgELXeQr6NKRR7M0Hd+B BkDaund7u2ILJa3G6nGPV6rYhkyaD6POJVAct4pu6QzGo1rZ7S7+3Zn+1 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: At4AAJeaqU6rRDoH/2dsb2JhbABDmg+PUYEFgXIBAQEEAQEBDwEnLQcLDAQLDgMBAwEBAScHFBMfAwYOEwkSB4doljIBnkyIfgSIBowHkX8
X-IronPort-AV: E=Sophos;i="4.69,414,1315180800"; d="scan'208";a="10749401"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-3.cisco.com with ESMTP; 27 Oct 2011 17:57:34 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p9RHvYY1029275; Thu, 27 Oct 2011 17:57:34 GMT
Received: from mcast-linux1.cisco.com (mdt-linux4 [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id p9RHvYNC002294;  Thu, 27 Oct 2011 10:57:34 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id p9RHvXTA002291; Thu, 27 Oct 2011 10:57:33 -0700
Date: Thu, 27 Oct 2011 10:57:33 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Leonard Giuliano <lenny@juniper.net>
Message-ID: <20111027175733.GI8267@cisco.com>
References: <8999C52267AF8844B77A280D0CD584C13B46CE2CBA@FTI2K3CMSMBX1.forsythe.com> <CAL3FGfxjXDq682Gp5WN0c2SvJed-qFhjn0tQWe_cs1XpTC0iGw@mail.gmail.com> <8999C52267AF8844B77A280D0CD584C13B4832FDED@FTI2K3CMSMBX1.forsythe.com> <4EA59C83.3010103@venaas.com> <8999C52267AF8844B77A280D0CD584C13B4985B9B7@FTI2K3CMSMBX1.forsythe.com> <20111026144807.X86913@eng-mail01.juniper.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20111026144807.X86913@eng-mail01.juniper.net>
User-Agent: Mutt/1.4.2.2i
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] pop-count ready for wglc?
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Oct 2011 17:57:35 -0000

Short version:

I support this work to become experimental RFC. 

Comment on Lennys point:


IGP Route prefixes are not per application flow state.
Multicast (*,G) and (S,G) state is per-application-flow state.
PIM is thereby a much more logical option to carry per-flow application
awareness than IGPs.  That's why i think the comparison PIM with IGPs is
not very strong here.

But even if i went down your argument: How about the free bandwidth
attributes in IGPs that where introduced for RSVP-TE CSPF operations into
IGP LSAs ? And i am not even aware of all LSA carried "additional" information,
but i think there is active work to actually do more in that area.

Long rant version:

I do very much like the idea of continuing to work on solutions
that allows to keep the value of the overall service inside the network
devices and minimize the total number of layers required for the
network operator to do her/his job. Especially when it also reduces the
overall complexity of the solution, improve visilibity and enables
more simply implemented intelligence in the network. 

Pop count does provide a very elegant and simple to implement solution
to provide a set of very crucial eleements of visibility  to the network
operator without relying on however many layers of additional outside 
tools. 

What is the alternative to pop count ? Openflow for multicast with some
controller or an NMS utilizing 5 different MIBs trying to figure out all
this information ?? give me a break!!!. You would never ever be able to
improve the ease-of-use perception of IP multicast as a network service
that way. At best you would create the perception of "IP multicast sucks,
but i found this cool tool from NMS/Controller vendor 'FOO' that made it
actually quite nice to use". 

Layering the solution becomes even more difficult when we try to
utilize pop count type information to drive intelligent actions in the
network.  Admission control based on "tree with smallest number of eyeballs
gets dropped". Or automatic upstream fragmentation or transrating or the
like. And i think nobody has even tried to enlist/brainstom all possible
intelligence that could build on top of it when necessary/beneficial.

Once you mandate that the situation awareness that pop count gives you
only exists at a higher level than the network layer, then all the
intelligence that would depends on it can also only be built outside of
the network layer and routers could not do them autonomously anymore unless
you throw a lot of more complexity into the mix (higher level standardized
coordination between routers).

I think it is an incorrect mantra trying to push up functionality to
higher layers as much as possible. You just create more overall
complexity and more layers. This approach is not a mantra but a type
of reverse engineered justification to what happens when lower layers of
the stack are not innovating (fast enough) and you MUST layer stuff on
top of it to move ahead. 

The correct mantra IMHO is still the same as it was always
in layered systems: Do the work in the layer where it is best suited
to simplify, scale, standardize and drive adoption of the solution.
For pop count type information that seems clearly to be the network layer
with PIM. 

End of longer rant 

Cheers
    Toerless

On Wed, Oct 26, 2011 at 02:52:20PM -0700, Leonard Giuliano wrote:
> 
> I would support shelving the work.  We would never use OSPF/ISIS to carry 
> unicast accounting info, so why do so in mcast?  Better to leave this up 
> to the application layer.
> 
> -Lenny
> 
> On Tue, 25 Oct 2011, Mike McBride wrote:
> 
> -) We need to hear something. Anything. It's difficult to justify, to the 
> -) IESG, that the wg is rallying behind the draft when there is zero 
> -) response during the wglc. So I'm going to extend this wglc for another 
> -) 2 weeks. Please speak up. If there continues to be zero response, we 
> -) will assume there is no interest in progressing the draft and will 
> -) shelve the wglc for the time being.
> -) 
> -) thanks,
> -) mike
> -) 
> -) > -----Original Message-----
> -) > From: Stig Venaas [mailto:stig@venaas.com]
> -) > Sent: Monday, October 24, 2011 10:13 AM
> -) > To: Mike McBride
> -) > Cc: pim@ietf.org
> -) > Subject: Re: [pim] pop-count ready for wglc?
> -) > 
> -) > On 10/10/2011 2:17 PM, Mike McBride wrote:
> -) > > Today begins a two week wglc for draft-ietf-pim-pop-count-04. Please
> -) > review the draft. Please then comment, on the list, with a thumbs up or
> -) > a thumbs down.
> -) > 
> -) > I haven't seen any comments on the list, and the WGLC is about to end.
> -) > Please provide your comments and whether you support the draft or not.
> -) > 
> -) > Since I'm now an author of the draft, please regard this request as
> -) > coming from an author and not a chair.
> -) > 
> -) > I'll leave to Mike to figure out what to do with the draft, I'm just
> -) > urging you to provide comments.
> -) > 
> -) > Stig
> -) > 
> -) > > thanks,
> -) > > mike
> -) > >
> -) > > http://www.ietf.org/id/draft-ietf-pim-pop-count-04.txt
> -) > >
> -) > >> -----Original Message-----
> -) > >> From: Mike McBride
> -) > >> Sent: Tuesday, September 27, 2011 8:06 PM
> -) > >> To: pim@ietf.org
> -) > >> Subject: pop-count ready for wglc?
> -) > >>
> -) > >> We had consensus (5-0) in the Quebec pimwg meeting to issue a wglc
> -) > for
> -) > >> the pim-pop-count draft:
> -) > >>
> -) > >> http://www.ietf.org/id/draft-ietf-pim-pop-count-04.txt
> -) > >>
> -) > >>
> -) > >> Before doing so we'd like to bring it to the list. If you feel this
> -) > >> draft is not ready for wglc please speak up. Otherwise we will begin
> -) > a
> -) > >> wglc next week.
> -) > >>
> -) > >> thanks,
> -) > >> mike
> -) > > NOTICE OF CONFIDENTIALITY:
> -) > > The information contained in this email transmission is confidential
> -) > information which may contain information that is legally privileged
> -) > and prohibited from disclosure under applicable law or by contractual
> -) > agreement.  The information is intended solely for the use of the
> -) > individual or entity named above.
> -) > > If you are not the intended recipient, you are hereby notified that
> -) > any disclosure, copying, distribution or taking of any action in
> -) > reliance on the contents of this email transmission is strictly
> -) > prohibited.
> -) > > If you have received this email transmission in error, please notify
> -) > us immediately by telephone to arrange for the return of the original
> -) > transmission to us.
> -) > >
> -) > > _______________________________________________
> -) > > pim mailing list
> -) > > pim@ietf.org
> -) > > https://www.ietf.org/mailman/listinfo/pim
> -) 
> -) NOTICE OF CONFIDENTIALITY:  
> -) The information contained in this email transmission is confidential information which may contain information that is legally privileged and prohibited from disclosure under applicable law or by contractual agreement.  The information is intended solely for the use of the individual or entity named above.  
> -) If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking of any action in reliance on the contents of this email transmission is strictly prohibited.  
> -) If you have received this email transmission in error, please notify us immediately by telephone to arrange for the return of the original transmission to us.
> -) 
> -) _______________________________________________
> -) pim mailing list
> -) pim@ietf.org
> -) https://www.ietf.org/mailman/listinfo/pim
> -) 
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim

-- 
---
Toerless Eckert, eckert@cisco.com
Cisco NSSTG Systems & Technology Architecture
Network Agnostic: Applications that work best on cheap, stupid networks.
Suicide: Devaluating the intelligent network with network agnostic apps.


From internet-drafts@ietf.org  Thu Oct 27 17:13:52 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AF0E1F0C47; Thu, 27 Oct 2011 17:13:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.58
X-Spam-Level: 
X-Spam-Status: No, score=-102.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0zHMM9eY3mFU; Thu, 27 Oct 2011 17:13:51 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 958F41F0C3E; Thu, 27 Oct 2011 17:13:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.62
Message-ID: <20111028001351.21735.19715.idtracker@ietfa.amsl.com>
Date: Thu, 27 Oct 2011 17:13:51 -0700
Cc: pim@ietf.org
Subject: [pim] I-D Action: draft-ietf-pim-rfc4601bis-01.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Oct 2011 00:13:52 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Protocol Independent Multicast Workin=
g Group of the IETF.

	Title           : Protocol Independent Multicast - Sparse Mode (PIM-SM): P=
rotocol Specification (Revised)
	Author(s)       : Bill Fenner
                          Mark Handley
                          Hugh Holbrook
                          Isidor Kouvelas
                          Rishabh Parekh
                          Zhaohui (Jeffrey) Zhang
                          Lianshu Zheng
	Filename        : draft-ietf-pim-rfc4601bis-01.txt
	Pages           : 132
	Date            : 2011-10-27

   This document specifies Protocol Independent Multicast - Sparse Mode
   (PIM-SM).  PIM-SM is a multicast routing protocol that can use the
   underlying unicast routing information base or a separate multicast-
   capable routing information base.  It builds unidirectional shared
   trees rooted at a Rendezvous Point (RP) per group, and optionally
   creates shortest-path trees per source.

   This document addresses errata filed against RFC 4601, and removes
   the optional (*,*,RP) feature that lacks sufficient deployment
   experience.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pim-rfc4601bis-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-pim-rfc4601bis-01.txt

From rishabhp@gmail.com  Thu Oct 27 17:22:51 2011
Return-Path: <rishabhp@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3CF81F0C4B for <pim@ietfa.amsl.com>; Thu, 27 Oct 2011 17:22:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gjnxPVJpzjgs for <pim@ietfa.amsl.com>; Thu, 27 Oct 2011 17:22:51 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id E85291F0C45 for <pim@ietf.org>; Thu, 27 Oct 2011 17:22:50 -0700 (PDT)
Received: by iabn5 with SMTP id n5so4388657iab.31 for <pim@ietf.org>; Thu, 27 Oct 2011 17:22:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=YVVo1aCVbeTypLy9rJwc7CqqxV85g7ZqoQOmquxtUj0=; b=pPTHJb95pnq1NKw2Eh1cv29nyNh3c0oogWB+T9mFA+rr41kloepIkJ901djfUTnXr4 lkAF8cMHRlwKkuDDxQGAqQ850AfqOo9KVzi7w5jNunobl74753YMCIS/+RQNQ8Kzj0s/ N/Ny3rXtphOfVOuYfAIAiuyt2oZpCeXA5o710=
MIME-Version: 1.0
Received: by 10.231.62.197 with SMTP id y5mr86111ibh.85.1319761369479; Thu, 27 Oct 2011 17:22:49 -0700 (PDT)
Received: by 10.231.199.72 with HTTP; Thu, 27 Oct 2011 17:22:49 -0700 (PDT)
In-Reply-To: <20111028001351.21735.19715.idtracker@ietfa.amsl.com>
References: <20111028001351.21735.19715.idtracker@ietfa.amsl.com>
Date: Thu, 27 Oct 2011 17:22:49 -0700
Message-ID: <CABjMoXaYtWQcYA_dU_cLxfvHN_dxcJjJCDLgWR=-RT_bYh2qmA@mail.gmail.com>
From: Rishabh Parekh <rishabhp@gmail.com>
To: pim@ietf.org
Content-Type: multipart/alternative; boundary=000e0cd4d3e89dbb2104b050e314
Subject: Re: [pim] I-D Action: draft-ietf-pim-rfc4601bis-01.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Oct 2011 00:22:52 -0000

--000e0cd4d3e89dbb2104b050e314
Content-Type: text/plain; charset=ISO-8859-1

This update just addresses some recently filed errata; there is no change
in technical content.

Regards,
-Rishabh.

On Thu, Oct 27, 2011 at 5:13 PM, <internet-drafts@ietf.org> wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This draft is a work item of the Protocol Independent
> Multicast Working Group of the IETF.
>
>        Title           : Protocol Independent Multicast - Sparse Mode
> (PIM-SM): Protocol Specification (Revised)
>        Author(s)       : Bill Fenner
>                          Mark Handley
>                          Hugh Holbrook
>                          Isidor Kouvelas
>                          Rishabh Parekh
>                          Zhaohui (Jeffrey) Zhang
>                          Lianshu Zheng
>        Filename        : draft-ietf-pim-rfc4601bis-01.txt
>        Pages           : 132
>        Date            : 2011-10-27
>
>   This document specifies Protocol Independent Multicast - Sparse Mode
>   (PIM-SM).  PIM-SM is a multicast routing protocol that can use the
>   underlying unicast routing information base or a separate multicast-
>   capable routing information base.  It builds unidirectional shared
>   trees rooted at a Rendezvous Point (RP) per group, and optionally
>   creates shortest-path trees per source.
>
>   This document addresses errata filed against RFC 4601, and removes
>   the optional (*,*,RP) feature that lacks sufficient deployment
>   experience.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-pim-rfc4601bis-01.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-pim-rfc4601bis-01.txt
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim
>

--000e0cd4d3e89dbb2104b050e314
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

This update just addresses some recently filed errata; there is no change i=
n technical content.<br><br>Regards,<br>-Rishabh.<br><br><div class=3D"gmai=
l_quote">On Thu, Oct 27, 2011 at 5:13 PM,  <span dir=3D"ltr">&lt;<a href=3D=
"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a>&gt;</span> w=
rote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">A New Internet-Draft is available from the =
on-line Internet-Drafts directories. This draft is a work item of the Proto=
col Independent Multicast Working Group of the IETF.<br>

<br>
 =A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : Protocol Independent Multicast =
- Sparse Mode (PIM-SM): Protocol Specification (Revised)<br>
 =A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : Bill Fenner<br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Mark Handley<br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Hugh Holbrook<br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Isidor Kouvelas<br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Rishabh Parekh<br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Zhaohui (Jeffrey) Zhang=
<br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Lianshu Zheng<br>
 =A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-ietf-pim-rfc4601bis-01.txt<=
br>
 =A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 132<br>
 =A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2011-10-27<br>
<br>
 =A0 This document specifies Protocol Independent Multicast - Sparse Mode<b=
r>
 =A0 (PIM-SM). =A0PIM-SM is a multicast routing protocol that can use the<b=
r>
 =A0 underlying unicast routing information base or a separate multicast-<b=
r>
 =A0 capable routing information base. =A0It builds unidirectional shared<b=
r>
 =A0 trees rooted at a Rendezvous Point (RP) per group, and optionally<br>
 =A0 creates shortest-path trees per source.<br>
<br>
 =A0 This document addresses errata filed against RFC 4601, and removes<br>
 =A0 the optional (*,*,RP) feature that lacks sufficient deployment<br>
 =A0 experience.<br>
<br>
<br>
A URL for this Internet-Draft is:<br>
<a href=3D"http://www.ietf.org/internet-drafts/draft-ietf-pim-rfc4601bis-01=
.txt" target=3D"_blank">http://www.ietf.org/internet-drafts/draft-ietf-pim-=
rfc4601bis-01.txt</a><br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-drafts/</a><br>
<br>
This Internet-Draft can be retrieved at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/draft-ietf-pim-rfc4601bis-01.=
txt" target=3D"_blank">ftp://ftp.ietf.org/internet-drafts/draft-ietf-pim-rf=
c4601bis-01.txt</a><br>
_______________________________________________<br>
pim mailing list<br>
<a href=3D"mailto:pim@ietf.org">pim@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pim" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/pim</a><br>
</blockquote></div><br>

--000e0cd4d3e89dbb2104b050e314--

From stig@venaas.com  Fri Oct 28 15:17:30 2011
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 113C31F0C46 for <pim@ietfa.amsl.com>; Fri, 28 Oct 2011 15:17:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.481
X-Spam-Level: 
X-Spam-Status: No, score=-102.481 tagged_above=-999 required=5 tests=[AWL=0.118, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2EOlpLkqGCxt for <pim@ietfa.amsl.com>; Fri, 28 Oct 2011 15:17:29 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id 74FFB1F0C38 for <pim@ietf.org>; Fri, 28 Oct 2011 15:17:29 -0700 (PDT)
Received: from [10.33.12.70] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id 72206800D; Sat, 29 Oct 2011 00:17:27 +0200 (CEST)
Message-ID: <4EAB29F5.5020207@venaas.com>
Date: Fri, 28 Oct 2011 15:17:25 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: "pim@ietf.org" <pim@ietf.org>
References: <4EA5B42A.7060900@venaas.com>
In-Reply-To: <4EA5B42A.7060900@venaas.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pim-chairs@tools.ietf.org
Subject: [pim] Draft pim agenda for IETF 82
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Oct 2011 22:17:30 -0000

The draft pim agenda for IETF 82 is available at
http://www.ietf.org/proceedings/82/agenda/pim.txt

I'm also including it below for your convenience. Please let me
know if there are further requests.

Sorry if I have missed any, and please let me know if there are
changes regarding speakers, or you need more/less time.

Stig

Meeting slot: Tuesday 0900-1130

Agenda bashing, document status                Mike/Stig      15 min

draft-ietf-pim-rfc4601bis-01 and questionnaire Vero Zheng     20 min
draft-ietf-pim-ecmp-01                         Yiqun Cai      10 min
draft-ietf-pim-explicit-tracking-00            Hitoshi Asaeda 10 min

draft-hou-pim-drlb-00.txt                      Sri Vallepalli 20 min
draft-hu-pim-route-flap-damping-00.txt         Fangwei Hu     20 min
draft-zzhang-pim-bidir-rp-prune-graft-00       Jeffrey Zhang  20 min
draft-wijnands-pim-source-discovery-bsr        Ice Wijnands   20 min

From internet-drafts@ietf.org  Fri Oct 28 20:13:49 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACCD31F0C4A; Fri, 28 Oct 2011 20:13:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.56
X-Spam-Level: 
X-Spam-Status: No, score=-102.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W8a8FdRA6-vy; Fri, 28 Oct 2011 20:13:49 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 122ED1F0C36; Fri, 28 Oct 2011 20:13:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.62
Message-ID: <20111029031349.2258.77460.idtracker@ietfa.amsl.com>
Date: Fri, 28 Oct 2011 20:13:49 -0700
Cc: pim@ietf.org
Subject: [pim] I-D Action: draft-ietf-pim-ecmp-01.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Oct 2011 03:13:49 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Protocol Independent Multicast Workin=
g Group of the IETF.

	Title           : Protocol Independent Multicast ECMP Redirect
	Author(s)       : Yiqun Cai
                          Liming Wei
                          Heidi Ou
                          Vishal Arya
                          Sunil Jethwani
	Filename        : draft-ietf-pim-ecmp-01.txt
	Pages           : 11
	Date            : 2011-10-28

   A PIM router uses RPF procedure to select an upstream interface and
   router to build forwarding state.  When there are equal cost multiple
   paths (ECMP), existing implementations often use hash algorithms to
   select a path.  Such algorithms do not allow the spread of traffic
   among the ECMPs according to administrative metrics.  This usually
   leads to inefficient or ineffective use of network resources.  This
   document introduces the ECMP Redirect, a mechanism to improve the RPF
   procedure over ECMPs.  It allows ECMP path selection to be based on
   administratively selected metrics, such as data transmission delays,
   path preferences and routing metrics.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pim-ecmp-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-pim-ecmp-01.txt

From hu.fangwei@zte.com.cn  Sun Oct 30 19:34:00 2011
Return-Path: <hu.fangwei@zte.com.cn>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78CDF1F0C62 for <pim@ietfa.amsl.com>; Sun, 30 Oct 2011 19:34:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.221
X-Spam-Level: 
X-Spam-Status: No, score=-95.221 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lf-pvgcn3e0z for <pim@ietfa.amsl.com>; Sun, 30 Oct 2011 19:34:00 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 3DCF321F8906 for <pim@ietf.org>; Sun, 30 Oct 2011 19:33:59 -0700 (PDT)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 41713910329168; Mon, 31 Oct 2011 10:30:00 +0800 (CST)
Received: from [10.30.3.21] by [192.168.168.15] with StormMail ESMTP id 20387.910329168; Mon, 31 Oct 2011 10:33:50 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id p9V2XenE027140 for <pim@ietf.org>; Mon, 31 Oct 2011 10:33:40 +0800 (GMT-8) (envelope-from hu.fangwei@zte.com.cn)
To: "pim@ietf.org" <pim@ietf.org>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.0.4 June 01, 2004
Message-ID: <OF96705003.D9E703F5-ON4825793A.000C5039-4825793A.000E1293@zte.com.cn>
From: hu.fangwei@zte.com.cn
Date: Mon, 31 Oct 2011 10:33:41 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-10-31 10:33:42, Serialize complete at 2011-10-31 10:33:42
Content-Type: multipart/alternative; boundary="=_alternative 000E12904825793A_="
X-MAIL: mse02.zte.com.cn p9V2XenE027140
Subject: [pim] Fwd: New Version Notification for draft-hu-pim-route-flap-damping-00.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Oct 2011 02:34:00 -0000

This is a multipart message in MIME format.
--=_alternative 000E12904825793A_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

SGksIGFsbA0KDQpUaGlzIGRvY3VtZW50IHNwZWNpZmllcyB0aGUgcm91dGUgZmxhcCBkYW1waW5n
IGZ1bmN0aW9ucyBmb3IgDQpQSU0tU00oUkZDNDYwMSksIHRvIHJlZHVjZSB0aGUgcHJvY2Vzc2lu
ZyBsb2FkIGNhdXNlZCBieSByb3V0ZSBmbGFwcyBvbiANCnRoZSBkb3duc3RyZWFtIHJvdXRlcnMu
IEl0IGlzIGEgb3B0aW1pemF0aW9uIHNvbHV0aW9uIGZvciBQSU0tU00uIFRoZSANCmRhbXBpbmcg
ZnVuY3Rpb25zIGFyZSBjYXRlZ29yaXplZCBhY2NvcmRpbmcgdG8gcm91dGUgZmxhcHMgcmVzdWx0
aW5nIGZyb20gDQpkaWZmZXJlbnQgdHlwZXMgb2YgSm9pbi9QcnVuZSBtZXNzYWdlcyByZWNlaXZl
ZC4NClRoZSBuZXcgZGFtcGluZyBzdGF0ZXMgYW5kIHN0YXRlIG1hY2hpbmVzIGFyZSBwcm92aWRl
ZCBpbiB0aGlzIGRvY3VtZW50LCANCndoaWxlIHRoZSBvcmlnaW5hbCBvcGVyYXRpb25zIGFuZCBz
dGF0ZSBtYWNoaW5lcyBvZiB0aGUgUElNIHByb3RvY29sIGFyZSANCnByZXNlcnZlZC4NCg0KQ29t
bWVudHMgYXJlIGFwcHJlY2lhdGVkbHkgd2VsY29tZWQuDQoNCg0KLS0tLS0g16q3osjLIEh1RmFu
Z1dlaTE3NTc3Mi91c2VyL3p0ZV9sdGQgyrG85CAyMDExLTEwLTMxIDEwOjE0IC0tLS0tDQoNCmlu
dGVybmV0LWRyYWZ0c0BpZXRmLm9yZyANCjIwMTEtMTAtMjQgMTY6NTENCg0KytW8/sjLDQpodS5m
YW5nd2VpQHp0ZS5jb20uY24NCrOty80NCnh1LmJlbmNob25nQHp0ZS5jb20uY24sIHpoYW5nLnpo
ZW5nQHp0ZS5jb20uY24sIGphY25pQGphY25pLmNvbSwgDQpodS5mYW5nd2VpQHp0ZS5jb20uY24N
Ctb3zOINCk5ldyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3IgZHJhZnQtaHUtcGltLXJvdXRlLWZs
YXAtZGFtcGluZy0wMC50eHQNCg0KDQoNCg0KDQoNCkEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFm
dC1odS1waW0tcm91dGUtZmxhcC1kYW1waW5nLTAwLnR4dCBoYXMgYmVlbiANCnN1Y2Nlc3NmdWxs
eSBzdWJtaXR0ZWQgYnkgRmFuZ3dlaSBIdSBhbmQgcG9zdGVkIHRvIHRoZSBJRVRGIHJlcG9zaXRv
cnkuDQoNCkZpbGVuYW1lOiAgICAgICAgICAgICAgICAgZHJhZnQtaHUtcGltLXJvdXRlLWZsYXAt
ZGFtcGluZw0KUmV2aXNpb246ICAgICAgICAgICAgICAgICAwMA0KVGl0bGU6ICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIFBJTSBSb3V0ZSBGbGFwIERhbXBpbmcNCkNyZWF0aW9uIGRhdGU6ICAg
ICAgICAgICAgMjAxMS0xMC0yNA0KV0cgSUQ6ICAgICAgICAgICAgICAgICAgICAgICAgICAgIElu
ZGl2aWR1YWwgU3VibWlzc2lvbg0KTnVtYmVyIG9mIHBhZ2VzOiAxOQ0KDQpBYnN0cmFjdDoNCiAg
IFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIHRoZSByb3V0ZSBmbGFwIGRhbXBpbmcgZnVuY3Rpb25z
IGZvciBQSU0tU00NCiAgIFtSRkM0NjAxXSwgdG8gcmVkdWNlIHRoZSBwcm9jZXNzaW5nIGxvYWQg
Y2F1c2VkIGJ5IHRoZSBpbnN0YWJpbGl0eSBvZg0KICAgcm91dGluZyBwZWVycy4NCg0KICANCmh0
dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaHUtcGltLXJvdXRlLWZsYXAtZGFt
cGluZy8NCg0KVGhlIElFVEYgU2VjcmV0YXJpYXQNCg0KDQo=
--=_alternative 000E12904825793A_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9IkRlZmF1bHQgU2VyaWYiPkhpLCBhbGw8L2ZvbnQ+DQo8
YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9IkRlZmF1bHQgU2VyaWYiPlRoaXMgZG9jdW1lbnQg
c3BlY2lmaWVzIHRoZSByb3V0ZQ0KZmxhcCBkYW1waW5nIGZ1bmN0aW9ucyBmb3IgUElNLVNNKFJG
QzQ2MDEpLCB0byByZWR1Y2UgdGhlIHByb2Nlc3NpbmcgbG9hZA0KY2F1c2VkIGJ5IHJvdXRlIGZs
YXBzIG9uIHRoZSBkb3duc3RyZWFtIHJvdXRlcnMuIEl0IGlzIGEgb3B0aW1pemF0aW9uIHNvbHV0
aW9uDQpmb3IgUElNLVNNLiBUaGUgZGFtcGluZyBmdW5jdGlvbnMgYXJlIGNhdGVnb3JpemVkIGFj
Y29yZGluZyB0byByb3V0ZSBmbGFwcw0KcmVzdWx0aW5nIGZyb20gZGlmZmVyZW50IHR5cGVzIG9m
IEpvaW4vUHJ1bmUgbWVzc2FnZXMgcmVjZWl2ZWQuPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBm
YWNlPSJEZWZhdWx0IFNlcmlmIj5UaGUgbmV3IGRhbXBpbmcgc3RhdGVzIGFuZCBzdGF0ZQ0KbWFj
aGluZXMgYXJlIHByb3ZpZGVkIGluIHRoaXMgZG9jdW1lbnQsIHdoaWxlIHRoZSBvcmlnaW5hbCBv
cGVyYXRpb25zIGFuZA0Kc3RhdGUgbWFjaGluZXMgb2YgdGhlIFBJTSBwcm90b2NvbCBhcmUgcHJl
c2VydmVkPC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4uPC9mb250Pg0KPGJy
Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5Db21tZW50cyBhcmUgYXBwcmVj
aWF0ZWRseSB3ZWxjb21lZC48L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2Vy
aWYiPjxicj4NCjwvZm9udD4NCjxicj48Zm9udCBzaXplPTEgY29sb3I9IzgwMDA4MCBmYWNlPSJz
YW5zLXNlcmlmIj4tLS0tLSDXqreiyMsgSHVGYW5nV2VpMTc1NzcyL3VzZXIvenRlX2x0ZA0KyrG8
5CAyMDExLTEwLTMxIDEwOjE0IC0tLS0tPC9mb250Pg0KPGJyPg0KPHRhYmxlIHdpZHRoPTEwMCU+
DQo8dHIgdmFsaWduPXRvcD4NCjx0ZCB3aWR0aD0zNSU+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMt
c2VyaWYiPjxiPmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZzwvYj4NCjwvZm9udD4NCjxwPjxmb250
IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj4yMDExLTEwLTI0IDE2OjUxPC9mb250Pg0KPHRkIHdp
ZHRoPTY0JT4NCjx0YWJsZSB3aWR0aD0xMDAlPg0KPHRyIHZhbGlnbj10b3A+DQo8dGQ+DQo8ZGl2
IGFsaWduPXJpZ2h0Pjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj7K1bz+yMs8L2ZvbnQ+
PC9kaXY+DQo8dGQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPmh1LmZhbmd3ZWlAenRl
LmNvbS5jbjwvZm9udD4NCjx0ciB2YWxpZ249dG9wPg0KPHRkPg0KPGRpdiBhbGlnbj1yaWdodD48
Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+s63LzTwvZm9udD48L2Rpdj4NCjx0ZD48Zm9u
dCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+eHUuYmVuY2hvbmdAenRlLmNvbS5jbiwgemhhbmcu
emhlbmdAenRlLmNvbS5jbiwNCmphY25pQGphY25pLmNvbSwgaHUuZmFuZ3dlaUB6dGUuY29tLmNu
PC9mb250Pg0KPHRyIHZhbGlnbj10b3A+DQo8dGQ+DQo8ZGl2IGFsaWduPXJpZ2h0Pjxmb250IHNp
emU9MSBmYWNlPSJzYW5zLXNlcmlmIj7W98ziPC9mb250PjwvZGl2Pg0KPHRkPjxmb250IHNpemU9
MSBmYWNlPSJzYW5zLXNlcmlmIj5OZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LWh1
LXBpbS1yb3V0ZS1mbGFwLWRhbXBpbmctMDAudHh0PC9mb250PjwvdGFibGU+DQo8YnI+DQo8dGFi
bGU+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD4NCjx0ZD48L3RhYmxlPg0KPGJyPjwvdGFibGU+DQo8
YnI+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yPjx0dD5BIG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJh
ZnQtaHUtcGltLXJvdXRlLWZsYXAtZGFtcGluZy0wMC50eHQNCmhhcyBiZWVuIHN1Y2Nlc3NmdWxs
eSBzdWJtaXR0ZWQgYnkgRmFuZ3dlaSBIdSBhbmQgcG9zdGVkIHRvIHRoZSBJRVRGIHJlcG9zaXRv
cnkuPGJyPg0KPGJyPg0KRmlsZW5hbWU6ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsNCiZuYnNwO2RyYWZ0LWh1LXBpbS1yb3V0ZS1mbGFwLWRh
bXBpbmc8YnI+DQpSZXZpc2lvbjogJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOw0KJm5ic3A7MDA8YnI+DQpUaXRsZTogJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOw0KJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsNClBJTSBSb3V0
ZSBGbGFwIERhbXBpbmc8YnI+DQpDcmVhdGlvbiBkYXRlOiAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsNCiZuYnNwOyAmbmJzcDsyMDExLTEwLTI0PGJyPg0K
V0cgSUQ6ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsNCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7DQpJbmRpdmlkdWFsIFN1Ym1pc3Npb248YnI+DQpOdW1iZXIgb2YgcGFnZXM6
IDE5PGJyPg0KPGJyPg0KQWJzdHJhY3Q6PGJyPg0KICZuYnNwOyBUaGlzIGRvY3VtZW50IGRlc2Ny
aWJlcyB0aGUgcm91dGUgZmxhcCBkYW1waW5nIGZ1bmN0aW9ucyBmb3IgUElNLVNNPGJyPg0KICZu
YnNwOyBbUkZDNDYwMV0sIHRvIHJlZHVjZSB0aGUgcHJvY2Vzc2luZyBsb2FkIGNhdXNlZCBieSB0
aGUgaW5zdGFiaWxpdHkNCm9mPGJyPg0KICZuYnNwOyByb3V0aW5nIHBlZXJzLjwvdHQ+PC9mb250
Pg0KPGJyPjxmb250IHNpemU9Mj48dHQ+PGJyPg0KICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOw0KJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOw0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOw0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyA8YnI+DQpodHRwOi8vZGF0YXRyYWNrZXIuaWV0
Zi5vcmcvZG9jL2RyYWZ0LWh1LXBpbS1yb3V0ZS1mbGFwLWRhbXBpbmcvPGJyPg0KPGJyPg0KVGhl
IElFVEYgU2VjcmV0YXJpYXQ8YnI+DQo8YnI+DQo8L3R0PjwvZm9udD4NCg==
--=_alternative 000E12904825793A_=--


From adrian@olddog.co.uk  Mon Oct 31 12:39:59 2011
Return-Path: <adrian@olddog.co.uk>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 702021F0CB8 for <pim@ietfa.amsl.com>; Mon, 31 Oct 2011 12:39:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zBlqP3RyLpLe for <pim@ietfa.amsl.com>; Mon, 31 Oct 2011 12:39:59 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id AF7B71F0C41 for <pim@ietf.org>; Mon, 31 Oct 2011 12:39:58 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id p9VJdueF029638 for <pim@ietf.org>; Mon, 31 Oct 2011 19:39:56 GMT
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id p9VJdtAS029630 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <pim@ietf.org>; Mon, 31 Oct 2011 19:39:56 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pim@ietf.org>
References: <20111031173846.1666.13885.idtracker@ietfa.amsl.com>
In-Reply-To: <20111031173846.1666.13885.idtracker@ietfa.amsl.com>
Date: Mon, 31 Oct 2011 19:39:55 -0000
Message-ID: <078401cc9804$de901f20$9bb05d60$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQF8c7UbfI5ysIBvUAAsD/8X0LLll5Y3Iaxg
Content-Language: en-gb
Subject: [pim] FW: I-D Action: draft-ietf-multimob-igmp-mld-tuning-02.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Oct 2011 19:39:59 -0000

Heads up.
Adrian

> -----Original Message-----
> From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org]
> On Behalf Of internet-drafts@ietf.org
> Sent: 31 October 2011 17:39
> To: i-d-announce@ietf.org
> Cc: multimob@ietf.org
> Subject: I-D Action: draft-ietf-multimob-igmp-mld-tuning-02.txt
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> This draft is a work item of the Multicast Mobility Working Group of the IETF.
> 
> 	Title           : Tuning the Behavior of IGMP and MLD for Routers in
Mobile
> and Wireless Networks
> 	Author(s)       : Hitoshi Asaeda
>                           Hui Liu
>                           Qin Wu
> 	Filename        : draft-ietf-multimob-igmp-mld-tuning-02.txt
> 	Pages           : 18
> 	Date            : 2011-10-31
> 
>    IGMP and MLD are the protocols used by hosts and multicast routers to
>    exchange their IP multicast group memberships with each other.  This
>    document describes the ways of IGMPv3 and MLDv2 protocol optimization
>    for mobility, and aims to become a guideline for query and other
>    timers and values tuning.
> 
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-multimob-igmp-mld-tuning-02.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-multimob-igmp-mld-tuning-02.txt
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

