RFC 2836: Per Hop Behavior Identification Codes
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3140.
Current version: RFC 3140 — Per Hop Behavior Identification Codes
In plain English — editorial summary, not part of the RFC
This document defines a binary encoding to uniquely identify PHBs (Per Hop Behaviors) and/or sets of PHBs in protocol messages. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2836
- Published
- May 2000
- Authors
- S. Brim; B. Carpenter; F. Le Faucheur
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 7
- Also known as
- —
- Obsoleted by:
- RFC 3140
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4594Configuration Guidelines for DiffServ Service ClassesUpdated
August 2006
- RFC 2688Integrated Services Mappings for Low Speed NetworksCurrent
September 1999
- RFC 2598An Expedited Forwarding PHBObsoleted
June 1999
- RFC 2597Assured Forwarding PHB GroupUpdated
June 1999
- RFC 3246An Expedited Forwarding PHB (Per-Hop Behavior)Current
March 2002
- RFC 3248A Delay Bound alternative revision of RFC 2598Current
March 2002
- RFC 2205Resource ReSerVation Protocol (RSVP) -- Version 1 Functional SpecificationUpdated
September 1997
- RFC 2203RPCSEC_GSS Protocol SpecificationUpdated
September 1997
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?