Re: [MBONED] Mail regarding draft-tissa-pim-mcastoam

"Tissa Senevirathne (tsenevir)" <tsenevir@cisco.com> Wed, 21 March 2012 16:00 UTC

Return-Path: <tsenevir@cisco.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 676CF21F85E5 for <mboned@ietfa.amsl.com>; Wed, 21 Mar 2012 09:00:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.481
X-Spam-Level:
X-Spam-Status: No, score=-8.481 tagged_above=-999 required=5 tests=[AWL=2.118, 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 4a4fxMe6BlSt for <mboned@ietfa.amsl.com>; Wed, 21 Mar 2012 09:00:44 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 1306821F8697 for <mboned@ietf.org>; Wed, 21 Mar 2012 09:00:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=tsenevir@cisco.com; l=2382; q=dns/txt; s=iport; t=1332345642; x=1333555242; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=F/SBIvt6X9yT9NAuoPdGUgeNtFhbl1Z09Ne7eIaG8pY=; b=G7rPKwFvu8zycj2q6LLwYc9o9FRP7jmc1h+0nIdtG/5X+B6fbOYHZS6w bE+wrnuV/k3kgPER76ILeQJYyIfOBtt+yLMNIQ/H6uYIJ86tjuhFJjAuh HOnSlcLLsf+XLhbgule38A/jrkFKiIQkHrw0J9o1gSBHXboNdkfLQDCJK 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAKv6aU+rRDoG/2dsb2JhbABEtn2BB4IJAQEBBBIBHQo/DAQCAQgOAwQBAQsGFwEGAUUJCAEBBAESCBMHh2cBmQefEIphhT1jBIhWm0iBaIMHgTQFAw
X-IronPort-AV: E=Sophos;i="4.73,623,1325462400"; d="scan'208";a="34497722"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-3.cisco.com with ESMTP; 21 Mar 2012 16:00:39 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id q2LG0dL8023897; Wed, 21 Mar 2012 16:00:39 GMT
Received: from xmb-sjc-214.amer.cisco.com ([171.70.151.145]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 21 Mar 2012 09:00:39 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 21 Mar 2012 09:00:37 -0700
Message-ID: <344037D7CFEFE84E97E9CC1F56C5F4A5D0FCD8@xmb-sjc-214.amer.cisco.com>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D768806F55@EMBX01-WF.jnpr.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Mail regarding draft-tissa-pim-mcastoam
Thread-Index: Ac0GG/Iw6vtXBbrBTxGWarf6ZPOOwwAKaTBQABgLJlAAGOsz8AAD5oGwABgzKmA=
References: <13205C286662DE4387D9AF3AC30EF456D768745564@EMBX01-WF.jnpr.net> <344037D7CFEFE84E97E9CC1F56C5F4A5C80039@xmb-sjc-214.amer.cisco.com> <13205C286662DE4387D9AF3AC30EF456D768745B27@EMBX01-WF.jnpr.net> <344037D7CFEFE84E97E9CC1F56C5F4A5D0FBE7@xmb-sjc-214.amer.cisco.com> <13205C286662DE4387D9AF3AC30EF456D768806F55@EMBX01-WF.jnpr.net>
From: "Tissa Senevirathne (tsenevir)" <tsenevir@cisco.com>
To: Ronald Bonica <rbonica@juniper.net>, draft-tissa-pim-mcastoam@tools.ietf.org, mboned@ietf.org
X-OriginalArrivalTime: 21 Mar 2012 16:00:39.0009 (UTC) FILETIME=[C28E4D10:01CD077B]
Cc: "Raghava Sivaramu (raghavas)" <raghavas@cisco.com>
Subject: Re: [MBONED] Mail regarding draft-tissa-pim-mcastoam
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2012 16:00:46 -0000

Hi Ron

Rate limiting as proposed is only needed in the interim until
implementations include propose extensions. Secondly, these extensions
can be utilized to discover various roles performed by routers in
multicast forwarding, which RFC 6450 cannot do.

With RFC 6450 every end stations has to run the required servers and
need to have the clients. Routers would not be able to perform such a
thing and operators always have to log in to end devices, consider the
operational nightmare. Additionally, as pointed out earlier, sometimes
it is not even administratively possible. In short with RFC 6450, you
are leaving customers to troubleshoot their own problems.

Like I pointed out earlier, we needed to look forward, so some point to
the future we will have the required tools in place if we take right
steps today. If we do agree the problem space is important then we can
discuss during the WG what best approaches we can take.

Thanks
Tissa

-----Original Message-----
From: Ronald Bonica [mailto:rbonica@juniper.net] 
Sent: Tuesday, March 20, 2012 9:54 PM
To: Tissa Senevirathne (tsenevir);
draft-tissa-pim-mcastoam@tools.ietf.org; mboned@ietf.org
Subject: RE: Mail regarding draft-tissa-pim-mcastoam

Tissa,

Having thought about your draft a while longer, I think that I can do a
better job of articulating my objection. That is, that the tool
described in 6450 is better suited to the problem at hand. 

Operators need a tool like this when a customer calls in wanting to know
why he can't receive a multicast stream. In this case, it makes sense
for the customer to initiate a test between himself and the server. It
makes less sense for the server to blast something out to all of its
clients hoping to elicit only a manageable number of responses.

One drawback of the solution described in RFC 6450 is that it requires
clients and servers to be deployed on end systems. On the other hand,
draft-tissa requires protocol changes on senders, receivers and
intermediate routers. That seems to be a wash.

Furthermore, 6450 is fairly robust. Draft-tissa performance is subject
to filters and rate limits that are imposed upon ICMP and optioned IP
packets.

                                            Ron

BTW, In this email and in all previous messages on this thread, I am
speaking as an individual contributor.