The IP over ATM Mailing List Archive by date

[Philippe Oechslin <oechslin@lrc.epfl.ch>]

>  
>  >       Title     : Application REQuested IP over ATM (AREQUIPA)            
>  >       Author(s) : W. Almesberger, J. Le Boudec, P. Oechslin
> 
> 
> this reminds me a lot of an idea in UK protocols of the early 80s
> called 'yellow book',which basically allowed support of "onward
> addressing" of calls
> 
> basically what you want is for a "haning" tuple at the active and
> passive host ends to be bound and what arequipa provides is an API
> (and some suggestions for ATMARP extension echanisms ) to support t
> 
> i would prefer the API to simply look like the yellow book idea-
> basically, invenet a new "socket address family" called AREQUIPA, and
> allow it to consist of
> IP address+ application port + atm address
> 
> then you can connect, bind, accpet and getperername on it. and all is
> well, you have your 'combined address and call setup and singlaing'
> interface, without any change to the applications
> 
> then you could even use Juha's DNS support for atm addresses to enable
> applicatiosn that are name based to ue this "as is"
> 
> maybe?
> 
> comments?
> 
> cheers

Jon,

We don't want to define another family of sockets. We want to give a
mechanism to provide application to application QoS on normal TCP or
UDP sockets or any other end points.

Arequipa just tells your IP over ATM implementation to open a direct ATM 
connection between two given hosts, with a given QoS, and for the exclusive 
use by a given pair of sockets. Once you have done the Arequipa system call, 
you can open TCP or UDP sockets and profit from the requested QoS. 

Basically you get what NHRP and RSVP would give you for point to point 
connections between IP hosts in an ATM network. The advantage is that you 
don't need any support from the network, neither RSVP routers nor the 
deployment of NHRP. 

With Arequipa, two applications which want to exchange data with
guaranteed QoS do not require external help for address
resolution. Since they will initially negociate the QoS parameters and
the socktes to be used, they can as well exchange their ATM
addresses. If they don't trust each other they can still use extended
DNS or NHRP to verify the addresses.

 cheers,

   Philippe

--
oechslin@di.epfl.ch