Re: [ssm] Re: last call comments on ssm-arch doc

Toerless Eckert <eckert@cisco.com> Wed, 15 January 2003 17:11 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 MAA03686 for <ssm-archive@lists.ietf.org>; Wed, 15 Jan 2003 12:11:46 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FHQGJ27125; Wed, 15 Jan 2003 12:26:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FHCoJ26499 for <ssm@optimus.ietf.org>; Wed, 15 Jan 2003 12:12:50 -0500
Received: from sj-msg-core-4.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03175 for <ssm@ietf.org>; Wed, 15 Jan 2003 11:57:37 -0500 (EST)
Received: from cisco.com (cypher.cisco.com [171.69.11.143]) by sj-msg-core-4.cisco.com (8.12.2/8.12.6) with ESMTP id h0FH0v0E017137; Wed, 15 Jan 2003 09:00:57 -0800 (PST)
Received: (from eckert@localhost) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id JAA18658; Wed, 15 Jan 2003 09:00:56 -0800 (PST)
Date: Wed, 15 Jan 2003 09:00:56 -0800
From: Toerless Eckert <eckert@cisco.com>
To: Rolland Vida <Rolland.Vida@lip6.fr>
Cc: Toerless Eckert <eckert@cisco.com>, ssm@ietf.org
Subject: Re: [ssm] Re: last call comments on ssm-arch doc
Message-ID: <20030115170056.GJ2103@cypher.cisco.com>
References: <20030115155041.GF2103@cypher.cisco.com> <NDBBLPHLPKFAHIKICCDPCEFMCMAA.Rolland.Vida@lip6.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <NDBBLPHLPKFAHIKICCDPCEFMCMAA.Rolland.Vida@lip6.fr>
User-Agent: Mutt/1.4i
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>

On Wed, Jan 15, 2003 at 05:08:46PM +0100, Rolland Vida wrote:
> > Because in SSM the reflection is done at application level, so the
> > reflecting server can do a lot of useful stuff like source filtering
> > (access control), (re-)encoding/fec, (re-)encryption, filtering,
> > synchronization, buffering, shaping, adding coffee.
> 
> It depends on the application. For some, I agree that this model can be
> useful. for a small size videoconference for example, you could mix all the
> voice flows together at the server, and send out only one voice stream on
> the SSM channel (for the video it's more complicated...)
> 
> But in any case, I see it as a way to use SSM for doing something that is
> quite different from what SSM was originaly meant for.

I think that that opinion requires a narrow minded expectation on what
SSM was meant for ;-))

> One basic feature of
> SSM is source filtering. In your model the server can only filter out
> malicious sources for example. But if two different receivers want to listen
> to two different "legal" sources, and do not want to listen to nobody else,
> your server can never support that on the same SSM channel.

Not true. If you ONLY want to have a server for reasons of securities et. al.,
then you can still have this server reflect each sources traffic on an
individual channel. You don't save SSM channels, but this can help you
hide the IP addresses of the sources for example for scurity reasons.

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