idnits 2.17.1 draft-ietf-diffserv-ef-supplemental-01.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3247 5 Title: Supplemental Information for the New Definition of 6 the EF PHB (Expedited Forwarding Per-Hop Behavior) 7 Author(s): A. Charny, J. Bennet, K. Benson, J. Boudec, 8 A. Chiu, W. Courtney, S. Davari, V. Firoiu, 9 C. Kalmanek, K. Ramakrishnan 10 Status: Informational 11 Date: March 2002 12 Mailbox: acharny@cisco.com, jcrb@motorola.com, 13 Kent.Benson@tellabs.com, 14 jean-yves.leboudec@epfl.ch, 15 angela.chiu@celion.com, 16 bill.courtney@trw.com, 17 sahram_davari@pmc-sierra.com, 18 vfiroiu@nortelnetworks.com, crk@research.att.com, 19 kk@teraoptic.com 20 Pages: 25 21 Characters: 53786 22 Updates/Obsoletes/SeeAlso: None 24 I-D Tag: draft-ietf-diffserv-ef-supplemental-01.txt 26 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3247.txt 28 This document was written during the process of clarification of 29 RFC 2598 "An Expedited Forwarding PHB" that led to the publication of 30 revised specification of EF "An Expedited Forwarding PHB". Its 31 primary motivation is providing additional explanation to the revised 32 EF definition and its properties. The document also provides 33 additional implementation examples and gives some guidance for 34 computation of the numerical parameters of the new definition for 35 several well known schedulers and router architectures. 37 This document is a product of the Differentiated Services Working 38 Group of the IETF. 40 This announcement is sent to the IETF list and the RFC-DIST list. 41 Requests to be added to or deleted from the IETF distribution list 42 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 43 added to or deleted from the RFC-DIST distribution list should 44 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 46 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 47 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 48 help: ways_to_get_rfcs. For example: 50 To: rfc-info@RFC-EDITOR.ORG 51 Subject: getting rfcs 53 help: ways_to_get_rfcs 55 Requests for special distribution should be addressed to either the 56 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 57 specifically noted otherwise on the RFC itself, all RFCs are for 58 unlimited distribution.echo 59 Submissions for Requests for Comments should be sent to 60 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 61 Authors, for further information.