Per Hop Behavior Identification Codes
The information below is for an old version of the document that is already published as an RFC.
This is an older version of an Internet-Draft that was ultimately published as RFC 3140.
|Authors||Brian E. Carpenter , Scott W. Brim , David L. Black , François Le Faucheur|
|Last updated||2013-03-02 (Latest revision 2001-05-09)|
|RFC stream||Internet Engineering Task Force (IETF)|
|IESG||IESG state||RFC 3140 (Proposed Standard)|
|Send notices to||(None)|
A new Request for Comments is now available in online RFC libraries. RFC 3140 Title: Per Hop Behavior Identification Codes Author(s): D. Black, S. Brim, B. Carpenter, F. Le Faucheur Status: Standards Track Date: June 2001 Mailbox: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com Pages: 8 Characters: 16586 Obsoletes: 2836 I-D Tag: draft-ietf-diffserv-2836bis-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3140.txt This document defines a 16 bit encoding mechanism for the identification of differentiated services Per Hop Behaviors in protocol messages. It replaces RFC 2836. This document is a product of the Differentiated Services Working Group of the IETF. This is now a Proposed Standard Protocol. 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. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information.