Subject: new draft draft-tommasi-rsvp-enhan-scalab-01.txt

From: Franco Tommasi <[email-masked]>
Date: Sun, 31 Oct 1999 22:38:16 +0100

Sorry if this is the second time you receive this message (I didn`t receive it from the list so I thought something went wrong).
============================================================================

Hi,

A new version of our draft is available.

You can download it from

http://www.ietf.org/internet-drafts/draft-tommasi-rsvp-enhan-scalab-01.txt

Its subject is RSVP scalability, and it updates the draft sent
on the 1st of July (rejected; at the time we didn`t suspect of any deadline, we apologize) and resent (successfully: draft-tommasi-rsvp-enhan-scalab-00.txt) soon after the Oslo meeting.

We will be in Washington, and we received a positive answer to our request of a little time on the agenda to present the draft.

Perhaps a few lines about its content can be of help. 
We would be happy to answer to comments and questions.

Contents

2.   MESSAGE_ID OBJECTS
3.   BUNDLE MESSAGES
Just pointers to Berger's work, with slight differences.

4.   HOW TO DELAY MESSAGES
4.1. URGENT BIT
The context is the interim meeting's decision, about using a
100msec-delay-buffer for bundling's purposes.
We think it is in general incorrect to force all application to suffer a delay that could end up being greater than that caused by IP`s best-effort. 
So:
1) The delay timer of the Bundle buffer is determined, when possible, as a
percentage of the RTT between nodes.
2) An Urgent bit is defined in trigger messages, so that these
applications can escape the bundling delay.

5.   LIST_DESCRIPTOR OBJECTS
List of Message_IDs. Quite similar to Berger's MESSAGE_ID LIST objects: they
where parallely developed.

5.1. COMPRESSED_LIST_DESCRIPTOR OBJECTS
Some simple compression mechanisms for LIST_DESCRIPTOR objects.
(Their are used to simplify some operation like Strong Refresh)

6.   ACK MESSAGES
LIST_DESCRIPTOR objects for multple acks can be used.

7.   WEAK REFRESH
A simple refresh mechanism: just exchange messages with LIST_DESCRIPTOR
objects.

8.   STRONG REFRESH
A reliable refresh mechanism. It is very useful on really congested links,
to avoid state time-outs due to lost refresh messages.
The full list of messages to be refreshed is exchanged, so that neighbor routers
can fully syncronize their state.
COMPRESSED_LIST_DESCRIPTOR objects perhaps should be used.

Best regards

Franco Tommasi <[email-masked]>
and 
Simone Molendini <[email-masked]>

University of Lecce 
Lecce - Italy