The IP Over NBMA (ION) Archive

Cell Relay Retreat>ION Archive>month:1996-Jun> msg00161



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

arequipa presentation on ISSLL agenda

  • From: Philippe Oechslin <oechslin@lrc.epfl.ch>
  • Date: Thu, 20 Jun 1996 13:52:39 +0200
  • cc: men@login.net, ssilverman@reston.btna.com
  • X-face: /.djtld]hG%u(62*;}o.4wE~ef{DUV!fcj6cSMV|td_JjPQi/6[R?LXx.*3tD,AGS*nn.D^3=W.BbTm+C:mt!\ILPi&zXu~S9Dqc>`n3?-1M2*~Ssf_y/f@;_nW\\BbVhMY|Q4-9Y~?Pkn$U\fs(5X]0v~-PyO<<yvDS'nY5.5ht0ndg:=AXDa28;[fKo/37RTh0La!cH}_9jV6Vk&5!a>m5C/u%5Fz"OI@
  • X-url: http://lrcwww.epfl.ch/~oechslin

For those of you who followed the discussion about Arequipa in the late ipatm 
group: We have a presentation of Arequipa and its implementation in the linux 
kernel in the second session of the ISSLL group, Tuesday around 11h10.

The latest ID about Arequipa is draft-almesberger-arequipa-01.txt.

  Philippe

--

Abstract

   We propose a method for allowing ATM-attached hosts that have direct
   ATM connectivity to set up end-to-end IP over ATM connections within
   the reachable ATM cloud, on request from applications, and for the
   exclusive use by the requesting applications. This allows the
   requesting applications to benefit in a straightforward way from
   ATM's inherent ability to guarantee the quality of service (QoS).

   Given a mapping from service classes, as defined by INTSERV[6], to
   ATM traffic descriptors, Arequipa can be used to implement
   integrated services over ATM link layers. Usage of Arequipa to
   provide integrated services even if ATM is only available for
   intermediate links is not discussed in this document but should be
   straight-forward. 

   The major advantage of using an approach like Arequipa is that it
   needs to be implemented only on the hosts using it. It requires no
   extra service (eg. NHRP or RSVP) to be deployed on the switches or
   routers of the ATM cloud.


   We discuss the implementation of Arequipa for hosts running IPv4 and
   IPv6. As an illustration, we also discuss how World-Wide-Web
   applications can use Arequipa to deliver documents with a guaranteed
   quality of service.

   In particular we show that

     - Arequipa can be implemented in IPv4 by slightly modifying the
       existing implementation of support for IP over ATM [1],
     - Arequipa can be implemented in IPv6[3] by the appropriate
       flow labels and the extension of the neighbour cache,
     - Arequipa can be used in the Web by adding extra information in
       the headers of HTTP requests and responses.

    Finally, we address safety and security implications.