Browse Prior Art Database

Per Hop Behavior Identification Codes (RFC2836)

IP.com Disclosure Number: IPCOM000003435D
Original Publication Date: 2000-May-01
Included in the Prior Art Database: 2019-Feb-13
Document File: 7 page(s) / 9K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Brim: AUTHOR [+2]

Related Documents

10.17487/RFC2836: DOI

Abstract

This document defines a binary encoding to uniquely identify PHBs (Per Hop Behaviors) and/or sets of PHBs in protocol messages. [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 26% of the total text.

Network Working Group S. Brim Request for Comments: 2836 B. Carpenter Category: Standards Track F. Le Faucheur May 2000

Per Hop Behavior Identification Codes

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 (2000). All Rights Reserved.

Table of Contents:

1. Introduction................................................. 1 1.1. Usage Scenarios............................................ 2 2. Encoding..................................................... 3 3. IANA Considerations.......................................... 4 4. Security considerations...................................... 4 References...................................................... 4 Authors’ Addresses.............................................. 5 Intellectual Property........................................... 6 Full Copyright Statement........................................ 7

1. Introduction

Differentiated Services [RFC 2474, RFC 2475] introduces the notion of Per Hop Behaviors (PHBs) that define how traffic belonging to a particular behavior aggregate is treated at an individual network node. In IP packet headers, PHBs are not indicated as such; instead Differentiated Services Codepoint (DSCP) values are used. There are only 64 possible DSCP values, but there is no such limit on the number of PHBs. In a given network domain, there is a locally defined mapping between DSCP values and PHBs. Standardized PHBs recommend a DSCP mapping, but network operators may choose alternative mappings.

Brim, et al. Standards Track [Page 1]

RFC 2836 Per Hop Behavior Identification Codes May 2000

In some cases it is necessary or desirable to identify a particular PHB in a protocol message, such as a message negotiating bandwidth management or path selection, especially when such messages pass between management domains. Examples where work is in progress include communication between bandwidth brokers, and MPLS support of diffserv.

In certain cases, what needs to be identified is not an individual PHB, but a set of PHBs. One example is a set of PHBs that must follow the same physical path to prevent re-ordering. An instance of this is the set of three PHBs belonging to a single Assured Forwarding class, such as the PHBs AF11, AF12 and AF13 [RFC 2597].

This document defines a binary encoding to uniquely identify PHBs and/or sets of PHBs in protocol messages. This encoding MUST be used when such identification is required.

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 [RFC2119].

1.1. Usage Scenarios

Diffs...

Processing...
Loading...