Browse Prior Art Database

RSVP over ATM Implementation Requirements (RFC2380)

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

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

L. Berger: AUTHOR

Abstract

This memo presents specific implementation requirements for running RSVP over ATM switched virtual circuits (SVCs). It presents requirements that ensure interoperability between multiple implementations and conformance to the RSVP and Integrated Services specifications. A separate document [5] provides specific guidelines for running over today's ATM networks. The general problem is discussed in [9]. Integrated Services to ATM service mappings are covered in [6]. 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 10% of the total text.

Network Working Group L. Berger

Request for Comments: 2380 FORE Systems

Category: Standards Track August 1998

RSVP over ATM Implementation Requirements

Status of this Memo

This document specifies an Internet standards track protocol for the

Internet community, and requests discussion and suggestions for

improvements. Please refer to the current edition of the "Internet

Official Protocol Standards" (STD 1) for the standardization state

and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

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

Abstract

This memo presents specific implementation requirements for running

RSVP over ATM switched virtual circuits (SVCs). It presents

requirements that ensure interoperability between multiple

implementations and conformance to the RSVP and Integrated Services

specifications. A separate document [5] provides specific guidelines

for running over today's ATM networks. The general problem is

discussed in [9]. Integrated Services to ATM service mappings are

covered in [6]. The full set of documents present the background and

information needed to implement Integrated Services and RSVP over

ATM.

Table of Contents

1. Introduction ................................................. 2

1.1 Terms .................................................... 2

1.2 Assumptions .............................................. 3

2. General RSVP Session Support ................................. 4

2.1 RSVP Message VC Usage .................................... 4

2.2 VC Initiation ............................................ 4

2.3 VC Teardown .............................................. 5

2.4 Dynamic QoS .............................................. 6

2.5 Encapsulation ............................................ 6

3. Multicast RSVP Session Support ............................... 7

3.1 Data VC Management for Heterogeneous Sessions ............ 7

3.2 Multicast End-Point Identification ....................... 8

3.3 Multicast Data Distribution .............................. 9

3.4 Receiver Transitions ..................................... 11

4. Security Considerations ...................................... 11

5. Acknowledgments .............................................. 11

6. Author's Address ............................................. 12

REFERENCES ...................................................... 13

FULL COPYRIGHT STATEMENT ........................................ 14

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 [4] methods for supporting IP over ATM. The gener...