idnits 2.17.1 draft-ietf-diffserv-pdb-def-03.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 3086 5 Title: Definition of Differentiated Services Per Domain 6 Behaviors and Rules for their Specification 7 Author(s): K. Nichols, B. Carpenter 8 Status: Informational 9 Date: April 2001 10 Mailbox: nichols@packetdesign.com, brian@icair.org 11 Pages: 24 12 Characters: 63122 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-diffserv-pdb-def-03.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3086.txt 19 The differentiated services framework enables quality-of-service 20 provisioning within a network domain by applying rules at the edges to 21 create traffic aggregates and coupling each of these with a specific 22 forwarding path treatment in the domain through use of a codepoint in 23 the IP header. The diffserv WG has defined the general architecture 24 for differentiated services and has focused on the forwarding path 25 behavior required in routers, known as "per-hop forwarding behaviors" 26 (or PHBs). The WG has also discussed functionality required at 27 diffserv (DS) domain edges to select (classifiers) and condition 28 (e.g., policing and shaping) traffic according to the rules. 29 Short-term changes in the QoS goals for a DS domain are implemented by 30 changing only the configuration of these edge behaviors without 31 necessarily reconfiguring the behavior of interior network nodes. 33 The next step is to formulate examples of how forwarding path 34 components (PHBs, classifiers, and traffic conditioners) can be used 35 to compose traffic aggregates whose packets experience specific 36 forwarding characteristics as they transit a differentiated services 37 domain. The WG has decided to use the term per-domain behavior, or 38 PDB, to describe the behavior experienced by a particular set of 39 packets as they cross a DS domain. A PDB is characterized by specific 40 metrics that quantify the treatment a set of packets with a particular 41 DSCP (or set of DSCPs) will receive as it crosses a DS domain. A PDB 42 specifies a forwarding path treatment for a traffic aggregate and, due 43 to the role that particular choices of edge and PHB configuration play 44 in its resulting attributes, it is where the forwarding path and the 45 control plane interact. The measurable parameters of a PDB should be 46 suitable for use in Service Level Specifications at the network edge. 48 This document defines and discusses Per-Domain Behaviors in detail 49 and lays out the format and required content for contributions 50 to the Diffserv WG on PDBs and the procedure that will be applied 51 for individual PDB specifications to advance as WG products. This 52 format is specified to expedite working group review of PDB 53 submissions. 55 This document is a product of the Differentiated Services Working 56 Group of the IETF. 58 This memo provides information for the Internet community. It does 59 not specify an Internet standard of any kind. Distribution of this 60 memo is unlimited. 62 This announcement is sent to the IETF list and the RFC-DIST list. 63 Requests to be added to or deleted from the IETF distribution list 64 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 65 added to or deleted from the RFC-DIST distribution list should 66 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 68 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 69 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 70 help: ways_to_get_rfcs. For example: 72 To: rfc-info@RFC-EDITOR.ORG 73 Subject: getting rfcs 75 help: ways_to_get_rfcs 77 Requests for special distribution should be addressed to either the 78 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 79 specifically noted otherwise on the RFC itself, all RFCs are for 80 unlimited distribution.echo 81 Submissions for Requests for Comments should be sent to 82 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 83 Authors, for further information.