From omcast-bounces@ietf.org Tue Sep 27 12:27:38 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKIIs-00066S-LD; Tue, 27 Sep 2005 12:27:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EKIIr-00066H-8K
	for omcast@megatron.ietf.org; Tue, 27 Sep 2005 12:27:37 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24296
	for <omcast@ietf.org>; Tue, 27 Sep 2005 12:27:35 -0400 (EDT)
Received: from lennon.multicasttech.com
	([63.105.122.7] helo=multicasttech.com ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EKIQ9-0002VI-60
	for omcast@ietf.org; Tue, 27 Sep 2005 12:35:09 -0400
Received: from [68.100.84.146] (account <marshall_eubanks@multicasttech.com>)
	by multicasttech.com (CommuniGate Pro WebUser 3.4.8)
	with HTTP id 2993595 for <omcast@ietf.org>;
	Tue, 27 Sep 2005 12:27:33 -0400
From: "Marshall Eubanks" <tme@multicasttech.com>
To: omcast@ietf.org
X-Mailer: CommuniGate Pro Web Mailer v.3.4.8
Date: Tue, 27 Sep 2005 12:27:33 -0400
Message-ID: <web-2993595@multicasttech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Spam-Score: 2.8 (++)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 8bit
Subject: [Omcast] Hello to OMCast
X-BeenThere: omcast@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: pre-BOF overlay multicast discussions <omcast.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/omcast>,
	<mailto:omcast-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/omcast>
List-Post: <mailto:omcast@ietf.org>
List-Help: <mailto:omcast-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/omcast>,
	<mailto:omcast-request@ietf.org?subject=subscribe>
Sender: omcast-bounces@ietf.org
Errors-To: omcast-bounces@ietf.org

Hello;

RE: If you join, please send to the list a brief description
of why you're interested, to get discussion going. If
there are enough participants, we'll try for a BOF at
an upcoming IETF meeting.

Well, I mostly have questions :

Shouldn't the invite be sent to the MBoned and other lists ? I would be glad to 
forward it.

Is OMC intended to support SSM ? ASM ? Bi-Dir ? In a Peer-2-Peer fashion like
BitTorrent or using routers ?

What is the relationship between Overlay Multicast and AMT ?

http://www.americafree.tv/papers/draft-ietf-mboned-auto-multicast-04.txt

And, of course, are there any drafts to look at ?

Regards
Marshall Eubanks

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



From omcast-bounces@ietf.org Tue Sep 27 23:46:29 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKStp-0004KM-7x; Tue, 27 Sep 2005 23:46:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EKStn-0004JI-D0
	for omcast@megatron.ietf.org; Tue, 27 Sep 2005 23:46:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11199
	for <omcast@ietf.org>; Tue, 27 Sep 2005 23:46:25 -0400 (EDT)
Received: from [129.174.65.2] (helo=netlab.gmu.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EKT1A-0006sT-7V
	for omcast@ietf.org; Tue, 27 Sep 2005 23:54:05 -0400
Received: from netlab.gmu.edu (localhost [127.0.0.1])
	by netlab.gmu.edu (8.12.10+Sun/8.12.9) with ESMTP id j8S3kHbY011124;
	Tue, 27 Sep 2005 23:46:17 -0400 (EDT)
Received: from localhost (mpullen@localhost)
	by netlab.gmu.edu (8.12.10+Sun/8.12.8/Submit) with ESMTP id
	j8S3kHM1011120; Tue, 27 Sep 2005 23:46:17 -0400 (EDT)
Date: Tue, 27 Sep 2005 23:46:17 -0400 (EDT)
From: Mark Pullen <mpullen@netlab.gmu.edu>
To: Marshall Eubanks <tme@multicasttech.com>
Subject: Re: [Omcast] Hello to OMCast
In-Reply-To: <web-2993595@multicasttech.com>
Message-ID: <Pine.GSO.4.52.0509272337180.10958@netlab.gmu.edu>
References: <web-2993595@multicasttech.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: omcast@ietf.org
X-BeenThere: omcast@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: pre-BOF overlay multicast discussions <omcast.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/omcast>,
	<mailto:omcast-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/omcast>
List-Post: <mailto:omcast@ietf.org>
List-Help: <mailto:omcast-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/omcast>,
	<mailto:omcast-request@ietf.org?subject=subscribe>
Sender: omcast-bounces@ietf.org
Errors-To: omcast-bounces@ietf.org

Marshall,

On Tue, 27 Sep 2005, Marshall Eubanks wrote:

> Hello;
>
> RE: If you join, please send to the list a brief description
> of why you're interested, to get discussion going. If
> there are enough participants, we'll try for a BOF at
> an upcoming IETF meeting.
>
> Well, I mostly have questions :
>
> Shouldn't the invite be sent to the MBoned and other lists ? I would be glad to
> forward it.

Yes, please do.

>
> Is OMC intended to support SSM ? ASM ? Bi-Dir ? In a Peer-2-Peer fashion like
> BitTorrent or using routers ?

Could be any of the above. Our work is ASM but I doubt the
interest group will achieve critical mass if we resrict it;
so I beleive it is best that we look for commonality among
related approaches.

>
> What is the relationship between Overlay Multicast and AMT ?
>
> http://www.americafree.tv/papers/draft-ietf-mboned-auto-multicast-04.txt
>

As I read the AMT draft, it is intended to function at the
network layer. The OMcast doesn't require or even hope for
any relationship with routers other than send/receive of
unicast packets.

> And, of course, are there any drafts to look at ?
>

No.  Our work is mature enough to support a draft but it's
not clear to me what the common basis for interoperation
will be. I hope to gain insight into that from discussions
on the new list.

Mark


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



From omcast-bounces@ietf.org Wed Sep 28 13:04:47 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKfMN-0000zU-MB; Wed, 28 Sep 2005 13:04:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EKfML-0000zH-6h
	for omcast@megatron.ietf.org; Wed, 28 Sep 2005 13:04:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21441
	for <omcast@ietf.org>; Wed, 28 Sep 2005 13:04:42 -0400 (EDT)
Received: from lennon.multicasttech.com
	([63.105.122.7] helo=multicasttech.com ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EKfTk-00033R-Tc
	for omcast@ietf.org; Wed, 28 Sep 2005 13:12:30 -0400
Received: from [68.100.84.146] (account <marshall_eubanks@multicasttech.com>)
	by multicasttech.com (CommuniGate Pro WebUser 3.4.8)
	with HTTP id 2995069 for <omcast@ietf.org>;
	Wed, 28 Sep 2005 13:04:29 -0400
From: "Marshall Eubanks" <tme@multicasttech.com>
To: omcast@ietf.org
X-Mailer: CommuniGate Pro Web Mailer v.3.4.8
Date: Wed, 28 Sep 2005 13:04:29 -0400
Message-ID: <web-2995069@multicasttech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 8bit
Subject: [Omcast] Microsoft ConferenceXP
X-BeenThere: omcast@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: pre-BOF overlay multicast discussions <omcast.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/omcast>,
	<mailto:omcast-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/omcast>
List-Post: <mailto:omcast@ietf.org>
List-Help: <mailto:omcast-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/omcast>,
	<mailto:omcast-request@ietf.org?subject=subscribe>
Sender: omcast-bounces@ietf.org
Errors-To: omcast-bounces@ietf.org

Is ConferenceXP related to the OMCast goals ?

http://www.conferencexp.net/community/Default.aspx?tabindex=12&tabid=22

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.


There is also

Inter-Partition Networking for Overlay Multicast
Sauleh Eetemadi
Michigan State University

http://www.conferencexp.net/community/library/papers/InternPartitionNetworking.pdf

Regards
Marshall

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



From omcast-bounces@ietf.org Wed Sep 28 21:52:43 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKnbG-0002QJ-Vj; Wed, 28 Sep 2005 21:52:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EKnbF-0002QA-Th
	for omcast@megatron.ietf.org; Wed, 28 Sep 2005 21:52:41 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27622
	for <omcast@ietf.org>; Wed, 28 Sep 2005 21:52:40 -0400 (EDT)
Received: from [129.174.65.2] (helo=netlab.gmu.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EKnip-0002SK-1v
	for omcast@ietf.org; Wed, 28 Sep 2005 22:00:31 -0400
Received: from netlab.gmu.edu (localhost [127.0.0.1])
	by netlab.gmu.edu (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 netlab.gmu.edu (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 (EDT)
From: Mark Pullen <mpullen@netlab.gmu.edu>
To: Marshall Eubanks <tme@multicasttech.com>
Subject: Re: [Omcast] Microsoft ConferenceXP
In-Reply-To: <web-2995069@multicasttech.com>
Message-ID: <Pine.GSO.4.52.0509282138440.18040@netlab.gmu.edu>
References: <web-2995069@multicasttech.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: omcast@ietf.org
X-BeenThere: omcast@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: pre-BOF overlay multicast discussions <omcast.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/omcast>,
	<mailto:omcast-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/omcast>
List-Post: <mailto:omcast@ietf.org>
List-Help: <mailto:omcast-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/omcast>,
	<mailto:omcast-request@ietf.org?subject=subscribe>
Sender: omcast-bounces@ietf.org
Errors-To: omcast-bounces@ietf.org



On Wed, 28 Sep 2005, Marshall Eubanks wrote:

> Is ConferenceXP related to the OMCast goals ?
>
> http://www.conferencexp.net/community/Default.aspx?tabindex=12&tabid=22
>
> 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
>
> http://www.conferencexp.net/community/library/papers/InternPartitionNetworking.pdf
>

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.

Mark


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



