Interoperation of Controlled-Load Service and Guaranteed Service with ATM
RFC 2381

Document Type RFC - Proposed Standard (August 1998; No errata)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 2381 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
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.)

Garrett & Borden            Standards Track                     [Page 1]
RFC 2381         Interoperation of CLS and GS with ATM       August 1998

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  .............................................. 18
        2.5.3 Translating Traffic Descriptors for Best Effort Service 19
    2.6 QoS Classes and Parameters .................................. 19
    2.7 Additional Parameters -- Frame Discard Mode ................. 22
3.0 Additional IP-Integrated Services Protocol Features ............. 22
    3.1 Path Characterization Parameters for IP Integrated Services . 22
    3.2 Handling of Excess Traffic .................................. 24
    3.3 Use of Guaranteed Service Adspec Parameters and Slack Term .. 25
4.0 Miscellaneous Items ............................................. 26
    4.1 Units Conversion ............................................ 26
5.0 Summary of ATM VC Setup Parameters for Guaranteed Service ....... 27
    5.1 Encoding GS Using Real-Time VBR ............................. 28
    5.2 Encoding GS Using CBR ....................................... 29
    5.3 Encoding GS Using Non-Real-Time VBR ......................... 30
    5.4 Encoding GS Using ABR ....................................... 30
    5.5 Encoding GS Using UBR ....................................... 30
    5.6 Encoding GS Using UNI 3.0 and UNI 3.1. ...................... 31
6.0 Summary of ATM VC Setup Parameters for Controlled Load Service .. 32
    6.1 Encoding CLS Using Non-Real-Time VBR ........................ 32
    6.2 Encoding CLS Using ABR ...................................... 33
    6.3 Encoding CLS Using CBR ...................................... 35
    6.4 Encoding CLS Using Real-Time VBR ............................ 35
    6.5 Encoding CLS Using UBR ...................................... 35
    6.6 Encoding CLS Using UNI 3.0 and UNI 3.1. ..................... 35
7.0 Summary of ATM VC Setup Parameters for Best Effort Service ...... 36
    7.1 Encoding Best Effort Service Using UBR ...................... 37
Show full document text