The IP over ATM Mailing List Archive by date

Cell Relay Retreat>List Archive>month:1996-Jan> msg00249



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

new Internet Draft draft-ietf-ipatm-arequipa-00.txt

  • From: Philippe Oechslin <oechslin@lrc.epfl.ch>
  • Date: Mon, 29 Jan 1996 19:59:42 +0100
  • Cc: ip-atm@matmos.hpl.hp.com, almesber@lrcsuns.epfl.ch, leboudec@lrcsuns.epfl.ch


curtis@ans.net said:
>  This mechanism fails completely if the host is one ethernet or FDDI 
> hop away from the ATM network or for any other non-ATM service that 
> offers QoS.  The mechanisms provided by RSVP offer the much more 
> general capability.  I recommend that the WG not adopt this draft. 

You are right, Arequipa can only be used between host that have direct ATM 
connectivity. However, it is not intended to replace RSVP. 

The value of Arequipa is that it can provide 'ATM-grade' QoS to hosts 
connected to any ATM network, without having to wait for RSVP and/or NHRP to 
be deployed over the ATM network. 

In the mean-time, a machine connected one hop away on FDDI or ethernet, could 
still use an application layer proxy, as described in the section about 
security and firewalls. A typical situation would be a HTTP proxy and cache on 
the FDDI-ATM gateway. You wouldn't even have to modify your HTTP client but it 
would still benefit from the guaranteed QoS between the proxy and a distant 
server, if the local network was provisioned with enough spare bandwidth. 

  regards,
 
    Philippe 


--
Philippe Oechslin                                    mailto:oechslin@di.epfl.ch
Laboratoire de Reseaux de Communication (LRC)         Phone:  +41(21) 693 66 16
Swiss Federal Institute of Technology (EPFL)            Fax:  +41(21) 693 66 10
CH-1015 Lausanne, Switzerland                   http://lrcwww.epfl.ch/~oechslin