Subject: Orlando IETF "RUTS" BOF

From: [email-masked]
Date: Wed, 02 Dec 1998 10:00 -0800 (PST)

Subject: Orlando IETF "RUTS" BOF
From: [email-masked]
To: [email-masked]
Cc: [email-masked]
Date: Tue, 01 Dec 1998 23:11 -0800 (PST)

     FYI.
     
     --aaron

______________________________ Forward Header __________________________________
Subject: Orlando IETF "RUTS" BOF
Author:  [email-masked] at mime
Date:    12/1/98 11:11 PM

A number of IETF efforts have developed or are developing different forms of 
reliable (and often "lightweight") transport protocols, frequently using UDP 
with their own retransmission algorithm, because they perceive that TCP is 
inadequate for their requirements.  We've put together a BOF for next Monday 
morning (9:30-11:30) at the Orlando IETF to understand these requirements 
better (description appended).
     
The elements of the BOF span much of the Transport Area.  If you think 
that your WG members would find this BOF of interest, please forward this 
message to the WG mailing list.
     
        Thanks,
     
                Vern
     
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     
Requirements for Unicast Transport/Sessions (RUTS)
     
Chairs: Scott Bradner & Vern Paxson
     
Description:
     
A number of IETF efforts have developed or are developing different forms 
of reliable (and often "lightweight") transport protocols, because they 
perceive that TCP is inadequate for their requirements.  This BOF will 
explore what those requirements are, serving both as input into a TSV 
directorate document discussing the services that can be built on top of 
TCP; and to gauge the utility of developing a transport protocol (perhaps 
a TCP variant) and/or session protocol that can meet these needs in a 
general way.
     
The focus is on clear-and-present requirements for unicast and reliable (or 
"near-reliable") transport/sessions, and not on general transport protocol 
features, nor on specific alternative transport protocols (except as they 
illustrate requirements).
     
Agenda:
     
        Introduction
        Requirements underlying:
                COPS
                RADIUS
                L2TP
                HTTP-NG
                SIP
                NFSv4
                telephony
        Requirements summary
        Security implications
        TCP and these requirements
                which can it currently meet
                which can it meet by adding options
                which can it meet by tweaking its model 
                which are significantly outside its model