
From mmcbride7@gmail.com  Wed Oct  2 19:47:17 2013
Return-Path: <mmcbride7@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 6A42021F9B90 for <pim@ietfa.amsl.com>; Wed,  2 Oct 2013 19:47:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ImiCPGK2uLZp for <pim@ietfa.amsl.com>; Wed,  2 Oct 2013 19:47:10 -0700 (PDT)
Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id 2EAB421F9B08 for <pim@ietf.org>; Wed,  2 Oct 2013 19:47:03 -0700 (PDT)
Received: by mail-pa0-f51.google.com with SMTP id kp14so1929037pab.10 for <pim@ietf.org>; Wed, 02 Oct 2013 19:47:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=Pr8vSk5b5gWTcZUsuP3jNXTSzfda4OjfAWSwA9Eic94=; b=yQwCskmekeQXP2CSgb+pJK1YcUhMtv6tuhSs25QphEp3TH3+i1TYtDOkkW0n5VTEK5 MVL+DL6flCGpjOUHRt2VT3YioUWjFhAgOhXBjw5WMjlt8Z9G3BILXqyB0nnf7NShPuBo +rW7oGbvz/4S98C4Ct/jZ6XvplQBizR2sHoxBbkefH7DJ/0tIRvH2cXqGVDpsfn+b4Kd xaiSY54Bb/2dBq/be+lrD82M2j051SLnarg5XVBYODfPlQnlxE+lQJAE/HgJxA+GYkrQ vwtMapqJnvF3yi7BrYIz6qfVDmwGvpV1mZCeaKQIK/RWmpLZtH+BvaTYS71+nJTUnUdR UX4w==
MIME-Version: 1.0
X-Received: by 10.68.230.166 with SMTP id sz6mr5772528pbc.157.1380768423715; Wed, 02 Oct 2013 19:47:03 -0700 (PDT)
Received: by 10.68.65.198 with HTTP; Wed, 2 Oct 2013 19:47:03 -0700 (PDT)
Date: Wed, 2 Oct 2013 19:47:03 -0700
Message-ID: <CAL3FGfxPuyZ1j4yD_MreuT77E_Lt+EWWU17nHKq1kqA1KgzTow@mail.gmail.com>
From: Mike McBride <mmcbride7@gmail.com>
To: "pim@ietf.org" <pim@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [pim] adoption call for draft-venaas-pim-hierarchicaljoinattr-00
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Oct 2013 02:47:17 -0000

I'm making the call that we have enough support to adopt. Authors:
please submit as a wg document.

thanks,
mike

On Mon, Sep 23, 2013 at 1:54 PM, Mike McBride <mmcbride7@gmail.com> wrote:
> During our most recent meeting in Berlin, 4 of you were in favor of
> adopting this draft. None against. Bharat Joshi has expressed support
> of adoption on the list. Not a ton of feedback but perhaps enough. I'm
> opening this up for comment one last time before making a decision.
> Please speak your peace about this draft within a week from today.
>
> thanks,
> mike
>
> On Sun, Jul 14, 2013 at 12:24 AM, Mike McBride <mmcbride7@gmail.com> wrote:
>> Today begins a call for adoption of:
>> http://www.ietf.org/id/draft-venaas-pim-hierarchicaljoinattr-00.txt.
>> This draft was presented in Orlando where 3 were in favor, of working
>> on this within the wg, and none against.
>>
>> Please read this short draft and provide an opinion on the list before
>> we meet in Berlin.
>>
>> thanks,
>> mike

From asaeda@sfc.wide.ad.jp  Sun Oct  6 02:50:57 2013
Return-Path: <asaeda@sfc.wide.ad.jp>
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 51C8D21F9E6B for <pim@ietfa.amsl.com>; Sun,  6 Oct 2013 02:50:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U33tDH-4dbjg for <pim@ietfa.amsl.com>; Sun,  6 Oct 2013 02:50:56 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (ns.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:143]) by ietfa.amsl.com (Postfix) with ESMTP id 3CF1D21F9FB7 for <pim@ietf.org>; Sun,  6 Oct 2013 02:50:52 -0700 (PDT)
Received: from localhost (p14180-ipngn2101marunouchi.tokyo.ocn.ne.jp [114.178.225.180]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 2753A2780BE; Sun,  6 Oct 2013 18:50:51 +0900 (JST)
Date: Sun, 06 Oct 2013 18:50:50 +0900 (JST)
Message-Id: <20131006.185050.264038763.asaeda@sfc.wide.ad.jp>
To: bharat_joshi@infosys.com
From: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
In-Reply-To: <35347FBF2796F94E936EE76C0E6047ED32ECE5B4@BLRKECMBX13.ad.infosys.com>
References: <52278117.30906@venaas.com> <35347FBF2796F94E936EE76C0E6047ED32ECE5B4@BLRKECMBX13.ad.infosys.com>
X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: pim@ietf.org
Subject: Re: [pim] draft-ietf-pim-explicit-tracking pim 3rd 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: Sun, 06 Oct 2013 09:50:57 -0000

Hi Bharat,

Thank you for your detail comments, and sorry for my late response.
I'll submit -08 tomorrow, but before it, I reply for your mail.

> * In Introduction, in following sentence:
> 
>    Also, a querier router periodically sends IGMP/MLD General Query
>    messages within the General Query timer interval (i.e. [Query
>    Interval] value defined in [2][3]).
> 
> Should we use 'every' instead of 'within the'? It will become:
> 
>    Also, a querier router periodically sends IGMP/MLD General Query
>    messages every General Query timer interval (i.e. [Query
>    Interval] value defined in [2][3]).

Done.

> * In Introduction, in following sentence:
> 
>    IGMPv3 [2], MLDv2 [3], and these lightweight protocols [4] can
>    provide the ability to keep track of the downstream (adjacent)
>    multicast membership state to multicast routers, yet the
>    specifications are not clearly given. 
> 
> Should we use 'in mulicast routers' instead of 'to multicast routers'. It will become:
> 
>    IGMPv3 [2], MLDv2 [3], and these lightweight protocols [4] can
>    provide the ability to keep track of the downstream (adjacent)
>    multicast membership state in multicast routers, yet the
>    specifications are not clearly given. 

Done.

> * In Introduction, in following sentence:
> 
>    Particularly when a router needs to maintain a large number of
>    member hosts, this resource requirement could have an impact. 
> 
> Can we elaborate a little on the 'impact' we are referring here? What kind of impact? Is it impact on router functionality or something else?

I changed to "might be sensitive".

> * In section 3, the draft describes the new multicast membership
> state information a multicast router conforming to this draft
> creates. For implementors, should not this draft also mention when
> or under what conditions to remove this membership state?

I added;
"The router will flush the maintained membership state information
when it reboots or restarts the multicast routing processes."

> * In section 4, in following sentence:
> 
>    All member hosts joining the identical
>    channel then reply their own states after acquiring these query
>    messages. 
> 
> Will it be better to add a 'with' between 'reply' and 'their'? It will become:
> 
>    All member hosts joining the identical
>    channel then reply with their own states after acquiring these query
>    messages. 

Done.

> * In section 4, in second para, it is exaplained that if router
> receives one or more replies from the downstream members, it can
> stop retransmitting the specific query message. In my understanding,
> this should be reworeded to say that the groups or sources for which
> downstream members exist, should not be included in subsequent
> specific query messages. If there is no such group or source
> available, router can stop sending specific query message.

I added "for the specified source and/or group" at the last part of
that sentence such as:
"... it can stop (i.e., cancel) retransmitting the specific query
message(s) for the specified source and/or group."

> * In section 4, in last para, in following sentence:
> 
>    For the latter
>    case, when the querier suppresses the specific query message
>    transmission, and expects that the State-Change Report sender is not
>    the sole member of the channel, it does not send the specific query
>    and none of the routers on the same LAN receive a Current-State
>    Report message from the corresponding member hosts. 
> 
> This sentence is too big and is not clear enough. Can we please divide this into multiple sentences?

I split into two sentences.

> * In section 5, in para 4 :
> 
>    Furthermore, if operators believe that their link is fairly robust or
>    that they can configure the [Robustness Variable] value appropriately
>    so that the chances of unsolicited messages being lost are
>    sufficiently low, and if the querier router is always the forwarder
>    router in their link, they will set smaller LMQC/LLQC and shorter
>    LMQI/LLQI (and hence shorter LMQT/LLQT) with the specific query
>    suppression or enable the specific query suppression in a robust link
>    state (Section 4) for their routers.
> 
> This whole para is one single sentence. Someone reading it may be
> lost. So in my opinion, it is better to divide this into multiple
> sentences.

I use "()" for sentence to be omitted. If you skip "()" parts, it will
be;

"Furthermore, if operators are confident that their link is fairly
robust, and if the querier router always acts as the forwarder router
for all mutlicast channels in the LAN, they will set smaller LMQC/LLQC
and shorter LMQI/LLQI with the specific query suppression, or enable
the specific query suppression in a robust link state (Section 4) for
their routers."

It is readable?

> Another suggestion is that we do not really need the part "and if
> the querier router is always the forwarder router in their link," in
> this sentence. I am not sure why is this required here?

It is explained in Sect.4 as follows;
"when the querier suppresses the specific query message transmission,
and expects that the State-Change Report sender is not the sole member
of the channel, it does not send the specific query. Then the routers
(including the forwarder) on the same LAN do not receive a
Current-State Report message from the corresponding member hosts. The
forwarder in this case may prune the routing path, although there are
other member hosts subscribing to the channel on the LAN."
(This sentense is a little modified from -07.)

> * In Security consideration, do you think it will be good to mention
> about 'IPSec' usage for IGMP/MLD messages as well?

I don't think so. It needs enough consideration, which is out of
scope of this document.
(Relying on IPsec is not always happy for every situation, IMO.)

Regards,
--
Hitoshi Asaeda

From bharat_joshi@infosys.com  Sun Oct  6 19:53:18 2013
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 2FF1821E811F for <pim@ietfa.amsl.com>; Sun,  6 Oct 2013 19:53:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6148H-Q8e-0F for <pim@ietfa.amsl.com>; Sun,  6 Oct 2013 19:53:13 -0700 (PDT)
Received: from kecgate06.infosys.com (kecgate06.infosys.com [122.98.14.33]) by ietfa.amsl.com (Postfix) with ESMTP id 24A8821F9EE1 for <pim@ietf.org>; Sun,  6 Oct 2013 19:53:11 -0700 (PDT)
X-TM-IMSS-Message-ID: <1d1d9a21000433c1@infosys.com>
Received: from blrkechub01.ad.infosys.com ([10.66.236.41]) by infosys.com ([122.98.14.33]) with ESMTP (TREND IMSS SMTP Service 7.1) id 1d1d9a21000433c1 ; Mon, 7 Oct 2013 08:23:28 +0530
Received: from BLRKECHUB07.ad.infosys.com (10.66.236.117) by blrkechub01.ad.infosys.com (10.66.236.41) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 7 Oct 2013 08:21:08 +0530
Received: from BLRKECMBX13.ad.infosys.com ([fe80::c43d:ba67:abc0:11c3]) by BLRKECHUB07.ad.infosys.com ([::1]) with mapi id 14.02.0318.004; Mon, 7 Oct 2013 08:21:08 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
Thread-Topic: [pim] draft-ietf-pim-explicit-tracking pim 3rd wglc
Thread-Index: AQHOqZ+2G+mQy2J0Pk2hn5mLyLwI2ZnACUlLgCc6VwCAAXd9Hw==
Date: Mon, 7 Oct 2013 02:51:07 +0000
Message-ID: <35347FBF2796F94E936EE76C0E6047ED3BFF0BF1@BLRKECMBX13.ad.infosys.com>
References: <52278117.30906@venaas.com> <35347FBF2796F94E936EE76C0E6047ED32ECE5B4@BLRKECMBX13.ad.infosys.com>, <20131006.185050.264038763.asaeda@sfc.wide.ad.jp>
In-Reply-To: <20131006.185050.264038763.asaeda@sfc.wide.ad.jp>
Accept-Language: en-US, en-IN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.200.132]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] draft-ietf-pim-explicit-tracking pim 3rd 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, 07 Oct 2013 02:53:18 -0000

Hitoshi,

       Thanks for taking care of my comments. I have some replies inline =
with 'Bharat>'

Regards,
Bharat Joshi
http://bite-the-bytes.blogspot.com/

> * In Introduction, in following sentence:
>
>    Particularly when a router needs to maintain a large number of
>    member hosts, this resource requirement could have an impact.
>
> Can we elaborate a little on the 'impact' we are referring here? What k=
ind of impact? Is it impact on router functionality or something else?

I changed to "might be sensitive".

Bharat> If we are saying that it could have an impact or it might be sens=
itive, I think we should also say in what respect? This will give a beter=
 idea for an implementor. Please ask others in the mailing list if they c=
an suggest something.

> * In section 3, the draft describes the new multicast membership
> state information a multicast router conforming to this draft
> creates. For implementors, should not this draft also mention when
> or under what conditions to remove this membership state?

I added;
"The router will flush the maintained membership state information
when it reboots or restarts the multicast routing processes."

Bharat> This takes care of only one part. In this section, we describe wh=
en to add the membership state, so we should also describe when to remove=
 this state. For example: when a leave is received from a requestor, this=
 membership state for this requestor will be removed. Similarly, if the g=
roup/source timer fires for a given group, all the membership state will =
also be removed.

> * In section 5, in para 4 :
>
>    Furthermore, if operators believe that their link is fairly robust o=
r
>    that they can configure the [Robustness Variable] value appropriatel=
y
>    so that the chances of unsolicited messages being lost are
>    sufficiently low, and if the querier router is always the forwarder
>    router in their link, they will set smaller LMQC/LLQC and shorter
>    LMQI/LLQI (and hence shorter LMQT/LLQT) with the specific query
>    suppression or enable the specific query suppression in a robust lin=
k
>    state (Section 4) for their routers.
>
> This whole para is one single sentence. Someone reading it may be
> lost. So in my opinion, it is better to divide this into multiple
> sentences.

I use "()" for sentence to be omitted. If you skip "()" parts, it will
be;

"Furthermore, if operators are confident that their link is fairly
robust, and if the querier router always acts as the forwarder router
for all mutlicast channels in the LAN, they will set smaller LMQC/LLQC
and shorter LMQI/LLQI with the specific query suppression, or enable
the specific query suppression in a robust link state (Section 4) for
their routers."

It is readable?

Bharat> Yes, it seems ok.

**************** 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***

From ramakanthjosyula@gmail.com  Mon Oct  7 05:03:53 2013
Return-Path: <ramakanthjosyula@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 E089221F9F21; Mon,  7 Oct 2013 05:03:53 -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, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rj6g7CVOLlr2; Mon,  7 Oct 2013 05:03:53 -0700 (PDT)
Received: from mail-la0-x232.google.com (mail-la0-x232.google.com [IPv6:2a00:1450:4010:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 6DB1B21E805F; Mon,  7 Oct 2013 05:03:48 -0700 (PDT)
Received: by mail-la0-f50.google.com with SMTP id gx14so5363979lab.23 for <multiple recipients>; Mon, 07 Oct 2013 05:03:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=H0PLyHYk4hBVt/oh5ueQ+GhSvj9r9TPElKJa8TRYdjU=; b=Ea/VThEGRxGD/SIOHqTiUApVO0A3yjIbsGrnSH9nTIl86xCldfLcvDUg0s1HjmHJiG zQ84le4mt1uJId78uhMNRch3D723EA7kErPasAtrvdVluazw+oLEV8Fc9uNsQ/fFLhNI Qv1piRntARQxKWf/cDtv6ya1B/I5sMueCM5I0B6DQLWs449xNyXfBLIOedMaco29iJqs s1hHF7VJeInXlO4z7PouBsEjdOVJU1NweIcGlsW5Hy1EUXBC6HrJfj9DrJIJTFm0umSB ctB/asrrYYILVG2XDauY5yAHpdFhw+aVfJnGmV/Ar/c833FmgRrDujtW7ECRlCfcQZjL 3D5w==
MIME-Version: 1.0
X-Received: by 10.152.8.115 with SMTP id q19mr26604117laa.16.1381147427344; Mon, 07 Oct 2013 05:03:47 -0700 (PDT)
Received: by 10.114.200.176 with HTTP; Mon, 7 Oct 2013 05:03:47 -0700 (PDT)
Date: Mon, 7 Oct 2013 17:33:47 +0530
Message-ID: <CAO_L_qAhn4Y8e6w-6R-Nwmwwh3=KTS1CgNdwchupjMAPrLHc6g@mail.gmail.com>
From: Ramakanth Josyula <ramakanthjosyula@gmail.com>
To: dhcwg@ietf.org, pim@ietf.org
Content-Type: multipart/alternative; boundary=001a11c34f5cca181f04e825711a
Cc: josyular@brocade.com
Subject: [pim] Review request - draft-josyula-dhc-multicast - DHCP Option for IPTV source addresses
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, 07 Oct 2013 12:03:54 -0000

--001a11c34f5cca181f04e825711a
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I have submitted the below internet draft proposing a new DHCP option for
IPTV source addresses.

http://www.ietf.org/internet-drafts/draft-josyula-dhc-multicast-02.txt

I would request you to review this document and provide the comments on
standardizing the same.

Please guide me through the process if I miss anything with respect to the
process of the review.


Thanks and regards,

Ramakanth.


*Below is the brief introduction about the background and the benefits of
the proposed option :*


*Back ground : *



IPTV Solution is widely integrated as part of the broadband networks in
triple/multi play solutions. In many cases this service is run by
delivering multicast streams to the IP hosts/Set top boxes connected to the
home gateways.  IGMP protocol in IPv4 networks and   MLD protocol in IPv6
networks are commonly used for requesting these  multicast streams from the
nearest router connected via an access network. By using the IGMP version-3
in IPv4 networks and MLD version-2 in IPv6 networks, the hosts can request
multicast streams from the specific set of multicast sources.

The proposed option is intended to supply all the available IPv4 or IPv6
source addresses from which the multicast hosts can request and receive the
multicast streams.

 *Benefits of implementing this option :*

- It provides an effective method for maintaining and updating the
multicast source address information to every multicast host in the network
as per their individual SLAs.

- Intermediate access nodes can snoop this option from the DHCP messages to
extend the its multicast services like : Authentication of multicast users,
integrating non-source aware multicast clients etc.

- Convergence of IPTV services from different users can be achieved at the
user level irrespective of the multicast transmitting technologies used in
the network. For example, any service provider who manages the aggregation
and access networks can receive the multicast streams from different
sources/networks (may not be under their own administration) and feed them
to their access networks.

- The subscribers can easily validate the quality of the service offered by
different IPTV sources dynamically and switch to the interested source as
per their own set of requirements.

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

<div dir=3D"ltr"><p class=3D"">Hi,</p>

<p class=3D"">I have submitted the below internet draft proposing a new
DHCP option for IPTV source addresses.<br></p><p class=3D""></p>

<p class=3D""><a href=3D"http://www.ietf.org/internet-drafts/draft-josyula-=
dhc-multicast-02.txt">http://www.ietf.org/internet-drafts/draft-josyula-dhc=
-multicast-02.txt</a><br></p><p class=3D""></p>

<p class=3D"">I would request you to review this document and provide
the comments on standardizing the same.<br></p><p class=3D""></p>

<p class=3D"">Please guide me through the process if I miss anything
with respect to the process of the review.<br></p><p class=3D""></p>

<p class=3D""><br></p><p class=3D"">Thanks and regards,<br></p><p class=3D"=
"></p>

<p class=3D"">Ramakanth.</p>

<p class=3D""><br></p>

<p class=3D""><b>Below is the brief introduction about the background and
the benefits of the proposed option :</b></p>

<p class=3D""><br></p>

<p class=3D""><b><u>Back ground : </u></b></p>

<p class=3D"">=A0</p>

<p class=3D"">IPTV Solution is widely integrated as part of the broadband
networks in triple/multi play solutions. In many cases this service is run =
by
delivering multicast streams to the IP hosts/Set top boxes connected to the
home gateways.=A0 IGMP protocol in IPv4 networks and=A0=A0 MLD
protocol in IPv6 networks are commonly used for requesting these=A0
multicast streams from the nearest router connected via an access network. =
By
using the IGMP version-3 in IPv4 networks and MLD version-2 in IPv6 network=
s,
the hosts can request multicast streams from the specific set of multicast
sources. </p>

<p class=3D"">The proposed option is intended to supply all the available
IPv4 or IPv6 source addresses from which the multicast hosts can request an=
d
receive the multicast streams.<br></p><p class=3D""></p>

<p class=3D"">=A0<b><u>Benefits of implementing this option :</u></b></p>

<p class=3D"">- It provides an effective method for
maintaining and updating the multicast source address information to every
multicast host in the network as per their individual SLAs.</p><p class=3D"=
"></p>

<p class=3D"">- Intermediate access nodes can snoop this
option from the DHCP messages to extend the its multicast services like :
Authentication of multicast users, integrating non-source aware multicast
clients etc.<br></p><p class=3D""></p>

<p class=3D"">- Convergence of IPTV services from different
users can be achieved at the user level irrespective of the multicast
transmitting technologies used in the network. For example, any service
provider who manages the aggregation and access networks can
receive the multicast streams from different sources/networks (may not be u=
nder
their own administration) and feed them to their access networks.=A0</p><p =
class=3D""></p>

<p class=3D"">- The subscribers can easily validate the
quality of the service offered by different IPTV sources dynamically and sw=
itch
to the interested source as per their own set of requirements.</p>

<p class=3D"">=A0</p></div>

--001a11c34f5cca181f04e825711a--

From internet-drafts@ietf.org  Mon Oct  7 05:31:46 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1098721E8090; Mon,  7 Oct 2013 05:31:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.559
X-Spam-Level: 
X-Spam-Status: No, score=-102.559 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nvums5mdHAFQ; Mon,  7 Oct 2013 05:31:45 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CBF021F9FE7; Mon,  7 Oct 2013 05:31:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131007123145.16131.30691.idtracker@ietfa.amsl.com>
Date: Mon, 07 Oct 2013 05:31:45 -0700
Cc: pim@ietf.org
Subject: [pim] I-D Action: draft-ietf-pim-explicit-tracking-08.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 07 Oct 2013 12:31:46 -0000

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

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

Abstract:
   This document describes the IGMP/MLD-based explicit membership
   tracking function for multicast routers and IGMP/MLD proxy devices
   supporting IGMPv3/MLDv2.  The explicit membership tracking function
   contributes to saving network resources and shortening leave latency.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pim-explicit-tracking

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-pim-explicit-tracking-08

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pim-explicit-tracking-08


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From stig@venaas.com  Mon Oct  7 08:57:04 2013
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 2B97D21E80BA for <pim@ietfa.amsl.com>; Mon,  7 Oct 2013 08:57:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.3
X-Spam-Level: 
X-Spam-Status: No, score=-101.3 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rbSoLbnWSrOB for <pim@ietfa.amsl.com>; Mon,  7 Oct 2013 08:57:03 -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 2C06921E81B2 for <pim@ietf.org>; Mon,  7 Oct 2013 08:55:51 -0700 (PDT)
Received: from [10.21.144.13] (128-107-239-234.cisco.com [128.107.239.234]) by ufisa.uninett.no (Postfix) with ESMTPSA id 0D4927FD9 for <pim@ietf.org>; Mon,  7 Oct 2013 17:55:48 +0200 (CEST)
Message-ID: <5252DB50.3040105@venaas.com>
Date: Mon, 07 Oct 2013 09:03:28 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
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] Agenda for IETF 88
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, 07 Oct 2013 15:57:04 -0000

Hi

We've been scheduled for a meeting Friday afternoon. Please plan your
travels accordingly. Our slot may still change, but unless there are
conflicts with other meetings in the Friday afternoon session, we're
likely to remain in that session.

See the draft agenda at
https://datatracker.ietf.org/meeting/88/agenda.html

Please email Mike and me with presentation requests.

Stig

From internet-drafts@ietf.org  Tue Oct  8 15:18:07 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 203F621E80AD; Tue,  8 Oct 2013 15:18:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level: 
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rI1sPr0CerX5; Tue,  8 Oct 2013 15:18:06 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A09A121E80AE; Tue,  8 Oct 2013 15:18:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131008221803.28645.52829.idtracker@ietfa.amsl.com>
Date: Tue, 08 Oct 2013 15:18:03 -0700
Cc: pim@ietf.org
Subject: [pim] I-D Action: draft-ietf-pim-hierarchicaljoinattr-00.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Oct 2013 22:18:07 -0000

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

	Title           : Hierarchical Join/Prune Attributes
	Author(s)       : Stig Venaas
                          Isidor Kouvelas
                          Jesus Arango
	Filename        : draft-ietf-pim-hierarchicaljoinattr-00.txt
	Pages           : 7
	Date            : 2013-10-03

Abstract:
   This document defines a hierachical method of encoding Join
   attributes, providing a more efficient encoding when the same
   attribute values need to be specified for multiple sources in a PIM
   Join/Prune message.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pim-hierarchicaljoinattr

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-pim-hierarchicaljoinattr-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From ramakanthjosyula@gmail.com  Sun Oct  6 22:37:29 2013
Return-Path: <ramakanthjosyula@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 B944221E8161; Sun,  6 Oct 2013 22:37:29 -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, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cLMeXxuQdR4O; Sun,  6 Oct 2013 22:37:29 -0700 (PDT)
Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::235]) by ietfa.amsl.com (Postfix) with ESMTP id 658C921E815E; Sun,  6 Oct 2013 22:37:28 -0700 (PDT)
Received: by mail-lb0-f181.google.com with SMTP id u14so5198726lbd.12 for <multiple recipients>; Sun, 06 Oct 2013 22:37:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=Z9nnS65WGltABmq9/L7ZXJUJ8JIpewfQBoMzlRZWeEE=; b=cjKrjPuMdoi/oWo0AVmxxgnm4ghTE8hJ+UFQv441UFTUG3PAxULnLH8m3L2FSOsauK jwHQljr26EGk4ydNVC5qBLZcdDXjvw1ZKM5sjZTQJ4djUwCZkusiPMPuU+BrEVUrO5a9 oX92HvoSUkoxnR1KkY7b/FtF6yZNeL+06mVIsXs00lDHfrrnj6URae79BvYfR5ZThoG+ ELqQSIa5eeE7dKFYyYa/tfUp9wFkmsgBTh/AxNLT5SaK2+ifovNrCS/g9z809LE+MuCt EnJuL5MFBFaFWyrbPfpSUE4zdqVbat4ZBt61TTJp51k78OJj95X18xXpZ5vNinsD/n2r fAYA==
MIME-Version: 1.0
X-Received: by 10.112.0.242 with SMTP id 18mr23662390lbh.18.1381124247177; Sun, 06 Oct 2013 22:37:27 -0700 (PDT)
Received: by 10.114.200.176 with HTTP; Sun, 6 Oct 2013 22:37:27 -0700 (PDT)
Date: Mon, 7 Oct 2013 11:07:27 +0530
Message-ID: <CAO_L_qA6ed+jGWA96r5K68tP8chFuQnG_QNGZT51bqfmyuNNCQ@mail.gmail.com>
From: Ramakanth Josyula <ramakanthjosyula@gmail.com>
To: dhcwg@ietf.org, pim@ietf.org
Content-Type: multipart/alternative; boundary=f46d042ac0e824d1a904e8200c1d
X-Mailman-Approved-At: Tue, 08 Oct 2013 18:48:05 -0700
Cc: josyular@brocade.com
Subject: [pim] Review request - draft-josyula-dhc-multicast - DHCP Option for IPTV source addresses
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, 07 Oct 2013 05:38:02 -0000

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

Hi all,



I have submitted the below internet draft proposing a new DHCP option for
IPTV source addresses.



http://www.ietf.org/internet-drafts/draft-josyula-dhc-multicast-02.txt



I would request you to review this document and provide the comments on
standardizing the same.



Please guide me through the process if I miss anything with respect to the
process of the review.



Thanks and regards,

Ramakanth.





*Below is the brief introduction about the background and the benefits of
the proposed option :*



*Back ground : *



IPTV Solution is widely integrated as part of the broadband networks in
triple/multi play solutions. In many cases this service is run by
delivering multicast streams to the IP hosts/Set top boxes connected to the
home gateways.  IGMP protocol in IPv4 networks and   MLD protocol in IPv6
networks are commonly used for requesting these  multicast streams from the
nearest router connected via an access network. By using the IGMP version-3
in IPv4 networks and MLD version-2 in IPv6 networks, the hosts can request
multicast streams from the specific set of multicast sources.



The proposed option is intended to supply all the available IPv4 or IPv6
source addresses from which the multicast hosts can request and receive the
multicast streams.



*Benefits of implementing this option :*



   - It provides an effective method for maintaining and updating the
multicast source address information to every multicast host in the network
as per their individual SLAs.



   - Intermediate access nodes can snoop this option from the DHCP messages
to extend the its multicast services like : Authentication of multicast
users, integrating non-source aware multicast clients etc.



   - Convergence of IPTV services from different users can be achieved at
the user level irrespective of the multicast transmitting technologies used
in the network. For example, any service provider who manages the
aggregation

     and access networks can receive the multicast streams from different
sources/networks (may not be under their own administration) and feed them
to their access networks.



   - The subscribers can easily validate the quality of the service offered
by different IPTV sources dynamically and switch to the interested source
as per their own set of requirements.

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

<div dir=3D"ltr"><p class=3D"">Hi all,</p>

<p class=3D"">=A0</p>

<p class=3D"">I have submitted the below internet draft proposing a new
DHCP option for IPTV source addresses. </p>

<p class=3D"">=A0</p>

<p class=3D""><a href=3D"http://www.ietf.org/internet-drafts/draft-josyula-=
dhc-multicast-02.txt">http://www.ietf.org/internet-drafts/draft-josyula-dhc=
-multicast-02.txt</a></p>

<p class=3D"">=A0</p>

<p class=3D"">I would request you to review this document and provide
the comments on standardizing the same.</p>

<p class=3D"">=A0</p>

<p class=3D"">Please guide me through the process if I miss anything
with respect to the process of the review.</p>

<p class=3D"">=A0</p>

<p class=3D"">Thanks and regards,</p>

<p class=3D"">Ramakanth.</p>

<p class=3D"">=A0</p>

<p class=3D"">=A0</p>

<p class=3D""><b>Below is the brief introduction about the background and
the benefits of the proposed option :</b></p>

<p class=3D"">=A0</p>

<p class=3D""><b><u>Back ground : </u></b></p>

<p class=3D"">=A0</p>

<p class=3D"">IPTV Solution is widely integrated as part of the broadband
networks in triple/multi play solutions. In many cases this service is run =
by
delivering multicast streams to the IP hosts/Set top boxes connected to the
home gateways.=A0 IGMP protocol in IPv4 networks and=A0=A0 MLD
protocol in IPv6 networks are commonly used for requesting these=A0
multicast streams from the nearest router connected via an access network. =
By
using the IGMP version-3 in IPv4 networks and MLD version-2 in IPv6 network=
s,
the hosts can request multicast streams from the specific set of multicast
sources. </p>

<p class=3D"">=A0</p>

<p class=3D"">The proposed option is intended to supply all the available
IPv4 or IPv6 source addresses from which the multicast hosts can request an=
d
receive the multicast streams.</p>

<p class=3D"">=A0</p>

<p class=3D""><b><u>Benefits of implementing this option :</u></b></p>

<p class=3D"">=A0</p>

<p class=3D"">=A0=A0 - It provides an effective method for
maintaining and updating the multicast source address information to every
multicast host in the network as per their individual SLAs.</p>

<p class=3D"">=A0</p>

<p class=3D"">=A0=A0 - Intermediate access nodes can snoop this
option from the DHCP messages to extend the its multicast services like :
Authentication of multicast users, integrating non-source aware multicast
clients etc.</p>

<p class=3D"">=A0</p>

<p class=3D"">=A0=A0 - Convergence of IPTV services from different
users can be achieved at the user level irrespective of the multicast
transmitting technologies used in the network. For example, any service
provider who manages the aggregation =A0=A0</p>

<p class=3D"">=A0=A0=A0=A0=A0and access networks can
receive the multicast streams from different sources/networks (may not be u=
nder
their own administration) and feed them to their access networks.=A0 </p>

<p class=3D"">=A0=A0</p>

<p class=3D"">=A0=A0=A0- The subscribers can easily validate the
quality of the service offered by different IPTV sources dynamically and sw=
itch
to the interested source as per their own set of requirements.</p>

<p class=3D"">=A0</p></div>

--f46d042ac0e824d1a904e8200c1d--

From mike.mcbride@ericsson.com  Mon Oct  7 16:26:43 2013
Return-Path: <mike.mcbride@ericsson.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6DA721E81C4 for <pim@ietfa.amsl.com>; Mon,  7 Oct 2013 16:26:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.523
X-Spam-Level: 
X-Spam-Status: No, score=-2.523 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qR4dAIiaHFNU for <pim@ietfa.amsl.com>; Mon,  7 Oct 2013 16:26:37 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 898AE21E81B7 for <pim@ietf.org>; Mon,  7 Oct 2013 16:26:36 -0700 (PDT)
X-AuditID: c618062d-b7fda8e0000024c6-a3-5253432b1555
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id F0.AC.09414.B2343525; Tue,  8 Oct 2013 01:26:35 +0200 (CEST)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.02.0328.009; Mon, 7 Oct 2013 19:26:26 -0400
From: Mike McBride <mike.mcbride@ericsson.com>
To: "pim@ietf.org" <pim@ietf.org>
Thread-Topic: McBride change of affiliation
Thread-Index: Ac7Ds7jNAqVGMVL8RWOAv3V4D4yl3g==
Date: Mon, 7 Oct 2013 23:26:26 +0000
Message-ID: <6F5149063CE40341BE7953160A93C5A0D7A151@eusaamb109.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: multipart/alternative; boundary="_000_6F5149063CE40341BE7953160A93C5A0D7A151eusaamb109ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKLMWRmVeSWpSXmKPExsUyuXSPn662c3CQwbkFVhZfHt5kdmD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxrFF7gXLRSrOLOpna2D8I9jFyMkhIWAicfnoIWYIW0ziwr31 bCC2kMBRRompu3m7GLmA7GWMEhv/97CCJNgE9CROL2wGs0UEFCXa57aA2cICahK7m6cwQ8S1 JQ793s8EYetJbP++G8jm4GARUJG4ctYaJMwr4C2x+OBudhCbEWjv91NrwMqZBcQlbj2ZzwRx j4DEkj3noW4TlXj5+B8rhK0sseTJfhaI+nyJDa9WM0LMFJQ4OfMJywRGoVlIRs1CUjYLSRlE XEdiwe5PbBC2tsSyha+ZYewzBx4zIYsvYGRfxchRWpxalptuZLCJERj0xyTYdHcw7nlpeYhR moNFSZz3y1vnICGB9MSS1OzU1ILUovii0pzU4kOMTBycUg2My00Mnj2peFZTucdj8k3tZtk/ PPei3y4yeGzHJ6v4WIR18omnxvwXHjxY8Dbtimr3p+afx3drHdFTZVo0ZdKd21pc6cd6rbym hWzYqrF934kP3HVrYkM32FquX3AhsM697DWP18bHATyHjSZPOlG/PElO/piJ6W3vPhdV+9yZ G2/tyWdafmzyZiWW4oxEQy3mouJEAKXTnQJIAgAA
X-Mailman-Approved-At: Tue, 08 Oct 2013 18:48:05 -0700
Subject: [pim] McBride change of affiliation
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, 07 Oct 2013 23:26:44 -0000

--_000_6F5149063CE40341BE7953160A93C5A0D7A151eusaamb109ericsso_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Per request from our illustrious AD, for transparency reasons, please note =
that my affiliation has changed to Ericsson. No, I don't have career ADD. O=
k, maybe a little.

See you in Vancouver.

mike

--_000_6F5149063CE40341BE7953160A93C5A0D7A151eusaamb109ericsso_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Per request from our illustrious AD, for transparenc=
y reasons, please note that my affiliation has changed to Ericsson. No, I d=
on&#8217;t have career ADD. Ok, maybe a little.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">See you in Vancouver. <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">mike<o:p></o:p></p>
</div>
</body>
</html>

--_000_6F5149063CE40341BE7953160A93C5A0D7A151eusaamb109ericsso_--

From stig@venaas.com  Wed Oct  9 12:47:25 2013
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 3F4AE21E819A for <pim@ietfa.amsl.com>; Wed,  9 Oct 2013 12:47:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.949
X-Spam-Level: 
X-Spam-Status: No, score=-101.949 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DcauKZs4cH6z for <pim@ietfa.amsl.com>; Wed,  9 Oct 2013 12:47:24 -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 E765C21E8191 for <pim@ietf.org>; Wed,  9 Oct 2013 12:47:19 -0700 (PDT)
Received: from [10.33.12.93] (128-107-239-234.cisco.com [128.107.239.234]) by ufisa.uninett.no (Postfix) with ESMTPSA id EB4777FB9 for <pim@ietf.org>; Wed,  9 Oct 2013 21:47:17 +0200 (CEST)
Message-ID: <5255B2C3.4090705@venaas.com>
Date: Wed, 09 Oct 2013 12:47:15 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: pim@ietf.org
References: <20131007123145.16131.30691.idtracker@ietfa.amsl.com>
In-Reply-To: <20131007123145.16131.30691.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [pim] I-D Action: draft-ietf-pim-explicit-tracking-08.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: Wed, 09 Oct 2013 19:47:25 -0000

I've now requested publication of this document. I'm the shepherd. We've
had 3 last calls and I believe all comments/concerns have been
addressed. But if anyone still has any concerns, let me know. It will
also go to IETF last call later.

Stig

From Siva.Kollipara@alcatel-lucent.com  Thu Oct 10 09:13:24 2013
Return-Path: <Siva.Kollipara@alcatel-lucent.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BF3111E81A8 for <pim@ietfa.amsl.com>; Thu, 10 Oct 2013 09:13:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jjcnymeXe+MT for <pim@ietfa.amsl.com>; Thu, 10 Oct 2013 09:13:19 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 00A6D21E809B for <pim@ietf.org>; Thu, 10 Oct 2013 09:13:16 -0700 (PDT)
Received: from us70uusmtp4.zam.alcatel-lucent.com (h135-5-2-66.lucent.com [135.5.2.66]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id r9AGDFfM013818 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <pim@ietf.org>; Thu, 10 Oct 2013 11:13:15 -0500 (CDT)
Received: from US70TWXCHHUB03.zam.alcatel-lucent.com (us70twxchhub03.zam.alcatel-lucent.com [135.5.2.35]) by us70uusmtp4.zam.alcatel-lucent.com (GMO) with ESMTP id r9AGCxOZ003491 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <pim@ietf.org>; Thu, 10 Oct 2013 12:13:15 -0400
Received: from US70UWXCHMBA03.zam.alcatel-lucent.com ([169.254.9.66]) by US70TWXCHHUB03.zam.alcatel-lucent.com ([135.5.2.35]) with mapi id 14.02.0247.003; Thu, 10 Oct 2013 12:13:03 -0400
From: "Kollipara, Siva (Siva)" <Siva.Kollipara@alcatel-lucent.com>
To: "pim@ietf.org" <pim@ietf.org>
Thread-Topic: I-D Action: draft-ietf-pim-hierarchicaljoinattr-00.txt
Thread-Index: AQHOxdOYRCIRdDRUO0aCyfKQipncNg==
Date: Thu, 10 Oct 2013 16:13:03 +0000
Message-ID: <0AC308EE21CA5B428A35736A5B851D1F15D674@US70UWXCHMBA03.zam.alcatel-lucent.com>
References: <mailman.15.1381345206.16741.pim@ietf.org>
In-Reply-To: <mailman.15.1381345206.16741.pim@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.5.27.16]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Subject: Re: [pim] I-D Action: draft-ietf-pim-hierarchicaljoinattr-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: Thu, 10 Oct 2013 16:13:24 -0000

Offline discussions on this draft: (for the benefit of others)

---

On 10/9/2013 9:29 AM, Kollipara, Siva (Siva) wrote:
> Hi Stig,
>
> Thanks for the response. Your plan sounds good. I believe your plan is in=
 line with the optional idea I mentioned. I thought about the following poi=
nts with this idea:
>
> 1) If G specifies a "Don't-Inherit-Attrib", does that mean S can still in=
herit that attribute from UN or that UN attribute is totally invisible to S=
?

I think the meaning should simply be not to inherit the attribute, so it sh=
ould be as if it was not specified higher up in the hierarchy. So if Don't =
Inherit is present in G specifying that attribute A should not be inherited=
, then if UN has attribute A, then that A should not apply to G and below. =
It is blocking A from being inherited down the tree to G and below.

Note that sources below G could have attribute A specified still if needed =
(but it's not inherited). Also attribute A could be present for G, but then=
 there is no point in Don't Inherit since it would override the attribute A=
 if present in UN.

> 2) if S specified a "Don't-inherit-attrib", does that apply to not inheri=
ting from G or from UN or both?

If attribute A is specified in G, then that A is inherited for the sources =
S (independent of whether A is present (or not) with some value in UN). If =
A is present only in UN, then it is inherited down. It does not matter how =
it is inherited by S, if Don't Inherit is specified for attribute A, then i=
t is simply not inherited.

> A bitmask specifying the following:
> - don't inherit from G
> - don't inherit from UN
> This allows the S to not inherit from both or one of them specifically=20
> (the case of bypass G and inherit from UN being the useful case). The=20
> same mask can also be used at G level to prevent it from inheriting=20
> from UN (although the G bit is don't-care)
>
> I see the flexibility in saying that "once G un-inherits an attribute, S =
doesn't see that attribute at all", but I also flexibility in allowing that=
 to happen.
>
> Thoughts?

I think this is too complicated. I think all we need is to basically clear =
the attribute for an S or G. Attributes specified for G apply to all source=
s for G, so if you clear it for G, then I think it should also be cleared f=
or all sources. If no sources under G should have it, just clear it for G (=
by using Don't Inherit for G). If most of the sources should have the attri=
bute, then you can clear it for the few sources that should not have it. If=
 most of the sources should not have the attribute, you can clear it for G,=
 and then set the attribute again for the few sources that should have it.

Don't you think this is sufficient? It is a bit hard to explain this I thin=
k, not sure whether I'm able to convey my idea well. I'll try to think of a=
 good way to describe it in the draft, as it is important that the idea is =
clear.

> I hope it is ok that I am brainstorming with you on this topic.

Sure, but good if you can comment on the mailing list actually. The discuss=
ion should be of interest in the pim wg in general.

Stig

> Regards,
> Siva
>
>> -----Original Message-----
>> From: Stig Venaas [mailto:stig@cisco.com]
>> Sent: Tuesday, October 08, 2013 5:58 PM
>> To: Siva.Kollipara@alcatel-lucent.com
>> Cc: kouvelas@cisco.com; jearango@cisco.com
>> Subject: Re: draft-ietf-pim-hierarchicaljoinattr-00.txt comments
>>
>> Hi Siva
>>
>> On 08.10.2013 17:11, Kollipara, Siva (Siva) wrote:
>>> Hi Stig, Isidor, Jesus
>>>
>>> Nice optimization. I wanted to point out the following case, and it
>> would be beneficial to include it in the draft as well.
>>>
>>> The draft suggested the following:
>>>
>>> UNAddr [UN-JPAttribute]
>>> |
>>> |-G1 [G1-JPAttribute]
>>> |  |
>>> |  |-S1 [S1-JPAttribute]
>>> |  |-S2
>>> |
>>> |-G2
>>> |  |-S3
>>> |  |-S4
>>>
>>> In the above example: S2 inherits G1-JPAttribute and S3/S4 inherit
>> UN-JPAttribute.
>>>
>>> One of the impact of this is that if previously, let's say S2 didn't
>> need a JP attribute, then with hierarchical JP attributes (S2,G1)=20
>> will have to sent in a separate JP message. In essence, only those=20
>> SGs that require an base common set of JP attributes can be bunched=20
>> in the same JP message. What previously could've been sent as 1 JP=20
>> message may now have to split into multiple JP messages. For example:=20
>> if all SGs except one doesn't require/use particular JP attribute,=20
>> then its best to separate the SG into another JP message. Ofcourse,=20
>> the implementation can choose to use regular JP Attributes despite=20
>> over hierarchical JP attributes.
>>>
>>> Optionally, we could also indicate that a SG *should not* inherit an
>> attribute from G/UN. Although, I presume that complicates things=20
>> further.
>>>
>>> Please let me know your thoughts.
>>
>> Thanks, I'm planning to do this actually. I've been thinking about a=20
>> couple of ways of doing this and will add it to the next draft=20
>> revision.
>> Then we'll see next IETF whether people are OK with the additional=20
>> flexibility/complexity.
>>
>> I think what I would do is a new attribute type that can contain=20
>> types to remove. Like a don't inherit attribute where the value is a=20
>> list of attribute types to not inherit. You could put it into say S3=20
>> so that it is not inherited just for S3. Or if you put it in say G2=20
>> you could prevent inheriting for all under G2...
>>
>> Stig
>>
>>> Regards,
>>> Siva
>>>
>>>>
>>>> -----Original Message-----
>>>> From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf
>> Of
>>>> internet-drafts@ietf.org
>>>> Sent: Tuesday, October 08, 2013 3:18 PM
>>>> To: i-d-announce@ietf.org
>>>> Cc: pim@ietf.org
>>>> Subject: [pim] I-D Action: draft-ietf-pim-hierarchicaljoinattr-
>> 00.txt
>>>>
>>>>
>>>> A New Internet-Draft is available from the on-line Internet-Drafts=20
>>>> directories.
>>>>    This draft is a work item of the Protocol Independent Multicast=20
>>>> Working Group of the IETF.
>>>>
>>>> 	Title           : Hierarchical Join/Prune Attributes
>>>> 	Author(s)       : Stig Venaas
>>>>                             Isidor Kouvelas
>>>>                             Jesus Arango
>>>> 	Filename        : draft-ietf-pim-hierarchicaljoinattr-00.txt
>>>> 	Pages           : 7
>>>> 	Date            : 2013-10-03
>>>>
>>>> Abstract:
>>>>      This document defines a hierachical method of encoding Join
>>>>      attributes, providing a more efficient encoding when the same
>>>>      attribute values need to be specified for multiple sources in=20
>>>> a
>> PIM
>>>>      Join/Prune message.
>>>>
>>>>
>>>> The IETF datatracker status page for this draft is:
>>>> https://datatracker.ietf.org/doc/draft-ietf-pim-hierarchicaljoinatt
>>>> r
>>>>
>>>> There's also a htmlized version available at:
>>>> http://tools.ietf.org/html/draft-ietf-pim-hierarchicaljoinattr-00
>>>>
>>>>
>>>> Please note that it may take a couple of minutes from the time of=20
>>>> submission until the htmlized version and diff are available at=20
>>>> tools.ietf.org.
>>>>
>>>> Internet-Drafts are also available by anonymous FTP at:
>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>
>>>> _______________________________________________
>>>> pim mailing list
>>>> pim@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/pim


From mmcbride7@gmail.com  Mon Oct 14 14:11:33 2013
Return-Path: <mmcbride7@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 D84D621F9048 for <pim@ietfa.amsl.com>; Mon, 14 Oct 2013 14:11:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SxOip+IrnQgO for <pim@ietfa.amsl.com>; Mon, 14 Oct 2013 14:11:33 -0700 (PDT)
Received: from mail-pa0-x231.google.com (mail-pa0-x231.google.com [IPv6:2607:f8b0:400e:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id B724E21F8D90 for <pim@ietf.org>; Mon, 14 Oct 2013 14:11:27 -0700 (PDT)
Received: by mail-pa0-f49.google.com with SMTP id ld10so8038851pab.36 for <pim@ietf.org>; Mon, 14 Oct 2013 14:11:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=8RjxfLtYABmj/W1lx3Nxi3TGCnh318Pm53SvvvwRKoI=; b=dVOHpN6YImK5Sz8abKocbEtlORjMgmPQOIziHufZvXCtfqKTBqNUKxQyxX/qXwRDjq 6dsIY3dYbgdmXtyb1+De0RNSi1vtQINhNwcnQTB5Kbsd1eNFI3GVaQn486UHhUPM3YdU 9JBBSUeF6SAQCW0+7TF00ZvfuWeTyRduO+ac1d4/DXAv1LvXG5SdYmmOl5nqm4Kn8KNf BVB7kV9ggz97+rReDjYjQOP5+bANplHO/DTAOfzTS7ZPpuNWuxVgLrIZjMYCx2mNjEUJ C/7G6o44HBk4wyW0UIz1i2gpgRDs+cjgenD+8uaufMwHhALae8nhwybRQDvU/RrQjai4 Klag==
MIME-Version: 1.0
X-Received: by 10.66.65.108 with SMTP id w12mr2246pas.183.1381785076154; Mon, 14 Oct 2013 14:11:16 -0700 (PDT)
Received: by 10.68.65.198 with HTTP; Mon, 14 Oct 2013 14:11:16 -0700 (PDT)
Date: Mon, 14 Oct 2013 14:11:16 -0700
Message-ID: <CAL3FGfwoVE0CPTCQynPdN8P77wo0-TBh=TyzE__qextO3TjfZw@mail.gmail.com>
From: Mike McBride <mmcbride7@gmail.com>
To: "pim@ietf.org" <pim@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [pim] VRRP and PIM
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Oct 2013 21:11:34 -0000

This begins a two week poll to gauge interest with working on vrrp
related work within the pim wg. We have a couple of vrrp related
drafts being proposed for adoption. As discussed in Berlin, we've had
some interest on this work in the past but no hands of support went up
in Berlin. Before making any decisions with regards to the two
proposed drafts, Stig and I would like to get a pulse of current
interest.

If you are in favor of this work in pim please respond on the list. If
you are not in favor of this work in pim please respond on the list.

thanks,
mike

Here are the notes from our meeting in Berlin:

draft-zhou-pim-vrrp-01 adoption discussion (Mike)
=================================================
Adoption currently on hold. Authors of
draft-xu-pim-drpriority-auto-adjustment-04 would like wg to consider a
merge because there is an overlap particularly with aligning vrrp with
pim. We will have a brief overview of both and discuss how to proceed.

draft-xu-pim-drpriority-auto-adjustment wasn't accepted as a wg item a
couple of years ago. No strong interest in the group.

The WG needs to decide if its interested in this work, the earlier
draft. If not we proceed with draft-zhou-pim-vrrp adoption call if
there is interest. If interest we either:

-Adopt and progress both drafts. One as a problem statement, the other
as protocol work.
-Reference earlier draft in draft-zhou-pim-vrrp
-Merge drafts into new draft

Any interest in VRRP in general? No hands. Will take it to the list
and see if there is any interest. If no one but the authors care we
won't work it. 4 in favor last time in addition to authors.

Note: the usual suspects were not in the room primarily due to
conflicting WG meetings.

From adrian@olddog.co.uk  Wed Oct 16 13:41:33 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86F5C21F9D35 for <pim@ietfa.amsl.com>; Wed, 16 Oct 2013 13:41:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.563
X-Spam-Level: 
X-Spam-Status: No, score=-2.563 tagged_above=-999 required=5 tests=[AWL=0.036,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jqDknyEuzrNv for <pim@ietfa.amsl.com>; Wed, 16 Oct 2013 13:41:27 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 6895121F9CAC for <pim@ietf.org>; Wed, 16 Oct 2013 13:41:26 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r9GKfP4i028041;  Wed, 16 Oct 2013 21:41:25 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r9GKfO3r028030 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 16 Oct 2013 21:41:24 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <draft-ietf-pim-explicit-tracking.all@tools.ietf.org>
Date: Wed, 16 Oct 2013 21:41:23 +0100
Message-ID: <019201cecab0$14113550$3c339ff0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac7KsASHDK4uzFGgRkWNFbsOxDRzpA==
Content-Language: en-gb
Cc: pim@ietf.org
Subject: [pim] AD review draft-ietf-pim-explicit-tracking
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Oct 2013 20:41:33 -0000

Hi,

Thank you for this document. I have done my usual AD review to find any
issues before taking the document to IETF last call and IESG evaluation.

In this case I have only a few minor issues that I have captured below.
Since they are so small, I will enter them as IETF last call comments
and we don't need to hold the work up any further at this time.

Thanks,
Adrian

===

I think your core reference [6] is supposed to refer to RFC 2236 for the
core definition of IGMPv2. That RFC certainly matches the name of the
document you have given.

[Hint: idnits is your friend!]

---

idnits complains about the 2119 boiler plate because you are missing a
space in
  "RECOMMENDED","MAY",

---

Section 1 contains a clumsy sentence

   To alleviate the problem, unsolicited
   report messages are transmitted the [Robustness Variable] times
   (defined in [2][3]).

How about

   To alleviate this problem, unsolicited
   report messages are retransmitted a number of times according to the
   value of the [Robustness Variable] defined in [2] and [3].

---

Section 3

While *everyone* knows what S and G stand for, you should still say.


From iesg-secretary@ietf.org  Wed Oct 16 13:46:00 2013
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8DFC21F9CA8; Wed, 16 Oct 2013 13:46:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.431
X-Spam-Level: 
X-Spam-Status: No, score=-102.431 tagged_above=-999 required=5 tests=[AWL=0.169, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zMaZQnIHDz28; Wed, 16 Oct 2013 13:46:00 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7988E21F9DCA; Wed, 16 Oct 2013 13:45:57 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p2
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <20131016204557.16404.47618.idtracker@ietfa.amsl.com>
Date: Wed, 16 Oct 2013 13:45:57 -0700
Cc: pim@ietf.org
Subject: [pim] Last Call: <draft-ietf-pim-explicit-tracking-08.txt> (IGMP/MLD-Based	Explicit Membership Tracking Function for Multicast Routers) to	Proposed Standard
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: ietf@ietf.org
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, 16 Oct 2013 20:46:01 -0000

The IESG has received a request from the Protocol Independent Multicast
WG (pim) to consider the following document:
- 'IGMP/MLD-Based Explicit Membership Tracking Function for Multicast
   Routers'
  <draft-ietf-pim-explicit-tracking-08.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2013-11-06 (this is a 3 week last call to allow
extra time as people are preparing for IETF-88). Exceptionally, comments
may be sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract

   This document describes the IGMP/MLD-based explicit membership
   tracking function for multicast routers and IGMP/MLD proxy devices
   supporting IGMPv3/MLDv2.  The explicit membership tracking function
   contributes to saving network resources and shortening leave latency.


The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-pim-explicit-tracking/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-pim-explicit-tracking/ballot/


No IPR declarations have been submitted directly on this I-D.

From adrian@olddog.co.uk  Wed Oct 16 13:50:54 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9C0621F9985; Wed, 16 Oct 2013 13:50:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.563
X-Spam-Level: 
X-Spam-Status: No, score=-2.563 tagged_above=-999 required=5 tests=[AWL=0.036,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uuUP1mVyyQ62; Wed, 16 Oct 2013 13:50:42 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 319B221F995B; Wed, 16 Oct 2013 13:50:41 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r9GKoeVZ030581;  Wed, 16 Oct 2013 21:50:40 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r9GKocFn030500 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 16 Oct 2013 21:50:39 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
Date: Wed, 16 Oct 2013 21:50:37 +0100
Message-ID: <01a101cecab1$5ee6f6e0$1cb4e4a0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac7KsVqD5Pwz8Vn0TmSmjwGpaJrDqw==
Content-Language: en-gb
Cc: pim@ietf.org
Subject: Re: [pim] Last Call: <draft-ietf-pim-explicit-tracking-08.txt>	(IGMP/MLD-Based	Explicit Membership Tracking Function for	Multicast Routers) to	Proposed Standard
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Oct 2013 20:50:54 -0000

I have a few small comments that I collected during my review as responsible AD.
Please address them as part of the IETF last call.

Thanks,
Adrian

===

I think your core reference [6] is supposed to refer to RFC 2236 for the
core definition of IGMPv2. That RFC certainly matches the name of the
document you have given.

[Hint: idnits is your friend!]

---

idnits complains about the 2119 boiler plate because you are missing a
space in
  "RECOMMENDED","MAY",

---

Section 1 contains a clumsy sentence

   To alleviate the problem, unsolicited
   report messages are transmitted the [Robustness Variable] times
   (defined in [2][3]).

How about

   To alleviate this problem, unsolicited
   report messages are retransmitted a number of times according to the
   value of the [Robustness Variable] defined in [2] and [3].

---

Section 3

While *everyone* knows what S and G stand for, you should still say.

> -----Original Message-----
> From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of The
> IESG
> Sent: 16 October 2013 21:46
> To: IETF-Announce
> Cc: pim@ietf.org
> Subject: [pim] Last Call: <draft-ietf-pim-explicit-tracking-08.txt> (IGMP/MLD-
> Based Explicit Membership Tracking Function for Multicast Routers) to Proposed
> Standard
> 
> The IESG has received a request from the Protocol Independent Multicast
> WG (pim) to consider the following document:
> - 'IGMP/MLD-Based Explicit Membership Tracking Function for Multicast
>    Routers'
>   <draft-ietf-pim-explicit-tracking-08.txt> as Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-11-06 (this is a 3 week last call to allow
> extra time as people are preparing for IETF-88). Exceptionally, comments
> may be sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.


From stig@venaas.com  Wed Oct 16 14:23:01 2013
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 CB2D721F9AF0 for <pim@ietfa.amsl.com>; Wed, 16 Oct 2013 14:22:59 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jqiVi3ggHYzx for <pim@ietfa.amsl.com>; Wed, 16 Oct 2013 14:22:54 -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 5DF3B21F92E7 for <pim@ietf.org>; Wed, 16 Oct 2013 14:22:47 -0700 (PDT)
Received: from [IPv6:2001:420:301:1004:c93b:2992:3e9e:de2a] (unknown [IPv6:2001:420:301:1004:c93b:2992:3e9e:de2a]) by ufisa.uninett.no (Postfix) with ESMTPSA id 6985A8017 for <pim@ietf.org>; Wed, 16 Oct 2013 23:22:44 +0200 (CEST)
Message-ID: <525F03A1.5030206@venaas.com>
Date: Wed, 16 Oct 2013 14:22:41 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "pim@ietf.org" <pim@ietf.org>
References: <20131016204557.16404.47618.idtracker@ietfa.amsl.com>
In-Reply-To: <20131016204557.16404.47618.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20131016204557.16404.47618.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [pim] Fwd: Last Call: <draft-ietf-pim-explicit-tracking-08.txt> (IGMP/MLD-Based Explicit Membership Tracking Function for Multicast Routers) to Proposed Standard
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, 16 Oct 2013 21:23:01 -0000

This document is now in IETF last call. If you like you have another
chance to see if you're OK with the document. Please respond to the
last call if you have any issues. Hopefully at this point there would
be only minor editorial ones though.

Stig

-------- Original Message --------
Subject: Last Call: <draft-ietf-pim-explicit-tracking-08.txt> 
(IGMP/MLD-Based Explicit Membership Tracking Function for Multicast 
Routers) to Proposed Standard
Date: Wed, 16 Oct 2013 13:45:57 -0700
From: The IESG <iesg-secretary@ietf.org>
Reply-To: ietf@ietf.org
To: IETF-Announce <ietf-announce@ietf.org>
CC: pim@ietf.org


The IESG has received a request from the Protocol Independent Multicast
WG (pim) to consider the following document:
- 'IGMP/MLD-Based Explicit Membership Tracking Function for Multicast
    Routers'
   <draft-ietf-pim-explicit-tracking-08.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2013-11-06 (this is a 3 week last call to 
allow
extra time as people are preparing for IETF-88). Exceptionally, comments
may be sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract

    This document describes the IGMP/MLD-based explicit membership
    tracking function for multicast routers and IGMP/MLD proxy devices
    supporting IGMPv3/MLDv2.  The explicit membership tracking function
    contributes to saving network resources and shortening leave latency.


The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-pim-explicit-tracking/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-pim-explicit-tracking/ballot/


No IPR declarations have been submitted directly on this I-D.



From asaeda@sfc.wide.ad.jp  Wed Oct 16 18:38:23 2013
Return-Path: <asaeda@sfc.wide.ad.jp>
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 7CE0A11E821C for <pim@ietfa.amsl.com>; Wed, 16 Oct 2013 18:38:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sTdmfNrF+ges for <pim@ietfa.amsl.com>; Wed, 16 Oct 2013 18:38:22 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (ns.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:143]) by ietfa.amsl.com (Postfix) with ESMTP id D1E9611E81B0 for <pim@ietf.org>; Wed, 16 Oct 2013 18:38:16 -0700 (PDT)
Received: from localhost (unknown [133.69.35.12]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 02ED1278083; Thu, 17 Oct 2013 10:38:14 +0900 (JST)
Date: Thu, 17 Oct 2013 10:38:06 +0900 (JST)
Message-Id: <20131017.103806.203151971.asaeda@sfc.wide.ad.jp>
To: adrian@olddog.co.uk
From: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
In-Reply-To: <019201cecab0$14113550$3c339ff0$@olddog.co.uk>
References: <019201cecab0$14113550$3c339ff0$@olddog.co.uk>
X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: pim@ietf.org
Subject: Re: [pim] AD review draft-ietf-pim-explicit-tracking
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Oct 2013 01:38:23 -0000

Hi Adrian,

> In this case I have only a few minor issues that I have captured below.
> Since they are so small, I will enter them as IETF last call comments
> and we don't need to hold the work up any further at this time.

I'll address your comments as well as other comments that will be
given during the LC.
Thank you very much.

Regards,
--
Hitoshi Asaeda


> ===
> 
> I think your core reference [6] is supposed to refer to RFC 2236 for the
> core definition of IGMPv2. That RFC certainly matches the name of the
> document you have given.
> 
> [Hint: idnits is your friend!]
> 
> ---
> 
> idnits complains about the 2119 boiler plate because you are missing a
> space in
>   "RECOMMENDED","MAY",
> 
> ---
> 
> Section 1 contains a clumsy sentence
> 
>    To alleviate the problem, unsolicited
>    report messages are transmitted the [Robustness Variable] times
>    (defined in [2][3]).
> 
> How about
> 
>    To alleviate this problem, unsolicited
>    report messages are retransmitted a number of times according to the
>    value of the [Robustness Variable] defined in [2] and [3].
> 
> ---
> 
> Section 3
> 
> While *everyone* knows what S and G stand for, you should still say.
> 
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim

From internet-drafts@ietf.org  Thu Oct 17 08:10:08 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E89F21F935A; Thu, 17 Oct 2013 08:10:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.572
X-Spam-Level: 
X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yiAJHbd66oxv; Thu, 17 Oct 2013 08:10:07 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DE7021F9D7C; Thu, 17 Oct 2013 08:10:05 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131017151005.21895.48824.idtracker@ietfa.amsl.com>
Date: Thu, 17 Oct 2013 08:10:05 -0700
Cc: pim@ietf.org
Subject: [pim] I-D Action: draft-ietf-pim-rfc4601bis-02.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Oct 2013 15:10:09 -0000

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

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

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

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


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pim-rfc4601bis

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-pim-rfc4601bis-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pim-rfc4601bis-02


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From jktu17@gmail.com  Thu Oct 17 07:31:00 2013
Return-Path: <jktu17@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 5970721F90FD for <pim@ietfa.amsl.com>; Thu, 17 Oct 2013 07:31:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.49
X-Spam-Level: 
X-Spam-Status: No, score=0.49 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001, J_BACKHAIR_33=1, J_CHICKENPOX_61=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZYL5Tv527r+s for <pim@ietfa.amsl.com>; Thu, 17 Oct 2013 07:30:59 -0700 (PDT)
Received: from mail-vc0-x229.google.com (mail-vc0-x229.google.com [IPv6:2607:f8b0:400c:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id D3E9D21F9985 for <pim@ietf.org>; Thu, 17 Oct 2013 07:30:55 -0700 (PDT)
Received: by mail-vc0-f169.google.com with SMTP id hu8so1019610vcb.14 for <pim@ietf.org>; Thu, 17 Oct 2013 07:30:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=avcsut8dCiesoYWbvGZjpFW5UUFmMXnDwKmxapCk0zQ=; b=lMyq56Mse4qYteANNXGemKg60l+Z4uqUKauI90ZqJOWjLqM/FO9BHF2CoKkhhu3KZk IAuhenLOA2p0mm0iotcYlApKqz5rL6L22m3GeMDDfZ/HWcGItwP3DJz6i0qptPKS2ext Yc713d4Z9+6eX2Or0NUBKF1v/2sRDghIOFeUgRHF58yVBHxTZ1IWRDxq4nnULQHNWiar 29wt+sg7oGx/tx9amEgniMIFe06SU6Jqqn9dO/ax6R4rlyOZtwtaxfeRVR6x/ffrnXh3 ZmGcjBPGCYSEI3HxWU9myoLPv5eCpbah8mIpYdeY0vMyaYnJMXhJDPv6dklTkCB6mQZY /Q9g==
MIME-Version: 1.0
X-Received: by 10.58.143.17 with SMTP id sa17mr7150469veb.14.1382020250520; Thu, 17 Oct 2013 07:30:50 -0700 (PDT)
Received: by 10.220.249.129 with HTTP; Thu, 17 Oct 2013 07:30:50 -0700 (PDT)
Date: Thu, 17 Oct 2013 18:30:50 +0400
Message-ID: <CANV1Ld9ioPR2Gd7zTCf3o+SVGbe2iDVeJzO9SL7aBp-GLAtYnQ@mail.gmail.com>
From: Oleg Gvozdev <jktu17@gmail.com>
To: pim@ietf.org
Content-Type: multipart/alternative; boundary=047d7b6d95ee1ad3ed04e8f0aa2e
Subject: [pim] About using scoped addresses(boundaries)
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Oct 2013 15:24:38 -0000

--047d7b6d95ee1ad3ed04e8f0aa2e
Content-Type: text/plain; charset=ISO-8859-1

Hello

I am using pimd..I have simple test stend:

SRC<-->PIM-RP<--PIM-BSR-->DST

SRC - mcast source
DST - mcast clients(receipients)

When I use scoped address on PIM-RP router - nothing happens - mcast
continues to go to DST,

When I use scoped address on router PIM-BSR - all is OK, mcast stopped.

As i've realized - I must set scoped addresses on router, which is no
directly connected to  mcast source,i mean - on forwading routers..Am i
right?

What are the rules for correct setting of adm.boundaries ? On which routers
boundaries must be set to deny forwarding mcast traffic of given group ?

Thanks.

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

<div dir=3D"ltr"><div><div><div><div><div><div><div><div><div><div>Hello<br=
></div><br></div>I am using pimd..I have simple test stend:<br><br></div>SR=
C&lt;--&gt;PIM-RP&lt;--PIM-BSR--&gt;DST<br><br></div>SRC - mcast source<br>
</div>DST - mcast clients(receipients)<br></div><br></div>When I use scoped=
 address on PIM-RP router - nothing happens - mcast continues to go to DST,=
<br><br></div>When I use scoped address on router PIM-BSR - all is OK, mcas=
t stopped.<br>
<br></div></div><div>As i&#39;ve realized - I must set scoped addresses on =
router, which is no directly connected to=A0 mcast source,i mean - on forwa=
ding routers..Am i right?<br></div><div><br>What are the rules for correct =
setting of adm.boundaries ? On which routers boundaries must be set to deny=
 forwarding mcast traffic of given group ?<br>
<br></div>Thanks.<br></div>

--047d7b6d95ee1ad3ed04e8f0aa2e--

From jktu17@gmail.com  Fri Oct 18 00:42:58 2013
Return-Path: <jktu17@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 C9ED621F9FB3 for <pim@ietfa.amsl.com>; Fri, 18 Oct 2013 00:42:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_BACKHAIR_33=1, J_CHICKENPOX_61=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n5ebN864kzQg for <pim@ietfa.amsl.com>; Fri, 18 Oct 2013 00:42:58 -0700 (PDT)
Received: from mail-vb0-x22b.google.com (mail-vb0-x22b.google.com [IPv6:2607:f8b0:400c:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 64FD221F9F3A for <pim@ietf.org>; Fri, 18 Oct 2013 00:42:55 -0700 (PDT)
Received: by mail-vb0-f43.google.com with SMTP id h11so1718757vbh.30 for <pim@ietf.org>; Fri, 18 Oct 2013 00:42:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=pRQh2ZPo+3FjwtZzTdFkAE1cRApXzlhTkN+7iA17Qvc=; b=ZOW+PEE4pRkFRlWBNmPbpgOvA8bWaYkkgcjewNPG/SKYSRwXjJcHc/Jfrb0mGJUVad qLtV5xWg0HCsiMiLOGxv4FXChCLMTMxORDkGe74lgwFOexsbGWZ3rBooB0GzwdibstuN 32QFPZpnsUvWus/+d0mdIHIeBGJWQucq/FPXJJ+9i703OCNzoH5RNV+UTnzSkVj8P5+3 TU12EwyFYGPr5QNICc5Xf37Or/NOy27velfGtY8irQtxXG/2rRm/awGMufE1poBmFxNj 7/WMcXjNzsKx322SMXDaZrE3IN0IUW1XFMHHuYdiXqgong0JrhzPZGq6yirBOF3pOJLm fLnA==
MIME-Version: 1.0
X-Received: by 10.58.215.135 with SMTP id oi7mr105293vec.27.1382082174706; Fri, 18 Oct 2013 00:42:54 -0700 (PDT)
Received: by 10.220.249.129 with HTTP; Fri, 18 Oct 2013 00:42:54 -0700 (PDT)
Date: Fri, 18 Oct 2013 11:42:54 +0400
Message-ID: <CANV1Ld8S+4hF2iTjWFB3e1Ad2Qoc7NWwfiRkwg96rD478KkVYw@mail.gmail.com>
From: Oleg Gvozdev <jktu17@gmail.com>
To: pim@ietf.org
Content-Type: multipart/alternative; boundary=001a11c39f2412ebba04e8ff15b7
Subject: [pim] About using boundaries.
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, 18 Oct 2013 07:42:58 -0000

--001a11c39f2412ebba04e8ff15b7
Content-Type: text/plain; charset=ISO-8859-1

Hello

I am using pimd..I have simple test stend:

SRC<-->PIM-RP<--PIM-BSR-->DST

SRC - mcast source
DST - mcast clients(receipients)

When I use scoped address on PIM-RP router - nothing happens - mcast
continues to go to DST,

When I use scoped address on router PIM-BSR - all is OK, mcast stopped.

As i've realized - I must set scoped addresses on router, which is no
directly connected to  mcast source,i mean - on forwading routers..Am i
right?

What are the rules for correct setting of adm.boundaries ? On which routers
boundaries must be set to deny forwarding mcast traffic of given group ?

Thanks.

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

<div dir=3D"ltr"><div><div><div><div><div><div><div><div><div><div>Hello<br=
></div><br></div>I am using pimd..I have simple test stend:<br><br></div>SR=
C&lt;--&gt;PIM-RP&lt;--PIM-BSR--&gt;DST<br><br></div>SRC - mcast source<br>

</div>DST - mcast clients(receipients)<br></div><br></div>When I use scoped=
 address on PIM-RP router - nothing happens - mcast continues to go to DST,=
<br><br></div>When I use scoped address on router PIM-BSR - all is OK, mcas=
t stopped.<br>

<br></div></div><div>As i&#39;ve realized - I must set scoped addresses on=
=20
router, which is no directly connected to=A0 mcast source,i mean - on=20
forwading routers..Am i right?<br></div><div><br>What are the rules for=20
correct setting of adm.boundaries ? On which routers boundaries must be=20
set to deny forwarding mcast traffic of given group ?<br>
<br></div>Thanks.</div>

--001a11c39f2412ebba04e8ff15b7--

From internet-drafts@ietf.org  Fri Oct 18 14:25:15 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25FC411E8319; Fri, 18 Oct 2013 14:25:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.581
X-Spam-Level: 
X-Spam-Status: No, score=-102.581 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c5JdwoX1ZKXp; Fri, 18 Oct 2013 14:25:14 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DA3011E81DB; Fri, 18 Oct 2013 14:25:14 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131018212514.4069.28201.idtracker@ietfa.amsl.com>
Date: Fri, 18 Oct 2013 14:25:14 -0700
Cc: pim@ietf.org
Subject: [pim] I-D Action: draft-ietf-pim-hierarchicaljoinattr-01.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 18 Oct 2013 21:25:15 -0000

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

	Title           : Hierarchical Join/Prune Attributes
	Author(s)       : Stig Venaas
                          Isidor Kouvelas
                          Jesus Arango
	Filename        : draft-ietf-pim-hierarchicaljoinattr-01.txt
	Pages           : 8
	Date            : 2013-10-18

Abstract:
   This document defines a hierachical method of encoding Join
   attributes, providing a more efficient encoding when the same
   attribute values need to be specified for multiple sources in a PIM
   Join/Prune message.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pim-hierarchicaljoinattr

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-pim-hierarchicaljoinattr-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pim-hierarchicaljoinattr-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From internet-drafts@ietf.org  Sun Oct 20 10:07:39 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AECF11E820C; Sun, 20 Oct 2013 10:07:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level: 
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3569odXy4waM; Sun, 20 Oct 2013 10:07:38 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7732611E81F9; Sun, 20 Oct 2013 10:07:37 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131020170737.22766.70117.idtracker@ietfa.amsl.com>
Date: Sun, 20 Oct 2013 10:07:37 -0700
Cc: pim@ietf.org
Subject: [pim] I-D Action: draft-ietf-pim-explicit-rpf-vector-03.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 20 Oct 2013 17:07:39 -0000

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

	Title           : Explicit RPF Vector
	Author(s)       : Javed Asghar
                          IJsbrand Wijnands
                          Sowmya Krishnaswamy
                          Apoorva Karan
                          Vishal Arya
	Filename        : draft-ietf-pim-explicit-rpf-vector-03.txt
	Pages           : 5
	Date            : 2013-10-20

Abstract:
   This document defines a new Reverse Path Forwarding (RPF) Vector
   TLV to build multicast trees via an explicit path sent in the PIM
   join.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pim-explicit-rpf-vector

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-pim-explicit-rpf-vector-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pim-explicit-rpf-vector-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From wwwrun@rfc-editor.org  Tue Oct 22 15:24:34 2013
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 5BF9A11E81DB for <pim@ietfa.amsl.com>; Tue, 22 Oct 2013 15:24:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.39
X-Spam-Level: 
X-Spam-Status: No, score=-102.39 tagged_above=-999 required=5 tests=[AWL=0.210, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jXn-hRc8FTkg for <pim@ietfa.amsl.com>; Tue, 22 Oct 2013 15:24:33 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 247E211E8224 for <pim@ietf.org>; Tue, 22 Oct 2013 15:24:32 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B6CAC726001; Tue, 22 Oct 2013 15:15:58 -0700 (PDT)
To: M.Handley@cs.ucl.ac.uk, kouvelas@cisco.com, speakman@cisco.com, lorenzo@digitalfountain.com, stbryant@cisco.com, adrian@olddog.co.uk, stig@venaas.com, mmcbride7@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20131022221558.B6CAC726001@rfc-editor.org>
Date: Tue, 22 Oct 2013 15:15:58 -0700 (PDT)
X-Mailman-Approved-At: Wed, 23 Oct 2013 10:37:43 -0700
Cc: ctbrown@cisco.com, pim@ietf.org, rfc-editor@rfc-editor.org
Subject: [pim] [Editorial Errata Reported] RFC5015 (3762)
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, 22 Oct 2013 22:24:34 -0000

The following errata report has been submitted for RFC5015,
"Bidirectional Protocol Independent Multicast (BIDIR-PIM)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5015&eid=3762

--------------------------------------
Type: Editorial
Reported by: Christopher Brown <ctbrown@cisco.com>

Section: 3.5.3.1.

Original Text
-------------
      Best-Offer
         Used by the DF to record the identity and advertised metrics of
         the router that has made the last offer, for use when sending
         the Path message.


Corrected Text
--------------
      Best-Offer
         Used by the DF to record the identity and advertised metrics of
         the router that has made the last offer, for use when sending
         the Pass message.


Notes
-----
typo: Path message should be Pass message

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC5015 (draft-ietf-pim-bidir-09)
--------------------------------------
Title               : Bidirectional Protocol Independent Multicast (BIDIR-PIM)
Publication Date    : October 2007
Author(s)           : M. Handley, I. Kouvelas, T. Speakman, L. Vicisano
Category            : PROPOSED STANDARD
Source              : Protocol Independent Multicast
Area                : Routing
Stream              : IETF
Verifying Party     : IESG

From ietf-secretariat-reply@ietf.org  Wed Oct 23 11:08:14 2013
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E96EA11E813A for <pim@ietfa.amsl.com>; Wed, 23 Oct 2013 11:08:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.489
X-Spam-Level: 
X-Spam-Status: No, score=-102.489 tagged_above=-999 required=5 tests=[AWL=0.111, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ks0FLPaz9AE3 for <pim@ietfa.amsl.com>; Wed, 23 Oct 2013 11:08:13 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 07E0611E8346 for <pim@ietf.org>; Wed, 23 Oct 2013 11:08:08 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
To: pim@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.81
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131023180808.27955.16951.idtracker@ietfa.amsl.com>
Date: Wed, 23 Oct 2013 11:08:08 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
X-Mailman-Approved-At: Thu, 24 Oct 2013 11:03:12 -0700
Subject: [pim] Milestones changed for pim WG
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 23 Oct 2013 18:08:14 -0000

Changed milestone "First WG version of udated RFC 4601", resolved as
"Done".

Changed milestone "Submit a more reliable PIM solution (refresh
reduction) to the IESG", resolved as "Done".

Changed milestone "Submit a population count extension to PIM to the
IESG", resolved as "Done".

URL: http://datatracker.ietf.org/wg/pim/charter/

From mike.mcbride@ericsson.com  Thu Oct 24 16:27:15 2013
Return-Path: <mike.mcbride@ericsson.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07B0A11E826E for <pim@ietfa.amsl.com>; Thu, 24 Oct 2013 16:27:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level: 
X-Spam-Status: No, score=-2.561 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ilbEcF2mINg8 for <pim@ietfa.amsl.com>; Thu, 24 Oct 2013 16:27:08 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 22AC411E821F for <pim@ietf.org>; Thu, 24 Oct 2013 16:27:07 -0700 (PDT)
X-AuditID: c6180641-b7fe28e000000d82-3e-5269accbd998
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 12.5A.03458.BCCA9625; Fri, 25 Oct 2013 01:27:07 +0200 (CEST)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC004.ericsson.se ([147.117.188.84]) with mapi id 14.02.0328.009; Thu, 24 Oct 2013 19:27:07 -0400
From: Mike McBride <mike.mcbride@ericsson.com>
To: "pim@ietf.org" <pim@ietf.org>
Thread-Topic: draft agenda for Vancouver
Thread-Index: Ac7REDVW+L74CFaPQom9FwpgRL1OIg==
Date: Thu, 24 Oct 2013 23:27:06 +0000
Message-ID: <6F5149063CE40341BE7953160A93C5A0D89190@eusaamb109.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrALMWRmVeSWpSXmKPExsUyuXRPiO7pNZlBBv9OyFl8eXiT2YHRY8mS n0wBjFFcNimpOZllqUX6dglcGUunnWEteMFcsfjeK9YGxjnMXYycHBICJhJnltxggrDFJC7c W8/WxcjFISRwlFHi0+yHLBDOckaJddf3soBUsQnoSZxe2MwKYosIKEq0z20Bs4UFlCX+zV7I AhHXkNh87xojhK0ncWzOarANLAKqEnf/rQer4RXwlljz9h9YDSPQ5u+n1oDVMAuIS9x6Mh/q IgGJJXvOQ10qKvHy8T9WCFtZ4vucRywQ9ToSC3Z/YoOwtSWWLXzNDDFfUOLkzCcsExiFZyEZ OwtJyywkLbOQtCxgZFnFyFFanFqWm25kuIkRGMrHJNgcdzAu+GR5iFGag0VJnPfLW+cgIYH0 xJLU7NTUgtSi+KLSnNTiQ4xMHJxSDYwctx3Wdm//GM6tJ23fGmH+sG1Wol/lD6lOpadb/JNP Jvd0b7unHlK2dkv6siV8u9fMMfs5X1TGWkfh2s4iP7u1upND1HTXNzl8ld/2typnyaXCpn3K 5jsfrDDnXhF+oF9r1RG79VHTuSVmc+8J3sMdMOvBEv1Y0fTVhQc/y24u/7g5zP+IXYkSS3FG oqEWc1FxIgD/gyl/MwIAAA==
Subject: [pim] draft agenda for Vancouver
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Oct 2013 23:27:15 -0000

Please let us know if we missed you on the agenda. We have room for a coupl=
e more draft discussions.

WG Update					Stig/Mike
draft-ietf-pim-drlb-02				TBD
draft-ietf-pim-hierarchicaljoinattr-01		Stig Venaas
draft-atwood-mboned-mrac-req-00		Bill Atwood
draft-atwood-mboned-mrac-arch-00		Bill Atwood
draft-yong-isis-ext-4-distribution-tree-01    	Lucy Yong
draft-ietf-l2vpn-vpls-pim-snooping-05		Jeffrey Zhang
draft-arango-pim-join-attributes-for-lisp-00	TBD

thanks,
mike

From mmcbride7@gmail.com  Fri Oct 25 15:08:02 2013
Return-Path: <mmcbride7@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 9D5B011E8181 for <pim@ietfa.amsl.com>; Fri, 25 Oct 2013 15:08:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20CaQuZq2hbs for <pim@ietfa.amsl.com>; Fri, 25 Oct 2013 15:08:02 -0700 (PDT)
Received: from mail-pd0-x231.google.com (mail-pd0-x231.google.com [IPv6:2607:f8b0:400e:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id D49C511E81CE for <pim@ietf.org>; Fri, 25 Oct 2013 15:08:01 -0700 (PDT)
Received: by mail-pd0-f177.google.com with SMTP id p10so4549784pdj.22 for <pim@ietf.org>; Fri, 25 Oct 2013 15:07:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=KMqBs4p4fDCTGZhx0yGlJk61qu+5WghGX3C3aYrEQXM=; b=Zf3U6Ly62/gnKLmqp/Gyfn2IpyArO+Jw1Fa5NFTeSj8D/bk+b8HUOu0A7wQwjMI8FP FZrZfYYHxZP6A6MRcVZ36/RL3kIXZ42sP/wefuVEYF0PcW4aBns9ySs4F4yK3BD4MnDd kqYOtOVC+G390DLPs3H4MgUfXJh7wYco4ScoQV1mSlr7V41Inqa+KIV4bCeSGvH2LXYV uWgmSAFG6he8ZgJnlQ5K9odcxOsSs5pKbeO4jlLkrdxH9sRUXtqBZY3ELgu9tPmovH3p cHqkMb78QTyzYgYL7s2W//VXYarP9Jsn1+pQjGHstjyqfFJlYginB9bgHY9ECY2dDsKo 7gIA==
MIME-Version: 1.0
X-Received: by 10.68.215.38 with SMTP id of6mr9164533pbc.14.1382738879598; Fri, 25 Oct 2013 15:07:59 -0700 (PDT)
Received: by 10.68.24.166 with HTTP; Fri, 25 Oct 2013 15:07:59 -0700 (PDT)
Date: Fri, 25 Oct 2013 15:07:59 -0700
Message-ID: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com>
From: Mike McBride <mmcbride7@gmail.com>
To: "pim@ietf.org" <pim@ietf.org>
Content-Type: multipart/alternative; boundary=001a11346638bc581504e997fbfd
Subject: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
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, 25 Oct 2013 22:08:02 -0000

--001a11346638bc581504e997fbfd
Content-Type: text/plain; charset=ISO-8859-1

The authors of draft-wijnands-pim-source-discovery-bsr-03 have requested
that we initiate a call for adoption of their draft which they presented in
our last meeting in Berlin. Notes from that presentation are below. Please
comment over the next week (before ietf week) on your interest/non-interest
with adoption of this draft.

http://www.ietf.org/id/draft-wijnands-pim-source-discovery-bsr-03.txt

thanks,
mike

draft-wignands-pim-source-discovery-bsr-03 (Ice)
==============================================
highly redudant mcast network without single point of failure.
Jeffrey: Of the 10k flows how many groups?
Ice: the sources are what's relevant. 10k s,gs. Not introducing a new
routing protocol.
Jeffrey: Could use mospf. pim bidir is another viable approach. With
bidir, while the RPA canbe an address that is not tried to any router
(the address would be associated with a LAN), the LAN that the RPA is
on could become partitioned. When that happens, traffic cannot be
exchanged on the LAN between the partitions, affecting lots of
receivers. That's the problem using PIM-BIDIR instead of BSR flooing.
However, that can be easily resolved by a protocol extension. I should
be able to publish it for the next IETF meeting. With that resolved,
PIM bidir will be a better solution for the targeted deployment
scenario.
stig: one issue with bidir is you don't have the optimal path.
operator DT: I like the use case and support.
Hitoshi: flooding is not typically optimal.
Ice: its only using mechanisms that exist today with bsr.
jeffrey: the amount of information is more with today.
Hitoshi: Why not use SAP (I'm not a fan of SAP though)? Whats the
meaning of flooding. Use MSDP if interdomain?
lighthouse networks: you mentioned dns, why can't you use that?
Ice; this is a case where you don't know the source. bsr based
flooding. not inter domain discussion. Enterprise network.
Mike: applaud any efforts to make multicast more simple. But flooding
may be a problem.

1 room interested. 2 operators on draft interested. Mike will poll on list.

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

<div dir=3D"ltr"><div>The authors of draft-wijnands-pim-source-discovery-bs=
r-03 have requested that we initiate a call for adoption of their draft whi=
ch they presented in our last meeting in Berlin. Notes from that presentati=
on are below. Please comment over the next week (before ietf week) on your =
interest/non-interest with adoption of this draft.<br>
<br><a href=3D"http://www.ietf.org/id/draft-wijnands-pim-source-discovery-b=
sr-03.txt">http://www.ietf.org/id/draft-wijnands-pim-source-discovery-bsr-0=
3.txt</a><br><br></div>thanks,<br>mike<br><br><pre>draft-wignands-pim-sourc=
e-discovery-bsr-03 (Ice)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
highly redudant mcast network without single point of failure. =20
Jeffrey: Of the 10k flows how many groups?
Ice: the sources are what&#39;s relevant. 10k s,gs. Not introducing a new r=
outing protocol.
Jeffrey: Could use mospf. pim bidir is another viable approach. With bidir,=
 while the RPA canbe an address that is not tried to any router (the addres=
s would be associated with a LAN), the LAN that the RPA is on could become =
partitioned. When that happens, traffic cannot be exchanged on the LAN betw=
een the partitions, affecting lots of receivers. That&#39;s the problem usi=
ng PIM-BIDIR instead of BSR flooing. However, that can be easily resolved b=
y a protocol extension. I should be able to publish it for the next IETF me=
eting. With that resolved, PIM bidir will be a better solution for the targ=
eted deployment scenario.
stig: one issue with bidir is you don&#39;t have the optimal path.
operator DT: I like the use case and support.
Hitoshi: flooding is not typically optimal.
Ice: its only using mechanisms that exist today with bsr.
jeffrey: the amount of information is more with today.
Hitoshi: Why not use SAP (I&#39;m not a fan of SAP though)? Whats the meani=
ng of flooding. Use MSDP if interdomain?
lighthouse networks: you mentioned dns, why can&#39;t you use that?
Ice; this is a case where you don&#39;t know the source. bsr based flooding=
. not inter domain discussion. Enterprise network.
Mike: applaud any efforts to make multicast more simple. But flooding may b=
e a problem.

1 room interested. 2 operators on draft interested. Mike will poll on list.=
</pre><br></div>

--001a11346638bc581504e997fbfd--

From jeff.tantsura@ericsson.com  Sun Oct 27 21:38:14 2013
Return-Path: <jeff.tantsura@ericsson.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AE9B11E8223 for <pim@ietfa.amsl.com>; Sun, 27 Oct 2013 21:37:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.215
X-Spam-Level: 
X-Spam-Status: No, score=-2.215 tagged_above=-999 required=5 tests=[AWL=-0.217, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u82aEyz6PoJJ for <pim@ietfa.amsl.com>; Sun, 27 Oct 2013 21:37:49 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 1365D11E814B for <pim@ietf.org>; Sun, 27 Oct 2013 21:37:47 -0700 (PDT)
X-AuditID: c618062d-b7fda8e0000024c6-b7-526dea18dbda
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 05.3D.09414.81AED625; Mon, 28 Oct 2013 05:37:44 +0100 (CET)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.02.0328.009; Mon, 28 Oct 2013 00:37:43 -0400
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Thread-Topic: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
Thread-Index: AQHO0c6weVIa22rD30Kay1ePXEfBwJoJWQOA
Date: Mon, 28 Oct 2013 04:37:43 +0000
Message-ID: <60DEDD93F5E54B4AB55647B8B6C74839986457@eusaamb109.ericsson.se>
In-Reply-To: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.5.121010
x-originating-ip: [147.117.188.135]
Content-Type: multipart/alternative; boundary="_000_60DEDD93F5E54B4AB55647B8B6C74839986457eusaamb109ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrCLMWRmVeSWpSXmKPExsUyuXRPuK7Eq9wggz3rdSy+3pvLZPHl4U1m ByaPnbPusnssWfKTKYApissmJTUnsyy1SN8ugStjQs8RtoJ75hVzOm+wNjCe1O9i5OCQEDCR 2H2XrYuRE8gUk7hwbz2QzcUhJHCEUWLbpeesEM5yRone6+1gVWwCBhL/vx1nAbFFBFwlerZs ZgaxhQV8JCZsbmGGiPtK/F93hAnCNpJ4c+4gWJxFQFWiY/Y1VhCbV8BbYs+jnWA2p0CgxON5 X8FqGIGu+H5qDVgvs4C4xK0n85kgrhOQWLLnPDOELSrx8vE/sF5RAT2JtmNn2CHiyhLf5zxi gejNl+iefJodYpegxMmZT1gmMIrMQjJ2FpKyWUjKIOI6Egt2f2KDsLUlli18zQxjnznwGKiX A8i2lpg+PQpZyQJGjlWMHKXFqWW56UYGmxiBMXVMgk13B+Oel5aHGKU5WJTEeb+8dQ4SEkhP LEnNTk0tSC2KLyrNSS0+xMjEwSnVwJib93pDbvDMqZcuHr3F/OfzJDFbpn+M4Xk/DuunXVsV nTNFcfrV2fkaCd+mvXG6ctF3ydbz2cKLUmzuVxZWXXuxiqX0OpPLJa703QqhKTOlNDZXeEtP 1/G3eV4gJfouK+3xr+IHb9V8jGtu/U2oXm2jJflCOL5vZqsdx5L13yfemvwk+YBjop0SS3FG oqEWc1FxIgDRYxwMdwIAAA==
Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
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, 28 Oct 2013 04:38:14 -0000

--_000_60DEDD93F5E54B4AB55647B8B6C74839986457eusaamb109ericsso_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Mike,

Support.

Cheers,
Jeff

From: Mike McBride <mmcbride7@gmail.com<mailto:mmcbride7@gmail.com>>
Date: Friday, October 25, 2013 3:07 PM
To: "pim@ietf.org<mailto:pim@ietf.org>" <pim@ietf.org<mailto:pim@ietf.org>>
Subject: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption

The authors of draft-wijnands-pim-source-discovery-bsr-03 have requested th=
at we initiate a call for adoption of their draft which they presented in o=
ur last meeting in Berlin. Notes from that presentation are below. Please c=
omment over the next week (before ietf week) on your interest/non-interest =
with adoption of this draft.

http://www.ietf.org/id/draft-wijnands-pim-source-discovery-bsr-03.txt

thanks,
mike


draft-wignands-pim-source-discovery-bsr-03 (Ice)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
highly redudant mcast network without single point of failure.
Jeffrey: Of the 10k flows how many groups?
Ice: the sources are what's relevant. 10k s,gs. Not introducing a new routi=
ng protocol.
Jeffrey: Could use mospf. pim bidir is another viable approach. With bidir,=
 while the RPA canbe an address that is not tried to any router (the addres=
s would be associated with a LAN), the LAN that the RPA is on could become =
partitioned. When that happens, traffic cannot be exchanged on the LAN betw=
een the partitions, affecting lots of receivers. That's the problem using P=
IM-BIDIR instead of BSR flooing. However, that can be easily resolved by a =
protocol extension. I should be able to publish it for the next IETF meetin=
g. With that resolved, PIM bidir will be a better solution for the targeted=
 deployment scenario.
stig: one issue with bidir is you don't have the optimal path.
operator DT: I like the use case and support.
Hitoshi: flooding is not typically optimal.
Ice: its only using mechanisms that exist today with bsr.
jeffrey: the amount of information is more with today.
Hitoshi: Why not use SAP (I'm not a fan of SAP though)? Whats the meaning o=
f flooding. Use MSDP if interdomain?
lighthouse networks: you mentioned dns, why can't you use that?
Ice; this is a case where you don't know the source. bsr based flooding. no=
t inter domain discussion. Enterprise network.
Mike: applaud any efforts to make multicast more simple. But flooding may b=
e a problem.

1 room interested. 2 operators on draft interested. Mike will poll on list.


--_000_60DEDD93F5E54B4AB55647B8B6C74839986457eusaamb109ericsso_
Content-Type: text/html; charset="us-ascii"
Content-ID: <20960CB09FC5D84B82F7DA2FCD3B45CB@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>
<div>
<div>Hi Mike,</div>
<div><br>
</div>
<div>Support.</div>
<div>
<div><span style=3D"font-family: Calibri; "><br>
</span></div>
<div><span style=3D"font-family: Calibri; ">Cheers,</span></div>
<div><font class=3D"Apple-style-span" color=3D"#000000"><font class=3D"Appl=
e-style-span" face=3D"Calibri">Jeff</font></font></div>
</div>
</div>
</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Mike McBride &lt;<a href=3D"m=
ailto:mmcbride7@gmail.com">mmcbride7@gmail.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Friday, October 25, 2013 3:07=
 PM<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:pim@iet=
f.org">pim@ietf.org</a>&quot; &lt;<a href=3D"mailto:pim@ietf.org">pim@ietf.=
org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>[pim] draft-wijnands-pim-s=
ource-discovery-bsr call for adoption<br>
</div>
<div><br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT:=
 #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<div dir=3D"ltr">
<div>The authors of draft-wijnands-pim-source-discovery-bsr-03 have request=
ed that we initiate a call for adoption of their draft which they presented=
 in our last meeting in Berlin. Notes from that presentation are below. Ple=
ase comment over the next week (before
 ietf week) on your interest/non-interest with adoption of this draft.<br>
<br>
<a href=3D"http://www.ietf.org/id/draft-wijnands-pim-source-discovery-bsr-0=
3.txt">http://www.ietf.org/id/draft-wijnands-pim-source-discovery-bsr-03.tx=
t</a><br>
<br>
</div>
thanks,<br>
mike<br>
<br>
<pre>draft-wignands-pim-source-discovery-bsr-03 (Ice)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
highly redudant mcast network without single point of failure. =20
Jeffrey: Of the 10k flows how many groups?
Ice: the sources are what's relevant. 10k s,gs. Not introducing a new routi=
ng protocol.
Jeffrey: Could use mospf. pim bidir is another viable approach. With bidir,=
 while the RPA canbe an address that is not tried to any router (the addres=
s would be associated with a LAN), the LAN that the RPA is on could become =
partitioned. When that happens, traffic cannot be exchanged on the LAN betw=
een the partitions, affecting lots of receivers. That's the problem using P=
IM-BIDIR instead of BSR flooing. However, that can be easily resolved by a =
protocol extension. I should be able to publish it for the next IETF meetin=
g. With that resolved, PIM bidir will be a better solution for the targeted=
 deployment scenario.
stig: one issue with bidir is you don't have the optimal path.
operator DT: I like the use case and support.
Hitoshi: flooding is not typically optimal.
Ice: its only using mechanisms that exist today with bsr.
jeffrey: the amount of information is more with today.
Hitoshi: Why not use SAP (I'm not a fan of SAP though)? Whats the meaning o=
f flooding. Use MSDP if interdomain?
lighthouse networks: you mentioned dns, why can't you use that?
Ice; this is a case where you don't know the source. bsr based flooding. no=
t inter domain discussion. Enterprise network.
Mike: applaud any efforts to make multicast more simple. But flooding may b=
e a problem.

1 room interested. 2 operators on draft interested. Mike will poll on list.=
</pre>
<br>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>

--_000_60DEDD93F5E54B4AB55647B8B6C74839986457eusaamb109ericsso_--

From zzhang@juniper.net  Mon Oct 28 06:27:41 2013
Return-Path: <zzhang@juniper.net>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4ADE11E82F2 for <pim@ietfa.amsl.com>; Mon, 28 Oct 2013 06:27:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m2kRNUaySLre for <pim@ietfa.amsl.com>; Mon, 28 Oct 2013 06:27:36 -0700 (PDT)
Received: from db9outboundpool.messaging.microsoft.com (mail-db9lp0250.outbound.messaging.microsoft.com [213.199.154.250]) by ietfa.amsl.com (Postfix) with ESMTP id B568D11E82FB for <pim@ietf.org>; Mon, 28 Oct 2013 06:27:26 -0700 (PDT)
Received: from mail143-db9-R.bigfish.com (10.174.16.253) by DB9EHSOBE024.bigfish.com (10.174.14.87) with Microsoft SMTP Server id 14.1.225.22; Mon, 28 Oct 2013 13:27:25 +0000
Received: from mail143-db9 (localhost [127.0.0.1])	by mail143-db9-R.bigfish.com (Postfix) with ESMTP id EC6B4400D7; Mon, 28 Oct 2013 13:27:24 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT002.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -19
X-BigFish: VPS-19(zz9371Ic85fhzz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1d7338h1de098h1033IL17326ah8275bh8275dh18c673h1c8fb4h1de097h186068hz2fh2a8h839hd24hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1bceh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h20f0h9a9j1155h)
Received-SPF: pass (mail143-db9: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=zzhang@juniper.net; helo=BL2PRD0510HT002.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(377454003)(199002)(189002)(54356001)(18717965001)(81686001)(81816001)(53806001)(56816003)(51856001)(77096001)(76796001)(19300405004)(46102001)(76786001)(76576001)(74316001)(81542001)(19609705001)(4396001)(80976001)(49866001)(65816001)(85306002)(15202345003)(74876001)(54316002)(16236675002)(69226001)(76482001)(56776001)(74706001)(15975445006)(74366001)(19580395003)(83322001)(66066001)(19580405001)(81342001)(83072001)(80022001)(47736001)(50986001)(47976001)(74662001)(77982001)(59766001)(79102001)(74502001)(31966008)(47446002)(33646001)(63696002)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BY2PR05MB078; H:BY2PR05MB079.namprd05.prod.outlook.com; CLIP:66.129.241.18; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail143-db9 (localhost.localdomain [127.0.0.1]) by mail143-db9 (MessageSwitch) id 1382966841409040_23707; Mon, 28 Oct 2013 13:27:21 +0000 (UTC)
Received: from DB9EHSMHS001.bigfish.com (unknown [10.174.16.244])	by mail143-db9.bigfish.com (Postfix) with ESMTP id 5F1073C008B; Mon, 28 Oct 2013 13:27:21 +0000 (UTC)
Received: from BL2PRD0510HT002.namprd05.prod.outlook.com (157.56.240.101) by DB9EHSMHS001.bigfish.com (10.174.14.11) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 28 Oct 2013 13:27:18 +0000
Received: from BY2PR05MB078.namprd05.prod.outlook.com (10.242.38.12) by BL2PRD0510HT002.namprd05.prod.outlook.com (10.255.100.37) with Microsoft SMTP Server (TLS) id 14.16.371.2; Mon, 28 Oct 2013 13:27:18 +0000
Received: from BY2PR05MB079.namprd05.prod.outlook.com (10.242.38.16) by BY2PR05MB078.namprd05.prod.outlook.com (10.242.38.12) with Microsoft SMTP Server (TLS) id 15.0.810.5; Mon, 28 Oct 2013 13:27:15 +0000
Received: from BY2PR05MB079.namprd05.prod.outlook.com ([169.254.8.16]) by BY2PR05MB079.namprd05.prod.outlook.com ([169.254.8.16]) with mapi id 15.00.0810.005; Mon, 28 Oct 2013 13:27:15 +0000
From: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
To: Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Thread-Topic: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
Thread-Index: AQHO0c68DdGwj3jORkCcwV771ygo/5oKHOxg
Date: Mon, 28 Oct 2013 13:27:14 +0000
Message-ID: <bc63bb3bdfbe420cb9c464bf8a8398f7@BY2PR05MB079.namprd05.prod.outlook.com>
References: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com>
In-Reply-To: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.18]
x-forefront-prvs: 0013079544
Content-Type: multipart/alternative; boundary="_000_bc63bb3bdfbe420cb9c464bf8a8398f7BY2PR05MB079namprd05pro_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
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, 28 Oct 2013 13:27:41 -0000

--_000_bc63bb3bdfbe420cb9c464bf8a8398f7BY2PR05MB079namprd05pro_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

We should not rush to a decision before the IETF week.

The drawbacks of the solution have been discussed before.

The draft has two aspects:


1.       Source information flooding in an environment with high resilience=
 requirement

2.       Should we extend BSR to a generic flooding mechanism

For both of them, PIM-Bidir is a very good alternative - after the RP resil=
ience problem is resolved.

In Vancouver I will present a simple enhancement to PIM-Bidir procedures (n=
o signaling extension is required) to address that - http://tools.ietf.org/=
html/draft-zzhang-pim-bidir-rpl-resiliency-00.

Thanks.
Jeffrey

From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of Mike =
McBride
Sent: Friday, October 25, 2013 6:08 PM
To: pim@ietf.org
Subject: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption

The authors of draft-wijnands-pim-source-discovery-bsr-03 have requested th=
at we initiate a call for adoption of their draft which they presented in o=
ur last meeting in Berlin. Notes from that presentation are below. Please c=
omment over the next week (before ietf week) on your interest/non-interest =
with adoption of this draft.

http://www.ietf.org/id/draft-wijnands-pim-source-discovery-bsr-03.txt
thanks,
mike

draft-wignands-pim-source-discovery-bsr-03 (Ice)

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

highly redudant mcast network without single point of failure.

Jeffrey: Of the 10k flows how many groups?

Ice: the sources are what's relevant. 10k s,gs. Not introducing a new routi=
ng protocol.

Jeffrey: Could use mospf. pim bidir is another viable approach. With bidir,=
 while the RPA canbe an address that is not tried to any router (the addres=
s would be associated with a LAN), the LAN that the RPA is on could become =
partitioned. When that happens, traffic cannot be exchanged on the LAN betw=
een the partitions, affecting lots of receivers. That's the problem using P=
IM-BIDIR instead of BSR flooing. However, that can be easily resolved by a =
protocol extension. I should be able to publish it for the next IETF meetin=
g. With that resolved, PIM bidir will be a better solution for the targeted=
 deployment scenario.

stig: one issue with bidir is you don't have the optimal path.

operator DT: I like the use case and support.

Hitoshi: flooding is not typically optimal.

Ice: its only using mechanisms that exist today with bsr.

jeffrey: the amount of information is more with today.

Hitoshi: Why not use SAP (I'm not a fan of SAP though)? Whats the meaning o=
f flooding. Use MSDP if interdomain?

lighthouse networks: you mentioned dns, why can't you use that?

Ice; this is a case where you don't know the source. bsr based flooding. no=
t inter domain discussion. Enterprise network.

Mike: applaud any efforts to make multicast more simple. But flooding may b=
e a problem.



1 room interested. 2 operators on draft interested. Mike will poll on list.


--_000_bc63bb3bdfbe420cb9c464bf8a8398f7BY2PR05MB079namprd05pro_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1889534835;
	mso-list-type:hybrid;
	mso-list-template-ids:421693704 543039676 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.25in;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">We should not rush to a d=
ecision before the IETF week.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">The drawbacks of the solu=
tion have been discussed before.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">The draft has two aspects=
:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.25in;text-indent:-.25in=
;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-list:Ign=
ore">1.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Source informatio=
n flooding in an environment with high resilience requirement<o:p></o:p></s=
pan></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.25in;text-indent:-.25in=
;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-list:Ign=
ore">2.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Should we extend =
BSR to a generic flooding mechanism<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">For both of them, PIM-Bid=
ir is a very good alternative &#8211; after the RP resilience problem is re=
solved.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">In Vancouver I will prese=
nt a simple enhancement to PIM-Bidir procedures (no signaling extension is =
required) to address that -
</span><a href=3D"http://tools.ietf.org/html/draft-zzhang-pim-bidir-rpl-res=
iliency-00">http://tools.ietf.org/html/draft-zzhang-pim-bidir-rpl-resilienc=
y-00</a>.<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks.<br>
Jeffrey<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> pim-boun=
ces@ietf.org [mailto:pim-bounces@ietf.org]
<b>On Behalf Of </b>Mike McBride<br>
<b>Sent:</b> Friday, October 25, 2013 6:08 PM<br>
<b>To:</b> pim@ietf.org<br>
<b>Subject:</b> [pim] draft-wijnands-pim-source-discovery-bsr call for adop=
tion<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">The authors of draft-=
wijnands-pim-source-discovery-bsr-03 have requested that we initiate a call=
 for adoption of their draft which they presented in our last meeting in Be=
rlin. Notes from that presentation are
 below. Please comment over the next week (before ietf week) on your intere=
st/non-interest with adoption of this draft.<br>
<br>
<a href=3D"http://www.ietf.org/id/draft-wijnands-pim-source-discovery-bsr-0=
3.txt">http://www.ietf.org/id/draft-wijnands-pim-source-discovery-bsr-03.tx=
t</a><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">thanks,<br>
mike<o:p></o:p></p>
<pre>draft-wignands-pim-source-discovery-bsr-03 (Ice)<o:p></o:p></pre>
<pre>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p><=
/o:p></pre>
<pre>highly redudant mcast network without single point of failure.&nbsp; <=
o:p></o:p></pre>
<pre>Jeffrey: Of the 10k flows how many groups?<o:p></o:p></pre>
<pre>Ice: the sources are what's relevant. 10k s,gs. Not introducing a new =
routing protocol.<o:p></o:p></pre>
<pre>Jeffrey: Could use mospf. pim bidir is another viable approach. With b=
idir, while the RPA canbe an address that is not tried to any router (the a=
ddress would be associated with a LAN), the LAN that the RPA is on could be=
come partitioned. When that happens, traffic cannot be exchanged on the LAN=
 between the partitions, affecting lots of receivers. That's the problem us=
ing PIM-BIDIR instead of BSR flooing. However, that can be easily resolved =
by a protocol extension. I should be able to publish it for the next IETF m=
eeting. With that resolved, PIM bidir will be a better solution for the tar=
geted deployment scenario.<o:p></o:p></pre>
<pre>stig: one issue with bidir is you don't have the optimal path.<o:p></o=
:p></pre>
<pre>operator DT: I like the use case and support.<o:p></o:p></pre>
<pre>Hitoshi: flooding is not typically optimal.<o:p></o:p></pre>
<pre>Ice: its only using mechanisms that exist today with bsr.<o:p></o:p></=
pre>
<pre>jeffrey: the amount of information is more with today.<o:p></o:p></pre=
>
<pre>Hitoshi: Why not use SAP (I'm not a fan of SAP though)? Whats the mean=
ing of flooding. Use MSDP if interdomain?<o:p></o:p></pre>
<pre>lighthouse networks: you mentioned dns, why can't you use that?<o:p></=
o:p></pre>
<pre>Ice; this is a case where you don't know the source. bsr based floodin=
g. not inter domain discussion. Enterprise network.<o:p></o:p></pre>
<pre>Mike: applaud any efforts to make multicast more simple. But flooding =
may be a problem.<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>1 room interested. 2 operators on draft interested. Mike will poll on =
list.<o:p></o:p></pre>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_bc63bb3bdfbe420cb9c464bf8a8398f7BY2PR05MB079namprd05pro_--

From tom.taylor.stds@gmail.com  Mon Oct 28 07:56:06 2013
Return-Path: <tom.taylor.stds@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 D210D21E8092 for <pim@ietfa.amsl.com>; Mon, 28 Oct 2013 07:56:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.586
X-Spam-Level: 
X-Spam-Status: No, score=-2.586 tagged_above=-999 required=5 tests=[AWL=0.013,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v+CjVIKoirHV for <pim@ietfa.amsl.com>; Mon, 28 Oct 2013 07:56:06 -0700 (PDT)
Received: from mail-qc0-x22e.google.com (mail-qc0-x22e.google.com [IPv6:2607:f8b0:400d:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id CB54011E8331 for <pim@ietf.org>; Mon, 28 Oct 2013 07:56:00 -0700 (PDT)
Received: by mail-qc0-f174.google.com with SMTP id v1so3808671qcw.5 for <pim@ietf.org>; Mon, 28 Oct 2013 07:56:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=GOk++6pAGR/9bWbh3uS+iq9P8FKIJkshBuOGuRfqmU8=; b=Pa7P3xCV4wmQNC4Dzqft1JEs6pioB7VUEeGnkElK5NeGK5BprhJP+f9eu03o6bUNqm Yn2mMjy0fnxtEPZQ2hwsYp9BOSqIulQcyalUjkRRARpyR6ffg7OPH5C96FXFiCMmCwul DTmJT8fl59nhLGEqqeSHZdDv8puX52ToxPUlBeRl4rkY4pLVnQ/T50F9ozH++1i4VBN4 qcg64+dcz9amaf0BC0ubmwQyjx3oliD51Q8VYfyvnhY9ouc5YnTeT+iF2Sw11pgGrMWz 3Bjo6r/h3xCGOZyqn689gFWXn9FlDej1n/hKNfafHIIjYNLLMccGPGiWaDZFq3dJFhVg v7gg==
X-Received: by 10.224.12.137 with SMTP id x9mr2582224qax.110.1382972160311; Mon, 28 Oct 2013 07:56:00 -0700 (PDT)
Received: from [192.168.1.69] (dsl-173-206-11-102.tor.primus.ca. [173.206.11.102]) by mx.google.com with ESMTPSA id a5sm40323137qae.2.2013.10.28.07.55.59 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 28 Oct 2013 07:55:59 -0700 (PDT)
Message-ID: <526E7AFC.2010207@gmail.com>
Date: Mon, 28 Oct 2013 10:55:56 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
References: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com>
In-Reply-To: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
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, 28 Oct 2013 14:56:06 -0000

Support.

Tom Taylor

On 25/10/2013 6:07 PM, Mike McBride wrote:
> The authors of draft-wijnands-pim-source-discovery-bsr-03 have requested
> that we initiate a call for adoption of their draft which they presented in
> our last meeting in Berlin. Notes from that presentation are below. Please
> comment over the next week (before ietf week) on your interest/non-interest
> with adoption of this draft.
>
> http://www.ietf.org/id/draft-wijnands-pim-source-discovery-bsr-03.txt
>
> thanks,
> mike
...

From mike.mcbride@ericsson.com  Mon Oct 28 08:10:21 2013
Return-Path: <mike.mcbride@ericsson.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09F1B21F9EB6 for <pim@ietfa.amsl.com>; Mon, 28 Oct 2013 08:10:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level: 
X-Spam-Status: No, score=-2.104 tagged_above=-999 required=5 tests=[AWL=-0.106, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fV0GAKocvZdB for <pim@ietfa.amsl.com>; Mon, 28 Oct 2013 08:10:14 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 6945411E814C for <pim@ietf.org>; Mon, 28 Oct 2013 08:10:14 -0700 (PDT)
X-AuditID: c6180641-b7fe28e000000d82-ad-526e7e55f084
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id B9.88.03458.55E7E625; Mon, 28 Oct 2013 16:10:13 +0100 (CET)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.02.0328.009; Mon, 28 Oct 2013 11:10:13 -0400
From: Mike McBride <mike.mcbride@ericsson.com>
To: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>, Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Thread-Topic: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
Thread-Index: AQHO0c68eVIa22rD30Kay1ePXEfBwJoKHOxggAAdSFA=
Date: Mon, 28 Oct 2013 15:10:12 +0000
Message-ID: <6F5149063CE40341BE7953160A93C5A0D89EC7@eusaamb109.ericsson.se>
References: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com> <bc63bb3bdfbe420cb9c464bf8a8398f7@BY2PR05MB079.namprd05.prod.outlook.com>
In-Reply-To: <bc63bb3bdfbe420cb9c464bf8a8398f7@BY2PR05MB079.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: multipart/alternative; boundary="_000_6F5149063CE40341BE7953160A93C5A0D89EC7eusaamb109ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrCLMWRmVeSWpSXmKPExsUyuXSPt25oXV6QwbyN2hZf781lsvjy8Caz xZGLjSwOzB47Z91l91iy5CeTx/Wmq+wBzFFcNimpOZllqUX6dglcGSdeTWIpONPHWPF65ROW Bsa/tV2MnBwSAiYS7x6cYYGwxSQu3FvPBmILCRxhlFjxi6uLkQvIXs4o0XNwD1gRm4CexOmF zawgtohAucTmvX/YQWxhAR+JR7O+sUDEfSX+rzvC1MXIAWRbScxtrwcJswioSny8uYsJxOYV 8JZo/XWbHWL+HEaJEyebwBZzCoRJrNh9GWwmI9BB30+tAWtgFhCXuPVkPhPEoQISS/acZ4aw RSVePv7HCmErS3yf84gFoj5fYtOX3VDLBCVOznzCMoFRZBaSUbOQlM1CUgYR15FYsPsTG4St LbFs4WtmGPvMgcdMyOILGNlXMXKUFqeW5aYbGW5iBMbUMQk2xx2MCz5ZHmKU5mBREuf98tY5 SEggPbEkNTs1tSC1KL6oNCe1+BAjEwenVANj38qDrx4salpezBh5YOuhpS1NgnpveUImzvdf zNorsPHB/N0GCwJT3YTK7bfOsuuf1sd9XWLdm8i6ZUU/m15xPfrN2iKxNHyr0izv3J2c8jlq jWseZos9+eG8KEXvyAnPKwrX4mOiZrhUrk8Q2bPz6JRNLx4XCZm0PXwZWxzIEfFQhu/bBA8b JZbijERDLeai4kQAtXdomHcCAAA=
Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
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, 28 Oct 2013 15:10:21 -0000

--_000_6F5149063CE40341BE7953160A93C5A0D89EC7eusaamb109ericsso_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Agreed. No rush. But we should be able to receive enough wg feedback, befor=
e our meeting, to make a decision.

I will interpret your feedback as not necessarily being opposed to this wor=
k but that we need to be aware of alternatives which may be better. Looking=
 forward to your presentation.

Thanks,
mike

From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of Jeffr=
ey (Zhaohui) Zhang
Sent: Monday, October 28, 2013 6:27 AM
To: Mike McBride; pim@ietf.org
Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for adoptio=
n

Hi,

We should not rush to a decision before the IETF week.

The drawbacks of the solution have been discussed before.

The draft has two aspects:


1.       Source information flooding in an environment with high resilience=
 requirement

2.       Should we extend BSR to a generic flooding mechanism

For both of them, PIM-Bidir is a very good alternative - after the RP resil=
ience problem is resolved.

In Vancouver I will present a simple enhancement to PIM-Bidir procedures (n=
o signaling extension is required) to address that - http://tools.ietf.org/=
html/draft-zzhang-pim-bidir-rpl-resiliency-00.

Thanks.
Jeffrey

From: pim-bounces@ietf.org<mailto:pim-bounces@ietf.org> [mailto:pim-bounces=
@ietf.org] On Behalf Of Mike McBride
Sent: Friday, October 25, 2013 6:08 PM
To: pim@ietf.org<mailto:pim@ietf.org>
Subject: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption

The authors of draft-wijnands-pim-source-discovery-bsr-03 have requested th=
at we initiate a call for adoption of their draft which they presented in o=
ur last meeting in Berlin. Notes from that presentation are below. Please c=
omment over the next week (before ietf week) on your interest/non-interest =
with adoption of this draft.

http://www.ietf.org/id/draft-wijnands-pim-source-discovery-bsr-03.txt
thanks,
mike

draft-wignands-pim-source-discovery-bsr-03 (Ice)

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

highly redudant mcast network without single point of failure.

Jeffrey: Of the 10k flows how many groups?

Ice: the sources are what's relevant. 10k s,gs. Not introducing a new routi=
ng protocol.

Jeffrey: Could use mospf. pim bidir is another viable approach. With bidir,=
 while the RPA canbe an address that is not tried to any router (the addres=
s would be associated with a LAN), the LAN that the RPA is on could become =
partitioned. When that happens, traffic cannot be exchanged on the LAN betw=
een the partitions, affecting lots of receivers. That's the problem using P=
IM-BIDIR instead of BSR flooing. However, that can be easily resolved by a =
protocol extension. I should be able to publish it for the next IETF meetin=
g. With that resolved, PIM bidir will be a better solution for the targeted=
 deployment scenario.

stig: one issue with bidir is you don't have the optimal path.

operator DT: I like the use case and support.

Hitoshi: flooding is not typically optimal.

Ice: its only using mechanisms that exist today with bsr.

jeffrey: the amount of information is more with today.

Hitoshi: Why not use SAP (I'm not a fan of SAP though)? Whats the meaning o=
f flooding. Use MSDP if interdomain?

lighthouse networks: you mentioned dns, why can't you use that?

Ice; this is a case where you don't know the source. bsr based flooding. no=
t inter domain discussion. Enterprise network.

Mike: applaud any efforts to make multicast more simple. But flooding may b=
e a problem.



1 room interested. 2 operators on draft interested. Mike will poll on list.


--_000_6F5149063CE40341BE7953160A93C5A0D89EC7eusaamb109ericsso_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1889534835;
	mso-list-type:hybrid;
	mso-list-template-ids:421693704 543039676 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.25in;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Agreed. No rush. But we s=
hould be able to receive enough wg feedback, before our meeting, to make a =
decision.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I will interpret your fee=
dback as not necessarily being opposed to this work but that we need to be =
aware of alternatives which may be better. Looking forward
 to your presentation. <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">mike<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> pim-boun=
ces@ietf.org [mailto:pim-bounces@ietf.org]
<b>On Behalf Of </b>Jeffrey (Zhaohui) Zhang<br>
<b>Sent:</b> Monday, October 28, 2013 6:27 AM<br>
<b>To:</b> Mike McBride; pim@ietf.org<br>
<b>Subject:</b> Re: [pim] draft-wijnands-pim-source-discovery-bsr call for =
adoption<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">We should not rush to a d=
ecision before the IETF week.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">The drawbacks of the solu=
tion have been discussed before.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">The draft has two aspects=
:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.25in;text-indent:-.25in=
;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-list:Ign=
ore">1.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Source informatio=
n flooding in an environment with high resilience requirement<o:p></o:p></s=
pan></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.25in;text-indent:-.25in=
;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-list:Ign=
ore">2.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Should we extend =
BSR to a generic flooding mechanism<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">For both of them, PIM-Bid=
ir is a very good alternative &#8211; after the RP resilience problem is re=
solved.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">In Vancouver I will prese=
nt a simple enhancement to PIM-Bidir procedures (no signaling extension is =
required) to address that -
</span><a href=3D"http://tools.ietf.org/html/draft-zzhang-pim-bidir-rpl-res=
iliency-00">http://tools.ietf.org/html/draft-zzhang-pim-bidir-rpl-resilienc=
y-00</a>.<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks.<br>
Jeffrey<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:pim-bounces@ietf.org">pim-bounces@ietf.org</a> [<a href=
=3D"mailto:pim-bounces@ietf.org">mailto:pim-bounces@ietf.org</a>]
<b>On Behalf Of </b>Mike McBride<br>
<b>Sent:</b> Friday, October 25, 2013 6:08 PM<br>
<b>To:</b> <a href=3D"mailto:pim@ietf.org">pim@ietf.org</a><br>
<b>Subject:</b> [pim] draft-wijnands-pim-source-discovery-bsr call for adop=
tion<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">The authors of draft-=
wijnands-pim-source-discovery-bsr-03 have requested that we initiate a call=
 for adoption of their draft which they presented in our last meeting in Be=
rlin. Notes from that presentation are
 below. Please comment over the next week (before ietf week) on your intere=
st/non-interest with adoption of this draft.<br>
<br>
<a href=3D"http://www.ietf.org/id/draft-wijnands-pim-source-discovery-bsr-0=
3.txt">http://www.ietf.org/id/draft-wijnands-pim-source-discovery-bsr-03.tx=
t</a><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">thanks,<br>
mike<o:p></o:p></p>
<pre>draft-wignands-pim-source-discovery-bsr-03 (Ice)<o:p></o:p></pre>
<pre>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p><=
/o:p></pre>
<pre>highly redudant mcast network without single point of failure.&nbsp; <=
o:p></o:p></pre>
<pre>Jeffrey: Of the 10k flows how many groups?<o:p></o:p></pre>
<pre>Ice: the sources are what's relevant. 10k s,gs. Not introducing a new =
routing protocol.<o:p></o:p></pre>
<pre>Jeffrey: Could use mospf. pim bidir is another viable approach. With b=
idir, while the RPA canbe an address that is not tried to any router (the a=
ddress would be associated with a LAN), the LAN that the RPA is on could be=
come partitioned. When that happens, traffic cannot be exchanged on the LAN=
 between the partitions, affecting lots of receivers. That's the problem us=
ing PIM-BIDIR instead of BSR flooing. However, that can be easily resolved =
by a protocol extension. I should be able to publish it for the next IETF m=
eeting. With that resolved, PIM bidir will be a better solution for the tar=
geted deployment scenario.<o:p></o:p></pre>
<pre>stig: one issue with bidir is you don't have the optimal path.<o:p></o=
:p></pre>
<pre>operator DT: I like the use case and support.<o:p></o:p></pre>
<pre>Hitoshi: flooding is not typically optimal.<o:p></o:p></pre>
<pre>Ice: its only using mechanisms that exist today with bsr.<o:p></o:p></=
pre>
<pre>jeffrey: the amount of information is more with today.<o:p></o:p></pre=
>
<pre>Hitoshi: Why not use SAP (I'm not a fan of SAP though)? Whats the mean=
ing of flooding. Use MSDP if interdomain?<o:p></o:p></pre>
<pre>lighthouse networks: you mentioned dns, why can't you use that?<o:p></=
o:p></pre>
<pre>Ice; this is a case where you don't know the source. bsr based floodin=
g. not inter domain discussion. Enterprise network.<o:p></o:p></pre>
<pre>Mike: applaud any efforts to make multicast more simple. But flooding =
may be a problem.<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>1 room interested. 2 operators on draft interested. Mike will poll on =
list.<o:p></o:p></pre>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_6F5149063CE40341BE7953160A93C5A0D89EC7eusaamb109ericsso_--

From lenny@juniper.net  Mon Oct 28 12:08:29 2013
Return-Path: <lenny@juniper.net>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EC1411E8295 for <pim@ietfa.amsl.com>; Mon, 28 Oct 2013 12:08:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.199
X-Spam-Level: 
X-Spam-Status: No, score=-102.199 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_12=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iAIg8ykEfzqw for <pim@ietfa.amsl.com>; Mon, 28 Oct 2013 12:08:24 -0700 (PDT)
Received: from db9outboundpool.messaging.microsoft.com (mail-db9lp0253.outbound.messaging.microsoft.com [213.199.154.253]) by ietfa.amsl.com (Postfix) with ESMTP id 93B6811E81D7 for <pim@ietf.org>; Mon, 28 Oct 2013 12:08:22 -0700 (PDT)
Received: from mail22-db9-R.bigfish.com (10.174.16.247) by DB9EHSOBE021.bigfish.com (10.174.14.84) with Microsoft SMTP Server id 14.1.225.22; Mon, 28 Oct 2013 19:08:21 +0000
Received: from mail22-db9 (localhost [127.0.0.1])	by mail22-db9-R.bigfish.com (Postfix) with ESMTP id BFA942400F8; Mon, 28 Oct 2013 19:08:21 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:66.129.224.51; KIP:(null); UIP:(null); IPV:NLI; H:P-EMF01-SAC.jnpr.net; RD:none; EFVD:NLI
X-SpamScore: -18
X-BigFish: VPS-18(zzdb82h98dIzz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6h1082kz8dhz1033IL17326ah8275dh1de097h186068hz2fh2a8h839h944hd25hf0ah11b5h121eh1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h16a6h1758h18e1h1946h19b5h1ad9h1b0ah1b2fh1fb3h1d0ch1d2eh1d3fh1de2h1dfeh1dffh1fe8h1ff5h1155h)
Received-SPF: pass (mail22-db9: domain of juniper.net designates 66.129.224.51 as permitted sender) client-ip=66.129.224.51; envelope-from=lenny@juniper.net; helo=P-EMF01-SAC.jnpr.net ; SAC.jnpr.net ; 
Received: from mail22-db9 (localhost.localdomain [127.0.0.1]) by mail22-db9 (MessageSwitch) id 1382987299337229_3865; Mon, 28 Oct 2013 19:08:19 +0000 (UTC)
Received: from DB9EHSMHS011.bigfish.com (unknown [10.174.16.231])	by mail22-db9.bigfish.com (Postfix) with ESMTP id 4533C3A005A; Mon, 28 Oct 2013 19:08:19 +0000 (UTC)
Received: from P-EMF01-SAC.jnpr.net (66.129.224.51) by DB9EHSMHS011.bigfish.com (10.174.14.21) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 28 Oct 2013 19:08:19 +0000
Received: from magenta.juniper.net (172.17.27.123) by P-EMF01-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.146.0; Mon, 28 Oct 2013 12:08:16 -0700
Received: from eng-mail01.juniper.net (eng-mail01.juniper.net [172.17.28.114]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id r9SJ8AL64449; Mon, 28 Oct 2013 12:08:10 -0700 (PDT)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id 950471148F;  Mon, 28 Oct 2013 12:08:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id 8AC271148D; Mon, 28 Oct 2013 12:08:08 -0700 (PDT)
Date: Mon, 28 Oct 2013 12:08:08 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: Mike McBride <mmcbride7@gmail.com>
In-Reply-To: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com>
Message-ID: <20131028115859.L5138@eng-mail01.juniper.net>
References: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
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, 28 Oct 2013 19:08:29 -0000

I think this is a pointless step in the wrong direction.  The last 15 
years have shown us that network-based source discovery was a bad idea- we 
should be deprecating ASM and pushing SSM as the way forward.

This proposal is a marginal improvement over the existing RP/shared tree 
mechanism from a simplicity standpoint, but it can't possibly scale for 
interdomain/large deployments.  Maybe, this might have been a useful 
conversation in 1996.  But today, this is a solution in search of a 
problem.

We already have a solution that eliminates RPs, shared trees and doesn't 
scale: PIM-DM.  We don't another.

-Lenny

On Fri, 25 Oct 2013, Mike McBride wrote:

-) The authors of draft-wijnands-pim-source-discovery-bsr-03 have requested
-) that we initiate a call for adoption of their draft which they presented in
-) our last meeting in Berlin. Notes from that presentation are below. Please
-) comment over the next week (before ietf week) on your interest/non-interest
-) with adoption of this draft.
-) 
-) http://www.ietf.org/id/draft-wijnands-pim-source-discovery-bsr-03.txt
-) 
-) thanks,
-) mike
-) 
-) draft-wignands-pim-source-discovery-bsr-03 (Ice)
-) ==============================================
-) highly redudant mcast network without single point of failure.
-) Jeffrey: Of the 10k flows how many groups?
-) Ice: the sources are what's relevant. 10k s,gs. Not introducing a new
-) routing protocol.
-) Jeffrey: Could use mospf. pim bidir is another viable approach. With
-) bidir, while the RPA canbe an address that is not tried to any router
-) (the address would be associated with a LAN), the LAN that the RPA is
-) on could become partitioned. When that happens, traffic cannot be
-) exchanged on the LAN between the partitions, affecting lots of
-) receivers. That's the problem using PIM-BIDIR instead of BSR flooing.
-) However, that can be easily resolved by a protocol extension. I should
-) be able to publish it for the next IETF meeting. With that resolved,
-) PIM bidir will be a better solution for the targeted deployment
-) scenario.
-) stig: one issue with bidir is you don't have the optimal path.
-) operator DT: I like the use case and support.
-) Hitoshi: flooding is not typically optimal.
-) Ice: its only using mechanisms that exist today with bsr.
-) jeffrey: the amount of information is more with today.
-) Hitoshi: Why not use SAP (I'm not a fan of SAP though)? Whats the
-) meaning of flooding. Use MSDP if interdomain?
-) lighthouse networks: you mentioned dns, why can't you use that?
-) Ice; this is a case where you don't know the source. bsr based
-) flooding. not inter domain discussion. Enterprise network.
-) Mike: applaud any efforts to make multicast more simple. But flooding
-) may be a problem.
-) 
-) 1 room interested. 2 operators on draft interested. Mike will poll on list.
-) 


From ice@cisco.com  Mon Oct 28 12:45:10 2013
Return-Path: <ice@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 6B17A21F9F45 for <pim@ietfa.amsl.com>; Mon, 28 Oct 2013 12:45:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level: 
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jMphXXTb7NB1 for <pim@ietfa.amsl.com>; Mon, 28 Oct 2013 12:44:58 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 64E1A21F9D0A for <pim@ietf.org>; Mon, 28 Oct 2013 12:44:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4061; q=dns/txt; s=iport; t=1382989499; x=1384199099; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=MOo4RcpdhdcZdb27Y3MpXSYOhHORm8n97iatXWYTDw4=; b=BFyC7txu8CEPISQZyK/yMjgeqY4Y7kVm27nfzKbgtxMOzJ/fdF0miFl3 ARqMm8Y5wZ1FydHddHuBVUwnfC92eNPyvI3U5SJeWLah1PZaeaUY5VXmT Xc3emH8yDHrImQmuI4stN1uJEIOMr5XOsX/Q4RUWtB66Y5+Hioot8TMx8 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArAMAKK9blKQ/khN/2dsb2JhbABZgwc4qkuUbYEpFnSCJQEBAQMBAQEBGlELBQsLEQQBASgHJx8JCAYTCRKHZgYNuD2PIjMHgx+BDQOYCoEvkFiDJzs
X-IronPort-AV: E=Sophos;i="4.93,587,1378857600"; d="scan'208";a="18601303"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-3.cisco.com with ESMTP; 28 Oct 2013 19:44:53 +0000
Received: from ams-iwijnand-8712.cisco.com (ams-iwijnand-8712.cisco.com [10.55.191.147]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r9SJikir009464 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 28 Oct 2013 19:44:48 GMT
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: IJsbrand Wijnands <ice@cisco.com>
In-Reply-To: <bc63bb3bdfbe420cb9c464bf8a8398f7@BY2PR05MB079.namprd05.prod.outlook.com>
Date: Mon, 28 Oct 2013 20:44:46 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <60835226-85FD-429B-BCC7-09150BE7F28C@cisco.com>
References: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com> <bc63bb3bdfbe420cb9c464bf8a8398f7@BY2PR05MB079.namprd05.prod.outlook.com>
To: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
X-Mailer: Apple Mail (2.1499)
Cc: Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
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, 28 Oct 2013 19:45:10 -0000

Hi Jeffrey,

> For both of them, PIM-Bidir is a very good alternative =96 after the =
RP resilience problem is resolved.
> =20
> In Vancouver I will present a simple enhancement to PIM-Bidir =
procedures (no signaling extension is required) to address that - =
http://tools.ietf.org/html/draft-zzhang-pim-bidir-rpl-resiliency-00.

"Simple" is in the eye of the beholder ;-)

I've just read your draft, I would not say this is simple. When a =
phantom RP is not owned by any particular router, this is a new can of =
worms. It opens the door for loops because multiple routers may =
temporality claim ownership of the phantom address at the same time. The =
phantom address works well if the network where the phantom address is =
located is the root of the networks that connect to it. There are =
operators that are discarding Bidir how it is today due to the risk of =
creating transient loops, so lets be very careful when making the RP =
even more random.

The problem we are solving would require all the routers in the network =
to participate in the functionality you describe in your draft. Its =
great to explore this idea in IETF, but this idea if far from cooked to =
be considered as alternative to draft-wijnands-pim-source-discovery-bsr. =
Either-way, I'm not against if it does, the market will decide.

Thx,

Ice.

> =20
> Thanks.
> Jeffrey
> =20
> From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of =
Mike McBride
> Sent: Friday, October 25, 2013 6:08 PM
> To: pim@ietf.org
> Subject: [pim] draft-wijnands-pim-source-discovery-bsr call for =
adoption
> =20
> The authors of draft-wijnands-pim-source-discovery-bsr-03 have =
requested that we initiate a call for adoption of their draft which they =
presented in our last meeting in Berlin. Notes from that presentation =
are below. Please comment over the next week (before ietf week) on your =
interest/non-interest with adoption of this draft.
>=20
> http://www.ietf.org/id/draft-wijnands-pim-source-discovery-bsr-03.txt
>=20
> thanks,
> mike
>=20
> draft-wignands-pim-source-discovery-bsr-03 (Ice)
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> highly redudant mcast network without single point of failure. =20
> Jeffrey: Of the 10k flows how many groups?
> Ice: the sources are what's relevant. 10k s,gs. Not introducing a new =
routing protocol.
> Jeffrey: Could use mospf. pim bidir is another viable approach. With =
bidir, while the RPA canbe an address that is not tried to any router =
(the address would be associated with a LAN), the LAN that the RPA is on =
could become partitioned. When that happens, traffic cannot be exchanged =
on the LAN between the partitions, affecting lots of receivers. That's =
the problem using PIM-BIDIR instead of BSR flooing. However, that can be =
easily resolved by a protocol extension. I should be able to publish it =
for the next IETF meeting. With that resolved, PIM bidir will be a =
better solution for the targeted deployment scenario.
> stig: one issue with bidir is you don't have the optimal path.
> operator DT: I like the use case and support.
> Hitoshi: flooding is not typically optimal.
> Ice: its only using mechanisms that exist today with bsr.
> jeffrey: the amount of information is more with today.
> Hitoshi: Why not use SAP (I'm not a fan of SAP though)? Whats the =
meaning of flooding. Use MSDP if interdomain?
> lighthouse networks: you mentioned dns, why can't you use that?
> Ice; this is a case where you don't know the source. bsr based =
flooding. not inter domain discussion. Enterprise network.
> Mike: applaud any efforts to make multicast more simple. But flooding =
may be a problem.
> =20
> 1 room interested. 2 operators on draft interested. Mike will poll on =
list.
> =20
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim


From zzhang@juniper.net  Mon Oct 28 13:01:03 2013
Return-Path: <zzhang@juniper.net>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 013DD11E814C for <pim@ietfa.amsl.com>; Mon, 28 Oct 2013 13:01:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, J_CHICKENPOX_12=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mnk+s1EqLyLt for <pim@ietfa.amsl.com>; Mon, 28 Oct 2013 13:00:57 -0700 (PDT)
Received: from db9outboundpool.messaging.microsoft.com (mail-db9lp0249.outbound.messaging.microsoft.com [213.199.154.249]) by ietfa.amsl.com (Postfix) with ESMTP id 5F35F11E8189 for <pim@ietf.org>; Mon, 28 Oct 2013 13:00:53 -0700 (PDT)
Received: from mail13-db9-R.bigfish.com (10.174.16.230) by DB9EHSOBE026.bigfish.com (10.174.14.89) with Microsoft SMTP Server id 14.1.225.22; Mon, 28 Oct 2013 20:00:52 +0000
Received: from mail13-db9 (localhost [127.0.0.1])	by mail13-db9-R.bigfish.com (Postfix) with ESMTP id 6C31740426; Mon, 28 Oct 2013 20:00:52 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT001.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -21
X-BigFish: VPS-21(zz9371I542I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL17326ah8275dh1de097h186068hz2fh2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h2216h9a9j1155h)
Received-SPF: pass (mail13-db9: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=zzhang@juniper.net; helo=BL2PRD0510HT001.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(199002)(189002)(13464003)(51704005)(377454003)(54356001)(53806001)(85306002)(51856001)(79102001)(54316002)(56776001)(76482001)(77982001)(83072001)(59766001)(74316001)(15975445006)(46102001)(74366001)(74876001)(66066001)(15202345003)(74706001)(81342001)(50986001)(47976001)(19580405001)(83322001)(49866001)(47736001)(80976001)(19580395003)(47446002)(74502001)(74662001)(81816001)(4396001)(69226001)(76796001)(81542001)(76786001)(81686001)(33646001)(76576001)(77096001)(63696002)(56816003)(65816001)(80022001)(31966008)(87266001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BY2PR05MB077; H:BY2PR05MB079.namprd05.prod.outlook.com; CLIP:66.129.241.17; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail13-db9 (localhost.localdomain [127.0.0.1]) by mail13-db9 (MessageSwitch) id 1382990450777425_16199; Mon, 28 Oct 2013 20:00:50 +0000 (UTC)
Received: from DB9EHSMHS020.bigfish.com (unknown [10.174.16.230])	by mail13-db9.bigfish.com (Postfix) with ESMTP id B96F22A00EF; Mon, 28 Oct 2013 20:00:50 +0000 (UTC)
Received: from BL2PRD0510HT001.namprd05.prod.outlook.com (157.56.240.101) by DB9EHSMHS020.bigfish.com (10.174.14.30) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 28 Oct 2013 20:00:50 +0000
Received: from BY2PR05MB077.namprd05.prod.outlook.com (10.242.38.11) by BL2PRD0510HT001.namprd05.prod.outlook.com (10.255.100.36) with Microsoft SMTP Server (TLS) id 14.16.371.2; Mon, 28 Oct 2013 20:00:46 +0000
Received: from BY2PR05MB079.namprd05.prod.outlook.com (10.242.38.16) by BY2PR05MB077.namprd05.prod.outlook.com (10.242.38.11) with Microsoft SMTP Server (TLS) id 15.0.810.5; Mon, 28 Oct 2013 20:00:43 +0000
Received: from BY2PR05MB079.namprd05.prod.outlook.com ([169.254.8.16]) by BY2PR05MB079.namprd05.prod.outlook.com ([169.254.8.16]) with mapi id 15.00.0810.005; Mon, 28 Oct 2013 20:00:43 +0000
From: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
To: IJsbrand Wijnands <ice@cisco.com>
Thread-Topic: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
Thread-Index: AQHO0c68DdGwj3jORkCcwV771ygo/5oKHOxggABrxQCAAAEdoA==
Date: Mon, 28 Oct 2013 20:00:42 +0000
Message-ID: <75a2ddc0cd374e3a88c5b4548618f338@BY2PR05MB079.namprd05.prod.outlook.com>
References: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com> <bc63bb3bdfbe420cb9c464bf8a8398f7@BY2PR05MB079.namprd05.prod.outlook.com> <60835226-85FD-429B-BCC7-09150BE7F28C@cisco.com>
In-Reply-To: <60835226-85FD-429B-BCC7-09150BE7F28C@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.17]
x-forefront-prvs: 0013079544
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
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, 28 Oct 2013 20:01:03 -0000

Ice,

> -----Original Message-----
> From: IJsbrand Wijnands [mailto:ice@cisco.com]
> Sent: Monday, October 28, 2013 3:45 PM
> To: Jeffrey (Zhaohui) Zhang
> Cc: Mike McBride; pim@ietf.org
> Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for
> adoption
>=20
> Hi Jeffrey,
>=20
> > For both of them, PIM-Bidir is a very good alternative - after the RP
> resilience problem is resolved.
> >
> > In Vancouver I will present a simple enhancement to PIM-Bidir
> procedures (no signaling extension is required) to address that -
> http://tools.ietf.org/html/draft-zzhang-pim-bidir-rpl-resiliency-00.
>=20
> "Simple" is in the eye of the beholder ;-)
>=20
> I've just read your draft, I would not say this is simple. When a
> phantom RP is not owned by any particular router, this is a new can of
> worms. It opens the door for loops because multiple routers may
> temporality claim ownership of the phantom address at the same time.

If the RPL partitions, the (entire) network will have several RPLs, leading=
 to isolation but should not cause loops. The draft actually address that e=
xisting problem by electing an active RPL partition.

> The phantom address works well if the network where the phantom address
> is located is the root of the networks that connect to it. There are
> operators that are discarding Bidir how it is today due to the risk of
> creating transient loops, so lets be very careful when making the RP
> even more random.
>=20
> The problem we are solving would require all the routers in the network
> to participate in the functionality you describe in your draft. Its

Just the routers on the RPL need to participate. For comparison, BSR floodi=
ng source information requires every router to do it :-)

Thanks.
Jeffrey

> great to explore this idea in IETF, but this idea if far from cooked to
> be considered as alternative to draft-wijnands-pim-source-discovery-bsr.
> Either-way, I'm not against if it does, the market will decide.
>=20
> Thx,
>=20
> Ice.
>=20
> >
> > Thanks.
> > Jeffrey
> >
> > From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of
> Mike McBride
> > Sent: Friday, October 25, 2013 6:08 PM
> > To: pim@ietf.org
> > Subject: [pim] draft-wijnands-pim-source-discovery-bsr call for
> adoption
> >
> > The authors of draft-wijnands-pim-source-discovery-bsr-03 have
> requested that we initiate a call for adoption of their draft which
> they presented in our last meeting in Berlin. Notes from that
> presentation are below. Please comment over the next week (before ietf
> week) on your interest/non-interest with adoption of this draft.
> >
> > http://www.ietf.org/id/draft-wijnands-pim-source-discovery-bsr-03.txt
> >
> > thanks,
> > mike
> >
> > draft-wignands-pim-source-discovery-bsr-03 (Ice)
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > highly redudant mcast network without single point of failure.
> > Jeffrey: Of the 10k flows how many groups?
> > Ice: the sources are what's relevant. 10k s,gs. Not introducing a new
> routing protocol.
> > Jeffrey: Could use mospf. pim bidir is another viable approach. With
> bidir, while the RPA canbe an address that is not tried to any router
> (the address would be associated with a LAN), the LAN that the RPA is
> on could become partitioned. When that happens, traffic cannot be
> exchanged on the LAN between the partitions, affecting lots of
> receivers. That's the problem using PIM-BIDIR instead of BSR flooing.
> However, that can be easily resolved by a protocol extension. I should
> be able to publish it for the next IETF meeting. With that resolved,
> PIM bidir will be a better solution for the targeted deployment
> scenario.
> > stig: one issue with bidir is you don't have the optimal path.
> > operator DT: I like the use case and support.
> > Hitoshi: flooding is not typically optimal.
> > Ice: its only using mechanisms that exist today with bsr.
> > jeffrey: the amount of information is more with today.
> > Hitoshi: Why not use SAP (I'm not a fan of SAP though)? Whats the
> meaning of flooding. Use MSDP if interdomain?
> > lighthouse networks: you mentioned dns, why can't you use that?
> > Ice; this is a case where you don't know the source. bsr based
> flooding. not inter domain discussion. Enterprise network.
> > Mike: applaud any efforts to make multicast more simple. But flooding
> may be a problem.
> >
> > 1 room interested. 2 operators on draft interested. Mike will poll on
> list.
> >
> > _______________________________________________
> > pim mailing list
> > pim@ietf.org
> > https://www.ietf.org/mailman/listinfo/pim
>=20
>=20



From ice@cisco.com  Mon Oct 28 13:04:34 2013
Return-Path: <ice@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 6E5E711E81C3 for <pim@ietfa.amsl.com>; Mon, 28 Oct 2013 13:04:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.524
X-Spam-Level: 
X-Spam-Status: No, score=-10.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YB7X-xRNdahg for <pim@ietfa.amsl.com>; Mon, 28 Oct 2013 13:04:29 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 13F9B21F9EED for <pim@ietf.org>; Mon, 28 Oct 2013 13:04:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1123; q=dns/txt; s=iport; t=1382990669; x=1384200269; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=01WdfUUoOseg4Kkf091ZeR3lE2lIjusPrsOgU7M2H2w=; b=kSQHBb+P/CzG2j7RYNqdweNPE35uzEnxblBkjaaxt0nbKj/+nGm08SHK l15atheDhQnJe8qvX09Q2ydJR7Z0pVlQb6wemjlchUBVZU9wEreIZApJZ tFSFBVxzTvyanhS9dQh51EA5PIioIVKIDBcyfbzykvyXOMDgCyFp1S1TX U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai0FAFTCblKQ/khR/2dsb2JhbABZgwe/cIEpFnSCJQEBAQMBHR0/BQsLDjhXBi6HZga4PI8iMweDH4ENA5gKkgeDJzs
X-IronPort-AV: E=Sophos;i="4.93,587,1378857600"; d="scan'208";a="87726185"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-2.cisco.com with ESMTP; 28 Oct 2013 20:04:27 +0000
Received: from ams-iwijnand-8712.cisco.com (ams-iwijnand-8712.cisco.com [10.55.191.147]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r9SK4MwY002583 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 28 Oct 2013 20:04:24 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: IJsbrand Wijnands <ice@cisco.com>
In-Reply-To: <20131028115859.L5138@eng-mail01.juniper.net>
Date: Mon, 28 Oct 2013 21:04:22 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <2AE7C375-B94C-4286-BC5C-245192D2574D@cisco.com>
References: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com> <20131028115859.L5138@eng-mail01.juniper.net>
To: Leonard Giuliano <lenny@juniper.net>
X-Mailer: Apple Mail (2.1499)
Cc: Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
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, 28 Oct 2013 20:04:34 -0000

Hi Lenny,

> I think this is a pointless step in the wrong direction.  The last 15=20=

> years have shown us that network-based source discovery was a bad =
idea- we=20
> should be deprecating ASM and pushing SSM as the way forward.

We've been saying that for at least 10 years now. However, solutions are =
still being developed to support PIM-SM, like =
draft-rekhter-mpls-pim-sm-over-mldp, which according to your statement =
above is a step in the wrong direction. I don't disagree with that.

> This proposal is a marginal improvement over the existing RP/shared =
tree=20
> mechanism from a simplicity standpoint, but it can't possibly scale =
for=20
> interdomain/large deployments.  Maybe, this might have been a useful=20=


Agreed, and that is not the intention of this draft. This solves a very =
specific problem for sub-set of the customers, but it solves a real =
problem

> conversation in 1996.  But today, this is a solution in search of a=20
> problem.

Lets not give the customer a solution to a problem that he does not need =
to solve, like Inter-domain.

Thx,

Ice.



From lenny@juniper.net  Mon Oct 28 13:52:46 2013
Return-Path: <lenny@juniper.net>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0F1111E81CE for <pim@ietfa.amsl.com>; Mon, 28 Oct 2013 13:52:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.079
X-Spam-Level: 
X-Spam-Status: No, score=-103.079 tagged_above=-999 required=5 tests=[AWL=0.520, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZN+rgEif-cIC for <pim@ietfa.amsl.com>; Mon, 28 Oct 2013 13:52:40 -0700 (PDT)
Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe002.messaging.microsoft.com [213.199.154.205]) by ietfa.amsl.com (Postfix) with ESMTP id 5340411E80F7 for <pim@ietf.org>; Mon, 28 Oct 2013 13:52:40 -0700 (PDT)
Received: from mail4-am1-R.bigfish.com (10.3.201.251) by AM1EHSOBE008.bigfish.com (10.3.204.28) with Microsoft SMTP Server id 14.1.225.22; Mon, 28 Oct 2013 20:52:38 +0000
Received: from mail4-am1 (localhost [127.0.0.1])	by mail4-am1-R.bigfish.com (Postfix) with ESMTP id D6B9C1600BF; Mon, 28 Oct 2013 20:52:38 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:66.129.224.54; KIP:(null); UIP:(null); IPV:NLI; H:P-EMF01-SAC.jnpr.net; RD:none; EFVD:NLI
X-SpamScore: 2
X-BigFish: VPS2(zzdb82h98dIzz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6h1082kzzz2fh2a8h839h944hd25hf0ah11b5h121eh1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h16a6h1758h18e1h1946h19b5h1ad9h1b0ah1b2fh1fb3h1d0ch1d2eh1d3fh1de2h1dfeh1dffh1fe8h1ff5h2216h1155h)
Received-SPF: pass (mail4-am1: domain of juniper.net designates 66.129.224.54 as permitted sender) client-ip=66.129.224.54; envelope-from=lenny@juniper.net; helo=P-EMF01-SAC.jnpr.net ; SAC.jnpr.net ; 
Received: from mail4-am1 (localhost.localdomain [127.0.0.1]) by mail4-am1 (MessageSwitch) id 1382993556451619_5003; Mon, 28 Oct 2013 20:52:36 +0000 (UTC)
Received: from AM1EHSMHS005.bigfish.com (unknown [10.3.201.239])	by mail4-am1.bigfish.com (Postfix) with ESMTP id 6A8E522004C; Mon, 28 Oct 2013 20:52:36 +0000 (UTC)
Received: from P-EMF01-SAC.jnpr.net (66.129.224.54) by AM1EHSMHS005.bigfish.com (10.3.207.105) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 28 Oct 2013 20:52:36 +0000
Received: from magenta.juniper.net (172.17.27.123) by P-EMF01-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.146.0; Mon, 28 Oct 2013 13:52:33 -0700
Received: from eng-mail01.juniper.net (eng-mail01.juniper.net [172.17.28.114]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id r9SKqWL24488; Mon, 28 Oct 2013 13:52:32 -0700 (PDT)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id C1DB511446;  Mon, 28 Oct 2013 13:52:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id A65B01141B; Mon, 28 Oct 2013 13:52:27 -0700 (PDT)
Date: Mon, 28 Oct 2013 13:52:27 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: IJsbrand Wijnands <ice@cisco.com>
In-Reply-To: <2AE7C375-B94C-4286-BC5C-245192D2574D@cisco.com>
Message-ID: <20131028134708.C5138@eng-mail01.juniper.net>
References: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com> <20131028115859.L5138@eng-mail01.juniper.net> <2AE7C375-B94C-4286-BC5C-245192D2574D@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
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, 28 Oct 2013 20:52:46 -0000

How about the last point: if you want to avoid shared trees, RPs, register 
messages and don't want something that scales, why is dense mode not 
sufficient?  With state refresh, you flood the source info.


On Mon, 28 Oct 2013, IJsbrand Wijnands wrote:

-) Hi Lenny,
-) 
-) > I think this is a pointless step in the wrong direction.  The last 15 
-) > years have shown us that network-based source discovery was a bad idea- we 
-) > should be deprecating ASM and pushing SSM as the way forward.
-) 
-) We've been saying that for at least 10 years now. However, solutions are still being developed to support PIM-SM, like draft-rekhter-mpls-pim-sm-over-mldp, which according to your statement above is a step in the wrong direction. I don't disagree with that.
-) 
-) > This proposal is a marginal improvement over the existing RP/shared tree 
-) > mechanism from a simplicity standpoint, but it can't possibly scale for 
-) > interdomain/large deployments.  Maybe, this might have been a useful 
-) 
-) Agreed, and that is not the intention of this draft. This solves a very specific problem for sub-set of the customers, but it solves a real problem
-) 
-) > conversation in 1996.  But today, this is a solution in search of a 
-) > problem.
-) 
-) Lets not give the customer a solution to a problem that he does not need to solve, like Inter-domain.
-) 
-) Thx,
-) 
-) Ice.
-) 
-) 
-) 


From ice@cisco.com  Tue Oct 29 02:31:19 2013
Return-Path: <ice@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 9166711E8169 for <pim@ietfa.amsl.com>; Tue, 29 Oct 2013 02:31:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.541
X-Spam-Level: 
X-Spam-Status: No, score=-9.541 tagged_above=-999 required=5 tests=[AWL=-0.938, BAYES_00=-2.599, J_CHICKENPOX_12=0.6, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id za2MQnUWPtma for <pim@ietfa.amsl.com>; Tue, 29 Oct 2013 02:31:15 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id C187A21F9EAF for <pim@ietf.org>; Tue, 29 Oct 2013 02:30:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6394; q=dns/txt; s=iport; t=1383039056; x=1384248656; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=aDkmr/yoHEXdSYISqPHlWCTmrFy9W2tQDitNOGG0UTw=; b=aO+nafl/7Jz4vVtVvRbI4cUR/r7xO+Ai8VwaqfEz013iL7Y8GJDZQxSf kfpWTV2GWIhURSIX2MOIO39Vl0tRyfNGXkznf9hGi+j/38oVb/uInFJ6l J/bkx0pdeb891iXRs4eFst82fCN5c5zMmdmb5jAiugtz4VL8uWf7wulSB 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AloKAOt/b1KQ/khL/2dsb2JhbABZgwc4qxyUaIEnFnSCJQEBAQMBAQEBGh00CxALEQQBASgHJx8JCAYTCRKHZgYNuQaPFDMHgx+BDQOYCpIIgyc7
X-IronPort-AV: E=Sophos;i="4.93,591,1378857600"; d="scan'208";a="87742145"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 29 Oct 2013 09:30:47 +0000
Received: from ams-iwijnand-8712.cisco.com (ams-iwijnand-8712.cisco.com [10.55.191.147]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r9T9Ugr6010135 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 29 Oct 2013 09:30:44 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: IJsbrand Wijnands <ice@cisco.com>
In-Reply-To: <75a2ddc0cd374e3a88c5b4548618f338@BY2PR05MB079.namprd05.prod.outlook.com>
Date: Tue, 29 Oct 2013 10:30:42 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <C63CD9AF-03D7-4375-9BA9-D3A1B1FA3A3D@cisco.com>
References: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com> <bc63bb3bdfbe420cb9c464bf8a8398f7@BY2PR05MB079.namprd05.prod.outlook.com> <60835226-85FD-429B-BCC7-09150BE7F28C@cisco.com> <75a2ddc0cd374e3a88c5b4548618f338@BY2PR05MB079.namprd05.prod.outlook.com>
To: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
X-Mailer: Apple Mail (2.1499)
Cc: Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
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, 29 Oct 2013 09:31:19 -0000

Jeffrey,

An phantom RP is useful if the RPA is on an RPL that is an Ethernet, or =
even better, a cloud, like MPLS for example. In your proposal it seems =
there is very little benefit since you have no view on the topology how =
the ad-hoc network is going to look like, and if there will be any =
ethernet links to begin with. Since the allocation and activation of the =
Active Partition is not pre-determind (I believe ultimately based on =
lowest IP address), there is no guarantee that this will provide you any =
additional protection. If the Active partition is over a P2P link, and =
one of the routers goes down, the link goes down too. This is just as =
good/bad as if you would be using a real RPA. Would your proposal not be =
simplified if we define the following rule; "The lowest /32 (Router ID) =
in the Routing Table is the RPA"?

>> I've just read your draft, I would not say this is simple. When a
>> phantom RP is not owned by any particular router, this is a new can =
of
>> worms. It opens the door for loops because multiple routers may
>> temporality claim ownership of the phantom address at the same time.
>=20
> If the RPL partitions, the (entire) network will have several RPLs, =
leading to isolation but should not cause loops. The draft actually =
address that existing problem by electing an active RPL partition.

And what if the network heals? The fact that the Active partitioned can =
move around the network and is based on election procedures, it looks to =
me that opens up additional race conditions to create loops.=20

>> The phantom address works well if the network where the phantom =
address
>> is located is the root of the networks that connect to it. There are
>> operators that are discarding Bidir how it is today due to the risk =
of
>> creating transient loops, so lets be very careful when making the RP
>> even more random.
>>=20
>> The problem we are solving would require all the routers in the =
network
>> to participate in the functionality you describe in your draft. Its
>=20
> Just the routers on the RPL need to participate. For comparison, BSR =
flooding source information requires every router to do it :-)

That is not a good comparison, BSR flooding a packet is not the same as =
participating in election procedures when a link/node goes down.

While I think your proposal could work, you still run into issues due to =
PIM Bidir, and will not provide the same level of  redundancy we're =
looking for in a ad-hoc network.

The location of the Active partitioned (Phantom RPA) can end up in a =
part of the network that is very inefficient. This goes back to the ever =
lasting question, where do I place the RP, but this time is pretty much =
random. The RPA (or router to the RPL) goes down, existing flows are =
effected and traffic is interrupted. This is because Bidir traffic flows =
along the path to the RPA. This is a single point of failure. With =
traditional PIM-SM, if the RPA goes down, this does not nessesarily =
effect existing forwarding since its along the shortest path (assuming =
the RPA is not in the path). Only new senders are effected for the time =
the RP is down and re-elected.

Thx,

Ice.

>=20
> Thanks.
> Jeffrey
>=20
>> great to explore this idea in IETF, but this idea if far from cooked =
to
>> be considered as alternative to =
draft-wijnands-pim-source-discovery-bsr.
>> Either-way, I'm not against if it does, the market will decide.
>>=20
>> Thx,
>>=20
>> Ice.
>>=20
>>>=20
>>> Thanks.
>>> Jeffrey
>>>=20
>>> From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf =
Of
>> Mike McBride
>>> Sent: Friday, October 25, 2013 6:08 PM
>>> To: pim@ietf.org
>>> Subject: [pim] draft-wijnands-pim-source-discovery-bsr call for
>> adoption
>>>=20
>>> The authors of draft-wijnands-pim-source-discovery-bsr-03 have
>> requested that we initiate a call for adoption of their draft which
>> they presented in our last meeting in Berlin. Notes from that
>> presentation are below. Please comment over the next week (before =
ietf
>> week) on your interest/non-interest with adoption of this draft.
>>>=20
>>> =
http://www.ietf.org/id/draft-wijnands-pim-source-discovery-bsr-03.txt
>>>=20
>>> thanks,
>>> mike
>>>=20
>>> draft-wignands-pim-source-discovery-bsr-03 (Ice)
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>> highly redudant mcast network without single point of failure.
>>> Jeffrey: Of the 10k flows how many groups?
>>> Ice: the sources are what's relevant. 10k s,gs. Not introducing a =
new
>> routing protocol.
>>> Jeffrey: Could use mospf. pim bidir is another viable approach. With
>> bidir, while the RPA canbe an address that is not tried to any router
>> (the address would be associated with a LAN), the LAN that the RPA is
>> on could become partitioned. When that happens, traffic cannot be
>> exchanged on the LAN between the partitions, affecting lots of
>> receivers. That's the problem using PIM-BIDIR instead of BSR flooing.
>> However, that can be easily resolved by a protocol extension. I =
should
>> be able to publish it for the next IETF meeting. With that resolved,
>> PIM bidir will be a better solution for the targeted deployment
>> scenario.
>>> stig: one issue with bidir is you don't have the optimal path.
>>> operator DT: I like the use case and support.
>>> Hitoshi: flooding is not typically optimal.
>>> Ice: its only using mechanisms that exist today with bsr.
>>> jeffrey: the amount of information is more with today.
>>> Hitoshi: Why not use SAP (I'm not a fan of SAP though)? Whats the
>> meaning of flooding. Use MSDP if interdomain?
>>> lighthouse networks: you mentioned dns, why can't you use that?
>>> Ice; this is a case where you don't know the source. bsr based
>> flooding. not inter domain discussion. Enterprise network.
>>> Mike: applaud any efforts to make multicast more simple. But =
flooding
>> may be a problem.
>>>=20
>>> 1 room interested. 2 operators on draft interested. Mike will poll =
on
>> list.
>>>=20
>>> _______________________________________________
>>> pim mailing list
>>> pim@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pim
>>=20
>>=20
>=20
>=20


From ice@cisco.com  Tue Oct 29 02:43:12 2013
Return-Path: <ice@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 4F15F11E81E8 for <pim@ietfa.amsl.com>; Tue, 29 Oct 2013 02:43:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.383
X-Spam-Level: 
X-Spam-Status: No, score=-10.383 tagged_above=-999 required=5 tests=[AWL=0.216, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DOzhELvra8fH for <pim@ietfa.amsl.com>; Tue, 29 Oct 2013 02:43:07 -0700 (PDT)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id E186D11E81D3 for <pim@ietf.org>; Tue, 29 Oct 2013 02:43:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2434; q=dns/txt; s=iport; t=1383039787; x=1384249387; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=Mnm9eN2tFomfLmaRI1EtWB2+blpUVBPPZIeID/Yz34k=; b=bnB2QuoEFMBxh3pDEWHcaHEt4qCU1hIP/uOpKvf+xMeMMtKAhHNnRM5r AamAiAI3HZTwCOVUJ+Yo6IF6YY5XTzCLeKFouNCHfiPuhgdgzbfviKng4 2THgBzNS0QVygrW9LWrHoOJ1JB/pYuBtInIoQx5N4AuOgOyvU8jB5aedZ o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4FAD6Cb1KQ/khL/2dsb2JhbABZgwfAPIEnFnSCJQEBAQMBHR0/BQsLDgouVwYuh2YGuRiPFDMHgx+BDQOYCpIIgyc7
X-IronPort-AV: E=Sophos;i="4.93,591,1378857600"; d="scan'208";a="19093498"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-4.cisco.com with ESMTP; 29 Oct 2013 09:43:05 +0000
Received: from ams-iwijnand-8712.cisco.com (ams-iwijnand-8712.cisco.com [10.55.191.147]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r9T9h0r1013096 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 29 Oct 2013 09:43:02 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: IJsbrand Wijnands <ice@cisco.com>
In-Reply-To: <20131028134708.C5138@eng-mail01.juniper.net>
Date: Tue, 29 Oct 2013 10:43:00 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <A03B605F-3865-4862-9B91-3639CB8730C2@cisco.com>
References: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com> <20131028115859.L5138@eng-mail01.juniper.net> <2AE7C375-B94C-4286-BC5C-245192D2574D@cisco.com> <20131028134708.C5138@eng-mail01.juniper.net>
To: Leonard Giuliano <lenny@juniper.net>
X-Mailer: Apple Mail (2.1499)
Cc: Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
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, 29 Oct 2013 09:43:12 -0000

Lenny,

> How about the last point: if you want to avoid shared trees, RPs, =
register=20
> messages and don't want something that scales, why is dense mode not=20=

> sufficient?  With state refresh, you flood the source info.

When BSR flooding the Source information, intermediate routers don't =
need to create state if there are no directly connected receivers. They =
will just BSR flood the messages.

PIM-DM State-Refresh is still dense-mode in the way you have to =
periodically refresh the Prune state. I think its a better model to =
refresh the Join state, as this will only involve routers that are on =
the shortest path.

PIM-DM State-Refresh has been dead for 13 years, and never made it =
through the IETF process (draft-ietf-pim-refresh-02.txt).

As soon as the egress PIM routers learns about the Source, the PIM =
procedures are like SSM. In that respect, I think we all like that. =
Regarding BSR flooding, IMO, advertising a mapping between a Group and a =
RP is not very different from mapping a Group to a Source.

Thx,

Ice.


>=20
>=20
> On Mon, 28 Oct 2013, IJsbrand Wijnands wrote:
>=20
> -) Hi Lenny,
> -)=20
> -) > I think this is a pointless step in the wrong direction.  The =
last 15=20
> -) > years have shown us that network-based source discovery was a bad =
idea- we=20
> -) > should be deprecating ASM and pushing SSM as the way forward.
> -)=20
> -) We've been saying that for at least 10 years now. However, =
solutions are still being developed to support PIM-SM, like =
draft-rekhter-mpls-pim-sm-over-mldp, which according to your statement =
above is a step in the wrong direction. I don't disagree with that.
> -)=20
> -) > This proposal is a marginal improvement over the existing =
RP/shared tree=20
> -) > mechanism from a simplicity standpoint, but it can't possibly =
scale for=20
> -) > interdomain/large deployments.  Maybe, this might have been a =
useful=20
> -)=20
> -) Agreed, and that is not the intention of this draft. This solves a =
very specific problem for sub-set of the customers, but it solves a real =
problem
> -)=20
> -) > conversation in 1996.  But today, this is a solution in search of =
a=20
> -) > problem.
> -)=20
> -) Lets not give the customer a solution to a problem that he does not =
need to solve, like Inter-domain.
> -)=20
> -) Thx,
> -)=20
> -) Ice.
> -)=20
> -)=20
> -)=20
>=20


From zzhang@juniper.net  Wed Oct 30 06:25:46 2013
Return-Path: <zzhang@juniper.net>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2B0E21E80F3 for <pim@ietfa.amsl.com>; Wed, 30 Oct 2013 06:25:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.827
X-Spam-Level: 
X-Spam-Status: No, score=-2.827 tagged_above=-999 required=5 tests=[AWL=0.172,  BAYES_00=-2.599, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ZRvw5yt7vQ8 for <pim@ietfa.amsl.com>; Wed, 30 Oct 2013 06:25:33 -0700 (PDT)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe005.messaging.microsoft.com [216.32.180.188]) by ietfa.amsl.com (Postfix) with ESMTP id F36BF11E8220 for <pim@ietf.org>; Wed, 30 Oct 2013 06:25:01 -0700 (PDT)
Received: from mail129-co1-R.bigfish.com (10.243.78.239) by CO1EHSOBE019.bigfish.com (10.243.66.82) with Microsoft SMTP Server id 14.1.225.22; Wed, 30 Oct 2013 13:25:01 +0000
Received: from mail129-co1 (localhost [127.0.0.1])	by mail129-co1-R.bigfish.com (Postfix) with ESMTP id 3E9474400A3; Wed, 30 Oct 2013 13:25:01 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT001.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -21
X-BigFish: VPS-21(zzdb82h9371I542I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL17326ah8275dh1de097h186068hz2fh2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h2216h9a9j1155h)
Received-SPF: pass (mail129-co1: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=zzhang@juniper.net; helo=BL2PRD0510HT001.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(13464003)(51704005)(377454003)(189002)(199002)(47976001)(50986001)(81342001)(19580405001)(83322001)(74706001)(15202345003)(19580395003)(80976001)(561944002)(47736001)(49866001)(74876001)(66066001)(74366001)(65816001)(56816003)(77096001)(63696002)(76576001)(87266001)(31966008)(80022001)(33646001)(81816001)(4396001)(74662001)(69226001)(47446002)(74502001)(76786001)(81686001)(76796001)(81542001)(79102001)(51856001)(54316002)(54356001)(85306002)(53806001)(74316001)(59766001)(83072001)(15975445006)(46102001)(77982001)(56776001)(76482001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BY2PR05MB077; H:BY2PR05MB079.namprd05.prod.outlook.com; CLIP:66.129.241.18; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Received: from mail129-co1 (localhost.localdomain [127.0.0.1]) by mail129-co1 (MessageSwitch) id 1383139498767579_27590; Wed, 30 Oct 2013 13:24:58 +0000 (UTC)
Received: from CO1EHSMHS021.bigfish.com (unknown [10.243.78.242])	by mail129-co1.bigfish.com (Postfix) with ESMTP id AE1F9A8003F; Wed, 30 Oct 2013 13:24:58 +0000 (UTC)
Received: from BL2PRD0510HT001.namprd05.prod.outlook.com (157.56.240.101) by CO1EHSMHS021.bigfish.com (10.243.66.31) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 30 Oct 2013 13:24:58 +0000
Received: from BY2PR05MB077.namprd05.prod.outlook.com (10.242.38.11) by BL2PRD0510HT001.namprd05.prod.outlook.com (10.255.100.36) with Microsoft SMTP Server (TLS) id 14.16.371.2; Wed, 30 Oct 2013 13:24:58 +0000
Received: from BY2PR05MB079.namprd05.prod.outlook.com (10.242.38.16) by BY2PR05MB077.namprd05.prod.outlook.com (10.242.38.11) with Microsoft SMTP Server (TLS) id 15.0.810.5; Wed, 30 Oct 2013 13:24:55 +0000
Received: from BY2PR05MB079.namprd05.prod.outlook.com ([169.254.8.16]) by BY2PR05MB079.namprd05.prod.outlook.com ([169.254.8.16]) with mapi id 15.00.0810.005; Wed, 30 Oct 2013 13:24:55 +0000
From: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
To: IJsbrand Wijnands <ice@cisco.com>
Thread-Topic: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
Thread-Index: AQHO0c68DdGwj3jORkCcwV771ygo/5oKHOxggABrxQCAAAEdoIAA5acAgABCsCA=
Date: Wed, 30 Oct 2013 13:24:54 +0000
Message-ID: <fe6eae90ac9f4e74a0782c6688636762@BY2PR05MB079.namprd05.prod.outlook.com>
References: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com> <bc63bb3bdfbe420cb9c464bf8a8398f7@BY2PR05MB079.namprd05.prod.outlook.com> <60835226-85FD-429B-BCC7-09150BE7F28C@cisco.com> <75a2ddc0cd374e3a88c5b4548618f338@BY2PR05MB079.namprd05.prod.outlook.com> <C63CD9AF-03D7-4375-9BA9-D3A1B1FA3A3D@cisco.com>
In-Reply-To: <C63CD9AF-03D7-4375-9BA9-D3A1B1FA3A3D@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.18]
x-forefront-prvs: 00159D1518
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
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, 30 Oct 2013 13:25:47 -0000

Ice,

> -----Original Message-----
> From: IJsbrand Wijnands [mailto:ice@cisco.com]
> Sent: Tuesday, October 29, 2013 5:31 AM
> To: Jeffrey (Zhaohui) Zhang
> Cc: Mike McBride; pim@ietf.org
> Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for
> adoption
>=20
> Jeffrey,
>=20
> An phantom RP is useful if the RPA is on an RPL that is an Ethernet, or
> even better, a cloud, like MPLS for example. In your proposal it seems
> there is very little benefit since you have no view on the topology how
> the ad-hoc network is going to look like, and if there will be any
> ethernet links to begin with. Since the allocation and activation of
> the Active Partition is not pre-determind (I believe ultimately based
> on lowest IP address), there is no guarantee that this will provide you
> any additional protection. If the Active partition is over a P2P link,
> and one of the routers goes down, the link goes down too. This is just
> as good/bad as if you would be using a real RPA. Would your proposal
> not be simplified if we define the following rule; "The lowest /32
> (Router ID) in the Routing Table is the RPA"?

Because a phantom RP does not have the risk of the RP going down, the draft=
 currently focus on phantom RP, even though the same idea can be applied to=
 a real RPA. In fact, the reason to use lowest IP address (instead of highe=
st) is for future consideration of real RPs (need to resolve some details).

We do not want just any router to become the RPA - so we did not go with "t=
he lowest /32 in the routing table is the RPA".=20

Even if a network only has p2p links, phantom RP may still be used. A set o=
f routers could have a loopback interface configured with a subnet (instead=
 of a host address) and a phantom address on that subnet can be the phantom=
 RP. There will be no adjacencies on the subnet so only one of the routers =
will be elected to represent the "active partition" and advertise the host =
route to the RPA and it becomes the only router on the RPL. If that router =
dies, another router will take over after IGP convergence.

This does give some control where the active partition ends up.

>=20
> >> I've just read your draft, I would not say this is simple. When a
> >> phantom RP is not owned by any particular router, this is a new can of
> >> worms. It opens the door for loops because multiple routers may
> >> temporality claim ownership of the phantom address at the same time.
> >
> > If the RPL partitions, the (entire) network will have several RPLs,
> leading to isolation but should not cause loops. The draft actually
> address that existing problem by electing an active RPL partition.
>=20
> And what if the network heals? The fact that the Active partitioned can
> move around the network and is based on election procedures, it looks
> to me that opens up additional race conditions to create loops.

If the network heals, there will be one partition and that is the RPL. The =
election result should be deterministic. It does not move around unless the=
 entire network has partitioned.

>=20
> >> The phantom address works well if the network where the phantom addres=
s
> >> is located is the root of the networks that connect to it. There are
> >> operators that are discarding Bidir how it is today due to the risk of
> >> creating transient loops, so lets be very careful when making the RP
> >> even more random.
> >>
> >> The problem we are solving would require all the routers in the networ=
k
> >> to participate in the functionality you describe in your draft. Its
> >
> > Just the routers on the RPL need to participate. For comparison, BSR
> flooding source information requires every router to do it :-)
>=20
> That is not a good comparison, BSR flooding a packet is not the same as
> participating in election procedures when a link/node goes down.

What is the concern with those routers on the RPL participating in the elec=
tion? I had thought you were concerned with software upgrade for all router=
s.

>=20
> While I think your proposal could work, you still run into issues due
> to PIM Bidir, and will not provide the same level of  redundancy we're
> looking for in a ad-hoc network.
>=20
> The location of the Active partitioned (Phantom RPA) can end up in a
> part of the network that is very inefficient. This goes back to the
> ever lasting question, where do I place the RP, but this time is pretty
> much random.

Is your target network ad hoc in that routers will move around? That's the =
only situation I can think of where you may not have control (with currentl=
y proposed election) that a disadvantaged partition becomes the active part=
ition.

> The RPA (or router to the RPL) goes down, existing flows
> are effected and traffic is interrupted. This is because Bidir traffic
> flows along the path to the RPA. This is a single point of failure.

Only traffic that needs to cross that failure point need to be rerouted.

Jeffrey

> With traditional PIM-SM, if the RPA goes down, this does not
> nessesarily effect existing forwarding since its along the shortest
> path (assuming the RPA is not in the path). Only new senders are
> effected for the time the RP is down and re-elected.
>=20
> Thx,
>=20
> Ice.
>=20
> >
> > Thanks.
> > Jeffrey
> >
> >> great to explore this idea in IETF, but this idea if far from cooked t=
o
> >> be considered as alternative to draft-wijnands-pim-source-discovery-bs=
r.
> >> Either-way, I'm not against if it does, the market will decide.
> >>
> >> Thx,
> >>
> >> Ice.
> >>
> >>>
> >>> Thanks.
> >>> Jeffrey
> >>>
> >>> From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf
> Of
> >> Mike McBride
> >>> Sent: Friday, October 25, 2013 6:08 PM
> >>> To: pim@ietf.org
> >>> Subject: [pim] draft-wijnands-pim-source-discovery-bsr call for
> >> adoption
> >>>
> >>> The authors of draft-wijnands-pim-source-discovery-bsr-03 have
> >> requested that we initiate a call for adoption of their draft which
> >> they presented in our last meeting in Berlin. Notes from that
> >> presentation are below. Please comment over the next week (before
> ietf
> >> week) on your interest/non-interest with adoption of this draft.
> >>>
> >>> http://www.ietf.org/id/draft-wijnands-pim-source-discovery-bsr-
> 03.txt
> >>>
> >>> thanks,
> >>> mike
> >>>
> >>> draft-wignands-pim-source-discovery-bsr-03 (Ice)
> >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >>> highly redudant mcast network without single point of failure.
> >>> Jeffrey: Of the 10k flows how many groups?
> >>> Ice: the sources are what's relevant. 10k s,gs. Not introducing a
> new
> >> routing protocol.
> >>> Jeffrey: Could use mospf. pim bidir is another viable approach.
> With
> >> bidir, while the RPA canbe an address that is not tried to any
> router
> >> (the address would be associated with a LAN), the LAN that the RPA
> is
> >> on could become partitioned. When that happens, traffic cannot be
> >> exchanged on the LAN between the partitions, affecting lots of
> >> receivers. That's the problem using PIM-BIDIR instead of BSR flooing.
> >> However, that can be easily resolved by a protocol extension. I
> should
> >> be able to publish it for the next IETF meeting. With that resolved,
> >> PIM bidir will be a better solution for the targeted deployment
> >> scenario.
> >>> stig: one issue with bidir is you don't have the optimal path.
> >>> operator DT: I like the use case and support.
> >>> Hitoshi: flooding is not typically optimal.
> >>> Ice: its only using mechanisms that exist today with bsr.
> >>> jeffrey: the amount of information is more with today.
> >>> Hitoshi: Why not use SAP (I'm not a fan of SAP though)? Whats the
> >> meaning of flooding. Use MSDP if interdomain?
> >>> lighthouse networks: you mentioned dns, why can't you use that?
> >>> Ice; this is a case where you don't know the source. bsr based
> >> flooding. not inter domain discussion. Enterprise network.
> >>> Mike: applaud any efforts to make multicast more simple. But
> flooding
> >> may be a problem.
> >>>
> >>> 1 room interested. 2 operators on draft interested. Mike will poll
> on
> >> list.
> >>>
> >>> _______________________________________________
> >>> pim mailing list
> >>> pim@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/pim
> >>
> >>
> >
> >
>=20
>=20



From ice@cisco.com  Wed Oct 30 11:35:19 2013
Return-Path: <ice@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 9CCC121E813A for <pim@ietfa.amsl.com>; Wed, 30 Oct 2013 11:35:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.114
X-Spam-Level: 
X-Spam-Status: No, score=-10.114 tagged_above=-999 required=5 tests=[AWL=-0.115, BAYES_00=-2.599, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z7egFz-1iuIP for <pim@ietfa.amsl.com>; Wed, 30 Oct 2013 11:35:15 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 3E9B721E814F for <pim@ietf.org>; Wed, 30 Oct 2013 11:34:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5964; q=dns/txt; s=iport; t=1383158098; x=1384367698; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=g/c55P0vfnipqIGGRPHjCVTyyciK/BipYG0WZa75oJA=; b=biOQMW81qvdn3UImlbUrFsW1ZrDfcyi0VDKZruBvRjKce6e8PYbuy33D xBC6avfiqvE0CoaF6bgO51XtwcIQMyE2WS+uK8C2GdSXcN9jf14+NWHdt y4CXLKyFrDTZIlQAS9muouhDmY8dWVKYCHAgaBzAUpQPTcClyqOIP5iZX g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AusKAKtQcVKQ/khM/2dsb2JhbABZgwc4qzqUboEnFnSCJQEBAQMBAQEBGh00CwULCxEEAQEoBycfCQgGEwkSh2YGDbpsjxwzB4MfgQ0DmAqGPYtMgyc7
X-IronPort-AV: E=Sophos;i="4.93,603,1378857600"; d="scan'208";a="87783649"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 30 Oct 2013 18:34:47 +0000
Received: from [10.61.172.32] ([10.61.172.32]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r9UIYgQi019387 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 30 Oct 2013 18:34:43 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: IJsbrand Wijnands <ice@cisco.com>
In-Reply-To: <fe6eae90ac9f4e74a0782c6688636762@BY2PR05MB079.namprd05.prod.outlook.com>
Date: Wed, 30 Oct 2013 19:34:49 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <97A5F48C-AC8E-41E8-BE23-DDC664427534@cisco.com>
References: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com> <bc63bb3bdfbe420cb9c464bf8a8398f7@BY2PR05MB079.namprd05.prod.outlook.com> <60835226-85FD-429B-BCC7-09150BE7F28C@cisco.com> <75a2ddc0cd374e3a88c5b4548618f338@BY2PR05MB079.namprd05.prod.outlook.com> <C63CD9AF-03D7-4375-9BA9-D3A1B1FA3A3D@cisco.com> <fe6eae90ac9f4e74a0782c6688636762@BY2PR05MB079.namprd05.prod.outlook.com>
To: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
X-Mailer: Apple Mail (2.1499)
Cc: Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
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, 30 Oct 2013 18:35:19 -0000

Jeffery,

> Because a phantom RP does not have the risk of the RP going down, the =
draft currently focus on phantom RP, even though the same idea can be =
applied to a real RPA. In fact, the reason to use lowest IP address =
(instead of highest) is for future consideration of real RPs (need to =
resolve some details).
>=20
> We do not want just any router to become the RPA - so we did not go =
with "the lowest /32 in the routing table is the RPA".=20

But in the ad-hoc network we are looking at, this is exactly what we =
would need. There is no way to predetermine the best location of the RP =
since we don't know what the network is going to look like. For that =
reason depending on an RP is bad to begin with. You can also simply add =
an attribute in OSPF/ISIS to flag the /32's that it can be used as RP. =
But, the next questions will be, can we assign different RP's for =
different group addresses to share the load, which makes it less =
attractive.

>=20
> Even if a network only has p2p links, phantom RP may still be used. A =
set of routers could have a loopback interface configured with a subnet =
(instead of a host address) and a phantom address on that subnet can be =
the phantom RP. There will be no adjacencies on the subnet so only one =
of the routers will be elected to represent the "active partition" and =
advertise the host route to the RPA and it becomes the only router on =
the RPL. If that router dies, another router will take over after IGP =
convergence.

Sure, but my point is that this is not any better than Anycast RP.=20

> Is your target network ad hoc in that routers will move around? That's =
the only situation I can think of where you may not have control (with =
currently proposed election) that a disadvantaged partition becomes the =
active partition.

Yes.

>=20
>> The RPA (or router to the RPL) goes down, existing flows
>> are effected and traffic is interrupted. This is because Bidir =
traffic
>> flows along the path to the RPA. This is a single point of failure.
>=20
> Only traffic that needs to cross that failure point need to be =
rerouted.

If the RPA moves from one router to the other, the tree has to be =
rebuild. This is not only impacting the failure point.

Thx,

Ice.

>=20
> Jeffrey
>=20
>> With traditional PIM-SM, if the RPA goes down, this does not
>> nessesarily effect existing forwarding since its along the shortest
>> path (assuming the RPA is not in the path). Only new senders are
>> effected for the time the RP is down and re-elected.
>>=20
>> Thx,
>>=20
>> Ice.
>>=20
>>>=20
>>> Thanks.
>>> Jeffrey
>>>=20
>>>> great to explore this idea in IETF, but this idea if far from =
cooked to
>>>> be considered as alternative to =
draft-wijnands-pim-source-discovery-bsr.
>>>> Either-way, I'm not against if it does, the market will decide.
>>>>=20
>>>> Thx,
>>>>=20
>>>> Ice.
>>>>=20
>>>>>=20
>>>>> Thanks.
>>>>> Jeffrey
>>>>>=20
>>>>> From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf
>> Of
>>>> Mike McBride
>>>>> Sent: Friday, October 25, 2013 6:08 PM
>>>>> To: pim@ietf.org
>>>>> Subject: [pim] draft-wijnands-pim-source-discovery-bsr call for
>>>> adoption
>>>>>=20
>>>>> The authors of draft-wijnands-pim-source-discovery-bsr-03 have
>>>> requested that we initiate a call for adoption of their draft which
>>>> they presented in our last meeting in Berlin. Notes from that
>>>> presentation are below. Please comment over the next week (before
>> ietf
>>>> week) on your interest/non-interest with adoption of this draft.
>>>>>=20
>>>>> http://www.ietf.org/id/draft-wijnands-pim-source-discovery-bsr-
>> 03.txt
>>>>>=20
>>>>> thanks,
>>>>> mike
>>>>>=20
>>>>> draft-wignands-pim-source-discovery-bsr-03 (Ice)
>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>>> highly redudant mcast network without single point of failure.
>>>>> Jeffrey: Of the 10k flows how many groups?
>>>>> Ice: the sources are what's relevant. 10k s,gs. Not introducing a
>> new
>>>> routing protocol.
>>>>> Jeffrey: Could use mospf. pim bidir is another viable approach.
>> With
>>>> bidir, while the RPA canbe an address that is not tried to any
>> router
>>>> (the address would be associated with a LAN), the LAN that the RPA
>> is
>>>> on could become partitioned. When that happens, traffic cannot be
>>>> exchanged on the LAN between the partitions, affecting lots of
>>>> receivers. That's the problem using PIM-BIDIR instead of BSR =
flooing.
>>>> However, that can be easily resolved by a protocol extension. I
>> should
>>>> be able to publish it for the next IETF meeting. With that =
resolved,
>>>> PIM bidir will be a better solution for the targeted deployment
>>>> scenario.
>>>>> stig: one issue with bidir is you don't have the optimal path.
>>>>> operator DT: I like the use case and support.
>>>>> Hitoshi: flooding is not typically optimal.
>>>>> Ice: its only using mechanisms that exist today with bsr.
>>>>> jeffrey: the amount of information is more with today.
>>>>> Hitoshi: Why not use SAP (I'm not a fan of SAP though)? Whats the
>>>> meaning of flooding. Use MSDP if interdomain?
>>>>> lighthouse networks: you mentioned dns, why can't you use that?
>>>>> Ice; this is a case where you don't know the source. bsr based
>>>> flooding. not inter domain discussion. Enterprise network.
>>>>> Mike: applaud any efforts to make multicast more simple. But
>> flooding
>>>> may be a problem.
>>>>>=20
>>>>> 1 room interested. 2 operators on draft interested. Mike will poll
>> on
>>>> list.
>>>>>=20
>>>>> _______________________________________________
>>>>> pim mailing list
>>>>> pim@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/pim
>>>>=20
>>>>=20
>>>=20
>>>=20
>>=20
>>=20
>=20
>=20


From lenny@juniper.net  Wed Oct 30 13:04:54 2013
Return-Path: <lenny@juniper.net>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DFE611E81E4 for <pim@ietfa.amsl.com>; Wed, 30 Oct 2013 13:04:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.166
X-Spam-Level: 
X-Spam-Status: No, score=-103.166 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HeT4t39viXFS for <pim@ietfa.amsl.com>; Wed, 30 Oct 2013 13:04:48 -0700 (PDT)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe001.messaging.microsoft.com [216.32.180.184]) by ietfa.amsl.com (Postfix) with ESMTP id 28DF211E81A6 for <pim@ietf.org>; Wed, 30 Oct 2013 13:04:48 -0700 (PDT)
Received: from mail78-co1-R.bigfish.com (10.243.78.248) by CO1EHSOBE032.bigfish.com (10.243.66.97) with Microsoft SMTP Server id 14.1.225.22; Wed, 30 Oct 2013 20:04:47 +0000
Received: from mail78-co1 (localhost [127.0.0.1])	by mail78-co1-R.bigfish.com (Postfix) with ESMTP id 37B685C0190; Wed, 30 Oct 2013 20:04:47 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:66.129.224.54; KIP:(null); UIP:(null); IPV:NLI; H:P-EMF01-SAC.jnpr.net; RD:none; EFVD:NLI
X-SpamScore: 2
X-BigFish: VPS2(zz98dIzz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6h1082kzz1de097hz2fh2a8h839h944hd25hf0ah11b5h121eh1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h16a6h1758h18e1h1946h19b5h1ad9h1b0ah1b2fh1fb3h1d0ch1d2eh1d3fh1de2h1dfeh1dffh1fe8h1ff5h2216h1155h)
Received-SPF: pass (mail78-co1: domain of juniper.net designates 66.129.224.54 as permitted sender) client-ip=66.129.224.54; envelope-from=lenny@juniper.net; helo=P-EMF01-SAC.jnpr.net ; SAC.jnpr.net ; 
Received: from mail78-co1 (localhost.localdomain [127.0.0.1]) by mail78-co1 (MessageSwitch) id 1383163484504716_23382; Wed, 30 Oct 2013 20:04:44 +0000 (UTC)
Received: from CO1EHSMHS019.bigfish.com (unknown [10.243.78.254])	by mail78-co1.bigfish.com (Postfix) with ESMTP id 6D694220031; Wed, 30 Oct 2013 20:04:44 +0000 (UTC)
Received: from P-EMF01-SAC.jnpr.net (66.129.224.54) by CO1EHSMHS019.bigfish.com (10.243.66.29) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 30 Oct 2013 20:04:44 +0000
Received: from magenta.juniper.net (172.17.27.123) by P-EMF01-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.146.0; Wed, 30 Oct 2013 13:04:41 -0700
Received: from eng-mail01.juniper.net (eng-mail01.juniper.net [172.17.28.114]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id r9UK4RL32789; Wed, 30 Oct 2013 13:04:36 -0700 (PDT)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id 6AE461145A;  Wed, 30 Oct 2013 13:04:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id 5F7F711446; Wed, 30 Oct 2013 13:04:27 -0700 (PDT)
Date: Wed, 30 Oct 2013 13:04:27 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: IJsbrand Wijnands <ice@cisco.com>
In-Reply-To: <A03B605F-3865-4862-9B91-3639CB8730C2@cisco.com>
Message-ID: <20131030124704.F72700@eng-mail01.juniper.net>
References: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com> <20131028115859.L5138@eng-mail01.juniper.net> <2AE7C375-B94C-4286-BC5C-245192D2574D@cisco.com> <20131028134708.C5138@eng-mail01.juniper.net> <A03B605F-3865-4862-9B91-3639CB8730C2@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
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, 30 Oct 2013 20:04:54 -0000

On Tue, 29 Oct 2013, IJsbrand Wijnands wrote:

-) Lenny,
-) 
-) > How about the last point: if you want to avoid shared trees, RPs, register 
-) > messages and don't want something that scales, why is dense mode not 
-) > sufficient?  With state refresh, you flood the source info.
-) 
-) When BSR flooding the Source information, intermediate routers don't 
-) need to create state if there are no directly connected receivers. They 
-) will just BSR flood the messages.
-) 
-) PIM-DM State-Refresh is still dense-mode in the way you have to 
-) periodically refresh the Prune state. I think its a better model to 
-) refresh the Join state, as this will only involve routers that are on 
-) the shortest path.
-) 
-) PIM-DM State-Refresh has been dead for 13 years, and never made it 
-) through the IETF process (draft-ietf-pim-refresh-02.txt).

This is perhaps a revealing data point on the usefulness of a scheme that 
floods (and refloods to refresh) source info for all routers in the domain 
in order to obviate the need for RPs.  The fact that DM is not very widely 
used and development has been abandoned certainly provides me skepticism 
that this is indeed a real world problem that folks are clamoring to 
solve.  This just seems like DM by a different name.

-) 
-) As soon as the egress PIM routers learns about the Source, the PIM 
-) procedures are like SSM. In that respect, I think we all like that. 

And pretty similiar functionally to DM...

-) Regarding BSR flooding, IMO, advertising a mapping between a Group and 
-) a RP is not very different from mapping a Group to a Source.

There's a HUGE difference!  The group-RP mapping is in many/most 
deployments a single 224/4 mapping.  The s-g mapping includes every single 
mcast stream.  The number of s-g mappings is  >>>> group-RP mappings.


From ice@cisco.com  Wed Oct 30 13:12:33 2013
Return-Path: <ice@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 D015E21E8063 for <pim@ietfa.amsl.com>; Wed, 30 Oct 2013 13:12:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.399
X-Spam-Level: 
X-Spam-Status: No, score=-10.399 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nta-I5iXcPVZ for <pim@ietfa.amsl.com>; Wed, 30 Oct 2013 13:12:28 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 77DC411E8110 for <pim@ietf.org>; Wed, 30 Oct 2013 13:12:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2272; q=dns/txt; s=iport; t=1383163948; x=1384373548; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=BRRvNv40sbtbYdXkbYoO9sdTbSru2cFbUVXj9iH22LM=; b=XdqGy5kdYTjBburL7b7+0XWgGP0SqfiVmswov8cKic2PxWUwPv6grjej 5hUXVwz/BTBoUyDXpFDB9xUOb4Z54UwAzs/FtWpVGQYBrvpyAPaKp2GSS p7kDdhOjo5Xzpngc2KNZ39IAfjYzG9cqTh57xo7LqpHcFg75CCIiHWCcZ w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAOtmcVKQ/khL/2dsb2JhbABZgwfAX4EpFnSCJgEBBB0dPxALDjhXBi6HbLpnjxwzB4MfgQ0DlCqDYIY9i0yDJzs
X-IronPort-AV: E=Sophos;i="4.93,603,1378857600"; d="scan'208";a="161218614"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 30 Oct 2013 20:12:27 +0000
Received: from [10.61.172.32] ([10.61.172.32]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r9UKCLQr012984 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 30 Oct 2013 20:12:24 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: IJsbrand Wijnands <ice@cisco.com>
In-Reply-To: <20131030124704.F72700@eng-mail01.juniper.net>
Date: Wed, 30 Oct 2013 21:12:25 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <25A558C2-5E1E-45BC-B86F-6AB2C61F1075@cisco.com>
References: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com> <20131028115859.L5138@eng-mail01.juniper.net> <2AE7C375-B94C-4286-BC5C-245192D2574D@cisco.com> <20131028134708.C5138@eng-mail01.juniper.net> <A03B605F-3865-4862-9B91-3639CB8730C2@cisco.com> <20131030124704.F72700@eng-mail01.juniper.net>
To: Leonard Giuliano <lenny@juniper.net>
X-Mailer: Apple Mail (2.1499)
Cc: Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
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, 30 Oct 2013 20:12:34 -0000

Lenny,

> -) > How about the last point: if you want to avoid shared trees, RPs, =
register=20
> -) > messages and don't want something that scales, why is dense mode =
not=20
> -) > sufficient?  With state refresh, you flood the source info.
> -)=20
> -) When BSR flooding the Source information, intermediate routers =
don't=20
> -) need to create state if there are no directly connected receivers. =
They=20
> -) will just BSR flood the messages.
> -)=20
> -) PIM-DM State-Refresh is still dense-mode in the way you have to=20
> -) periodically refresh the Prune state. I think its a better model to=20=

> -) refresh the Join state, as this will only involve routers that are =
on=20
> -) the shortest path.
> -)=20
> -) PIM-DM State-Refresh has been dead for 13 years, and never made it=20=

> -) through the IETF process (draft-ietf-pim-refresh-02.txt).
>=20
> This is perhaps a revealing data point on the usefulness of a scheme =
that=20
> floods (and refloods to refresh) source info for all routers in the =
domain=20
> in order to obviate the need for RPs.  The fact that DM is not very =
widely=20
> used and development has been abandoned certainly provides me =
skepticism=20
> that this is indeed a real world problem that folks are clamoring to=20=

> solve.  This just seems like DM by a different name.

Re-read the part above you did not comment on, this solution does not =
create state in the network where it is not needed. If you think this is =
the same as DM, we have a different view on what DM is.

>=20
> -)=20
> -) As soon as the egress PIM routers learns about the Source, the PIM=20=

> -) procedures are like SSM. In that respect, I think we all like that.=20=

>=20
> And pretty similiar functionally to DM...
>=20
> -) Regarding BSR flooding, IMO, advertising a mapping between a Group =
and=20
> -) a RP is not very different from mapping a Group to a Source.
>=20
> There's a HUGE difference!  The group-RP mapping is in many/most=20
> deployments a single 224/4 mapping.  The s-g mapping includes every =
single=20
> mcast stream.  The number of s-g mappings is  >>>> group-RP mappings.

We already discussed the scalability and applicability aspect of it.

Thx,

Ice.=

From lenny@juniper.net  Wed Oct 30 13:38:54 2013
Return-Path: <lenny@juniper.net>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14D7221F9EE0 for <pim@ietfa.amsl.com>; Wed, 30 Oct 2013 13:38:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.228
X-Spam-Level: 
X-Spam-Status: No, score=-103.228 tagged_above=-999 required=5 tests=[AWL=0.371, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hZqjiVMTEEIS for <pim@ietfa.amsl.com>; Wed, 30 Oct 2013 13:38:48 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe004.messaging.microsoft.com [216.32.181.184]) by ietfa.amsl.com (Postfix) with ESMTP id 1FF2421F9E36 for <pim@ietf.org>; Wed, 30 Oct 2013 13:38:27 -0700 (PDT)
Received: from mail191-ch1-R.bigfish.com (10.43.68.248) by CH1EHSOBE006.bigfish.com (10.43.70.56) with Microsoft SMTP Server id 14.1.225.22; Wed, 30 Oct 2013 20:38:26 +0000
Received: from mail191-ch1 (localhost [127.0.0.1])	by mail191-ch1-R.bigfish.com (Postfix) with ESMTP id 357B62A00E5; Wed, 30 Oct 2013 20:38:26 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:66.129.224.53; KIP:(null); UIP:(null); IPV:NLI; H:P-EMF01-SAC.jnpr.net; RD:none; EFVD:NLI
X-SpamScore: 3
X-BigFish: VPS3(zzzz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6h1082kzzz2fh2a8h839h944hd25hf0ah11b5h121eh1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h16a6h1758h18e1h1946h19b5h1ad9h1b0ah1b2fh1fb3h1d0ch1d2eh1d3fh1de2h1dfeh1dffh1fe8h1ff5h2216h1155h)
Received-SPF: pass (mail191-ch1: domain of juniper.net designates 66.129.224.53 as permitted sender) client-ip=66.129.224.53; envelope-from=lenny@juniper.net; helo=P-EMF01-SAC.jnpr.net ; SAC.jnpr.net ; 
Received: from mail191-ch1 (localhost.localdomain [127.0.0.1]) by mail191-ch1 (MessageSwitch) id 1383165503966648_13042; Wed, 30 Oct 2013 20:38:23 +0000 (UTC)
Received: from CH1EHSMHS033.bigfish.com (snatpool3.int.messaging.microsoft.com [10.43.68.225])	by mail191-ch1.bigfish.com (Postfix) with ESMTP id DE301260111;	Wed, 30 Oct 2013 20:38:23 +0000 (UTC)
Received: from P-EMF01-SAC.jnpr.net (66.129.224.53) by CH1EHSMHS033.bigfish.com (10.43.70.33) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 30 Oct 2013 20:38:21 +0000
Received: from magenta.juniper.net (172.17.27.123) by P-EMF01-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.146.0; Wed, 30 Oct 2013 13:38:19 -0700
Received: from eng-mail01.juniper.net (eng-mail01.juniper.net [172.17.28.114]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id r9UKcIL50810; Wed, 30 Oct 2013 13:38:18 -0700 (PDT)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id B1B3711446;  Wed, 30 Oct 2013 13:38:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id A39171141B; Wed, 30 Oct 2013 13:38:16 -0700 (PDT)
Date: Wed, 30 Oct 2013 13:38:16 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: IJsbrand Wijnands <ice@cisco.com>
In-Reply-To: <25A558C2-5E1E-45BC-B86F-6AB2C61F1075@cisco.com>
Message-ID: <20131030133107.A72700@eng-mail01.juniper.net>
References: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com> <20131028115859.L5138@eng-mail01.juniper.net> <2AE7C375-B94C-4286-BC5C-245192D2574D@cisco.com> <20131028134708.C5138@eng-mail01.juniper.net> <A03B605F-3865-4862-9B91-3639CB8730C2@cisco.com> <20131030124704.F72700@eng-mail01.juniper.net> <25A558C2-5E1E-45BC-B86F-6AB2C61F1075@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
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, 30 Oct 2013 20:38:54 -0000

Ice,

-) > This is perhaps a revealing data point on the usefulness of a scheme that 
-) > floods (and refloods to refresh) source info for all routers in the domain 
-) > in order to obviate the need for RPs.  The fact that DM is not very widely 
-) > used and development has been abandoned certainly provides me skepticism 
-) > that this is indeed a real world problem that folks are clamoring to 
-) > solve.  This just seems like DM by a different name.
-) 
-) Re-read the part above you did not comment on, this solution does not 
-) create state in the network where it is not needed. If you think this 
-) is the same as DM, we have a different view on what DM is.
-) 

>From the draft:

5.  Processing SG messages

   A router that receives an SG message should parse the message and
   store the SG mappings with a holdtimer started with the advertised
   holdtime for that group.  If there are directly connected receivers
   for that group this router should send PIM (S,G) joins for all the SG
   mappings advertised in the message.  The SG mappings are kept alive
   for as long as the holdtimer for the source is running.  Once the
   holdtimer expires a PIM (S,G) prune must be sent to remove itself
   from the tree.

I read this mean these SG messages are flooded to all routers in the 
domain, and every router then stores this information in the event that he 
has a local receiver that wants to join a group, so it knows the source 
for every group and knows how/where to send the s,g join.  Am I 
misinterpreting this?  Are you suggesting that only the LHRs should be 
storing this source info, and the non-LHRs should ignore this source info?  
If so, how does a router know he is a LHR or not?


From stig@venaas.com  Thu Oct 31 10:43:39 2013
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 C554311E8231 for <pim@ietfa.amsl.com>; Thu, 31 Oct 2013 10:43:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.309
X-Spam-Level: 
X-Spam-Status: No, score=-102.309 tagged_above=-999 required=5 tests=[AWL=0.290, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EVGVy+yQJl05 for <pim@ietfa.amsl.com>; Thu, 31 Oct 2013 10:43:04 -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 9C60911E8164 for <pim@ietf.org>; Thu, 31 Oct 2013 10:40:26 -0700 (PDT)
Received: from [10.33.12.93] (128-107-239-235.cisco.com [128.107.239.235]) by ufisa.uninett.no (Postfix) with ESMTPSA id 344BC7FFB; Thu, 31 Oct 2013 18:40:19 +0100 (CET)
Message-ID: <52729601.9040606@venaas.com>
Date: Thu, 31 Oct 2013 10:40:17 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Leonard Giuliano <lenny@juniper.net>,  IJsbrand Wijnands <ice@cisco.com>
References: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com>	<20131028115859.L5138@eng-mail01.juniper.net>	<2AE7C375-B94C-4286-BC5C-245192D2574D@cisco.com>	<20131028134708.C5138@eng-mail01.juniper.net>	<A03B605F-3865-4862-9B91-3639CB8730C2@cisco.com>	<20131030124704.F72700@eng-mail01.juniper.net>	<25A558C2-5E1E-45BC-B86F-6AB2C61F1075@cisco.com> <20131030133107.A72700@eng-mail01.juniper.net>
In-Reply-To: <20131030133107.A72700@eng-mail01.juniper.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Oct 2013 17:43:53 -0000

Hi

On 10/30/2013 1:38 PM, Leonard Giuliano wrote:
[...]
>>From the draft:
>
> 5.  Processing SG messages
>
>     A router that receives an SG message should parse the message and
>     store the SG mappings with a holdtimer started with the advertised
>     holdtime for that group.  If there are directly connected receivers
>     for that group this router should send PIM (S,G) joins for all the SG
>     mappings advertised in the message.  The SG mappings are kept alive
>     for as long as the holdtimer for the source is running.  Once the
>     holdtimer expires a PIM (S,G) prune must be sent to remove itself
>     from the tree.
>
> I read this mean these SG messages are flooded to all routers in the
> domain, and every router then stores this information in the event that he
> has a local receiver that wants to join a group, so it knows the source
> for every group and knows how/where to send the s,g join.  Am I
> misinterpreting this?  Are you suggesting that only the LHRs should be
> storing this source info, and the non-LHRs should ignore this source info?
> If so, how does a router know he is a LHR or not?

This can be an administrative decision. If you know that a router will
not function as a LHR, it can be configured to only forward the
messages. If you have a deployment where most routers only function as
a LHR for a few selected groups, then the routers only need to store
state for those.

Stig

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


From stig@venaas.com  Thu Oct 31 10:45:02 2013
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 EC60111E825F for <pim@ietfa.amsl.com>; Thu, 31 Oct 2013 10:45:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.057
X-Spam-Level: 
X-Spam-Status: No, score=-102.057 tagged_above=-999 required=5 tests=[AWL=-0.058, BAYES_00=-2.599, J_CHICKENPOX_12=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UlMQ9291Skwm for <pim@ietfa.amsl.com>; Thu, 31 Oct 2013 10:45:00 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id E868411E817F for <pim@ietf.org>; Thu, 31 Oct 2013 10:44:14 -0700 (PDT)
Received: from [10.33.12.93] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id 01FB77FFB; Thu, 31 Oct 2013 18:44:05 +0100 (CET)
Message-ID: <527296E3.8020904@venaas.com>
Date: Thu, 31 Oct 2013 10:44:03 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Leonard Giuliano <lenny@juniper.net>, Mike McBride <mmcbride7@gmail.com>
References: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com> <20131028115859.L5138@eng-mail01.juniper.net>
In-Reply-To: <20131028115859.L5138@eng-mail01.juniper.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Oct 2013 17:45:03 -0000

Hi

On 10/28/2013 12:08 PM, Leonard Giuliano wrote:
>
> I think this is a pointless step in the wrong direction.  The last 15
> years have shown us that network-based source discovery was a bad idea- we
> should be deprecating ASM and pushing SSM as the way forward.

This proposal is IMO the closest you can get to SSM without requiring
IGMPv3 and application source discovery. Once application figure out
the source discovery, then I would certainly want them to use SSM as
well. SSM is great, but doesn't fit all.

> This proposal is a marginal improvement over the existing RP/shared tree
> mechanism from a simplicity standpoint, but it can't possibly scale for
> interdomain/large deployments.  Maybe, this might have been a useful
> conversation in 1996.  But today, this is a solution in search of a
> problem.
>
> We already have a solution that eliminates RPs, shared trees and doesn't
> scale: PIM-DM.  We don't another.

DM is being used in some environments where this solution is desired.
We would like to move away from DM though. I think this proposal is a
move in the right direction. From PIM point of view, this is pretty
much SSM (we just need the source discovery).

Stig

> -Lenny
>
> On Fri, 25 Oct 2013, Mike McBride wrote:
>
> -) The authors of draft-wijnands-pim-source-discovery-bsr-03 have requested
> -) that we initiate a call for adoption of their draft which they presented in
> -) our last meeting in Berlin. Notes from that presentation are below. Please
> -) comment over the next week (before ietf week) on your interest/non-interest
> -) with adoption of this draft.
> -)
> -) http://www.ietf.org/id/draft-wijnands-pim-source-discovery-bsr-03.txt
> -)
> -) thanks,
> -) mike
> -)
> -) draft-wignands-pim-source-discovery-bsr-03 (Ice)
> -) ==============================================
> -) highly redudant mcast network without single point of failure.
> -) Jeffrey: Of the 10k flows how many groups?
> -) Ice: the sources are what's relevant. 10k s,gs. Not introducing a new
> -) routing protocol.
> -) Jeffrey: Could use mospf. pim bidir is another viable approach. With
> -) bidir, while the RPA canbe an address that is not tried to any router
> -) (the address would be associated with a LAN), the LAN that the RPA is
> -) on could become partitioned. When that happens, traffic cannot be
> -) exchanged on the LAN between the partitions, affecting lots of
> -) receivers. That's the problem using PIM-BIDIR instead of BSR flooing.
> -) However, that can be easily resolved by a protocol extension. I should
> -) be able to publish it for the next IETF meeting. With that resolved,
> -) PIM bidir will be a better solution for the targeted deployment
> -) scenario.
> -) stig: one issue with bidir is you don't have the optimal path.
> -) operator DT: I like the use case and support.
> -) Hitoshi: flooding is not typically optimal.
> -) Ice: its only using mechanisms that exist today with bsr.
> -) jeffrey: the amount of information is more with today.
> -) Hitoshi: Why not use SAP (I'm not a fan of SAP though)? Whats the
> -) meaning of flooding. Use MSDP if interdomain?
> -) lighthouse networks: you mentioned dns, why can't you use that?
> -) Ice; this is a case where you don't know the source. bsr based
> -) flooding. not inter domain discussion. Enterprise network.
> -) Mike: applaud any efforts to make multicast more simple. But flooding
> -) may be a problem.
> -)
> -) 1 room interested. 2 operators on draft interested. Mike will poll on list.
> -)
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim
>


From lenny@juniper.net  Thu Oct 31 11:35:34 2013
Return-Path: <lenny@juniper.net>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECE6321E8115 for <pim@ietfa.amsl.com>; Thu, 31 Oct 2013 11:35:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.774
X-Spam-Level: 
X-Spam-Status: No, score=-104.774 tagged_above=-999 required=5 tests=[AWL=1.825, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gCSTRaXFKRTR for <pim@ietfa.amsl.com>; Thu, 31 Oct 2013 11:35:10 -0700 (PDT)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe005.messaging.microsoft.com [65.55.88.15]) by ietfa.amsl.com (Postfix) with ESMTP id 8F16A11E824A for <pim@ietf.org>; Thu, 31 Oct 2013 11:35:09 -0700 (PDT)
Received: from mail239-tx2-R.bigfish.com (10.9.14.250) by TX2EHSOBE002.bigfish.com (10.9.40.22) with Microsoft SMTP Server id 14.1.225.22; Thu, 31 Oct 2013 18:35:03 +0000
Received: from mail239-tx2 (localhost [127.0.0.1])	by mail239-tx2-R.bigfish.com (Postfix) with ESMTP id 3082922018D; Thu, 31 Oct 2013 18:35:03 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:66.129.224.54; KIP:(null); UIP:(null); IPV:NLI; H:P-EMF01-SAC.jnpr.net; RD:none; EFVD:NLI
X-SpamScore: 0
X-BigFish: VPS0(zzdb82h1432I1418I1447Izz1f42h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6h1082kzzz2fh2a8h839h944hd25hf0ah11b5h121eh1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h16a6h1758h18e1h1946h19b5h1ad9h1b0ah1b2fh1fb3h1d0ch1d2eh1d3fh1de2h1dfeh1dffh1fe8h1ff5h2216h1155h)
Received-SPF: pass (mail239-tx2: domain of juniper.net designates 66.129.224.54 as permitted sender) client-ip=66.129.224.54; envelope-from=lenny@juniper.net; helo=P-EMF01-SAC.jnpr.net ; SAC.jnpr.net ; 
Received: from mail239-tx2 (localhost.localdomain [127.0.0.1]) by mail239-tx2 (MessageSwitch) id 1383244500269642_5257; Thu, 31 Oct 2013 18:35:00 +0000 (UTC)
Received: from TX2EHSMHS008.bigfish.com (unknown [10.9.14.239])	by mail239-tx2.bigfish.com (Postfix) with ESMTP id 3BE33440066; Thu, 31 Oct 2013 18:35:00 +0000 (UTC)
Received: from P-EMF01-SAC.jnpr.net (66.129.224.54) by TX2EHSMHS008.bigfish.com (10.9.99.108) with Microsoft SMTP Server (TLS) id 14.16.227.3; Thu, 31 Oct 2013 18:35:00 +0000
Received: from magenta.juniper.net (172.17.27.123) by P-EMF01-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.146.0; Thu, 31 Oct 2013 11:34:58 -0700
Received: from eng-mail01.juniper.net (eng-mail01.juniper.net [172.17.28.114]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id r9VIYvL57653; Thu, 31 Oct 2013 11:34:58 -0700 (PDT)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id 6564B1144F;  Thu, 31 Oct 2013 11:34:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id 5A8881144E; Thu, 31 Oct 2013 11:34:57 -0700 (PDT)
Date: Thu, 31 Oct 2013 11:34:57 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: Stig Venaas <stig@venaas.com>
In-Reply-To: <52729601.9040606@venaas.com>
Message-ID: <20131031104817.O72868@eng-mail01.juniper.net>
References: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com> <20131028115859.L5138@eng-mail01.juniper.net> <2AE7C375-B94C-4286-BC5C-245192D2574D@cisco.com> <20131028134708.C5138@eng-mail01.juniper.net> <A03B605F-3865-4862-9B91-3639CB8730C2@cisco.com> <20131030124704.F72700@eng-mail01.juniper.net> <25A558C2-5E1E-45BC-B86F-6AB2C61F1075@cisco.com> <20131030133107.A72700@eng-mail01.juniper.net> <52729601.9040606@venaas.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Oct 2013 18:35:35 -0000

-) > > From the draft:
-) > 
-) > 5.  Processing SG messages
-) > 
-) >     A router that receives an SG message should parse the message and
-) >     store the SG mappings with a holdtimer started with the advertised
-) >     holdtime for that group.  If there are directly connected receivers
-) >     for that group this router should send PIM (S,G) joins for all the SG
-) >     mappings advertised in the message.  The SG mappings are kept alive
-) >     for as long as the holdtimer for the source is running.  Once the
-) >     holdtimer expires a PIM (S,G) prune must be sent to remove itself
-) >     from the tree.
-) > 
-) > I read this mean these SG messages are flooded to all routers in the
-) > domain, and every router then stores this information in the event that he
-) > has a local receiver that wants to join a group, so it knows the source
-) > for every group and knows how/where to send the s,g join.  Am I
-) > misinterpreting this?  Are you suggesting that only the LHRs should be
-) > storing this source info, and the non-LHRs should ignore this source info?
-) > If so, how does a router know he is a LHR or not?
-) 
-) This can be an administrative decision. If you know that a router will
-) not function as a LHR, it can be configured to only forward the
-) messages. If you have a deployment where most routers only function as
-) a LHR for a few selected groups, then the routers only need to store
-) state for those.

Stig- thanks for the clarification.  I read the draft over a few times, 
and saw nothing about this.  As the draft is written today, it appears 
that all routers will flood all source info and cache all of that state.  
I guess you are saying that an unmentioned option is for the non LHRs to 
flood but not cache.  OK, but you have to somehow know who is a LHR, and 
who isn't.  Which you seem to be implying that this can be done via 
config.  Or, I suppose to you could just look and see if you have any 
local igmp state to figure out if you are a LHR.  But that would lead to 
join latency of 1-60s when the joins come after the source starts up, and 
I can't imagine any use case where 30s avg join latency is acceptable.

Ultimately, the added state isn't so horrible to me.  In most practical 
cases it doesn't really matter that some routers carry the state and 
others don't.  Besides, you seem to be implying that the use case you have 
in mind doesn't have that many sources, so I guess that's OK.  But you 
still end up with flooding of source info across the domain.  That is 
functionally what DM does- flood source info across the domain (and 
reflood periodically) so that you can build SPTs and not need RPs.  The 
message names are different (refreshing prune state and sending grafts to 
join on the SPT vs refreshing sg messages and sending s,g's to join the on 
the SPT), but the functionality is the same.

I'm not trying to wave the DM banner, but rather to suggest that there 
appears to be no desire by anyone to use DM these days- tough to imagine 
anyone proposing new drafts to develop DM now.  I think that provides 
pretty clear evidence for the utility of another proposal that 
functionally does the same thing under a different name: flood source info 
across the domain (and reflood periodically) so that you can build SPTs 
and not need RPs.

And as for the claim that this is more like SSM- this is no more 
SSM-friendly than DM.


From stig@venaas.com  Thu Oct 31 12:54:56 2013
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 4204221F9E5A for <pim@ietfa.amsl.com>; Thu, 31 Oct 2013 12:54:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.349
X-Spam-Level: 
X-Spam-Status: No, score=-102.349 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id utFUjX+VUCfI for <pim@ietfa.amsl.com>; Thu, 31 Oct 2013 12:54:54 -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 1164B21F9E77 for <pim@ietf.org>; Thu, 31 Oct 2013 12:54:48 -0700 (PDT)
Received: from [10.33.12.93] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id 031D67FEB; Thu, 31 Oct 2013 20:54:45 +0100 (CET)
Message-ID: <5272B584.9030805@venaas.com>
Date: Thu, 31 Oct 2013 12:54:44 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Leonard Giuliano <lenny@juniper.net>
References: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com> <20131028115859.L5138@eng-mail01.juniper.net> <2AE7C375-B94C-4286-BC5C-245192D2574D@cisco.com> <20131028134708.C5138@eng-mail01.juniper.net> <A03B605F-3865-4862-9B91-3639CB8730C2@cisco.com> <20131030124704.F72700@eng-mail01.juniper.net> <25A558C2-5E1E-45BC-B86F-6AB2C61F1075@cisco.com> <20131030133107.A72700@eng-mail01.juniper.net> <52729601.9040606@venaas.com> <20131031104817.O72868@eng-mail01.juniper.net>
In-Reply-To: <20131031104817.O72868@eng-mail01.juniper.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Oct 2013 19:54:56 -0000

Hi

On 10/31/2013 11:34 AM, Leonard Giuliano wrote:
>
> -) > > From the draft:
> -) >
> -) > 5.  Processing SG messages
> -) >
> -) >     A router that receives an SG message should parse the message and
> -) >     store the SG mappings with a holdtimer started with the advertised
> -) >     holdtime for that group.  If there are directly connected receivers
> -) >     for that group this router should send PIM (S,G) joins for all the SG
> -) >     mappings advertised in the message.  The SG mappings are kept alive
> -) >     for as long as the holdtimer for the source is running.  Once the
> -) >     holdtimer expires a PIM (S,G) prune must be sent to remove itself
> -) >     from the tree.
> -) >
> -) > I read this mean these SG messages are flooded to all routers in the
> -) > domain, and every router then stores this information in the event that he
> -) > has a local receiver that wants to join a group, so it knows the source
> -) > for every group and knows how/where to send the s,g join.  Am I
> -) > misinterpreting this?  Are you suggesting that only the LHRs should be
> -) > storing this source info, and the non-LHRs should ignore this source info?
> -) > If so, how does a router know he is a LHR or not?
> -)
> -) This can be an administrative decision. If you know that a router will
> -) not function as a LHR, it can be configured to only forward the
> -) messages. If you have a deployment where most routers only function as
> -) a LHR for a few selected groups, then the routers only need to store
> -) state for those.
>
> Stig- thanks for the clarification.  I read the draft over a few times,
> and saw nothing about this.  As the draft is written today, it appears
> that all routers will flood all source info and cache all of that state.
> I guess you are saying that an unmentioned option is for the non LHRs to
> flood but not cache.  OK, but you have to somehow know who is a LHR, and
> who isn't.  Which you seem to be implying that this can be done via
> config.  Or, I suppose to you could just look and see if you have any
> local igmp state to figure out if you are a LHR.  But that would lead to
> join latency of 1-60s when the joins come after the source starts up, and
> I can't imagine any use case where 30s avg join latency is acceptable.

I'm not talking about dynamic state here. Obviously it is dynamic
whether a router is a LHR or not. What I'm saying is that with a typical
network design, you have transit routers that you know will never be a
LHR (except perhaps for some specific groups like NTP or something, but
the admin would know which groups). Then you have edge routers that are
potential LHRs. If you know that a router will never be the LHR for all
or certain groups, then you could configure it to not store that state.

> Ultimately, the added state isn't so horrible to me.  In most practical
> cases it doesn't really matter that some routers carry the state and
> others don't.  Besides, you seem to be implying that the use case you have
> in mind doesn't have that many sources, so I guess that's OK.  But you
> still end up with flooding of source info across the domain.  That is
> functionally what DM does- flood source info across the domain (and
> reflood periodically) so that you can build SPTs and not need RPs.  The
> message names are different (refreshing prune state and sending grafts to
> join on the SPT vs refreshing sg messages and sending s,g's to join the on
> the SPT), but the functionality is the same.
>
> I'm not trying to wave the DM banner, but rather to suggest that there
> appears to be no desire by anyone to use DM these days- tough to imagine
> anyone proposing new drafts to develop DM now.  I think that provides

I don't want DM either, I would rather have existing DM users move to
SM, and this solution would make that easier. Basically there are
deployments that only use DM because there is no central point of
failure etc. and with this solution we can provide some of those
properties without using DM. Allowing them to move to SM.

> pretty clear evidence for the utility of another proposal that
> functionally does the same thing under a different name: flood source info
> across the domain (and reflood periodically) so that you can build SPTs
> and not need RPs.
>
> And as for the claim that this is more like SSM- this is no more
> SSM-friendly than DM.

It looks a lot like SSM from routing perspective. We're using SM with
only SPTs and no RPs, just like with SSM. The only difference is where
the source discovery is done.

Stig



From lenny@juniper.net  Thu Oct 31 13:56:38 2013
Return-Path: <lenny@juniper.net>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C31F11E8231 for <pim@ietfa.amsl.com>; Thu, 31 Oct 2013 13:56:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.477
X-Spam-Level: 
X-Spam-Status: No, score=-103.477 tagged_above=-999 required=5 tests=[AWL=0.122, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id koMdenwPLgtr for <pim@ietfa.amsl.com>; Thu, 31 Oct 2013 13:56:30 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe003.messaging.microsoft.com [216.32.181.183]) by ietfa.amsl.com (Postfix) with ESMTP id C116521F9E76 for <pim@ietf.org>; Thu, 31 Oct 2013 13:56:15 -0700 (PDT)
Received: from mail8-ch1-R.bigfish.com (10.43.68.234) by CH1EHSOBE015.bigfish.com (10.43.70.65) with Microsoft SMTP Server id 14.1.225.22; Thu, 31 Oct 2013 20:56:14 +0000
Received: from mail8-ch1 (localhost [127.0.0.1])	by mail8-ch1-R.bigfish.com (Postfix) with ESMTP id 5E7DFE015B; Thu, 31 Oct 2013 20:56:14 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:66.129.224.51; KIP:(null); UIP:(null); IPV:NLI; H:P-EMF01-SAC.jnpr.net; RD:none; EFVD:NLI
X-SpamScore: 3
X-BigFish: VPS3(zzzz1f42h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6h1082kzz17326ah8275dh1de097h186068hz2fh2a8h839h944hd25hf0ah11b5h121eh1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h16a6h1758h18e1h1946h19b5h1ad9h1b0ah1b2fh1fb3h1d0ch1d2eh1d3fh1de2h1dfeh1dffh1fe8h1ff5h2216h1155h)
Received-SPF: pass (mail8-ch1: domain of juniper.net designates 66.129.224.51 as permitted sender) client-ip=66.129.224.51; envelope-from=lenny@juniper.net; helo=P-EMF01-SAC.jnpr.net ; SAC.jnpr.net ; 
Received: from mail8-ch1 (localhost.localdomain [127.0.0.1]) by mail8-ch1 (MessageSwitch) id 1383252972701045_4104; Thu, 31 Oct 2013 20:56:12 +0000 (UTC)
Received: from CH1EHSMHS042.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.247])	by mail8-ch1.bigfish.com (Postfix) with ESMTP id A617A24007E; Thu, 31 Oct 2013 20:56:12 +0000 (UTC)
Received: from P-EMF01-SAC.jnpr.net (66.129.224.51) by CH1EHSMHS042.bigfish.com (10.43.69.251) with Microsoft SMTP Server (TLS) id 14.16.227.3; Thu, 31 Oct 2013 20:56:12 +0000
Received: from magenta.juniper.net (172.17.27.123) by P-EMF01-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.146.0; Thu, 31 Oct 2013 13:56:10 -0700
Received: from eng-mail01.juniper.net (eng-mail01.juniper.net [172.17.28.114]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id r9VKRSL18533; Thu, 31 Oct 2013 13:27:28 -0700 (PDT)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id 8A1A51145A;  Thu, 31 Oct 2013 13:27:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id 7F6AF11446; Thu, 31 Oct 2013 13:27:27 -0700 (PDT)
Date: Thu, 31 Oct 2013 13:27:27 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: Stig Venaas <stig@venaas.com>
In-Reply-To: <5272B584.9030805@venaas.com>
Message-ID: <20131031131130.R97291@eng-mail01.juniper.net>
References: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com> <20131028115859.L5138@eng-mail01.juniper.net> <2AE7C375-B94C-4286-BC5C-245192D2574D@cisco.com> <20131028134708.C5138@eng-mail01.juniper.net> <A03B605F-3865-4862-9B91-3639CB8730C2@cisco.com> <20131030124704.F72700@eng-mail01.juniper.net> <25A558C2-5E1E-45BC-B86F-6AB2C61F1075@cisco.com> <20131030133107.A72700@eng-mail01.juniper.net> <52729601.9040606@venaas.com> <20131031104817.O72868@eng-mail01.juniper.net> <5272B584.9030805@venaas.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Oct 2013 20:56:38 -0000

-) > And as for the claim that this is more like SSM- this is no more
-) > SSM-friendly than DM.
-) 
-) It looks a lot like SSM from routing perspective. We're using SM with
-) only SPTs and no RPs, just like with SSM. The only difference is where
-) the source discovery is done.
-) 

All you are doing is changing the name of the protocol, not the behavior.  
You are just making SM act like DM and saying it is better bc it is now SM 
and not DM. The problem with PIM-DM is not the name "PIM-DM"; the problem 
is that it floods source data across the domain.  If you just just make SM 
start flooding source info, that isn't any better.  If you can live with a 
solution that floods source data across the domain so that you can use 
SPTs only and don't care about scale, what's the difference between this 
solution and DM, besides the names of the protocols/messages?

If it looks like a duck, swims like a duck, and quacks like a duck, then 
it probably is a duck. (http://en.wikipedia.org/wiki/Duck_test)


From eckert@cisco.com  Thu Oct 31 17:14:50 2013
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 2D1C511E81E6 for <pim@ietfa.amsl.com>; Thu, 31 Oct 2013 17:14:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.341
X-Spam-Level: 
X-Spam-Status: No, score=-10.341 tagged_above=-999 required=5 tests=[AWL=0.258, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vi9eCofpU7YU for <pim@ietfa.amsl.com>; Thu, 31 Oct 2013 17:14:45 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id D48E311E8198 for <pim@ietf.org>; Thu, 31 Oct 2013 17:14:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8512; q=dns/txt; s=iport; t=1383264886; x=1384474486; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=fhOE8rpoUDYN5DMSjIe8Hhb396EkqSbjXdbcjGlLbgg=; b=aXRduwxeK8/cXxMAiZMEtcW64OwREd9YZTiQ5ICW7Gd9Hn9VzBTY+NZN 5ZECJ4psUe8xNVXkw4OdesuiFpZRqMg0oyoWWYkxvoR+d0zm+csNweNc2 f8ufll0mGS/csgXSFYFP2N8FU2GfE0hx+2xmN40VsZ5enY9ZFCsA4GXk1 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjEFACvyclKrRDoG/2dsb2JhbABZgwc4vEmDc4EjFnSCJQEBAQQBAQEaHTQLEAsOCgklDwUTNhMbh2sOvF+OEIE/B4QuA4lAjkkBkgmDRhyBLA
X-IronPort-AV: E=Sophos;i="4.93,613,1378857600"; d="scan'208";a="96194556"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 01 Nov 2013 00:14:36 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id rA10EY20022712 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 1 Nov 2013 00:14:34 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id rA10EYPG026986;  Thu, 31 Oct 2013 17:14:34 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id rA10EX4d026984; Thu, 31 Oct 2013 17:14:33 -0700
Date: Thu, 31 Oct 2013 17:14:33 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Leonard Giuliano <lenny@juniper.net>
Message-ID: <20131101001433.GX6467@cisco.com>
References: <2AE7C375-B94C-4286-BC5C-245192D2574D@cisco.com> <20131028134708.C5138@eng-mail01.juniper.net> <A03B605F-3865-4862-9B91-3639CB8730C2@cisco.com> <20131030124704.F72700@eng-mail01.juniper.net> <25A558C2-5E1E-45BC-B86F-6AB2C61F1075@cisco.com> <20131030133107.A72700@eng-mail01.juniper.net> <52729601.9040606@venaas.com> <20131031104817.O72868@eng-mail01.juniper.net> <5272B584.9030805@venaas.com> <20131031131130.R97291@eng-mail01.juniper.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20131031131130.R97291@eng-mail01.juniper.net>
User-Agent: Mutt/1.4.2.2i
Cc: Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
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, 01 Nov 2013 00:14:50 -0000

Oh boy...

Short version:
 I support the adoption of this idea wholeheartedly

Long version:
 Long set of rants below, some of which might hopefully be convertable into
 useful explanatory text for the draft:

a) Beneft:

   Ice may have also other use cases in mind (that i am just missing out
   on right now), but IMHO the biggest ones are the cases where PIM-SM/MSDP is
   the best solution today: Not SSM (for apps that can't and will never be able
   to do SSM) and no source-scale issue (eg: no Bidir-case).

   These standard PIM-SM/MSDP deployments provide great but redundant
   job security for vendor consultants and customer architects  to breed,
   feed, cocker and babysit RPs and MSDP: Placement, platform selection,
   redundancy, performance, configuration, troubleshooting, partitioning
   effects and the like. This complexity is 90% of the cost of running
   ASM multicast. And IMHO it is 95% of the reason why multicast is not
   deployed in more eg: enterprises.

   So, yes, this proposal could put me out of one of my jobs because
   i am giving exactly this type of "how to care for your RPs" talk to
   customers - *sob* ;-)

   Oh, and i forgot the lovely breed of DRs and RPs: Lots and lots of
   register tunnels which have even trickled into HW implementations
   because chip designers couldn't find a better feature to waste ASIC
   real estate - and admittedly because customers had real problems without
   that HW accelerateion in some key situations.

   So yes, this proposal would remove the revenues for companies even
   selling register tunnel HW acceleration as an add-on in their
   boxes *sob* *sob* ;-)

b) What happened that this idea came up:

   1. We took a decade to explore all SSM transition options. The customers who
     understand and can, will go to SSM, and use things like SSM
     mapping only as a migration solution - as intended.
     
     But there is a frightning number of customers who are so annoyed
     by PIM-SM/RP/MSDP that they even consider SSM-mapping deployments to
     be better than PIM-SM/RP/MSDP even if there is clearly no way to get
     the apps towards native SSM.

     And we even had asks for SSM mappings in DC-cluster environments
     where one out of 40 sources would send to a group, but with static
     SSM mapping you would have 40 times as much state as with PIM-SM.
     That says a lot about the complexity of RP/MSDP operations.

   2. Multicast trees IMHO are getting denser.  In the 90th it was hip to
     use multicast for any app because you could, now you predominantly
     see new multicast deployments of multicast for apps that can't live 
     without it. And those are apps with a lot of replication == large
     set of receivers.
   
   3. ASM to do source discovery is becoming less relevant. Traditional
     one-off-hacky service discovery was like this: app developers goes
     to IANA asks for a multicast group, and programs it's app clients
     to send a multicast request packet to the group, and have his app
     groups listen to that. Luckily we're getting over that and that
     eliminites the real painful set of bursty-source-apps.

c) Why this solution
   
   b.1) clearly indicates that SSM operationally in the network is
   very successfull with operators. It's even successfull to the extend
   that they consider going way beyond the usefulness of SSM mapping,
   and we should really stop that to happen (with this proposal) because
   that will cause backlash againt SSM in some future when it starts to
   fails to be manageable under change/expansion.

   b.1) + b2) to me means that we want a solution that effectively
   automates SSM mapping. It also means that for the key class of
   deployments, its not a problem to have some control plane flooding
   of Source-Active state into places where it's not needed. The total
   number of states we flood is limited by by the total number of 
   forwarding states we could build. I would guess that >= 90% of
   enterpride PIM deployments have less than 10,000 multicast states
   and with IPv6 and timeouts that's less than half a megabye of memory
   without even trying any optimizations on how we store SAs. And a
   very high likley that all these SAs are useful for the router anyhow
   (b.2).
   
   b.3) also means that it wouldn't leave a lot of PIM-SM apps behind 
   that can not use this solution, so this proposal has a real good chance
   to replace PIM-SM in the mayority of deployments with something that's
   simpler: purely based on SSM forwarding plus the most lightweight way
   to keep ASM apps running.
   
   To rephrase: The original goal of SSM to simplify deployment did not
   happen because SSM could only be added to PIM-SM/RP/MSDP because of
   all the ASM leftover apps. With this proposal we could really have a large
   set of deployments avoid having ever to learn or worry about RPs, MSDP,
   register tunnels and all their associated care.

d) Why not PIM-DM

   PIM-DM might have been quite on-par with PIM-SM in the late 90th,
   but i think since then it has deteriorated. It still is as encumbered by
   data-triggered events as it ever was.

   HW implementations in routers most certainly will not have optimized
   for that in the same way as the optimziations done for PIM-SM/SSM in
   platforms (can't of course speak for all vendors). If i remember correctly,
   assert is still different between DM and SM/SSM (SM/SSM using the same).

   State refresh was never finalized as an RFC. PIM-DM itself is not
   standards track. We never fixed the limitations DM even had vs.
   DVMRP. There are even important products not supporting DM at all,
   and those who do will have more interop issues than PIM-SM/SSM interop.

   Fixing up that badly, incompletely specified and mostly legacy
   implemented DM router hardware forwarding plane as opposed to using the
   PIM-SSM forwarding plane plus one tiny bit from PIM-SM (first hop router
   new (S,G) discovery) is the best choice to maintain all the HW/implementation
   benefits of what we have been using in most deployments in the last
   10 years AND to strip down the complexity in the forwarding plane to the
   minimum needed to suport a form of SSM that be be zero-config for
   the mayority of deployments.

   Last but not least: Maybe i remember DM incorrectly, but i thought
   that even with SR it was necessary to have on all routers (S,G)
   forwarding-plane ("prune") state. That's a totally different problem
   from <= 0.5MByte control plane memory.

   Last but not last: As i mentioned in any rant: I want an SSM network,
   so i want customers to have only the need to do SSM forwarding and
   control plane debugging and as little more as possible. With PIM-DM
   i wold continue to have a totally orthogonal forwading plane and
   control plane that just shares the name "PIM", but that's really double
   effort. With this poposal i have SSM for everything plus some add-on
   for ASM-apps, where i have no idea how we could do the ASM-add on
   any easier.

Cheers
    Toerless

On Thu, Oct 31, 2013 at 01:27:27PM -0700, Leonard Giuliano wrote:
> 
> -) > And as for the claim that this is more like SSM- this is no more
> -) > SSM-friendly than DM.
> -) 
> -) It looks a lot like SSM from routing perspective. We're using SM with
> -) only SPTs and no RPs, just like with SSM. The only difference is where
> -) the source discovery is done.
> -) 
> 
> All you are doing is changing the name of the protocol, not the behavior.  
> You are just making SM act like DM and saying it is better bc it is now SM 
> and not DM. The problem with PIM-DM is not the name "PIM-DM"; the problem 
> is that it floods source data across the domain.  If you just just make SM 
> start flooding source info, that isn't any better.  If you can live with a 
> solution that floods source data across the domain so that you can use 
> SPTs only and don't care about scale, what's the difference between this 
> solution and DM, besides the names of the protocols/messages?
> 
> If it looks like a duck, swims like a duck, and quacks like a duck, then 
> it probably is a duck. (http://en.wikipedia.org/wiki/Duck_test)
> 
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim
