
From tena@huawei.com  Fri Apr 29 15:58:10 2011
Return-Path: <tena@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 A52A8E06AD; Fri, 29 Apr 2011 15:58:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level: 
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[AWL=2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BBJ6Az+juLRu; Fri, 29 Apr 2011 15:58:10 -0700 (PDT)
Received: from usaga04-in.huawei.com (usaga04-in.huawei.com [206.16.17.180]) by ietfa.amsl.com (Postfix) with ESMTP id 0AE63E0698; Fri, 29 Apr 2011 15:58:10 -0700 (PDT)
Received: from huawei.com (usaga04-in [172.18.4.101]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LKF00MWCRSXB4@usaga04-in.huawei.com>; Fri, 29 Apr 2011 17:58:09 -0500 (CDT)
Received: from TingZousc1 ([10.193.34.188]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LKF009NURSUYC@usaga04-in.huawei.com>; Fri, 29 Apr 2011 17:58:09 -0500 (CDT)
Date: Fri, 29 Apr 2011 15:58:10 -0700
From: Tina Tsou <tena@huawei.com>
To: multrans@ietf.org
Message-id: <009401cc06c0$eaa919e0$bffb4da0$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcwGwOluKJ5ympwvR4KrSLJ5rPlZEA==
X-Mailman-Approved-At: Mon, 02 May 2011 09:16:43 -0700
Cc: 'MBONED WG' <mboned@ietf.org>, pim@ietf.org
Subject: [pim] Comments on Dual Stack case
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, 29 Apr 2011 22:58:10 -0000

Hi all,
Just bring some comments on the dual stack case for the new problem
statement I-D based on
https://datatracker.ietf.org/doc/draft-jaclee-behave-v4v6-mcast-ps/. And I
also suggest the new problem statement I-D being
draft-jaclee-multrans-v4v6-mcast-ps, since it is not ONLY behave any more.

I cc pim@ietf.org and mboned@ietf.org looking for multicast expertise to
help on input to this new problem statement.

Comments on Dual Stack case are below, inspired by talk with Stig.
1. Even in the native dual stack case, you want to save bandwidth, not put
two copy of bandwidth under one source.

2. For P2MP case, the receivers are part of IPv4, part of IPv6, this is
problem.

3. For video conference, you have 30 people, 15 are v4, 15 are v6, and any
of them can send their videos (everyone has a webcam and microphone).


We keep our promises with one another - no matter what!

Best Regards,
Tina TSOU
http://tinatsou.weebly.com/contact.html




From mounir.kellil@cea.fr  Mon May  2 08:09:43 2011
Return-Path: <mounir.kellil@cea.fr>
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 A48C9E06AD; Mon,  2 May 2011 08:09:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WKBPhz9crKHg; Mon,  2 May 2011 08:09:43 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id 9EAAFE066E; Mon,  2 May 2011 08:09:42 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.2) with ESMTP id p42F9XsH016934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 2 May 2011 17:09:34 +0200
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id p42F9XKD030153; Mon, 2 May 2011 17:09:33 +0200 (envelope-from mounir.kellil@cea.fr)
Received: from excah-b0.intra.cea.fr (excah-b0.intra.cea.fr [132.166.88.85]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.1) with ESMTP id p42F9XGq018937; Mon, 2 May 2011 17:09:33 +0200
Received: from levau.intra.cea.fr (132.166.88.52) by excah-b0.intra.cea.fr (132.166.88.85) with Microsoft SMTP Server id 14.1.270.1; Mon, 2 May 2011 17:09:33 +0200
Received: from LODERI.intra.cea.fr ([132.166.64.47]) by levau.intra.cea.fr with Microsoft SMTPSVC(6.0.3790.4675); Mon, 2 May 2011 17:09:33 +0200
x-mimeole: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 2 May 2011 17:09:32 +0200
Message-ID: <A2408947975D7A4C95A0DD337F638258021C7FC6@LODERI.intra.cea.fr>
In-Reply-To: <009401cc06c0$eaa919e0$bffb4da0$@com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [multrans] Comments on Dual Stack case
Thread-Index: AcwGwOluKJ5ympwvR4KrSLJ5rPlZEACF+jLg
References: <009401cc06c0$eaa919e0$bffb4da0$@com>
From: KELLIL Mounir <mounir.kellil@cea.fr>
To: Tina Tsou <tena@huawei.com>
X-OriginalArrivalTime: 02 May 2011 15:09:33.0028 (UTC) FILETIME=[F13FBA40:01CC08DA]
X-TM-AS-Product-Ver: SMEX-10.0.0.4152-6.500.1024-18110.007
X-TM-AS-Result: No--24.229000-8.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
X-Mailman-Approved-At: Mon, 02 May 2011 09:17:54 -0700
Cc: MBONED WG <mboned@ietf.org>, multrans@ietf.org, pim@ietf.org
Subject: Re: [pim] [multrans] Comments on Dual Stack case
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, 02 May 2011 15:09:43 -0000

Hi Tina,

I think the problem you are addressing is interesting. It reminds me a =
work we've done in our team a few months ago (an old draft: =
http://tools.ietf.org/html/draft-kellil-sam-mtocp-01). We addressed the =
multicasting problem in a heterogeneous IP network (heterogeneity in =
terms of multicast support and IP protocol version). We proposed an =
overlay paradigm to be applied at the transport layer. Overlay nodes are =
in charge of forwarding traffic, but also translating IPv4 packets into =
IPv6 packets and vice versa. Maybe this work (and probably others from =
IRTF's SAMRG group) could be quoted as a "state-of-the-art". Just a =
suggestion...
=20

Regards

Mounir KELLIL

CEA LIST
web : http://www-list.cea.fr
=20
> -----Message d'origine-----
> De=A0: multrans-bounces@ietf.org [mailto:multrans-bounces@ietf.org] De =
la
> part de Tina Tsou
> Envoy=E9=A0: samedi 30 avril 2011 00:58
> =C0=A0: multrans@ietf.org
> Cc=A0: 'MBONED WG'; pim@ietf.org
> Objet=A0: [multrans] Comments on Dual Stack case
>=20
> Hi all,
> Just bring some comments on the dual stack case for the new problem
> statement I-D based on
> https://datatracker.ietf.org/doc/draft-jaclee-behave-v4v6-mcast-ps/.
> And I
> also suggest the new problem statement I-D being
> draft-jaclee-multrans-v4v6-mcast-ps, since it is not ONLY behave any
> more.
>=20
> I cc pim@ietf.org and mboned@ietf.org looking for multicast expertise
> to
> help on input to this new problem statement.
>=20
> Comments on Dual Stack case are below, inspired by talk with Stig.
> 1. Even in the native dual stack case, you want to save bandwidth, not
> put
> two copy of bandwidth under one source.
>=20
> 2. For P2MP case, the receivers are part of IPv4, part of IPv6, this =
is
> problem.
>=20
> 3. For video conference, you have 30 people, 15 are v4, 15 are v6, and
> any
> of them can send their videos (everyone has a webcam and microphone).
>=20
>=20
> We keep our promises with one another - no matter what!
>=20
> Best Regards,
> Tina TSOU
> http://tinatsou.weebly.com/contact.html
>=20
>=20
>=20
> _______________________________________________
> multrans mailing list
> multrans@ietf.org
> https://www.ietf.org/mailman/listinfo/multrans

From tena@huawei.com  Mon May  2 11:28:49 2011
Return-Path: <tena@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 E7369E0718; Mon,  2 May 2011 11:28:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.599
X-Spam-Level: 
X-Spam-Status: No, score=-105.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dnLfqjuASKmr; Mon,  2 May 2011 11:28:49 -0700 (PDT)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by ietfa.amsl.com (Postfix) with ESMTP id 5F1D5E0678; Mon,  2 May 2011 11:28:49 -0700 (PDT)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LKK00BJ2ZC03I@usaga02-in.huawei.com>; Mon, 02 May 2011 11:28:49 -0700 (PDT)
Received: from TingZousc1 ([10.193.34.188]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LKK000ZCZBZYG@usaga02-in.huawei.com>; Mon, 02 May 2011 11:28:48 -0700 (PDT)
Date: Mon, 02 May 2011 11:28:54 -0700
From: Tina Tsou <tena@huawei.com>
In-reply-to: <A2408947975D7A4C95A0DD337F638258021C7FC6@LODERI.intra.cea.fr>
To: 'KELLIL Mounir' <mounir.kellil@cea.fr>
Message-id: <018701cc08f6$cb23cd80$616b6880$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=ISO-8859-1
Content-language: en-us
Content-transfer-encoding: quoted-printable
Thread-index: AcwGwOluKJ5ympwvR4KrSLJ5rPlZEACF+jLgAAdmFIA=
References: <009401cc06c0$eaa919e0$bffb4da0$@com> <A2408947975D7A4C95A0DD337F638258021C7FC6@LODERI.intra.cea.fr>
Cc: 'MBONED WG' <mboned@ietf.org>, multrans@ietf.org, pim@ietf.org
Subject: Re: [pim] [multrans] Comments on Dual Stack case
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, 02 May 2011 18:28:50 -0000

Bonjour Mounir,
Thank you. I read draft-kellil-sam-mtocp-01, it is useful to multrans. =
Do
you consider dual stack network and/or dual stack source?
How is the status of IRTF's SAMRG group? Is it time to move some of the
research result into IETF now?


We keep our promises with one another =96 no matter what!

Best Regards,
Tina TSOU
http://tinatsou.weebly.com/contact.html


-----Original Message-----
From: KELLIL Mounir [mailto:mounir.kellil@cea.fr]=20
Sent: Monday, May 02, 2011 8:10 AM
To: Tina Tsou
Cc: MBONED WG; pim@ietf.org; multrans@ietf.org
Subject: RE: [multrans] Comments on Dual Stack case

Hi Tina,

I think the problem you are addressing is interesting. It reminds me a =
work
we've done in our team a few months ago (an old draft:
http://tools.ietf.org/html/draft-kellil-sam-mtocp-01). We addressed the
multicasting problem in a heterogeneous IP network (heterogeneity in =
terms
of multicast support and IP protocol version). We proposed an overlay
paradigm to be applied at the transport layer. Overlay nodes are in =
charge
of forwarding traffic, but also translating IPv4 packets into IPv6 =
packets
and vice versa. Maybe this work (and probably others from IRTF's SAMRG
group) could be quoted as a "state-of-the-art". Just a suggestion...
=20

Regards

Mounir KELLIL

CEA LIST
web : http://www-list.cea.fr
=20
> -----Message d'origine-----
> De=A0: multrans-bounces@ietf.org [mailto:multrans-bounces@ietf.org] De =
la
> part de Tina Tsou
> Envoy=E9=A0: samedi 30 avril 2011 00:58
> =C0=A0: multrans@ietf.org
> Cc=A0: 'MBONED WG'; pim@ietf.org
> Objet=A0: [multrans] Comments on Dual Stack case
>=20
> Hi all,
> Just bring some comments on the dual stack case for the new problem
> statement I-D based on
> https://datatracker.ietf.org/doc/draft-jaclee-behave-v4v6-mcast-ps/.
> And I
> also suggest the new problem statement I-D being
> draft-jaclee-multrans-v4v6-mcast-ps, since it is not ONLY behave any
> more.
>=20
> I cc pim@ietf.org and mboned@ietf.org looking for multicast expertise
> to
> help on input to this new problem statement.
>=20
> Comments on Dual Stack case are below, inspired by talk with Stig.
> 1. Even in the native dual stack case, you want to save bandwidth, not
> put
> two copy of bandwidth under one source.
>=20
> 2. For P2MP case, the receivers are part of IPv4, part of IPv6, this =
is
> problem.
>=20
> 3. For video conference, you have 30 people, 15 are v4, 15 are v6, and
> any
> of them can send their videos (everyone has a webcam and microphone).
>=20
>=20
> We keep our promises with one another - no matter what!
>=20
> Best Regards,
> Tina TSOU
> http://tinatsou.weebly.com/contact.html
>=20
>=20
>=20
> _______________________________________________
> multrans mailing list
> multrans@ietf.org
> https://www.ietf.org/mailman/listinfo/multrans


From tena@huawei.com  Mon May  2 11:45:48 2011
Return-Path: <tena@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 16581E071B; Mon,  2 May 2011 11:45:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.742
X-Spam-Level: 
X-Spam-Status: No, score=-105.742 tagged_above=-999 required=5 tests=[AWL=0.857, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7iE+L0QD6dQM; Mon,  2 May 2011 11:45:46 -0700 (PDT)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by ietfa.amsl.com (Postfix) with ESMTP id 97F96E06E6; Mon,  2 May 2011 11:45:46 -0700 (PDT)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LKL00B060493I@usaga02-in.huawei.com>; Mon, 02 May 2011 11:45:46 -0700 (PDT)
Received: from TingZousc1 ([10.193.34.188]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LKL00DZU048YO@usaga02-in.huawei.com>; Mon, 02 May 2011 11:45:45 -0700 (PDT)
Date: Mon, 02 May 2011 11:45:51 -0700
From: Tina Tsou <tena@huawei.com>
In-reply-to: <BLU0-SMTP5011B891313371C358E82ED89F0@phx.gbl>
To: 'Tom Taylor' <tom111.taylor@bell.net>, multrans@ietf.org
Message-id: <018f01cc08f9$299b8a40$7cd29ec0$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcwI+AqeuIFFwgS0RLqTX3uoSYB8fQAAHZSg
References: <BLU0-SMTP5011B891313371C358E82ED89F0@phx.gbl>
Cc: 'MBONED WG' <mboned@ietf.org>, pim@ietf.org
Subject: Re: [pim] [multrans] How does the receiver initially acquire the <Source, Group> address pair?
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, 02 May 2011 18:45:48 -0000

Thank you, Tom.
Your question is valid. I also want to get the verification from multicast
expertise.
Again, may I invite the interested experts from PIM and MBONED to subscribe
to multrans mailing list?

The current version of problem statement talks about dual stack source. In
my mind, we also need to consider dual stack network, since it is the most
possible case for some operators.


We keep our promises with one another - no matter what!

Best Regards,
Tina TSOU
http://tinatsou.weebly.com/contact.html


-----Original Message-----
From: multrans-bounces@ietf.org [mailto:multrans-bounces@ietf.org] On Behalf
Of Tom Taylor
Sent: Monday, May 02, 2011 11:37 AM
To: multrans@ietf.org
Subject: [multrans] How does the receiver initially acquire the <Source,
Group> address pair?

I am thinking of the IPTV case.

I need help in understanding how receiver address acquisition works in 
the absence of v4/v6 transition issues. I assume the receiver gets the 
address pair from some sort of signalling exchange with a network node 
(please verify), but would this node be located in the core network 
serving the receiver or hang off the backbone network beyond that (which 
is where I assume the sources lie)?

Of course, in some cases the addresses could be configured by management 
action.

Tom Taylor
_______________________________________________
multrans mailing list
multrans@ietf.org
https://www.ietf.org/mailman/listinfo/multrans


From tena@huawei.com  Tue May  3 17:21:51 2011
Return-Path: <tena@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 EA46BE074E; Tue,  3 May 2011 17:21:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.999
X-Spam-Level: 
X-Spam-Status: No, score=-105.999 tagged_above=-999 required=5 tests=[AWL=0.600, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D87gKVqhuTwh; Tue,  3 May 2011 17:21:50 -0700 (PDT)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by ietfa.amsl.com (Postfix) with ESMTP id 52A93E06CE; Tue,  3 May 2011 17:21:50 -0700 (PDT)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LKN00LGFACCN3@usaga02-in.huawei.com>; Tue, 03 May 2011 17:21:48 -0700 (PDT)
Received: from TingZousc1 ([10.193.34.188]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LKN00B1XACBF8@usaga02-in.huawei.com>; Tue, 03 May 2011 17:21:48 -0700 (PDT)
Date: Tue, 03 May 2011 17:21:51 -0700
From: Tina Tsou <tena@huawei.com>
In-reply-to: <A2408947975D7A4C95A0DD337F638258021C7FFD@LODERI.intra.cea.fr>
To: 'KELLIL Mounir' <mounir.kellil@cea.fr>
Message-id: <012c01cc09f1$441cacc0$cc560640$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=ISO-8859-1
Content-language: en-us
Content-transfer-encoding: quoted-printable
Thread-index: AcwGwOluKJ5ympwvR4KrSLJ5rPlZEACF+jLgAAdmFIAAHIpN4AAiDQsQ
References: <009401cc06c0$eaa919e0$bffb4da0$@com> <A2408947975D7A4C95A0DD337F638258021C7FC6@LODERI.intra.cea.fr> <018701cc08f6$cb23cd80$616b6880$@com> <A2408947975D7A4C95A0DD337F638258021C7FFD@LODERI.intra.cea.fr>
Cc: 'MBONED WG' <mboned@ietf.org>, multrans@ietf.org, pim@ietf.org
Subject: Re: [pim] [multrans] Comments on Dual Stack case
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, 04 May 2011 00:21:52 -0000

Bonjour Mounir,
If you consider a dual-stack network only, that's what we are looking =
for.

Would you review
https://datatracker.ietf.org/doc/draft-jaclee-behave-v4v6-mcast-ps/, and
send out your comments or proposed text to reflect the issues of a dual
stack network, which is not covered by the current version?

Merci.

Yiu Lee is editing the XML file.


We keep our promises with one another =96 no matter what!

Best Regards,
Tina TSOU
http://tinatsou.weebly.com/contact.html


-----Original Message-----
From: KELLIL Mounir [mailto:mounir.kellil@cea.fr]=20
Sent: Tuesday, May 03, 2011 1:12 AM
To: Tina Tsou
Cc: MBONED WG; pim@ietf.org; multrans@ietf.org
Subject: RE: [multrans] Comments on Dual Stack case

Bonjour Tina,

We consider a dual-stack network only. The source could be IPv4 only or =
IPv6
only, not necessarily both. Regarding SAMRG, they normally intend to =
push
the work (not ours) further to IETF. But, honestly, I am not aware of =
their
current status.=20

BTW, I will be happy to follow the discussions on multirans=20

Best regards

Mounir

Mounir KELLIL
CEA LIST
e-mail : mounir.kellil@cea.fr
web : http://www-list.cea.fr
=20
> -----Message d'origine-----
> De=A0: Tina Tsou [mailto:tena@huawei.com]
> Envoy=E9=A0: lundi 2 mai 2011 20:29
> =C0=A0: KELLIL Mounir
> Cc=A0: 'MBONED WG'; pim@ietf.org; multrans@ietf.org
> Objet=A0: RE: [multrans] Comments on Dual Stack case
>=20
> Bonjour Mounir,
> Thank you. I read draft-kellil-sam-mtocp-01, it is useful to multrans.
> Do
> you consider dual stack network and/or dual stack source?
> How is the status of IRTF's SAMRG group? Is it time to move some of =
the
> research result into IETF now?
>=20
>=20
> We keep our promises with one another - no matter what!
>=20
> Best Regards,
> Tina TSOU
> http://tinatsou.weebly.com/contact.html
>=20
>=20
> -----Original Message-----
> From: KELLIL Mounir [mailto:mounir.kellil@cea.fr]
> Sent: Monday, May 02, 2011 8:10 AM
> To: Tina Tsou
> Cc: MBONED WG; pim@ietf.org; multrans@ietf.org
> Subject: RE: [multrans] Comments on Dual Stack case
>=20
> Hi Tina,
>=20
> I think the problem you are addressing is interesting. It reminds me a
> work
> we've done in our team a few months ago (an old draft:
> http://tools.ietf.org/html/draft-kellil-sam-mtocp-01). We addressed =
the
> multicasting problem in a heterogeneous IP network (heterogeneity in
> terms
> of multicast support and IP protocol version). We proposed an overlay
> paradigm to be applied at the transport layer. Overlay nodes are in
> charge
> of forwarding traffic, but also translating IPv4 packets into IPv6
> packets
> and vice versa. Maybe this work (and probably others from IRTF's SAMRG
> group) could be quoted as a "state-of-the-art". Just a suggestion...
>=20
>=20
> Regards
>=20
> Mounir KELLIL
>=20
> CEA LIST
> web : http://www-list.cea.fr
>=20
> > -----Message d'origine-----
> > De=A0: multrans-bounces@ietf.org [mailto:multrans-bounces@ietf.org] =
De
> la
> > part de Tina Tsou
> > Envoy=E9=A0: samedi 30 avril 2011 00:58
> > =C0=A0: multrans@ietf.org
> > Cc=A0: 'MBONED WG'; pim@ietf.org
> > Objet=A0: [multrans] Comments on Dual Stack case
> >
> > Hi all,
> > Just bring some comments on the dual stack case for the new problem
> > statement I-D based on
> > https://datatracker.ietf.org/doc/draft-jaclee-behave-v4v6-mcast-ps/.
> > And I
> > also suggest the new problem statement I-D being
> > draft-jaclee-multrans-v4v6-mcast-ps, since it is not ONLY behave any
> > more.
> >
> > I cc pim@ietf.org and mboned@ietf.org looking for multicast =
expertise
> > to
> > help on input to this new problem statement.
> >
> > Comments on Dual Stack case are below, inspired by talk with Stig.
> > 1. Even in the native dual stack case, you want to save bandwidth,
> not
> > put
> > two copy of bandwidth under one source.
> >
> > 2. For P2MP case, the receivers are part of IPv4, part of IPv6, this
> is
> > problem.
> >
> > 3. For video conference, you have 30 people, 15 are v4, 15 are v6,
> and
> > any
> > of them can send their videos (everyone has a webcam and =
microphone).
> >
> >
> > We keep our promises with one another - no matter what!
> >
> > Best Regards,
> > Tina TSOU
> > http://tinatsou.weebly.com/contact.html
> >
> >
> >
> > _______________________________________________
> > multrans mailing list
> > multrans@ietf.org
> > https://www.ietf.org/mailman/listinfo/multrans



From mounir.kellil@cea.fr  Tue May  3 01:11:51 2011
Return-Path: <mounir.kellil@cea.fr>
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 036DEE068B; Tue,  3 May 2011 01:11:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xbXqde-IMEvc; Tue,  3 May 2011 01:11:50 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) by ietfa.amsl.com (Postfix) with ESMTP id E84DAE0688; Tue,  3 May 2011 01:11:49 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.2) with ESMTP id p438BcTW020905 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 3 May 2011 10:11:38 +0200
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id p438Bc4Z010688; Tue, 3 May 2011 10:11:38 +0200 (envelope-from mounir.kellil@cea.fr)
Received: from EXCAH-B1.intra.cea.fr (excah-b1.intra.cea.fr [132.166.88.86]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.1) with ESMTP id p438Bcrc018505; Tue, 3 May 2011 10:11:38 +0200
Received: from levau.intra.cea.fr (132.166.88.52) by EXCAH-B1.intra.cea.fr (132.166.88.86) with Microsoft SMTP Server id 14.1.270.1; Tue, 3 May 2011 10:11:38 +0200
Received: from LODERI.intra.cea.fr ([132.166.64.47]) by levau.intra.cea.fr with Microsoft SMTPSVC(6.0.3790.4675); Tue, 3 May 2011 10:11:38 +0200
x-mimeole: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 3 May 2011 10:11:37 +0200
Message-ID: <A2408947975D7A4C95A0DD337F638258021C7FFD@LODERI.intra.cea.fr>
In-Reply-To: <018701cc08f6$cb23cd80$616b6880$@com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [multrans] Comments on Dual Stack case
Thread-Index: AcwGwOluKJ5ympwvR4KrSLJ5rPlZEACF+jLgAAdmFIAAHIpN4A==
References: <009401cc06c0$eaa919e0$bffb4da0$@com> <A2408947975D7A4C95A0DD337F638258021C7FC6@LODERI.intra.cea.fr> <018701cc08f6$cb23cd80$616b6880$@com>
From: KELLIL Mounir <mounir.kellil@cea.fr>
To: Tina Tsou <tena@huawei.com>
X-OriginalArrivalTime: 03 May 2011 08:11:38.0021 (UTC) FILETIME=[B9CB0D50:01CC0969]
X-TM-AS-Product-Ver: SMEX-10.0.0.4152-6.500.1024-18112.002
X-TM-AS-Result: No--38.721600-8.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
X-Mailman-Approved-At: Wed, 04 May 2011 10:22:19 -0700
Cc: MBONED WG <mboned@ietf.org>, multrans@ietf.org, pim@ietf.org
Subject: Re: [pim] [multrans] Comments on Dual Stack case
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, 03 May 2011 08:11:51 -0000

Bonjour Tina,

We consider a dual-stack network only. The source could be IPv4 only or =
IPv6 only, not necessarily both. Regarding SAMRG, they normally intend =
to push the work (not ours) further to IETF. But, honestly, I am not =
aware of their current status.=20

BTW, I will be happy to follow the discussions on multirans=20

Best regards

Mounir

Mounir KELLIL
CEA LIST
e-mail : mounir.kellil@cea.fr
web : http://www-list.cea.fr
=20
> -----Message d'origine-----
> De=A0: Tina Tsou [mailto:tena@huawei.com]
> Envoy=E9=A0: lundi 2 mai 2011 20:29
> =C0=A0: KELLIL Mounir
> Cc=A0: 'MBONED WG'; pim@ietf.org; multrans@ietf.org
> Objet=A0: RE: [multrans] Comments on Dual Stack case
>=20
> Bonjour Mounir,
> Thank you. I read draft-kellil-sam-mtocp-01, it is useful to multrans.
> Do
> you consider dual stack network and/or dual stack source?
> How is the status of IRTF's SAMRG group? Is it time to move some of =
the
> research result into IETF now?
>=20
>=20
> We keep our promises with one another - no matter what!
>=20
> Best Regards,
> Tina TSOU
> http://tinatsou.weebly.com/contact.html
>=20
>=20
> -----Original Message-----
> From: KELLIL Mounir [mailto:mounir.kellil@cea.fr]
> Sent: Monday, May 02, 2011 8:10 AM
> To: Tina Tsou
> Cc: MBONED WG; pim@ietf.org; multrans@ietf.org
> Subject: RE: [multrans] Comments on Dual Stack case
>=20
> Hi Tina,
>=20
> I think the problem you are addressing is interesting. It reminds me a
> work
> we've done in our team a few months ago (an old draft:
> http://tools.ietf.org/html/draft-kellil-sam-mtocp-01). We addressed =
the
> multicasting problem in a heterogeneous IP network (heterogeneity in
> terms
> of multicast support and IP protocol version). We proposed an overlay
> paradigm to be applied at the transport layer. Overlay nodes are in
> charge
> of forwarding traffic, but also translating IPv4 packets into IPv6
> packets
> and vice versa. Maybe this work (and probably others from IRTF's SAMRG
> group) could be quoted as a "state-of-the-art". Just a suggestion...
>=20
>=20
> Regards
>=20
> Mounir KELLIL
>=20
> CEA LIST
> web : http://www-list.cea.fr
>=20
> > -----Message d'origine-----
> > De=A0: multrans-bounces@ietf.org [mailto:multrans-bounces@ietf.org] =
De
> la
> > part de Tina Tsou
> > Envoy=E9=A0: samedi 30 avril 2011 00:58
> > =C0=A0: multrans@ietf.org
> > Cc=A0: 'MBONED WG'; pim@ietf.org
> > Objet=A0: [multrans] Comments on Dual Stack case
> >
> > Hi all,
> > Just bring some comments on the dual stack case for the new problem
> > statement I-D based on
> > https://datatracker.ietf.org/doc/draft-jaclee-behave-v4v6-mcast-ps/.
> > And I
> > also suggest the new problem statement I-D being
> > draft-jaclee-multrans-v4v6-mcast-ps, since it is not ONLY behave any
> > more.
> >
> > I cc pim@ietf.org and mboned@ietf.org looking for multicast =
expertise
> > to
> > help on input to this new problem statement.
> >
> > Comments on Dual Stack case are below, inspired by talk with Stig.
> > 1. Even in the native dual stack case, you want to save bandwidth,
> not
> > put
> > two copy of bandwidth under one source.
> >
> > 2. For P2MP case, the receivers are part of IPv4, part of IPv6, this
> is
> > problem.
> >
> > 3. For video conference, you have 30 people, 15 are v4, 15 are v6,
> and
> > any
> > of them can send their videos (everyone has a webcam and =
microphone).
> >
> >
> > We keep our promises with one another - no matter what!
> >
> > Best Regards,
> > Tina TSOU
> > http://tinatsou.weebly.com/contact.html
> >
> >
> >
> > _______________________________________________
> > multrans mailing list
> > multrans@ietf.org
> > https://www.ietf.org/mailman/listinfo/multrans


From mounir.kellil@cea.fr  Wed May  4 00:56:19 2011
Return-Path: <mounir.kellil@cea.fr>
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 4D46EE0756; Wed,  4 May 2011 00:56:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p6JUp2qFDHDm; Wed,  4 May 2011 00:56:18 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id 25587E06D4; Wed,  4 May 2011 00:56:17 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.2) with ESMTP id p447u8pI021297 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 4 May 2011 09:56:09 +0200
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id p447u8Zs007437; Wed, 4 May 2011 09:56:08 +0200 (envelope-from mounir.kellil@cea.fr)
Received: from EXCAH-A3.intra.cea.fr (excah-a3.intra.cea.fr [132.166.88.77]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.1) with ESMTP id p447u8r7007952; Wed, 4 May 2011 09:56:08 +0200
Received: from mansart.intra.cea.fr (132.166.88.54) by EXCAH-A3.intra.cea.fr (132.166.88.77) with Microsoft SMTP Server id 14.1.270.1; Wed, 4 May 2011 09:56:08 +0200
Received: from LODERI.intra.cea.fr ([132.166.64.47]) by mansart.intra.cea.fr with Microsoft SMTPSVC(6.0.3790.4675); Wed, 4 May 2011 09:56:07 +0200
x-mimeole: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 4 May 2011 09:56:06 +0200
Message-ID: <A2408947975D7A4C95A0DD337F638258021C8066@LODERI.intra.cea.fr>
In-Reply-To: <012c01cc09f1$441cacc0$cc560640$@com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [multrans] Comments on Dual Stack case
Thread-Index: AcwGwOluKJ5ympwvR4KrSLJ5rPlZEACF+jLgAAdmFIAAHIpN4AAiDQsQAA/ku3A=
References: <009401cc06c0$eaa919e0$bffb4da0$@com> <A2408947975D7A4C95A0DD337F638258021C7FC6@LODERI.intra.cea.fr> <018701cc08f6$cb23cd80$616b6880$@com> <A2408947975D7A4C95A0DD337F638258021C7FFD@LODERI.intra.cea.fr> <012c01cc09f1$441cacc0$cc560640$@com>
From: KELLIL Mounir <mounir.kellil@cea.fr>
To: Tina Tsou <tena@huawei.com>
X-OriginalArrivalTime: 04 May 2011 07:56:07.0988 (UTC) FILETIME=[B9DD0740:01CC0A30]
X-TM-AS-Product-Ver: SMEX-10.0.0.4152-6.500.1024-18114.002
X-TM-AS-Result: No--38.509900-8.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
X-Mailman-Approved-At: Wed, 04 May 2011 10:22:19 -0700
Cc: MBONED WG <mboned@ietf.org>, multrans@ietf.org, pim@ietf.org
Subject: Re: [pim] [multrans] Comments on Dual Stack case
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, 04 May 2011 07:56:19 -0000

Bonjour Tina,

Sure I will be happy to review the document

Regards

Mounir KELLIL
CEA LIST
e-mail : mounir.kellil@cea.fr
web : http://www-list.cea.fr
=20
> -----Message d'origine-----
> De=A0: Tina Tsou [mailto:tena@huawei.com]
> Envoy=E9=A0: mercredi 4 mai 2011 02:22
> =C0=A0: KELLIL Mounir
> Cc=A0: 'MBONED WG'; pim@ietf.org; multrans@ietf.org
> Objet=A0: RE: [multrans] Comments on Dual Stack case
>=20
> Bonjour Mounir,
> If you consider a dual-stack network only, that's what we are looking
> for.
>=20
> Would you review
> https://datatracker.ietf.org/doc/draft-jaclee-behave-v4v6-mcast-ps/,
> and
> send out your comments or proposed text to reflect the issues of a =
dual
> stack network, which is not covered by the current version?
>=20
> Merci.
>=20
> Yiu Lee is editing the XML file.
>=20
>=20
> We keep our promises with one another - no matter what!
>=20
> Best Regards,
> Tina TSOU
> http://tinatsou.weebly.com/contact.html
>=20
>=20
> -----Original Message-----
> From: KELLIL Mounir [mailto:mounir.kellil@cea.fr]
> Sent: Tuesday, May 03, 2011 1:12 AM
> To: Tina Tsou
> Cc: MBONED WG; pim@ietf.org; multrans@ietf.org
> Subject: RE: [multrans] Comments on Dual Stack case
>=20
> Bonjour Tina,
>=20
> We consider a dual-stack network only. The source could be IPv4 only =
or
> IPv6
> only, not necessarily both. Regarding SAMRG, they normally intend to
> push
> the work (not ours) further to IETF. But, honestly, I am not aware of
> their
> current status.
>=20
> BTW, I will be happy to follow the discussions on multirans
>=20
> Best regards
>=20
> Mounir
>=20
> Mounir KELLIL
> CEA LIST
> e-mail : mounir.kellil@cea.fr
> web : http://www-list.cea.fr
>=20
> > -----Message d'origine-----
> > De=A0: Tina Tsou [mailto:tena@huawei.com]
> > Envoy=E9=A0: lundi 2 mai 2011 20:29
> > =C0=A0: KELLIL Mounir
> > Cc=A0: 'MBONED WG'; pim@ietf.org; multrans@ietf.org
> > Objet=A0: RE: [multrans] Comments on Dual Stack case
> >
> > Bonjour Mounir,
> > Thank you. I read draft-kellil-sam-mtocp-01, it is useful to
> multrans.
> > Do
> > you consider dual stack network and/or dual stack source?
> > How is the status of IRTF's SAMRG group? Is it time to move some of
> the
> > research result into IETF now?
> >
> >
> > We keep our promises with one another - no matter what!
> >
> > Best Regards,
> > Tina TSOU
> > http://tinatsou.weebly.com/contact.html
> >
> >
> > -----Original Message-----
> > From: KELLIL Mounir [mailto:mounir.kellil@cea.fr]
> > Sent: Monday, May 02, 2011 8:10 AM
> > To: Tina Tsou
> > Cc: MBONED WG; pim@ietf.org; multrans@ietf.org
> > Subject: RE: [multrans] Comments on Dual Stack case
> >
> > Hi Tina,
> >
> > I think the problem you are addressing is interesting. It reminds me
> a
> > work
> > we've done in our team a few months ago (an old draft:
> > http://tools.ietf.org/html/draft-kellil-sam-mtocp-01). We addressed
> the
> > multicasting problem in a heterogeneous IP network (heterogeneity in
> > terms
> > of multicast support and IP protocol version). We proposed an =
overlay
> > paradigm to be applied at the transport layer. Overlay nodes are in
> > charge
> > of forwarding traffic, but also translating IPv4 packets into IPv6
> > packets
> > and vice versa. Maybe this work (and probably others from IRTF's
> SAMRG
> > group) could be quoted as a "state-of-the-art". Just a suggestion...
> >
> >
> > Regards
> >
> > Mounir KELLIL
> >
> > CEA LIST
> > web : http://www-list.cea.fr
> >
> > > -----Message d'origine-----
> > > De=A0: multrans-bounces@ietf.org =
[mailto:multrans-bounces@ietf.org]
> De
> > la
> > > part de Tina Tsou
> > > Envoy=E9=A0: samedi 30 avril 2011 00:58
> > > =C0=A0: multrans@ietf.org
> > > Cc=A0: 'MBONED WG'; pim@ietf.org
> > > Objet=A0: [multrans] Comments on Dual Stack case
> > >
> > > Hi all,
> > > Just bring some comments on the dual stack case for the new =
problem
> > > statement I-D based on
> > > https://datatracker.ietf.org/doc/draft-jaclee-behave-v4v6-mcast-
> ps/.
> > > And I
> > > also suggest the new problem statement I-D being
> > > draft-jaclee-multrans-v4v6-mcast-ps, since it is not ONLY behave
> any
> > > more.
> > >
> > > I cc pim@ietf.org and mboned@ietf.org looking for multicast
> expertise
> > > to
> > > help on input to this new problem statement.
> > >
> > > Comments on Dual Stack case are below, inspired by talk with Stig.
> > > 1. Even in the native dual stack case, you want to save bandwidth,
> > not
> > > put
> > > two copy of bandwidth under one source.
> > >
> > > 2. For P2MP case, the receivers are part of IPv4, part of IPv6,
> this
> > is
> > > problem.
> > >
> > > 3. For video conference, you have 30 people, 15 are v4, 15 are v6,
> > and
> > > any
> > > of them can send their videos (everyone has a webcam and
> microphone).
> > >
> > >
> > > We keep our promises with one another - no matter what!
> > >
> > > Best Regards,
> > > Tina TSOU
> > > http://tinatsou.weebly.com/contact.html
> > >
> > >
> > >
> > > _______________________________________________
> > > multrans mailing list
> > > multrans@ietf.org
> > > https://www.ietf.org/mailman/listinfo/multrans
>=20


From mmcbride@cisco.com  Fri May  6 13:08:28 2011
Return-Path: <mmcbride@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 6B45DE07F8 for <pim@ietfa.amsl.com>; Fri,  6 May 2011 13:08:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zskF6B+vrYG7 for <pim@ietfa.amsl.com>; Fri,  6 May 2011 13:08:27 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfa.amsl.com (Postfix) with ESMTP id C1421E0780 for <pim@ietf.org>; Fri,  6 May 2011 13:08:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mmcbride@cisco.com; l=1034; q=dns/txt; s=iport; t=1304712507; x=1305922107; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=B6U6PTdlp+qZVNwTRRXAu5o0ty6mzgZxMMzNcToQEOs=; b=Ubg3P92qt2WeSukFjFWd1zivBGNK5UjVUHQRw2tYP1NeKyQQS8hllVeO aiX64DYZeRSG0hPqieVBNoLwt8bm29zfSBRwoA1f3N6uOFjsrIPbSpqKE +yZLmCr/TPgtiDoIAfzKMFcIv+AxCxq/uGqca4uxo4isfToq5IL4h6FXv 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Am0JAJlUxE2rRDoI/2dsb2JhbACXc0CNa3d7pWideoYJBIY9jUiKRw
X-IronPort-AV: E=Sophos;i="4.64,327,1301875200"; d="scan'208";a="310182540"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by sj-iport-3.cisco.com with ESMTP; 06 May 2011 20:08:27 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p46K8Rmb023227 for <pim@ietf.org>; Fri, 6 May 2011 20:08:27 GMT
Received: from xmb-sjc-21d.amer.cisco.com ([171.70.151.140]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 6 May 2011 13:08:27 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 6 May 2011 13:08:17 -0700
Message-ID: <DB95C89A3E33E946B4E3F7E00BA8B0931312E9@xmb-sjc-21d.amer.cisco.com>
In-Reply-To: <4DB1F7DA.2020906@venaas.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [pim] I-D Action:draft-ietf-pim-hello-intid-00.txt
Thread-Index: AcwBNyw2umUTY+cNSSefCeIEJEOEtgK8HwFw
References: <20110422213004.21602.99410.idtracker@ietfc.amsl.com> <4DB1F7DA.2020906@venaas.com>
From: "Mike McBride (mmcbride)" <mmcbride@cisco.com>
To: <pim@ietf.org>
X-OriginalArrivalTime: 06 May 2011 20:08:27.0457 (UTC) FILETIME=[5CA76B10:01CC0C29]
Subject: Re: [pim] I-D Action:draft-ietf-pim-hello-intid-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: Fri, 06 May 2011 20:08:28 -0000

Please review draft-ietf-pim-hello-intid-00. We intend to initiate a
wglc for this draft in two weeks time. Please let us know if you feel it
is not ready for wglc.

http://www.ietf.org/id/draft-ietf-pim-hello-intid-00.txt

thanks,
mike

> -----Original Message-----
> From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of
> Stig Venaas
> Sent: Friday, April 22, 2011 2:49 PM
> To: pim@ietf.org
> Subject: Re: [pim] I-D Action:draft-ietf-pim-hello-intid-00.txt
>=20
> As just announced, this draft is now adopted as a wg document.
>=20
> Speaking as an individual, I am hoping this draft can go to wglc
> soon, since PORT relies on this, and it probably makes sense to
> have this through wglc, before doing the same for PORT.
>=20
> Could you guys please have a look at the draft and see whether
> you have any issues or see room for improvement?
>=20
> Stig
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim

From wwwrun@rfc-editor.org  Fri May  6 17:20:22 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 535DCE071D; Fri,  6 May 2011 17:20:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.97
X-Spam-Level: 
X-Spam-Status: No, score=-101.97 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y5r2kVHFSwyg; Fri,  6 May 2011 17:20:21 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id B7882E071A; Fri,  6 May 2011 17:20:21 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id BACABE0778; Fri,  6 May 2011 17:20:21 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110507002021.BACABE0778@rfc-editor.org>
Date: Fri,  6 May 2011 17:20:21 -0700 (PDT)
Cc: pim@ietf.org, rfc-editor@rfc-editor.org
Subject: [pim] RFC 6226 on PIM Group-to-Rendezvous-Point Mapping
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, 07 May 2011 00:20:22 -0000

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

        
        RFC 6226

        Title:      PIM Group-to-Rendezvous-Point Mapping 
        Author:     B. Joshi, A. Kessler,
                    D. McWalter
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2011
        Mailbox:    bharat_joshi@infosys.com, 
                    kessler@cisco.com, 
                    david@mcwalter.eu
        Pages:      11
        Characters: 24092
        Updates:    RFC4601

        I-D Tag:    draft-ietf-pim-group-rp-mapping-10.txt

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

Each Protocol Independent Multicast - Sparse Mode (PIM-SM) router in
a PIM domain that supports Any Source Multicast (ASM) maintains
Group-to-RP mappings that are used to identify a Rendezvous Point
(RP) for a specific multicast group.  PIM-SM has defined an algorithm
to choose a RP from the Group-to-RP mappings learned using various
mechanisms.  This algorithm does not consider the PIM mode and the
mechanism through which a Group-to-RP mapping was learned.

This document defines a standard algorithm to deterministically
choose between several Group-to-RP mappings for a specific group.
This document first explains the requirements to extend the
Group-to-RP mapping algorithm and then proposes the new algorithm.  
[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 Adrian.Farrel@huawei.com  Sun May  8 07:51:22 2011
Return-Path: <Adrian.Farrel@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 62675E070F for <pim@ietfa.amsl.com>; Sun,  8 May 2011 07:51:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.762
X-Spam-Level: 
X-Spam-Status: No, score=-105.762 tagged_above=-999 required=5 tests=[AWL=0.837, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0aybjza7LoXe for <pim@ietfa.amsl.com>; Sun,  8 May 2011 07:51:21 -0700 (PDT)
Received: from usaga03-in.huawei.com (usaga03-in.huawei.com [206.16.17.220]) by ietfa.amsl.com (Postfix) with ESMTP id 6E67FE0794 for <pim@ietf.org>; Sun,  8 May 2011 07:51:21 -0700 (PDT)
Received: from huawei.com (usaga03-in [172.18.4.17]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LKV00615T9KDR@usaga03-in.huawei.com> for pim@ietf.org; Sun, 08 May 2011 09:51:20 -0500 (CDT)
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LKV00CG8T9HBH@usaga03-in.huawei.com> for pim@ietf.org; Sun, 08 May 2011 09:51:20 -0500 (CDT)
Date: Sun, 08 May 2011 15:51:17 +0100
From: Adrian Farrel <Adrian.Farrel@huawei.com>
To: pim@ietf.org
Message-id: <00a001cc0d8f$64182490$2c486db0$@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Outlook 14.0
Content-type: text/plain; charset=us-ascii
Content-language: en-gb
Content-transfer-encoding: 7BIT
Thread-index: AcwNjvvLWy7aG+e0Txi90jlVcL6Pgg==
Subject: [pim] Help with an IGMP Erratum
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Adrian.Farrel@huawei.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: Sun, 08 May 2011 14:51:22 -0000

Hi,

There is an open erratum against RFC 3376.

I would welcome people's opinions on whether anything needs to be done.

The reference is:

http://www.rfc-editor.org/errata_search.php?eid=770

Thanks,
Adrian




From bharat_joshi@infosys.com  Sun May  8 22:12:47 2011
Return-Path: <bharat_joshi@infosys.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 57C95E064E for <pim@ietfa.amsl.com>; Sun,  8 May 2011 22:12:47 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ky2V8YuD3GOU for <pim@ietfa.amsl.com>; Sun,  8 May 2011 22:12:46 -0700 (PDT)
Received: from KECGATE08.infosys.com (kecgate08.infosys.com [122.98.10.33]) by ietfa.amsl.com (Postfix) with ESMTP id 89F0CE0686 for <pim@ietf.org>; Sun,  8 May 2011 22:12:45 -0700 (PDT)
X-TM-IMSS-Message-ID: <7a935831000d76a0@infosys.com>
Received: from blrkechub03.ad.infosys.com ([10.66.236.43]) by infosys.com ([122.98.10.33]) with ESMTP (TREND IMSS SMTP Service 7.1) id 7a935831000d76a0 ; Mon, 9 May 2011 10:47:25 +0530
Received: from BLRKECHUB05.ad.infosys.com (10.66.236.45) by blrkechub03.ad.infosys.com (10.66.236.43) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 9 May 2011 10:42:33 +0530
Received: from BLRKECMBX02.ad.infosys.com ([10.66.236.22]) by BLRKECHUB05.ad.infosys.com ([10.66.236.45]) with mapi; Mon, 9 May 2011 10:42:33 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: "Adrian.Farrel@huawei.com" <Adrian.Farrel@huawei.com>, "pim@ietf.org" <pim@ietf.org>
Date: Mon, 9 May 2011 10:40:49 +0530
Thread-Topic: [pim] Help with an IGMP Erratum
Thread-Index: AcwNjvvLWy7aG+e0Txi90jlVcL6PggAeHpxk
Message-ID: <31D55C4D55BEED48A4459EB64567589A10B356A4F1@BLRKECMBX02.ad.infosys.com>
References: <00a001cc0d8f$64182490$2c486db0$@huawei.com>
In-Reply-To: <00a001cc0d8f$64182490$2c486db0$@huawei.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] Help with an IGMP Erratum
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, 09 May 2011 05:12:47 -0000

Adrian,

=20=20=20=20=20=20If=20I=20have=20understood=20the=20context=20correctly=
=20from=20the=20errata,=20I=20think=20RFC=20is=20correct=20in=20saying=20=
that=20recorded=20source-list=20should=20be=20cleared=20if=20the=20newly=
=20received=20query=20is=20group-specific=20query.=20So=20I=20think=20we=
=20do=20not=20need=20any=20change=20here.

Regards,
Bharat
_______________________________________
From:=20pim-bounces@ietf.org=20[pim-bounces@ietf.org]=20On=20Behalf=20Of=
=20Adrian=20Farrel=20[Adrian.Farrel@huawei.com]
Sent:=20Sunday,=20May=2008,=202011=208:21=20PM
To:=20pim@ietf.org
Subject:=20[pim]=20Help=20with=20an=20IGMP=20Erratum

Hi,

There=20is=20an=20open=20erratum=20against=20RFC=203376.

I=20would=20welcome=20people's=20opinions=20on=20whether=20anything=20nee=
ds=20to=20be=20done.

The=20reference=20is:

http://www.rfc-editor.org/errata_search.php?eid=3D770

Thanks,
Adrian



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

****************=20CAUTION=20-=20Disclaimer=20*****************
This=20e-mail=20contains=20PRIVILEGED=20AND=20CONFIDENTIAL=20INFORMATION=
=20intended=20solely=20
for=20the=20use=20of=20the=20addressee(s).=20If=20you=20are=20not=20the=
=20intended=20recipient,=20please=20
notify=20the=20sender=20by=20e-mail=20and=20delete=20the=20original=20mes=
sage.=20Further,=20you=20are=20not=20
to=20copy,=20disclose,=20or=20distribute=20this=20e-mail=20or=20its=20con=
tents=20to=20any=20other=20person=20and=20
any=20such=20actions=20are=20unlawful.=20This=20e-mail=20may=20contain=20=
viruses.=20Infosys=20has=20taken=20
every=20reasonable=20precaution=20to=20minimize=20this=20risk,=20but=20is=
=20not=20liable=20for=20any=20damage=20
you=20may=20sustain=20as=20a=20result=20of=20any=20virus=20in=20this=20e-=
mail.=20You=20should=20carry=20out=20your=20
own=20virus=20checks=20before=20opening=20the=20e-mail=20or=20attachment.=
=20Infosys=20reserves=20the=20
right=20to=20monitor=20and=20review=20the=20content=20of=20all=20messages=
=20sent=20to=20or=20from=20this=20e-mail=20
address.=20Messages=20sent=20to=20or=20from=20this=20e-mail=20address=20m=
ay=20be=20stored=20on=20the=20
Infosys=20e-mail=20system.
***INFOSYS********=20End=20of=20Disclaimer=20********INFOSYS***

From Sundara.Moorthy@aricent.com  Mon May  9 01:39:36 2011
Return-Path: <Sundara.Moorthy@aricent.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 230AAE06C4 for <pim@ietfa.amsl.com>; Mon,  9 May 2011 01:39:36 -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=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v-LPAPvqCBqe for <pim@ietfa.amsl.com>; Mon,  9 May 2011 01:39:35 -0700 (PDT)
Received: from jaguar.aricent.com (jaguar.aricent.com [121.241.96.11]) by ietfa.amsl.com (Postfix) with ESMTP id 2A5D9E066A for <pim@ietf.org>; Mon,  9 May 2011 01:39:35 -0700 (PDT)
Received: from jaguar.aricent.com (localhost [127.0.0.1]) by postfix.imss71 (Postfix) with ESMTP id 3E41E36BA6 for <pim@ietf.org>; Mon,  9 May 2011 14:05:26 +0530 (IST)
Received: from GUREXHT01.ASIAN.AD.ARICENT.COM (gurexht01.asian.ad.aricent.com [10.203.171.136]) by jaguar.aricent.com (Postfix) with ESMTP id 2774A36BA1 for <pim@ietf.org>; Mon,  9 May 2011 14:05:26 +0530 (IST)
Received: from GUREXMB02.ASIAN.AD.ARICENT.COM ([10.203.171.130]) by GUREXHT01.ASIAN.AD.ARICENT.COM ([10.203.171.137]) with mapi; Mon, 9 May 2011 14:09:26 +0530
From: Sundara Moorthy M <Sundara.Moorthy@aricent.com>
To: "pim@ietf.org" <pim@ietf.org>
Date: Mon, 9 May 2011 14:09:24 +0530
Thread-Topic: Reg -  Scoped address architecture support for PIM -- I am in need of some clarification about the multicast routing when scope-zone support is given
Thread-Index: AcwNsiVljs1oiFdlQZ2GV3TmzqQlxAAaXdUg
Message-ID: <50F4072463B8464890B6051A13E6F7BC05486A1489@GUREXMB02.ASIAN.AD.ARICENT.COM>
References: <mailman.0.1304881202.28392.pim@ietf.org>
In-Reply-To: <mailman.0.1304881202.28392.pim@ietf.org>
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: [pim] Reg - Scoped address architecture support for PIM -- I am in need of some clarification about the multicast routing when scope-zone support is given
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, 09 May 2011 08:39:36 -0000

Hi,

I have some doubts in implementing scoped address architecture support for =
PIM.

In Scoped Address Architecture support for PIM,

How do we route the multicast packets based on scope-zone information?

How do we check that the multicast and unicast PIM control packets are not =
crossing the zone boundary.

Is there any RFC standards for resolving the routing issues in PIM for scop=
e-zone support??

"DISCLAIMER: This message is proprietary to Aricent and is intended solely =
for the use of the individual to whom it is addressed. It may contain privi=
leged or confidential information and should not be circulated or used for =
any purpose other than for what it is intended. If you have received this m=
essage in error, please notify the originator immediately. If you are not t=
he intended recipient, you are notified that you are strictly prohibited fr=
om using, copying, altering, or disclosing the contents of this message. Ar=
icent accepts no responsibility for loss or damage arising from the use of =
the information transmitted by this email including damage from virus."

From brian@innovationslab.net  Mon May  9 06:14:36 2011
Return-Path: <brian@innovationslab.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 A88D1E06C8 for <pim@ietfa.amsl.com>; Mon,  9 May 2011 06:14:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.407
X-Spam-Level: 
X-Spam-Status: No, score=-102.407 tagged_above=-999 required=5 tests=[AWL=0.192, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B4OZF5lAKM9v for <pim@ietfa.amsl.com>; Mon,  9 May 2011 06:14:35 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id E9ABCE0674 for <pim@ietf.org>; Mon,  9 May 2011 06:14:35 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 45A1D8812B for <pim@ietf.org>; Mon,  9 May 2011 06:09:18 -0700 (PDT)
Received: from clemson.jhuapl.edu (unknown [128.244.243.28]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 8839A13682EB for <pim@ietf.org>; Mon,  9 May 2011 06:14:35 -0700 (PDT)
Message-ID: <4DC7E8BB.8000708@innovationslab.net>
Date: Mon, 09 May 2011 09:14:35 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: pim@ietf.org
References: <mailman.0.1304881202.28392.pim@ietf.org> <50F4072463B8464890B6051A13E6F7BC05486A1489@GUREXMB02.ASIAN.AD.ARICENT.COM>
In-Reply-To: <50F4072463B8464890B6051A13E6F7BC05486A1489@GUREXMB02.ASIAN.AD.ARICENT.COM>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [pim] Reg - Scoped address architecture support for PIM -- I am in need of some clarification about the multicast routing when scope-zone support is given
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, 09 May 2011 13:14:36 -0000

In IPv6, this is documented in RFC 4007.

Regards,
Brian

On 5/9/11 4:39 AM, Sundara Moorthy M wrote:
> 
> Hi,
> 
> I have some doubts in implementing scoped address architecture
> support for PIM.
> 
> In Scoped Address Architecture support for PIM,
> 
> How do we route the multicast packets based on scope-zone
> information?
> 
> How do we check that the multicast and unicast PIM control packets
> are not crossing the zone boundary.
> 
> Is there any RFC standards for resolving the routing issues in PIM
> for scope-zone support??

From eckert@cisco.com  Mon May  9 08:39:10 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 1EA15E07E4 for <pim@ietfa.amsl.com>; Mon,  9 May 2011 08:39:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.495
X-Spam-Level: 
X-Spam-Status: No, score=-8.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RCVD_IN_DNSWL_HI=-8, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OGNUaRKPy7xC for <pim@ietfa.amsl.com>; Mon,  9 May 2011 08:39:09 -0700 (PDT)
Received: from sj-iport-6.cisco.com (unknown [171.71.176.117]) by ietfa.amsl.com (Postfix) with ESMTP id 3DD1FE07CC for <pim@ietf.org>; Mon,  9 May 2011 08:39:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckert@cisco.com; l=3067; q=dns/txt; s=iport; t=1304955549; x=1306165149; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=MRN7yHvzYcQblogYMqh6LP5QWeqUCgCOqZG3YVgMc/M=; b=aIwd+4ezHtzbT3nasjwwqEI5EBRzY+SVPwgIOSyGxbG5ueo1zXEfM694 yYB+ZaDSDQYY9SSEnHf9cMhazQxieO8+1wjZSkM1w2quYipdRlO8Xb44T LASpSXZRZlsdht8y6V2cpVCsnwrHy7jPeMK1xiqXK1IG35en490sA4dxS E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAD0JyE2rRDoJ/2dsb2JhbAClf3epH51thgwEhkCJJY59
X-IronPort-AV: E=Sophos;i="4.64,341,1301875200"; d="scan'208";a="694236393"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-6.cisco.com with ESMTP; 09 May 2011 15:39:08 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p49Fd8v3025179; Mon, 9 May 2011 15:39:08 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 p49Fd8Af015611;  Mon, 9 May 2011 08:39:08 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id p49Fd8PA015610; Mon, 9 May 2011 08:39:08 -0700
Date: Mon, 9 May 2011 08:39:08 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Brian Haberman <brian@innovationslab.net>
Message-ID: <20110509153908.GU18582@cisco.com>
References: <mailman.0.1304881202.28392.pim@ietf.org> <50F4072463B8464890B6051A13E6F7BC05486A1489@GUREXMB02.ASIAN.AD.ARICENT.COM> <4DC7E8BB.8000708@innovationslab.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4DC7E8BB.8000708@innovationslab.net>
User-Agent: Mutt/1.4.2.2i
Cc: pim@ietf.org
Subject: Re: [pim] Reg - Scoped address architecture support for PIM -- I am in need of some clarification about the multicast routing when scope-zone support is given
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, 09 May 2011 15:39:10 -0000

rfc4007 IMHO defines an architecture that is way too complex for 
IP multicast. Unfortunately we could never get the IETF to fix this even
though we tried.  Nidhi Bhaskar gave a good explanation talk of the problem
back in the days at the IETF and i had a long talk with Steve Deering about
it, but he did not want to go back and revisit the address architecture with
his co-authors. I think rffc4007 was originally written and approved without
ever checking with someone who would have to actually implement it on a
HW assisted router.

This history is of course particularily annoying because on the unicast side,
even the way more simple site local scope addresses where removed after
implementers and deployment folks complained about it due to complexity.
But why fix multicast or make it simple... *sigh* *mumble* ;-).

Reminder for those without the background:

  If you wanted to implement rfc4007 scoped zones where the scope boundaries
  arbitrarily cut through a router leaving two or more interfaces on either
  side, you effectively need to implement a separate virtual routing table
  for each of the zones. It is like what you do for a VRF in an MPLS-VPN/PE
  LSR, just that you now really needed create invisibly something like
  a different VRF for each set of interfaces that is in the same zones for all
  scopes 3 and up. And then of course you would also have some extranet routes
  if some of these sets only share larger scopes but not smaller scopes. Or
  you implemented hierarchical VRF routing. And then try to think how to
  implement that on top of a router that already does support other explicit
  virtual routing contexts (MPLS-VPN/VRFs or others too.

In any case, at the time this was discussed, the slient implication to
implementers was that they just did not support scoped multicast zones > 2 
to cut through a router itself. Instead, like in IPv4 they where only
implemented cutting through a link.  That of course makes it quite 
"interesting" to answer questions about RFC4007 support in RFPs.

If anyone has actually implemented multi-zone IPv6 IP multicast routing
without tying it to VRF or other PE-like infra, i would be very interested
to hear about it.

Cheers
    Toerless

On Mon, May 09, 2011 at 09:14:35AM -0400, Brian Haberman wrote:
> In IPv6, this is documented in RFC 4007.
> 
> Regards,
> Brian
> 
> On 5/9/11 4:39 AM, Sundara Moorthy M wrote:
> > 
> > Hi,
> > 
> > I have some doubts in implementing scoped address architecture
> > support for PIM.
> > 
> > In Scoped Address Architecture support for PIM,
> > 
> > How do we route the multicast packets based on scope-zone
> > information?
> > 
> > How do we check that the multicast and unicast PIM control packets
> > are not crossing the zone boundary.
> > 
> > Is there any RFC standards for resolving the routing issues in PIM
> > for scope-zone support??
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim

From Sundara.Moorthy@aricent.com  Mon May  9 23:29:23 2011
Return-Path: <Sundara.Moorthy@aricent.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 E81B1E06F1 for <pim@ietfa.amsl.com>; Mon,  9 May 2011 23:29:23 -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=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y9URj8BVyAEl for <pim@ietfa.amsl.com>; Mon,  9 May 2011 23:29:23 -0700 (PDT)
Received: from jaguar.aricent.com (jaguar.aricent.com [121.241.96.11]) by ietfa.amsl.com (Postfix) with ESMTP id 90877E0669 for <pim@ietf.org>; Mon,  9 May 2011 23:29:22 -0700 (PDT)
Received: from jaguar.aricent.com (localhost [127.0.0.1]) by postfix.imss71 (Postfix) with ESMTP id F0BEB36B8F; Tue, 10 May 2011 11:28:35 +0530 (IST)
Received: from GUREXHT02.ASIAN.AD.ARICENT.COM (gurexht02.asian.ad.aricent.com [10.203.171.138]) by jaguar.aricent.com (Postfix) with ESMTP id DB05936B8E; Tue, 10 May 2011 11:28:35 +0530 (IST)
Received: from GUREXMB02.ASIAN.AD.ARICENT.COM ([10.203.171.130]) by GUREXHT02.ASIAN.AD.ARICENT.COM ([10.203.171.138]) with mapi; Tue, 10 May 2011 11:32:35 +0530
From: Sundara Moorthy M <Sundara.Moorthy@aricent.com>
To: Toerless Eckert <eckert@cisco.com>, Brian Haberman <brian@innovationslab.net>
Date: Tue, 10 May 2011 11:32:33 +0530
Thread-Topic: [pim] Reg - Scoped address architecture support for PIM -- I am	in need of some clarification about the multicast routing	when scope-zone support is given
Thread-Index: AcwOe1Q16UmQzX65R1CWc00TLLEJLgAWiEYg
Message-ID: <50F4072463B8464890B6051A13E6F7BC0550753314@GUREXMB02.ASIAN.AD.ARICENT.COM>
References: <mailman.0.1304881202.28392.pim@ietf.org> <50F4072463B8464890B6051A13E6F7BC05486A1489@GUREXMB02.ASIAN.AD.ARICENT.COM> <4DC7E8BB.8000708@innovationslab.net> <20110509153908.GU18582@cisco.com>
In-Reply-To: <20110509153908.GU18582@cisco.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
Cc: Muthulakshmi Varadharajan <Muthulakshmi.V@aricent.com>, Muthulakshmi Radhakrishnan <Muthulakshmi.R@aricent.com>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] Reg - Scoped address architecture support for PIM -- I am	in need of some clarification about the multicast routing	when scope-zone support is given
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, 10 May 2011 06:29:24 -0000

Hi,

Thanks for your response.

>>In any case, at the time this was discussed, the slient implication to im=
plementers was that they just did not support >>scoped multicast zones > 2 =
to cut through a router itself. Instead, like in IPv4 they where only imple=
mented cutting
>>through a link.  That of course makes it quite "interesting" to answer qu=
estions about RFC4007 support in RFPs.

you meant to say multicast can work with only two scope zones (link local a=
nd interface local), then
how to reach the global RP address and BSR?

We are not planning to have VRF kind of routing table for IPv6 scopes.

We are facing problems while finding unicast route lookup for RP, BSR, sour=
ce
and feel that it may cross the zone boundary.
Shall we have administrative restriction that all the unicast routes to
reach a particular destination should lie in the same scope zone ?


Thanks and Regards,
 Sundara Moorthy M

-----Original Message-----
From: Toerless Eckert [mailto:eckert@cisco.com]
Sent: Monday, May 09, 2011 9:09 PM
To: Brian Haberman
Cc: pim@ietf.org
Subject: Re: [pim] Reg - Scoped address architecture support for PIM -- I a=
m in need of some clarification about the multicast routing when scope-zone=
 support is given

rfc4007 IMHO defines an architecture that is way too complex for IP multica=
st. Unfortunately we could never get the IETF to fix this even though we tr=
ied.  Nidhi Bhaskar gave a good explanation talk of the problem back in the=
 days at the IETF and i had a long talk with Steve Deering about it, but he=
 did not want to go back and revisit the address architecture with his co-a=
uthors. I think rffc4007 was originally written and approved without ever c=
hecking with someone who would have to actually implement it on a HW assist=
ed router.

This history is of course particularily annoying because on the unicast sid=
e, even the way more simple site local scope addresses where removed after =
implementers and deployment folks complained about it due to complexity.
But why fix multicast or make it simple... *sigh* *mumble* ;-).

Reminder for those without the background:

  If you wanted to implement rfc4007 scoped zones where the scope boundarie=
s
  arbitrarily cut through a router leaving two or more interfaces on either
  side, you effectively need to implement a separate virtual routing table
  for each of the zones. It is like what you do for a VRF in an MPLS-VPN/PE
  LSR, just that you now really needed create invisibly something like
  a different VRF for each set of interfaces that is in the same zones for =
all
  scopes 3 and up. And then of course you would also have some extranet rou=
tes
  if some of these sets only share larger scopes but not smaller scopes. Or
  you implemented hierarchical VRF routing. And then try to think how to
  implement that on top of a router that already does support other explici=
t
  virtual routing contexts (MPLS-VPN/VRFs or others too.

In any case, at the time this was discussed, the slient implication to impl=
ementers was that they just did not support scoped multicast zones > 2 to c=
ut through a router itself. Instead, like in IPv4 they where only implement=
ed cutting through a link.  That of course makes it quite "interesting" to =
answer questions about RFC4007 support in RFPs.

If anyone has actually implemented multi-zone IPv6 IP multicast routing wit=
hout tying it to VRF or other PE-like infra, i would be very interested to =
hear about it.

Cheers
    Toerless

On Mon, May 09, 2011 at 09:14:35AM -0400, Brian Haberman wrote:
> In IPv6, this is documented in RFC 4007.
>
> Regards,
> Brian
>
> On 5/9/11 4:39 AM, Sundara Moorthy M wrote:
> >
> > Hi,
> >
> > I have some doubts in implementing scoped address architecture
> > support for PIM.
> >
> > In Scoped Address Architecture support for PIM,
> >
> > How do we route the multicast packets based on scope-zone
> > information?
> >
> > How do we check that the multicast and unicast PIM control packets
> > are not crossing the zone boundary.
> >
> > Is there any RFC standards for resolving the routing issues in PIM
> > for scope-zone support??
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim


"DISCLAIMER: This message is proprietary to Aricent and is intended solely =
for the use of the individual to whom it is addressed. It may contain privi=
leged or confidential information and should not be circulated or used for =
any purpose other than for what it is intended. If you have received this m=
essage in error, please notify the originator immediately. If you are not t=
he intended recipient, you are notified that you are strictly prohibited fr=
om using, copying, altering, or disclosing the contents of this message. Ar=
icent accepts no responsibility for loss or damage arising from the use of =
the information transmitted by this email including damage from virus."

From verozheng@huawei.com  Tue May 17 19:01:41 2011
Return-Path: <verozheng@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 94F2AE06A4 for <pim@ietfa.amsl.com>; Tue, 17 May 2011 19:01:41 -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=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VdImDko-SZFB for <pim@ietfa.amsl.com>; Tue, 17 May 2011 19:01:41 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id D7307E0659 for <pim@ietf.org>; Tue, 17 May 2011 19:01:40 -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 <0LLD00D4BCANX1@szxga05-in.huawei.com> for pim@ietf.org; Wed, 18 May 2011 10:01:36 +0800 (CST)
Received: from Z50128Z ([10.110.98.58]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LLD004T3CAI1M@szxga05-in.huawei.com> for pim@ietf.org; Wed, 18 May 2011 10:01:35 +0800 (CST)
Date: Wed, 18 May 2011 10:01:30 +0800
From: Vero Zheng <verozheng@huawei.com>
In-reply-to: <47951CBFA6409B4C8916514FCB05BFBE0C7F0E5F@xmb-sjc-219.amer.cisco.com>
To: "'Mike McBride (mmcbride)'" <mmcbride@cisco.com>, pim@ietf.org
Message-id: <003501cc14ff$81d52fb0$857f8f10$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: zh-cn
Content-transfer-encoding: 7BIT
Thread-index: AcwBFNjMb2FdADp5RgiNSRDv3F4XWwAAASjABPqnCFA=
References: <47951CBFA6409B4C8916514FCB05BFBE0C7F0E5F@xmb-sjc-219.amer.cisco.com>
Subject: Re: [pim] additions to the charter
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, 18 May 2011 02:01:41 -0000

Yay Yay!

Vero
> -----Original Message-----
> From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of Mike
> McBride (mmcbride)
> Sent: Saturday, April 23, 2011 1:57 AM
> To: pim@ietf.org
> Subject: [pim] additions to the charter
> 
> We have two proposed additions to our charter:
> 
> "There is a significant number of errata that need to be addressed in
> order to advance RFC4601 to Draft Standard. The PIM WG will correct the
> errata, as necessary, and update RFC4601."
> 
> and
> 
> "The working group primarily works on extensions to PIM, but may take on
> work related to IGMP/MLD."
> 
> The igmp/mld addition is based upon a request from mboned wg. We either
> reopen MAGMA or we take igmp/mld on in pim. During the Prague pimwg
> meeting there was strong support to take on igmp/mld.
> 
> Please provide a yay or nay or propose alternative text.
> 
> Thanks,
> mike
> 
> 
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim



From mmcbride@cisco.com  Fri May 20 10:59:24 2011
Return-Path: <mmcbride@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 E5CD5E073D for <pim@ietfa.amsl.com>; Fri, 20 May 2011 10:59:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mUf+LXc9g0mx for <pim@ietfa.amsl.com>; Fri, 20 May 2011 10:59:24 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by ietfa.amsl.com (Postfix) with ESMTP id 3E70EE0727 for <pim@ietf.org>; Fri, 20 May 2011 10:59:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mmcbride@cisco.com; l=239; q=dns/txt; s=iport; t=1305914364; x=1307123964; h=mime-version:content-transfer-encoding:subject:date: message-id:from:to; bh=5neo8DbMz5hWMQX+6075LN0/cN+aRvLfqZJhGzEXnik=; b=YfG2FJOJzphZu7vT84jQF9Z+N23e816PhikiNWLFvV1IuBCgLGJg9AFc UuExZpTFi6q8SVcowpjeyTvslf3RkMzyju0EFdFeL+Y88gh3LdZwA3VZJ 3nqSs55DBawgQL1thG5J5bq+7I8BSi1GmtT9WDjc1Z0xulcVsjKppO7oM U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlIGAL+r1k2rRDoG/2dsb2JhbACYJI17eKMYgR2eAYYZBIZQjXmKXQ
X-IronPort-AV: E=Sophos;i="4.65,243,1304294400"; d="scan'208";a="451628942"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-1.cisco.com with ESMTP; 20 May 2011 17:59:23 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p4KHxNU9020421 for <pim@ietf.org>; Fri, 20 May 2011 17:59:23 GMT
Received: from xmb-sjc-21d.amer.cisco.com ([171.70.151.140]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 20 May 2011 10:59:23 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-CR-Puzzleid: {6BB7E958-8495-4B24-9CB9-9A25314760E5}
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-CR-Hashedpuzzle: At5Q A6W1 BW3X B1r6 CrOu EH/P E1TG FBe+ FFgQ FRlq F6K+ G1dJ H+ID Iwkl I+G7 JIfb; 1; cABpAG0AQABpAGUAdABmAC4AbwByAGcA; Sosha1_v1; 7; {6BB7E958-8495-4B24-9CB9-9A25314760E5}; bQBtAGMAYgByAGkAZABlAEAAYwBpAHMAYwBvAC4AYwBvAG0A; Fri, 20 May 2011 17:59:11 GMT; ZAByAGEAZgB0AC0AaQBlAHQAZgAtAHAAaQBtAC0AaABlAGwAbABvAC0AaQBuAHQAaQBkAC0AMAAwACAAdwBnAGwAYwA=
Content-class: urn:content-classes:message
Date: Fri, 20 May 2011 10:59:11 -0700
Message-ID: <DB95C89A3E33E946B4E3F7E00BA8B09331FE0C@xmb-sjc-21d.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-pim-hello-intid-00 wglc
Thread-Index: AcwXF59mNb6pl+6tTaCJV1Ep8x77qQ==
From: "Mike McBride (mmcbride)" <mmcbride@cisco.com>
To: <pim@ietf.org>
X-OriginalArrivalTime: 20 May 2011 17:59:23.0697 (UTC) FILETIME=[A6CBEA10:01CC1717]
Subject: [pim] draft-ietf-pim-hello-intid-00 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: Fri, 20 May 2011 17:59:25 -0000

Today begins a two week wglc for draft-ietf-pim-hello-intid-00. Please
review the draft. Then indicate to us if its worthy, or not, of being
sent to the iesg.

http://www.ietf.org/id/draft-ietf-pim-hello-intid-00.txt

thanks,
mike

From bharat_joshi@infosys.com  Mon May 23 08:55:17 2011
Return-Path: <bharat_joshi@infosys.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 A024EE0798 for <pim@ietfa.amsl.com>; Mon, 23 May 2011 08:55:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.299
X-Spam-Level: 
X-Spam-Status: No, score=-5.299 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I2qk9O9GB+MF for <pim@ietfa.amsl.com>; Mon, 23 May 2011 08:55:16 -0700 (PDT)
Received: from KECGATE08.infosys.com (kecgate08.infosys.com [122.98.10.33]) by ietfa.amsl.com (Postfix) with ESMTP id 07812E067F for <pim@ietf.org>; Mon, 23 May 2011 08:55:15 -0700 (PDT)
X-TM-IMSS-Message-ID: <01cde93400005d40@infosys.com>
Received: from blrkechub03.ad.infosys.com ([10.66.236.43]) by infosys.com ([122.98.10.33]) with ESMTP (TREND IMSS SMTP Service 7.1) id 01cde93400005d40 ; Mon, 23 May 2011 21:30:14 +0530
Received: from BLRKECMBX02.ad.infosys.com ([10.66.236.22]) by blrkechub03.ad.infosys.com ([10.66.236.43]) with mapi; Mon, 23 May 2011 21:25:12 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: "Mike McBride (mmcbride)" <mmcbride@cisco.com>, "pim@ietf.org" <pim@ietf.org>
Date: Mon, 23 May 2011 21:24:09 +0530
Thread-Topic: draft-ietf-pim-hello-intid-00 wglc
Thread-Index: AcwXF59mNb6pl+6tTaCJV1Ep8x77qQCSggKw
Message-ID: <31D55C4D55BEED48A4459EB64567589A115E3C9ED3@BLRKECMBX02.ad.infosys.com>
References: <DB95C89A3E33E946B4E3F7E00BA8B09331FE0C@xmb-sjc-21d.amer.cisco.com>
In-Reply-To: <DB95C89A3E33E946B4E3F7E00BA8B09331FE0C@xmb-sjc-21d.amer.cisco.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] draft-ietf-pim-hello-intid-00 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, 23 May 2011 15:55:17 -0000

Hi=20Stig,

=20=20=20=20=20I=20have=20few=20suggestions=20below,=20almost=20all=20min=
ors=20on=20this=20draft.

Mike,
=20=20=20=20I=20think=20this=20is=20ready=20for=20the=20next=20level.

Thanks,
Bharat

=95=20Should=20we=20use=20"interface=20id"=20or=20"interface=20identifier=
"=20in=20Abstract?

=95=20In=20following=20sentence=20in=20Introduction:

The=20identifiers=20can=20optionally=20be=20generated=20so=20that=20they=
=20are=20unique=20within,=20e.g.,=20an=20administrative=20=20domain.

will=20'such=20that'=20instead=20of=20'so=20that'=20be=20better?

=95=20Should=20we=20move=20the=20second=20part=20of=20introduction=20to=
=20another=20section=20called=20'Use=20cases'?

=95=20In=20following=20statement:

=20=20=20It=20is=20assumed=20that=20different=20protocols=20may=20have=20=
different=20minimum=20requirements=20for=20stability=20and=20uniqueness,=
=20but=20that=20they=20have=20no=20=20maximum=20requirement.=20

Can=20we=20use=20'Interface=20identifier'=20as=20follows:

=20=20=20It=20is=20assumed=20that=20different=20protocols=20may=20have=20=
different=20minimum=20requirements=20for=20stability=20and=20uniqueness=
=20of=20the=20interface=20identifier,=20but=20that=20they=20have=20no=20=
=20maximum=20requirement.=20

=95=20Following=20statement:

If=20an=20interface=20goes=20down=20and=20up,=20the=20router=20SHOULD=20u=
se=20the=20same=20Identifier.

to

If=20an=20interface=20goes=20down=20and=20comes=20up,=20the=20router=20SH=
OULD=20use=20the=20same=20Identifier.

=95=20In=20Message=20format,=20can=20we=20move=20explanation=20of=20'Rout=
er=20Identifier'=20before=20'Local=20Interface=20Identifier'=20to=20keep=
=20it=20consistent=20with=20format?

=95=20Should=20not=20PIM-Port=20be=20normative=20reference=20for=20this=
=20work?

________________________________________
From:=20pim-bounces@ietf.org=20[pim-bounces@ietf.org]=20On=20Behalf=20Of=
=20Mike=20McBride=20(mmcbride)=20[mmcbride@cisco.com]
Sent:=20Friday,=20May=2020,=202011=2011:29=20PM
To:=20pim@ietf.org
Subject:=20[pim]=20draft-ietf-pim-hello-intid-00=20wglc

Today=20begins=20a=20two=20week=20wglc=20for=20draft-ietf-pim-hello-intid=
-00.=20Please
review=20the=20draft.=20Then=20indicate=20to=20us=20if=20its=20worthy,=20=
or=20not,=20of=20being
sent=20to=20the=20iesg.

http://www.ietf.org/id/draft-ietf-pim-hello-intid-00.txt

thanks,
mike
_______________________________________________
pim=20mailing=20list
pim@ietf.org
https://www.ietf.org/mailman/listinfo/pim

****************=20CAUTION=20-=20Disclaimer=20*****************
This=20e-mail=20contains=20PRIVILEGED=20AND=20CONFIDENTIAL=20INFORMATION=
=20intended=20solely=20
for=20the=20use=20of=20the=20addressee(s).=20If=20you=20are=20not=20the=
=20intended=20recipient,=20please=20
notify=20the=20sender=20by=20e-mail=20and=20delete=20the=20original=20mes=
sage.=20Further,=20you=20are=20not=20
to=20copy,=20disclose,=20or=20distribute=20this=20e-mail=20or=20its=20con=
tents=20to=20any=20other=20person=20and=20
any=20such=20actions=20are=20unlawful.=20This=20e-mail=20may=20contain=20=
viruses.=20Infosys=20has=20taken=20
every=20reasonable=20precaution=20to=20minimize=20this=20risk,=20but=20is=
=20not=20liable=20for=20any=20damage=20
you=20may=20sustain=20as=20a=20result=20of=20any=20virus=20in=20this=20e-=
mail.=20You=20should=20carry=20out=20your=20
own=20virus=20checks=20before=20opening=20the=20e-mail=20or=20attachment.=
=20Infosys=20reserves=20the=20
right=20to=20monitor=20and=20review=20the=20content=20of=20all=20messages=
=20sent=20to=20or=20from=20this=20e-mail=20
address.=20Messages=20sent=20to=20or=20from=20this=20e-mail=20address=20m=
ay=20be=20stored=20on=20the=20
Infosys=20e-mail=20system.
***INFOSYS********=20End=20of=20Disclaimer=20********INFOSYS***

From stig@venaas.com  Mon May 23 10:36:33 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 44DB8E077F for <pim@ietfa.amsl.com>; Mon, 23 May 2011 10:36:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MKAd+iuVs90w for <pim@ietfa.amsl.com>; Mon, 23 May 2011 10:36:32 -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 7ECF9E0670 for <pim@ietf.org>; Mon, 23 May 2011 10:36:32 -0700 (PDT)
Received: from [IPv6:2001:420:4:ea0c:68d2:8a73:f085:62d3] (unknown [IPv6:2001:420:4:ea0c:68d2:8a73:f085:62d3]) by ufisa.uninett.no (Postfix) with ESMTPSA id 4D98A801A; Mon, 23 May 2011 19:36:30 +0200 (CEST)
Message-ID: <4DDA9B1A.50400@venaas.com>
Date: Mon, 23 May 2011 10:36:26 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Bharat Joshi <bharat_joshi@infosys.com>
References: <DB95C89A3E33E946B4E3F7E00BA8B09331FE0C@xmb-sjc-21d.amer.cisco.com> <31D55C4D55BEED48A4459EB64567589A115E3C9ED3@BLRKECMBX02.ad.infosys.com>
In-Reply-To: <31D55C4D55BEED48A4459EB64567589A115E3C9ED3@BLRKECMBX02.ad.infosys.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "Mike McBride \(mmcbride\)" <mmcbride@cisco.com>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] draft-ietf-pim-hello-intid-00 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, 23 May 2011 17:36:33 -0000

On 5/23/2011 8:54 AM, Bharat Joshi wrote:
[...]
> • Should not PIM-Port be normative reference for this work?

Thanks, I think I agree with your comments. Apart from this one. This
is independent of PORT in the sense that it can be used when an ID is
required for other protocols. Supporting PORT is not a requirement to
implement this. Hence it does not need to reference PORT. This is also
why it was split out.

However, the PORT draft will need to have a normative reference to
this one, as PORT relies on this.

Stig

> ________________________________________
> From: pim-bounces@ietf.org [pim-bounces@ietf.org] On Behalf Of Mike McBride (mmcbride) [mmcbride@cisco.com]
> Sent: Friday, May 20, 2011 11:29 PM
> To: pim@ietf.org
> Subject: [pim] draft-ietf-pim-hello-intid-00 wglc
>
> Today begins a two week wglc for draft-ietf-pim-hello-intid-00. Please
> review the draft. Then indicate to us if its worthy, or not, of being
> sent to the iesg.
>
> http://www.ietf.org/id/draft-ietf-pim-hello-intid-00.txt
>
> thanks,
> mike
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim
>
> **************** CAUTION - Disclaimer *****************
> This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
> for the use of the addressee(s). If you are not the intended recipient, please
> notify the sender by e-mail and delete the original message. Further, you are not
> to copy, disclose, or distribute this e-mail or its contents to any other person and
> any such actions are unlawful. This e-mail may contain viruses. Infosys has taken
> every reasonable precaution to minimize this risk, but is not liable for any damage
> you may sustain as a result of any virus in this e-mail. You should carry out your
> own virus checks before opening the e-mail or attachment. Infosys reserves the
> right to monitor and review the content of all messages sent to or from this e-mail
> address. Messages sent to or from this e-mail address may be stored on the
> Infosys e-mail system.
> ***INFOSYS******** End of Disclaimer ********INFOSYS***
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim


From bharat_joshi@infosys.com  Mon May 23 20:23:00 2011
Return-Path: <bharat_joshi@infosys.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 E8235E06D1 for <pim@ietfa.amsl.com>; Mon, 23 May 2011 20:23:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.949
X-Spam-Level: 
X-Spam-Status: No, score=-5.949 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DTVh1YWWKiFw for <pim@ietfa.amsl.com>; Mon, 23 May 2011 20:23:00 -0700 (PDT)
Received: from kecgate06.infosys.com (kecgate06.infosys.com [122.98.14.33]) by ietfa.amsl.com (Postfix) with ESMTP id 9DE48E0688 for <pim@ietf.org>; Mon, 23 May 2011 20:22:59 -0700 (PDT)
X-TM-IMSS-Message-ID: <0450d29800007a1d@infosys.com>
Received: from blrkechub02.ad.infosys.com ([10.66.236.42]) by infosys.com ([122.98.14.33]) with ESMTP (TREND IMSS SMTP Service 7.1) id 0450d29800007a1d ; Tue, 24 May 2011 08:54:16 +0530
Received: from BLRKECMBX02.ad.infosys.com ([10.66.236.22]) by blrkechub02.ad.infosys.com ([10.66.236.42]) with mapi; Tue, 24 May 2011 08:52:57 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: Stig Venaas <stig@venaas.com>
Date: Tue, 24 May 2011 08:49:51 +0530
Thread-Topic: [pim] draft-ietf-pim-hello-intid-00 wglc
Thread-Index: AcwZb/rldEcQAxcWTu+qqNeEUvjyMAAUXacV
Message-ID: <31D55C4D55BEED48A4459EB64567589A115E3C9ED5@BLRKECMBX02.ad.infosys.com>
References: <DB95C89A3E33E946B4E3F7E00BA8B09331FE0C@xmb-sjc-21d.amer.cisco.com> <31D55C4D55BEED48A4459EB64567589A115E3C9ED3@BLRKECMBX02.ad.infosys.com>, <4DDA9B1A.50400@venaas.com>
In-Reply-To: <4DDA9B1A.50400@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="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Mike McBride \(mmcbride\)" <mmcbride@cisco.com>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] draft-ietf-pim-hello-intid-00 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, 24 May 2011 03:23:01 -0000

Hi Stig,

       I was thinking that this draft is using only one use case and that i=
s of PORT and if this draft becomes an RFC before PORT and then PORT makes =
some changes and do not use interface identifier at all (its a hypothetical=
 situation which won't happen here though) then it will not be good. That i=
s why I raised this concern.

       As we are sure in this case that the above situation won't arise, I =
think it is fine to keep it as informative reference as well.

Regards,
Bharat
________________________________________
From: Stig Venaas [stig@venaas.com]
Sent: Monday, May 23, 2011 11:06 PM
To: Bharat Joshi
Cc: Mike McBride (mmcbride); pim@ietf.org
Subject: Re: [pim] draft-ietf-pim-hello-intid-00 wglc

On 5/23/2011 8:54 AM, Bharat Joshi wrote:
[...]
> =95 Should not PIM-Port be normative reference for this work?

Thanks, I think I agree with your comments. Apart from this one. This
is independent of PORT in the sense that it can be used when an ID is
required for other protocols. Supporting PORT is not a requirement to
implement this. Hence it does not need to reference PORT. This is also
why it was split out.

However, the PORT draft will need to have a normative reference to
this one, as PORT relies on this.

Stig

> ________________________________________
> From: pim-bounces@ietf.org [pim-bounces@ietf.org] On Behalf Of Mike McBri=
de (mmcbride) [mmcbride@cisco.com]
> Sent: Friday, May 20, 2011 11:29 PM
> To: pim@ietf.org
> Subject: [pim] draft-ietf-pim-hello-intid-00 wglc
>
> Today begins a two week wglc for draft-ietf-pim-hello-intid-00. Please
> review the draft. Then indicate to us if its worthy, or not, of being
> sent to the iesg.
>
> http://www.ietf.org/id/draft-ietf-pim-hello-intid-00.txt
>
> thanks,
> mike
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim
>
> **************** CAUTION - Disclaimer *****************
> This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended sol=
ely
> for the use of the addressee(s). If you are not the intended recipient, p=
lease
> notify the sender by e-mail and delete the original message. Further, you=
 are not
> to copy, disclose, or distribute this e-mail or its contents to any other=
 person and
> any such actions are unlawful. This e-mail may contain viruses. Infosys h=
as taken
> every reasonable precaution to minimize this risk, but is not liable for =
any damage
> you may sustain as a result of any virus in this e-mail. You should carry=
 out your
> own virus checks before opening the e-mail or attachment. Infosys reserve=
s the
> right to monitor and review the content of all messages sent to or from t=
his e-mail
> address. Messages sent to or from this e-mail address may be stored on th=
e
> Infosys e-mail system.
> ***INFOSYS******** End of Disclaimer ********INFOSYS***
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim


From tena@huawei.com  Tue May 24 15:17:43 2011
Return-Path: <tena@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 0EEF5E07E0; Tue, 24 May 2011 15:17:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.959
X-Spam-Level: 
X-Spam-Status: No, score=-105.959 tagged_above=-999 required=5 tests=[AWL=0.640, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JhtYsTorNbZA; Tue, 24 May 2011 15:17:42 -0700 (PDT)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by ietfa.amsl.com (Postfix) with ESMTP id 02D8BE07E1; Tue, 24 May 2011 15:17:42 -0700 (PDT)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LLQ008RS0LGS6@usaga02-in.huawei.com>; Tue, 24 May 2011 15:17:41 -0700 (PDT)
Received: from TingZousc1 ([10.193.34.188]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LLQ00DND0LF6B@usaga02-in.huawei.com>; Tue, 24 May 2011 15:17:40 -0700 (PDT)
Date: Tue, 24 May 2011 15:17:40 -0700
From: Tina Tsou <tena@huawei.com>
In-reply-to: <A2408947975D7A4C95A0DD337F638258021C8066@LODERI.intra.cea.fr>
To: 'KELLIL Mounir' <mounir.kellil@cea.fr>
Message-id: <028b01cc1a60$659de150$30d9a3f0$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=iso-8859-1
Content-language: en-us
Content-transfer-encoding: quoted-printable
Thread-index: AcwGwOluKJ5ympwvR4KrSLJ5rPlZEACF+jLgAAdmFIAAHIpN4AAiDQsQAA/ku3AEC+zpwA==
References: <009401cc06c0$eaa919e0$bffb4da0$@com> <A2408947975D7A4C95A0DD337F638258021C7FC6@LODERI.intra.cea.fr> <018701cc08f6$cb23cd80$616b6880$@com> <A2408947975D7A4C95A0DD337F638258021C7FFD@LODERI.intra.cea.fr> <012c01cc09f1$441cacc0$cc560640$@com> <A2408947975D7A4C95A0DD337F638258021C8066@LODERI.intra.cea.fr>
Cc: 'MBONED WG' <mboned@ietf.org>, multrans@ietf.org, pim@ietf.org
Subject: Re: [pim] [multrans] Comments on Dual Stack case
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, 24 May 2011 22:17:43 -0000

Bonjour Mounir,
Would you send out your comments these two days?
Christian is working on the Problem Statement I-D and plans to post the =
I-D
at the end of this week.


We keep our promises with one another =96 no matter what!

Best Regards,
Tina TSOU
http://tinatsou.weebly.com/contact.html


-----Original Message-----
From: KELLIL Mounir [mailto:mounir.kellil@cea.fr]=20
Sent: Wednesday, May 04, 2011 12:56 AM
To: Tina Tsou
Cc: MBONED WG; pim@ietf.org; multrans@ietf.org
Subject: RE: [multrans] Comments on Dual Stack case

Bonjour Tina,

Sure I will be happy to review the document

Regards

Mounir KELLIL
CEA LIST
e-mail : mounir.kellil@cea.fr
web : http://www-list.cea.fr
=20
> -----Message d'origine-----
> De=A0: Tina Tsou [mailto:tena@huawei.com]
> Envoy=E9=A0: mercredi 4 mai 2011 02:22
> =C0=A0: KELLIL Mounir
> Cc=A0: 'MBONED WG'; pim@ietf.org; multrans@ietf.org
> Objet=A0: RE: [multrans] Comments on Dual Stack case
>=20
> Bonjour Mounir,
> If you consider a dual-stack network only, that's what we are looking
> for.
>=20
> Would you review
> https://datatracker.ietf.org/doc/draft-jaclee-behave-v4v6-mcast-ps/,
> and
> send out your comments or proposed text to reflect the issues of a =
dual
> stack network, which is not covered by the current version?
>=20
> Merci.
>=20
> Yiu Lee is editing the XML file.
>=20
>=20
> We keep our promises with one another - no matter what!
>=20
> Best Regards,
> Tina TSOU
> http://tinatsou.weebly.com/contact.html
>=20
>=20
> -----Original Message-----
> From: KELLIL Mounir [mailto:mounir.kellil@cea.fr]
> Sent: Tuesday, May 03, 2011 1:12 AM
> To: Tina Tsou
> Cc: MBONED WG; pim@ietf.org; multrans@ietf.org
> Subject: RE: [multrans] Comments on Dual Stack case
>=20
> Bonjour Tina,
>=20
> We consider a dual-stack network only. The source could be IPv4 only =
or
> IPv6
> only, not necessarily both. Regarding SAMRG, they normally intend to
> push
> the work (not ours) further to IETF. But, honestly, I am not aware of
> their
> current status.
>=20
> BTW, I will be happy to follow the discussions on multirans
>=20
> Best regards
>=20
> Mounir
>=20
> Mounir KELLIL
> CEA LIST
> e-mail : mounir.kellil@cea.fr
> web : http://www-list.cea.fr
>=20
> > -----Message d'origine-----
> > De=A0: Tina Tsou [mailto:tena@huawei.com]
> > Envoy=E9=A0: lundi 2 mai 2011 20:29
> > =C0=A0: KELLIL Mounir
> > Cc=A0: 'MBONED WG'; pim@ietf.org; multrans@ietf.org
> > Objet=A0: RE: [multrans] Comments on Dual Stack case
> >
> > Bonjour Mounir,
> > Thank you. I read draft-kellil-sam-mtocp-01, it is useful to
> multrans.
> > Do
> > you consider dual stack network and/or dual stack source?
> > How is the status of IRTF's SAMRG group? Is it time to move some of
> the
> > research result into IETF now?
> >
> >
> > We keep our promises with one another - no matter what!
> >
> > Best Regards,
> > Tina TSOU
> > http://tinatsou.weebly.com/contact.html
> >
> >
> > -----Original Message-----
> > From: KELLIL Mounir [mailto:mounir.kellil@cea.fr]
> > Sent: Monday, May 02, 2011 8:10 AM
> > To: Tina Tsou
> > Cc: MBONED WG; pim@ietf.org; multrans@ietf.org
> > Subject: RE: [multrans] Comments on Dual Stack case
> >
> > Hi Tina,
> >
> > I think the problem you are addressing is interesting. It reminds me
> a
> > work
> > we've done in our team a few months ago (an old draft:
> > http://tools.ietf.org/html/draft-kellil-sam-mtocp-01). We addressed
> the
> > multicasting problem in a heterogeneous IP network (heterogeneity in
> > terms
> > of multicast support and IP protocol version). We proposed an =
overlay
> > paradigm to be applied at the transport layer. Overlay nodes are in
> > charge
> > of forwarding traffic, but also translating IPv4 packets into IPv6
> > packets
> > and vice versa. Maybe this work (and probably others from IRTF's
> SAMRG
> > group) could be quoted as a "state-of-the-art". Just a suggestion...
> >
> >
> > Regards
> >
> > Mounir KELLIL
> >
> > CEA LIST
> > web : http://www-list.cea.fr
> >
> > > -----Message d'origine-----
> > > De=A0: multrans-bounces@ietf.org =
[mailto:multrans-bounces@ietf.org]
> De
> > la
> > > part de Tina Tsou
> > > Envoy=E9=A0: samedi 30 avril 2011 00:58
> > > =C0=A0: multrans@ietf.org
> > > Cc=A0: 'MBONED WG'; pim@ietf.org
> > > Objet=A0: [multrans] Comments on Dual Stack case
> > >
> > > Hi all,
> > > Just bring some comments on the dual stack case for the new =
problem
> > > statement I-D based on
> > > https://datatracker.ietf.org/doc/draft-jaclee-behave-v4v6-mcast-
> ps/.
> > > And I
> > > also suggest the new problem statement I-D being
> > > draft-jaclee-multrans-v4v6-mcast-ps, since it is not ONLY behave
> any
> > > more.
> > >
> > > I cc pim@ietf.org and mboned@ietf.org looking for multicast
> expertise
> > > to
> > > help on input to this new problem statement.
> > >
> > > Comments on Dual Stack case are below, inspired by talk with Stig.
> > > 1. Even in the native dual stack case, you want to save bandwidth,
> > not
> > > put
> > > two copy of bandwidth under one source.
> > >
> > > 2. For P2MP case, the receivers are part of IPv4, part of IPv6,
> this
> > is
> > > problem.
> > >
> > > 3. For video conference, you have 30 people, 15 are v4, 15 are v6,
> > and
> > > any
> > > of them can send their videos (everyone has a webcam and
> microphone).
> > >
> > >
> > > We keep our promises with one another - no matter what!
> > >
> > > Best Regards,
> > > Tina TSOU
> > > http://tinatsou.weebly.com/contact.html
> > >
> > >
> > >
> > > _______________________________________________
> > > multrans mailing list
> > > multrans@ietf.org
> > > https://www.ietf.org/mailman/listinfo/multrans
>=20



From rishabhp@gmail.com  Wed May 25 13:52:07 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 6B745130105 for <pim@ietfa.amsl.com>; Wed, 25 May 2011 13:52:07 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YP5WaSDQfoK2 for <pim@ietfa.amsl.com>; Wed, 25 May 2011 13:52:02 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id B149E1300F2 for <pim@ietf.org>; Wed, 25 May 2011 13:52:01 -0700 (PDT)
Received: by iwn39 with SMTP id 39so46495iwn.31 for <pim@ietf.org>; Wed, 25 May 2011 13:52:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to:cc :content-type; bh=TYuQEYLGxf5Vjase/DoN7WFQsuKjsRM4LcDLcqWimzQ=; b=wcIMwNcI8UlWxnMU5LktCJm8FUPYIuRkxLhR7EpxaeyP7JfNWRt8qjEaH4B2GApOFj qgMERugy6WMx4y94EWHPxZVZtXO/ygJqofJ51RSzykCMPtbnAeEj+jm0jeWTZqEiqZ6y Baw8Kk0kVhp4+8HNgTMnsQ41tW1gPBNgTPzG4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=ktA/NAjqFvJ4j3J+RHC39+guO5K/I8LGUMbzsMmHK7D2Bsj9vAT+qoz/YyaPTTN6KK ia0EyZnXb8tZmL42iWfsIBKyJZHX8rlubSdfqW3tK6pUybR1ge/d/yMeHc09ZbbSiPey NLMMMoXonHIubbHu1EpnReED0Wd5p5H8kI80o=
MIME-Version: 1.0
Received: by 10.231.5.79 with SMTP id 15mr45985ibu.48.1306356721238; Wed, 25 May 2011 13:52:01 -0700 (PDT)
Received: by 10.231.206.144 with HTTP; Wed, 25 May 2011 13:52:01 -0700 (PDT)
Date: Wed, 25 May 2011 13:52:01 -0700
Message-ID: <BANLkTimPiuPR7CdV2kecfSBiV5ofm3giEA@mail.gmail.com>
From: Rishabh Parekh <rishabhp@gmail.com>
To: pim@ietf.org
Content-Type: multipart/alternative; boundary=00151774046e51c14104a41fe00f
Subject: [pim] rfc4601bis draft
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, 25 May 2011 20:52:07 -0000

--00151774046e51c14104a41fe00f
Content-Type: text/plain; charset=ISO-8859-1

As a part of the WG effort to advance PIM-SM to a Draft Standard, as
mentioned in the below messages to the mailing list, we have submitted the
first revision of rfc4601bis draft @
http://tools.ietf.org/id/draft-parekh-pim-rfc4601bis-00.txt

http://www.ietf.org/mail-archive/web/pim/current/msg02123.html
http://www.ietf.org/mail-archive/web/pim/current/msg02124.html

This 00 revision of the draft addresses all errata, except those classified
as Rejected and erratum 1161, filed against RFC 4601. Although all the
errata fixed are of non-technical nature, we encourage the list members to
go through the draft and provide comments.

Thanks,
Rishabh.

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

As a part of the WG effort to advance PIM-SM to a Draft Standard, as mentio=
ned in the below messages to the mailing list, we have submitted the first =
revision of rfc4601bis draft @ <a href=3D"http://tools.ietf.org/id/draft-pa=
rekh-pim-rfc4601bis-00.txt">http://tools.ietf.org/id/draft-parekh-pim-rfc46=
01bis-00.txt</a><br>
<br><a href=3D"http://www.ietf.org/mail-archive/web/pim/current/msg02123.ht=
ml">http://www.ietf.org/mail-archive/web/pim/current/msg02123.html</a><br><=
a href=3D"http://www.ietf.org/mail-archive/web/pim/current/msg02124.html">h=
ttp://www.ietf.org/mail-archive/web/pim/current/msg02124.html</a><br>
<br>This 00 revision of the draft addresses all errata, except those classi=
fied as Rejected and erratum 1161, filed against RFC 4601. Although all the=
 errata fixed are of non-technical nature, we encourage the list members to=
 go through the draft and provide comments.<br>
<br>Thanks,<br>Rishabh. <br>

--00151774046e51c14104a41fe00f--

From thomas.morin@orange-ftgroup.com  Fri May 27 01:59:47 2011
Return-Path: <thomas.morin@orange-ftgroup.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 690CFE07B9 for <pim@ietfa.amsl.com>; Fri, 27 May 2011 01:59:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.148
X-Spam-Level: 
X-Spam-Status: No, score=-102.148 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gf4bKZmUW-zQ for <pim@ietfa.amsl.com>; Fri, 27 May 2011 01:59:46 -0700 (PDT)
Received: from r-mail2.rd.francetelecom.com (r-mail2.rd.francetelecom.com [217.108.152.42]) by ietfa.amsl.com (Postfix) with ESMTP id 8ED28E0761 for <pim@ietf.org>; Fri, 27 May 2011 01:59:46 -0700 (PDT)
Received: from r-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 01045FC40E1 for <pim@ietf.org>; Fri, 27 May 2011 10:59:45 +0200 (CEST)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by r-mail2.rd.francetelecom.com (Postfix) with ESMTP id EB149FC40E0 for <pim@ietf.org>; Fri, 27 May 2011 10:59:44 +0200 (CEST)
Received: from ftrdmel10.rd.francetelecom.fr ([10.192.128.44]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 27 May 2011 10:59:44 +0200
Received: from [10.193.71.142] ([10.193.71.142]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 27 May 2011 10:59:44 +0200
Message-ID: <4DDF6800.3050004@orange-ftgroup.com>
Date: Fri, 27 May 2011 10:59:44 +0200
From: Thomas Morin <thomas.morin@orange-ftgroup.com>
Organization: France Telecom Orange
User-Agent: Mozilla/5.0 (X11; U; ; ; ) Gecko/2010 Thunderbird/3.1.x
MIME-Version: 1.0
To: pim@ietf.org
References: <BANLkTimPiuPR7CdV2kecfSBiV5ofm3giEA@mail.gmail.com>
In-Reply-To: <BANLkTimPiuPR7CdV2kecfSBiV5ofm3giEA@mail.gmail.com>
X-TagToolbar-Keys: D20110527105943993
Content-Type: multipart/alternative; boundary="------------090200050603090901090106"
X-OriginalArrivalTime: 27 May 2011 08:59:44.0201 (UTC) FILETIME=[6C012B90:01CC1C4C]
Subject: Re: [pim] rfc4601bis draft
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, 27 May 2011 08:59:47 -0000

This is a multi-part message in MIME format.
--------------090200050603090901090106
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

For those who want to easily see what's changed between RFC4601 and this 
draft:

http://tools.ietf.org//rfcdiff?url1=rfc4601&url2=http://tools.ietf.org/id/draft-parekh-pim-rfc4601bis

-Thomas


Rishabh Parekh a Ã©crit :
> As a part of the WG effort to advance PIM-SM to a Draft Standard, as 
> mentioned in the below messages to the mailing list, we have submitted 
> the first revision of rfc4601bis draft @ 
> http://tools.ietf.org/id/draft-parekh-pim-rfc4601bis-00.txt
>
> http://www.ietf.org/mail-archive/web/pim/current/msg02123.html
> http://www.ietf.org/mail-archive/web/pim/current/msg02124.html
>
> This 00 revision of the draft addresses all errata, except those 
> classified as Rejected and erratum 1161, filed against RFC 4601. 
> Although all the errata fixed are of non-technical nature, we 
> encourage the list members to go through the draft and provide comments.
>
> Thanks,
> Rishabh.
>
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim

--------------090200050603090901090106
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#ffffff">
    For those who want to easily see what's changed between RFC4601 and
    this draft:<br>
    <br>
<a class="moz-txt-link-freetext" href="http://tools.ietf.org//rfcdiff?url1=rfc4601&amp;url2=http://tools.ietf.org/id/draft-parekh-pim-rfc4601bis">http://tools.ietf.org//rfcdiff?url1=rfc4601&amp;url2=http://tools.ietf.org/id/draft-parekh-pim-rfc4601bis</a><br>
    <br>
    -Thomas<br>
    <br>
    <br>
    Rishabh Parekh a Ã©critÂ :
    <blockquote
      cite="mid:BANLkTimPiuPR7CdV2kecfSBiV5ofm3giEA@mail.gmail.com"
      type="cite">As a part of the WG effort to advance PIM-SM to a
      Draft Standard, as mentioned in the below messages to the mailing
      list, we have submitted the first revision of rfc4601bis draft @ <a
        moz-do-not-send="true"
        href="http://tools.ietf.org/id/draft-parekh-pim-rfc4601bis-00.txt">http://tools.ietf.org/id/draft-parekh-pim-rfc4601bis-00.txt</a><br>
      <br>
      <a moz-do-not-send="true"
        href="http://www.ietf.org/mail-archive/web/pim/current/msg02123.html">http://www.ietf.org/mail-archive/web/pim/current/msg02123.html</a><br>
      <a moz-do-not-send="true"
        href="http://www.ietf.org/mail-archive/web/pim/current/msg02124.html">http://www.ietf.org/mail-archive/web/pim/current/msg02124.html</a><br>
      <br>
      This 00 revision of the draft addresses all errata, except those
      classified as Rejected and erratum 1161, filed against RFC 4601.
      Although all the errata fixed are of non-technical nature, we
      encourage the list members to go through the draft and provide
      comments.<br>
      <br>
      Thanks,<br>
      Rishabh. <br>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
pim mailing list
<a class="moz-txt-link-abbreviated" href="mailto:pim@ietf.org">pim@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/pim">https://www.ietf.org/mailman/listinfo/pim</a>
</pre>
    </blockquote>
  </body>
</html>

--------------090200050603090901090106--

From stig@venaas.com  Fri May 27 10:56:29 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 B2662E0655 for <pim@ietfa.amsl.com>; Fri, 27 May 2011 10:56:29 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fYdMYMJGQ2sx for <pim@ietfa.amsl.com>; Fri, 27 May 2011 10:56: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 A69EFE066A for <pim@ietf.org>; Fri, 27 May 2011 10:56:28 -0700 (PDT)
Received: from [10.33.12.67] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id CBC1C7FCB for <pim@ietf.org>; Fri, 27 May 2011 19:56:22 +0200 (CEST)
Message-ID: <4DDFE5C2.4000803@venaas.com>
Date: Fri, 27 May 2011 10:56:18 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: pim@ietf.org
References: <DB95C89A3E33E946B4E3F7E00BA8B09331FE0C@xmb-sjc-21d.amer.cisco.com>
In-Reply-To: <DB95C89A3E33E946B4E3F7E00BA8B09331FE0C@xmb-sjc-21d.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [pim] draft-ietf-pim-hello-intid-00 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: Fri, 27 May 2011 17:56:29 -0000

On 5/20/2011 10:59 AM, Mike McBride (mmcbride) wrote:
> Today begins a two week wglc for draft-ietf-pim-hello-intid-00. Please
> review the draft. Then indicate to us if its worthy, or not, of being
> sent to the iesg.
>
> http://www.ietf.org/id/draft-ietf-pim-hello-intid-00.txt

We only have one week left of the wglc, and only got one response
so far. Please let us know whether you think this document is ready,
or needs some changes.

Even if you are in favor, we need to hear your support,

Stig

>
> thanks,
> mike
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim


From stig@venaas.com  Fri May 27 11:03: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 6688EE0726 for <pim@ietfa.amsl.com>; Fri, 27 May 2011 11:03: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Al+05yGnmjI for <pim@ietfa.amsl.com>; Fri, 27 May 2011 11:03:59 -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 CB7CDE066A for <pim@ietf.org>; Fri, 27 May 2011 11:03:58 -0700 (PDT)
Received: from [10.33.12.67] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id 66A687FD2 for <pim@ietf.org>; Fri, 27 May 2011 20:03:57 +0200 (CEST)
Message-ID: <4DDFE78B.9040309@venaas.com>
Date: Fri, 27 May 2011 11:03:55 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
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
Subject: [pim] Adoption of draft-asaeda-mboned-explicit-tracking-02
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, 27 May 2011 18:03:59 -0000

We seem to be in full agreement on adding the text allowing some IGMP
work to our charter. While we haven't officially rechartered yet, we
would like to hear from you whether you believe
draft-asaeda-mboned-explicit-tracking-02
should be adopted, pending the charter update.

Please let us know by the end of next week (June 3rd) whether it should
be adopted.

If you have any concerns about the draft, please let us know what those
are as well.

Stig

From N.Leymann@telekom.de  Mon May 30 00:42:50 2011
Return-Path: <N.Leymann@telekom.de>
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 03B90E0692 for <pim@ietfa.amsl.com>; Mon, 30 May 2011 00:42:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b3hccZVojz6N for <pim@ietfa.amsl.com>; Mon, 30 May 2011 00:42:49 -0700 (PDT)
Received: from tcmail33.telekom.de (tcmail33.telekom.de [194.25.30.7]) by ietfa.amsl.com (Postfix) with ESMTP id ED7BBE064A for <pim@ietf.org>; Mon, 30 May 2011 00:42:47 -0700 (PDT)
Received: from he101250.emea1.cds.t-internal.com ([10.125.92.153]) by tcmail31.telekom.de with ESMTP/TLS/AES128-SHA; 30 May 2011 09:37:04 +0200
Received: from HE111543.emea1.cds.t-internal.com ([169.254.4.212]) by HE101250.emea1.cds.t-internal.com ([fe80::e439:4046:12e2:e37%15]) with mapi; Mon, 30 May 2011 09:37:03 +0200
From: <N.Leymann@telekom.de>
To: <stig@venaas.com>, <pim@ietf.org>
Date: Mon, 30 May 2011 09:37:02 +0200
Thread-Topic: [pim] Adoption of draft-asaeda-mboned-explicit-tracking-02
Thread-Index: AcwcmHtzqBP3cUGmT72ejp3BLyl2bQCA9JEQ
Message-ID: <9762ACF04FA26B4388476841256BDE02011445EAF218@HE111543.emea1.cds.t-internal.com>
References: <4DDFE78B.9040309@venaas.com>
In-Reply-To: <4DDFE78B.9040309@venaas.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pim] Adoption of draft-asaeda-mboned-explicit-tracking-02
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, 30 May 2011 07:42:50 -0000

Support!

-----Urspr=FCngliche Nachricht-----
Von: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] Im Auftrag von Stig=
 Venaas
Gesendet: Freitag, 27. Mai 2011 20:04
An: pim@ietf.org
Betreff: [pim] Adoption of draft-asaeda-mboned-explicit-tracking-02

We seem to be in full agreement on adding the text allowing some IGMP
work to our charter. While we haven't officially rechartered yet, we
would like to hear from you whether you believe
draft-asaeda-mboned-explicit-tracking-02
should be adopted, pending the charter update.

Please let us know by the end of next week (June 3rd) whether it should
be adopted.

If you have any concerns about the draft, please let us know what those
are as well.

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