[ssm] building multi-sender apps with ssm
Hugh Holbrook <holbrook@cisco.com> Fri, 17 January 2003 18:22 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 NAA00852 for <ssm-archive@lists.ietf.org>; Fri, 17 Jan 2003 13:22:04 -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 h0HIbLJ20794; Fri, 17 Jan 2003 13:37:21 -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 h0HISsJ19914 for <ssm@optimus.ietf.org>; Fri, 17 Jan 2003 13:28:54 -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 NAA00528 for <ssm@ietf.org>; Fri, 17 Jan 2003 13:12:41 -0500 (EST)
Received: from holbrook-laptop.cisco.com (sjc-vpn2-304.cisco.com [10.21.113.48]) by sj-msg-core-4.cisco.com (8.12.2/8.12.6) with ESMTP id h0HIC50E020826; Fri, 17 Jan 2003 10:12:09 -0800 (PST)
Received: by holbrook-laptop.cisco.com (Postfix, from userid 500) id 96D1710B7A7; Fri, 17 Jan 2003 13:09:43 -0500 (EST)
From: Hugh Holbrook <holbrook@cisco.com>
To: holbrook@dsg.stanford.edu
Cc: Pavlin Radoslavov <pavlin@icir.org>, holbrook@cisco.com, Michael Luby <luby@digitalfountain.com>, Pavlin Radoslavov <pavlin@icir.org>, ssm@ietf.org
In-reply-to: <20030117065557.67CD010B7A7@holbrook-laptop.cisco.com>
Reply-To: holbrook@cisco.com
Message-Id: <20030117180943.96D1710B7A7@holbrook-laptop.cisco.com>
Date: Fri, 17 Jan 2003 13:09:43 -0500
Subject: [ssm] building multi-sender apps with ssm
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>
[Was Re: Re: Re: [ssm] Re: last call comments on ssm-arch doc ] Hopefully these are the last tweaks. Hitoshi pointed out that this sentence of what I wrote > SSM is particularly well-suited to dissemination-style applications > with a single sender. can be interpreted to mean that SSM isn't well-suited to applications with more than one sender. I think he is right and furthermore, I realized that I'm missing a fundamental aspect in this paragraph: The key attribute of an SSM-based application that introduces the need for application-layer rendezvous is not the fact that there are multiple senders but the fact that the senders are not all known in advance, so I ought to say that. Furthermore, my example application of a backup data source is more in the category one of an application with two sources that are known in advance, so I moved it to follow the text that describes that application model. So... this is hopefully my last try on this paragraph. SSM is particularly well-suited to dissemination-style applications with one or more senders whose identities are known before the application begins. For instance, a data dissemination application that desires to provide a secondary data source in case the primary source fails over might implement this by using one channel for each source and advertising both of them to receivers. It can be used to build multi-source applications where all participants' identities are not known in advance, but the multi-source "rendezvous" functionality does not occur in the network layer. Just like in an application that uses unicast as the underlying transport, this functionality can be implemented by the application or by an application-layer library. Peer-to-peer multicast resource discovery of the form in which a client sends a multicast query directly to a "service location group" to which servers listen is not directly supported by SSM -Hugh _______________________________________________ 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