The IP over ATM Mailing List Archive by date

[Curtis Villamizar <curtis@ans.net>]

>              Application REQuested IP over ATM (AREQUIPA)
>                  <draft-ietf-ipatm-arequipa-00.txt>
> 
> [...]
> 
> 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).
> 
>    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 mainly modifying the
>        implementation of ATMARP[1],
     - Arequipa can be implemented in IPv6[3] by the appropriate use of
>        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.

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.

Curtis