From mailnull@www1.ietf.org  Wed Mar  5 06:41:02 2003
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 GAA27302
	for <rmt-archive@odin.ietf.org>; Wed, 5 Mar 2003 06:41:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25BpwJ18319
	for rmt-archive@odin.ietf.org; Wed, 5 Mar 2003 06:51:58 -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 h25Bpw518312
	for <rmt-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 06:51:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27230
	for <rmt-web-archive@ietf.org>; Wed, 5 Mar 2003 06:40:29 -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 h25Bp4518112;
	Wed, 5 Mar 2003 06:51:04 -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 h25Bhp517433
	for <rmt@optimus.ietf.org>; Wed, 5 Mar 2003 06:43:51 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26581;
	Wed, 5 Mar 2003 06:32:22 -0500 (EST)
Message-Id: <200303051132.GAA26581@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rmt@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Wed, 05 Mar 2003 06:32:22 -0500
Subject: [Rmt] I-D ACTION:draft-ietf-rmt-pi-norm-06.txt,.ps
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Reliable Multicast Transport Working Group of the IETF.

	Title		: NACK-Oriented Reliable Multicast Protocol (NORM)
	Author(s)	: B. Adamson, C. Bormann, M. Handley, J. Macker
	Filename	: draft-ietf-rmt-pi-norm-06.txt,.ps
	Pages		: 63
	Date		: 2003-3-4
	
This document describes the messages and procedures of the Negative-
acknowledgement (NACK) Oriented Reliable Multicast (NORM) protocol.
This protocol is designed to provide end-to-end reliable transport of
bulk data objects or streams over generic IP multicast routing and
forwarding services.  NORM uses a selective, negative acknowledgement
mechanism for transport reliability and offers additional protocol
mechanisms to conduct reliable multicast sessions with limited 'a
priori' coordination among senders and receivers.  A congestion
control scheme is specified to allow the NORM protocol fairly share
available network bandwidth with other transport protocols such as
Transmission Control Protocol (TCP).  It is capable of operating with
both reciprocal multicast routing among senders and receivers and with
asymmetric connectivity (possibly a unicast return path) from the
senders to receivers.  The protocol offers a number of features to
allow different types of applications or possibly other higher level
transport protocols to utilize its service in different ways.  The
protocol leverages the use of FEC-based repair and other IETF reliable
multicast transport (RMT) building blocks in its design.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rmt-pi-norm-06.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-rmt-pi-norm-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rmt-pi-norm-06.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-3-4174454.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rmt-pi-norm-06.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rmt-pi-norm-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-3-4174454.I-D@ietf.org>

--OtherAccess--

--NextPart--


_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From mailnull@www1.ietf.org  Fri Mar  7 07:10:07 2003
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 HAA23860
	for <rmt-archive@odin.ietf.org>; Fri, 7 Mar 2003 07:10:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27CLap17831
	for rmt-archive@odin.ietf.org; Fri, 7 Mar 2003 07:21:36 -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 h27CLaO17828
	for <rmt-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 07:21:36 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23829
	for <rmt-web-archive@ietf.org>; Fri, 7 Mar 2003 07:09:35 -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 h27CIsO17650;
	Fri, 7 Mar 2003 07:18:54 -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 h27C6BO15775
	for <rmt@optimus.ietf.org>; Fri, 7 Mar 2003 07:06:11 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21479;
	Fri, 7 Mar 2003 06:54:11 -0500 (EST)
Message-Id: <200303071154.GAA21479@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rmt@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 07 Mar 2003 06:54:11 -0500
Subject: [Rmt] I-D ACTION:draft-ietf-rmt-bb-norm-05.txt,.ps
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Reliable Multicast Transport Working Group of the IETF.

	Title		: NACK-Oriented Reliable Multicast (NORM) Protocol 
                          Building Blocks
	Author(s)	: B. Adamson, C. Bormann, M. Handley, J. Macker
	Filename	: draft-ietf-rmt-bb-norm-05.txt,.ps
	Pages		: 32
	Date		: 2003-3-6
	
This document discusses the creation the of negative-acknowledgment
(NACK)-oriented reliable multicast (NORM) protocols.  The general
goals and  assumptions for NORM are defined.  Technical challenges for
NACK-oriented (and in some cases general) reliable multicast protocol
operation are identified.  These goals and challenges are resolved
into a set of functional 'building blocks' that address different
aspects of NORM protocol operation.  It is anticipated that these
building blocks will be useful in generating different instantiations
of reliable multicast protocols.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rmt-bb-norm-05.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-rmt-bb-norm-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rmt-bb-norm-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-3-6125404.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rmt-bb-norm-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rmt-bb-norm-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-3-6125404.I-D@ietf.org>

--OtherAccess--

--NextPart--


_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From mailnull@www1.ietf.org  Tue Mar 11 02:13:16 2003
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 CAA10603
	for <rmt-archive@odin.ietf.org>; Tue, 11 Mar 2003 02:13:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2B7QcD04498
	for rmt-archive@odin.ietf.org; Tue, 11 Mar 2003 02:26:38 -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 h2B7QbO04495
	for <rmt-web-archive@optimus.ietf.org>; Tue, 11 Mar 2003 02:26:37 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10545
	for <rmt-web-archive@ietf.org>; Tue, 11 Mar 2003 02:12:45 -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 h2B7PqO04442;
	Tue, 11 Mar 2003 02:25:52 -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 h2B7NSO04346
	for <rmt@optimus.ietf.org>; Tue, 11 Mar 2003 02:23:28 -0500
Received: from sj-core-2.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09425
	for <rmt@ietf.org>; Tue, 11 Mar 2003 02:09:35 -0500 (EST)
Received: from cisco.com (cypher.cisco.com [171.69.11.143])
	by sj-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h2B7BgEY017222;
	Mon, 10 Mar 2003 23:11:42 -0800 (PST)
Received: (from lorenzo@localhost)
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id XAA21510;
	Mon, 10 Mar 2003 23:11:42 -0800 (PST)
Date: Mon, 10 Mar 2003 23:11:42 -0800
From: Lorenzo Vicisano <lorenzo@cisco.com>
To: rmt@ietf.org
Cc: Roger.Kermode@motorola.com, Lorenzo Vicisano <lorenzo@cisco.com>
Message-ID: <20030310231142.C16781@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.23i
Subject: [Rmt] SF IETF: call for agenda items
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=subscribe>

dear RMT-ers,

please send us your agenda item requests for the upcoming
IETF.

We would appreciate if you could do so by Thursday evening PST,
so that we would have a chace to post the agend before the w.e.

The usual considerations about the presentation content apply.

	thank you,
	Lorenzo and Roger.
_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From mailnull@www1.ietf.org  Sun Mar 16 19:21:10 2003
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 TAA13829
	for <rmt-archive@odin.ietf.org>; Sun, 16 Mar 2003 19:21:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2H0bI904749
	for rmt-archive@odin.ietf.org; Sun, 16 Mar 2003 19:37:18 -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 h2H0bIO04740
	for <rmt-web-archive@optimus.ietf.org>; Sun, 16 Mar 2003 19:37:18 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13820
	for <rmt-web-archive@ietf.org>; Sun, 16 Mar 2003 19:20:39 -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 h2H0aLO04068;
	Sun, 16 Mar 2003 19:36: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 h2H0YuO04010
	for <rmt@optimus.ietf.org>; Sun, 16 Mar 2003 19:34:56 -0500
Received: from sj-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13759
	for <rmt@ietf.org>; Sun, 16 Mar 2003 19:18:17 -0500 (EST)
Received: from cisco.com (cypher.cisco.com [171.69.11.143])
	by sj-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h2H0KR0E028359;
	Sun, 16 Mar 2003 16:20:28 -0800 (PST)
Received: (from lorenzo@localhost)
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id QAA27353;
	Sun, 16 Mar 2003 16:20:27 -0800 (PST)
Date: Sun, 16 Mar 2003 16:20:27 -0800
From: Lorenzo Vicisano <lorenzo@cisco.com>
To: rmt@ietf.org
Cc: Roger Kermode <Roger.Kermode@motorola.com>,
        Allison Mankin <mankin@psg.com>, jon.peterson@neustar.biz,
        Lorenzo Vicisano <lorenzo@cisco.com>
Message-ID: <20030316162027.M14088@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.23i
Subject: [Rmt] new RMT Charter
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=subscribe>

dear RMTers,

please find attached the text of what will likely be our
new charter. It has already been approved by the IESG, but
it is still under IAB review.

We will have a discussion about this in tomorrow's meeting,
but please note two important changes:

 - RMT is hosting a sub-group chartered to standardize a
   small-scale, unicast-based, simple replication service.

 - TRACK has been taken out of the charter.

Also please note the new aggressive milestones, aimed at
closing the WG activity within the next one or two IETF meetings,
after the current one.

	thank you,
	Roger and Lorenzo


Reliable Multicast Transport (rmt) Working Group

Chairs:
Roger Kermode <roger.kermode@motorola.com>
Lorenzo Vicisano <lorenzo@cisco.com>

Area Director:  Allison Mankin <mankin@psg.com>



The purpose of this WG is to standardize reliable multicast transport.

Initial efforts have focused solely on the standardization of the
one-to-many transport of large amounts of data. Due to the large
number of applications that fall into this category, and the sometimes
orthogonal requirements these applications exhibit, it is believed
that a "one size fits all" protocol will be unable to meet the
requirements of all applications. In recognition of this observation,
this working group will standardize two protocol instantiations,
initially as Experimental protocols, and then as warranted, in the
standards track, from the following families:

1) A NACK-based protocol.
2) An "Asynchronous Layered Coding protocol that uses Forward Error
   Correction.

In addition, the rmt WG will have a sub-group for a different task.
This sub-group will develop a protocol for a simple unicast
replication service that is specifically designed to address the need
of very-small-scale multicast sessions. The goal of this protocol is
to provide a small-scale replication solution that does not require
per-session state in all parts of the network crossed by the session
traffic, unlike native IP multicast.  The applicability of this
protocol is to situations where end-to-end unicast replication is not
appropriate due to bandwidth limitation in some part of the
network (usually last-mile links).

It should be noted that this simple unicast replication work is in a
sub-group because a strict interpretation of this service would
determine that it falls somewhat outside the transport domain (other
than congestion control) and has more routing issues than most of the
other work in rmt.  Given that the bulk of the experts who would be
qualified to comment on this work item are already active participants
in the rmt WG, the Routing and Transport Area Directors have concluded
to make an exception and develop it in this working group's sub-group
instead of forming a new working group.

The WG will carry out protocol standardization in general by composing a
a set of RFCs that specify
       
- building blocks: A set of easily-separable coarse-grained modular
components that are common to multiple protocols along with abstract
APIs that define a building block's access methods and their
arguments.

- protocol instantiations: Specifications that define the necessary
gluing logic and minimal additional functionality required to realize
a working protocol from one or more building blocks. These
specifications will also include an abstract API that defines the
interface between the protocol implementation and an application.

The WG has previously completed work on three documents to assist in
the standardization process. RFC2887 describes the design-space in  
which the one-to-many transport protocols will be developed. RFC3048
explains the concepts of building-blocks and protocol
instantiations. RFC3269 provides guidelines to authors of drafts that
specify building-blocks and protocol instantiations.

The WG will generate and submit for standardization drafts of the
following building-blocks for use in the construction of the two
protocols: congestion control, negative acknowledgments, forward error
correction, generic mechanisms for router assist, and to address the  
RFC 2357 security requirements.

The WG will also standardize and generate RFCs for the following two
protocol instantiations: A NACK-based protocol, and an Asynchronous 
Layered Coding (ALC) protocol that uses Forward Error Correction.   
RFC 3450 is the Experimental RFC of the ALC protocol instantiation. 

If new requirements are identified that cannot be satisfied with the
building-blocks and protocol instantiations described above, the Area
Directors in consultation with the IESG may add additional
building-blocks and protocol instantiations to the working group
deliverables.

This working group will work closely with the Internet Research Task
Force (IRTF) groups on Reliable Multicast (RMRG) and
Secure Multicast (SMUG), especially for meeting the congestion control
and security requirements mandated by RFC 2357. This working group may
work with the Area Directors to recharter to standardize reliable
multicast for additional scenarios beyond the one-to-many transport of
bulk data once they are sufficiently well understood.

Future MILESTONES:

 MAY 03 Submit congestion control building block (TFMCC, WEBRC, PGMCC) for
        publication as Experimental

 AUG 03 Submit NACK building block and protocol instantiation for publication
        as Experimental

 AUG 03 Submission of simple unicast replication building block
        for publication as Experimental, possibly including a specification
        or considerations on how to achieve congestion control

 DEC 03 Evaluate when and how the RMT Experimental specifications
        will be submitted for publication as Proposed Standard, and
        update this charter accordingly.


_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From mailnull@www1.ietf.org  Sun Mar 16 19:45:42 2003
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 TAA14107
	for <rmt-archive@odin.ietf.org>; Sun, 16 Mar 2003 19:45:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2H11pu05649
	for rmt-archive@odin.ietf.org; Sun, 16 Mar 2003 20:01:51 -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 h2H11pO05646
	for <rmt-web-archive@optimus.ietf.org>; Sun, 16 Mar 2003 20:01:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14101
	for <rmt-web-archive@ietf.org>; Sun, 16 Mar 2003 19:45:11 -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 h2H0vAO05472;
	Sun, 16 Mar 2003 19:57:10 -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 h2H0uKO05442
	for <rmt@optimus.ietf.org>; Sun, 16 Mar 2003 19:56:20 -0500
Received: from sj-core-5.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14042
	for <rmt@ietf.org>; Sun, 16 Mar 2003 19:39:41 -0500 (EST)
Received: from cisco.com (cypher.cisco.com [171.69.11.143])
	by sj-core-5.cisco.com (8.12.6/8.12.6) with ESMTP id h2H0fqhs009186;
	Sun, 16 Mar 2003 16:41:52 -0800 (PST)
Received: (from lorenzo@localhost)
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id QAA29303;
	Sun, 16 Mar 2003 16:39:46 -0800 (PST)
Date: Sun, 16 Mar 2003 16:39:46 -0800
From: Lorenzo Vicisano <lorenzo@cisco.com>
To: rmt@ietf.org
Cc: Roger Kermode <Roger.Kermode@motorola.com>,
        Allison Mankin <mankin@psg.com>, jon.peterson@neustar.biz,
        Lorenzo Vicisano <lorenzo@cisco.com>
Message-ID: <20030316163946.N14088@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.23i
Subject: [Rmt] 56th IETF - RMT agenda
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=subscribe>

Dear RMTers,

please find attached the meeting agenda.

	thank you,
	Lorenzo


RMT Meeting, 56th IETF - San Francisco
Mon, March 17, 1530-1730 (Room: Continental 1-4)


   Agenda Bashing                            Lorenzo Vicisano    5 mins

   New Charter discussion                    ADs/Chairs         20 mins
   
   NORM BB and PI updates                    Brian Adamson      15 mins
        draft-ietf-rmt-bb-norm-05.txt
        draft-ietf-rmt-pi-norm-06.txt
   New "compact" scheme FEC BB               Mike Luby          20 mins
        draft-ietf-rmt-bb-fec-supp-inband-00.txt
   New FDALC draft                           Toni Paila         20 mins
        draft-paila-rmt-fdalc-00.txt

   Kick off of the "Small Group Replication Service" subgroup
                                             Rick Boivie        20 mins

_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From mailnull@www1.ietf.org  Mon Mar 17 17:47:55 2003
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 RAA05475
	for <rmt-archive@odin.ietf.org>; Mon, 17 Mar 2003 17:47:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2HN4T111188
	for rmt-archive@odin.ietf.org; Mon, 17 Mar 2003 18:04:29 -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 h2HN4TO11185
	for <rmt-web-archive@optimus.ietf.org>; Mon, 17 Mar 2003 18:04:29 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05462
	for <rmt-web-archive@ietf.org>; Mon, 17 Mar 2003 17:47:23 -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 h2HN46O11162;
	Mon, 17 Mar 2003 18:04:06 -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 h2HN2mO11046
	for <rmt@optimus.ietf.org>; Mon, 17 Mar 2003 18:02:48 -0500
Received: from eve.icir.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05364
	for <rmt@ietf.org>; Mon, 17 Mar 2003 17:45:42 -0500 (EST)
Received: from eve.icir.org (localhost [127.0.0.1])
	by eve.icir.org (8.12.7/8.12.2) with ESMTP id h2HMlVec006345;
	Mon, 17 Mar 2003 14:47:31 -0800 (PST)
From: Mark Handley <mjh@icir.org>
X-Organisation: ICIR
To: Lorenzo Vicisano <lorenzo@cisco.com>
cc: rmt@ietf.org, Roger Kermode <Roger.Kermode@motorola.com>,
        Allison Mankin <mankin@psg.com>, jon.peterson@neustar.biz
Subject: Re: [Rmt] new RMT Charter 
In-reply-to: Your message of "Sun, 16 Mar 2003 16:20:27 PST."
             <20030316162027.M14088@cisco.com> 
Date: Mon, 17 Mar 2003 14:47:31 -0800
Message-ID: <6344.1047941251@eve.icir.org>
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=subscribe>


>In addition, the rmt WG will have a sub-group for a different task.
>This sub-group will develop a protocol for a simple unicast
>replication service that is specifically designed to address the need
>of very-small-scale multicast sessions. The goal of this protocol is
>to provide a small-scale replication solution that does not require
>per-session state in all parts of the network crossed by the session
>traffic, unlike native IP multicast.  The applicability of this
>protocol is to situations where end-to-end unicast replication is not
>appropriate due to bandwidth limitation in some part of the
>network (usually last-mile links).

I'm confused.  Is the proposal that the replication happens at the
application layer, or is this a ressurection of xcast through a
transport-area back door?

Cheers,
	Mark
_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From mailnull@www1.ietf.org  Tue Mar 18 16:54:19 2003
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 QAA02072
	for <rmt-archive@odin.ietf.org>; Tue, 18 Mar 2003 16:54:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2IMBNZ24108
	for rmt-archive@odin.ietf.org; Tue, 18 Mar 2003 17:11:23 -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 h2IMBNO24105
	for <rmt-web-archive@optimus.ietf.org>; Tue, 18 Mar 2003 17:11:23 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02049
	for <rmt-web-archive@ietf.org>; Tue, 18 Mar 2003 16:53:47 -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 h2IMAcO24056;
	Tue, 18 Mar 2003 17:10:38 -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 h2IM8xO23959
	for <rmt@optimus.ietf.org>; Tue, 18 Mar 2003 17:09:00 -0500
Received: from sj-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01987
	for <rmt@ietf.org>; Tue, 18 Mar 2003 16:51:24 -0500 (EST)
Received: from cisco.com (cypher.cisco.com [171.69.11.143])
	by sj-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h2ILra0E018734;
	Tue, 18 Mar 2003 13:53:37 -0800 (PST)
Received: (from lorenzo@localhost)
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id NAA07754;
	Tue, 18 Mar 2003 13:53:36 -0800 (PST)
Date: Tue, 18 Mar 2003 13:53:36 -0800
From: Lorenzo Vicisano <lorenzo@cisco.com>
To: rmt@ietf.org
Cc: Roger Kermode <Roger.Kermode@motorola.com>,
        Allison Mankin <mankin@psg.com>, jon.peterson@neustar.biz
Message-ID: <20030318135336.E23051@cisco.com>
References: <20030316162027.M14088@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030316162027.M14088@cisco.com>
User-Agent: Mutt/1.3.23i
Subject: [Rmt] Re: new RMT Charter
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=subscribe>

A few updates on the re-chartering:

first of all, I apologize that I gave the wrong impression that
the WG had no saying on the new charter. This was just a
proposed-charter and the WG Is invited to comment on it.

Indeed at yesterday's meeting we had important feedback
that lead to a few changes:

 - The small-scale, unicast-based, simple replication service
   subgroup has been removed from the proposed charter

 - some of the milestones dates have been adjusted to allow
   more time to complete the tasks.

We will soon send the re-vised proposed charter to this mailing list.

	thank you,
	Lorenzo

On Sun, Mar 16, 2003 at 04:20:27PM -0800, Lorenzo Vicisano wrote:
> dear RMTers,
> 
> please find attached the text of what will likely be our
> new charter. It has already been approved by the IESG, but
> it is still under IAB review.
> 
> We will have a discussion about this in tomorrow's meeting,
> but please note two important changes:
> 
>  - RMT is hosting a sub-group chartered to standardize a
>    small-scale, unicast-based, simple replication service.
> 
>  - TRACK has been taken out of the charter.
> 
> Also please note the new aggressive milestones, aimed at
> closing the WG activity within the next one or two IETF meetings,
> after the current one.
> 
> 	thank you,
> 	Roger and Lorenzo
> 
> 
> Reliable Multicast Transport (rmt) Working Group
> 
> Chairs:
> Roger Kermode <roger.kermode@motorola.com>
> Lorenzo Vicisano <lorenzo@cisco.com>
> 
> Area Director:  Allison Mankin <mankin@psg.com>
> 
> 
> 
> The purpose of this WG is to standardize reliable multicast transport.
> 
> Initial efforts have focused solely on the standardization of the
> one-to-many transport of large amounts of data. Due to the large
> number of applications that fall into this category, and the sometimes
> orthogonal requirements these applications exhibit, it is believed
> that a "one size fits all" protocol will be unable to meet the
> requirements of all applications. In recognition of this observation,
> this working group will standardize two protocol instantiations,
> initially as Experimental protocols, and then as warranted, in the
> standards track, from the following families:
> 
> 1) A NACK-based protocol.
> 2) An "Asynchronous Layered Coding protocol that uses Forward Error
>    Correction.
> 
> In addition, the rmt WG will have a sub-group for a different task.
> This sub-group will develop a protocol for a simple unicast
> replication service that is specifically designed to address the need
> of very-small-scale multicast sessions. The goal of this protocol is
> to provide a small-scale replication solution that does not require
> per-session state in all parts of the network crossed by the session
> traffic, unlike native IP multicast.  The applicability of this
> protocol is to situations where end-to-end unicast replication is not
> appropriate due to bandwidth limitation in some part of the
> network (usually last-mile links).
> 
> It should be noted that this simple unicast replication work is in a
> sub-group because a strict interpretation of this service would
> determine that it falls somewhat outside the transport domain (other
> than congestion control) and has more routing issues than most of the
> other work in rmt.  Given that the bulk of the experts who would be
> qualified to comment on this work item are already active participants
> in the rmt WG, the Routing and Transport Area Directors have concluded
> to make an exception and develop it in this working group's sub-group
> instead of forming a new working group.
> 
> The WG will carry out protocol standardization in general by composing a
> a set of RFCs that specify
>        
> - building blocks: A set of easily-separable coarse-grained modular
> components that are common to multiple protocols along with abstract
> APIs that define a building block's access methods and their
> arguments.
> 
> - protocol instantiations: Specifications that define the necessary
> gluing logic and minimal additional functionality required to realize
> a working protocol from one or more building blocks. These
> specifications will also include an abstract API that defines the
> interface between the protocol implementation and an application.
> 
> The WG has previously completed work on three documents to assist in
> the standardization process. RFC2887 describes the design-space in  
> which the one-to-many transport protocols will be developed. RFC3048
> explains the concepts of building-blocks and protocol
> instantiations. RFC3269 provides guidelines to authors of drafts that
> specify building-blocks and protocol instantiations.
> 
> The WG will generate and submit for standardization drafts of the
> following building-blocks for use in the construction of the two
> protocols: congestion control, negative acknowledgments, forward error
> correction, generic mechanisms for router assist, and to address the  
> RFC 2357 security requirements.
> 
> The WG will also standardize and generate RFCs for the following two
> protocol instantiations: A NACK-based protocol, and an Asynchronous 
> Layered Coding (ALC) protocol that uses Forward Error Correction.   
> RFC 3450 is the Experimental RFC of the ALC protocol instantiation. 
> 
> If new requirements are identified that cannot be satisfied with the
> building-blocks and protocol instantiations described above, the Area
> Directors in consultation with the IESG may add additional
> building-blocks and protocol instantiations to the working group
> deliverables.
> 
> This working group will work closely with the Internet Research Task
> Force (IRTF) groups on Reliable Multicast (RMRG) and
> Secure Multicast (SMUG), especially for meeting the congestion control
> and security requirements mandated by RFC 2357. This working group may
> work with the Area Directors to recharter to standardize reliable
> multicast for additional scenarios beyond the one-to-many transport of
> bulk data once they are sufficiently well understood.
> 
> Future MILESTONES:
> 
>  MAY 03 Submit congestion control building block (TFMCC, WEBRC, PGMCC) for
>         publication as Experimental
> 
>  AUG 03 Submit NACK building block and protocol instantiation for publication
>         as Experimental
> 
>  AUG 03 Submission of simple unicast replication building block
>         for publication as Experimental, possibly including a specification
>         or considerations on how to achieve congestion control
> 
>  DEC 03 Evaluate when and how the RMT Experimental specifications
>         will be submitted for publication as Proposed Standard, and
>         update this charter accordingly.
> 
_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From mailnull@www1.ietf.org  Wed Mar 19 12:55:53 2003
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 MAA27974
	for <rmt-archive@odin.ietf.org>; Wed, 19 Mar 2003 12:55:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2JIDKw17253
	for rmt-archive@odin.ietf.org; Wed, 19 Mar 2003 13:13:20 -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 h2JIDKO17250
	for <rmt-web-archive@optimus.ietf.org>; Wed, 19 Mar 2003 13:13:20 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27925
	for <rmt-web-archive@ietf.org>; Wed, 19 Mar 2003 12:55:22 -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 h2JICYO17213;
	Wed, 19 Mar 2003 13:12:34 -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 h2JIBCO17152
	for <rmt@optimus.ietf.org>; Wed, 19 Mar 2003 13:11:12 -0500
Received: from e32.co.us.ibm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27855
	for <rmt@ietf.org>; Wed, 19 Mar 2003 12:53:14 -0500 (EST)
Received: from westrelay04.boulder.ibm.com (westrelay04.boulder.ibm.com [9.17.193.32])
	by e32.co.us.ibm.com (8.12.8/8.12.2) with ESMTP id h2JHsZTr029656;
	Wed, 19 Mar 2003 12:54:35 -0500
Received: from d03nm690.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.193.82])
	by westrelay04.boulder.ibm.com (8.12.8/NCO/VER6.5) with ESMTP id h2JHtPZt173230;
	Wed, 19 Mar 2003 10:55:25 -0700
Importance: Normal
To: Sally Floyd <floyd@icir.org>
Cc: rmt@ietf.org
X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000
Message-ID: <OFDD308438.D9CEDB1E-ON85256CEE.0057C55E@us.ibm.com>
From: Rick Boivie <rhboivie@us.ibm.com>
Date: Wed, 19 Mar 2003 12:55:22 -0500
X-MIMETrack: Serialize by Router on D03NM690/03/M/IBM(Release 6.0 [IBM]|December 16, 2002) at
 03/19/2003 10:55:24
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Subject: [Rmt] small group replication service, application-level multicast etc.
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=subscribe>





Sally,
You mentioned the work that's been done in application-level multicast.
But this doesn't appear to be useful in solving the problem we're trying to
solve.

As I mentioned in the meeting on Monday, we're trying to solve the problem
of limited bandwidth in the first mile so that we can provide scalable
support for applications like VoIP conferencing, videoconferencing,
e-meetings in which there are likely to be very large numbers of
not-very-large groups.

In our view, the various multicast schemes (e.g. real multicast,
application level multicast) don't solve this problem very well since they
involve per-flow state and per flow signaling -- which, in our view, is not
the right model if one wants to support very large numbers of simultaneous
conferences.  We don't want to have to store state for tens of thousands or
tens of millions of distinct small groups and we don't want to have to
repair millions of distinct multicast distribution trees after a topology
change.

Does that make sense?

Rick Boivie

This problem of maintaining multicast state can be minimized in an
end-system multicast scheme if the multicast state is kept only in the
end-systems of the meeting participants.  But this approach doesn't seem
appropriate if we have limited bandwidth in the first mile (see problem
statement above).

_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From mailnull@www1.ietf.org  Wed Mar 19 13:44:19 2003
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 NAA00187
	for <rmt-archive@odin.ietf.org>; Wed, 19 Mar 2003 13:44:18 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2JJ1l921672
	for rmt-archive@odin.ietf.org; Wed, 19 Mar 2003 14:01:47 -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 h2JJ1lO21669
	for <rmt-web-archive@optimus.ietf.org>; Wed, 19 Mar 2003 14:01:47 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00166
	for <rmt-web-archive@ietf.org>; Wed, 19 Mar 2003 13:43:47 -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 h2JJ19O21617;
	Wed, 19 Mar 2003 14:01:09 -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 h2JJ0KO21554
	for <rmt@optimus.ietf.org>; Wed, 19 Mar 2003 14:00:20 -0500
Received: from open-content.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA00087
	for <rmt@ietf.org>; Wed, 19 Mar 2003 13:42:21 -0500 (EST)
Received: (qmail 3351 invoked from network); 20 Mar 2003 07:46:45 -0000
Received: from c-24-118-168-169.mn.client2.attbi.com (HELO chapweske.com) (24.118.168.169)
  by onionnetworks.com with SMTP; 20 Mar 2003 07:46:45 -0000
Message-ID: <3E78BA8F.8040206@chapweske.com>
Date: Wed, 19 Mar 2003 12:44:31 -0600
From: Justin Chapweske <justin@chapweske.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Rick Boivie <rhboivie@us.ibm.com>
CC: Sally Floyd <floyd@icir.org>, rmt@ietf.org
Subject: Re: [Rmt] small group replication service, application-level multicast
 etc.
References: <OFDD308438.D9CEDB1E-ON85256CEE.0057C55E@us.ibm.com>
In-Reply-To: <OFDD308438.D9CEDB1E-ON85256CEE.0057C55E@us.ibm.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Actually, the Swarmcast system that we developed in late 1999 utilized 
Forward Error Correction combined with peer-to-peer (end-system) 
multicast to overcome the first-mile bottleneck in systems like this.

I'd be happy to discuss this approach off-line with anyone that is 
interested.

Thanks,

-Justin

> 
> This problem of maintaining multicast state can be minimized in an
> end-system multicast scheme if the multicast state is kept only in the
> end-systems of the meeting participants.  But this approach doesn't seem
> appropriate if we have limited bandwidth in the first mile (see problem
> statement above).
> 

-- 
Justin Chapweske, Onion Networks
http://onionnetworks.com/

_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From mailnull@www1.ietf.org  Wed Mar 19 14:00:28 2003
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 OAA00920
	for <rmt-archive@odin.ietf.org>; Wed, 19 Mar 2003 14:00:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2JJHu623595
	for rmt-archive@odin.ietf.org; Wed, 19 Mar 2003 14:17:56 -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 h2JJHuO23592
	for <rmt-web-archive@optimus.ietf.org>; Wed, 19 Mar 2003 14:17:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00860
	for <rmt-web-archive@ietf.org>; Wed, 19 Mar 2003 13:59:56 -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 h2JJHCO23549;
	Wed, 19 Mar 2003 14:17:12 -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 h2JJG8O23491
	for <rmt@optimus.ietf.org>; Wed, 19 Mar 2003 14:16:08 -0500
Received: from e35.co.us.ibm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00792
	for <rmt@ietf.org>; Wed, 19 Mar 2003 13:58:08 -0500 (EST)
Received: from westrelay04.boulder.ibm.com (westrelay04.boulder.ibm.com [9.17.193.32])
	by e35.co.us.ibm.com (8.12.8/8.12.2) with ESMTP id h2JJ0HgJ042196;
	Wed, 19 Mar 2003 14:00:17 -0500
Received: from d03nm690.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.193.82])
	by westrelay04.boulder.ibm.com (8.12.8/NCO/VER6.5) with ESMTP id h2JJ0FZu196582;
	Wed, 19 Mar 2003 12:00:16 -0700
Importance: Normal
Subject: Re: [Rmt] small group replication service, application-level multicast etc.
To: Justin Chapweske <justin@chapweske.com>
Cc: Sally Floyd <floyd@icir.org>, rmt@ietf.org
X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000
Message-ID: <OFA0A5687F.26B339AE-ON85256CEE.0068399D@us.ibm.com>
From: Rick Boivie <rhboivie@us.ibm.com>
Date: Wed, 19 Mar 2003 14:00:14 -0500
X-MIMETrack: Serialize by Router on D03NM690/03/M/IBM(Release 6.0 [IBM]|December 16, 2002) at
 03/19/2003 12:00:16
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=subscribe>





>Actually, the Swarmcast system that we developed in late 1999 utilized
>Forward Error Correction combined with peer-to-peer (end-system)
>multicast to overcome the first-mile bottleneck in systems like this.
>
>I'd be happy to discuss this approach off-line with anyone that is
>interested.
>

Justin,  Thanks.  Can you provide a reference?
Rick

_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From mailnull@www1.ietf.org  Wed Mar 19 14:31:40 2003
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 OAA02486
	for <rmt-archive@odin.ietf.org>; Wed, 19 Mar 2003 14:31:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2JJnAS26960
	for rmt-archive@odin.ietf.org; Wed, 19 Mar 2003 14:49:10 -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 h2JJnAO26955
	for <rmt-web-archive@optimus.ietf.org>; Wed, 19 Mar 2003 14:49:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02459
	for <rmt-web-archive@ietf.org>; Wed, 19 Mar 2003 14:31:08 -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 h2JJm9O26795;
	Wed, 19 Mar 2003 14:48:09 -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 h2JJjYO26443
	for <rmt@optimus.ietf.org>; Wed, 19 Mar 2003 14:45:34 -0500
Received: from open-content.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA02200
	for <rmt@ietf.org>; Wed, 19 Mar 2003 14:27:33 -0500 (EST)
Received: (qmail 3485 invoked from network); 20 Mar 2003 08:31:58 -0000
Received: from c-24-118-168-169.mn.client2.attbi.com (HELO chapweske.com) (24.118.168.169)
  by onionnetworks.com with SMTP; 20 Mar 2003 08:31:58 -0000
Message-ID: <3E78C52B.1050505@chapweske.com>
Date: Wed, 19 Mar 2003 13:29:47 -0600
From: Justin Chapweske <justin@chapweske.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Rick Boivie <rhboivie@us.ibm.com>
CC: Sally Floyd <floyd@icir.org>, rmt@ietf.org
Subject: Re: [Rmt] small group replication service, application-level multicast
 etc.
References: <OFA0A5687F.26B339AE-ON85256CEE.0068399D@us.ibm.com>
In-Reply-To: <OFA0A5687F.26B339AE-ON85256CEE.0068399D@us.ibm.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>>Actually, the Swarmcast system that we developed in late 1999 utilized
>>Forward Error Correction combined with peer-to-peer (end-system)
>>multicast to overcome the first-mile bottleneck in systems like this.
>>
>>I'd be happy to discuss this approach off-line with anyone that is
>>interested.
>>
> 
> 
> Justin,  Thanks.  Can you provide a reference?
> Rick

Swarmcast was a commercial endeavor, so no papers were published on it.

An old article at 
(http://www.openp2p.com/pub/a/p2p/2001/05/24/swarmcast_beta.html) 
provides an overview of the system and I'd be happy to answer any 
questions about it off-line.

-- 
Justin Chapweske, Onion Networks
http://onionnetworks.com/

_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From mailnull@www1.ietf.org  Wed Mar 19 14:40:01 2003
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 OAA02857
	for <rmt-archive@odin.ietf.org>; Wed, 19 Mar 2003 14:40:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2JJvVE27584
	for rmt-archive@odin.ietf.org; Wed, 19 Mar 2003 14:57:31 -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 h2JJvVO27581
	for <rmt-web-archive@optimus.ietf.org>; Wed, 19 Mar 2003 14:57:31 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02827
	for <rmt-web-archive@ietf.org>; Wed, 19 Mar 2003 14:39:30 -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 h2JJv4O27543;
	Wed, 19 Mar 2003 14:57:04 -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 h2JJutO27500
	for <rmt@optimus.ietf.org>; Wed, 19 Mar 2003 14:56:55 -0500
Received: from scandium.dolby.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA02800
	for <rmt@ietf.org>; Wed, 19 Mar 2003 14:38:54 -0500 (EST)
Received: from platinum.dolby.net ([172.16.33.28]) by 192.168.16.253 with InterScan Messaging Security Suite; Wed, 19 Mar 2003 11:40:24 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Subject: RE: [Rmt] small group replication service, application-level multicast etc.
Date: Wed, 19 Mar 2003 11:40:24 -0800
Message-ID: <5FCCC03CAF7C5C4C8E2F995E3D72E133CE3EBA@platinum.dolby.net>
Thread-Topic: [Rmt] small group replication service, application-level multicast etc.
Thread-Index: AcLuTzGMGNOUtJfeTLi2/e3DKa2qvwAACx1S
From: "Bauer, Claus" <cb@dolby.com>
To: "Justin Chapweske" <justin@chapweske.com>,
        "Rick Boivie" <rhboivie@us.ibm.com>
Cc: "Sally Floyd" <floyd@icir.org>, <rmt@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2JJutO27501
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


Do you have a pointer to a description of the Swarmcast ?


-----Original Message-----
From:	Justin Chapweske [mailto:justin@chapweske.com]
Sent:	Wed 3/19/2003 10:44 AM
To:	Rick Boivie
Cc:	Sally Floyd; rmt@ietf.org
Subject:	Re: [Rmt] small group replication service, application-level multicast etc.
Actually, the Swarmcast system that we developed in late 1999 utilized 
Forward Error Correction combined with peer-to-peer (end-system) 
multicast to overcome the first-mile bottleneck in systems like this.

I'd be happy to discuss this approach off-line with anyone that is 
interested.

Thanks,

-Justin

> 
> This problem of maintaining multicast state can be minimized in an
> end-system multicast scheme if the multicast state is kept only in the
> end-systems of the meeting participants.  But this approach doesn't seem
> appropriate if we have limited bandwidth in the first mile (see problem
> statement above).
> 

-- 
Justin Chapweske, Onion Networks
http://onionnetworks.com/

_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt




This message (including any attachments) may contain confidential information intended for a specific individual and purpose. If you are not the intended recipient, delete this message. If you are not the intended recipient, disclosing, copying, distributing, or taking any action based on this message is strictly prohibited.
_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From mailnull@www1.ietf.org  Wed Mar 19 20:47:27 2003
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 UAA20342
	for <rmt-archive@odin.ietf.org>; Wed, 19 Mar 2003 20:47:27 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2K254u29306
	for rmt-archive@odin.ietf.org; Wed, 19 Mar 2003 21:05:04 -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 h2K254O29303
	for <rmt-web-archive@optimus.ietf.org>; Wed, 19 Mar 2003 21:05:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20311
	for <rmt-web-archive@ietf.org>; Wed, 19 Mar 2003 20:46:55 -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 h2K24TO29264;
	Wed, 19 Mar 2003 21:04:29 -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 h2K234O29182
	for <rmt@optimus.ietf.org>; Wed, 19 Mar 2003 21:03:04 -0500
Received: from e32.co.us.ibm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20219
	for <rmt@ietf.org>; Wed, 19 Mar 2003 20:44:55 -0500 (EST)
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11])
	by e32.co.us.ibm.com (8.12.8/8.12.2) with ESMTP id h2K1kBTr044498;
	Wed, 19 Mar 2003 20:46:11 -0500
Received: from d03nm690.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.193.82])
	by westrelay02.boulder.ibm.com (8.12.8/NCO/VER6.5) with ESMTP id h2K1l2Jo107056;
	Wed, 19 Mar 2003 18:47:03 -0700
Importance: Normal
Subject: Re: [Rmt] small group replication service, application-level mult	icast etc.
To: sjkoh@etri.re.kr
Cc: justin@chapweske.com, floyd@icir.org, rmt@ietf.org
X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000
Message-ID: <OF45BB4910.1A4C1027-ON85256CEF.00098E89@us.ibm.com>
From: Rick Boivie <rhboivie@us.ibm.com>
Date: Wed, 19 Mar 2003 20:47:00 -0500
X-MIMETrack: Serialize by Router on D03NM690/03/M/IBM(Release 6.0 [IBM]|December 16, 2002) at
 03/19/2003 18:47:03
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=subscribe>





> An ideal approach, I think, will be to combine those two, Xcast and ALM,
>more effectively, so that only good features of them can be drawn.

Seok.  This sounds right.  And this is what I think we were trying to
define
with the small group replication service.
Rick Boivie

_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From mailnull@www1.ietf.org  Wed Mar 19 22:09:24 2003
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 WAA21850
	for <rmt-archive@odin.ietf.org>; Wed, 19 Mar 2003 22:09:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2K3R4v02024
	for rmt-archive@odin.ietf.org; Wed, 19 Mar 2003 22:27:04 -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 h2K3R3O02021
	for <rmt-web-archive@optimus.ietf.org>; Wed, 19 Mar 2003 22:27:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21834
	for <rmt-web-archive@ietf.org>; Wed, 19 Mar 2003 22:08:53 -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 h2K3QRO01993;
	Wed, 19 Mar 2003 22:26: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 h2K3PNO01963
	for <rmt@optimus.ietf.org>; Wed, 19 Mar 2003 22:25:23 -0500
Received: from scandium.dolby.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA21814
	for <Rmt@ietf.org>; Wed, 19 Mar 2003 22:07:12 -0500 (EST)
Received: from platinum.dolby.net ([172.16.33.28]) by 192.168.16.253 with InterScan Messaging Security Suite; Wed, 19 Mar 2003 19:09:25 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Rmt] small group replication service, application-level mult	icast etc.
Date: Wed, 19 Mar 2003 19:09:26 -0800
Message-ID: <5FCCC03CAF7C5C4C8E2F995E3D72E13301418CC6@platinum.dolby.net>
Thread-Topic: [Rmt] small group replication service, application-level mult	icast etc.
Thread-Index: AcLuhhS7CK5ZhK/sSsGrYkaffl71QgAB+/KA
From: "Bauer, Claus" <cb@dolby.com>
To: "Rick Boivie" <rhboivie@us.ibm.com>, <Rmt@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2K3PNO01964
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


Should we maybe get together a list of the AML approaches we think about ?

-----Original Message-----
From: Rick Boivie [mailto:rhboivie@us.ibm.com]
Sent: Wednesday, March 19, 2003 5:47 PM
To: sjkoh@etri.re.kr
Cc: justin@chapweske.com; floyd@icir.org; rmt@ietf.org
Subject: Re: [Rmt] small group replication service, application-level
mult icast etc.






> An ideal approach, I think, will be to combine those two, Xcast and ALM,
>more effectively, so that only good features of them can be drawn.

Seok.  This sounds right.  And this is what I think we were trying to
define
with the small group replication service.
Rick Boivie

_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt

This message (including any attachments) may contain confidential information intended for a specific individual and purpose. If you are not the intended recipient, delete this message. If you are not the intended recipient, disclosing, copying, distributing, or taking any action based on this message is strictly prohibited.
_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From mailnull@www1.ietf.org  Thu Mar 20 03:14:16 2003
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 DAA11311
	for <rmt-archive@odin.ietf.org>; Thu, 20 Mar 2003 03:14:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2K8VuL00889
	for rmt-archive@odin.ietf.org; Thu, 20 Mar 2003 03:31:56 -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 h2K8VUO00848
	for <rmt-web-archive@optimus.ietf.org>; Thu, 20 Mar 2003 03:31:30 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11279
	for <rmt-web-archive@ietf.org>; Thu, 20 Mar 2003 03:12:14 -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 h2K8UAO00774;
	Thu, 20 Mar 2003 03:30:10 -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 h2K8QtO00672
	for <rmt@optimus.ietf.org>; Thu, 20 Mar 2003 03:26:56 -0500
Received: from fgwmail6.fujitsu.co.jp (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11224
	for <rmt@ietf.org>; Thu, 20 Mar 2003 03:08:18 -0500 (EST)
Received: from m6.gw.fujitsu.co.jp ([10.0.50.76]) by fgwmail6.fujitsu.co.jp (8.12.8/Fujitsu Gateway)
	id h2K8AEfv005911; Thu, 20 Mar 2003 17:10:14 +0900
	(envelope-from kimai@labs.fujitsu.com)
Received: from n9.gw.fujitsu.co.jp by m6.gw.fujitsu.co.jp (8.12.8/Fujitsu Domain Master)
	id h2K84BS3007171; Thu, 20 Mar 2003 17:10:14 +0900
	(envelope-from kimai@labs.fujitsu.com)
Received: from guardian.kawasaki.flab.fujitsu.co.jp ([10.0.50.61])
 by n9.gw.fujitsu.co.jp (SAVSMTP 3.0.0.44) with SMTP id M2003032017101314325
 ; Thu, 20 Mar 2003 17:10:13 +0900
Received: from localhost (localhost [127.0.0.1])
	by guardian.kawasaki.flab.fujitsu.co.jp (8.11.6/8.11.6) with ESMTP id h2K8KH814707;
	Thu, 20 Mar 2003 17:20:17 +0900 (JST)
	(envelope-from kimai@labs.fujitsu.com)
To: justin@chapweske.com
Cc: rhboivie@us.ibm.com, floyd@icir.org, rmt@ietf.org
Subject: Re: [Rmt] small group replication service, application-level
 multicast etc.
In-Reply-To: <3E78C52B.1050505@chapweske.com>
References: <OFA0A5687F.26B339AE-ON85256CEE.0068399D@us.ibm.com>
	<3E78C52B.1050505@chapweske.com>
X-Mailer: Mew version 1.94.2 on XEmacs 21.1 (Cuyahoga Valley)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20030320172016L.kimai@labs.fujitsu.com>
Date: Thu, 20 Mar 2003 17:20:16 +0900
From: IMAI Yuji <kimai@labs.fujitsu.com>
X-Dispatcher: imput version 20000228(IM140)
Lines: 62
Content-Transfer-Encoding: 7bit
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Justin,

  Reading the article you pointed out, your P2P mechanism
  is very clever system to copy a immutable file from peer to
  peer. If one peer that provide some part of copy but have not
  enough up-link bandwidth to deliver, request side peer look for
  other peers who connect via broader up-link and can deliver
  more while receiving from first one. And to compile several
  part from several node, FEC is used.

  Is my understanding correct?

  It is very interesting idea because popular file will be
  duplicated on many hosts broadly on the Internet already,
  requester can ask several peers to send different part of
  files while encoding FEC.

  But your system seems to be focused on the goal different from
  ours. For real time datagram exchanging like VoIP and video
  meeting, source of original is only one node and it is not
  difficult, I think nearly impossible, for the listeners to
  require other several nodes to relay each part of real time
  streaming data depending of various unsettled bandwidth
  situation.

  For me, this looks the example of "There is no one-fits-all
  multicast transport protocol."
----
Yuji

From: Justin Chapweske <justin@chapweske.com>
Subject: Re: [Rmt] small group replication service, application-level multicast etc.
Date: Wed, 19 Mar 2003 13:29:47 -0600

> >>Actually, the Swarmcast system that we developed in late 1999 utilized
> >>Forward Error Correction combined with peer-to-peer (end-system)
> >>multicast to overcome the first-mile bottleneck in systems like this.
> >>
> >>I'd be happy to discuss this approach off-line with anyone that is
> >>interested.
> >>
> > 
> > 
> > Justin,  Thanks.  Can you provide a reference?
> > Rick
> 
> Swarmcast was a commercial endeavor, so no papers were published on it.
> 
> An old article at 
> (http://www.openp2p.com/pub/a/p2p/2001/05/24/swarmcast_beta.html) 
> provides an overview of the system and I'd be happy to answer any 
> questions about it off-line.
> 
> -- 
> Justin Chapweske, Onion Networks
> http://onionnetworks.com/
> 
> _______________________________________________
> Rmt mailing list
> Rmt@ietf.org
> https://www1.ietf.org/mailman/listinfo/rmt
> 
_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From mailnull@www1.ietf.org  Thu Mar 20 11:47:30 2003
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 LAA24173
	for <rmt-archive@odin.ietf.org>; Thu, 20 Mar 2003 11:47:30 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2KH5Rd04475
	for rmt-archive@odin.ietf.org; Thu, 20 Mar 2003 12:05: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 h2KH5RO04472
	for <rmt-web-archive@optimus.ietf.org>; Thu, 20 Mar 2003 12:05:27 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24142
	for <rmt-web-archive@ietf.org>; Thu, 20 Mar 2003 11:46:59 -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 h2KH50O04433;
	Thu, 20 Mar 2003 12:05:00 -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 h2KGxNO04095
	for <rmt@optimus.ietf.org>; Thu, 20 Mar 2003 11:59:23 -0500
Received: from hotmail.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24019
	for <Rmt@ietf.org>; Thu, 20 Mar 2003 11:40:55 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Thu, 20 Mar 2003 08:43:11 -0800
Received: from 130.129.133.232 by oe65.law12.hotmail.com with DAV;
	Thu, 20 Mar 2003 16:43:11 +0000
X-Originating-IP: [130.129.133.232]
X-Originating-Email: [korykang@hotmail.com]
From: "Kyungran Kang" <korykang@hotmail.com>
To: "Bauer, Claus" <cb@dolby.com>, "Rick Boivie" <rhboivie@us.ibm.com>
Cc: <Rmt@ietf.org>
References: <5FCCC03CAF7C5C4C8E2F995E3D72E13301418CC6@platinum.dolby.net>
Subject: Re: [Rmt] small group replication service, application-level mult	icast etc.
Date: Fri, 21 Mar 2003 01:41:32 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Message-ID: <OE65l6frSHnlLMEndfw00009728@hotmail.com>
X-OriginalArrivalTime: 20 Mar 2003 16:43:11.0322 (UTC) FILETIME=[CB369BA0:01C2EEFF]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id h2KGxOO04096
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

The list of technical papers that deal with application level multicast is available at
http://snow.icu.ac.kr/~korykang/refs/overlay.html.
I think that it can be a good starting point if you are not familiar with ALM.

As Sally Floyd suggested, the problem defintion is the most important to devise a solution.

Kyungran Kang
korykang@icu.ac.kr


----- Original Message ----- 
From: "Bauer, Claus" <cb@dolby.com>
To: "Rick Boivie" <rhboivie@us.ibm.com>; <Rmt@ietf.org>
Sent: Thursday, March 20, 2003 12:09 PM
Subject: RE: [Rmt] small group replication service, application-level mult icast etc.


> 
> Should we maybe get together a list of the AML approaches we think about ?
> 
> -----Original Message-----
> From: Rick Boivie [mailto:rhboivie@us.ibm.com]
> Sent: Wednesday, March 19, 2003 5:47 PM
> To: sjkoh@etri.re.kr
> Cc: justin@chapweske.com; floyd@icir.org; rmt@ietf.org
> Subject: Re: [Rmt] small group replication service, application-level
> mult icast etc.
> 
> 
> 
> 
> 
> 
> > An ideal approach, I think, will be to combine those two, Xcast and ALM,
> >more effectively, so that only good features of them can be drawn.
> 
> Seok.  This sounds right.  And this is what I think we were trying to
> define
> with the small group replication service.
> Rick Boivie
> 
> _______________________________________________
> Rmt mailing list
> Rmt@ietf.org
> https://www1.ietf.org/mailman/listinfo/rmt
> 
> This message (including any attachments) may contain confidential information intended for a specific individual and purpose. If you are not the intended recipient, delete this message. If you are not the intended recipient, disclosing, copying, distributing, or taking any action based on this message is strictly prohibited.
> _______________________________________________
> Rmt mailing list
> Rmt@ietf.org
> https://www1.ietf.org/mailman/listinfo/rmt
> 
_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From mailnull@www1.ietf.org  Thu Mar 20 12:15:49 2003
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 MAA25597
	for <rmt-archive@odin.ietf.org>; Thu, 20 Mar 2003 12:15:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2KHXke07687
	for rmt-archive@odin.ietf.org; Thu, 20 Mar 2003 12:33:46 -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 h2KHXkO07684
	for <rmt-web-archive@optimus.ietf.org>; Thu, 20 Mar 2003 12:33:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25574
	for <rmt-web-archive@ietf.org>; Thu, 20 Mar 2003 12:15:17 -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 h2KHX9O07629;
	Thu, 20 Mar 2003 12:33:09 -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 h2KHWqO07605
	for <rmt@optimus.ietf.org>; Thu, 20 Mar 2003 12:32:52 -0500
Received: from e35.co.us.ibm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25538
	for <Rmt@ietf.org>; Thu, 20 Mar 2003 12:14:23 -0500 (EST)
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11])
	by e35.co.us.ibm.com (8.12.8/8.12.2) with ESMTP id h2KHGYgJ062894;
	Thu, 20 Mar 2003 12:16:34 -0500
Received: from d03nm690.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.193.82])
	by westrelay02.boulder.ibm.com (8.12.8/NCO/VER6.5) with ESMTP id h2KHGXEc030876;
	Thu, 20 Mar 2003 10:16:33 -0700
Importance: Normal
Subject: Re: [Rmt] small group replication service, application-level mult	icast etc.
To: "Kyungran Kang" <korykang@hotmail.com>
Cc: <Rmt@ietf.org>
X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000
Message-ID: <OF3106DB8B.A685A7EB-ON85256CEF.005E1E85@us.ibm.com>
From: Rick Boivie <rhboivie@us.ibm.com>
Date: Thu, 20 Mar 2003 12:16:31 -0500
X-MIMETrack: Serialize by Router on D03NM690/03/M/IBM(Release 6.0 [IBM]|December 16, 2002) at
 03/20/2003 10:16:33
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=subscribe>





As I mentioned the other day,  I'd like to solve the problem of limited
bandwidth in the first mile and provide a scalable solution for
applications like VoIP conferencing, videoconferencing and e-meetings in
which there are likely to be very large numbers of not-very-large groups.

Does that sound like a reasonable problem definition to everybody?

Rick Boivie





"Kyungran Kang" <korykang@hotmail.com> on 03/20/2003 11:41:32 AM

To:    "Bauer, Claus" <cb@dolby.com>, Rick Boivie/Hawthorne/IBM@IBMUS
cc:    <Rmt@ietf.org>
Subject:    Re: [Rmt] small group replication service, application-level
       mult icast etc.



The list of technical papers that deal with application level multicast is
available at
http://snow.icu.ac.kr/~korykang/refs/overlay.html.
I think that it can be a good starting point if you are not familiar with
ALM.

As Sally Floyd suggested, the problem defintion is the most important to
devise a solution.

Kyungran Kang
korykang@icu.ac.kr


----- Original Message -----
From: "Bauer, Claus" <cb@dolby.com>
To: "Rick Boivie" <rhboivie@us.ibm.com>; <Rmt@ietf.org>
Sent: Thursday, March 20, 2003 12:09 PM
Subject: RE: [Rmt] small group replication service, application-level mult
icast etc.


>
> Should we maybe get together a list of the AML approaches we think about
?
>
> -----Original Message-----
> From: Rick Boivie [mailto:rhboivie@us.ibm.com]
> Sent: Wednesday, March 19, 2003 5:47 PM
> To: sjkoh@etri.re.kr
> Cc: justin@chapweske.com; floyd@icir.org; rmt@ietf.org
> Subject: Re: [Rmt] small group replication service, application-level
> mult icast etc.
>
>
>
>
>
>
> > An ideal approach, I think, will be to combine those two, Xcast and
ALM,
> >more effectively, so that only good features of them can be drawn.
>
> Seok.  This sounds right.  And this is what I think we were trying to
> define
> with the small group replication service.
> Rick Boivie
>
> _______________________________________________
> Rmt mailing list
> Rmt@ietf.org
> https://www1.ietf.org/mailman/listinfo/rmt
>
> This message (including any attachments) may contain confidential
information intended for a specific individual and purpose. If you are not
the intended recipient, delete this message. If you are not the intended
recipient, disclosing, copying, distributing, or taking any action based on
this message is strictly prohibited.
> _______________________________________________
> Rmt mailing list
> Rmt@ietf.org
> https://www1.ietf.org/mailman/listinfo/rmt
 >


_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From mailnull@www1.ietf.org  Thu Mar 20 12:45:27 2003
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 MAA26868
	for <rmt-archive@odin.ietf.org>; Thu, 20 Mar 2003 12:45:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2KI3O510017
	for rmt-archive@odin.ietf.org; Thu, 20 Mar 2003 13:03:24 -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 h2KI3OO10014
	for <rmt-web-archive@optimus.ietf.org>; Thu, 20 Mar 2003 13:03:24 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26839
	for <rmt-web-archive@ietf.org>; Thu, 20 Mar 2003 12:44:55 -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 h2KI18O09890;
	Thu, 20 Mar 2003 13:01:08 -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 h2KHxeO09683
	for <rmt@optimus.ietf.org>; Thu, 20 Mar 2003 12:59:40 -0500
Received: from open-content.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA26705
	for <rmt@ietf.org>; Thu, 20 Mar 2003 12:41:11 -0500 (EST)
Received: (qmail 7666 invoked from network); 21 Mar 2003 06:45:37 -0000
Received: from c-24-118-168-169.mn.client2.attbi.com (HELO chapweske.com) (24.118.168.169)
  by onionnetworks.com with SMTP; 21 Mar 2003 06:45:37 -0000
Message-ID: <3E79FDBE.8010602@chapweske.com>
Date: Thu, 20 Mar 2003 11:43:26 -0600
From: Justin Chapweske <justin@chapweske.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IMAI Yuji <kimai@labs.fujitsu.com>, rmt@ietf.org
Subject: Re: [Rmt] small group replication service, application-level multicast
 etc.
References: <OFA0A5687F.26B339AE-ON85256CEE.0068399D@us.ibm.com>	<3E78C52B.1050505@chapweske.com> <20030320172016L.kimai@labs.fujitsu.com>
In-Reply-To: <20030320172016L.kimai@labs.fujitsu.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> 
>   But your system seems to be focused on the goal different from
>   ours. For real time datagram exchanging like VoIP and video
>   meeting, source of original is only one node and it is not
>   difficult, I think nearly impossible, for the listeners to
>   require other several nodes to relay each part of real time
>   streaming data depending of various unsettled bandwidth
>   situation.

While Swarmcast-like systems are optimized for static content 
distribution, they can certainly be applied to near-realtime delivery as 
well.

The tradeoff of using something like Swarmcast is that by encoding data, 
and delivering data out-of-order from multiple locations, you increase 
the latency of the communication.

So, for a near-live broadcast, you can easily buffer up 30 seconds of 
audio/video of data, and encode/interleave that chunk data swarming 
technologies.  So while the individual packets of the feed will be 
delivered out-of-order and from multiple sources in parallel, the 
overall feed can be reconstructed in its original sequential form.

So, while this approach obviously wouldn't work for a conference call 
VoIP application where latency is very critical, it might work well for 
a near-live news or sports broadcast where latency can be traded off for 
better performance and reliability.

>   For me, this looks the example of "There is no one-fits-all
>   multicast transport protocol."

So true.

-- 
Justin Chapweske, Onion Networks
http://onionnetworks.com/

_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From mailnull@www1.ietf.org  Thu Mar 20 19:01:52 2003
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 TAA14768
	for <rmt-archive@odin.ietf.org>; Thu, 20 Mar 2003 19:01:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2L0Jwv10308
	for rmt-archive@odin.ietf.org; Thu, 20 Mar 2003 19:19:58 -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 h2L0JwO10305
	for <rmt-web-archive@optimus.ietf.org>; Thu, 20 Mar 2003 19:19:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14736
	for <rmt-web-archive@ietf.org>; Thu, 20 Mar 2003 19:01:21 -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 h2L0JLO10280;
	Thu, 20 Mar 2003 19:19: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 h2L0G6O10185
	for <rmt@optimus.ietf.org>; Thu, 20 Mar 2003 19:16:06 -0500
Received: from e31.co.us.ibm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14684
	for <rmt@ietf.org>; Thu, 20 Mar 2003 18:57:29 -0500 (EST)
Received: from westrelay04.boulder.ibm.com (westrelay04.boulder.ibm.com [9.17.193.32])
	by e31.co.us.ibm.com (8.12.8/8.12.2) with ESMTP id h2KNxFWO067160;
	Thu, 20 Mar 2003 18:59:15 -0500
Received: from d03nm690.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.193.82])
	by westrelay04.boulder.ibm.com (8.12.8/NCO/VER6.5) with ESMTP id h2KNxasf232068;
	Thu, 20 Mar 2003 16:59:37 -0700
Importance: Normal
Subject: Re: [Rmt] small group replication service, application-level multicast etc.
To: Justin Chapweske <justin@chapweske.com>
Cc: IMAI Yuji <kimai@labs.fujitsu.com>, rmt@ietf.org
X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000
Message-ID: <OF6BAFCE1C.8C2596A2-ON85256CEF.0083A7AC@us.ibm.com>
From: Rick Boivie <rhboivie@us.ibm.com>
Date: Thu, 20 Mar 2003 18:59:34 -0500
X-MIMETrack: Serialize by Router on D03NM690/03/M/IBM(Release 6.0 [IBM]|December 16, 2002) at
 03/20/2003 16:59:36
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=subscribe>






Justin>So, while this approach obviously wouldn't work for a conference
call
Justin>VoIP application where latency is very critical, it might work well
for
Justin>a near-live news or sports broadcast where latency can be traded off
for
Justin>better performance and reliability.
Justin>

Yuji>>   For me, this looks the example of "There is no one-fits-all
Yuji>>   multicast transport protocol."

Justin>
Justin>So true.

Agreed.

_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From mailnull@www1.ietf.org  Fri Mar 21 14:25:24 2003
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 OAA23632
	for <rmt-archive@odin.ietf.org>; Fri, 21 Mar 2003 14:25:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2LJhsP31910
	for rmt-archive@odin.ietf.org; Fri, 21 Mar 2003 14:43:54 -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 h2LJhrO31907
	for <rmt-web-archive@optimus.ietf.org>; Fri, 21 Mar 2003 14:43:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23602
	for <rmt-web-archive@ietf.org>; Fri, 21 Mar 2003 14:24:53 -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 h2LJhXO31888;
	Fri, 21 Mar 2003 14:43:33 -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 h2LJd7O31669
	for <rmt@optimus.ietf.org>; Fri, 21 Mar 2003 14:39:07 -0500
Received: from sj-core-2.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23479
	for <rmt@ietf.org>; Fri, 21 Mar 2003 14:20:07 -0500 (EST)
Received: from cisco.com (cypher.cisco.com [171.69.11.143])
	by sj-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h2LJMMmU016586
	for <rmt@ietf.org>; Fri, 21 Mar 2003 11:22:23 -0800 (PST)
Received: (from lorenzo@localhost)
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id LAA26375
	for rmt@ietf.org; Fri, 21 Mar 2003 11:22:22 -0800 (PST)
Date: Fri, 21 Mar 2003 11:22:22 -0800
From: Lorenzo Vicisano <lorenzo@cisco.com>
To: rmt@ietf.org
Message-ID: <20030321112222.G22460@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.23i
Subject: [Rmt] presentation material submission
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=subscribe>

just a reminder for the presenters at Monday's meeting.
Please submit your slides to minutes@ietf.org

please check http://www.ietf.org/instructions/slides.html
for more infos.

	thank you,
	Lorenzo
_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From mailnull@www1.ietf.org  Fri Mar 28 19:44:37 2003
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 TAA26866
	for <rmt-archive@odin.ietf.org>; Fri, 28 Mar 2003 19:44:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2T16ba23055
	for rmt-archive@odin.ietf.org; Fri, 28 Mar 2003 20:06:37 -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 h2T16bO23052
	for <rmt-web-archive@optimus.ietf.org>; Fri, 28 Mar 2003 20:06:37 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26857
	for <rmt-web-archive@ietf.org>; Fri, 28 Mar 2003 19:44:06 -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 h2T15wO23033;
	Fri, 28 Mar 2003 20:05:58 -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 h2T12hO22959
	for <rmt@optimus.ietf.org>; Fri, 28 Mar 2003 20:02:43 -0500
Received: from sj-core-2.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26813;
	Fri, 28 Mar 2003 19:40:12 -0500 (EST)
Received: from cisco.com (cypher.cisco.com [171.69.11.143])
	by sj-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h2T0fW9a007118;
	Fri, 28 Mar 2003 16:41:58 -0800 (PST)
Received: (from lorenzo@localhost)
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id QAA12816;
	Fri, 28 Mar 2003 16:41:32 -0800 (PST)
Date: Fri, 28 Mar 2003 16:41:32 -0800
From: Lorenzo Vicisano <lorenzo@cisco.com>
To: minutes@ietf.org
Cc: rmt@ietf.org
Message-ID: <20030328164132.J19293@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.23i
Subject: [Rmt] IETF56: RMT WG meeting minutes
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=subscribe>

please find attached the minutes of the RMT WG meeting.

	thank you,
	Lorenzo Vicisano

###############################################################################

RMT WG Meeting, 56th IETF - San Francisco
Mon, March 17, 1530-1730

Many thanks to Marshall Eubanks for taking minutes.

Agenda:

 - New Charter discussion                                      Lorenzo Vicisano
 - NORM BB and PI updates                                      Brian Adamson
	draft-ietf-rmt-bb-norm-05.txt
	draft-ietf-rmt-pi-norm-06.txt
 - New "compact" scheme FEC BB                                 Mike Luby
	draft-ietf-rmt-bb-fec-supp-inband-00.txt
 - New FDALC draft                                             Toni Paila
	draft-paila-rmt-fdalc-00.txt
 - Kick off of the "Small Group Replication Service" subgroup  Rick Boivie

Please see slides for the new charter.
The main feedback on the new charter were:
  - delay the Milestone for TFMCC Experimental submission 
  - it was noted that GRA had been removed from the milestone due to
    perceived lack of resource and interest. It was decided to try and
    and find new resources to work on this. Tom Pusateri to
    investigate on this with the help of Brian Adamson and in
    coordination with the existing GRA authors. Tom to report on this
    in a timely fashion.
  - more comments on the "small-replication service" later in this
    report.

Brian Adamson on NORM BB and PI. Please see slides.
Brian felt that the "implementability" status of NORM is good as long
as both BB and PI are used.

The WG was *strongly encouraged* to provide feedback on these two
documents, soon to be pushed forward.

Mike Luby - ALC updates. Please see slides.
Mike is still waiting for WEBRC BB to be submitted for publication.

Mike Luby on new compact FEC BB. please see slides.

Toni Paila on New FDALC draft. Please see slides.
This is not a working group item yet. The WG decided that this
was to become a WG item as a good completion of ALC. No need
for changes in charter as this is only a completion of ALC.

Rick Boivie presented on Small group replication service. Please
sees slides.

Long discussion followed on whether this work was pertinent to RMT and
on whether this problem had been faced/resolved elsewhere in the
transport or application areas. Many objected that this work did not
belong in RMT. Other suggested possible alternatives, for example
the peer-to-peer research group.

The consensus seemed to be that a BOF is needed, maybe a "end-system
multicast" BOF.

###############################################################################
_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



