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

Jon Zeeff <jzeeff@internet2.edu> Tue, 10 June 2003 13:09 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 JAA27464 for <ssm-archive@lists.ietf.org>; Tue, 10 Jun 2003 09:09:22 -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 h5AD7vB20042; Tue, 10 Jun 2003 09:07:57 -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 h5AD55B19004 for <ssm@optimus.ietf.org>; Tue, 10 Jun 2003 09:05:05 -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 JAA27228 for <ssm@ietf.org>; Tue, 10 Jun 2003 09:05:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19PimB-0005YH-00 for ssm@ietf.org; Tue, 10 Jun 2003 09:02:59 -0400
Received: from basie.internet2.edu ([207.75.164.22]) by ietf-mx with esmtp (Exim 4.12) id 19PimA-0005YD-00 for ssm@ietf.org; Tue, 10 Jun 2003 09:02:58 -0400
Received: from localhost (localhost.localdomain [127.0.0.1]) by basie.internet2.edu (Postfix) with ESMTP id 209F47B4A0; Tue, 10 Jun 2003 09:05:00 -0400 (EDT)
Received: from magic.internet2.edu (aa106.internet2.edu [207.75.164.106]) by basie.internet2.edu (Postfix) with ESMTP id 16F1D7B4B3; Tue, 10 Jun 2003 09:04:59 -0400 (EDT)
Message-Id: <5.1.0.14.2.20030610085539.023c1740@mail.internet2.edu>
X-Sender: jzeeff@mail.internet2.edu
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 10 Jun 2003 09:04:52 -0400
To: Toerless Eckert <eckert@cisco.com>
From: Jon Zeeff <jzeeff@internet2.edu>
Subject: Re: [ssm] Document Action: An Overview of Source-Specific Multicast(SSM) Deployment to Informational
Cc: Bill Fenner <fenner@research.att.com>, ssm@ietf.org
In-Reply-To: <20030606201936.GI16697@cypher.cisco.com>
References: <5.1.0.14.2.20030606144813.01d03370@mail.internet2.edu> <200306040550.h545oaD08547@windsor.research.att.com> <5.1.0.14.2.20030606144813.01d03370@mail.internet2.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Virus-Scanned: by AMaViS 0.3.12pre8
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>


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

>So, as far as easy gradual migration to SSM with DoS attack prevention is 
>concerned,
>this has almost completely been ignored by the IETF process.

I see similar lack of concern about real world security in wireless routing 
protocols (and DHCP and IPv6 and PIM and ...).

Thanks for the info.

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