colip BoF tentative agenda

Hiroshi Esaki <hiroshi@ctr.columbia.edu> Thu, 23 March 1995 14:59 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03146; 23 Mar 95 9:59 EST
Received: from acton.timeplex.com by IETF.CNRI.Reston.VA.US id aa03136; 23 Mar 95 9:59 EST
Received: from sirius.ctr.columbia.edu (root@sirius.ctr.columbia.edu [128.59.64.60]) by maelstrom.acton.timeplex.com (8.6.9/ACTON-MAIN-1.2) with ESMTP id JAA19103 for <rolc@maelstrom.timeplex.com>; Thu, 23 Mar 1995 09:36:44 -0500
Received: from mimas.ctr.columbia.edu (hiroshi@mimas.ctr.columbia.edu [128.59.74.18]) by sirius.ctr.columbia.edu (8.6.10/8.6.4.287) with ESMTP id JAA14029; Thu, 23 Mar 1995 09:31:53 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Hiroshi Esaki <hiroshi@ctr.columbia.edu>
Received: (hiroshi@localhost) by mimas.ctr.columbia.edu (8.6.10/8.6.4.788743) id JAA03694; Thu, 23 Mar 1995 09:31:51 -0500
Date: Thu, 23 Mar 1995 09:31:51 -0500
Message-Id: <199503231431.JAA03694@mimas.ctr.columbia.edu>
To: rsvp@isi.edu, rolc@maelstrom.timeplex.com, ip-atm@matmos.hpl.hp.com, colip@ctr.columbia.edu
Subject: colip BoF tentative agenda


Hi all, 

The following is a tentative agenda of colip-BoF. 
When you want to give a talk, please let us know. 

Best Regards, 

Hiroshi Esaki
(Toshiba Corp.)


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

[Time of BoF] 
    April 4 (Tue) 13:00-15:00 colip  


[BoF tentative agenda]
    1. Conventional IP model and RSVP (by Ohta)  

    2. Router architecture extentions for ATM : Overview (by Katsube) 

    3. Flow management/control issues on ATM (maybe by Esaki)  

    4. Others   


[Purpose of the BoF]
    The purpose of this BoF is to discuss the protocol and architecture
    that extract the capability of ATM, that can provide QoS data-link 
    pipe for each commnication flow, for IP communication with new 
    network and transport protocol suite (e.g. resource reservation 
    oriented protocol such as RSVP). 

    In the wide area Internet, it was said that it was almost 
    impossible to provide cell-relay based end-to-end pipe. 
    When the QoS requirement and the required banswidth for the IP 
    flow can be explicitly indicated to the router, it will be easy 
    to relay the IP packet cell-by-cell in the router, while provide 
    QoS assurance.  
    In other words, the interaction between the QoS oriented network/
    transport protocol (e.g.RSVP/ST-II) and the ATM protocol must 
    be explored to provide end-to-end QoS provision over the Internet. 

    The conventinal connectionless service can be provided just 
    using a connection oriented data-link pipe among the routers.