Re: [ssm] Document Action: An Overview of Source-Specific Multicast(SSM) Deployment to Informational

Hitoshi Asaeda <Hitoshi.Asaeda@sophia.inria.fr> Tue, 10 June 2003 14:05 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00896 for <ssm-archive@lists.ietf.org>; Tue, 10 Jun 2003 10:05:34 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5AE4TB24190; Tue, 10 Jun 2003 10:04:29 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5AE0IB24023 for <ssm@optimus.ietf.org>; Tue, 10 Jun 2003 10:00:18 -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 KAA00448 for <ssm@ietf.org>; Tue, 10 Jun 2003 10:00:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Pjdb-0006Vc-00 for ssm@ietf.org; Tue, 10 Jun 2003 09:58:11 -0400
Received: from sophia.inria.fr ([138.96.64.20]) by ietf-mx with esmtp (Exim 4.12) id 19PjdZ-0006VO-00 for ssm@ietf.org; Tue, 10 Jun 2003 09:58:10 -0400
Received: from localhost (odie.inria.fr [138.96.88.52]) by sophia.inria.fr (8.12.8/8.12.5) with ESMTP id h5ADxXvK026856; Tue, 10 Jun 2003 15:59:33 +0200
Date: Tue, 10 Jun 2003 15:59:31 +0200
Message-Id: <20030610.155931.117536967.Hitoshi.Asaeda@sophia.inria.fr>
To: jzeeff@internet2.edu
Cc: eckert@cisco.com, fenner@research.att.com, ssm@ietf.org
Subject: Re: [ssm] Document Action: An Overview of Source-Specific Multicast(SSM) Deployment to Informational
From: Hitoshi Asaeda <Hitoshi.Asaeda@sophia.inria.fr>
In-Reply-To: <5.1.0.14.2.20030610085539.023c1740@mail.internet2.edu>
References: <5.1.0.14.2.20030606144813.01d03370@mail.internet2.edu> <20030606201936.GI16697@cypher.cisco.com> <5.1.0.14.2.20030610085539.023c1740@mail.internet2.edu>
X-Mailer: Mew version 2.2rc1 on Emacs 21.1 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>, <mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>, <mailto:ssm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

> > From my experience, windows XP does send IGMPv2 reports if it sees IGMPv2 
> > queries.
> >It MUST do this according to the IGMPv3 spec.
> 
> So if I do manage to get my LAN completely IGMPv3 capable and thus allow 
> the use of SSM, all it takes is one person
> plugging in a machine running IGMPv2 and SSM breaks.  This probably means 
> that SSM is unimplementable except
> in some special cases (example: one host per vlan).

In fact, and unfortunately, you are right.
There was some lack of important statements in IGMPv3.

One is a following sentence:
	"the Querier continues to send IGMPv3 queries, regardless of
	 its Multicast Address Compatibility Mode."
This should be included in the RFC. But it was too late. Actually,
since we've found the problem before the MLDv2's last-call, it is
included in Sect.8.3.2 of draft-vida-mld-v2-07.txt, though.

Other is something related to "host compatibility mode" which I post
the problem in MAGMA ML.
<http://www1.ietf.org/mail-archive/working-groups/magma/current/msg00027.html>
But I heard this mail was also too late. Yes, it is also included in
MLDv2's I-D (Sect.10.1) as follows:
	"A forged Version 1 Query message will put MLDv2 listeners on
	 that link in MLDv1 Host Compatibility Mode.  This scenario
	 can be avoided by providing MLDv2 hosts with a configuration
	 option to ignore Version 1 messages completely."

FYI, my IGMPv3/MLDv2 implementations (incl. KAME) support them, anyway.
--
Hitoshi Asaeda

p.s. "IGMPv3 addendum" is the solution?
_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm