From owner-rmt@listserv.lbl.gov  Wed Nov  1 22:26:08 2000
Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA26209
	for <rmt-archive@odin.ietf.org>; Wed, 1 Nov 2000 22:26:08 -0500 (EST)
Received: (from majordom@localhost)
	by listserv.lbl.gov (8.9.3/8.9.3) id SAA08295;
	Wed, 1 Nov 2000 18:20:41 -0800 (PST)
X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f
Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id SAA08291
	for <rmt@listserv.lbl.gov>; Wed, 1 Nov 2000 18:20:39 -0800 (PST)
Received: from SpamWall.lbl.gov (localhost [127.0.0.1])
	by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id SAA06064
	for <rmt@listserv.lbl.gov>; Wed, 1 Nov 2000 18:20:38 -0800 (PST)
Received: from ftpbox.mot.com (ftpbox.mot.com [129.188.136.101])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id SAA06055
	for <rmt@lbl.gov>; Wed, 1 Nov 2000 18:20:38 -0800 (PST)
Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) by ftpbox.mot.com (ftpbox 2.1) with ESMTP id TAA10763 for <rmt@lbl.gov>; Wed, 1 Nov 2000 19:20:37 -0700 (MST)]
Received: [from homer.arc.corp.mot.com (homer.arc.corp.mot.com [217.1.10.38]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id TAA18637 for <rmt@lbl.gov>; Wed, 1 Nov 2000 19:20:35 -0700 (MST)]
Received: from motorola.com (mccoy.arc.corp.mot.com [217.1.10.204])
	by homer.arc.corp.mot.com (8.10.2/8.10.2) with ESMTP id eA22K1S16856
	for <rmt@lbl.gov>; Thu, 2 Nov 2000 13:20:01 +1100 (EST)
Message-ID: <3A00CEE7.DB675A83@motorola.com>
Date: Thu, 02 Nov 2000 13:18:15 +1100
From: Roger Kermode <Roger.Kermode@motorola.com>
Reply-To: Roger.Kermode@motorola.com
Organization: Motorola
X-Mailer: Mozilla 4.73 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: rmt-list <rmt@lbl.gov>
Subject: Announcment: multicast security BOF at San Diego IETF
Content-Type: multipart/mixed;
 boundary="------------608BAF969F4A519981D5B3B0"
Sender: owner-rmt@lbl.gov
Precedence: bulk

This is a multi-part message in MIME format.
--------------608BAF969F4A519981D5B3B0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Dear everyone,

the chairs of the IRTF Secure Multicast Research Group will
be holding a BoF on Secure Multicast at the next IETF.
Please take a moment to read the announcement below
if you're so interested,

cheers,

Roger

---------------------------------------------------------------------------

Multicast Security BOF (msec)

Tuesday, December 12 at 1415-1515
Tuesday, December 12 at 1700-1800
=================================

CHAIR: Ran Canetti <canetti@watson.ibm.com>
        Thomas Hardjono <hardjono@nortelnetworks.com>

DESCRIPTION:

There is significant interest in the networking industry and content
delivery network industry to use IP multicast a vehicle for data
delivery to a large audience.  One major hindrance to the successful
deployment of IP multicast and other group-oriented communication
protocols has been the lack of security for both the content and the
content-delivery infrastructure. In particular, there has been
increasing demand for secure solutions for the 1-to-Many type of
group communications, as exemplified by the interest of the cable
television sector in using the Internet for content distribution and
by the recent emergence of the single-source paradigm in IP
multicasting.

To this end, the Secure Multicast (SMuG) research group was formed in
1998 under the umbrella of the IRTF. That group has characterized the
security concerns and problem areas, has come up with a framework for
an overall solution, and has developed protocols for solving much of
the problem space in a satisfactory manner. Several of these protocols
have reached the needed maturity to be considered for standardization
at the IETF.

The proposed WG will further develop and standardize the protocols
developed at the SMuG RG. The focus will be on mature protocols that
are deployable in short term in today's internet. The SMuG RG will
continue to examine issues that need further research, delivering
protocols to MSEC when they are mature. In the immediate future
MSEC will focus on the 1-to-Many group communication, and will
address at least the following issues:

- Developing the transformations to be applied to the multicasted data.
   These transformations will provide at least the following
   functionalities:
   + Encryption of data using a group key available to all members.
   + Source and Data Authentications even when the data receivers
     do not trust each other.
   Both functionalities are required for content-authors and
   content-distributors. They represent an important element in the
   larger digital rights management area.

- Group Security Association and Key Management. Secure protocols are
   needed for management of cryptographic keys and Security Associations

   for groups. These include techniques for initial key dissemination,
   key updates and refreshments, and Group Security Association (Group
   SA) management.

Depending on the acceptance and stability of the above two issues, the
following issues will be addressed by the WG in the immediate future:

- Group Security Policies. Different levels of policies exist for a
   group, covering a range from member behavior to cryptographic
policies.

- Secure group announcements.  Information regarding the existence of a
   group, its policies, base security mechanisms and methods for joining

   needs to be announced in a suitable manner.

Secure multicast touches upon the work of several other working groups.
The proposed WG will take care to coordinate its activities with the
relevant directorates (security, routing, transport) and especially
with the IPSec and RMT working groups.

The WG will not work on:
- Security issues at firewalls and NATs relating to multicast traffic.
- Protection against illegal re-distribution of multicasted data.


AGENDA:

10 mins - Agenda bashing

10 mins - Charter presentation

80 mins - Internet draft presentations:

   10 mins - Taxonomy of multicast security concerns
             (draft-irtf-smug-taxonomy-01.txt)
   10 mins - Framework overview (draft-irtf-smug-framework-01.txt)
             - Data transforms:
   10 mins     - Overall design (draft-irtf-smug-data-transforms-00.txt)

   10 mins     - Source authentication (draft-irtf-smug-tesla-00.txt)
             - Group key and SA management
   10 mins     - GKM Building Block
(draft-irtf-smug-gkmbb-gsadef-00.txt)
   10 mins     - GSAKMP (draft-harney-sparta-gsakmp-sec-02.txt)
   10 mins     - Group DOI for ISAKMP (draft-irtf-smug-gdoi-00.txt)
   10 mins - Group policy management (draft-mcast-pol-req00.txt)

20 mins - Open Discussion (work descriptions, objectives,
goals/milestones)


MAILING LIST

The mailing list is at msec-request@securemulticast.org (or email the
chairs).
The website is at www.securemulticast.org


READING MATERIAL
     draft-irtf-smug-taxonomy-02.txt
     draft-irtf-smug-framework-01.txt
     draft-irtf-smug-data-transforms-01.txt
     draft-irtf-smug-tesla-00.txt
     draft-irtf-smug-gkmbb-gsadef-00.txt
     draft-harney-sparta-gsakmp-sec-02.txt
     draft-irtf-smug-gdoi-00.txt
     draft-irtf-smug-pol-req00.txt
---------------------------------------------------------------------------

--------------608BAF969F4A519981D5B3B0
Content-Type: text/x-vcard; charset=us-ascii;
 name="Roger.Kermode.vcf"
Content-Description: Card for Roger Kermode
Content-Disposition: attachment;
 filename="Roger.Kermode.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Kermode;Roger
tel;cell:+61-408-212-284
tel;fax:+61-2-9666-0501
tel;home:+61-2-9664-8335
tel;work:+61-2-9666-0558
x-mozilla-html:FALSE
url:www.mot.com.au
org:Motorola Australian Research Centre;Communications and Networking Lab
version:2.1
email;internet:Roger.Kermode@motorola.com
title:Principal Research Engineer, Manager
adr;quoted-printable:;;Level 3,=0D=0A12 Lord St.;Botany;NSW;2019;Australia
fn:Roger Kermode
end:vcard

--------------608BAF969F4A519981D5B3B0--



From owner-rmt@listserv.lbl.gov  Fri Nov  3 19:45:01 2000
Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA15129
	for <rmt-archive@odin.ietf.org>; Fri, 3 Nov 2000 19:45:01 -0500 (EST)
Received: (from majordom@localhost)
	by listserv.lbl.gov (8.9.3/8.9.3) id PAA25494;
	Fri, 3 Nov 2000 15:57:44 -0800 (PST)
X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f
Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id PAA25490
	for <rmt@listserv.lbl.gov>; Fri, 3 Nov 2000 15:57:42 -0800 (PST)
From: hv@of-hachetal.de
Received: from SpamWall.lbl.gov (localhost [127.0.0.1])
	by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id PAA05337
	for <rmt@listserv.lbl.gov>; Fri, 3 Nov 2000 15:57:41 -0800 (PST)
Received: from mail.sinet.net.cn ([202.103.190.4])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id PAA05296
	for <rmt@lbl.gov>; Fri, 3 Nov 2000 15:57:34 -0800 (PST)
Received: from isd.com.cn ([202.103.148.117])
	by mail.sinet.net.cn (8.9.3/8.9.3) with SMTP id HAA12727;
	Sat, 4 Nov 2000 07:53:34 +0800 (CST)
Date: Sat, 4 Nov 2000 07:53:34 +0800 (CST)
Message-Id: <200011032353.HAA12727@mail.sinet.net.cn>
Received: from h809 ([63.30.197.239]) by isd.com.cn (Lotus SMTP MTA v4.6.1  (569.2 2-6-1998)) with SMTP id 4825698C.0082E7B4; Wed, 4 Nov 1970 07:51:14 +0800
To: hv@of-hachetal.de
Subject: At last, Herbal V, the all natural alternative to V----A!
Sender: owner-rmt@lbl.gov
Precedence: bulk


Herbal V: An Incredible All-Natural Healthy Alternative 


  Herbal V is the All Natural Approach to Male Virility,
  Vitality and Pleasure.



Available N o w ! 


Welcome to the New Sexual Revolution.

It's the all natural male potency and pleasure pill that men 
everywhere are buzzing about. Herbal V is safe, natural and
specifically formulated to help support male sexual function
and pleasure. You just take two easy-to-swallow tablets
one hour before sex. And there's more great news - you can
get Herbal V for less than $1 a pill.

Amazing word of mouth praise on Herbal V has been spreading 
like wildfire-already over 1,500,000 men  have chosen
Herbal V. Since it is 100% natural you will never have
to worry about safety. Try doctor-recommended Herbal V
today and have the greatest night of your life!


Herbal V... Bringing Back the Magic!


1,585,000 men can't be wrong. To date over 1 million men 
have tried the super supplement Herbal V.
Here is why: 

No Doctor Visit Required 
Available Over the Counter 
Not a Drug 
100% Natural 
Safe, No Worries 
Highest Quality Pharmaceutical-Grade Pure Nutriceuticals 
Guaranteed Potency & Purity 

Be a Real Man Again!

Questions and Answers

What is Herbal V?

Herbal V is a proprietary blend that was specifically
developed as a safe alternative for men who prefer
an all-natural approach to address impotence and boost
sexual performance. This amazing formula first became
popular with Hollywood insiders and the wealthy elite.
They were maximizing their sex lives, long before it 
was available to the general public. 

How does Herbal V work?

Developed by a team whose goal was to create the perfect 
all-natural aphrodisiac. Herbal V is the result of that
remarkable effort. The Herbal V formula contains a precise
blend of cutting edge pro-sexual nutrients from around
the world that provide nutritional support, making it
possible for a man to have a pleasurable sexual experience. 

What can Herbal V do for me?

Herbal V helps support male sexual function and 
pleasure in a safe and natural manner. Simply put, 
it can make your sex life incredible. 

Is Herbal V Safe?

One of the great things about Herbal V is that it is
not a drug. It is an incredible herbal dietary supplement
that provides nutritional support for male sexual function
and pleasure. One of the most comforting features of
Herbal V is that you never have to worry about safety. 

Herbal V: Safe - Natural - Exciting

Many have speculated that because Herbal V is so
popular with men, it must contain prescription drugs
or chemical components. Herbal V does not contain any 
elements or traces of any prescription drug. Herbal V 
is made using the world's most technologically advanced
state-of-the-art cold processing equipment to ensure
maximum purity. Herbal V has been independently analyzed
by the nation's premier testing facility to ensure purity,
quality and to end the rumors that, because it is so
popular, it must somehow be chemical. It is not.
Herbal V is natural - just as it says on the label.
Herbal V is simply fantastic! 

Herbal V: Ingredients

Yohimbe, saw palmetto, avena sativa, androstenedione,
guarana, taurine, siberian ginseng, tribulus terrestris. 
Tribulus Terrestis is certified to enhanced testosterone
levels by increasing Luteinzing hormone (LH) levels. 
Androstenedione which is a precursor to testosterone
unlocks bound testosterone and makes it biologically
active again quickly. This means a dramatic surge in 
desire. Avena Sativa Stimulates the neurotransmitter 
pleasure centers to maximum capacity. This greatly
intensifies pleasure.

Just listen to what Herbal V has done for the sex lives
of people like you!

On a scale of 1 to 10, it's a 15. Electrifying. It's like 
a wonder pill! 
 Justin Q B., New Haven, Texas

I haven't had sexual relations in 11 years. Then with 
Herbal V it was... wow! It works again! 
 Sid R., Lakeland, Florida

I had sex four times in one night. It made me feel
like a 19-year-old again. 
 Chip S, Beech Mountain, North Carolina

Herbal V has turned my husband into a Sexual Superman! 
I like the fact that it's all natural and has no
side effects. It's bringing back the good old days. 
 Jennifer B, Beverly Hills, California 

The above testimonials are from product literature, 
and we have not independently verified them.
However, the following testimonial is from a "senior"
gentleman who has purchased his second bottle of
Herbal V. When we heard his words with our own ears,
we asked his permission to print them here. 

 Man! I'm wild as I can be! I feel like I'm 25 years old again! 
I'm not believing this! 
                           Mr. Murphy, age 64, Lampart, IL.



Risk Free: Double Your Money Back Guarantee

If Herbal V does not give the desired results as stated
above, simply return the unused portion for a
double-your money back refund. No questions asked ! 

Order Now: Safe, Fast, Secure, Private

Herbal V with its DOUBLE YOUR MONEY BACK GUARANTEE is
available only through this special promotional offer.
Herbal V arrives in plain packaging for your privacy.
Any and all information is kept strictly confidential.

Payment Methods

You may FAX or Postal Mail Checks, MasterCard, Visa,
& American Express.payments. Money Orders
are accepted only by Postal Mail. 


Each bottle of Herbal V contains 30 tablets, approximately
a 1 month supply.


Step 1: Place a check by your desired quanity.


______ 1 Bottle of Herbal V  $28


______ 2 Bottles of Herbal V $48


______ 3 Bottles of Herbal V $59


Please add $6 shipping and handling for any size order. 
[ Total cost including shipping & handling, 
1 bottle=$34, 2 bottles=$54, 3 bottles=$65 ]

International Orders
Please add $16 shipping and handling for any size order.
[ Total cost including shipping & handling,
1 bottle=$44, 2 bottles=$64, 3 bottles=$75 ]
We cannot accept foreign checks.
International money orders or credit cards only.

Step 2: Place a check by your desired payment method 
and complete fields if necessary.


_____Check or CHECK-BY-FAX [details below]


_____Money Order 


_____American Express 
Account Number__________________ Exp____/____

_____Visa
Account Number__________________ Exp____/____

_____MasterCard
Account Number__________________ Exp____/____


Please make your check or money order payable to
"Lion Sciences National".
 

Step 3: Please complete and print the following fields clearly.


Name ___________________________________________________ 


Address _________________________________________________


City ____________________________________________________ 


State ___________________________________________________ 


Zip _____________________________________________________ 


E-mail __________________________________________________ 


Signature _________________________________________________
[ required for check and credit card orders]



             Toll Free FAX Order Line: 1-800-940-6590
If faxing in your order, please state whether you require
a fax, email, or no confirmation at all. 
Allow up to one day for confirmation, if requested.
FAX orders are processed immediately.

  Or, print & mail to: LSN   
                       3502 N. Powerline Rd. #525 
                       Pompano Beach, FL 33069                


        ______________________________________________________


*CHECK BY FAX ORDERS: Complete the check as normal. Tape
the check in the area below. Below the check, clearly write
the check number, all numbers at the bottom of the check,
& your name. Tape the check below and fax the check to the
toll free FAX number above. Void the check. Our merchant
will electronically debit your account for the amount of 
the check; your reference number for this transaction will
be your check number. Nothing could be safer & easier !

                          TAPE CHECK BELOW















              _____________________________________________________________

This is a one time mailing: Removal is automatic and no further 
contact is necessary. Please Note: Herbal V is not intended to
diagnose, treat, cure or prevent any disease. As individuals differ,
so will results. Herbal V helps provide herbal and nutritional support
for male sexual performance. The FDA has not evaluated these 
statements. For details about our double your money back guarantee,
please write to the above address, attention consumer affairs 
department; enclose a self addressed stamped envelope for this and any 
requested contact information.
Thank You.


From owner-rmt@listserv.lbl.gov  Wed Nov  8 19:12:23 2000
Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA14209
	for <rmt-archive@odin.ietf.org>; Wed, 8 Nov 2000 19:12:22 -0500 (EST)
Received: (from majordom@localhost)
	by listserv.lbl.gov (8.9.3/8.9.3) id PAA18292;
	Wed, 8 Nov 2000 15:36:47 -0800 (PST)
X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f
Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id PAA18288
	for <rmt@listserv.lbl.gov>; Wed, 8 Nov 2000 15:36:45 -0800 (PST)
Received: from SpamWall.lbl.gov (localhost [127.0.0.1])
	by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id PAA28441
	for <rmt@listserv.lbl.gov>; Wed, 8 Nov 2000 15:36:44 -0800 (PST)
Received: from mailman.sprintlabs.com (mx.sprintlabs.com [208.30.174.2])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id PAA28435
	for <rmt@lbl.gov>; Wed, 8 Nov 2000 15:36:43 -0800 (PST)
Received: by mailman.sprintlabs.com with Internet Mail Service (5.5.2652.78)
	id <47VNGVPH>; Wed, 8 Nov 2000 15:36:40 -0800
Message-ID: <90B65CE19D3DD411895400805F0DAA7A0BDFF7@mailman.sprintlabs.com>
From: Christophe Diot <cdiot@sprintlabs.com>
To: NGC2000-PC <ngc2000-pc@sprintlabs.com>,
        "'Cost264@lip6.fr'"
	 <Cost264@lip6.fr>,
        "'rm@mash.CS.Berkeley.EDU'" <rm@mash.CS.Berkeley.EDU>,
        "'maddogs@ietf.org'" <maddogs@ietf.org>,
        "'ssm-interest@external.cisco.com'" <ssm-interest@external.cisco.com>,
        "'rmt@lbl.gov'" <rmt@lbl.gov>
Subject: NGC 2000 retransmission on SSM
Date: Wed, 8 Nov 2000 15:36:38 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain
Sender: owner-rmt@lbl.gov
Precedence: bulk

  8, November, 2000 

  Thanks to Sprint, Cisco, the University of Oregon, UC-Santa Barbara, and 
  Stanford University, NGC2000, the Second International Workshop on 
  Networked Group Communication is being multicast live from the Stanford 
  University Campus Nov. 8-10. The conference s being transmitted in 
  real-time via Source Specific Multicast. Sessions are only available by 
  SSM. For information on joining, see the University of Oregon Videolab 
  session page at:  http://videolab.uoregon.edu/cgi-bin/urd.cgi to join. 
  This is the first event to be retransmitted over SSM. 

  The conference is being held at Stanford University in Palo Alto, 
  California from November 8th to the 10th and the program can be found 
  at: http://www.cs.ucsb.edu/ngc2000/program/ 

  The aim of the Workshop is to allow researchers and practitioners to 
  present the design and implementation techniques for networked group 
  communication. The focus of the Workshop is strictly on multicast and 
  networked group communication. This Workshop is the second and only 
  international event in this area (first workshop was in Pisa, Italy, in 
  November 1999). 


From owner-rmt@listserv.lbl.gov  Sun Nov 12 11:48:34 2000
Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA22003
	for <rmt-archive@odin.ietf.org>; Sun, 12 Nov 2000 11:48:34 -0500 (EST)
Received: (from majordom@localhost)
	by listserv.lbl.gov (8.9.3/8.9.3) id HAA00959;
	Sun, 12 Nov 2000 07:59:51 -0800 (PST)
X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f
Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id HAA00955
	for <rmt@listserv.lbl.gov>; Sun, 12 Nov 2000 07:59:49 -0800 (PST)
Received: from SpamWall.lbl.gov (localhost [127.0.0.1])
	by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id HAA04060
	for <rmt@listserv.lbl.gov>; Sun, 12 Nov 2000 07:59:48 -0800 (PST)
Received: from davis.bandwiz.com ([212.150.220.34])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id HAA04057
	for <rmt@lbl.gov>; Sun, 12 Nov 2000 07:59:46 -0800 (PST)
Received: by davis.bandwiz.com with Internet Mail Service (5.5.2650.21)
	id <VTNHY8B6>; Sun, 12 Nov 2000 17:59:10 +0200
Message-ID: <E9DC428883F3D31180F900E081107FF204F1DF@davis.bandwiz.com>
From: Meir Feder <Meir@bandwiz.com>
To: "'rmt@lbl.gov'" <rmt@lbl.gov>,
        "'luby@digitalfountain.com'"
	 <luby@digitalfountain.com>
Cc: Doron Rajwan <Doron@bandwiz.com>, Nadav Shulman <Nadav@bandwiz.com>
Subject: Separating the MRCC from the ALC/FEC
Date: Sun, 12 Nov 2000 17:59:05 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-rmt@lbl.gov
Precedence: bulk


 Dear RMT-er's,

In response to the standardization effort of the RMT working group in the
drafts ALC-01 and MRCC-00, we feel that the ALC draft combines together the
FEC and the congestion control somewhat unnecessarily. Thus, we like to
suggest that the draft will maintain a clear separation of the functionality
between the MRCC and the ALC/FEC part.

We believe that the MRCC will prove itself as a working protocol for
multicast congestion control, that is important for interoperability and for
friendly network behavior. The FEC is the data (maybe the most natural data)
that is transferred via the MRCC transport. Thus, MRCC should essentially be
(and is) for the Transport layer (layer 4), while ALC/FEC should be for the
Application layer (layer 7).


The separation will give the following benefits:

1. MRCC will be able to deliver not only FEC packets but also, e.g., RTP
packets (for continuous real-time viewing). When the payload is ALC/FEC
packets, registering to more MRCC layers will provide a faster download.
When using RTP packets, it can provide higher quality streams, by using
successive refinement payload.

2. Since MRCC and ALC/FEC (implementing different communication layers) will
each have its own header, version number, header size field, extension
fields, and so on, modifications in one should not affect the other.

3. The long-term goal should be the implementation of MRCC at the kernel
level, like TCP today, in order to give true inter-operability, congestion
control, fairness, safety, robustness and so on. Applications will create
MRCC socket, possibly giving only (S,G), and start receiving packets at
varying rates. If MRCC is not implemented at the kernel, there is a danger
that we will see more aggressive MRCC implementations over time.

4. ALC/FEC packets should carry only application-related information, not
transport. Note that, then, the source of ALC/FEC packets can be payload of
MRCC protocol, disk files, caches, broadcast channels (when there is no need
for MRCC...) or any other source.


The separation is clear and simple. The header part of the ALC associated
with congestion control will be in the MRCC, while the ALC/FEC header will
have the code information. In general, in order to know if some information
should be in the header field of MRCC or ALC/FEC, one should ask the
following question: If a packet is cached to the disk, and re-transmitted
later, should it have the original value (ALC/FEC) or a new value (MRCC).
Thus, for example, the time extension mechanism should migrate to MRCC.


Meir Feder and Doron Rajwan
Bandwiz



From owner-rmt@listserv.lbl.gov  Sun Nov 12 14:30:05 2000
Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA13261
	for <rmt-archive@odin.ietf.org>; Sun, 12 Nov 2000 14:30:05 -0500 (EST)
Received: (from majordom@localhost)
	by listserv.lbl.gov (8.9.3/8.9.3) id LAA01115;
	Sun, 12 Nov 2000 11:02:05 -0800 (PST)
X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f
Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id LAA01111
	for <rmt@listserv.lbl.gov>; Sun, 12 Nov 2000 11:02:03 -0800 (PST)
Received: from SpamWall.lbl.gov (localhost [127.0.0.1])
	by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id LAA12365
	for <rmt@listserv.lbl.gov>; Sun, 12 Nov 2000 11:02:02 -0800 (PST)
Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id LAA12362
	for <rmt@lbl.gov>; Sun, 12 Nov 2000 11:02:00 -0800 (PST)
Received: (from luigi@localhost)
	by info.iet.unipi.it (8.9.3/8.9.3) id UAA06380;
	Sun, 12 Nov 2000 20:00:18 +0100 (CET)
	(envelope-from luigi)
From: Luigi Rizzo <luigi@info.iet.unipi.it>
Message-Id: <200011121900.UAA06380@info.iet.unipi.it>
Subject: Re: Separating the MRCC from the ALC/FEC
In-Reply-To: <E9DC428883F3D31180F900E081107FF204F1DF@davis.bandwiz.com> from
 Meir Feder at "Nov 12, 2000 05:59:05 pm"
To: Meir Feder <Meir@bandwiz.com>
Date: Sun, 12 Nov 2000 20:00:18 +0100 (CET)
CC: "'rmt@lbl.gov'" <rmt@lbl.gov>,
        "'luby@digitalfountain.com'" <luby@digitalfountain.com>,
        Doron Rajwan <Doron@bandwiz.com>, Nadav Shulman <Nadav@bandwiz.com>
X-Mailer: ELM [version 2.4ME+ PL61 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-rmt@lbl.gov
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

...
> drafts ALC-01 and MRCC-00, we feel that the ALC draft combines together the
> FEC and the congestion control somewhat unnecessarily. Thus, we like to

point well taken and in fact we are working on a revised version of
ALC draft mostly along the lines you suggest.

<PERSONAL OPINIONS FOLLOW>

In ALC-01 the MRCC info is already well separated from the ALC
header (the header field is opaque); it is true that ALC-01
still has some FEC-related header fields which do not belong there,
and we are revising the draft and move this info to the payload.

> 2. Since MRCC and ALC/FEC (implementing different communication layers) will
> each have its own header, version number, header size field, extension
> fields, and so on, modifications in one should not affect the other.

I am not too happy in using two different headers for MRCC (or whatever
cong. control protocol is going to be used) and ALC, as you seem to
suggest, as some form of cong.control is an integral part of ALC.

> 3. The long-term goal should be the implementation of MRCC at the kernel
> level, like TCP today, in order to give true inter-operability, congestion
...
> varying rates. If MRCC is not implemented at the kernel, there is a danger
> that we will see more aggressive MRCC implementations over time.

having a protocol implemented in kernel or user space is irrelevant for
most aspects, except perhaps overhead at source/receiver (which i
do not think is a concern here) and ease of deployment (and this is
a double-edged sword).

We can have bad (more aggressive, or buggy, or just initial) kernel
implementations of MRCC and be stuck with them for a long time
because people do not upgrade the OS (there are still IGMPv1 hosta
around). Or we can have good user-space implementations of MRCC
and stand the risk of people using "accelerators" which are more
aggressive than they should (same as it happens with TCP and various
companies offering modified stacks).

> The separation is clear and simple. The header part of the ALC associated
> with congestion control will be in the MRCC, while the ALC/FEC header will
> have the code information. In general, in order to know if some information
> should be in the header field of MRCC or ALC/FEC, one should ask the
> following question: If a packet is cached to the disk, and re-transmitted
> later, should it have the original value (ALC/FEC) or a new value (MRCC).
> Thus, for example, the time extension mechanism should migrate to MRCC.

I partly disagree with the example. CC controls the throughput ("slower",
"faster"), whereas the time extension mechanism operates at a higher
level ("I am not done yet"). It certainly does not belong to MRCC e.g. for
streaming video you do not need it ("sorry, the show is over!").
You might argue that it does not even belong to ALC/FEC, but the
thing is you have to info somewhere.

	cheers
	luigi rizzo
----------------------------------+-----------------------------------------
 Luigi RIZZO, luigi@iet.unipi.it  . ACIRI/ICSI (on leave from Univ. di Pisa)
 http://www.iet.unipi.it/~luigi/  . 1947 Center St, Berkeley CA 94704
 Phone (510) 666 2927             .
----------------------------------+-----------------------------------------


From owner-rmt@listserv.lbl.gov  Fri Nov 17 04:57:07 2000
Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA04445
	for <rmt-archive@odin.ietf.org>; Fri, 17 Nov 2000 04:57:07 -0500 (EST)
Received: (from majordom@localhost)
	by listserv.lbl.gov (8.9.3/8.9.3) id AAA23006;
	Fri, 17 Nov 2000 00:38:59 -0800 (PST)
X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f
Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id AAA23002
	for <rmt@listserv.lbl.gov>; Fri, 17 Nov 2000 00:38:57 -0800 (PST)
Received: from SpamWall.lbl.gov (localhost [127.0.0.1])
	by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id AAA01981
	for <rmt@listserv.lbl.gov>; Fri, 17 Nov 2000 00:38:57 -0800 (PST)
Received: from acm.cs.umn.edu (acm.cs.umn.edu [128.101.32.12])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id AAA01976
	for <rmt@lbl.gov>; Fri, 17 Nov 2000 00:38:56 -0800 (PST)
Received: from monopoly.cs.umn.edu (monopoly.cs.umn.edu [128.101.32.5])
	by acm.cs.umn.edu (8.11.1/8.11.0) with ESMTP id eAH8e6q09362
	for <rmt@lbl.gov>; Fri, 17 Nov 2000 02:40:06 -0600 (CST)
	(envelope-from orasis@acm.cs.umn.edu)
Received: (from orasis@localhost)
	by monopoly.cs.umn.edu (8.8.8/8.8.8) id CAA25368
	for rmt@lbl.gov; Fri, 17 Nov 2000 02:36:38 -0800 (PST)
Date: Fri, 17 Nov 2000 02:36:38 -0800 (PST)
Message-Id: <200011171036.CAA25368@monopoly.cs.umn.edu>
From: Justin Chapweske <orasis@acm.org>
To: rmt@lbl.gov
Subject: Java FEC Library & Java ALC
Sender: owner-rmt@lbl.gov
Precedence: bulk

Hello all, we have just released a Java library for FEC encoding,
decoding, and IO at http://www.sourceforge.net/projects/swarmcast/.  We
are committed to having the best Java FEC library out there, so we will be
constantly making minor improvements to this core package and would
greatly appreciate any feedback.  
	Next we will be doing an ALC/RLC implementation that will be
released under the LGPL.  We have not yet started on this and love to
collaborate with anyone else that has started or interested in such an
undertaking.

Release Notes for Java FEC v0.5

This software is a library for performing Forward Error Correction
(FEC) encoding, decoding, and IO in Java. 

1 Features

1. A SPI plugin architecture that allows any FEC code that has no inherent
  reception innefficiency to be plugged in. Preferences between different
  implementations can be expressed via a simple configuration file.

2. A pure Java port of Luigi Rizzo's wonderful C FEC package. The code
  for this port is quite solid and provides an acceptible 33/k MB/s
  performance on a 500mhz k6-2 for 8 bit codes. This is 4-5 times
  faster than the port done by Dan Rubenstein's group, which is to
  be expected as they were more focused on adding interesting 
  encoding/decoding features than speed.

3. A much improved version of Lorenzo Vicisano's JNI wrapper. The JNI
  calls now have a negligable overhead for a delightful 160/k MB/s
  on a 900mhz Athlon. If a native library for your platform is not
  available then it will fall back to the pure Java version.

4. A FEC I/O package that is optimized for decoding speed and low memory
  consumption.

5. For the license I've simply included Luigi's original copyright,
  so you can basically do whatever you want with this thing. But if
  you do use this thing, please let me know what I can do to make
  it better for you.

2 Future Work/Open Tasks

1. Implement different IO routines based on Jim Gemmel's very nicely
  written paper on FEC performance tuning.

2. Implement more codes (Please let me know if you know of any codes
  as I'll implement them myself if they are compelling enough)

3. Tune the 16 bit codes to create the minimum required matrices on
  demand, this will allow n values of up to 65536 to be feasible.

4. The shuffling proceedure causes some confusing behavior for decoding,
  this will be fixed asap.

5. Have the native implementation automatically deploy itself so that
  the user does not have to manually set up their library path.

-Justin



From owner-rmt@listserv.lbl.gov  Fri Nov 24 18:58:39 2000
Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA01412
	for <rmt-archive@odin.ietf.org>; Fri, 24 Nov 2000 18:58:38 -0500 (EST)
Received: (from majordom@localhost)
	by listserv.lbl.gov (8.9.3/8.9.3) id PAA23244;
	Fri, 24 Nov 2000 15:12:46 -0800 (PST)
X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f
Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id PAA23234
	for <rmt@listserv.lbl.gov>; Fri, 24 Nov 2000 15:12:43 -0800 (PST)
Received: from SpamWall.lbl.gov (localhost [127.0.0.1])
	by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id PAA15588
	for <rmt@listserv.lbl.gov>; Fri, 24 Nov 2000 15:12:43 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id PAA15582
	for <rmt@lbl.gov>; Fri, 24 Nov 2000 15:12:42 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21861;
	Fri, 24 Nov 2000 18:12:14 -0500 (EST)
Message-Id: <200011242312.SAA21861@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rmt@lbl.gov
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-rmt-bb-lct-00.txt
Date: Fri, 24 Nov 2000 18:12:13 -0500
Sender: owner-rmt@lbl.gov
Precedence: bulk

--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		: Layered Coding Transport: A massively scalable 
                          multicast protocol
	Author(s)	: M. Luby et al.
	Filename	: draft-ietf-rmt-bb-lct-00.txt
	Pages		: 28
	Date		: 22-Nov-00
	
This document describes Layered Coding Transport, a massively
scalable multicast protocol, hereafter referred to as LCT.

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

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-lct-00.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-lct-00.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:	<20001122150111.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rmt-bb-lct-00.txt

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

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

--OtherAccess--

--NextPart--




From owner-rmt@listserv.lbl.gov  Fri Nov 24 19:08:20 2000
Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA02669
	for <rmt-archive@odin.ietf.org>; Fri, 24 Nov 2000 19:08:19 -0500 (EST)
Received: (from majordom@localhost)
	by listserv.lbl.gov (8.9.3/8.9.3) id PAA23243;
	Fri, 24 Nov 2000 15:12:46 -0800 (PST)
X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f
Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id PAA23236
	for <rmt@listserv.lbl.gov>; Fri, 24 Nov 2000 15:12:43 -0800 (PST)
Received: from SpamWall.lbl.gov (localhost [127.0.0.1])
	by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id PAA15589
	for <rmt@listserv.lbl.gov>; Fri, 24 Nov 2000 15:12:43 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id PAA15583
	for <rmt@lbl.gov>; Fri, 24 Nov 2000 15:12:42 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21886;
	Fri, 24 Nov 2000 18:12:17 -0500 (EST)
Message-Id: <200011242312.SAA21886@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rmt@lbl.gov
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-rmt-bb-fec-02.txt
Date: Fri, 24 Nov 2000 18:12:17 -0500
Sender: owner-rmt@lbl.gov
Precedence: bulk

--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		: RMT BB Forward Error Correction Codes
	Author(s)	: M. Luby et al.
	Filename	: draft-ietf-rmt-bb-fec-02.txt
	Pages		: 12
	Date		: 22-Nov-00
	
This memo describes the abstract packet formats and IANA
registration procedures for use of Forward Error Correction
(FEC) codes within the context of reliable IP multicast
transport.  This memo should be read in conjunction with and
uses the terminology of the companion memo [1], which
describes the use of Forward Error Correction (FEC) codes
within the context of reliable IP multicast transport and
provides an introduction to some commonly used FEC codes.

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

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-fec-02.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-fec-02.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:	<20001122150120.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rmt-bb-fec-02.txt

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

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

--OtherAccess--

--NextPart--




From owner-rmt@listserv.lbl.gov  Fri Nov 24 19:15:47 2000
Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA03775
	for <rmt-archive@odin.ietf.org>; Fri, 24 Nov 2000 19:15:42 -0500 (EST)
Received: (from majordom@localhost)
	by listserv.lbl.gov (8.9.3/8.9.3) id PAA23282;
	Fri, 24 Nov 2000 15:28:09 -0800 (PST)
X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f
Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id PAA23278
	for <rmt@listserv.lbl.gov>; Fri, 24 Nov 2000 15:28:07 -0800 (PST)
Received: from SpamWall.lbl.gov (localhost [127.0.0.1])
	by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id PAA16822
	for <rmt@listserv.lbl.gov>; Fri, 24 Nov 2000 15:28:06 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id PAA16819
	for <rmt@lbl.gov>; Fri, 24 Nov 2000 15:28:06 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26342;
	Fri, 24 Nov 2000 18:28:03 -0500 (EST)
Message-Id: <200011242328.SAA26342@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rmt@lbl.gov
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-rmt-bb-lcc-00.txt
Date: Fri, 24 Nov 2000 18:28:02 -0500
Sender: owner-rmt@lbl.gov
Precedence: bulk

--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		: Reliable Multicast Transport Building Block: Layered 
                          Congestion Control
	Author(s)	: M. Luby et al.
	Filename	: draft-ietf-rmt-bb-lcc-00.txt
	Pages		: 20
	Date		: 22-Nov-00
	
This document describes LCC, a scalable layered congestion control
building block for multicast.  LCC is a combination of approaches that
allow multiple receivers to concurrently receive packets from a single
sender at varying rates depending on individual bandwidth connections
and network conditions.  Two basic goals of the approach are to allow
each receiver to obtain the full benefit of the available bandwidth to
the sender and to be fair to other flows in the network.

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

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-lcc-00.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-lcc-00.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:	<20001122150129.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rmt-bb-lcc-00.txt

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

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

--OtherAccess--

--NextPart--




From owner-rmt@listserv.lbl.gov  Fri Nov 24 19:23:26 2000
Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA04810
	for <rmt-archive@odin.ietf.org>; Fri, 24 Nov 2000 19:23:26 -0500 (EST)
Received: (from majordom@localhost)
	by listserv.lbl.gov (8.9.3/8.9.3) id PAA23288;
	Fri, 24 Nov 2000 15:28:12 -0800 (PST)
X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f
Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id PAA23284
	for <rmt@listserv.lbl.gov>; Fri, 24 Nov 2000 15:28:10 -0800 (PST)
Received: from SpamWall.lbl.gov (localhost [127.0.0.1])
	by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id PAA16829
	for <rmt@listserv.lbl.gov>; Fri, 24 Nov 2000 15:28:10 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id PAA16826
	for <rmt@lbl.gov>; Fri, 24 Nov 2000 15:28:09 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26352;
	Fri, 24 Nov 2000 18:28:06 -0500 (EST)
Message-Id: <200011242328.SAA26352@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rmt@lbl.gov
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-rmt-info-fec-00.txt
Date: Fri, 24 Nov 2000 18:28:06 -0500
Sender: owner-rmt@lbl.gov
Precedence: bulk

--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		: The use of Forward Error Correction in Reliable 
                          Multicast
	Author(s)	: M. Luby et al.
	Filename	: draft-ietf-rmt-info-fec-00.txt
	Pages		: 18
	Date		: 22-Nov-00
	
This memo describes the use of Forward Error Correction (FEC)
codes within the context of reliable IP multicast transport
and provides an introduction to some commonly-used FEC codes.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rmt-info-fec-00.txt

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-info-fec-00.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-info-fec-00.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:	<20001122150137.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rmt-info-fec-00.txt

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

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

--OtherAccess--

--NextPart--




From owner-rmt@listserv.lbl.gov  Tue Nov 28 00:07:54 2000
Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA14681
	for <rmt-archive@odin.ietf.org>; Tue, 28 Nov 2000 00:07:53 -0500 (EST)
Received: (from majordom@localhost)
	by listserv.lbl.gov (8.9.3/8.9.3) id UAA05463;
	Mon, 27 Nov 2000 20:23:56 -0800 (PST)
X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f
Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id UAA05459
	for <rmt@listserv.lbl.gov>; Mon, 27 Nov 2000 20:23:54 -0800 (PST)
Received: from SpamWall.lbl.gov (localhost [127.0.0.1])
	by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id UAA29593
	for <rmt@listserv.lbl.gov>; Mon, 27 Nov 2000 20:23:53 -0800 (PST)
Received: from acm.cs.umn.edu (acm.cs.umn.edu [128.101.32.12])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id UAA29590
	for <rmt@lbl.gov>; Mon, 27 Nov 2000 20:23:52 -0800 (PST)
Received: from monopoly.cs.umn.edu (monopoly.cs.umn.edu [128.101.32.5])
	by acm.cs.umn.edu (8.11.1/8.11.0) with ESMTP id eAS4OUq59925
	for <rmt@lbl.gov>; Mon, 27 Nov 2000 22:24:30 -0600 (CST)
	(envelope-from orasis@acm.cs.umn.edu)
Received: (from orasis@localhost)
	by monopoly.cs.umn.edu (8.8.8/8.8.8) id WAA21496
	for rmt@lbl.gov; Mon, 27 Nov 2000 22:21:21 -0800 (PST)
Date: Mon, 27 Nov 2000 22:21:21 -0800
From: Justin Chapweske <orasis@acm.cs.umn.edu>
To: rmt@lbl.gov
Subject: Vandermonde FEC name
Message-ID: <20001127222121.G12583@monopoly.cs.umn.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: owner-rmt@lbl.gov
Precedence: bulk

Very nice job on the newest drafts guys, especially on the RMT BB FEC
Codes draft.  It is very close to what I implemented against the old ALC
draft.  

Now that 128 is specified as the encoding ID for small block
codes, does anyone (Luigi) know what the FEC Encoding Name will be for the
Vandermonde codes?

-- 
Justin Chapweske, Lead Swarmcast Developer, openCOLA Inc.
http://www.sourceforge.net/projects/swarmcast/


From owner-rmt@listserv.lbl.gov  Tue Nov 28 00:44:07 2000
Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA22899
	for <rmt-archive@odin.ietf.org>; Tue, 28 Nov 2000 00:44:06 -0500 (EST)
Received: (from majordom@localhost)
	by listserv.lbl.gov (8.9.3/8.9.3) id VAA05541;
	Mon, 27 Nov 2000 21:00:08 -0800 (PST)
X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f
Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id VAA05537
	for <rmt@listserv.lbl.gov>; Mon, 27 Nov 2000 21:00:06 -0800 (PST)
Received: from SpamWall.lbl.gov (localhost [127.0.0.1])
	by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id VAA02421
	for <rmt@listserv.lbl.gov>; Mon, 27 Nov 2000 21:00:05 -0800 (PST)
Received: from acm.cs.umn.edu (acm.cs.umn.edu [128.101.32.12])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id VAA02417
	for <rmt@lbl.gov>; Mon, 27 Nov 2000 21:00:05 -0800 (PST)
Received: from monopoly.cs.umn.edu (monopoly.cs.umn.edu [128.101.32.5])
	by acm.cs.umn.edu (8.11.1/8.11.0) with ESMTP id eAS50gq60715
	for <rmt@lbl.gov>; Mon, 27 Nov 2000 23:00:42 -0600 (CST)
	(envelope-from orasis@acm.cs.umn.edu)
Received: (from orasis@localhost)
	by monopoly.cs.umn.edu (8.8.8/8.8.8) id WAA21875
	for rmt@lbl.gov; Mon, 27 Nov 2000 22:57:37 -0800 (PST)
Date: Mon, 27 Nov 2000 22:57:37 -0800
From: Justin Chapweske <orasis@acm.cs.umn.edu>
To: rmt@lbl.gov
Subject: test...
Message-ID: <20001127225737.H12583@monopoly.cs.umn.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: owner-rmt@lbl.gov
Precedence: bulk

testing to see if my mail is getting through to the list..

-- 
Justin Chapweske, Lead Swarmcast Developer, openCOLA Inc.
http://www.sourceforge.net/projects/swarmcast/


From owner-rmt@listserv.lbl.gov  Tue Nov 28 07:17:24 2000
Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA05402
	for <rmt-archive@odin.ietf.org>; Tue, 28 Nov 2000 07:17:23 -0500 (EST)
Received: (from majordom@localhost)
	by listserv.lbl.gov (8.9.3/8.9.3) id DAA05844;
	Tue, 28 Nov 2000 03:22:47 -0800 (PST)
X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f
Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id DAA05840
	for <rmt@listserv.lbl.gov>; Tue, 28 Nov 2000 03:22:45 -0800 (PST)
Received: from SpamWall.lbl.gov (localhost [127.0.0.1])
	by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id DAA10336
	for <rmt@listserv.lbl.gov>; Tue, 28 Nov 2000 03:22:44 -0800 (PST)
Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id DAA10325
	for <rmt@lbl.gov>; Tue, 28 Nov 2000 03:22:38 -0800 (PST)
Received: (from luigi@localhost)
	by info.iet.unipi.it (8.9.3/8.9.3) id MAA18835;
	Tue, 28 Nov 2000 12:25:14 +0100 (CET)
	(envelope-from luigi)
From: Luigi Rizzo <luigi@info.iet.unipi.it>
Message-Id: <200011281125.MAA18835@info.iet.unipi.it>
Subject: Re: Vandermonde FEC name
In-Reply-To: <20001127222121.G12583@monopoly.cs.umn.edu> from Justin Chapweske
 at "Nov 27, 2000 10:21:21 pm"
To: Justin Chapweske <orasis@acm.cs.umn.edu>
Date: Tue, 28 Nov 2000 12:25:14 +0100 (CET)
CC: rmt@lbl.gov
X-Mailer: ELM [version 2.4ME+ PL61 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-rmt@lbl.gov
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Very nice job on the newest drafts guys, especially on the RMT BB FEC
> Codes draft.  It is very close to what I implemented against the old ALC
> draft.  
> 
> Now that 128 is specified as the encoding ID for small block
> codes, does anyone (Luigi) know what the FEC Encoding Name will be for the
> Vandermonde codes?

no idea, sorry. 

	cheers
	luigi
> -- 
> Justin Chapweske, Lead Swarmcast Developer, openCOLA Inc.
> http://www.sourceforge.net/projects/swarmcast/
> 



From owner-rmt@listserv.lbl.gov  Wed Nov 29 07:16:23 2000
Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA23616
	for <rmt-archive@odin.ietf.org>; Wed, 29 Nov 2000 07:16:22 -0500 (EST)
Received: (from majordom@localhost)
	by listserv.lbl.gov (8.9.3/8.9.3) id DAA12846;
	Wed, 29 Nov 2000 03:31:26 -0800 (PST)
X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f
Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id DAA12842
	for <rmt@listserv.lbl.gov>; Wed, 29 Nov 2000 03:31:25 -0800 (PST)
Received: from SpamWall.lbl.gov (localhost [127.0.0.1])
	by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id DAA07749
	for <rmt@listserv.lbl.gov>; Wed, 29 Nov 2000 03:31:24 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id DAA07746
	for <rmt@lbl.gov>; Wed, 29 Nov 2000 03:31:23 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01933;
	Wed, 29 Nov 2000 06:31:22 -0500 (EST)
Message-Id: <200011291131.GAA01933@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rmt@lbl.gov
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-rmt-bb-track-00.txt
Date: Wed, 29 Nov 2000 06:31:21 -0500
Sender: owner-rmt@lbl.gov
Precedence: bulk

--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		: Reliable Multicast Transport Building Block for TRACK
	Author(s)	: B. Whetten, D. Chiu et al.
	Filename	: draft-ietf-rmt-bb-track-00.txt
	Pages		: 26
	Date		: 28-Nov-00
	
This document describes the TRACK Building Block.  It contains
functions relating to positive acknowledgments and hierarchical
tree construction and maintenance.  It is primarily meant to be
used as part of the TRACK Protocol Instantiation.  It is also
designed to be useful as part of overlay multicast systems that
wish to offer efficient confirmed delivery of multicast messages.

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

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-track-00.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-track-00.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:	<20001128134540.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rmt-bb-track-00.txt

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

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

--OtherAccess--

--NextPart--




From owner-rmt@listserv.lbl.gov  Wed Nov 29 07:22:46 2000
Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA26390
	for <rmt-archive@odin.ietf.org>; Wed, 29 Nov 2000 07:22:46 -0500 (EST)
Received: (from majordom@localhost)
	by listserv.lbl.gov (8.9.3/8.9.3) id DAA12853;
	Wed, 29 Nov 2000 03:31:30 -0800 (PST)
X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f
Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id DAA12849
	for <rmt@listserv.lbl.gov>; Wed, 29 Nov 2000 03:31:29 -0800 (PST)
Received: from SpamWall.lbl.gov (localhost [127.0.0.1])
	by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id DAA07764
	for <rmt@listserv.lbl.gov>; Wed, 29 Nov 2000 03:31:28 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id DAA07761
	for <rmt@lbl.gov>; Wed, 29 Nov 2000 03:31:27 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01967;
	Wed, 29 Nov 2000 06:31:26 -0500 (EST)
Message-Id: <200011291131.GAA01967@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rmt@lbl.gov
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-rmt-bb-tree-config-01.txt
Date: Wed, 29 Nov 2000 06:31:26 -0500
Sender: owner-rmt@lbl.gov
Precedence: bulk

--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		: Reliable Multicast Transport Building Block: Tree 
                          Auto-Configuration
	Author(s)	: M. Kadansky, B. Levine, D. Chiu, 
                          B. Whetten, G. Taskale, B. Cain, D. Thaler, S. Koh
	Filename	: draft-ietf-rmt-bb-tree-config-01.txt
	Pages		: 21
	Date		: 28-Nov-00
	
The Reliable Multicast Transport Working Group has been chartered to
standardize multicast transport services. This working group expects
to initially standardize three protocol instantiations. This draft is
concerned with the requirements of the tree-based ACK protocol. In
particular, it is concerned with defining the building block for
auto-configuration of the logical ACK-tree. According to the charter,
a building block is 'a coarse-grained modular component that is
common to multiple protocols along with abstract APIs that define a
building block's access methods and their arguments.'  For more
information, see the Reliable Multicast Transport Building Blocks and
Reliable Multicast Design Space documents [WLKHFL00][HWKFV00].

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

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-tree-config-01.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-tree-config-01.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:	<20001128134550.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rmt-bb-tree-config-01.txt

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

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

--OtherAccess--

--NextPart--




From owner-rmt@listserv.lbl.gov  Wed Nov 29 07:25:18 2000
Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA27530
	for <rmt-archive@odin.ietf.org>; Wed, 29 Nov 2000 07:25:17 -0500 (EST)
Received: (from majordom@localhost)
	by listserv.lbl.gov (8.9.3/8.9.3) id DAA12840;
	Wed, 29 Nov 2000 03:31:22 -0800 (PST)
X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f
Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id DAA12836
	for <rmt@listserv.lbl.gov>; Wed, 29 Nov 2000 03:31:20 -0800 (PST)
Received: from SpamWall.lbl.gov (localhost [127.0.0.1])
	by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id DAA07728
	for <rmt@listserv.lbl.gov>; Wed, 29 Nov 2000 03:31:20 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id DAA07718
	for <rmt@lbl.gov>; Wed, 29 Nov 2000 03:31:19 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01887;
	Wed, 29 Nov 2000 06:31:18 -0500 (EST)
Message-Id: <200011291131.GAA01887@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rmt@lbl.gov
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-rmt-pi-norm-00.txt
Date: Wed, 29 Nov 2000 06:31:17 -0500
Sender: owner-rmt@lbl.gov
Precedence: bulk

--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, S. Floyd, M. Handley,
                          J. Macker
	Filename	: draft-ietf-rmt-pi-norm-00.txt
	Pages		: 11
	Date		: 28-Nov-00
	
This document describes the messages and procedures of the Nega-
tive-acknowledgement (NACK) oriented reliable multicast (NORM).
This revision of the document represents an initial outline of the
protocol description.  The document requires refinement in a number
of areas to be considered complete.  At this time, the document
describes the high level details of the reliable multicast bulk
transfer service model this protocol hopes to fulfill and the gen-
eral message types and mechanisms which will be used to accomplish
those goals.

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

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-00.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-00.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:	<20001128134529.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--




From owner-rmt@listserv.lbl.gov  Wed Nov 29 21:57:57 2000
Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA02507
	for <rmt-archive@odin.ietf.org>; Wed, 29 Nov 2000 21:57:57 -0500 (EST)
Received: (from majordom@localhost)
	by listserv.lbl.gov (8.9.3/8.9.3) id RAA18573;
	Wed, 29 Nov 2000 17:59:38 -0800 (PST)
X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f
Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id RAA18565
	for <rmt@listserv.lbl.gov>; Wed, 29 Nov 2000 17:59:35 -0800 (PST)
Received: from SpamWall.lbl.gov (localhost [127.0.0.1])
	by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id RAA17940
	for <rmt@listserv.lbl.gov>; Wed, 29 Nov 2000 17:59:35 -0800 (PST)
Received: from mailman.lanl.gov (mailman.lanl.gov [128.165.5.1])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id RAA17935
	for <rmt@lbl.gov>; Wed, 29 Nov 2000 17:59:34 -0800 (PST)
Received: (from root@localhost)
	by mailman.lanl.gov (8.10.1/8.10.1/(cic-5, 6/12/00)) id eAU1msN25363;
	Wed, 29 Nov 2000 18:48:54 -0700
Received: from mailproxy.lanl.gov ([128.165.254.25])
	by mailman.lanl.gov (8.10.1/8.10.1/(cic-5, 6/12/00)) with ESMTP id eATM4Hf09303;
	Wed, 29 Nov 2000 15:04:17 -0700
Received: from loki.ietf.org (loki.ietf.org [132.151.1.177])
	by mailproxy.lanl.gov (8.10.1/8.10.1/(cic-5, 6/12/00)) with ESMTP id eATM4Ff25980;
	Wed, 29 Nov 2000 15:04:15 -0700
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id QAA06320
	for ietf-123-outbound.07@ietf.org; Wed, 29 Nov 2000 16:45:01 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id GAA01521
	for <all-ietf@loki.ietf.org>; Wed, 29 Nov 2000 06:31:27 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01967;
	Wed, 29 Nov 2000 06:31:26 -0500 (EST)
Message-Id: <200011291131.GAA01967@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rmt@lbl.gov
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-rmt-bb-tree-config-01.txt
Date: Wed, 29 Nov 2000 06:31:26 -0500
Sender: owner-rmt@lbl.gov
Precedence: bulk

--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		: Reliable Multicast Transport Building Block: Tree 
                          Auto-Configuration
	Author(s)	: M. Kadansky, B. Levine, D. Chiu, 
                          B. Whetten, G. Taskale, B. Cain, D. Thaler, S. Koh
	Filename	: draft-ietf-rmt-bb-tree-config-01.txt
	Pages		: 21
	Date		: 28-Nov-00
	
The Reliable Multicast Transport Working Group has been chartered to
standardize multicast transport services. This working group expects
to initially standardize three protocol instantiations. This draft is
concerned with the requirements of the tree-based ACK protocol. In
particular, it is concerned with defining the building block for
auto-configuration of the logical ACK-tree. According to the charter,
a building block is 'a coarse-grained modular component that is
common to multiple protocols along with abstract APIs that define a
building block's access methods and their arguments.'  For more
information, see the Reliable Multicast Transport Building Blocks and
Reliable Multicast Design Space documents [WLKHFL00][HWKFV00].

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

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-tree-config-01.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-tree-config-01.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:	<20001128134550.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rmt-bb-tree-config-01.txt

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

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

--OtherAccess--

--NextPart--





From owner-rmt@listserv.lbl.gov  Wed Nov 29 22:02:17 2000
Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA04136
	for <rmt-archive@odin.ietf.org>; Wed, 29 Nov 2000 22:02:17 -0500 (EST)
Received: (from majordom@localhost)
	by listserv.lbl.gov (8.9.3/8.9.3) id RAA18572;
	Wed, 29 Nov 2000 17:59:38 -0800 (PST)
X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f
Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id RAA18563
	for <rmt@listserv.lbl.gov>; Wed, 29 Nov 2000 17:59:35 -0800 (PST)
Received: from SpamWall.lbl.gov (localhost [127.0.0.1])
	by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id RAA17937
	for <rmt@listserv.lbl.gov>; Wed, 29 Nov 2000 17:59:34 -0800 (PST)
Received: from mailman.lanl.gov (mailman.lanl.gov [128.165.5.1])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id RAA17933
	for <rmt@lbl.gov>; Wed, 29 Nov 2000 17:59:34 -0800 (PST)
Received: (from root@localhost)
	by mailman.lanl.gov (8.10.1/8.10.1/(cic-5, 6/12/00)) id eAU1teo26146;
	Wed, 29 Nov 2000 18:55:40 -0700
Received: from mailproxy.lanl.gov ([128.165.254.25])
	by mailman.lanl.gov (8.10.1/8.10.1/(cic-5, 6/12/00)) with ESMTP id eATM4Hf09303;
	Wed, 29 Nov 2000 15:04:17 -0700
Received: from loki.ietf.org (loki.ietf.org [132.151.1.177])
	by mailproxy.lanl.gov (8.10.1/8.10.1/(cic-5, 6/12/00)) with ESMTP id eATM4Ff25980;
	Wed, 29 Nov 2000 15:04:15 -0700
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id QAA06320
	for ietf-123-outbound.07@ietf.org; Wed, 29 Nov 2000 16:45:01 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id GAA01521
	for <all-ietf@loki.ietf.org>; Wed, 29 Nov 2000 06:31:27 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01967;
	Wed, 29 Nov 2000 06:31:26 -0500 (EST)
Message-Id: <200011291131.GAA01967@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rmt@lbl.gov
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-rmt-bb-tree-config-01.txt
Date: Wed, 29 Nov 2000 06:31:26 -0500
Sender: owner-rmt@lbl.gov
Precedence: bulk

--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		: Reliable Multicast Transport Building Block: Tree 
                          Auto-Configuration
	Author(s)	: M. Kadansky, B. Levine, D. Chiu, 
                          B. Whetten, G. Taskale, B. Cain, D. Thaler, S. Koh
	Filename	: draft-ietf-rmt-bb-tree-config-01.txt
	Pages		: 21
	Date		: 28-Nov-00
	
The Reliable Multicast Transport Working Group has been chartered to
standardize multicast transport services. This working group expects
to initially standardize three protocol instantiations. This draft is
concerned with the requirements of the tree-based ACK protocol. In
particular, it is concerned with defining the building block for
auto-configuration of the logical ACK-tree. According to the charter,
a building block is 'a coarse-grained modular component that is
common to multiple protocols along with abstract APIs that define a
building block's access methods and their arguments.'  For more
information, see the Reliable Multicast Transport Building Blocks and
Reliable Multicast Design Space documents [WLKHFL00][HWKFV00].

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

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-tree-config-01.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-tree-config-01.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:	<20001128134550.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rmt-bb-tree-config-01.txt

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

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

--OtherAccess--

--NextPart--





From owner-rmt@listserv.lbl.gov  Wed Nov 29 22:07:46 2000
Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA06066
	for <rmt-archive@odin.ietf.org>; Wed, 29 Nov 2000 22:07:46 -0500 (EST)
Received: (from majordom@localhost)
	by listserv.lbl.gov (8.9.3/8.9.3) id SAA18640;
	Wed, 29 Nov 2000 18:13:29 -0800 (PST)
X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f
Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id SAA18636
	for <rmt@listserv.lbl.gov>; Wed, 29 Nov 2000 18:13:27 -0800 (PST)
Received: from SpamWall.lbl.gov (localhost [127.0.0.1])
	by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id SAA20665
	for <rmt@listserv.lbl.gov>; Wed, 29 Nov 2000 18:13:27 -0800 (PST)
Received: from mailman.lanl.gov (mailman.lanl.gov [128.165.5.1])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id SAA20662
	for <rmt@lbl.gov>; Wed, 29 Nov 2000 18:13:26 -0800 (PST)
Received: (from root@localhost)
	by mailman.lanl.gov (8.10.1/8.10.1/(cic-5, 6/12/00)) id eAU1u2s26542;
	Wed, 29 Nov 2000 18:56:02 -0700
Received: from listman.lanl.gov ([128.165.3.62])
	by mailman.lanl.gov (8.10.1/8.10.1/(cic-5, 6/12/00)) with ESMTP id eATM5af11545;
	Wed, 29 Nov 2000 15:05:36 -0700
Received: (from daemon@localhost)
	by listman.lanl.gov (8.9.3/8.9.3/(cic-5, 2/9/99)) id PAA02438
	for ietf-outgoing; Wed, 29 Nov 2000 15:05:32 -0700
Message-Id: <200011291131.GAA01933@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rmt@lbl.gov
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-rmt-bb-track-00.txt
Date: Wed, 29 Nov 2000 06:31:21 -0500
Sender: owner-rmt@lbl.gov
Precedence: bulk

--NextPart--


From owner-rmt@listserv.lbl.gov  Wed Nov 29 22:44:47 2000
Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA20664
	for <rmt-archive@odin.ietf.org>; Wed, 29 Nov 2000 22:44:47 -0500 (EST)
Received: (from majordom@localhost)
	by listserv.lbl.gov (8.9.3/8.9.3) id TAA18776;
	Wed, 29 Nov 2000 19:01:15 -0800 (PST)
X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f
Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id TAA18772
	for <rmt@listserv.lbl.gov>; Wed, 29 Nov 2000 19:01:13 -0800 (PST)
Received: from SpamWall.lbl.gov (localhost [127.0.0.1])
	by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id TAA27726
	for <rmt@listserv.lbl.gov>; Wed, 29 Nov 2000 19:01:12 -0800 (PST)
Received: from mailman.lanl.gov (mailman.lanl.gov [128.165.5.1])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id TAA27723
	for <rmt@lbl.gov>; Wed, 29 Nov 2000 19:01:12 -0800 (PST)
Received: (from root@localhost)
	by mailman.lanl.gov (8.10.1/8.10.1/(cic-5, 6/12/00)) id eAU2UcX09784;
	Wed, 29 Nov 2000 19:30:38 -0700
Received: from listman.lanl.gov ([128.165.3.62])
	by mailman.lanl.gov (8.10.1/8.10.1/(cic-5, 6/12/00)) with ESMTP id eATM5af11545;
	Wed, 29 Nov 2000 15:05:36 -0700
Received: (from daemon@localhost)
	by listman.lanl.gov (8.9.3/8.9.3/(cic-5, 2/9/99)) id PAA02438
	for ietf-outgoing; Wed, 29 Nov 2000 15:05:32 -0700
Message-Id: <200011291131.GAA01933@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rmt@lbl.gov
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-rmt-bb-track-00.txt
Date: Wed, 29 Nov 2000 06:31:21 -0500
Sender: owner-rmt@lbl.gov
Precedence: bulk

--NextPart--


From owner-rmt@listserv.lbl.gov  Wed Nov 29 22:57:26 2000
Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA25055
	for <rmt-archive@odin.ietf.org>; Wed, 29 Nov 2000 22:57:26 -0500 (EST)
Received: (from majordom@localhost)
	by listserv.lbl.gov (8.9.3/8.9.3) id TAA18770;
	Wed, 29 Nov 2000 19:01:12 -0800 (PST)
X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f
Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id TAA18761
	for <rmt@listserv.lbl.gov>; Wed, 29 Nov 2000 19:01:10 -0800 (PST)
Received: from SpamWall.lbl.gov (localhost [127.0.0.1])
	by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id TAA27710
	for <rmt@listserv.lbl.gov>; Wed, 29 Nov 2000 19:01:09 -0800 (PST)
Received: from mailman.lanl.gov (mailman.lanl.gov [128.165.5.1])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id TAA27702
	for <rmt@lbl.gov>; Wed, 29 Nov 2000 19:01:08 -0800 (PST)
Received: (from root@localhost)
	by mailman.lanl.gov (8.10.1/8.10.1/(cic-5, 6/12/00)) id eAU2TV409186;
	Wed, 29 Nov 2000 19:29:31 -0700
Received: from mailproxy.lanl.gov ([128.165.254.25])
	by mailman.lanl.gov (8.10.1/8.10.1/(cic-5, 6/12/00)) with ESMTP id eATM4Hf09303;
	Wed, 29 Nov 2000 15:04:17 -0700
Received: from loki.ietf.org (loki.ietf.org [132.151.1.177])
	by mailproxy.lanl.gov (8.10.1/8.10.1/(cic-5, 6/12/00)) with ESMTP id eATM4Ff25980;
	Wed, 29 Nov 2000 15:04:15 -0700
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id QAA06320
	for ietf-123-outbound.07@ietf.org; Wed, 29 Nov 2000 16:45:01 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id GAA01521
	for <all-ietf@loki.ietf.org>; Wed, 29 Nov 2000 06:31:27 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01967;
	Wed, 29 Nov 2000 06:31:26 -0500 (EST)
Message-Id: <200011291131.GAA01967@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rmt@lbl.gov
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-rmt-bb-tree-config-01.txt
Date: Wed, 29 Nov 2000 06:31:26 -0500
Sender: owner-rmt@lbl.gov
Precedence: bulk

--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		: Reliable Multicast Transport Building Block: Tree 
                          Auto-Configuration
	Author(s)	: M. Kadansky, B. Levine, D. Chiu, 
                          B. Whetten, G. Taskale, B. Cain, D. Thaler, S. Koh
	Filename	: draft-ietf-rmt-bb-tree-config-01.txt
	Pages		: 21
	Date		: 28-Nov-00
	
The Reliable Multicast Transport Working Group has been chartered to
standardize multicast transport services. This working group expects
to initially standardize three protocol instantiations. This draft is
concerned with the requirements of the tree-based ACK protocol. In
particular, it is concerned with defining the building block for
auto-configuration of the logical ACK-tree. According to the charter,
a building block is 'a coarse-grained modular component that is
common to multiple protocols along with abstract APIs that define a
building block's access methods and their arguments.'  For more
information, see the Reliable Multicast Transport Building Blocks and
Reliable Multicast Design Space documents [WLKHFL00][HWKFV00].

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

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-tree-config-01.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-tree-config-01.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:	<20001128134550.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rmt-bb-tree-config-01.txt

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

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

--OtherAccess--

--NextPart--





From owner-rmt@listserv.lbl.gov  Thu Nov 30 18:33:09 2000
Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA27629
	for <rmt-archive@odin.ietf.org>; Thu, 30 Nov 2000 18:33:08 -0500 (EST)
Received: (from majordom@localhost)
	by listserv.lbl.gov (8.9.3/8.9.3) id OAA21466;
	Thu, 30 Nov 2000 14:10:39 -0800 (PST)
X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f
Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id OAA21458
	for <rmt@listserv.lbl.gov>; Thu, 30 Nov 2000 14:10:36 -0800 (PST)
Received: from SpamWall.lbl.gov (localhost [127.0.0.1])
	by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id OAA10987
	for <rmt@listserv.lbl.gov>; Thu, 30 Nov 2000 14:10:36 -0800 (PST)
Received: from motgate2.mot.com (motgate2.mot.com [136.182.1.10])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id OAA10872
	for <rmt@lbl.gov>; Thu, 30 Nov 2000 14:10:20 -0800 (PST)
Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate2.mot.com (motgate2 2.1) with ESMTP id PAA17469; Thu, 30 Nov 2000 15:09:49 -0700 (MST)]
Received: [from homer.arc.corp.mot.com (homer.arc.corp.mot.com [217.1.10.38]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id PAA16741; Thu, 30 Nov 2000 15:09:46 -0700 (MST)]
Received: from arc.corp.mot.com (marcia.arc.corp.mot.com [217.1.10.74])
	by homer.arc.corp.mot.com (8.10.2/8.10.2) with ESMTP id eAUM8US05125;
	Fri, 1 Dec 2000 09:08:30 +1100 (EST)
Message-ID: <3A26CF70.552047EF@arc.corp.mot.com>
Date: Fri, 01 Dec 2000 09:06:40 +1100
From: Roger Kermode <rkermode@arc.corp.mot.com>
Reply-To: Roger.Kermode@motorola.com
Organization: Motorola
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: rmt-list <rmt@lbl.gov>
CC: Lorenzo Vicisano <lorenzo@cisco.com>, Allison Mankin <mankin@ISI.EDU>
Subject: RMT Tentative Agenda (items only at this stage)
Content-Type: multipart/mixed;
 boundary="------------0336CD28CEB2CCF5E1221257"
Sender: owner-rmt@lbl.gov
Precedence: bulk

This is a multi-part message in MIME format.
--------------0336CD28CEB2CCF5E1221257
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Dear RMT'ers,

in preparing the agenda for the San Diego meeting
We've noticed that we have a lot of drafts, some of
which are new and some of which have expired.

In keeping with directives from the ADs we are asking
that presenters assume that people have read the
draft and that their presentations consist of a brief
summary of the draft/updates to the draft followed
by discussion on outstanding issues.

Given this approach we are expecting that there
will only be presentations for the drafts that have
changed since the last meeting, i.e. drafts with *
in front of them.

To date we've only received a couple of explicit
requests for time slots. If you want to present
during the RMT sessions at the IETF please
email the chairs ASAP

regards,

Roger, Lorenzo, and Allison



Outstanding RMT Drafts/Potential Presentations at San Diego
=========================================
Key:
*  = updated since last meeting
exp = draft has expired



Agenda Bashing, Roger 5 mins

General Draft Updates
* <draft-ietf-rmt-building-blocks-03.txt>
<draft-ietf-author-guidelines-**.txt>

NORM reorganisation
* <draft-ietf-rmt-pi-norm-00.txt>

ALC drafts
* <draft-ietf-rmt-bb-lct-00.txt>
* <draft-ietf-rmt-info-fec-02.txt>
<draft-ietf-rmt-pi-alc-01.txt>

TRACK
<draft-ietf-rmt-bb-track-00.txt>
* <draft-ietf-rmt-bb-tree-config-01.txt>
<draft-ietf-rmt-track-arch-00.txt>
<draft-ietf-rmt-track-security-00.txt>

CONGESTION CONTROL
* <draft-ietf-rmt-bb-lcc-00.txt> Mike Luby 15 mins?
<draft-ietf-rmt-bb-mrcc-00.txt>

GRA
exp <draft-ietf-rmt-gra-arch-01.txt>

Individual drafts
* <draft-calvert-concast-svc-00.txt> Ken Calvert 15 mins

MIBs
<draft-petrova-pgmmib-00.txt> Michale Garwood 10 mins

msec WG advertisement, Roger, 5 mins


--------------0336CD28CEB2CCF5E1221257
Content-Type: text/x-vcard; charset=us-ascii;
 name="rkermode.vcf"
Content-Description: Card for Roger Kermode
Content-Disposition: attachment;
 filename="rkermode.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Kermode;Roger
tel;cell:+61-408-212-284
tel;fax:+61-2-9666-0501
tel;home:+61-2-9664-8335
tel;work:+61-2-9666-0558
x-mozilla-html:FALSE
url:www.mot.com.au
org:Motorola Australian Research Centre;Communications and Networking Lab
version:2.1
email;internet:Roger.Kermode@motorola.com
title:Principal Research Engineer, Manager
adr;quoted-printable:;;Level 3,=0D=0A12 Lord St.;Botany;NSW;2019;Australia
fn:Roger Kermode
end:vcard

--------------0336CD28CEB2CCF5E1221257--



