Re: [Omcast] Microsoft ConferenceXP

Mark Pullen <> Thu, 29 September 2005 01:52 UTC

Received: from localhost.localdomain ([] by with esmtp (Exim 4.32) id 1EKnbG-0002QJ-Vj; Wed, 28 Sep 2005 21:52:42 -0400
Received: from ([] by with esmtp (Exim 4.32) id 1EKnbF-0002QA-Th for; Wed, 28 Sep 2005 21:52:41 -0400
Received: from (ietf-mx []) by (8.9.1a/8.9.1a) with ESMTP id VAA27622 for <>; Wed, 28 Sep 2005 21:52:40 -0400 (EDT)
Received: from [] ( by with esmtp (Exim 4.43) id 1EKnip-0002SK-1v for; Wed, 28 Sep 2005 22:00:31 -0400
Received: from (localhost []) by (8.12.10+Sun/8.12.9) with ESMTP id j8T1qPbY018080; Wed, 28 Sep 2005 21:52:25 -0400 (EDT)
Received: from localhost (mpullen@localhost) by (8.12.10+Sun/8.12.8/Submit) with ESMTP id j8T1qONp018077; Wed, 28 Sep 2005 21:52:24 -0400 (EDT)
Date: Wed, 28 Sep 2005 21:52:24 -0400
From: Mark Pullen <>
To: Marshall Eubanks <>
Subject: Re: [Omcast] Microsoft ConferenceXP
In-Reply-To: <>
Message-ID: <>
References: <>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: pre-BOF overlay multicast discussions <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>

On Wed, 28 Sep 2005, Marshall Eubanks wrote:

> Is ConferenceXP related to the OMCast goals ?
> ConferenceXP employs a peer-to-peer architecture. Because no server is involved, this architecture
> makes deployment easy, and it prevents network traffic bottlenecks and single points of failure.
> This architecture uses multicast to ensure efficiency and scaling for multipoint video conferencing
> over a broadband network, as well as for sharing documents and ink over a 802.11b wireless network.
> It also supports point-to-point unicast for environments where multicast is unavailable.
Yes, I would say this is related to OMcast goals. I would prefer that
the interface to the application be an open one - ours is plain
IP multicast, which is about as open as you can get. Although the
ConferenceXP interface is an API that looks to be proprietary from
what I see on the webpage, they must have a group communications
service lower in their architecture and they might be interested
in defining a common standard. In any event I believe it would be
a bad idea to rule out the possibility before learning what interests
they may have.

> There is also
> Inter-Partition Networking for Overlay Multicast
> Sauleh Eetemadi
> Michigan State University

As I read the abstract, this is an analytical treatment of an important
part of the problem that we have been working on at GMU. Because we are
experimentalists, we have implemented a working prototype and have people
interested in using it; but this thesis appears to be an important
contribution to the theoretical basis of routing in overlay networks. So
yes it definitely fits and thats for pointing it out.


Omcast mailing list