Browse Prior Art Database

Interoperation of Controlled-Load Service and Guaranteed Service with ATM (RFC2381)

IP.com Disclosure Number: IPCOM000002953D
Original Publication Date: 1998-Aug-01
Included in the Prior Art Database: 2000-Sep-13

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Garrett: AUTHOR [+2]

Abstract

This document provides guidelines for mapping service classes, and traffic management features and parameters between Internet and ATM technologies. The service mappings are useful for providing effective interoperation and end-to-end Quality of Service for IP Integrated Services networks containing ATM subnetworks.

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

Network Working Group M. Garrett

Request for Comments: 2381 Bellcore

Category: Standards Track M. Borden

Bay Networks

August 1998

Interoperation of Controlled-Load Service

and Guaranteed Service with ATM

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 document provides guidelines for mapping service classes, and

traffic management features and parameters between Internet and ATM

technologies. The service mappings are useful for providing

effective interoperation and end-to-end Quality of Service for IP

Integrated Services networks containing ATM subnetworks.

The discussion and specifications given here support the IP

integrated services protocols for Guaranteed Service (GS),

Controlled-Load Service (CLS) and the ATM Forum UNI specification,

versions 3.0, 3.1 and 4.0. Some discussion of IP best effort service

over ATM is also included.

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 [1]. (Note,

in many cases the use of "MUST" or "REQUIRED" reflects our

interpretation of the requirements of a related standard, e.g., ATM

Forum UNI 4.0, rsvp, etc.)

Table of Contents

1.0 Introduction .................................................... 3

1.1 General System Architecture ................................. 4

1.2 Related Documents ........................................... 7

2.0 Major Protocol Features for Traffic Management and QoS .......... 8

2.1 Service Category and Bearer Capability ...................... 8

2.1.1 Service Categories for Guaranteed Service ............. 9

2.1.2 Service Categories for Controlled Load ................ 10

2.1.3 Service Categories for Best Effort .................... 11

2.2 Cell Loss Priority Bit, Tagging and Conformance Definitions . 11

2.3 ATM Adaptation Layer ........................................ 13

2.4 Broadband Low Layer Information ............................. 13

2.5 Traffic Descriptors ......................................... 13

2.5.1 Translating Traffic Descriptors for Guaranteed Service. 15

2.5.2 Translating Traffic Descriptors for Controlled Load

Service ................................................