Re: [ssm] Re: last call comments on ssm-arch doc
Daniel Zappala <zappala@cs.uoregon.edu> Thu, 16 January 2003 06:17 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 BAA22457 for <ssm-archive@lists.ietf.org>; Thu, 16 Jan 2003 01:17:57 -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 h0G6WRJ13934; Thu, 16 Jan 2003 01:32:27 -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 h0G6PmJ13685 for <ssm@optimus.ietf.org>; Thu, 16 Jan 2003 01:25:48 -0500
Received: from falcon.continet.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22339 for <ssm@ietf.org>; Thu, 16 Jan 2003 01:10:20 -0500 (EST)
Received: from [192.168.254.17] ([206.58.103.26]) by falcon.continet.com (Post.Office MTA v3.5.3 release 223 ID# 0-60955U4500L350S0V35) with ESMTP id com for <ssm@ietf.org>; Wed, 15 Jan 2003 22:32:11 -0800
Subject: Re: [ssm] Re: last call comments on ssm-arch doc
From: Daniel Zappala <zappala@cs.uoregon.edu>
To: ssm@ietf.org
In-Reply-To: <20030115155041.GF2103@cypher.cisco.com>
References: <20030115150558.GD2103@cypher.cisco.com> <NDBBLPHLPKFAHIKICCDPKEFKCMAA.Rolland.Vida@lip6.fr> <20030115155041.GF2103@cypher.cisco.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6)
Date: Wed, 15 Jan 2003 22:13:25 -0800
Message-Id: <1042697605.2622.44.camel@localhost>
Mime-Version: 1.0
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
On Wed, 2003-01-15 at 07:50, Toerless Eckert wrote: > On Wed, Jan 15, 2003 at 04:38:01PM +0100, Rolland Vida wrote: > > Toerless, > > > > > If you're building the white board application as pure peer to peer, > > > each peer has to become a SSM channel source. If you implement the > > > application as a client/server system, the clients could unicast to > > > the server, and the server would have one SSM channel to all clients. > > > Advantages: Easier model for access control, session management > > > and ressource allocation then in a full peer to peer model. > > > > This is a nice trick to provide a multi-source service through SSM. However, > > there are also some drawbacks: no source filtering, no shortest path > > delivery. It is basicly like standard PIM-SM: everybody sends to the RP > > (server), which forwards then on the shared tree (here the SSM channel). And > > as in PIM-SM already the shared tree is switched for a source-specific tree > > (to optimize delivery), why should it be now acceptable to use such a shared > > tree just to enable multi-source SSM? > > 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. And security > of the applications data flow is now completely under the control of > the application. Well put. I'd also like to add that you can get around the delay penalty (because shortest paths are no longer used if all data is relayed through a single source). You just use the primary source (the application-level relay) to bootstrap other relays. See: D. Zappala, and A. Fabbri, Using SSM Proxies to Provide Efficient Multiple-Source Multicast Delivery. IEEE Globecom, Sixth Global Internet Symposium, November, 2001. at http://www.cs.uoregon.edu/~zappala/uo/uo.publications.html or http://www.nrg.cs.uoregon.edu/pubs/ssm_gis01.pdf -- ====================================================================== Daniel Zappala Computer Science Assistant Professor University of Oregon _______________________________________________ ssm mailing list ssm@ietf.org https://www1.ietf.org/mailman/listinfo/ssm
- [ssm] Re: last call comments on ssm-arch doc Hugh Holbrook
- Re: [ssm] Re: last call comments on ssm-arch doc Hitoshi Asaeda
- RE: [ssm] Re: last call comments on ssm-arch doc Rolland Vida
- Re: [ssm] Re: last call comments on ssm-arch doc Hitoshi Asaeda
- Re: [ssm] Re: last call comments on ssm-arch doc Toerless Eckert
- RE: [ssm] Re: last call comments on ssm-arch doc Rolland Vida
- Re: [ssm] Re: last call comments on ssm-arch doc Toerless Eckert
- RE: [ssm] Re: last call comments on ssm-arch doc Rolland Vida
- Re: [ssm] Re: last call comments on ssm-arch doc Toerless Eckert
- Re: [ssm] Re: last call comments on ssm-arch doc Pavlin Radoslavov
- RE: [ssm] Re: last call comments on ssm-arch doc Michael Luby
- Re: [ssm] Re: last call comments on ssm-arch doc Daniel Zappala
- Re: RE: [ssm] Re: last call comments on ssm-arch … Hugh Holbrook
- Re: Re: [ssm] Re: last call comments on ssm-arch … Hugh Holbrook
- Re: [ssm] Re: last call comments on ssm-arch doc Pavlin Radoslavov
- Re: Re: [ssm] Re: last call comments on ssm-arch … Hugh Holbrook
- [ssm] building multi-sender apps with ssm Hugh Holbrook
- Re: [ssm] building multi-sender apps with ssm Pavlin Radoslavov
- Re: Re: [ssm] building multi-sender apps with ssm Hugh Holbrook