Browse Prior Art Database

RSVP over ATM Implementation Guidelines (RFC2379)

IP.com Disclosure Number: IPCOM000002950D
Original Publication Date: 1998-Aug-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 6 page(s) / 14K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

L. Berger: AUTHOR

Abstract

This memo presents specific implementation guidelines for running RSVP over ATM switched virtual circuits (SVCs). The general problem is discussed in [6]. Implementation requirements are discussed in [2]. Integrated Services to ATM service mappings are covered in [3]. The full set of documents present the background and information needed to implement Integrated Services and RSVP over ATM.

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

Network Working Group L. Berger

Request for Comments: 2379 FORE Systems

BCP: 24 August 1998

Category: Best Current Practice

RSVP over ATM Implementation Guidelines

Status of this Memo

This document specifies an Internet Best Current Practices for the

Internet Community, and requests discussion and suggestions for

improvements. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1998). All Rights Reserved.

Abstract

This memo presents specific implementation guidelines for running

RSVP over ATM switched virtual circuits (SVCs). The general problem

is discussed in [6]. Implementation requirements are discussed in

[2]. Integrated Services to ATM service mappings are covered in [3].

The full set of documents present the background and information

needed to implement Integrated Services and RSVP over ATM.

1. Introduction

This memo discusses running IP over ATM in an environment where SVCs

are used to support QoS flows and RSVP is used as the internet level

QoS signaling protocol. It applies when using CLIP/ION, LANE2.0 and

MPOA methods for supporting IP over ATM. The general issues related

to running RSVP[4] over ATM have been covered in several papers

including [6] and other earlier work. This document is intended as a

companion to [6,2] and as a guide to implementers. The reader should

be familiar with both documents.

This document provides a recommended set of functionality for

implementations using ATM UNI3.x and 4.0, while allowing for more

sophisticated approaches. We expect some vendors to additionally

provide some of the more sophisticated approaches described in [6],

and some networks to only make use of such approaches. The

recommended set of functionality is defined to ensure predictability

and interoperability between different implementations. Requirements

for RSVP over ATM implementations are provided in [2].

This document uses the same terms and assumption stated in [2].

Additionally, the key words "MUST", "MUST NOT", "REQUIRED", "SHALL",

"SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and

"OPTIONAL" in this document are to be interpreted as described in RFC

2119 [5].

2. Implementation Recommendations

This section provides implementation guidelines for implementation of

RSVP over ATM. Several recommendations are common for all, RSVP

sessions, both unicast and multicast. There are also recommendations

that are unique to unicast and multicast session types.

2.1 RSVP Message VC Usage

The general issues related to which VC should be used for RSVP

messages is covered in [6]. It discussed several implementation

options including: mixed control and data, single control VC per

session, single control VC multiplexed among sessions, and multiple

VCs multiplexed among sessi...