Re: [magma] Comments draft-ietf-magma-snoop-11.txt (SSM)

Toerless Eckert <eckert@cisco.com> Tue, 18 May 2004 21:01 UTC

Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18051 for <magma-archive@ietf.org>; Tue, 18 May 2004 17:01:05 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQBhy-0003dm-0r for magma-archive@ietf.org; Tue, 18 May 2004 17:01:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQBgz-0003aO-00 for magma-archive@ietf.org; Tue, 18 May 2004 17:00:05 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQBgN-0003Yi-00; Tue, 18 May 2004 16:59:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQBOm-0007kC-TX; Tue, 18 May 2004 16:41:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQAfC-00088o-DV for magma@optimus.ietf.org; Tue, 18 May 2004 15:54:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10427 for <magma@ietf.org>; Tue, 18 May 2004 15:54:08 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQAfA-0002gZ-Sy for magma@ietf.org; Tue, 18 May 2004 15:54:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQAeD-0002eI-00 for magma@ietf.org; Tue, 18 May 2004 15:53:10 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1BQAdU-0002Zx-00 for magma@ietf.org; Tue, 18 May 2004 15:52:25 -0400
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 18 May 2004 11:59:13 +0000
Received: from irp-view8.cisco.com (irp-view8.cisco.com [171.70.65.145]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i4IJpmC9018210; Tue, 18 May 2004 12:51:52 -0700 (PDT)
Received: (eckert@localhost) by irp-view8.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id RAA13568; Mon, 17 May 2004 17:17:47 -0700 (PDT)
Date: Mon, 17 May 2004 17:17:47 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Pekka Savola <pekkas@netcore.fi>
Cc: Isidor Kouvelas <kouvelas@cisco.com>, magma@ietf.org
Subject: Re: [magma] Comments draft-ietf-magma-snoop-11.txt (SSM)
Message-ID: <20040517171747.A5348@cisco.com>
References: <200405171952.MAA12458@cypher.cisco.com> <Pine.LNX.4.44.0405180025420.9689-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Pine.LNX.4.44.0405180025420.9689-100000@netcore.fi>; from pekkas@netcore.fi on Tue, May 18, 2004 at 12:27:03AM +0300
Sender: magma-admin@ietf.org
Errors-To: magma-admin@ietf.org
X-BeenThere: magma@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/magma>, <mailto:magma-request@ietf.org?subject=unsubscribe>
List-Id: Multicast and Anycast Group Membership <magma.ietf.org>
List-Post: <mailto:magma@ietf.org>
List-Help: <mailto:magma-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/magma>, <mailto:magma-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.6 required=5.0 tests=DATE_IN_PAST_06_12 autolearn=no version=2.60

On Tue, May 18, 2004 at 12:27:03AM +0300, Pekka Savola wrote:
> On Mon, 17 May 2004, Isidor Kouvelas wrote:
> > Excuse me but were you hybernating during the last call etc for this
> > draft? This is currently in the RFC editor queue!
> 
> Further, I think there was considerable pushback for configured SSM 
> ranges in IETF59 when we had this debate.

I don't remember that. I also know that our customers explicitly asked
us to have the SSM range configurable. But be that as it may. I don't think
we have arrived at the conclusion that there MUST only be SSM on the
default range, and providing automatic support for SSM on any range with
IGMP snooping is easy enough to do, so i don't thnk we need to gate a
decision on what to recommend for IGMP snooping by whatever discussion
we have over further down the road recommendations for scoped SSM 
address range support.

> If folks think that's important, it should be easily to specify as a 
> separate draft to the new mrdisc.  Then we'd see who would bother 
> implementing it :)

I wonder how many folks here have actively been involved in deployment
discussions for larger SSM solutions. I don't think that the active magma
working group participation should be so bold to exclude well working
approaches for scoping SSM purely based on their own perceptions. IGMP snooping
is currently the one most needed functionality in support of SSM and excluding
an already deployed and working solution to support this pending on the
adoption of a not yet deployed scoping approach doesn't sound like a logical
approach. And pushing the solution back to other protocols to be defined
and implemented first is likewise bogus.

Cheers
	Toerless

_______________________________________________
magma mailing list
magma@ietf.org
https://www1.ietf.org/mailman/listinfo/magma