--- 1/draft-ietf-dime-qos-attributes-11.txt 2009-06-05 22:12:11.000000000 +0200 +++ 2/draft-ietf-dime-qos-attributes-12.txt 2009-06-05 22:12:11.000000000 +0200 @@ -1,88 +1,84 @@ Diameter Maintenance and J. Korhonen Extensions (DIME) H. Tschofenig Internet-Draft Nokia Siemens Networks Intended status: Standards Track M. Arumaithurai -Expires: August 27, 2009 University of Goettingen +Expires: December 7, 2009 University of Goettingen M. Jones, Ed. A. Lior Bridgewater Systems - February 23, 2009 + June 5, 2009 Quality of Service Attributes for Diameter - draft-ietf-dime-qos-attributes-11.txt + draft-ietf-dime-qos-attributes-12.txt Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the - provisions of BCP 78 and BCP 79. + provisions of BCP 78 and BCP 79. This document may contain material + from IETF Documents or IETF Contributions published or made publicly + available before November 10, 2008. The person(s) controlling the + copyright in some of this material may not have granted the IETF + Trust the right to allow modifications of such material outside the + IETF Standards Process. Without obtaining an adequate license from + the person(s) controlling the copyright in such materials, this + document may not be modified outside the IETF Standards Process, and + derivative works of it may not be created outside the IETF Standards + Process, except to format it for publication as an RFC or to + translate it into languages other than English. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. - This Internet-Draft will expire on August 27, 2009. + This Internet-Draft will expire on December 7, 2009. Copyright Notice - Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal - Provisions Relating to IETF Documents - (http://trustee.ietf.org/license-info) in effect on the date of - publication of this document. Please review these documents - carefully, as they describe your rights and restrictions with respect - to this document. - - This document may contain material from IETF Documents or IETF - Contributions published or made publicly available before November - 10, 2008. The person(s) controlling the copyright in some of this - material may not have granted the IETF Trust the right to allow - modifications of such material outside the IETF Standards Process. - Without obtaining an adequate license from the person(s) controlling - the copyright in such materials, this document may not be modified - outside the IETF Standards Process, and derivative works of it may - not be created outside the IETF Standards Process, except to format - it for publication as an RFC or to translate it into languages other - than English. + Provisions Relating to IETF Documents in effect on the date of + publication of this document (http://trustee.ietf.org/license-info). + Please review these documents carefully, as they describe your rights + and restrictions with respect to this document. Abstract This document extends the IPFilterRule AVP functionality of the Diameter Base protocol and the functionality of the QoS-Filter-Rule AVP defined in RFC 4005. The ability to convey Quality of Service information using the AVPs defined in this document is available to existing and future Diameter applications where permitted by the command ABNF. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Rule Sets and Rules . . . . . . . . . . . . . . . . . . . . . 5 3.1. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 5 - 3.2. Rule AVP . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 3.3. Rule-Precedence AVP . . . . . . . . . . . . . . . . . . . 6 + 3.2. QoS-Rule AVP . . . . . . . . . . . . . . . . . . . . . . . 6 + 3.3. QoS-Rule-Precedence AVP . . . . . . . . . . . . . . . . . 6 4. Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4.1. Traffic Classifiers . . . . . . . . . . . . . . . . . . . 7 4.1.1. Classifier AVP . . . . . . . . . . . . . . . . . . . . 9 4.1.2. Classifier-ID AVP . . . . . . . . . . . . . . . . . . 10 4.1.3. Protocol AVP . . . . . . . . . . . . . . . . . . . . . 10 4.1.4. Direction AVP . . . . . . . . . . . . . . . . . . . . 10 4.1.5. From-Spec AVP . . . . . . . . . . . . . . . . . . . . 10 4.1.6. To-Spec AVP . . . . . . . . . . . . . . . . . . . . . 11 4.1.7. Source and Destination AVPs . . . . . . . . . . . . . 12 4.1.8. Header Option AVPs . . . . . . . . . . . . . . . . . . 16 @@ -91,154 +87,154 @@ 4.2.2. Time-Of-Day-Start AVP . . . . . . . . . . . . . . . . 24 4.2.3. Time-Of-Day-End AVP . . . . . . . . . . . . . . . . . 24 4.2.4. Day-Of-Week-Mask AVP . . . . . . . . . . . . . . . . . 24 4.2.5. Day-Of-Month-Mask AVP . . . . . . . . . . . . . . . . 25 4.2.6. Month-Of-Year-Mask AVP . . . . . . . . . . . . . . . . 25 4.2.7. Absolute-Start-Time AVP . . . . . . . . . . . . . . . 25 4.2.8. Absolute-End-Time AVP . . . . . . . . . . . . . . . . 26 4.2.9. Timezone-Flag AVP . . . . . . . . . . . . . . . . . . 26 4.2.10. Timezone-Offset AVP . . . . . . . . . . . . . . . . . 26 5. Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 - 5.1. Action AVP . . . . . . . . . . . . . . . . . . . . . . . . 26 + 5.1. QoS-Action AVP . . . . . . . . . . . . . . . . . . . . . . 26 5.2. QoS-Profile-Id AVP . . . . . . . . . . . . . . . . . . . . 27 - 5.3. QoS-Profile-Template AVP . . . . . . . . . . . . . . . . . 28 + 5.3. QoS-Profile-Template AVP . . . . . . . . . . . . . . . . . 27 5.4. QoS-Semantics . . . . . . . . . . . . . . . . . . . . . . 28 5.5. QoS-Parameters AVP . . . . . . . . . . . . . . . . . . . . 29 5.6. Excess-Treatment AVP . . . . . . . . . . . . . . . . . . . 29 - 5.7. Excess-Treatment-Action . . . . . . . . . . . . . . . . . 30 - 6. QoS Capability Indication . . . . . . . . . . . . . . . . . . 31 - 7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 - 7.1. Diameter EAP with QoS Information . . . . . . . . . . . . 31 - 7.2. Diameter NASREQ with QoS Information . . . . . . . . . . . 32 - 7.3. QoS Authorization . . . . . . . . . . . . . . . . . . . . 33 - 7.4. Diameter Server Initiated Re-authorization of QoS . . . . 34 - 7.5. Diameter Credit Control with QoS Information . . . . . . . 35 - 7.6. Classifier Examples . . . . . . . . . . . . . . . . . . . 36 - 7.7. QoS Examples . . . . . . . . . . . . . . . . . . . . . . . 37 - 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 38 - 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 38 - 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38 - 11. Security Considerations . . . . . . . . . . . . . . . . . . . 41 - 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 41 - 12.1. Normative References . . . . . . . . . . . . . . . . . . . 41 - 12.2. Informative References . . . . . . . . . . . . . . . . . . 42 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 42 + 6. QoS Capability Indication . . . . . . . . . . . . . . . . . . 30 + 7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 + 7.1. Diameter EAP with QoS Information . . . . . . . . . . . . 30 + 7.2. Diameter NASREQ with QoS Information . . . . . . . . . . . 31 + 7.3. QoS Authorization . . . . . . . . . . . . . . . . . . . . 32 + 7.4. Diameter Server Initiated Re-authorization of QoS . . . . 33 + 7.5. Diameter Credit Control with QoS Information . . . . . . . 34 + 7.6. Classifier Examples . . . . . . . . . . . . . . . . . . . 35 + 7.7. QoS Examples . . . . . . . . . . . . . . . . . . . . . . . 36 + 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 37 + 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 37 + 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 + 11. Security Considerations . . . . . . . . . . . . . . . . . . . 39 + 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 40 + 12.1. Normative References . . . . . . . . . . . . . . . . . . . 40 + 12.2. Informative References . . . . . . . . . . . . . . . . . . 40 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 41 1. Introduction This document defines a number of Diameter Quality of Service (QoS) related AVPs that can be used in existing and future Diameter applications where permitted by the ABNF of a command. The IPFilterRule AVP, defined in RFC 3588 [RFC3588], and the QoS-Filter- Rule AVP, defined in RFC 4005 [RFC4005], provide basic support for classification and QoS already. The classification rule syntax is a modified subset of FreeBSD ipfw packet filter implementation. The QoS functionality provided by the IPFilterRule AVP was updated by the - QoS-Filter-Rule AVP. The Rule AVP offers an extended way of + QoS-Filter-Rule AVP. The QoS-Rule AVP offers an extended way of expressing classification and QoS capabilities. - The structure of a rule in the entire rule set defined in this - document consist of a conditions part and corresponding actions. The - AVPs responsible for expressing a condition are defined in Section 4. - Capabilities to match all or a subset of the data traffic is - provided. Additionally, time-based conditions can be expressed based - on the functionality offered in Section 4.2. The action part of a - rule contains information for handling conflict resolution, such as a - priority value for each individual rule within a rule set, and - further description regarding QoS related actions. + The QoS-Resources AVP represents a complete rule set with each rule + represented by a QoS-Rule AVP. Each rule consists of a conditions + part and the corresponding actions to be performed if the conditions + are satisfied. The AVPs responsible for expressing a condition are + defined in Section 4. Capabilities to match all or a subset of the + data traffic is provided. Additionally, time-based conditions can be + expressed based on the functionality offered in Section 4.2. The + action part of a rule contains information for handling conflict + resolution, such as a priority value for each individual rule within + a rule set, and further description regarding QoS related actions. 2. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 3. Rule Sets and Rules As mentioned in the introduction the top-level element is the QoS- - Resources AVP that encapsulates one or more Rule AVPs. + Resources AVP that encapsulates one or more QoS-Rule AVPs. 3.1. QoS-Resources AVP The QoS-Resources AVP (AVP Code TBD) is of type Grouped and describes a list of policies. QoS-Resources ::= < AVP Header: XXX > - 1*{ Rule } + 1*{ QoS-Rule } * [ AVP ] -3.2. Rule AVP +3.2. QoS-Rule AVP - The Rule AVP (AVP Code TBD) is of type Grouped and defines a specific - condition and action combination. + The QoS-Rule AVP (AVP Code TBD) is of type Grouped and defines a + specific condition and action combination. - Rule ::= < AVP Header: XXX > - [ Rule-Precedence ] + QoS-Rule ::= < AVP Header: XXX > + [ QoS-Rule-Precedence ] ; Condition part of a Rule ; ------------------------ [ Classifier ] * [ Time-Of-Day-Condition ] ; Action and Meta-Data ; -------------------- - [ Action ] + [ QoS-Action ] ; Info about QoS related Actions ; ------------------------------ [ QoS-Semantics ] [ QoS-Profile-Template ] [ QoS-Parameters ] [ Excess-Treatment ] ; Extension Point ; --------------- * [ AVP ] - If the QoS-Profile-Template AVP is not included in the Rule AVP then - the default setting is assumed, namely a setting of the Vendor-Id AVP - to 0 (for IETF) and the QoS-Profile-Id AVP to zero (0) (for the - profile defined in [I-D.ietf-dime-qos-parameters]). Note that the - content of the QoS-Parameters are defined in the respective + If the QoS-Profile-Template AVP is not included in the Qos-Rule AVP + then the default setting is assumed, namely a setting of the + Vendor-Id AVP to 0 (for IETF) and the QoS-Profile-Id AVP to zero (0) + (for the profile defined in [I-D.ietf-dime-qos-parameters]). Note + that the content of the QoS-Parameters are defined in the respective specification defining the QoS parameters. When the Vendor-Id AVP is set to 0 (for IETF) and the QoS-Profile-Id AVP is set to zero (0) then the AVPs included in the QoS-Parameters AVP are the AVPs defined in [I-D.ietf-dime-qos-parameters]. -3.3. Rule-Precedence AVP +3.3. QoS-Rule-Precedence AVP - The Rule-Precedence AVP (AVP Code TBD) is of type Unsigned32 and + The QoS-Rule-Precedence AVP (AVP Code TBD) is of type Unsigned32 and specifies the execution order of the rules expressed in the QoS- - Resources AVP. Rules with equal precedence MAY be executed in - parallel if supported by the Resource Management Function. If the - Rule-Precedence AVP is absent from the Rule AVP, the rules SHOULD be - executed in the order in which they appear in the QoS-Resources AVP. - The lower the numerical value of Rule-Precedence AVP, the higher the - rule precedence. + Resources AVP. The lower the numerical value of QoS-Rule-Precedence + AVP, the higher the rule precedence. Rules with equal precedence MAY + be executed in parallel if supported by the Resource Management + Function. If the QoS-Rule-Precedence AVP is absent from the QoS-Rule + AVP, the rules SHOULD be executed in the order in which they appear + in the QoS-Resources AVP. 4. Conditions This section describes the condition part of a rule. Two condition types are introduced by this document: packet classification conditions represented by the Classifier AVP and time of day conditions represented by the Time-Of-Day-Condition AVP. If more than one instance of the Time-Of-Day-Condition AVP is present - in the Rule AVP, the current time at QoS rule evaluation MUST be + in the QoS-Rule AVP, the current time at QoS rule evaluation MUST be within at least one of the time windows specified in one of the Time- Of-Day-Condition AVPs. When the Time-Of-Day-Condition AVP and Classifier AVP are present in - the same Rule AVP, both the time of day and packet classification + the same QoS-Rule AVP, both the time of day and packet classification conditions MUST match for the QoS specification action to be applied. 4.1. Traffic Classifiers Classifiers are used in many applications to specify how to select a subset of data packets for subsequent treatment as indicated in the action part of a rule. For example in a QoS application, if a packet matches a classifier then that packet will be treated in accordance with a QoS specification associated with that classifier. Figure 1 shows a typical deployment. @@ -259,22 +255,22 @@ +------+------+ | | | AAA | | | +-------------+ Figure 1: Example of a Classifier Architecture The managed terminal, the terminal for which the classifiers are being specified is located on the left of the Classifying Entity. - The unmanaged terminal, the terminal that receives packets from the - Managed terminal or sends packets to the managed terminal is located + The unmanaged terminals, the terminals that receive packets from the + Managed terminal or send packets to the managed terminal are located to the right side of the Classifying Entity. The Classifying Entity is responsible for classifying packets that are incoming (IN) from the Managed Terminal or packets outgoing (OUT) to the Managed Terminal. A Classifier consists of a group of attributes that specify how to match a packet. Each set of attributes expresses values about aspects of the packet - typically the packet header. Different protocols therefore would use different attributes. @@ -358,21 +354,21 @@ 4.1.4. Direction AVP The Direction AVP (AVP Code TBD) is of type Enumerated and specifies in which direction to apply the Classifier. The values of the enumeration are: "IN","OUT","BOTH". In the "IN" and "BOTH" directions, the From-Spec refers to the address of the Managed Terminal and the To-Spec refers to the unmanaged terminal. In the "OUT" direction, the From-Spec refers to the Unmanaged Terminal whereas the To-Spec refers to the Managed Terminal. If the Direction AVP is omitted, the Classifier matches packets flowing in both - direction. + directions. Value | Name and Semantic ------+-------------------------------------------------- 0 | IN - The classifier applies to flows from the | Managed Terminal. 1 | OUT - The classifier applies to flows to the | Managed Terminal. 2 | BOTH - The classifier applies to flows both to | and from the Managed Terminal. @@ -504,23 +500,20 @@ specified IP-Address-End address. If the IP-Address-End AVP is not included then the address range starts at the address specified by the IP-Address-Start AVP and includes all the remaining valid IP addresses. For the IP-Address-Range AVP to be valid, the IP-Address-Start AVP MUST contain a value that is less than that of the IP-Address-End AVP. - If the IP-Address-Start AVP is empty then the semantic is equivalent - to not having the IP-Address-Start AVP included in the command. - 4.1.7.4. IP-Address-Start AVP The IP-Address-Start AVP (AVP Code TBD) is of type Address and specifies the first IP address (IPv4 or IPv6) address of an IP address range. 4.1.7.5. IP-Address-End AVP The IP-Address-End AVP (AVP Code TBD) is of type Address and specifies the last IP address (IPv4 or IPv6) address of an address @@ -612,23 +605,20 @@ inclusive range of ports. Port-Range ::= < AVP Header: XXX > [ Port-Start ] [ Port-End ] * [ AVP ] If the Port-Start AVP is omitted then port 0 is assumed. If the Port-End AVP is omitted then port 65535 is assumed. - If the Port-Start AVP is empty then this is equivalent to not - carrying a Port-Start AVP in the command. - 4.1.7.16. Port-Start AVP The Port-Start AVP (AVP Code TBD) is of type Integer32 and specifies the first port number of an IP port range. 4.1.7.17. Port-End AVP The Port-End AVP (AVP Code TBD) is of type Integer32 and specifies the last port number of an IP port range. @@ -800,40 +790,40 @@ in [RFC2780]. 4.1.8.14. ETH-Option AVP The ETH-Option AVP (AVP Code TBD) is of type Grouped and specifies Ethernet specific attributes. ETH-Option ::= < AVP Header: XXX > { ETH-Proto-Type } * [ VLAN-ID-Range ] - * [ ETH-Priority-Range ] + * [ User-Priority-Range ] * [ AVP ] 4.1.8.15. ETH-Proto-Type AVP The Eth-Proto-Type AVP (AVP Code TBD) is of type Grouped and specifies the encapsulated protocol type. ETH-Ether-Type and ETH-SAP are mutually exclusive. ETH-Proto-Type ::= < AVP Header: XXX > * [ ETH-Ether-Type ] * [ ETH-SAP ] * [ AVP ] 4.1.8.16. ETH-Ether-Type AVP The ETH-Ether-Type AVP (AVP Code TBD) is of type OctetString. The - value is a double octet the contains the value of the Ethertype field - in the packet to match. This AVP MAY be present in the case of DIX - or if SNAP is present at 802.2 but the ETH-SAP AVP MUST NOT be + value is a double octet that contains the value of the Ethertype + field in the packet to match. This AVP MAY be present in the case of + DIX or if SNAP is present at 802.2 but the ETH-SAP AVP MUST NOT be present in this case. 4.1.8.17. ETH-SAP AVP The ETH-SAP AVP (AVP Code TBD) is of type OctetString. The value is a double octet representing the 802.2 SAP as specified in [IEEE802.2]. The first octet contains the DSAP and the second the SSAP. 4.1.8.18. VLAN-ID-Range AVP @@ -922,44 +912,44 @@ The C-VID-Start AVP (AVP Code TBD) is of type Unsigned32. The value MUST be in the range from 0 to 4095. The value of this AVP specifies the start value of the range of C-VID VLAN-IDs to be matched. 4.1.8.22. C-VID-End AVP The C-VID-End AVP (AVP Code TBD) is of type Unsigned32. The value MUST be in the range from 0 to 4095. The value of this AVP specifies the end value of the range of C-VID VLAN-IDs to be matched. -4.1.8.23. ETH-Priority-Range AVP +4.1.8.23. User-Priority-Range AVP - The ETH-Priority-Range AVP (AVP Code TBD) is of type Grouped and + The User-Priority-Range AVP (AVP Code TBD) is of type Grouped and specifies an inclusive range to match the user_priority parameter specified in [IEEE802.1D]. An Ethernet packet containing the user_priority parameter matches this Classifier if the value is - greater than or equal to ETH-Low-Priority and less than or equal to - ETH-High-Priority. If this AVP is omitted, then comparison of the + greater than or equal to Low-User-Priority and less than or equal to + High-User-Priority. If this AVP is omitted, then comparison of the IEEE 802.1D user_priority parameter for this Classifier is irrelevant. - ETH-Priority-Range ::= < AVP Header: XXX > - * [ ETH-Low-Priority ] - * [ ETH-High-Priority ] + User-Priority-Range ::= < AVP Header: XXX > + * [ Low-User-Priority ] + * [ High-User-Priority ] * [ AVP ] -4.1.8.24. ETH-Low-Priority AVP +4.1.8.24. Low-User-Priority AVP - The ETH-Low-Priority AVP (AVP Code TBD) is of type Unsigned32. The + The Low-User-Priority AVP (AVP Code TBD) is of type Unsigned32. The value MUST be in the range from 0 to 7. -4.1.8.25. ETH-High-Priority AVP +4.1.8.25. High-User-Priority AVP - The ETH-High-Priority AVP (AVP Code TBD) is of type Unsigned32. The + The High-User-Priority AVP (AVP Code TBD) is of type Unsigned32. The value MUST be in the range from 0 to 7. 4.2. Time Of Day AVPs In many QoS applications, the QoS specification applied to the traffic flow is conditional upon the time of day when the flow was observed. The following sections define AVPs that can be used to express one or more time windows which determine when a QoS specification is applicable to a traffic flow. @@ -1106,95 +1096,90 @@ Time-Of-Day-Start, Time-Of-Day-End, Day-Of-Week-Mask, Day-Of-Month- Mask and Month-Of-Year-Mask AVPs. This AVP MUST be present if the Timezone-Flag AVP is set to OFFSET. 5. Actions This section illustrates the actions associated with a rule. This document only defines QoS specific actions but further actions can be specified as extensions. -5.1. Action AVP +5.1. QoS-Action AVP - The Action AVP (AVP Code TBD) is of type Enumerated and lists the + The QoS-Action AVP (AVP Code TBD) is of type Enumerated and lists the actions that are associated with the condition part of a rule. The following actions are defined in this document: 0: drop 1: shape - 2: police 2: mark drop: All traffic that is met by the condition part of a rule MUST be dropped. This action implements firewalling functionality. shape: [RFC2475] describes shaping as "the process of delaying packets within a traffic stream to cause it to conform to some defined traffic profile". When the action is set to 'shape', it is expected that the QoS-Parameters AVP carries QoS information to indicate how to shape the traffic indicated in the condition part of the rule. - police: - - [RFC2475] describes policing as "the process of discarding packets - (by a dropper) within a traffic stream in accordance with the - state of a corresponding meter enforcing a traffic profile". When - the action is set to 'police', it is expected that the QoS- - Parameters AVP carries QoS information to describe traffic - conforming to a traffic profile. Excess traffic is dropped. - Hence, there is no need to include the Excess-Treatement AVP with - the Excess-Treatment-Action AVP set to 'drop' as this - functionality is implied. mark: [RFC2475] describes marking as "the process of setting the DS codepoint in a packet based on defined rules". When the action is set to 'mark', it is expected that the QoS-Parameters AVP carries information about the DiffServ marking. Further action values can be registered, as described in - Section 10.4. + Section 10.3. + + [RFC2475] also describes an action called "policing" as "the process + of discarding packets (by a dropper) within a traffic stream in + accordance with the state of a corresponding meter enforcing a + traffic profile". This behavior in modeled in the QoS-Rule through + the inclusion of the Excess-Treatment AVP containing a QoS-Action AVP + set to "drop". 5.2. QoS-Profile-Id AVP The QoS-Profile-Id AVP (AVP Code TBD) is of type Unsigned32 and contains a QoS profile template identifier. An initial QoS profile template is defined with value of 0 and can be found in [I-D.ietf-dime-qos-parameters]. The registry for the QoS profile templates is created with the same document. 5.3. QoS-Profile-Template AVP The QoS-Profile-Template AVP (AVP Code TBD) is of type Grouped and defines the namespace of the QoS profile (indicated in the Vendor-ID AVP) followed by the specific value for the profile. - The Vendor-Id AVP contains a 32 bit IANA SMI Network Management - Private Enterprise Code and the QoS-Profile-Id AVP contains the - template identifier assigned by the vendor. The vendor identifier of - zero (0) is used for the IETF. + The Vendor-Id AVP contains a 32 bit IANA Private Enterprise Number + (PEN) and the QoS-Profile-Id AVP contains the template identifier + assigned by the vendor. The vendor identifier of zero (0) is used + for the IETF. QoS-Profile-Template ::= < AVP Header: XXX > { Vendor-Id } { QoS-Profile-Id } * [ AVP ] 5.4. QoS-Semantics The QoS-Semantics AVP (AVP Code TBD) is of type Enumerated and provides the semantics for the QoS-Profile-Template and QoS- - Parameters AVPs in the Rule AVP. + Parameters AVPs in the QoS-Rule AVP. This document defines the following values: (0): QoS-Desired (1): QoS-Available (2): QoS-Reserved (3): Minimum-QoS (4): QoS-Authorized The semantic of the QoS parameters depend on the information provided @@ -1242,71 +1227,33 @@ QoS-Parameters ::= < AVP Header: XXX > * [ AVP ] 5.6. Excess-Treatment AVP The Excess-Treatment AVP (AVP Code TBD) is of type grouped and indicates how out-of-profile traffic, i.e. traffic not covered by the original QoS-Profile-Template and QoS-Parameters AVPs, is treated. - The additional QoS-Profile-Template and QoS-Parameters AVPs carried - inside the Excess-Treatment AVP provide information about the QoS - treatment of the excess traffic. In case the Excess-Treatment AVP is - absent then the treatment of the out-of-profile traffic is left to - the discretion of the node performing QoS treatment. + The additional QoS-Action, QoS-Profile-Template and QoS-Parameters + AVPs carried inside the Excess-Treatment AVP provide information + about the QoS treatment of the excess traffic. In case the Excess- + Treatment AVP is absent then the treatment of the out-of-profile + traffic is left to the discretion of the node performing QoS + treatment. Excess-Treatment ::= < AVP Header: XXX > - { Excess-Treatment-Action } + { QoS-Action } [ QoS-Profile-Template ] [ QoS-Parameters ] * [ AVP ] -5.7. Excess-Treatment-Action - - The Excess-Treatment-Action AVP (AVP Code TBD) is of type Enumerated - and lists the actions about how the out-of-traffic regarding a - specific QoS profile is treated. - - 0: drop - 1: shape - 2: mark - - drop: - - When excess treatment action is set to 'drop', excess traffic is - dropped. - - shape: - - When excess treatment action is set to 'shape', it is expected - that the QoS-Parameters AVP carries information on how to shape - the excess traffic. For example, the TMOD AVP, defined in - [I-D.ietf-dime-qos-parameters], carried inside the QoS-Parameters - AVP of the Excess-Treatment AVP indicates how to shape the excess - traffic. Note that shaping might cause unbounded queue growth at - the shaper and consequently traffic may still get dropped. - - mark: - - When excess treatment action is set to 'mark', it is expected that - the QoS-Parameters AVP carries information about the QoS class. - For example, excess traffic may need to get marked differently to - the traffic conformant to the traffic profile. - - When the Excess-Treatment AVP is omitted then excess treatment is - essentially unspecified and there are no guaranted behavior with - regard to excess traffic, i.e., a QoS aware node can do what it finds - suitable. - - Further values can be registered, as described in Section 10.3. - 6. QoS Capability Indication The QoS-Capability AVP (AVP Code TBD) is of type Grouped and contains a list of supported Quality of Service profile templates (and therefore the support of the respective parameter AVPs). The QoS-Capability AVP may be used for a simple announcement of the QoS capabilities and QoS profiles supported by a peer. It may also be used to negotiate a mutually supported set of QoS capabilities and QoS profiles between two peers. In such a case, handling of failed @@ -1325,22 +1272,22 @@ Control applications message exchanges. The signalling flows for the Diameter QoS Application are described in [I-D.ietf-dime-diameter-qos]. 7.1. Diameter EAP with QoS Information Figure 2 shows a simple signaling flow where a NAS (Diameter Client) announces its QoS awareness and capabilities included into the DER message and as part of the access authentication procedure. Upon completion of the EAP exchange, the Diameter Server provides a pre- - provisioned QoS profile with the QoS-Semantics in the Rule AVP set to - "QoS-Authorized", to the NAS in the final DEA message. + provisioned QoS profile with the QoS-Semantics in the QoS-Rule AVP + set to "QoS-Authorized", to the NAS in the final DEA message. End Diameter Diameter Host Client Server | | | | (initiate EAP) | | |<----------------------------->| | | | Diameter-EAP-Request | | | EAP-Payload(EAP Start) | | | QoS-Capability | | |------------------------------->| @@ -1582,40 +1529,38 @@ 7.7. QoS Examples The following high level description aims to illustrate the interworking between the Diameter QoS AVPs defined in this document and the QoS parameters defined in [I-D.ietf-dime-qos-parameters]. Consider the following example where a rule should be installed that limits traffic to 1 Mbit/sec and where out-of-profile traffic shall be dropped.The Classifers are ignored in this example. - This would require the Action AVP to be set to 'police' (which also - implies the Excess-Treatment-Action AVP to be set to 'drop' and - explicitly including the Excess-Treatment-Action AVP is not - necessary). The QoS-Parameters AVP carries the Bandwidth AVP - indicating the 1 Mbit/sec limit. + This would require the QoS-Action AVP to be set to 'shape' and the + QoS-Parameters AVP carries the Bandwidth AVP indicating the 1 Mbit/ + sec limit. The QoS-Action carried inside the Excess-Treatment AVP + would be set to 'drop'. In a second, more complex scenario, we consider traffic marking with DiffServ. In-profile traffic (of 5 Mbits/sec in our example) shall be associated with a particular PHB-Class "X". Out-of-profile traffic shall belong to a different PHB-Class, in our example "Y". - This configuration would require the Action AVP to be set to 'mark'. - - The QoS-Parameters AVPs for the traffic conforming of the profile - contains two AVPs, namely the TMOD-1 AVP and the PHB-Class AVP. The - TMOD-1 AVP describes the traffic characteristics, namely 5 Mbit/sec, - and the PHB-Class AVP is set to class "X". Then, the Excess- - Treatment AVP has to be included with the Excess-Treatment-Action AVP - set to 'mark' and the QoS-Parameters AVP to carry another PHB-Class - AVP indicating PHB-Class AVP setting to class "Y". + This configuration would require the QoS-Action AVP to be set to + 'mark'. The QoS-Parameters AVPs for the traffic conforming of the + profile contains two AVPs, namely the TMOD-1 AVP and the PHB-Class + AVP. The TMOD-1 AVP describes the traffic characteristics, namely 5 + Mbit/sec, and the PHB-Class AVP is set to class "X". Then, the + Excess-Treatment AVP has to be included with the QoS-Action AVP set + to 'mark' and the QoS-Parameters AVP to carry another PHB-Class AVP + indicating PHB-Class AVP setting to class "Y". 8. Acknowledgments We would like to thank Victor Fajardo, Tseno Tsenov, Robert Hancock, Jukka Manner, Cornelia Kappler, Xiaoming Fu, Frank Alfano, Tolga Asveren, Mike Montemurro, Glen Zorn, Avri Doria, Dong Sun, Tina Tsou, Pete McCann, Georgios Karagiannis, Elwyn Davies, Max Riegel and Yong Li for their comments. We thank Victor Fajardo for his job as PROTO document shepherd. @@ -1628,21 +1573,22 @@ 10.1. AVP Codes IANA is requested to allocate AVP codes for the following AVPs that are defined in this document. +--------------------------------------------------------------------+ | AVP Section | | Attribute Name Code Defined Data Type | +--------------------------------------------------------------------+ |QoS-Resources TBD 3.1 Grouped | - |Rule TBD 3.2 Grouped | + |QoS-Rule TBD 3.2 Grouped | + |QoS-Rule-Precedence TBD 3.3 Unsigned32 | |Classifier TBD 4.1.1 Grouped | |Classifier-ID TBD 4.1.2 OctetString | |Protocol TBD 4.1.3 Enumerated | |Direction TBD 4.1.4 Enumerated | |From-Spec TBD 4.1.5 Grouped | |To-Spec TBD 4.1.6 Grouped | |Negated TBD 4.1.7.1 Enumerated | |IP-Address TBD 4.1.7.2 Address | |IP-Address-Range TBD 4.1.7.3 Grouped | |IP-Address-Start TBD 4.1.7.4 Address | @@ -1675,79 +1621,67 @@ |ICMP-Code TBD 4.1.8.13 Enumerated | |ETH-Option TBD 4.1.8.14 Grouped | |ETH-Proto-Type TBD 4.1.8.15 Grouped | |ETH-Ether-Type TBD 4.1.8.16 OctetString | |ETH-SAP TBD 4.1.8.17 OctetString | |VLAN-ID-Range TBD 4.1.8.18 Grouped | |S-VID-Start TBD 4.1.8.19 Unsigned32 | |S-VID-End TBD 4.1.8.20 Unsigned32 | |C-VID-Start TBD 4.1.8.21 Unsigned32 | |C-VID-End TBD 4.1.8.22 Unsigned32 | - |ETH-Priority-Range TBD 4.1.8.23 Grouped | - |ETH-Low-Priority TBD 4.1.8.24 Unsigned32 | - |ETH-High-Priority TBD 4.1.8.25 Unsigned32 | + |User-Priority-Range TBD 4.1.8.23 Grouped | + |Low-User-Priority TBD 4.1.8.24 Unsigned32 | + |High-User-Priority TBD 4.1.8.25 Unsigned32 | |Time-Of-Day-Condition TBD 4.2.1 Grouped | |Time-Of-Day-Start TBD 4.2.2 Unsigned32 | |Time-Of-Day-End TBD 4.2.3 Unsigned32 | |Day-Of-Week-Mask TBD 4.2.4 Unsigned32 | |Day-Of-Month-Mask TBD 4.2.5 Unsigned32 | |Month-Of-Year-Mask TBD 4.2.6 Unsigned32 | |Absolute-Start-Time TBD 4.2.7 Time | |Absolute-End-Time TBD 4.2.8 Time | |Timezone-Flag TBD 4.2.9 Enumerated | |Timezone-Offset TBD 4.2.10 Integer32 | - |Action TBD 5.1 Grouped | - |QoS-Profile-Id TBD 5.2.1 Unsigned32 | - |QoS-Profile-Template TBD 5.2.2 Grouped | - |QoS-Semantics TBD 5.2.3 Enumerated | - |QoS-Parameters TBD 5.2.4 Grouped | - |Rule-Precedence TBD 5.2.5 Unsigned32 | - |Excess-Treatment TBD 5.2.6 Grouped | - |Excess-Treatment-Action TBD 5.2.7 Unsigned32 | + |QoS-Action TBD 5.1 Grouped | + |QoS-Profile-Id TBD 5.2 Unsigned32 | + |QoS-Profile-Template TBD 5.3 Grouped | + |QoS-Semantics TBD 5.4 Enumerated | + |QoS-Parameters TBD 5.5 Grouped | + |Excess-Treatment TBD 5.6 Grouped | |QoS-Capability TBD 6 Grouped | +--------------------------------------------------------------------+ 10.2. QoS-Semantics IANA Registry IANA is also requested to allocate a registry for the QoS-Semantics AVP. The following values are allocated by this specification. (0): QoS-Desired (1): QoS-Available (2): QoS-Reserved (3): Minimum-QoS (4): QoS-Authorized - A specification is required to add a new value to the registry. - -10.3. Excess Treatment Action - - IANA is also requested to allocate a registry for the Excess- - Treatment-Action AVP. The following values are allocated by this - specification: - - (0): drop - (1): shape - (2): mark - - A specification is required to add a new value to the registry. + The definition of new values is subject to the Specification Required + policy [RFC5226]. -10.4. Action +10.3. Action - IANA is also requested to allocate a registry for the Action AVP. + IANA is also requested to allocate a registry for the QoS-Action AVP. The following values are allocated by this specification: 0: drop 1: shape - 2: police 2: mark - A specification is required to add a new value to the registry. + + The definition of new values is subject to the Specification Required + policy [RFC5226]. 11. Security Considerations This document describes the extension of Diameter for conveying Quality of Service information. The security considerations of the Diameter protocol itself have been discussed in RFC 3588 [RFC3588]. Use of the AVPs defined in this document MUST take into consideration the security issues and requirements of the Diameter Base protocol. 12. References @@ -1778,33 +1712,37 @@ [RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers", RFC 2474, December 1998. [RFC2780] Bradner, S. and V. Paxson, "IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers", BCP 37, RFC 2780, March 2000. + [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an + IANA Considerations Section in RFCs", BCP 26, RFC 5226, + May 2008. + 12.2. Informative References [I-D.ietf-dime-diameter-qos] Sun, D., McCann, P., Tschofenig, H., Tsou, T., Doria, A., and G. Zorn, "Diameter Quality of Service Application", - draft-ietf-dime-diameter-qos-07 (work in progress), - December 2008. + draft-ietf-dime-diameter-qos-08 (work in progress), + May 2009. [I-D.ietf-dime-qos-parameters] Korhonen, J., Tschofenig, H., and E. Davies, "Quality of Service Parameters for Usage with Diameter", - draft-ietf-dime-qos-parameters-09 (work in progress), - January 2009. + draft-ietf-dime-qos-parameters-11 (work in progress), + May 2009. [RFC2475] Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z., and W. Weiss, "An Architecture for Differentiated Services", RFC 2475, December 1998. [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko, "Diameter Base Protocol", RFC 3588, September 2003. [RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, "Diameter Network Access Server Application", RFC 4005,