Browse Prior Art Database

New Terminology and Clarifications for Diffserv (RFC3260)

IP.com Disclosure Number: IPCOM000007695D
Original Publication Date: 2002-Apr-01
Included in the Prior Art Database: 2002-Apr-16
Document File: 11 page(s) / 22K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D. Grossman: AUTHOR

Abstract

This memo captures Diffserv working group agreements concerning new and improved terminology, and provides minor technical clarifications. It is intended to update RFC 2474, RFC 2475 and RFC 2597. When RFCs 2474 and 2597 advance on the standards track, and RFC 2475 is updated, it is intended that the revisions in this memo will be incorporated, and that this memo will be obsoleted by the new RFCs.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 15% of the total text.

Network Working Group                                        D. Grossman

Request for Comments: 3260                                Motorola, Inc.

Updates: 2474, 2475, 2597                                     April 2002

Category: Informational

            New Terminology and Clarifications for Diffserv

Status of this Memo

   This memo provides information for the Internet community.  It does

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

   memo is unlimited.

Copyright Notice

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

Abstract

   This memo captures Diffserv working group agreements concerning new

   and improved terminology, and provides minor technical

   clarifications.  It is intended to update RFC 2474, RFC 2475 and RFC

   2597.  When RFCs 2474 and 2597 advance on the standards track, and

   RFC 2475 is updated, it is intended that the revisions in this memo

   will be incorporated, and that this memo will be obsoleted by the new

   RFCs.

1.  Introduction

   As the Diffserv work has evolved, there have been several cases where

   terminology has needed to be created or the definitions in Diffserv

   standards track RFCs have needed to be refined.  Some minor technical

   clarifications were also found to be needed.  This memo was created

   to capture group agreements, rather than attempting to revise the

   base RFCs and recycle them at proposed standard.  It updates in part

   RFC 2474, RFC 2475 and RFC 2597.  RFC 2598 has been obsoleted by RFC

   3246, and clarifications agreed by the group were incorporated in

   that revision.

2. Terminology Related to Service Level Agreements (SLAs)

   The Diffserv Architecture [2] uses the term "Service Level Agreement"

   (SLA) to describe the "service contract... that specifies the

   forwarding service a customer should receive".  The SLA may include

   traffic conditioning rules which (at least in part) constitute a

   Traffic Conditioning Agreement (TCA).  A TCA is "an agreement

Grossman                     Informational                      [Page 1]

RFC 3260    New Terminology and Clarifications for Diffserv   April 2002

   specifying classifier rules and any corresponding traffic profiles

   and metering, marking, discarding and/or shaping rules which are to

   apply...."

   As work progressed in Diffserv (as well as in the Policy WG [6]), it

   came to be believed that the notion of an "agreement" implied

   considerations that were of a pricing, contractual or other business

   nature, as well as those that were strictly technical.  There also

   could be other technical considerations in such an agreement (e.g.,

   service availability) which are not addressed by Diffserv.  It was

   therefore agreed that the notions of SLAs and TCAs would be taken to

   represent the broader context, and that new terminology would be used

   to describe those elements of service and traffic conditioning that

   are addressed by Diffserv.

      -  A Service Level Specification (SLS) is a set of parameters and

         their values which together define the service offered to a

         traffic stream by a DS domain.

      -  A Traffic Conditioning Specification (TCS) is a set of

         parameters and their values which together specify a set of

         classifier rules and a traffic profile...