Browse Prior Art Database

Application REQuested IP over ATM (AREQUIPA) (RFC2170)

IP.com Disclosure Number: IPCOM000002728D
Original Publication Date: 1997-Jul-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 9 page(s) / 21K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

W. Almesberger: AUTHOR [+3]

Abstract

This document specifies 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).

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 13% of the total text.

Network Working Group W. Almesberger

Request for Comments: 2170 J. Le Boudec

Category: Informational P. Oechslin

LRC, DI-EPFL, Switzerland

July 1997

Application REQuested IP over ATM (AREQUIPA)

Status of this Memo

This memo provides information for the Internet community. This memo

does not specify an Internet standard of any kind. Distribution of

this memo is unlimited.

IESG Note:

This RFC has not had the benefit of the rigorous peer review that is

part of the process in an IETF working group. The technology it

describes has been implemented and is now undergoing testing. It

would be wise to analyze the results of this testing as well as to

understand alternatives before committing to this approach for IP

over ATM with QoS guarantees.

Abstract

This document specifies 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 how

- Arequipa can be implemented in IPv4 by slightly modifying the

- 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.

1. I...