
From lenny@juniper.net  Mon Nov  4 08:47:27 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 0AAAE11E82DA for <pim@ietfa.amsl.com>; Mon,  4 Nov 2013 08:47:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.989
X-Spam-Level: 
X-Spam-Status: No, score=-102.989 tagged_above=-999 required=5 tests=[AWL=-0.390, 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 Zz7M6BklF2r3 for <pim@ietfa.amsl.com>; Mon,  4 Nov 2013 08:47:13 -0800 (PST)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0187.outbound.messaging.microsoft.com [213.199.154.187]) by ietfa.amsl.com (Postfix) with ESMTP id E383921E81C9 for <pim@ietf.org>; Mon,  4 Nov 2013 08:46:31 -0800 (PST)
Received: from mail150-db8-R.bigfish.com (10.174.8.247) by DB8EHSOBE014.bigfish.com (10.174.4.77) with Microsoft SMTP Server id 14.1.225.22; Mon, 4 Nov 2013 16:46:30 +0000
Received: from mail150-db8 (localhost [127.0.0.1])	by mail150-db8-R.bigfish.com (Postfix) with ESMTP id AA412201BC; Mon,  4 Nov 2013 16:46:30 +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: -19
X-BigFish: VPS-19(zzdb82h98dI1447Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6h1082kzz1de098h1033IL17326ah8275dh1de097h186068hz2fh2a8h839h944hd25hf0ah11b5h121eh1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h16a6h1758h18e1h1946h19b5h1ad9h1b0ah1b2fh1fb3h1d0ch1d2eh1d3fh1de2h1dfeh1dffh1fe8h1ff5h2216h1155h)
Received-SPF: pass (mail150-db8: 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 mail150-db8 (localhost.localdomain [127.0.0.1]) by mail150-db8 (MessageSwitch) id 1383583588503556_451; Mon,  4 Nov 2013 16:46:28 +0000 (UTC)
Received: from DB8EHSMHS027.bigfish.com (unknown [10.174.8.241])	by mail150-db8.bigfish.com (Postfix) with ESMTP id 6D88F140066; Mon,  4 Nov 2013 16:46:28 +0000 (UTC)
Received: from P-EMF01-SAC.jnpr.net (66.129.224.54) by DB8EHSMHS027.bigfish.com (10.174.4.37) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 4 Nov 2013 16:46:27 +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, 4 Nov 2013 08:46:23 -0800
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 rA4GkGL13471; Mon, 4 Nov 2013 08:46:22 -0800 (PST)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id 1685D1148C;  Mon,  4 Nov 2013 08:46:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id 0B0991148B; Mon,  4 Nov 2013 08:46:16 -0800 (PST)
Date: Mon, 4 Nov 2013 08:46:16 -0800
From: Leonard Giuliano <lenny@juniper.net>
To: Toerless Eckert <eckert@cisco.com>
In-Reply-To: <20131101001433.GX6467@cisco.com>
Message-ID: <20131104075423.N23002@eng-mail01.juniper.net>
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> <20131101001433.GX6467@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, 04 Nov 2013 16:47:27 -0000

Toerless- thanks for the details and explanation.  

The big challenge for ASM multicast routing protocols is source discovery.  
That is, if the receiver doesn't tell you who the source is, the network 
needs to figure this out.  PIM-DM accomplished this with flooding so that 
all routers in the domain become aware of the sources and can join using 
an SPT.  It is really simple, however due to this flooding, it is not 
scalable nor interdomain-friendly.  PIM-SM, on the other hand, uses RPs as 
a meeting place to know all source info, then starts with shared trees 
that may switch to SPTs.  PIM-SM is way more complex, but is far more 
scalable and supportive of interdomain.

This proposal, like DM, simply reuses the flooding concept to distribute 
source info throughout the domain.  By ignoring bursty source apps (which 
is perfectly reasonable and defensible, IMO), it just floods this source 
control traffic, rather than the actual data, which DM does at least 
initially (DM state refresh can be used susequently to refresh state by 
just reflooding the source control traffic, rather than data).  This 
proposal does have to periodically reflood the source info to refresh 
state, which is similiar to the DM state refresh.  Now, there is some 
benefit with this proposal by not requiring all the non-LHRs to cache the 
source messages (though, I can't seem to find this in the draft), but 
given the limited use cases you have in mind, that's probabaly not much 
gain.  So, comparing this proposal to DM: flooding of the data packets 
initially is eliminated (but there still is control traffic flooding), it 
is more of a flood-and-join model than a flood-and-prune model, and there 
is some minor state reduction on some intermediate routers.  All said, 
IMO, these are minimal, sublinear benefits over DM, but benefits 
nonetheless.

Now, doing roughly the same thing in 2 different protocols is done all the 
time, sometimes even for valid reasons ;)  Variety is, after all, the 
spice of life.  However, alternatives are usually used when there is a 
high demand for this mechanism.

In requesting adoption, the implicit question is if this is a problem 
worth working on.  Some will say yes, some no, but in most cases it's 
supposition and guesswork.  In this case, we have clear, unambiguous 
evidence in the PIM-DM experience to guide us when it comes to using 
flooding to distribute source info through a domain to eliminate the 
complexity of SM.  And that experience with DM is not good.  The DM spec 
was left for Experimental Limbo almost a decade ago.  Years before that, 
state refresh, which IMO is about 75% of what this new proposal does, was 
abandoned while still incomplete.  I don't recall seeing any proposals in 
all the time since to do anything more to DM.  Is this complete lack of 
interest in DM not a clear indicator?

Put another way, try the following thought experiment:  imagine someone 
submitted a draft for PIM-DMv2.  It sought to fix the problems of DM, 
eliminating data flooding for the initial flood, fixing state refresh for 
the subsequent refloods, adding the option to not cache the state on the 
non-LHRs, and moving towards explicit join.  Would there be enough support 
to adopt that?  I for one would not support a PIM-DMv2 effort based on the 
experiences of PIM-DMv1 and the fact that these improvements are marginal 
and sublinear.  

IMO, this draft is essentially PIM-DMv2 by another name.


On Thu, 31 Oct 2013, Toerless Eckert wrote:

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


From ice@cisco.com  Mon Nov  4 09:32: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 27F9B11E8375 for <pim@ietfa.amsl.com>; Mon,  4 Nov 2013 09:32:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.421
X-Spam-Level: 
X-Spam-Status: No, score=-10.421 tagged_above=-999 required=5 tests=[AWL=0.178, 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 PvMAdvu4iIlp for <pim@ietfa.amsl.com>; Mon,  4 Nov 2013 09:32:13 -0800 (PST)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 3948E11E829F for <pim@ietf.org>; Mon,  4 Nov 2013 09:29:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11422; q=dns/txt; s=iport; t=1383586174; x=1384795774; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=Xmcf4FC9woRXmlsk9etGeGtPhNygl4a1IEDnUuyQRmI=; b=ifw6r/FklaCNLDlJqhcWYLg6NthPvFifE5G/v0d3+ZwxV6ZLvirj+qyH P9K5rVDF13SYQu3U7iroVTa+HvVU+vDuPpiFQmDjmKJvRBrtHQz3ieI65 SAWL/Ii4z7F6IDxqAAMyZZWJPOHRLln5p4y7/NFZj48M5IaiUZ7+qLQ+q 0=;
X-IronPort-AV: E=Sophos;i="4.93,633,1378857600"; d="scan'208";a="18768147"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-3.cisco.com with ESMTP; 04 Nov 2013 17:29:31 +0000
Received: from [10.61.213.253] ([10.61.213.253]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id rA4HTL4B031011 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 4 Nov 2013 17:29: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: <20131104075423.N23002@eng-mail01.juniper.net>
Date: Mon, 4 Nov 2013 09:29:20 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <ECD09B63-5E6A-45E5-BC01-B284C6FF0C15@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> <20131101001433.GX6467@cisco.com> <20131104075423.N23002@eng-mail01.juniper.net>
To: Leonard Giuliano <lenny@juniper.net>
X-Mailer: Apple Mail (2.1499)
Cc: Toerless Eckert <eckert@cisco.com>, 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, 04 Nov 2013 17:32:20 -0000

Lenny,

> that may switch to SPTs.  PIM-SM is way more complex, but is far more=20=

> scalable and supportive of inter domain.

This solution is not intended for Inter-domain and targeted for low =
scale.

> initially is eliminated (but there still is control traffic flooding), =
it=20
> is more of a flood-and-join model than a flood-and-prune model, and =
there=20
> is some minor state reduction on some intermediate routers.  All said,=20=

> IMO, these are minimal, sublinear benefits over DM, but benefits=20
> nonetheless.

You keep saying this is like DM, but above you perfectly describe the =
different. Its a flood and join model, where DM is a flood and prune =
model. That is fundamentally different in the control plane.

Flooding BSR messages only creates state in the control plane. With =
PIM-DM, you also create state in the forwarding plane. An other big =
difference.

> flooding to distribute source info through a domain to eliminate the=20=

> complexity of SM.  And that experience with DM is not good.  The DM =
spec=20

According to your analogy, BSR RP distribution/discovery for PIM-SM is =
also like DM. RP information is flooded periodically through the =
network, interested egress routers join to the RP for the Group Mapping =
it received. This is nonsense of course.

The only difference we are proposing to this behaviour is that the =
mapping can be a Source-Group mapping, and not a RP-Group mapping.=20

Thx,

Ice.

>=20
>=20
>=20
> On Thu, 31 Oct 2013, Toerless Eckert wrote:
>=20
> -) Oh boy...
> -)=20
> -) Short version:
> -)  I support the adoption of this idea wholeheartedly
> -)=20
> -) Long version:
> -)  Long set of rants below, some of which might hopefully be =
convertable into
> -)  useful explanatory text for the draft:
> -)=20
> -) a) Beneft:
> -)=20
> -)    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).
> -)=20
> -)    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.
> -)=20
> -)    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* ;-)
> -)=20
> -)    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.
> -)=20
> -)    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* ;-)
> -)=20
> -) b) What happened that this idea came up:
> -)=20
> -)    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.
> -)     =20
> -)      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.
> -)=20
> -)      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.
> -)=20
> -)    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=20
> -)      without it. And those are apps with a lot of replication =3D=3D =
large
> -)      set of receivers.
> -)   =20
> -)    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.
> -)=20
> -) c) Why this solution
> -)   =20
> -)    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.
> -)=20
> -)    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=20=

> -)    forwarding states we could build. I would guess that >=3D 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).
> -)   =20
> -)    b.3) also means that it wouldn't leave a lot of PIM-SM apps =
behind=20
> -)    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.
> -)   =20
> -)    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.
> -)=20
> -) d) Why not PIM-DM
> -)=20
> -)    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.
> -)=20
> -)    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).
> -)=20
> -)    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.
> -)=20
> -)    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.
> -)=20
> -)    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 <=3D 0.5MByte control plane memory.
> -)=20
> -)    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.
> -)=20
> -) Cheers
> -)     Toerless
> -)=20
> -) On Thu, Oct 31, 2013 at 01:27:27PM -0700, Leonard Giuliano wrote:
> -) >=20
> -) > -) > And as for the claim that this is more like SSM- this is no =
more
> -) > -) > SSM-friendly than DM.
> -) > -)=20
> -) > -) 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.
> -) > -)=20
> -) >=20
> -) > All you are doing is changing the name of the protocol, not the =
behavior. =20
> -) > You are just making SM act like DM and saying it is better bc it =
is now SM=20
> -) > and not DM. The problem with PIM-DM is not the name "PIM-DM"; the =
problem=20
> -) > is that it floods source data across the domain.  If you just =
just make SM=20
> -) > start flooding source info, that isn't any better.  If you can =
live with a=20
> -) > solution that floods source data across the domain so that you =
can use=20
> -) > SPTs only and don't care about scale, what's the difference =
between this=20
> -) > solution and DM, besides the names of the protocols/messages?
> -) >=20
> -) > If it looks like a duck, swims like a duck, and quacks like a =
duck, then=20
> -) > it probably is a duck. (http://en.wikipedia.org/wiki/Duck_test)
> -) >=20
> -) > _______________________________________________
> -) > pim mailing list
> -) > pim@ietf.org
> -) > https://www.ietf.org/mailman/listinfo/pim
> -)=20
>=20
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim


From eckert@cisco.com  Mon Nov  4 09:41:24 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 1286521E822B for <pim@ietfa.amsl.com>; Mon,  4 Nov 2013 09:41:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.081
X-Spam-Level: 
X-Spam-Status: No, score=-10.081 tagged_above=-999 required=5 tests=[AWL=-0.082, BAYES_00=-2.599, J_CHICKENPOX_21=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 STOs6vc+Nf0b for <pim@ietfa.amsl.com>; Mon,  4 Nov 2013 09:41:19 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id A8B0521E80A5 for <pim@ietf.org>; Mon,  4 Nov 2013 09:41:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14677; q=dns/txt; s=iport; t=1383586873; x=1384796473; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=7N0GvAgAXF1AaAwGxkADa+fq+zhx0cbSPmAAElBtmSQ=; b=mnyuRLjh7/x+In8FcXM4yeoSOBXByC8iCV5Xs1uqGahO0zDWVfa6b/OF c8xz8l/mLFeRsPOmu8PDu+31+1XWJzaxkXgmjdgTPL6Fw35eFMUtc3woG /sRFYyFB5Pm3QhPwo2k+AbqxxUA1KlepAgnV01rwNRUhY2p8TZu+RTAiO 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFAPnbd1KrRDoJ/2dsb2JhbABZgwc4vBuDdoEpFnSCJQEBAQQBAQEaHTICCAMQCw4EBgklDwUTIhQTGQKHZQ6+R44ZBoE5B4QuA4lAjkkBkgmDRxuBLAkX
X-IronPort-AV: E=Sophos;i="4.93,633,1378857600"; d="scan'208";a="93290067"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-1.cisco.com with ESMTP; 04 Nov 2013 17:40:54 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id rA4HeqQu024621 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Nov 2013 17:40:52 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 rA4HeqqA027085;  Mon, 4 Nov 2013 09:40:52 -0800
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id rA4Heppf027084; Mon, 4 Nov 2013 09:40:51 -0800
Date: Mon, 4 Nov 2013 09:40:51 -0800
From: Toerless Eckert <eckert@cisco.com>
To: Leonard Giuliano <lenny@juniper.net>
Message-ID: <20131104174051.GQ6467@cisco.com>
References: <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> <20131101001433.GX6467@cisco.com> <20131104075423.N23002@eng-mail01.juniper.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20131104075423.N23002@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: Mon, 04 Nov 2013 17:41:24 -0000

Thanks, Lenny.

The PIM-DMv2 thought experiment is a good idea.
  - i still would not have SSM forwarding and PIM-control-plane but
    something different. Duplication of operational knowledge requirements.
    (assuming of course i will also have PIM-SSM capable apps in the network!).
  - I very much assume i would still have even on intermediate
    hops daa-triggered events
  - Still wouldn't be able to solve the basic prune issues where PIM-DM
    is worse than DVMRP.
  - If i'd outgrow the scale limits of flooding i can't smoothly change
    the SA signaling model to something better without changing the
    underlying forwarding/PIM_signaling plane from DM to SM. 
  - I could not plug potentially different SA signaling mechanisms
    (eg: better than just flood) into the system.
  - Wouldn't create an incentive to get rid of bursty source apps

Is the incentive for this new idea great enough to make it happen ?
I think we should well investigate this. As i tried to elaborate in the
prior mail more, i think iv'e seen a lot of cases where really bad workarounds
where used to come close to this, and there are IMHO equally many
networks where multicast isn't deployed because PIM-SM/MSDP is too 
difficult and PIM-DM known to not be a problem of scale but reliability
due to rot of implementation/specs and above described limits of mechanisms.

Cheers
    Toerless

On Mon, Nov 04, 2013 at 08:46:16AM -0800, Leonard Giuliano wrote:
> 
> Toerless- thanks for the details and explanation.  
> 
> The big challenge for ASM multicast routing protocols is source discovery.  
> That is, if the receiver doesn't tell you who the source is, the network 
> needs to figure this out.  PIM-DM accomplished this with flooding so that 
> all routers in the domain become aware of the sources and can join using 
> an SPT.  It is really simple, however due to this flooding, it is not 
> scalable nor interdomain-friendly.  PIM-SM, on the other hand, uses RPs as 
> a meeting place to know all source info, then starts with shared trees 
> that may switch to SPTs.  PIM-SM is way more complex, but is far more 
> scalable and supportive of interdomain.
> 
> This proposal, like DM, simply reuses the flooding concept to distribute 
> source info throughout the domain.  By ignoring bursty source apps (which 
> is perfectly reasonable and defensible, IMO), it just floods this source 
> control traffic, rather than the actual data, which DM does at least 
> initially (DM state refresh can be used susequently to refresh state by 
> just reflooding the source control traffic, rather than data).  This 
> proposal does have to periodically reflood the source info to refresh 
> state, which is similiar to the DM state refresh.  Now, there is some 
> benefit with this proposal by not requiring all the non-LHRs to cache the 
> source messages (though, I can't seem to find this in the draft), but 
> given the limited use cases you have in mind, that's probabaly not much 
> gain.  So, comparing this proposal to DM: flooding of the data packets 
> initially is eliminated (but there still is control traffic flooding), it 
> is more of a flood-and-join model than a flood-and-prune model, and there 
> is some minor state reduction on some intermediate routers.  All said, 
> IMO, these are minimal, sublinear benefits over DM, but benefits 
> nonetheless.
> 
> Now, doing roughly the same thing in 2 different protocols is done all the 
> time, sometimes even for valid reasons ;)  Variety is, after all, the 
> spice of life.  However, alternatives are usually used when there is a 
> high demand for this mechanism.
> 
> In requesting adoption, the implicit question is if this is a problem 
> worth working on.  Some will say yes, some no, but in most cases it's 
> supposition and guesswork.  In this case, we have clear, unambiguous 
> evidence in the PIM-DM experience to guide us when it comes to using 
> flooding to distribute source info through a domain to eliminate the 
> complexity of SM.  And that experience with DM is not good.  The DM spec 
> was left for Experimental Limbo almost a decade ago.  Years before that, 
> state refresh, which IMO is about 75% of what this new proposal does, was 
> abandoned while still incomplete.  I don't recall seeing any proposals in 
> all the time since to do anything more to DM.  Is this complete lack of 
> interest in DM not a clear indicator?
> 
> Put another way, try the following thought experiment:  imagine someone 
> submitted a draft for PIM-DMv2.  It sought to fix the problems of DM, 
> eliminating data flooding for the initial flood, fixing state refresh for 
> the subsequent refloods, adding the option to not cache the state on the 
> non-LHRs, and moving towards explicit join.  Would there be enough support 
> to adopt that?  I for one would not support a PIM-DMv2 effort based on the 
> experiences of PIM-DMv1 and the fact that these improvements are marginal 
> and sublinear.  
> 
> IMO, this draft is essentially PIM-DMv2 by another name.
> 
> 
> On Thu, 31 Oct 2013, Toerless Eckert wrote:
> 
> -) 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
> -) 

-- 
---
Toerless Eckert, eckert@cisco.com
Cisco NSSTG Systems & Technology Architecture
SDN: Let me play with the network, mommy!


From lenny@juniper.net  Mon Nov  4 10:19:05 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 E213921F9FCA for <pim@ietfa.amsl.com>; Mon,  4 Nov 2013 10:19:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.954
X-Spam-Level: 
X-Spam-Status: No, score=-104.954 tagged_above=-999 required=5 tests=[AWL=1.645, 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 Z3UneZ4MtBI1 for <pim@ietfa.amsl.com>; Mon,  4 Nov 2013 10:18:59 -0800 (PST)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe004.messaging.microsoft.com [207.46.163.27]) by ietfa.amsl.com (Postfix) with ESMTP id E759211E81F9 for <pim@ietf.org>; Mon,  4 Nov 2013 10:18:56 -0800 (PST)
Received: from mail133-co9-R.bigfish.com (10.236.132.239) by CO9EHSOBE028.bigfish.com (10.236.130.91) with Microsoft SMTP Server id 14.1.225.22; Mon, 4 Nov 2013 18:18:53 +0000
Received: from mail133-co9 (localhost [127.0.0.1])	by mail133-co9-R.bigfish.com (Postfix) with ESMTP id 39EF1CC0128; Mon,  4 Nov 2013 18:18:53 +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: 1
X-BigFish: VPS1(zzdb82h98dI146fIzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6h1082kzzz2fh2a8h839h944hd25hf0ah11b5h121eh1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h16a6h1758h18e1h1946h19b5h1ad9h1b0ah1b2fh1fb3h1d0ch1d2eh1d3fh1de2h1dfeh1dffh1fe8h1ff5h2216h1155h)
Received-SPF: pass (mail133-co9: 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 mail133-co9 (localhost.localdomain [127.0.0.1]) by mail133-co9 (MessageSwitch) id 1383589131708895_21081; Mon,  4 Nov 2013 18:18:51 +0000 (UTC)
Received: from CO9EHSMHS019.bigfish.com (unknown [10.236.132.231])	by mail133-co9.bigfish.com (Postfix) with ESMTP id 9DA1D3C003F; Mon,  4 Nov 2013 18:18:51 +0000 (UTC)
Received: from P-EMF01-SAC.jnpr.net (66.129.224.53) by CO9EHSMHS019.bigfish.com (10.236.130.29) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 4 Nov 2013 18:18:50 +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, 4 Nov 2013 10:18:50 -0800
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 rA4IInL63509; Mon, 4 Nov 2013 10:18:49 -0800 (PST)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id D7C761144F;  Mon,  4 Nov 2013 10:18:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id CCF421144E; Mon,  4 Nov 2013 10:18:48 -0800 (PST)
Date: Mon, 4 Nov 2013 10:18:48 -0800
From: Leonard Giuliano <lenny@juniper.net>
To: IJsbrand Wijnands <ice@cisco.com>
In-Reply-To: <ECD09B63-5E6A-45E5-BC01-B284C6FF0C15@cisco.com>
Message-ID: <20131104100616.B32334@eng-mail01.juniper.net>
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> <20131101001433.GX6467@cisco.com> <20131104075423.N23002@eng-mail01.juniper.net> <ECD09B63-5E6A-45E5-BC01-B284C6FF0C15@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: Toerless Eckert <eckert@cisco.com>, 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, 04 Nov 2013 18:19:05 -0000

On Mon, 4 Nov 2013, IJsbrand Wijnands wrote:

-) Lenny,
-) 
-) > that may switch to SPTs.  PIM-SM is way more complex, but is far more 
-) > scalable and supportive of inter domain.
-) 
-) This solution is not intended for Inter-domain and targeted for low scale.

If one doesn't care about interdomain or scale, then just about EVERYTHING 
will be good enough.  For example, static SSM mappings will do precisely 
what you want.  However, based on Toerless' comments, static SSM mapping 
doesn't scale well enough for this use case.

So I suppose the motivation here is SOME scalability, just not too much of 
it ;)

-) According to your analogy, BSR RP distribution/discovery for PIM-SM is 
-) also like DM. RP information is flooded periodically through the 
-) network, interested egress routers join to the RP for the Group Mapping 
-) it received. This is nonsense of course.
-) 
-) The only difference we are proposing to this behaviour is that the 
-) mapping can be a Source-Group mapping, and not a RP-Group mapping.

Well, I'm no fan of BSR and would love to see that deprecated as well, as 
Static Anycast RP gives you more benefits with none of the complexity.  
But that ship sailed...

Anyway, as I mentioned earlier, there is a HUGE difference between 
group-RP mappings and s-g mappings.  In many/most deployments, especially 
for the simple deployments you seem to have in mind, a single 224/4 
mapping to an RP is sufficient.  I suspect this proposal would envisage 
the deployment to have > 1 s-g in the domain?


From jeff.tantsura@ericsson.com  Tue Nov  5 11:24:53 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 DBFF511E81C4 for <pim@ietfa.amsl.com>; Tue,  5 Nov 2013 11:24:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.194
X-Spam-Level: 
X-Spam-Status: No, score=-2.194 tagged_above=-999 required=5 tests=[AWL=-0.195, 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 04gqlZC5u63O for <pim@ietfa.amsl.com>; Tue,  5 Nov 2013 11:24:48 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 5335D11E8142 for <pim@ietf.org>; Tue,  5 Nov 2013 11:24:47 -0800 (PST)
X-AuditID: c618062d-b7fd88e00000439f-9e-527945fe9a91
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 03.B5.17311.EF549725; Tue,  5 Nov 2013 20:24:46 +0100 (CET)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.02.0328.009; Tue, 5 Nov 2013 14:24:46 -0500
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: IJsbrand Wijnands <ice@cisco.com>, "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
Thread-Topic: [pim] draft-wijnands-pim-source-discovery-bsr call for adoption
Thread-Index: AQHO1ImJeVIa22rD30Kay1ePXEfBwJoW3fuA
Date: Tue, 5 Nov 2013 19:24:45 +0000
Message-ID: <60DEDD93F5E54B4AB55647B8B6C748399954D4@eusaamb109.ericsson.se>
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: 
user-agent: Microsoft-MacOutlook/14.2.5.121010
x-originating-ip: [147.117.188.135]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C88523CD8AD5A64F8E56BDB16A3D6AA6@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrOLMWRmVeSWpSXmKPExsUyuXSPn+4/18ogg/Wn1C1ezbnDbPH13lwm iy8PbzJbHLnYyOLA4jHl90ZWj52z7rJ7LFnyk8njetNV9gCWKC6blNSczLLUIn27BK6MZ0va 2QsOSVQ8azvC0sC4V6SLkZNDQsBE4s6uGSwQtpjEhXvr2boYuTiEBI4wSrx9+oURwlnGKNG+ aS8zSBWbgIHE/2/HgTo4OEQEwiX+t0WChJkFXCWanm0GKxEW8JGYsLkFzBYR8JX4v+4IE4Rt JHHj0T5WEJtFQEXi/9QJzCBjeAW8JRb05IOYnAK2EnfuSoBUMAKd8/3UGiaI6eISt57MZ4I4 U0BiyZ7zzBC2qMTLx//AJooK6Em0HTvDDhFXlvg+5xELRK+OxILdn9ggbGuJvpMXGCFsbYll C1+DzeEVEJQ4OfMJywRG8VlI1s1C0j4LSfssJO2zkLQvYGRdxchRWpxalptuZLCJERh5xyTY dHcw7nlpeYhRmoNFSZz3y1vnICGB9MSS1OzU1ILUovii0pzU4kOMTBycUg2MbD/ZA7NVMo9L sPyY+CB99x3BWVtiNO2SFnIvbjihfDGkmOXD9X9uEkWFi7hEXnT+M1blOB/5cfGa/oKd+75/ 7l/481Wn8RrBhS++9x2yko3lPp6gymDJJthi+Ds717OtyU7V9P9lpbmXXvccNGtVOCLP9kqv tCM7gUVfPaCnKDphvcsUpV1KLMUZiYZazEXFiQBkbu/AigIAAA==
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, 05 Nov 2013 19:24:54 -0000

Hi,

I support adoption of this draft, I believe it is useful for a multicast
enabled enterprise environment.

Cheers,
Jeff


-----Original Message-----

>>>>=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
>
>_______________________________________________
>pim mailing list
>pim@ietf.org
>https://www.ietf.org/mailman/listinfo/pim


From hermin.anggawijaya@gmail.com  Tue Nov  5 22:02:02 2013
Return-Path: <hermin.anggawijaya@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 B0FD611E8200 for <pim@ietfa.amsl.com>; Tue,  5 Nov 2013 22:02:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.044
X-Spam-Level: 
X-Spam-Status: No, score=-2.044 tagged_above=-999 required=5 tests=[AWL=0.555,  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 BrAvH72TWywx for <pim@ietfa.amsl.com>; Tue,  5 Nov 2013 22:02:01 -0800 (PST)
Received: from mail-vc0-x22b.google.com (mail-vc0-x22b.google.com [IPv6:2607:f8b0:400c:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 775AF11E818B for <pim@ietf.org>; Tue,  5 Nov 2013 22:02:01 -0800 (PST)
Received: by mail-vc0-f171.google.com with SMTP id ik5so6243268vcb.2 for <pim@ietf.org>; Tue, 05 Nov 2013 22:02:00 -0800 (PST)
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=W8hs+4jQuoykbiIt5ak7FMDv6kQIaBYeo9c+1wOV70g=; b=A3pUqAHdfORoxdJgXFHr0hiCDRjW4W7a3ViVE/uo8apNkxQOOov+4eLdaY5+Ho5Z7U nuFEAv8uSwyALymcPNPMYDTa2f1EJIa8s4Cl+NrCbyUz3dmftYqJir23fam45Qh/qxZt Wc+I6E0h174ppkxGEdCPTIsEwKJuMQp8EFOPAQIIDOo394VbdK0C62av/sKtJ0YpNCYR OmVYY7lTqR1hgF55FeTdrPVp2wxyg22EOY1l0ZbJa2btTYA/1ci2tc71bB7fN7hwfrYi ZU3KPR5ICpRfc5LtAOKoSXGl/je97qiUkrGjlMJ0yvTu26fcQd/hBS3mmQSEiHJjaTYT 0tfg==
MIME-Version: 1.0
X-Received: by 10.58.180.227 with SMTP id dr3mr275477vec.36.1383717720833; Tue, 05 Nov 2013 22:02:00 -0800 (PST)
Received: by 10.58.188.72 with HTTP; Tue, 5 Nov 2013 22:02:00 -0800 (PST)
Date: Tue, 5 Nov 2013 22:02:00 -0800
Message-ID: <CAJgsEzVZeyWt-RuFVa9-ohoizs5uKZpWeF+Y6kWPEvbZOb3MLQ@mail.gmail.com>
From: Hermin Anggawijaya <hermin.anggawijaya@gmail.com>
To: pim@ietf.org
Content-Type: multipart/alternative; boundary=047d7b66fbcf3844b104ea7be364
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, 06 Nov 2013 06:02:02 -0000

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

I support the WG adoption of this draft.


Regards

Angga


-----Original Message-----

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

--047d7b66fbcf3844b104ea7be364
Content-Type: text/html; charset=ISO-8859-1

<div dir="ltr"><div><div><div><br></div>I support the WG adoption of this draft.<br><br><br></div>Regards<br><br></div>Angga<br><br><br>-----Original Message-----<br>
<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; From: <a href="mailto:pim-bounces@ietf.org">pim-bounces@ietf.org</a> [mailto:<a href="mailto:pim-bounces@ietf.org">pim-bounces@ietf.org</a>] On Behalf Of<br>
&gt;&gt;&gt; Mike McBride<br>
&gt;&gt;&gt;&gt; Sent: Friday, October 25, 2013 6:08 PM<br>
&gt;&gt;&gt;&gt; To: <a href="mailto:pim@ietf.org">pim@ietf.org</a><br>
&gt;&gt;&gt;&gt; Subject: [pim] draft-wijnands-pim-source-<div id=":2pw">discovery-bsr call for<br>
&gt;&gt;&gt; adoption<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; The authors of draft-wijnands-pim-source-discovery-bsr-03 have<br>
&gt;&gt;&gt; requested that we initiate a call for adoption of their draft which<br>
&gt;&gt;&gt; they presented in our last meeting in Berlin. Notes from that<br>
&gt;&gt;&gt; presentation are below. Please comment over the next week (before ietf<br>
&gt;&gt;&gt; week) on your interest/non-interest with adoption of this draft.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; <a href="http://www.ietf.org/id/draft-wijnands-pim-source-discovery-bsr-03.txt" target="_blank">http://www.ietf.org/id/draft-wijnands-pim-source-discovery-bsr-03.txt</a><br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; thanks,<br>
&gt;&gt;&gt;&gt; mike<br>
&gt;&gt;&gt;&gt;</div><br><div><div><div><div><div><div id=":2ow"><br>
</div></div></div></div></div></div></div>

--047d7b66fbcf3844b104ea7be364--

From hermin.anggawijaya@gmail.com  Tue Nov  5 23:02:57 2013
Return-Path: <hermin.anggawijaya@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 823BB21E80D1 for <pim@ietfa.amsl.com>; Tue,  5 Nov 2013 23:02:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.883
X-Spam-Level: 
X-Spam-Status: No, score=-1.883 tagged_above=-999 required=5 tests=[AWL=0.117,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=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 BYw4CRKUsZ9q for <pim@ietfa.amsl.com>; Tue,  5 Nov 2013 23:02:57 -0800 (PST)
Received: from mail-vb0-x235.google.com (mail-vb0-x235.google.com [IPv6:2607:f8b0:400c:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id F21E221E80C2 for <pim@ietf.org>; Tue,  5 Nov 2013 23:02:56 -0800 (PST)
Received: by mail-vb0-f53.google.com with SMTP id i11so3171389vbh.12 for <pim@ietf.org>; Tue, 05 Nov 2013 23:02:56 -0800 (PST)
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=5JKhtxK5m32R7zBJMpY+ijNjky0b03eVB2dzEyTeqt4=; b=Uu4XZO659iMOIcu8+Wi/Zqauq8C8glCxf1+RiuRJIw7cB10vLJI4BaoUjzM6WOOvHr TaOB22p0xv1sOIWE0UEityhgJSrlWBnTC8rUWfKRy0eLevpJCkTbHjWTLLKPe2k8q6F/ /gVME7Cvcos1NvxlfKYXTEaJsVsFsEetZwgsS+h2J6BVKtsu0icRXj3ujvd8bLGD5yD4 mzwzsRtpR5StcbJ2t4i+oH5s2UxJHdeIFr2UUOy++723zkjEmR3irSOo8IfrA51b9XSI PduNtI45jttaIearn8ui4mrh2sADPA6mvOv89GYotUGQCI2GZjcNs9bdg9OjY/TMBZIO qgSQ==
MIME-Version: 1.0
X-Received: by 10.58.108.196 with SMTP id hm4mr1151348veb.28.1383721376372; Tue, 05 Nov 2013 23:02:56 -0800 (PST)
Received: by 10.58.188.72 with HTTP; Tue, 5 Nov 2013 23:02:56 -0800 (PST)
Date: Tue, 5 Nov 2013 23:02:56 -0800
Message-ID: <CAJgsEzXU_Rt+hpEJXwGzs+D-9MW9KVqbpV1Pvmwu8_sU+6jozQ@mail.gmail.com>
From: Hermin Anggawijaya <hermin.anggawijaya@gmail.com>
To: pim@ietf.org, ice@cisco.com, stig@cisco.com, michael.brig@mda.mil
Content-Type: multipart/alternative; boundary=001a11c3b4ac1b5f8304ea7cbd22
Subject: [pim] Comments on draft-wijnands-pim-source-discovery-bsr-03
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, 06 Nov 2013 07:02:57 -0000

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

Hello

Here are some comments on the draft

1) given the discussion that has been happening in v6ops on IPv6 fragments
dropping, I think it might be useful if the draft either sets a limit on
the total length of the PFP message
(for example  'min MTU' - IPv6 header length, or other appropriate limit),
or has an implementation guidance so that PFP messages sent by an
implementation are smaller than the effective MTU of the intended egress
interface, and split the SG info over multiple PFP messages if needed.

2) might like to add more details to the 'Processing SG Messages' such as
message length checking (if limit is specified in draft), checksum
checking, RPF checking (msg is received from RPF neighbour towards
originator)

3) might also want to suggest that implementation may want to allow manual
SG info configuration in the FHR as an alternative to msnip to deal with
the 'first' packet issue.

regards

Angga

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

<div dir=3D"ltr"><div><div><div><div><div><div>Hello <br><br></div><div>Her=
e are some comments on the draft<br></div><div><br></div>1) given the discu=
ssion that has been happening in v6ops on IPv6 fragments dropping, I think =
it might be useful if the draft either sets a limit on the total length of =
the PFP message<br>
</div>(for example=A0 &#39;min MTU&#39; - IPv6 header length, or other appr=
opriate limit), or has an implementation guidance so that PFP messages sent=
 by an implementation are smaller than the effective MTU of the intended eg=
ress interface, and split the SG info over multiple PFP messages if needed.=
<br>
<br></div>2) might like to add more details to the &#39;Processing SG Messa=
ges&#39; such as message length checking (if limit is specified in draft), =
checksum checking, RPF checking (msg is received from RPF neighbour towards=
 originator)<br>
<br></div>3) might also want to suggest that implementation may want to all=
ow manual SG info configuration in the FHR as an alternative to msnip to de=
al with the &#39;first&#39; packet issue.<br><br></div>regards<br><br></div=
>
Angga<br><br><div><div><div><div><div><br></div></div></div></div></div></d=
iv>

--001a11c3b4ac1b5f8304ea7cbd22--

From lenny@juniper.net  Wed Nov  6 08:41:01 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 131A921E8142 for <pim@ietfa.amsl.com>; Wed,  6 Nov 2013 08:41:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.791
X-Spam-Level: 
X-Spam-Status: No, score=-102.791 tagged_above=-999 required=5 tests=[AWL=-0.792, BAYES_00=-2.599, J_CHICKENPOX_21=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 JsfD5z+uIQPy for <pim@ietfa.amsl.com>; Wed,  6 Nov 2013 08:40:56 -0800 (PST)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0187.outbound.messaging.microsoft.com [213.199.154.187]) by ietfa.amsl.com (Postfix) with ESMTP id 8C2F121E8138 for <pim@ietf.org>; Wed,  6 Nov 2013 08:40:55 -0800 (PST)
Received: from mail80-db8-R.bigfish.com (10.174.8.247) by DB8EHSOBE005.bigfish.com (10.174.4.68) with Microsoft SMTP Server id 14.1.225.22; Wed, 6 Nov 2013 16:40:54 +0000
Received: from mail80-db8 (localhost [127.0.0.1])	by mail80-db8-R.bigfish.com (Postfix) with ESMTP id ABD41D60303; Wed,  6 Nov 2013 16:40:54 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:66.129.224.52; KIP:(null); UIP:(null); IPV:NLI; H:P-EMF01-SAC.jnpr.net; RD:none; EFVD:NLI
X-SpamScore: -20
X-BigFish: VPS-20(zzdb82h98dI4015I1447Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6h1082kzz1de098h1033IL17326ah8275bh8275dh1de097h186068hz2fh2a8h839h944hd25hf0ah11b5h121eh1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h16a6h1758h18e1h1946h19b5h1ad9h1b0ah1b2fh224fh1fb3h1d0ch1d2eh1d3fh1de2h1dfeh1dffh1fe8h1ff5h2216h1155h)
Received-SPF: pass (mail80-db8: domain of juniper.net designates 66.129.224.52 as permitted sender) client-ip=66.129.224.52; envelope-from=lenny@juniper.net; helo=P-EMF01-SAC.jnpr.net ; SAC.jnpr.net ; 
Received: from mail80-db8 (localhost.localdomain [127.0.0.1]) by mail80-db8 (MessageSwitch) id 138375605213118_30494; Wed,  6 Nov 2013 16:40:52 +0000 (UTC)
Received: from DB8EHSMHS004.bigfish.com (unknown [10.174.8.227])	by mail80-db8.bigfish.com (Postfix) with ESMTP id F2930DA020B; Wed,  6 Nov 2013 16:40:51 +0000 (UTC)
Received: from P-EMF01-SAC.jnpr.net (66.129.224.52) by DB8EHSMHS004.bigfish.com (10.174.4.14) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 6 Nov 2013 16:40:50 +0000
Received: from merlot.juniper.net (172.17.27.10) by P-EMF01-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.146.0; Wed, 6 Nov 2013 08:40:48 -0800
Received: from eng-mail01.juniper.net (eng-mail01.juniper.net [172.17.28.114]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id rA6GftW55869; Wed, 6 Nov 2013 08:41:55 -0800 (PST)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id 7F2931144E;  Wed,  6 Nov 2013 08:40:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id 706AC1141B; Wed,  6 Nov 2013 08:40:47 -0800 (PST)
Date: Wed, 6 Nov 2013 08:40:47 -0800
From: Leonard Giuliano <lenny@juniper.net>
To: Toerless Eckert <eckert@cisco.com>
In-Reply-To: <20131104174051.GQ6467@cisco.com>
Message-ID: <20131106073718.C70099@eng-mail01.juniper.net>
References: <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> <20131101001433.GX6467@cisco.com> <20131104075423.N23002@eng-mail01.juniper.net> <20131104174051.GQ6467@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, 06 Nov 2013 16:41:01 -0000

Thanks Toerless.  

The problem is that this is a point solution with very narrow 
applicability.  If the goal is to make things simpler, my suggestion is to 
analyze the current problems with existing protocols and mechanisms, 
understand the requirements and use cases, and then start from the ground 
up to determine how best to solve this problem.  This documents jumps to 
one particular solution- perhaps extending BSR to behave like DM state 
refresh is the best way to do this, or perhaps there are better solutions 
if we put other things on the table.  Maybe in the end we have a new mode: 
PIM-Simple.

FWIW, I have come to believe the underlying assumption that there is a 
constant linear relationship between simplicity and mcast deployment 
likelyhood is not the case- experience and empirical evidence does not 
seem to support this assumption.  That is, the belief that if only we make 
things simple enough, folks will happily turn on mcast.  This has led us 
on a quixotic journey over the years, as various mechanisms have been 
tried with the goal of just making things a little simpler- SSM, IGMPv3 
lite, URD, state refresh, IGMP Proxy, PIM-Bidir, static IGMP joins, LW 
IGMPv3, AnycastRP with PIM, SSM mapping, Embedded RP, mLDP, etc.  Each of 
these, in some way, promised to make things a little simpler, with the 
assumption that widespread deployment was just around the corner if only 
we just made things a little easier.

In economics, there is a phenomenon known as the "Penny Gap", which says 
that the biggest hurdle for some services is not the question of making it 
cheap enough, but rather getting the someone to pay anything at all- to 
pay the first penny.  I have observed this same phenomenon in mcast.  No 
matter how simple you make the protocols/config, the biggest problem is 
getting someone to turn it on at all- to config the first line.  
Generally, the only reason someone turns on mcast is bc they are forced to 
do so for some reason.  And once they have to turn it on, the complexity 
question isn't much of a barrier.  We've seen this with MVPNs- the same 
folks who scoffed at Internet mcast for years and claimed it was too 
complex were more than willing to turn on a bunch of MVPN mechanisms that 
are exponentially more complex.

After all, the complexity of mcast doesn't lie in it's configuration, but 
rather it's understanding.  In most cases, mcast is "damn simple" to 
config and get up and running.  The problem is when it breaks- you have to 
understand how mcast actually works in order to tshoot it.  In that way, I 
would argue that just using BSR to flood source info is not that much 
simpler than having a RPs+MSDP+shared trees.  With this proposal, one 
still has to understand SPTs, pim joins/prunes, igmp reports, what BSR is 
and how it carries this new source info, new policy to restrict these new 
BSR messages from leaving your domain, new policy to capture the claimed 
benefits of not caching this source info on non-LHRs, etc.  At the end of 
the day, is all of this really any easier than picking 2 or 3 routers to 
be RPs and running MSDP between them (or with AnycastRP w PIM, no need for 
MSDP at all)?  Viewed in totality, the gains are marginal at best and are 
unlikely to get over any real hurdles.

I suspect this proposal will make mcast deployment no more enticing no 
matter how much anyone complains RPs and shared trees are too complex.

-Lenny

On Mon, 4 Nov 2013, Toerless Eckert wrote:

-) Thanks, Lenny.
-) 
-) The PIM-DMv2 thought experiment is a good idea.
-)   - i still would not have SSM forwarding and PIM-control-plane but
-)     something different. Duplication of operational knowledge requirements.
-)     (assuming of course i will also have PIM-SSM capable apps in the network!).
-)   - I very much assume i would still have even on intermediate
-)     hops daa-triggered events
-)   - Still wouldn't be able to solve the basic prune issues where PIM-DM
-)     is worse than DVMRP.
-)   - If i'd outgrow the scale limits of flooding i can't smoothly change
-)     the SA signaling model to something better without changing the
-)     underlying forwarding/PIM_signaling plane from DM to SM. 
-)   - I could not plug potentially different SA signaling mechanisms
-)     (eg: better than just flood) into the system.
-)   - Wouldn't create an incentive to get rid of bursty source apps
-) 
-) Is the incentive for this new idea great enough to make it happen ?
-) I think we should well investigate this. As i tried to elaborate in the
-) prior mail more, i think iv'e seen a lot of cases where really bad workarounds
-) where used to come close to this, and there are IMHO equally many
-) networks where multicast isn't deployed because PIM-SM/MSDP is too 
-) difficult and PIM-DM known to not be a problem of scale but reliability
-) due to rot of implementation/specs and above described limits of mechanisms.
-) 
-) Cheers
-)     Toerless
-) 
-) On Mon, Nov 04, 2013 at 08:46:16AM -0800, Leonard Giuliano wrote:
-) > 
-) > Toerless- thanks for the details and explanation.  
-) > 
-) > The big challenge for ASM multicast routing protocols is source discovery.  
-) > That is, if the receiver doesn't tell you who the source is, the network 
-) > needs to figure this out.  PIM-DM accomplished this with flooding so that 
-) > all routers in the domain become aware of the sources and can join using 
-) > an SPT.  It is really simple, however due to this flooding, it is not 
-) > scalable nor interdomain-friendly.  PIM-SM, on the other hand, uses RPs as 
-) > a meeting place to know all source info, then starts with shared trees 
-) > that may switch to SPTs.  PIM-SM is way more complex, but is far more 
-) > scalable and supportive of interdomain.
-) > 
-) > This proposal, like DM, simply reuses the flooding concept to distribute 
-) > source info throughout the domain.  By ignoring bursty source apps (which 
-) > is perfectly reasonable and defensible, IMO), it just floods this source 
-) > control traffic, rather than the actual data, which DM does at least 
-) > initially (DM state refresh can be used susequently to refresh state by 
-) > just reflooding the source control traffic, rather than data).  This 
-) > proposal does have to periodically reflood the source info to refresh 
-) > state, which is similiar to the DM state refresh.  Now, there is some 
-) > benefit with this proposal by not requiring all the non-LHRs to cache the 
-) > source messages (though, I can't seem to find this in the draft), but 
-) > given the limited use cases you have in mind, that's probabaly not much 
-) > gain.  So, comparing this proposal to DM: flooding of the data packets 
-) > initially is eliminated (but there still is control traffic flooding), it 
-) > is more of a flood-and-join model than a flood-and-prune model, and there 
-) > is some minor state reduction on some intermediate routers.  All said, 
-) > IMO, these are minimal, sublinear benefits over DM, but benefits 
-) > nonetheless.
-) > 
-) > Now, doing roughly the same thing in 2 different protocols is done all the 
-) > time, sometimes even for valid reasons ;)  Variety is, after all, the 
-) > spice of life.  However, alternatives are usually used when there is a 
-) > high demand for this mechanism.
-) > 
-) > In requesting adoption, the implicit question is if this is a problem 
-) > worth working on.  Some will say yes, some no, but in most cases it's 
-) > supposition and guesswork.  In this case, we have clear, unambiguous 
-) > evidence in the PIM-DM experience to guide us when it comes to using 
-) > flooding to distribute source info through a domain to eliminate the 
-) > complexity of SM.  And that experience with DM is not good.  The DM spec 
-) > was left for Experimental Limbo almost a decade ago.  Years before that, 
-) > state refresh, which IMO is about 75% of what this new proposal does, was 
-) > abandoned while still incomplete.  I don't recall seeing any proposals in 
-) > all the time since to do anything more to DM.  Is this complete lack of 
-) > interest in DM not a clear indicator?
-) > 
-) > Put another way, try the following thought experiment:  imagine someone 
-) > submitted a draft for PIM-DMv2.  It sought to fix the problems of DM, 
-) > eliminating data flooding for the initial flood, fixing state refresh for 
-) > the subsequent refloods, adding the option to not cache the state on the 
-) > non-LHRs, and moving towards explicit join.  Would there be enough support 
-) > to adopt that?  I for one would not support a PIM-DMv2 effort based on the 
-) > experiences of PIM-DMv1 and the fact that these improvements are marginal 
-) > and sublinear.  
-) > 
-) > IMO, this draft is essentially PIM-DMv2 by another name.
-) > 
-) > 
-) > On Thu, 31 Oct 2013, Toerless Eckert wrote:
-) > 
-) > -) 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
-) > -) 
-) 
-) -- 
-) ---
-) Toerless Eckert, eckert@cisco.com
-) Cisco NSSTG Systems & Technology Architecture
-) SDN: Let me play with the network, mommy!
-) 
-) 


From solofsso.ietf@gmail.com  Fri Nov 15 00:27:47 2013
Return-Path: <solofsso.ietf@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 AD42721F9A59 for <pim@ietfa.amsl.com>; Fri, 15 Nov 2013 00:27:47 -0800 (PST)
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=[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 bTW2+NHekJBP for <pim@ietfa.amsl.com>; Fri, 15 Nov 2013 00:27:47 -0800 (PST)
Received: from mail-pb0-x229.google.com (mail-pb0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 1A22A11E80DC for <pim@ietf.org>; Fri, 15 Nov 2013 00:27:47 -0800 (PST)
Received: by mail-pb0-f41.google.com with SMTP id jt11so3271858pbb.14 for <pim@ietf.org>; Fri, 15 Nov 2013 00:27:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:message-id:mime-version:subject:date:references :to:in-reply-to; bh=TlqgdDzQSDf7YPrg/zPg5dLl5Spx4kIk91HASVPl0Os=; b=EMuCg68CMpjBHFhT6LClfSJOa+nZ2Nw4bqn7MQ5PlVkDbhtnCKhttXheKqtULnP3Ct TRy60obLvJVrA9KkLVA3/8qBpwxTHWwxPmr2wgwbsf26ikM6HhhNliu7zCxFobE73u+6 h0RgTSMHwzNyKRuEV02AOF8j7OSK6JPvh2iPsyhEgv8V/p8mGqC2xTotO318UaR+hrTK gnLEGMscS4xP2ZneSa7ReYXshAmqX+DnZ0McVx22qQoPpioPprIKyjZf0LvdjhbRjtd7 +oBV5JQhDLuWJyFgWgGoc8Y0ZyCv9M3qtYNZiNjNY6s4e9YJw4NxGu15dHasb/ALVfTn 2MhQ==
X-Received: by 10.67.23.164 with SMTP id ib4mr5830005pad.42.1384504066820; Fri, 15 Nov 2013 00:27:46 -0800 (PST)
Received: from [172.17.134.102] (173-164-209-210-SFBA.hfc.comcastbusiness.net. [173.164.209.210]) by mx.google.com with ESMTPSA id bp5sm2833392pbb.18.2013.11.15.00.27.45 for <pim@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 15 Nov 2013 00:27:46 -0800 (PST)
From: Stefan Olofsson <solofsso.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_DD5BF86A-846D-4440-BA5F-77C014D6B32F"
Message-Id: <F6CCF9D3-A01B-4F1E-893A-017005DB8EC2@gmail.com>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Date: Fri, 15 Nov 2013 00:27:45 -0800
References: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com> <E75A5287-8588-4F87-8A11-1A3E5300599C@cisco.com>
To: pim@ietf.org
In-Reply-To: <E75A5287-8588-4F87-8A11-1A3E5300599C@cisco.com>
X-Mailer: Apple Mail (2.1510)
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, 15 Nov 2013 08:27:47 -0000

--Apple-Mail=_DD5BF86A-846D-4440-BA5F-77C014D6B32F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Support.

Rgds
/Stefan


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. =20
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.
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
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> stig: one issue with bidir is you don't have the optimal path.
> Hitoshi: flooding is not typically optimal.
> Ice: its only using mechanisms that exist today with bsr.
> Hitoshi: Why not use SAP (I'm not a fan of SAP though)? Whats the =
meaning of flooding. Use MSDP if interdomain?
> Ice; this is a case where you don't know the source. bsr based =
flooding. not inter domain discussion. Enterprise network.
>=20
>> Jeffrey: Of the 10k flows how many groups?
>> operator DT: I like the use case and support.
>> jeffrey: the amount of information is more with today.
>> lighthouse networks: you mentioned dns, why can't you use that?


--Apple-Mail=_DD5BF86A-846D-4440-BA5F-77C014D6B32F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>Support.</div><div><br></div><div>Rgds</div><div>/Stefan</div><div>=
<br></div><div><br></div><div>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.<br><font =
color=3D"#007316"><br></font><a =
href=3D"http://www.ietf.org/id/draft-wijnands-pim-source-discovery-bsr-03.=
txt">http://www.ietf.org/id/draft-wijnands-pim-source-discovery-bsr-03.txt=
</a><br><font color=3D"#007316"><br></font>thanks,<br>mike<br><font =
color=3D"#007316"><br></font>draft-wignands-pim-source-discovery-bsr-03 =
(Ice)<br>highly redudant mcast network without single point of failure. =
&nbsp;<br>Ice: the sources are what's relevant. 10k s,gs. Not =
introducing a new routing protocol.<br>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.<br>Mike: applaud any efforts to =
make multicast more simple. But flooding may be a problem.<br>1 room =
interested. 2 operators on draft interested. Mike will poll on =
list.<br><font =
color=3D"#007316"><br></font>_____________________________________________=
__<br>pim mailing list<br><a =
href=3D"mailto:pim@ietf.org">pim@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/pim">https://www.ietf.org/ma=
ilman/listinfo/pim</a><br><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><blockquote =
type=3D"cite"></blockquote>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<br>stig: one issue with bidir is you don't have the =
optimal path.<br>Hitoshi: flooding is not typically optimal.<br>Ice: its =
only using mechanisms that exist today with bsr.<br>Hitoshi: Why not use =
SAP (I'm not a fan of SAP though)? Whats the meaning of flooding. Use =
MSDP if interdomain?<br>Ice; this is a case where you don't know the =
source. bsr based flooding. not inter domain discussion. Enterprise =
network.<br><font color=3D"#007316" face=3D"monospace"><span =
style=3D"white-space: pre;"><br></span></font><blockquote =
type=3D"cite"><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Diso-8859-1"><div dir=3D"ltr"><pre>Jeffrey: Of the 10k flows =
how many groups?
operator DT: I like the use case and support.
jeffrey: the amount of information is more with today.
lighthouse networks: you mentioned dns, why can't you use that?
</pre></div></blockquote><blockquote =
type=3D"cite"></blockquote><blockquote =
type=3D"cite"></blockquote></div></div></blockquote></div><br></body></htm=
l>=

--Apple-Mail=_DD5BF86A-846D-4440-BA5F-77C014D6B32F--

From mmcbride7@gmail.com  Mon Nov 18 00:22:54 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 49A6011E816B for <pim@ietfa.amsl.com>; Mon, 18 Nov 2013 00:22:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.511
X-Spam-Level: 
X-Spam-Status: No, score=-0.511 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, 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 YvfRsFBQz82X for <pim@ietfa.amsl.com>; Mon, 18 Nov 2013 00:22:53 -0800 (PST)
Received: from mail-pb0-x234.google.com (mail-pb0-x234.google.com [IPv6:2607:f8b0:400e:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id B176B11E8149 for <pim@ietf.org>; Mon, 18 Nov 2013 00:22:53 -0800 (PST)
Received: by mail-pb0-f52.google.com with SMTP id wy17so5204483pbc.39 for <pim@ietf.org>; Mon, 18 Nov 2013 00:22:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=QZvA/BRxWpPFsD+Dk/WkJvuYXP0EziY7BtDsKRjaRLc=; b=gfSUFE2OoBSnjXTNUey85VC8309DAgWCk+oYWJozzJcNjRuJb07Xpu8l/20v3E6QCw v8gduYVaHrPW/bBU2dM7L8vy1ys/sBKi9cMz7hyjS/96YJlwwFCFlCU7g1nDsi+IWosr VWhdoIeupDi9qki5Ck09NlqyzgQoMrZJ+xUTeieGFhLe3m57O3Rq5NTCGA4+3EyPQ2rP wy4jhQyU+BAW1MFIuj0739jw7gZDcWeOdRFrGCyqk/+QO02MPGndkC3iLogxIM7fF/5m hpXQPvm0ghAONhrw6ffixIiaNueG0+7Ddeoek06HOrgFu1j7bljaSionuY6a2ppclGh6 zvNA==
MIME-Version: 1.0
X-Received: by 10.67.21.226 with SMTP id hn2mr20259510pad.69.1384762973328; Mon, 18 Nov 2013 00:22:53 -0800 (PST)
Received: by 10.68.20.69 with HTTP; Mon, 18 Nov 2013 00:22:53 -0800 (PST)
In-Reply-To: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com>
References: <CAL3FGfwjWs-uwxNK8cxQQq-9Fm6MMMFsJz1DwODCZwLrJ7VYDg@mail.gmail.com>
Date: Mon, 18 Nov 2013 00:22:53 -0800
Message-ID: <CAL3FGfxR-gViLMTiroJmuP9=rQ0pWa3eE4GZG9ypqyJKBb6zvw@mail.gmail.com>
From: Mike McBride <mmcbride7@gmail.com>
To: "pim@ietf.org" <pim@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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, 18 Nov 2013 08:22:54 -0000

This draft has received sufficient support to declare rough consensus
for adoption. We are now the proud (for most) owners of this draft.
Authors, please submit a new draft-pim version of this draft. Thank
you all for your opinions on this draft, both for and against.

It was good seeing many of you in Vancouver. After a couple of back to
back Friday slots, PIM will NOT be meeting on a Friday again for
awhile.

mike

On Fri, Oct 25, 2013 at 3:07 PM, Mike McBride <mmcbride7@gmail.com> 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-interes=
t 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 rou=
ting protocol.
> Jeffrey: Could use mospf. pim bidir is another viable approach. With bidi=
r, while the RPA canbe an address that is not tried to any router (the addr=
ess would be associated with a LAN), the LAN that the RPA is on could becom=
e partitioned. When that happens, traffic cannot be exchanged on the LAN be=
tween 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 meet=
ing. With that resolved, PIM bidir will be a better solution for the target=
ed 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 lis=
t.
>
>

From internet-drafts@ietf.org  Mon Nov 18 14:53:25 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 746AE1AE6F8; Mon, 18 Nov 2013 14:53:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NpzjZnfEARab; Mon, 18 Nov 2013 14:53:24 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F09091AE6F4; Mon, 18 Nov 2013 14:53:23 -0800 (PST)
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.83.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131118225323.22016.54242.idtracker@ietfa.amsl.com>
Date: Mon, 18 Nov 2013 14:53:23 -0800
Cc: pim@ietf.org
Subject: [pim] I-D Action: draft-ietf-pim-source-discovery-bsr-00.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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, 18 Nov 2013 22:53:25 -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           : PIM flooding mechanism and source discovery
	Author(s)       : IJsbrand Wijnands
                          Stig Venaas
                          Michael Brig
	Filename        : draft-ietf-pim-source-discovery-bsr-00.txt
	Pages           : 10
	Date            : 2013-11-18

Abstract:
   PIM Sparse-Mode uses a Rendezvous Point (RP) and shared trees to
   forward multicast packets to Last Hop Routers (LHR).  After the first
   packet is received by the LHR, the source of the multicast stream is
   learned and the Shortest Path Tree (SPT) can be joined.  This draft
   proposes a solution to support PIM Sparse Mode (SM) without the need
   for PIM registers, RPs or shared trees.  Multicast source information
   is flooded throughout the multicast domain using a new generic PIM
   flooding mechanism.  This mechanism is defined in this document, and
   is modeled after the PIM Bootstrap Router protocol.  By removing the
   need for RPs and shared trees, the PIM-SM procedures are simplified,
   improving router operations, management and making the protocol more
   robust.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-pim-source-discovery-bsr-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/

