idnits 2.17.1 draft-ietf-diffserv-efresolve-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 3248 5 Title: A Delay Bound alternative revision of RFC 2598 6 Author(s): G. Armitage, B. Carpenter, A. Casati, 7 J. Crowcroft, J. Halpern, B. Kumar, J. Schnizlein 8 Status: Informational 9 Date: March 2002 10 Mailbox: garmitage@swin.edu.au, brian@hursley.ibm.com, 11 acasati@lucent.com, J.Crowcroft@cs.ucl.ac.uk, 12 joel@longsys.com, brijesh@coronanetworks.com, 13 john.schnizlein@cisco.com 14 Pages: 11 15 Characters: 21597 16 Updates/Obsoletes/SeeAlso: None 18 I-D Tag: draft-ietf-diffserv-efresolve-01.txt 20 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3248.txt 22 For historical interest, this document captures the EF Design Team's 23 proposed solution, preferred by the original authors of RFC 2598 but 24 not adopted by the working group in December 2000. The original 25 definition of EF was based on comparison of forwarding on an unloaded 26 network. This experimental Delay Bound (DB) PHB requires a bound on 27 the delay of packets due to other traffic in the network. At the 28 Pittsburgh IETF meeting in August 2000, the Differentiated Services 29 working group faced serious questions regarding RFC 2598 - the group's 30 standards track definition of the Expedited Forwarding (EF) Per Hop 31 Behavior (PHB). An 'EF Design Team' volunteered to develop a 32 re-expression of RFC 2598, bearing in mind the issues raised in the 33 DiffServ group. At the San Diego IETF meeting in December 2000 the 34 DiffServ working group decided to pursue an alternative re-expression 35 of the EF PHB. 37 This document is a product of the Differentiated Services Working 38 Group of the IETF. 40 This memo provides information for the Internet community. It does 41 not specify an Internet standard of any kind. Distribution of this 42 memo is unlimited. 44 This announcement is sent to the IETF list and the RFC-DIST list. 45 Requests to be added to or deleted from the IETF distribution list 46 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 47 added to or deleted from the RFC-DIST distribution list should 48 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 50 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 51 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 52 help: ways_to_get_rfcs. For example: 54 To: rfc-info@RFC-EDITOR.ORG 55 Subject: getting rfcs 57 help: ways_to_get_rfcs 59 Requests for special distribution should be addressed to either the 60 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 61 specifically noted otherwise on the RFC itself, all RFCs are for 62 unlimited distribution.echo 63 Submissions for Requests for Comments should be sent to 64 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 65 Authors, for further information.