IETF Logo Mail Archive

Re: [ssm] Who uses SSM?

Marshall Eubanks <marshall.eubanks@gmail.com> Wed, 17 November 2004 14:34 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03107 for <ssm-archive@lists.ietf.org>; Wed, 17 Nov 2004 09:34:54 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUQo7-0002rX-6a; Wed, 17 Nov 2004 09:29:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUQn3-0002bw-2V for ssm@megatron.ietf.org; Wed, 17 Nov 2004 09:28:09 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02647 for <ssm@ietf.org>; Wed, 17 Nov 2004 09:28:07 -0500 (EST)
Received: from rproxy.gmail.com ([64.233.170.203]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUQpS-0002CO-O7 for ssm@ietf.org; Wed, 17 Nov 2004 09:30:39 -0500
Received: by rproxy.gmail.com with SMTP id a36so886916rnf for <ssm@ietf.org>; Wed, 17 Nov 2004 06:28:06 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=BWayfUgur1WKR8j7TFZefNuch7UNB+hclbsl3Mo+Z3OYChBw2lzBgDOE/CRreaF61ZiEOZ5XEuufSgqzdRoRC81Mmv+9fY0COLYgL3UXk+2EaL/LYCQ2X+YlIcVvk5PTdqWzc3vuUzj74wiM9VSPkpPbWhyYTj88jSqBb+vBFjg=
Received: by 10.38.82.27 with SMTP id f27mr461815rnb; Wed, 17 Nov 2004 06:28:06 -0800 (PST)
Received: by 10.38.66.53 with HTTP; Wed, 17 Nov 2004 06:28:06 -0800 (PST)
Message-ID: <dcad22d804111706285b968aa0@mail.gmail.com>
Date: Wed, 17 Nov 2004 09:28:06 -0500
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Marc Barisch <mbarisch@gmx.net>
Subject: Re: [ssm] Who uses SSM?
In-Reply-To: <22794.1100698216@www62.gmx.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
References: <22794.1100698216@www62.gmx.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit
Cc: ssm@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Marshall Eubanks <marshall.eubanks@gmail.com>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>, <mailto:ssm-request@ietf.org?subject=unsubscribe>
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>
Sender: ssm-bounces@ietf.org
Errors-To: ssm-bounces@ietf.org
Content-Transfer-Encoding: 7bit

As far as I know, the users of SSM are a set of measure zero.

However, from time to time there are tests.

Compare
http://netflow.internet2.edu/weekly/longit/ssm-octets.png
with 
http://netflow.internet2.edu/weekly/longit/multicast-octets.png

Pay attention to the scales on the Y axes.

I would love to hear of assertions that disprove the above.

Regards
Marshall Eubanks


On Wed, 17 Nov 2004 14:30:16 +0100 (MET), Marc Barisch <mbarisch@gmx.net> wrote:
> Hi
> 
> I have read about the advantages of PIM-SSM over PIM-SM from a technical
> point of view.
> For a seminar paper at my university, I would like to provide some figures
> concerning the deployment of the different PIM modes, especially regarding
> TV broadcast over packet networks.
> 
> Does anybody know of providers using PIM-SSM or are using all PIM-SM?
> Are there any commercial deployments regarding PIM-SSM and IPv6.
> 
> Thanks in advance
> 
> Marc
> 
> --
> Geschenkt: 3 Monate GMX ProMail + 3 Top-Spielfilme auf DVD
> ++ Jetzt kostenlos testen http://www.gmx.net/de/go/mail ++
> 
> _______________________________________________
> ssm mailing list
> ssm@ietf.org
> https://www1.ietf.org/mailman/listinfo/ssm
>

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

v2.45.0 | Report a Bug | By Email | System Status