Diameter Maintenance and J. Korhonen Extensions (DIME) TeliaSonera Internet-Draft H. Tschofenig Intended status: Standards Track Nokia Siemens Networks Expires:December 28, 2008May 1, 2009 M. Arumaithurai University of Goettingen M. Jones, Ed. A. Lior Bridgewater SystemsJune 26,October 28, 2008 Quality of Service Attributes for Diameterdraft-ietf-dime-qos-attributes-07.txtdraft-ietf-dime-qos-attributes-08.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. 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 onDecember 28, 2008.May 1, 2009. 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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Diameter QoS Defined AVPs . . . . . . . . . . . . . . . . . . 4 3.1. QoS-Capability AVP . . . . . . . . . . . . . . . . . . . . 4 3.2. QoS-Profile-Template AVP . . . . . . . . . . . . . . . . . 4 3.3. Vendor-Specific-QoS-Profile-Template AVP . . . . . . . . . 4 3.4. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 5 3.5. Extended-QoS-Filter-Rule AVP . . . . . . . . . . . . . . . 5 3.6. QoS-Semantics . . . . . . . . . . . . . . . . . . . . . . 5 3.7. QoS-Parameters AVP . . . . . . . . . . . . . . . . . . . . 6 3.8. QoS-Rule-Precedence AVP . . . . . . . . . . . . . . . . . 6 4. Semantics of QoS Parameters . . . . . . . . . . . . . . . . . 6 5. Diameter Classifier AVPs . . . . . . . . . . . . . . . . . . . 7 5.1. Classifier AVP . . . . . . . . . . . . . . . . . . . . . . 9 5.2. Classifier-ID AVP . . . . . . . . . . . . . . . . . . . . 10 5.3. Protocol AVP . . . . . . . . . . . . . . . . . . . . . . . 10 5.4. Direction AVP . . . . . . . . . . . . . . . . . . . . . . 10 5.5. From-Spec AVP . . . . . . . . . . . . . . . . . . . . . . 10 5.6. To-Spec AVP . . . . . . . . . . . . . . . . . . . . . . . 11 5.7. Source and Destination AVPs . . . . . . . . . . . . . . . 12 5.7.1. Negated AVP . . . . . . . . . . . . . . . . . . . . .1312 5.7.2. IP-Address AVP . . . . . . . . . . . . . . . . . . . . 13 5.7.3. IP-Address-Range AVP . . . . . . . . . . . . . . . . . 13 5.7.4. IP-Address-Start AVP . . . . . . . . . . . . . . . . .1413 5.7.5. IP-Address-End AVP . . . . . . . . . . . . . . . . . .1413 5.7.6. IP-Address-Mask AVP . . . . . . . . . . . . . . . . . 14 5.7.7. IP-Mask-Bit-Mask-Width AVP . . . . . . . . . . . . . . 14 5.7.8. MAC-Address AVP . . . . . . . . . . . . . . . . . . . 14 5.7.9. MAC-Address-Mask AVP . . . . . . . . . . . . . . . . . 14 5.7.10. MAC-Address-Mask-Pattern AVP . . . . . . . . . . . . .1514 5.7.11. EUI64-Address AVP . . . . . . . . . . . . . . . . . . 15 5.7.12. EUI64-Address-Mask AVP . . . . . . . . . . . . . . . . 15 5.7.13. EUI64-Address-Mask-Pattern AVP . . . . . . . . . . . . 15 5.7.14.VLAN-ID AVP . . . . . . . . . . . . . . . . . . . . . 15 5.7.15.Port AVP . . . . . . . . . . . . . . . . . . . . . . .16 5.7.16.15 5.7.15. Port-Range AVP . . . . . . . . . . . . . . . . . . . .16 5.7.17.15 5.7.16. Port-Start AVP . . . . . . . . . . . . . . . . . . . . 165.7.18.5.7.17. Port-End AVP . . . . . . . . . . . . . . . . . . . . . 165.7.19.5.7.18. Use-Assigned-Address AVP . . . . . . . . . . . . . . . 16 5.8. Header Option AVPs . . . . . . . . . . . . . . . . . . . .1716 5.8.1. Diffserv-Code-Point AVP . . . . . . . . . . . . . . .1716 5.8.2. Fragmentation-Flag AVP . . . . . . . . . . . . . . . .1716 5.8.3. IP-Option AVP . . . . . . . . . . . . . . . . . . . . 17 5.8.4. IP-Option-Type AVP . . . . . . . . . . . . . . . . . .1817 5.8.5. IP-Option-Value AVP . . . . . . . . . . . . . . . . .1817 5.8.6. TCP-Option AVP . . . . . . . . . . . . . . . . . . . .1817 5.8.7. TCP-Option-Type AVP . . . . . . . . . . . . . . . . . 18 5.8.8. TCP-Option-Value AVP . . . . . . . . . . . . . . . . . 18 5.8.9. TCP-Flags AVP . . . . . . . . . . . . . . . . . . . . 18 5.8.10. TCP-Flag-Type AVP . . . . . . . . . . . . . . . . . .1918 5.8.11. ICMP-Type . . . . . . . . . . . . . . . . . . . . . . 19 5.8.12. ICMP-Type-Number AVP . . . . . . . . . . . . . . . . .2019 5.8.13. ICMP-Code AVP . . . . . . . . . . . . . . . . . . . .2019 5.8.14. ETH-Option AVP . . . . . . . . . . . . . . . . . . . .2019 5.8.15. ETH-Proto-Type AVP . . . . . . . . . . . . . . . . . . 20 5.8.16. ETH-Ether-Type AVP . . . . . . . . . . . . . . . . . . 20 5.8.17. ETH-SAP AVP . . . . . . . . . . . . . . . . . . . . . 20 5.8.18.ETH-Priority-RangeVLAN-ID-Range AVP . . . . . . . . . . . . . . . .21. . 20 5.8.19.ETH-Low-PriorityS-VID-Start AVP . . . . . . . . . . . . . . . . . . . 21 5.8.20.ETH-High-PriorityS-VID-End AVP . . . . . . . . . . . . . . . . . . . . 216. Examples5.8.21. C-VID-Start AVP . . . . . . . . . . . . . . . . . . . 22 5.8.22. C-VID-End AVP . . . . . . . .21 6.1. Diameter EAP with QoS Information. . . . . . . . . . . .21 6.2. Diameter NASREQ with QoS Information22 5.8.23. ETH-Priority-Range AVP . . . . . . . . . . . . . . . . 226.3. QoS Authorization5.8.24. ETH-Low-Priority AVP . . . . . . . . . . . . . . . . . 22 5.8.25. ETH-High-Priority AVP . . .23 6.4. Diameter Server Initiated Re-authorization of QoS. . . .24 6.5. Diameter Credit Control with QoS Information. . . . . . .25 6.6. Classifier Examples. . 22 6. Time Of Day AVPs . . . . . . . . . . . . . . . . .26 7. Acknowledgments. . . . . . 22 6.1. Time-Of-Day-Condition AVP . . . . . . . . . . . . . . . . 23 6.2. Time-Of-Day-Start AVP .27 8. IANA Considerations. . . . . . . . . . . . . . . . . 23 6.3. Time-Of-Day-End AVP . . . .27 9. Security Considerations. . . . . . . . . . . . . . . 24 6.4. Day-Of-Week-Mask AVP . . . .29 10. References. . . . . . . . . . . . . . . 24 6.5. Day-Of-Month-Mask AVP . . . . . . . . . . .29 10.1. Normative References. . . . . . . 24 6.6. Month-Of-Year-Mask AVP . . . . . . . . . . . .29 10.2. Informative References. . . . . . 24 6.7. Absolute-Start-Time AVP . . . . . . . . . . . .30 Authors' Addresses. . . . . 25 6.8. Absolute-End-Time AVP . . . . . . . . . . . . . . . . . . 25 6.9. Timezone-Flag AVP .30 Intellectual Property and Copyright Statements. . . . . . . . . .32 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 command ABNF. The Extended-QoS- Filter-Rule. . . . . . . . . 25 6.10. Timezone-Offset AVPthereby replaces the IPFilterRule, defined in RFC 3588bis [I-D.ietf-dime-rfc3588bis], and the QoS-Filter-Rule, defined in RFC 4005. . . . . . . . . . . . . . . . . . . 26 7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 7.1. Diameter EAP with QoS Information . . . . . . . . . . . . 26 7.2. Diameter NASREQ with QoS Information . . . . . . . . . . . 27 7.3. QoS Authorization . . . . . . . . . . . . . . . . . . . . 28 7.4. Diameter Server Initiated Re-authorization of QoS . . . . 29 7.5. Diameter Credit Control with QoS Information . . . . . . . 30 7.6. Classifier Examples . . . . . . . . . . . . . . . . . . . 31 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 32 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 32 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32 11. Security Considerations . . . . . . . . . . . . . . . . . . . 34 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35 12.1. Normative References . . . . . . . . . . . . . . . . . . . 35 12.2. Informative References . . . . . . . . . . . . . . . . . . 36 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 36 Intellectual Property and Copyright Statements . . . . . . . . . . 38 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 command ABNF. The Extended-QoS- Filter-Rule AVP thereby replaces the IPFilterRule, defined in RFC 3588bis [I-D.ietf-dime-rfc3588bis], and the QoS-Filter-Rule, defined in RFC 4005 [RFC4005]. 2. Terminology Thekey words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",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. Diameter QoS Defined AVPs 3.1. QoS-Capability AVP 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. QoS-Capability ::= < AVP Header: XXX > * [ QoS-Profile-Template ] * [ Vendor-Specific-QoS-Profile-Template ] * [ AVP ] 3.2. QoS-Profile-Template AVP The QoS-Profile-Template 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 is described in [I-D.ietf-dime-qos-parameters]. The registry for the QoS profile templates is created with the same document. 3.3. Vendor-Specific-QoS-Profile-Template AVP The Vendor-Specific-QoS-Profile-Template AVP (AVP Code TBD) is of type Grouped and defines a vendor-specific QoS profile template. The Vendor-Id AVP contains a 32 bit IANA SMI Network Management Private Enterprise Code and the QoS-Profile-Template AVP contains the template identifier assigned by the vendor. Vendor-Specific-QoS-Profile-Template ::= < AVP Header: XXX > { Vendor-Id } { QoS-Profile-Template } * [ AVP ] 3.4. QoS-Resources AVP The QoS-Resources AVP (AVP Code TBD) is of type Grouped and includes a description of the Quality of Service resources for policing traffic flows. QoS-Resources ::= < AVP Header: XXX > * [ Extended-QoS-Filter-Rule ] * [ AVP ] 3.5. Extended-QoS-Filter-Rule AVP The Extended-QoS-Filter-Rule AVP (AVP Code TBD) is of type Grouped and defines one or more traffic flows together with a set of QoS parameters that should be applied to the flow(s) by the Resource Management Function. This AVP uses the Classifier AVP (see Section 5) to describe traffic flows. Extended-QoS-Filter-Rule ::= < AVP Header: XXX > { QoS-Semantics } [ QoS-Profile-Template ] [ Vendor-Specific-QoS-Profile-Template ] [ QoS-Parameters ] [ QoS-Rule-Precedence ] [ Classifier ] * [ Time-Of-Day-Condition ] * [ AVP ] Either the QoS-Profile-Template or Vendor-Specific-QoS-Profile- Template AVP MUST appear in the Extended-QoS-Filter-Rule AVP. 3.6. 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 Extended-QoS-Filter-Rule AVP. This document defines the following values: (0): QoS-Desired (1): QoS-Available (2): QoS-Reserved (3): Minimum-QoS (4): QoS-Authorized 3.7. QoS-Parameters AVP The QoS-Parameters AVP (AVP Code TBD) is of type OctetString and contains Quality of Service parameters. These parameters are defined in a separate document, see [I-D.ietf-dime-qos-parameters]. 3.8. QoS-Rule-Precedence AVP The QoS-Rule-Precedence AVP (AVP Code TBD) is of type Unsigned32 and"OPTIONAL"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 QoS-Rule-Precedence AVP is absent from the Extended-QoS-Filter-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 QoS-Rule- Precedence AVP, the higher the rule precedence. 4. Semantics of QoS Parameters The QoS parameters carried in the QoS-Resources AVP may appear in different messages. The semantic of the QoS parameters depend on the information provided in the QoS-Semantics AVP which currently defines 5 values, namely QoS-Desired (0), QoS-Available (1), QoS-Reserved (2), Minimum-QoS (3), and QoS-Authorized (4). The semantics of the different values are as follows: Object Type Direction Semantic --------------------------------------------------------------------- QoS-Desired C->S Please authorize the indicated QoS QoS-Desired C<-S NA QoS-Available C->S Admission Control at interface indicates that this QoS is available. (note 1) QoS-Available C<-S Indicated QoS is available. (note 2) QoS-Reserved C->S Used for reporting during accounting. QoS-Reserved C<-S NA Minimum-QoS C->S Indicates that the client is not interested in authorizing QoS that is lower than Min. QoS. Minimum-QoS C<-S The client must not provide QoS guarantees lower than Min. QoS. QoS-Authorized C->S NA QoS-Authorized C<-S Indicated QoS authorized Legend: C: Diameter client S: Diameter server NA: Not applicable to this document; no semantic defined in thisdocumentspecification Notes: (1) QoS-Available is only useful in relationship with QoS-Desired (and optionally with Minimum-QoS). (2) QoS-Available is only useful when the AAA server performs admission control and knows about the resources in the network. 5. Diameter Classifier AVPs Classifiers are used in many applications to specify how to classify packets. For example in a QoS application, if a packet matches a classifier then that packet will beinterpreted as describedtreated inRFC 2119 [RFC2119]. 3. Diameteraccordance with a QoSDefined AVPs 3.1. QoS-Capability AVPspecification associated with that classifier. TheQoS-Capability AVP (AVP Code TBD)Classifiers are sent to on on-path element (e.g. a router) which uses the classifier to match packets. Figure 1 shows a typical deployment. +-----------+ +-----------+| +--------+ +-------------+ +------------+|| | | IN | | | ||| | +--------->| +------------->| ||| |Managed | | Classifying | | Unmanaged ||| |Terminal| OUT | Entity | | Terminal ||| | |<---------+ |<-------------+ ||+ | | | | | |+ +--------+ +-------------+ +------------+ ^ | Classifiers | +------+-------+ | | | 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 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 oftype Grouped and containsalistgroup ofsupported Qualityattributes that specify how to match a packet. Each set ofService profile templates (and therefore the supportattributes expresses values about aspects of therespective parameter AVPs). The QoS-Capability AVP may be used forpacket - typically the packet header. Different protocols therefore would use different attributes. In general asimple announcementClassifier consists of theQoS capabilitiesfollowing: Identifier: The identifier uniquely identifies this classifier andQoS profiles supported by a peer. Itmayalsobe used tonegotiate a mutually supported setreference the classifier from another structure. From: Specifies the rule for matching the source part ofQoS capabilities and QoS profiles between two peers. QoS-Capability ::= < AVP Header: XXX > * [ QoS-Profile-Template ] * [ Vendor-Specific-QoS-Profile-Template ] * [ AVP ] 3.2. QoS-Profile-Template AVP The QoS-Profile-Template AVP (AVP Code TBD) isthe packet. To: Specifies the rule for matching the destination part oftype Unsigned32 and contains a QoS profile template identifier. An initial QoS profile template is defined with valuethe packet. Protocol: Specifies the matching protocol of0 and is described in [I-D.ietf-dime-qos-parameters]. The registry fortheQoS profile templates is created withpacket. Direction: Specifies whether thesame document. 3.3. Vendor-Specific-QoS-Profile-Template AVP The Vendor-Specific-QoS-Profile-Template AVP (AVP Code TBD)classifier isof type Grouped and defines a vendor-specific QoS profile template. The Vendor-Id AVP contains a 32 bit IANA SMI Network Management Private Enterprise Code andto apply to packets flowing from theQoS-Profile-Template AVP containsManaged Terminal (IN) or to packets flowing to thetemplate identifier assigned byManaged Terminal (OUT), or packets flowing in both direction. Options: Associated with each protocol or layer, or various values specific to thevendor. Vendor-Specific-QoS-Profile-Template ::= < AVP Header: XXX > { Vendor-Id } { QoS-Profile-Template } * [ AVP ] 3.4. QoS-Resources AVP The QoS-Resources AVP (AVP Code TBD) isheader of the protocol or layer. Options allow matching on those values. Each protocol typeGrouped and includeswill have adescription of the Qualityspecific set ofService resourcesattributes that can be used to specify a classifier forpolicing traffic flows. QoS-Resources ::= < AVP Header: XXX > * [ Extended-QoS-Filter-Rule ] * [that protocol. These attributes will be grouped under a grouped AVP] 3.5. Extended-QoS-Filter-Rulecalled a Classifier AVP. 5.1. Classifier AVP TheExtended-QoS-Filter-RuleClassifier AVP (AVP Code TBD) is a grouped AVP that consists oftype Grouped and defines one or more traffic flows together witha set ofQoS parametersattributes thatshould be appliedspecify how tothe flow(s) by the Resource Management Function. This AVP uses thematch a packet. ClassifierAVP (see Section 5) to describe traffic flows. Extended-QoS-Filter-Rule::= < AVP Header: XXX > {QoS-SemanticsClassifier-ID } { Protocol } { Direction } * [QoS-Profile-TemplateFrom-Spec ] * [Vendor-Specific-QoS-Profile-TemplateTo-Spec ] * [QoS-ParametersDiffserv-Code-Point ] [QoS-Rule-PrecedenceFragmentation-Flag ] * [ClassifierIP-Option ] * [ TCP-Option ] [ TCP-Flags ] * [ ICMP-Type ] * [ ETH-Option ] * [ AVP ]Either5.2. Classifier-ID AVP The Classifier-ID AVP (AVP Code TBD) is of type OctetString and uniquely identifies theQoS-Profile-Template or Vendor-Specific-QoS-Profile- Templateclassifier. Each application will define the uniqueness scope of this identifier, e.g. unique per terminal or globally unique. Exactly one Classifier-ID AVP MUSTappear in the Extended-QoS-Filter-Rulebe contained within a Classifier AVP.3.6. QoS-Semantics5.3. Protocol AVP TheQoS-SemanticsProtocol AVP (AVP Code TBD) is of type Enumerated andprovides the semantics forspecifies theQoS-Profile-Template and QoS- Parameters AVPsprotocol being matched. The attributes included in theExtended-QoS-Filter-Rule AVP. This document definesClassifier AVP must be consistent with thefollowing values: (0): QoS-Desired (1): QoS-Available (2): QoS-Reserved (3): Minimum-QoS (4): QoS-Authorized 3.7. QoS-Parametersvalue of the Protocol AVP. Exactly one Protocol AVP MUST be contained within a Classifier AVP. TheQoS-Parametersvalues for this AVP(AVP Code TBD) is of type OctetString and contains Quality of Service parameters. These parametersaredefined in a separate document, see [I-D.ietf-dime-qos-parameters]. 3.8. QoS-Rule-Precedencemanaged by IANA under the Protocol Numbers registry [PROTOCOL]. 5.4. Direction AVP TheQoS-Rule-PrecedenceDirection AVP (AVP Code TBD) is of typeUnsigned32 andEnumerated that specifies in which direction to apply theexecution orderClassifier. The values of therules expressed inenumeration are: "IN","OUT","BOTH". In theQoS- Resources AVP. Rules with equal precedence MAY be executed in parallel if supported by"IN" and "BOTH" directions, theResource Management Function. IfFrom-Spec refers to theQoS-Rule-Precedenceaddress 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. Value | Name and Semantic ------+-------------------------------------------------- 0 | RESERVED 1 | IN - The classifier applies to flows from the | Managed Terminal. 2 | OUT - The classifier applies to flows to the | Managed Terminal. 3 | BOTH - The classifier applies to flows both to | and from the Managed Terminal. 5.5. From-Spec AVP The From-Spec AVP (AVP Code TBD) isabsent from the Extended-QoS-Filter-Rule AVP,a grouped AVP that specifies therules SHOULD be executed inSource Specification used to match theorder in which theypacket. Zero or more of these AVPs may appear in theQoS-Resources AVP. The lowerClassifier. If this AVP is absent from thenumerical valueClassifier then all packets are matched regardless ofQoS-Rule- Precedence AVP,thehigher the rule precedence. 4. Semanticssource address. If more than one instance ofQoS Parameters The QoS parameters carried in the QoS-Resourcesthis AVPmay appearappears indifferent messages. The semantic oftheQoS parameters depend onClassifier then theinformation provided insource of theQoS-Semantics AVP which currently defines 5 values, namely QoS-Desired (0), QoS-Available (1), QoS-Reserved (2), Minimum-QoS (3), and QoS-Authorized (4).packet can match any From-Spec AVP. Thesemanticscontents ofthe different values are as follows: Object Type Direction Semantic --------------------------------------------------------------------- QoS-Desired C->S Please authorize the indicated QoS QoS-Desired C<-S NA QoS-Available C->S Admission Control at interface indicates thatthisQoS is available. (note 1) QoS-Available C<-S Indicated QoS is available. (note 2) QoS-Reserved C->S Used for reporting during accounting. QoS-Reserved C<-S NA Minimum-QoS C->S Indicates that the client is not interested in authorizing QoS that is lower than Min. QoS. Minimum-QoS C<-S The client must not provide QoS guarantees lowerAVP are protocol specific. If more thanMin. QoS. QoS-Authorized C->S NA QoS-Authorized C<-S Indicated QoS authorized Legend: C: Diameter client S: Diameter server NA: Not applicable to this document; no semantic defined in this specification Notes: (1) QoS-Available is only usefulone instance of the IP address AVPs (IP-Address, IP- Address-Range, IP-Address-Mask, Use-Assigned-Address) appear inrelationship with QoS-Desired (and optionally with Minimum-QoS). (2) QoS-Available is only useful whentheAAA server performs admission control and knows aboutFrom-Spec AVP then theresources insource IP address of thenetwork. 5. Diameter Classifierpacket must match one of the addresses represented by these AVPs. If more that one instance of the layer 2 address AVPsClassifiers are used in many applications to specify how to classify packets. For example(MAC-Address, MAC-Address-Mask, EUI64-Address, EUI64-Address-Mask) appears ina QoS application, if a packet matches a classifierthe From-Spec thenthatthe the source layer 2 address of the packetwill be treatedmust match one of the addresses represented inaccordance with a QoS specification associated withthese AVPs. If more thatclassifier. The Classifiers are sent to on on-path element (e.g. a router) which usesone instance of theclassifier toport AVPs (Port, Port-Range) appears in the From-Spec AVP then the source port number must matchpackets. Figure 1 shows a typical deployment. +-----------+ +-----------+| +--------+ +-------------+ +------------+|| | | IN | | | ||| | +--------->| +------------->| ||| |Managed | | Classifying | | Unmanaged ||| |Terminal| OUT | Entity | | Terminal ||| | |<---------+ |<-------------+ ||+ | | | | | |+ +--------+ +-------------+ +------------+ ^ | Classifiers | +------+-------+ | | | AAA | | | +--------------+ Figure 1: Exampleone ofa Classifier Architecture The managed terminal,theterminal for whichport numbers represented in these AVPs. If the IP address, MAC address and port AVPs appear in the same From- Spec AVP then theclassifiers are being specified is located onsource packet must match all theleft ofspecifications, i.e. match theClassifying Entity.IP address AND MAC address AND port number. From-Spec ::= < AVP Header: XXX > * [ IP-Address ] * [ IP-Address-Range ] * [ IP-Address-Mask ] * [ MAC-Address ] * [ MAC-Address-Mask] * [ EUI64-Address ] * [ EUI64-Address-Mask] * [ Port ] * [ Port-Range ] [ Negated ] [ Use-Assigned-Address ] * [ AVP ] 5.6. To-Spec AVP Theunmanaged terminal, the terminalTo-Spec AVP (AVP Code TBD) is a grouped AVP thatreceives packets from the Managed terminal or sends packets tospecifies themanaged terminal is locatedDestination Specification used to match theright sidepacket. Zero or more of these AVPs may appear in theClassifying Entity. The Classifying EntityClassifier. If this AVP isresponsible for classifying packets that are incoming (IN)absent from theManaged Terminal or packets outgoing (OUT) to the Managed Terminal. AClassifierconsists of a group of attributes that specify how to match a packet. Each set of attributes expresses values about aspectsthen all packets are matched regardless of thepacket - typicallydestination address. If more than one instance of this AVP appears in thepacket header. Different protocols therefore would use different attributes. In general aClassifierconsiststhen the destination of thefollowing: Identifier:packet can match any To-Spec AVP. Theidentifier uniquely identifiescontents of thisclassifier and may be used to referenceAVP are protocol specific. If more than one instance of the IP address AVPs (IP-Address, IP- Address-Range, IP-Address-Mask, Use-Assigned-Address) appear in the To-Spec AVP then theclassifier from another structure. From: Specifiesdestination IP address of therule for matchingpacket must match one of thesource partaddresses represented by these AVPs. If more that one instance of thepacket. To: Specifieslayer 2 address AVPs (MAC-Address, MAC-Address-Mask, EUI64-Address, EUI64-Address-Mask) appears in the To-Spec then therule for matchingthe destinationpartlayer 2 address of thepacket. Protocol: Specifiespacket must match one of thematching protocoladdresses represented in these AVPs. If more that one instance of thepacket. Direction: Specifies whetherport AVPs (Port, Port-Range) appears in theclassifier is to apply to packets flowing fromTo-Spec AVP then theManaged Terminal (IN) or to packets flowing todestination port number must match one of theManaged Terminal (OUT), or packets flowingport numbers represented inboth direction. Options: Associated with each protocol or layer, or various values specific tothese AVPs. If theheader ofIP address, MAC address and port AVPs appear in theprotocol or layer. Options allow matching on those values. Each protocol type will have a specific set of attributes that can be used to specify a classifier for that protocol. These attributes will be grouped under a grouped AVP called a Classifier AVP. 5.1. Classifier AVP The Classifier AVP (AVP Code TBD) is a groupedsame To- Spec AVPthat consists of a set of attributes that specify how tothen the destination packet must matcha packet. Classifierall the specifications, i.e. match the IP address AND MAC address AND port number. To-Spec ::= < AVP Header: XXX >{ Classifier-ID } { Protocol } { Direction }* [From-SpecIP-Address ] * [ IP-Address-Range ] * [ IP-Address-Mask ] * [To-SpecMAC-Address ] * [Diffserv-Code-Point ]MAC-Address-Mask] * [Fragmentation-FlagEUI64-Address ] * [IP-Option ]EUI64-Address-Mask] * [TCP-OptionPort ] * [TCP-FlagsPort-Range ]*[ICMP-TypeNegated ]*[ETH-OptionUse-Assigned-Address ] * [ AVP ]5.2. Classifier-ID AVP The Classifier-ID AVP (AVP Code TBD) is of type OctetString and uniquely identifies the classifier. Each application will define the uniqueness scope of this identifier, e.g. unique per terminal or globally unique. Exactly one Classifier-ID AVP MUST be contained within a Classifier AVP. 5.3. Protocol AVP The Protocol AVP (AVP Code TBD) is of type Enumerated and specifies the protocol being matched. The attributes included in the Classifier AVP must be consistent with the value of the Protocol AVP. Exactly one Protocol AVP MUST be contained within a Classifier AVP. The values for this AVP are managed by IANA under the Protocol Numbers registry [PROTOCOL]. 5.4. Direction AVP The Direction AVP (AVP Code TBD) is of type Enumerated that specifies in which direction to apply the Classifier. The values of the enumeration are: "IN","OUT","BOTH". In the "IN"5.7. Source and"BOTH" directions, the From-Spec refers toDestination AVPs For packet classification theaddresscontents of theManaged Terminal and the To-Spec refers to the unmanaged terminal. In the "OUT" direction, theFrom-Specrefers to the Unmanaged Terminal whereas the To-Spec refers to the Managed Terminal. Value | Name and Semantic ------+-------------------------------------------------- 0 | RESERVED 1 | IN - The classifier applies to flows from the | Managed Terminal. 2 | OUT - The classifier applies to flows to the | Managed Terminal. 3 | BOTH - The classifier applies to flows both to |andfromTo-Spec can contain theManaged Terminal. 5.5.following AVPs. By combining several of these AVPs within a From-Spec or To-Spec AVPTheand using more than one From-Spec or To-Spec AVP in the Classifier AVP, one can express many different types of address pools. 5.7.1. Negated AVP The Negated AVP (AVP Code TBD)is a grouped AVP that specifies the Source Specification used to matchof type Enumerated containing thepacket. Zerovalues of True ormoreFalse. Exactly zero or one of these AVPs may appear in theClassifier. If this AVP is absent fromFrom-Spec or To-Spec AVP. When set to True theClassifier then all packetsmeaning of the match in the To-Spec and From-Spec are negated, causing all other addresses to be matchedregardless ofinstead. When set to False, or when thesource address. If more than one instance of thisAVPappearsis not included in theClassifierFrom-Spec or To-Spec AVP then thesourcemeaning of thepacket canmatchany From-Spec AVP.is not inverted, causing only the addresses specified to be matched. Note that the negation does not impact the port comparisons. Value | Name ------+-------- 0 | False 1 | True 5.7.2. IP-Address AVP ThecontentsIP-Address AVP (AVP Code TBD) is ofthistype Address and specifies a single IP address (IPv4 or IPv6) address to match. 5.7.3. IP-Address-Range AVPare protocol specific. If more than one instanceThe IP-Address-Range AVP (AVP Code TBD) is ofthetype Grouped and specifies an inclusive IP addressAVPs (IP-Address, IP- Address-Range, IP-Address-Mask, Use-Assigned-Address) appear inrange. IP-Address-Range ::= < AVP Header: XXX > [ IP-Address-Start ] [ IP-Address-End ] * [ AVP ] If theFrom-SpecIP-Address-Start AVP is not included then thesourceaddress range starts from the first valid IP addressof the packet must match one ofup to and including theaddresses represented by these AVPs.specified IP-Address-End address. Ifmore that one instance of the layer 2 address AVPs (MAC-Address, MAC-Address-Mask, EUI64-Address, EUI64-Address-Mask) appears intheFrom-SpecIP-Address-End AVP is not included then the address range starts at thesource layer 2addressofspecified by thepacket must match one ofIP-Address-Start AVP and includes all theaddresses represented in these AVPs. If more that one instance ofremaining valid IP addresses. For theVLAN-IDIP-Address-Range AVPappears in the From-Spec thento be valid, theVLAN-IDIP-Address-Start AVP MUST contain a value that is less than that of thepacket must match oneIP-Address-End AVP. 5.7.4. IP-Address-Start AVP The IP-Address-Start AVP (AVP Code TBD) is of type Address and specifies theVLAN-IDs represented in these AVPs. If more that one instancefirst IP address (IPv4 or IPv6) address ofthe port AVPs (Port, Port-Range) appears in the From-Specan IP address range. 5.7.5. IP-Address-End AVPthen the source port number must match oneThe IP-Address-End AVP (AVP Code TBD) is of type Address and specifies theport numbers represented in these AVPs. If thelast IP address (IPv4 or IPv6) address of an address range. 5.7.6. IP-Address-Mask AVP The IP-Address-Mask AVP (AVP Code TBD) is of type Grouped and specifies an IP address range using a base IPaddress, MACaddress andport AVPs appear inthesame From- Spec AVP thenbit- width of thesource packet mustmask. For example, a range expressed as 1.2.3.0/24 will match all IP addresses from 1.2.3.0 up to and including 1.2.3.255. The bit-width MUST be valid for thespecifications, i.e. match thetype of IPaddress AND MAC address AND port number. From-Specaddress. IP-Address-Mask ::= < AVP Header: XXX >* [{ IP-Address] * [ IP-Address-Range ] * [ IP-Address-Mask ] * [ MAC-Address ] * [ MAC-Address-Mask] * [ EUI64-Address ] * [ EUI64-Address-Mask] * [ VLAN-ID ] * [ Port ] * [ Port-Range ] [ Negated ] [ Use-Assigned-Address ]} { IP-Bit-Mask-Width } * [ AVP ]5.6. To-Spec5.7.7. IP-Mask-Bit-Mask-Width AVP TheTo-SpecIP-Bit-Mask-Width AVP (AVP Code TBD) is of type OctetString. The value is agrouped AVP thatsingle octet and specifies theDestination Specification used to match the packet. Zero or morewidth ofthese AVPs mayan IP address bit- mask. 5.7.8. MAC-Address AVP The MAC-Address AVP (AVP Code TBD) is of type OctetString and specifies a single layer 2 address in MAC-48 format. The value is a 6 octets encoding of the address as it would appear in theClassifier. If thisframe header. 5.7.9. MAC-Address-Mask AVP The MAC-Address-Mask AVP (AVP Code TBD) isabsent from the Classifier then all packets are matched regardlessof type Grouped and specifies a set of MAC addresses using a bit mask to indicate thedestination address. If more than one instancebits ofthis AVP appears intheClassifier thenMAC addresses which must fit to thedestinationspecified MAC address attribute. For example, a MAC-Address-Mask with the MAC-Address as 00-10-A4-23-00-00 and with a MAC-Address-Mask-Pattern of FF-FF-FF-FF- 00-00 will match all MAC addresses from 00-10-A4-23-00-00 up to and including 00-10-A4-23-FF-FF. MAC-Address-Mask ::= < AVP Header: XXX > { MAC-Address } { MAC-Address-Mask-Pattern } * [ AVP ] 5.7.10. MAC-Address-Mask-Pattern AVP The MAC-Address-Mask-Pattern AVP (AVP Code TBD) is ofthe packet can match any To-Spec AVP.type OctetString. Thecontentsvalue is a 6 octets specifying the bit positions ofthis AVPa MAC address, that areprotocol specific. If more than one instancetaken for matching. 5.7.11. EUI64-Address AVP The EUI64-Address AVP (AVP Code TBD) is of type OctetString and specifies a single layer 2 address in EUI-64 format. The value is a 8 octets encoding of theIPaddressAVPs (IP-Address, IP- Address-Range, IP-Address-Mask, Use-Assigned-Address)as it would appear in theTo-Specframe header. 5.7.12. EUI64-Address-Mask AVPthen the destination IP addressThe EUI64-Address-Mask AVP (AVP Code TBD) is of type Grouped and specifies a set of EUI64 addresses using a bit mask to indicate thepacket must match onebits of the EUI64 addressesrepresented by these AVPs. If more that one instance ofwhich must fit to thelayer 2specified EUI64 addressAVPs (MAC-Address, MAC-Address-Mask, EUI64-Address, EUI64-Address-Mask) appears in the To-Spec then theattribute. For example, a EUI64-Address-Mask with thedestination layer 2 addressEUI64- Address as 00-10-A4-FF-FE-23-00-00 and with a EUI64-Address-Mask- Pattern ofthe packet mustFF-FF-FF-FF-FF-FF-00-00 will matchone of theall EUI64 addressesrepresented in these AVPs. If more that one instance of the VLAN-IDfrom 00-10-A4-FF-FE-23-00-00 up to and including 00-10-A4-FF-FE-23- FF-FF. EUI64-Address-Mask ::= < AVPappears in the From-Spec then the VLAN-IDHeader: XXX > { EUI64-Address } { EUI64-Address-Mask-Pattern } * [ AVP ] 5.7.13. EUI64-Address-Mask-Pattern AVP The EUI64-Address-Mask-Pattern AVP (AVP Code TBD) is of type OctetString. The value is a 8 octets specifying thepacket must match onebit positions ofthe VLAN-IDs represented in these AVPs. If morea EUI64 address, thatone instanceare taken for matching. 5.7.14. Port AVP The Port AVP (AVP Code TBD) is ofthe port AVPs (Port, Port-Range) appearstype Integer32 in theTo-Spec AVP thenrange of 0 to 65535 and specifies thedestinationTCP or UDP port numbermust match oneto match. 5.7.15. Port-Range AVP The Port-Range AVP (AVP Code TBD) is ofthe port numbers represented in these AVPs. If the IP address, MAC addresstype Grouped andport AVPs appear in the same To- Spec AVP then the destination packet must match all the specifications, i.e. match the IP address AND MAC address AND port number. To-Specspecifies an inclusive range of ports. Port-Range ::= < AVP Header: XXX >* [ IP-Address ] * [ IP-Address-Range ] * [ IP-Address-Mask ] * [ MAC-Address ] * [ MAC-Address-Mask] * [ EUI64-Address ] * [ EUI64-Address-Mask] * [ VLAN-ID ] * [ Port ] * [ Port-Range ][NegatedPort-Start ] [Use-Assigned-AddressPort-End ] * [ AVP ]5.7. Source and Destination AVPs For packet classificationIf thecontents ofPort-Start AVP is omitted then port 0 is assumed. If theFrom-SpecPort-End AVP is omitted then port 65535 is assumed. 5.7.16. Port-Start AVP The Port-Start AVP (AVP Code TBD) is of type Integer32 andTo-Spec can containspecifies thefollowing AVPs. By combining severalfirst port number ofthese AVPs within a From-Spec or To-Specan IP port range. 5.7.17. Port-End AVP The Port-End AVP (AVP Code TBD) is of type Integer32 andusing more than one From-Spec or To-Specspecifies the last port number of an IP port range. 5.7.18. Use-Assigned-Address AVPinIn some scenarios, the AAA does not know the IP address assigned to the Managed Terminal at the time that the ClassifierAVP, one can express many different types of address pools. 5.7.1. Negated AVPis sent to the Classifying Entity. TheNegatedUse-Assigned-Address AVP (AVP Code TBD) is of type Enumerated containing the values of True or False.Exactly zero or one of these AVPs may appear in the From-Spec or To-Spec AVP.Whenset to True the meaning of the match in the To-Specpresent andFrom-Spec are negated, causing all other addresses to be matched instead. Whenset toFalse, or when the AVP is not included in the From-Spec or To-Spec AVP then the meaning of the match is not inverted, causing onlyTrue, it represents theaddresses specifiedIP address assigned tobe matched. Note that the negation does not impacttheport comparisons.Managed Terminal. Value | Name ------+-------- 0 | False 1 | True5.7.2. IP-Address5.8. Header Option AVPs The Classifier AVP may contain one or more of the following AVPs to match on the various possible IP, TCP or ICMP header options. 5.8.1. Diffserv-Code-Point AVP TheIP-AddressDiffserv-Code-Point AVP (AVP Code TBD) is of typeAddressEnumerated and specifiesa singlethe Differentiated Services Field Codepoints to match in the IPaddress (IPv4 or IPv6) addressheader. The values are managed by IANA under the Differentiated Services Field Codepoints registry [DSCP]. 5.8.2. Fragmentation-Flag AVP The Fragmentation-Flag AVP (AVP Code TBD) is of type Enumerated and specifies the packet fragmentation flags tomatch. 5.7.3. IP-Address-Rangematch in the IP header. Value | Name and Semantic ------+------------------------------------------------------------ 0 | RESERVED 1 | Don't Fragment (DF) 2 | More Fragments (MF) 5.8.3. IP-Option AVP TheIP-Address-RangeIP-Option AVP (AVP Code TBD) is of type Grouped and specifies aninclusiveIPaddress range. IP-Address-Rangeheader option that must be matched. IP-Option ::= < AVP Header: XXX > { IP-Option-Type } * [IP-Address-StartIP-Option-Value ] [IP-Address-EndNegated ] * [ AVP ] If one or more IP-Option-Value AVPs are present, one of theIP-Address-Start AVP is not included thenvalues MUST match theaddress range starts fromvalue in thefirst validIPaddress up to and including the specified IP-Address-End address.header option. If theIP-Address-EndIP-Option-Value AVP isnot included thenabsent, theaddress range starts atoption type MUST be present in theaddress specified byIP header but theIP-Address-Startvalue is wild carded. The Negated AVPand includes allis used in conjunction with theremaining validIP-Option-Value AVPs to specify IPaddresses. For the IP-Address-Rangeheader options which do not match specific values. The Negated AVPto be valid,is used without theIP-Address-StartIP-Option-Value AVPMUSTto specify IP headers which do not containa value that is less than that oftheIP-Address-End AVP. 5.7.4. IP-Address-Startoption type. 5.8.4. IP-Option-Type AVP TheIP-Address-StartIP-Option-Type AVP (AVP Code TBD) is of typeAddressEnumerated andspecifiesthefirst IP address (IPv4 or IPv6) address of anvalues are managed by IANA under the IPaddress range. 5.7.5. IP-Address-EndOption Numbers registry [IPOPTIONS]. 5.8.5. IP-Option-Value AVP TheIP-Address-EndIP-Option-Value AVP (AVP Code TBD) is of typeAddressOctetString andspecifiescontains thelast IP address (IPv4 or IPv6) address of an address range. 5.7.6. IP-Address-Maskoption value that must be matched. 5.8.6. TCP-Option AVP TheIP-Address-MaskTCP-Option AVP (AVP Code TBD) is of type Grouped and specifiesan IP address range usingabase IP address and the bit- widthTCP header option that must be matched. TCP-Option ::= < AVP Header: XXX > { TCP-Option-Type } * [ TCP-Option-Value ] [ Negated ] * [ AVP ] If one or more TCP-Option-Value AVPs are present, one of themask. For example, a range expressed as 1.2.3.0/24 willvalues MUST matchall IP addresses from 1.2.3.0 up to and including 1.2.3.255. The bit-widththe value in the TCP header option. If the TCP-Option- Value AVP is absent, the option type MUST bevalid forpresent in thetype of IP address. IP-Address-Mask ::= <TCP header but the value is wild carded. The Negated AVPHeader: XXX > { IP-Address } { IP-Bit-Mask-Width } * [is used in conjunction which the TCP-Option-Value AVPs to specify TCP header options which do not match specific values. The Negated AVP] 5.7.7. IP-Mask-Bit-Mask-Widthis used without the TCP-Option-Value AVP to specify TCP headers which do not contain the option type. 5.8.7. TCP-Option-Type AVP TheIP-Bit-Mask-WidthTCP-Option-Type AVP (AVP Code TBD) is of typeOctetString. The value is a single octetEnumerated andspecifiesthewidth of an IP address bit- mask. 5.7.8. MAC-Addressvalues are managed by IANA under the TCP Option Numbers registry [TCPOPTIONS]. 5.8.8. TCP-Option-Value AVP TheMAC-AddressTCP-Option-Value AVP (AVP Code TBD) is of type OctetString andspecifies a single layer 2 address in MAC-48 format. The value is a 6 octets encoding of the address as it would appear incontains theframe header. 5.7.9. MAC-Address-Maskoption value that must be matched. 5.8.9. TCP-Flags AVP TheMAC-Address-MaskTCP-Flags AVP (AVP Code TBD) is of type Grouped and specifies a set ofMAC addresses using a bit mask to indicate the bits of the MAC addresses whichTCP control flags that mustfit to the specified MAC address attribute. For example, a MAC-Address-Mask with the MAC-Address as 00-10-A4-23-00-00 and with a MAC-Address-Mask-Pattern of FF-FF-FF-FF- 00-00 will match all MAC addresses from 00-10-A4-23-00-00 up to and including 00-10-A4-23-FF-FF. MAC-Address-Maskbe matched. TCP-Flags ::= < AVP Header: XXX > 1* {MAC-Address } { MAC-Address-Mask-PatternTCP-Flag-Type } [ Negated ] * [ AVP ]5.7.10. MAC-Address-Mask-Pattern AVP The MAC-Address-Mask-PatternIf the Negated AVP(AVP Code TBD)isof type OctetString. The valuenot present, the TCP-Flag-Type AVPs specifies which flags MUST be set. If the Negated AVP isa 6 octets specifyingpresent, thebit positions of a MAC address, that are taken for matching. 5.7.11. EUI64-AddressTCP- Flag-Type AVPs specifies which flags MUST be cleared. 5.8.10. TCP-Flag-Type AVP TheEUI64-AddressTCP-Flag-Type AVP (AVP Code TBD) is of typeOctetStringEnumerated and specifies asingle layerTCP control flag type that must be matched. Value | Name and Semantic ------+------------------------------------------------------------ 0 | RESERVED 1 | CWR - Congestion Window Reduced. 2address in EUI-64 format. The value| ECE - ECN-Echo. TCP peer isa 8 octets encoding of the address as it would appear inECN capable. 3 | URG - URGent pointer field is significant. 4 | ACK - ACKnowledgment field is significant. 5 | PSH - Push function. 6 | RST - Reset theframe header. 5.7.12. EUI64-Address-Mask AVPconnection. 7 | SYN - Synchronize sequence numbers. 8 | FIN - No more data from sender. 5.8.11. ICMP-Type TheEUI64-Address-MaskICMP-Type AVP (AVP Code TBD) is of type Grouped and specifies aset of EUI64 addresses using a bit mask to indicate the bits of the EUI64 addresses whichICMP message type that mustfit to the specified EUI64 address attribute. For example, a EUI64-Address-Mask with the EUI64- Address as 00-10-A4-FF-FE-23-00-00 and with a EUI64-Address-Mask- Pattern of FF-FF-FF-FF-FF-FF-00-00 will match all EUI64 addresses from 00-10-A4-FF-FE-23-00-00 up to and including 00-10-A4-FF-FE-23- FF-FF. EUI64-Address-Maskbe matched. ICMP-Type ::= < AVP Header: XXX > {EUI64-Address } { EUI64-Address-Mask-PatternICMP-Type-Number } * [ ICMP-Code ] [ Negated ] * [ AVP ]5.7.13. EUI64-Address-Mask-PatternIf the ICMP-Code AVP is present, the value MUST match that in the ICMP header. If the ICMP-Code AVP is absent, the ICMP type MUST be present in the ICMP header but the code is wild carded. TheEUI64-Address-Mask-PatternNegated AVP(AVP Code TBD)isof type OctetString.used in conjunction which the ICMP-Code AVPs to specify ICMP codes which do not match specific values. ThevalueNegated AVP isa 8 octets specifyingused without thebit positions of a EUI64 address, that are taken for matching. 5.7.14. VLAN-IDICMP-Code AVPVLAN-IDto specify ICMP headers which do not contain the ICMP type. 5.8.12. ICMP-Type-Number AVP The ICMP-Type-Number AVP (AVP Code TBD) is of typeOctetString. The value is a double octet encoded in Network Byte Order. The value of this field specifies the matching value for the IEEE 802.1Q VLAN-ID bits. Only the lower (i.e., rightmost) 12 bits ofEnumerated and thespecified 2 octet VLAN-ID fieldvalues aresignificant; the upper four bits shall be ignored for comparison. If this field is omitted, then comparison ofmanaged by IANA under theIEEE 802.1Q VLAN-ID bits for this entry is irrelevant. If this parameter is specified for an entry, then Ethernet packets without IEEE 802.1Q encapsulation shall not match this entry. 5.7.15. PortICMP Type Numbers registry [ICMPTYPE]. 5.8.13. ICMP-Code AVP ThePortICMP-Code AVP (AVP Code TBD) is of typeInteger32 in the range of 0 to 65535Enumerated andspecifiestheTCP or UDP port number to match. 5.7.16. Port-Rangevalues are managed by IANA under the ICMP Type Numbers registry [ICMPTYPE]. 5.8.14. ETH-Option AVP ThePort-RangeETH-Option AVP (AVP Code TBD) is of type Grouped and specifiesan inclusive range of ports. Port-RangeEthernet specific attributes. ETH-Option ::= < AVP Header: XXX > { ETH-Proto-Type } * [Port-StartVLAN-ID-Range ] * [Port-EndETH-Priority-Range ] * [ 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. 5.7.17. 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. 5.7.18. Port-End5.8.15. ETH-Proto-Type AVP ThePort-EndEth-Proto-Type AVP (AVP Code TBD) is of typeInteger32Grouped and specifies thelast port number of an IP port range. 5.7.19. Use-Assigned-Addressencapsulated protocol type. ETH-Ether-Type and ETH-SAP are mutually exclusive. ETH-Proto-Type ::= < AVP Header: XXX > * [ ETH-Ether-Type ] * [ ETH-SAP ] * [ AVP ] 5.8.16. ETH-Ether-Type AVPIn some scenarios, the AAA does not know the IP address assigned to the Managed Terminal at the time that the Classifier is sent to the Classifying Entity.TheUse-Assigned-AddressETH-Ether-Type AVP (AVP Code TBD) is of typeEnumerated containing the values of True or False. When present and set to True, it representsOctetString. The value is a double octet theIP address assigned tocontains theManaged Terminal. Value | Name ------+-------- 0 | False 1 | True 5.8. Header Option AVPs The Classifier AVP may contain one or morevalue of thefollowing AVPsEthertype field in the packet tomatch onmatch. This AVP MAY be present in thevarious possible IP, TCPcase of DIX orICMP header options. 5.8.1. Diffserv-Code-Pointif SNAP is present at 802.2 but the ETH-SAP AVP MUST NOT be present in this case. 5.8.17. ETH-SAP AVP TheDiffserv-Code-PointETH-SAP AVP (AVP Code TBD) is of typeEnumerated and specifiesOctetString. The value is a double octet representing theDifferentiated Services Field Codepoints to match802.2 SAP as specified inthe IP header.[IEEE802.2]. Thevalues are managed by IANA underfirst octet contains theDifferentiated Services Field Codepoints registry [DSCP]. 5.8.2. Fragmentation-FlagDSAP and the second the SSAP. 5.8.18. VLAN-ID-Range AVP TheFragmentation-FlagVLAN-ID-Range AVP (AVP Code TBD) is of typeEnumeratedGrouped and specifies thepacket fragmentation flagsVLAN range tomatch inmatch. VLAN identities are either specified by a single VLAN-ID according to [IEEE802.1Q] or by a combination of Customer and Service VLAN-IDs according to [IEEE802.1ad]. The single VLAN-ID is represented by the C-VID-Start and C-VID-End AVPs and theIP header. Value | NameS-VID-Start andSemantic ------+------------------------------------------------------------ 0 | RESERVED 1 | Don't Fragment (DF) 2 | More Fragments (MF) 5.8.3. IP-Option AVP The IP-OptionS-VID-End AVPs SHALL be ommitted in this case. If the VLAN-ID-Range AVP(AVP Code TBD)is omitted from the Classifier, then comparison oftype Grouped and specifies an IP header option that must be matched. IP-Optionthe VLAN identity of the packet is irrelevant. VLAN-ID-Range ::= < AVP Header: XXX >{ IP-Option-Type } *[IP-Option-ValueS-VID-Start ] [NegatedS-VID-End ] [ C-VID-Start ] [ C-VID-End ] * [ AVP ]If one or more IP-Option-ValueWhen the S-VID-Start AVP is present but the S-VID-End AVP is absent, the S-VID-Start AVP value MUST equal the value of the IEEE 802.1ad S-VID bits specified in [IEEE802.1ad] for a successful match. When both S-VID-Start and S-VID-End AVPs are present,onethe value of thevaluesIEEE 802.1ad S-VID bits MUSTmatchbe greater than or equal to the S-VID- Start AVP valueinand less than or equal to theIP header option.S-VID-End AVP value for a successful match. If theIP-Option-ValueS-VID-Start and S-VID-End AVPs are omitted, then existence of IEEE802.1ad encapsulation or comparison of the IEEE 802.1ad S-VID bits is irrelevamt for this Classifier. If the S-VID-Start and S-VID-End AVPs are specified, then Ethernet packets without IEEE 802.1ad encapsulation MUST NOT match this Classifier. When the C-VID-Start AVP is present but the C-VID-End AVP is absent, theoption typeC-VID-Start AVP value MUSTbe presentequal the value of the IEEE 802.1ad C-VID bits specified in [IEEE802.1ad] or theIP header butIEEE 802.1Q VLAN-ID bits specified in [IEEE802.1Q] for a successful match. When both C-VID- Start and C-VID-End AVPs are present, the valueis wild carded. The Negatedof the IEEE 802.1ad C-VID bits or the IEEE 802.1Q VLAN-ID bits MUST be greater than or equal to the C-VID-Start AVP value and less than or equal to the C-VID-End AVP value for a successful match. If the C-VID-Start and C-VID-End AVPs are omitted, then comparison of the IEEE 802.1ad C-VID bits or IEEE 802.1Q VLAN-ID bits for this Classifier isused in conjunction withirrelevant. If theIP-Option-ValueC-VID-Start and C-VID-End AVPsto specify IP header options which do not match specific values. The Negated AVP is usedare specified, then Ethernet packets withoutthe IP-Option-Value AVP to specify IP headers which do not contain the option type. 5.8.4. IP-Option-TypeIEEE 802.1ad or IEEE 802.1Q encapsulation MUST NOT match this Classifier. 5.8.19. S-VID-Start AVP TheIP-Option-TypeS-VID-Start AVP (AVP Code TBD) is of typeEnumerated andUnsigned32. The value MUST be in thevalues are managed by IANA underrange from 0 to 4095. The value of this AVP specifies theIP Option Numbers registry [IPOPTIONS]. 5.8.5. IP-Option-Valuestart value of the range of S-VID VLAN-IDs to be matched. 5.8.20. S-VID-End AVP TheIP-Option-ValueS-VID-End AVP (AVP Code TBD) is of typeOctetString and containsUnsigned32. The value MUST be in theoptionrange from 0 to 4095. The valuethat mustof this AVP specifies the end value of the range of S-VID VLAN-IDs to be matched.5.8.6. TCP-Option5.8.21. C-VID-Start AVP TheTCP-OptionC-VID-Start AVP (AVP Code TBD) is of typeGrouped and specifies a TCP header option that must be matched. TCP-Option ::= < AVP Header: XXX > { TCP-Option-Type } * [ TCP-Option-Value ] [ Negated ] * [ AVP ] If one or more TCP-Option-Value AVPs are present, one of the values MUST match theUnsigned32. The valuein the TCP header option. If the TCP-Option- Value AVP is absent, the option typeMUST bepresent in the TCP header but the value is wild carded. The Negated AVP is usedinconjunction whichtheTCP-Option-Value AVPsrange from 0 tospecify TCP header options which do not match specific values.4095. TheNegatedvalue of this AVPis used withoutspecifies theTCP-Option-Value AVP to specify TCP headers which do not containstart value of theoption type. 5.8.7. TCP-Option-Typerange of C-VID VLAN-IDs to be matched. 5.8.22. C-VID-End AVP TheTCP-Option-TypeC-VID-End AVP (AVP Code TBD) is of typeEnumerated and the values are managed by IANA underUnsigned32. The value MUST be in theTCP Option Numbers registry [TCPOPTIONS]. 5.8.8. TCP-Option-Value AVPrange from 0 to 4095. TheTCP-Option-Value AVP (AVP Code TBD) isvalue oftype OctetString and containsthis AVP specifies theoptionend valuethat mustof the range of C-VID VLAN-IDs to be matched.5.8.9. TCP-Flags5.8.23. ETH-Priority-Range AVP TheTCP-FlagsETH-Priority-Range AVP (AVP Code TBD) is of type Grouped and specifiesa setan 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 ofTCP control flags that must be matched. TCP-Flagsthe IEEE 802.1D user_priority parameter for this Classifier is irrelevant. ETH-Priority-Range ::= < AVP Header: XXX >1* { TCP-Flag-Type }* [NegatedETH-Low-Priority ] * [ ETH-High-Priority ] * [ AVP ]If the Negated5.8.24. ETH-Low-Priority AVPis not present, the TCP-Flag-Type AVPs specifies which flags MUST be set. If the NegatedThe ETH-Low-Priority AVP (AVP Code TBD) ispresent, the TCP- Flag-Type AVPs specifies which flagsof type Unsigned32. The value MUST becleared. 5.8.10. TCP-Flag-Typein the range from 0 to 7. 5.8.25. ETH-High-Priority AVP TheTCP-Flag-TypeETH-High-Priority AVP (AVP Code TBD) is of typeEnumerated and specifies a TCP control flag type that mustUnsigned32. The value MUST bematched. Value | Name and Semantic ------+------------------------------------------------------------in the range from 0| RESERVED 1 | CWR - Congestion Window Reduced. 2 | ECE - ECN-Echo. TCP peer is ECN capable. 3 | URG - URGent pointer field is significant. 4 | ACK - ACKnowledgment fieldto 7. 6. Time Of Day AVPs In many QoS applications, the QoS specification applied to the traffic flow issignificant. 5 | PSH - Push function. 6 | RST - Resetconditional upon theconnection. 7 | SYN - Synchronize sequence numbers. 8 | FIN - Notime of day when the flow was observed. The following sections define AVPs that can be used to express one or moredata from sender. 5.8.11. ICMP-Typetime windows which determine when a QoS specification is applicable to a traffic flow. 6.1. Time-Of-Day-Condition AVP TheICMP-TypeTime-Of-Day-Condition AVP (AVP Code TBD) is of type Grouped and specifiesa ICMP message type that must be matched. ICMP-Typeone or more time windows. Time-Of-Day-Condition ::= < AVP Header: XXX >{ ICMP-Type-Number } *[ICMP-CodeTime-Of-Day-Start ] [NegatedTime-Of-Day-End ] [ Day-Of-Week-Mask ] [ Day-Of-Month-Mask ] [ Month-Of-Year-Mask ] [ Absolute-Start-Time ] [ Absolute-End-Time ] [ Timezone-Flag ] * [ AVP ] Ifthe ICMP-Codemore than one instance of this AVP ispresent,present in thevalueExtended-QoS- Filter-Rule AVP, the current time at QoS rule evaluation MUSTmatch thatbe within at least one of the time windows specified in one of theICMP header. IfTime- Of-Day-Condition AVPs. When theICMP-CodeTime-Of-Day-Condition AVPis absent, the ICMP type MUST beand Classifier AVP are present in theICMP header butsame Extended-QoS-Filter-Rule AVP, both thecode is wild carded.time of day and packet classification conditions MUST match for the QoS specification to be applied. For example, a time window for 9am to 5pm (local time) from Monday to Friday would be expressed as: Time-Of-Day-Condition = { Time-Of-Day-Start = 32400; Time-Of-Day-End = 61200; Day-Of-Week-Mask = ( MONDAY | TUESDAY | WEDNESDAY | THURSDAY | FRIDAY ); Timezone-Flag = LOCAL; } 6.2. Time-Of-Day-Start AVP TheNegatedTime-Of-Day-Start AVP (AVP Code TBD) isusedof type Unsigned32. The value MUST be inconjunction whichtheICMP-Code AVPsrange from 0 tospecify ICMP codes which do not match specific values.86400. TheNegatedvalue of this AVPis used withoutspecifies theICMP-Codestart of an inclusive time window expressed as the offset in seconds from midnight. If this AVPto specify ICMP headers which do not containis absent from theICMP type. 5.8.12. ICMP-Type-NumberTime-Of-Day-Condition AVP, the time window starts at midnight. 6.3. Time-Of-Day-End AVP TheICMP-Type-NumberTime-Of-Day-End AVP (AVP Code TBD) is of typeEnumerated and the values are managed by IANA underUnsigned32. The value MUST be in theICMP Type Numbers registry [ICMPTYPE]. 5.8.13. ICMP-Code AVPrange from 1 to 86400. TheICMP-Codevalue of this AVP(AVP Code TBD) isspecifies the end oftype Enumerated andan inclusive time window expressed as thevalues are managed by IANA underoffset in seconds from midnight. If this AVP is absent from theICMP Type Numbers registry [ICMPTYPE]. 5.8.14. ETH-OptionTime-Of- Day-Condition AVP, the time window ends one second before midnight. 6.4. Day-Of-Week-Mask AVP TheETH-OptionDay-Of-Week-Mask AVP (AVP Code TBD) is of typeGrouped andUnsigned32. The value is a bitmask which specifiesEthernet specific classifiers. ETH-Option ::= < AVP Header: XXX > { ETH-Proto-Type } * [ ETH-VLAN-ID ] * [ ETH-Priority-Range ] * [the day of the week for the time window to match. This document specifies the following bits: Bit | Name ------+------------ 0 | SUNDAY 1 | MONDAY 2 | TUESDAY 3 | WEDNESDAY 4 | THURSDAY 5 | FRIDAY 6 | SATURDAY The bit MUST be set for the time window to match on the corresponding day of the week. Bit 0 is the most significant bit and unused bits MUST be cleared. If this AVP] 5.8.15. ETH-Proto-Typeis absent from the Time-Of-Day- Condition AVP, the time windows match on all days of the week. 6.5. Day-Of-Month-Mask AVP TheEth-Proto-TypeDay-Of-Week-Month AVP (AVP Code TBD) is of typeGrouped andUnsigned32. The value MUST be in the range from 0 to 2147483647. The value is a bitmask which specifies theencapsulated protocol type. ETH-Ether-Typedays of the month where bit 0 represents the first day of the month through to bit 30 which represents the last day of the month. The bit MUST be set for the time window to match on the corresponding day of the month. Bit 0 is the most significant bit andETH-SAP are mutually exclusive. ETH-Proto-Type ::= < AVP Header: XXX > * [ ETH-Ether-Type ] * [ ETH-SAP ] * [unused bits MUST be cleared. If this AVP] 5.8.16. ETH-Ether-Typeis absent from the Time-Of-Day-Condition AVP, the time windows match on all days of the month. 6.6. Month-Of-Year-Mask AVP TheETH-Ether-TypeMonth-Of-Year-Month AVP (AVP Code TBD) is of typeOctetString.Unsigned32. The value is adouble octet the containsbitmask which specifies thevaluemonths of theEthertype thatyear for thepacket shall match in ordertime window tomatchmatch. This document specifies therule. It mightfollowing bits: Bit | Name ------+----------- 0 | JANUARY 1 | FEBRUARY 2 | MARCH 3 | APRIL 4 | MAY 5 | JUNE 6 | JULY 7 | AUGUST 8 | SEPTEMBER 9 | OCTOBER 10 | NOVEMBER 11 | DECEMBER The bit MUST bepresent in caseset for the time window to match on the corresponding month ofDIX or if SNAPthe year. Bit 0 ispresent at 802.2 (SAP shall notthe most significant bit and unused bits MUST bepresent incleared. If thiscase). 5.8.17. ETH-SAPAVP is absent from the Time-Of-Day- Condition AVP, the time windows match during all months of the year. 6.7. Absolute-Start-Time AVP TheETH-SAPAbsolute-Start-Time AVP (AVP Code TBD) is of typeOctetString.Time. The valueis a double octet representingof this AVP specifies the802.2 SAP as specifiedtime in"IEEE Standards for Local Area Networks: Logical Link Control". The first octet containsseconds since January 1, 1900, 00:00 UTC when theDSAP andtime window starts. If this AVP is absent from thesecondTime-Of-Day-Condition AVP, theSSAP. 5.8.18. ETH-Priority-Rangetime window starts on January 1, 1900, 00:00 UTC. 6.8. Absolute-End-Time AVP TheETH-Priority-RangeTime-Of-Day-End AVP (AVP Code TBD) is of typeGrouped andTime. The value of this AVP specifiesa valid priority range in betweentheLow-priority AVP totime in seconds since January 1, 1900, 00:00 UTC when theHigh-priority AVP specified. An Ethernet packet with IEEE 802.1D user_priority value "priority" matches these parameters if priority is greater than or equal to pri-low and priority is less than or equal to pri-high.time window ends. If thisfieldAVP isomitted, then comparison ofabsent from theIEEE 802.1D user_priority bits for this entryTime- Of-Day-Condition AVP, the time window isirrelevant. ETH-Priority-Range ::= < AVP Header: XXX > * [ ETH-Low-Priority ] * [ ETH-High-Priority ] * [ AVP ] 5.8.19. ETH-Low-Priorityopen-ended. 6.9. Timezone-Flag AVP TheETH-Low-PriorityTimezone-Flag AVP (AVP Code TBD) is of typeOctetString. The valueEnumerated and indicates whether the time windows are specified in UTC, local time at the managed terminal or as an offset from UTC. If this AVP isa single octet with a valid rangeabsent from the Time-Of-Day-Condition AVP, the time windows are in UTC. This document defines the following values: Value | Name and Semantic ------+-------------------------------------------------- 0to 7. 5.8.20. ETH-High-Priority| RESERVED 1 | UTC - The time windows are expressed in UTC. 2 | LOCAL - The time windows are expressed in local | time at the Managed Terminal. 3 | OFFSET - The time windows are expressed as an | offset from UTC (see Timezone-Offset AVP). 6.10. Timezone-Offset AVP TheETH-High-PriorityTimezone-Offset AVP (AVP Code TBD) is of typeOctetString.Integer32. The valueis a single octet with a validof this AVP MUST be in the range from0-43200 to 43200. It specifies the offset in seconds from UTC that was used to express 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. 7.6.Examples This section shows a number of signaling flows where QoS negotiation and authorization is part of the conventional NASREQ, EAP or Credit Control applications message exchanges. The signalling flows for the Diameter QoS Application are described in [I-D.ietf-dime-diameter-qos].6.1.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 Extended-QoS- Filter-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 | | |------------------------------->| | | | | | Diameter-EAP-Answer | | Result-Code=DIAMETER_MULTI_ROUND_AUTH | | | EAP-Payload(EAP Request #1) | | |<-------------------------------| | EAP Request(Identity) | | |<------------------------------| | : : : : <<<more message exchanges>>> : : : : | | | | EAP Response #N | | |------------------------------>| | | | Diameter-EAP-Request | | | EAP-Payload(EAP Response #N) | | |------------------------------->| | | | | | Diameter-EAP-Answer | | | Result-Code=DIAMETER_SUCCESS | | | EAP-Payload(EAP Success) | | | [EAP-Master-Session-Key] | | | (authorization AVPs) | | | QoS-Resources(QoS-Authorized) | | |<-------------------------------| | | | | EAP Success | | |<------------------------------| | | | | Figure 2: Example of a Diameter EAP enhanced with QoS Information6.2.7.2. Diameter NASREQ with QoS Information Figure 3 shows a similar pre-provisioned QoS signaling as in Figure 2 but using the NASREQ application instead of EAP application. End Diameter Host NAS Server | | | | Start Network | | | Attachment | | |<---------------->| | | | | | |AA-Request | | |NASREQ-Payload | | |QoS-Capability | | +----------------------------->| | | | | | AA-Answer| | Result-Code=DIAMETER_MULTI_ROUND_AUTH| | NASREQ-Payload(NASREQ Request #1)| | |<-----------------------------+ | | | | Request | | |<-----------------+ | | | | : : : : <<<more message exchanges>>> : : : : | Response #N | | +----------------->| | | | | | |AA-Request | | |NASREQ-Payload ( Response #N )| | +----------------------------->| | | | | | AA-Answer| | | Result-Code=DIAMETER_SUCCESS| | | (authorization AVPs)| | |QoS-Resources(QoS-Authorized) | | |<-----------------------------+ | | | | Success | | |<-----------------+ | | | | Figure 3: Example of a Diameter NASREQ enhanced with QoS Information6.3.7.3. QoS Authorization Figure 4 shows an example of authorization only QoS signaling as part of the NASREQ message exchange. The NAS provides the Diameter server with the "QoS-Desired" QoS-Semantics AVP included in the QoS- Resources AVP. The Diameter server then either authorizes the indicated QoS or rejects the request and informs the NAS about the result. In this scenario the NAS does not need to include the QoS- Capability AVP in the AAR message as the QoS-Resources AVP implicitly does the same and also the NAS is authorizing a specific QoS profile, not a pre-provisioned one. End Diameter Host NAS Server | | | | | | | QoS Request | | +----------------->| | | | | | |AA-Request | | |Auth-Request-Type=AUTHORIZE_ONLY | |NASREQ-Payload | | |QoS-Resources(QoS-Desired) | | +----------------------------->| | | | | | AA-Answer| | | NASREQ-Payload(Success)| | | QoS-Resources(QoS-Authorized)| | |<-----------------------------+ | Accept | | |<-----------------+ | | | | | | | | | | Figure 4: Example of an Authorization-Only Message Flow6.4.7.4. Diameter Server Initiated Re-authorization of QoS Figure 5 shows a message exchange for a Diameter server initiated QoS re-authorization procedure. The Diameter server sends the NAS a RAR message requesting re-authorization for an existing session and the NAS acknowledges it with a RAA message. The NAS is aware of its existing QoS profile and information for the ongoing session that the Diameter server requested for re-authorization. Thus, the NAS must initiate re-authorization of the existing QoS profile. The re- authorization procedure is the same as in Figure 4. End Diameter Host NAS Server | | | | | | : : : : <<<Initial Message Exchanges>>> : : : : | | | | | RA-Request | | |<-----------------------------+ | | | | |RA-Answer | | |Result-Code=DIAMETER_SUCCESS | | +----------------------------->| | | | | | | | |AA-Request | | |NASREQ-Payload | | |Auth-Request-Type=AUTHORIZE_ONLY | |QoS-Resources(QoS-Desired) | | +----------------------------->| | | | | | AA-Answer| | | Result-Code=DIAMETER_SUCCESS| | | (authorization AVPs)| | | QoS-Resources(QoS-Authorized)| | |<-----------------------------+ | | | Figure 5: Example of a Server-initiated Re-Authorization Procedure6.5.7.5. Diameter Credit Control with QoS Information In this case the User is charged as soon as the Service Element (CC client) receives the service request. In this case the client uses the "QoS-Desired" QoS-Semantics parameter in the QoS-Resources AVP that it sends to the Accounitng server. The server responds with a "QoS-Available" QoS-Semantics parameter in the QoS-Resources AVP Service Element End User (CC Client) B CC Server | | | | |(1) Service Request | | | |-------------------->| | | | |(2) CCR (event, DIRECT_DEBITING,| | | QoS-Resources[QoS-desired]) | | |-------------------------------->| | |(3) CCA (Granted-Units, QoS- | | | Resources[QoS-Authorized]) | | |<--------------------------------| |(4) Service Delivery | | | |<--------------------| | | |(5) Begin service | | | |<------------------------------------>| | | | | | . . . . . . . . Figure 6: Example for a One-Time Diameter Credit Control Charging Event6.6.7.6. Classifier Examples Example: Classify all packets from hosts on subnet 12.34.56.00/24 to ports 80, 8090 or 443 on web servers 23.45.67.123, 23.45.68.124, 23.45.69.125.ClassiferClassifier = { Classifier-Id = "web_svr_example"; Protocol = TCP; Direction = OUT; From-Spec = { IP-Address-Mask = { IP-Address = 12.34.56.00; IP-Bit-Mask-Width = 24; } } To-Spec = { IP-Address = 23.45.67.123; IP-Address = 23.45.68.124; IP-Address = 23.45.69.125; Port = 80; Port = 8080; Port = 443; } } Example: Any SIP signalling traffic from a device with a MAC address of 01:23:45:67:89:ab to servers with IP addresses in the range 34.56.78.90 to 34.56.78.190.ClassiferClassifier = { Classifier-Id = "web_svr_example"; Protocol = UDP; Direction = OUT; From-Spec = { MAC-Address = 01:23:45:67:89:ab; } To-Spec = { IP-Address-Range = { IP-Address-Start = 34.56.78.90; IP-Address-End = 34.56.78.190; } Port = 5060; Port = 3478; Port-Range = { Port-Start = 16348; Port-End = 32768; } } }7.8. Acknowledgments We would like to thank Victor Fajardo, Tseno Tsenov, Robert Hancock, Jukka Manner, Cornelia Kappler, Xiaoming Fu, Frank Alfano,Tolga Asveren, MikeMontemurro,GlenMontemurro, Glen Zorn, Avri Doria, Dong Sun, Tina Tsou, Pete McCann, GeorgiosKaragiannis andKaragiannis, ElwynDaviesDavies, Max Riegel and Yong Li for their comments.8.9. Contributors Max Riegel contributed the VLAN sections. 10. IANA Considerations 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-Capability TBD 3.1 Grouped | |QoS-Profile-Template TBD 3.2 Unsigned32 | |Vendor-Specific-QoS-Profile-Template TBD 3.3 Grouped | |Extended-QoS-Filter-Rule TBD 3.5 Grouped | |QoS-Semantics TBD 3.6 Enumerated | |QoS-Parameters TBD 3.7 OctetString | |QoS-Rule-Precedence TBD 3.8 Unsigned32 | |Classifier TBD 5.1 Grouped | |Classifier-ID TBD 5.2 OctetString | |Protocol TBD 5.3 Enumerated | |Direction TBD 5.4 Enumerated | |From-Spec TBD 5.5 Grouped | |To-Spec TBD 5.6 Grouped | |Negated TBD 5.7.1 Enumerated | |IP-Address TBD 5.7.2 Address | |IP-Address-Range TBD 5.7.3 Grouped | |IP-Address-Start TBD 5.7.4 Address | |IP-Address-End TBD 5.7.5 Address | |IP-Address-Mask TBD 5.7.6 Grouped | |IP-Mask-Bit-Mask-Width TBD 5.7.7 OctetString | |MAC-Address TBD 5.7.8 OctetString | |MAC-Address-Mask TBD 5.7.9 Grouped | |MAC-Address-Mask-Pattern TBD 5.7.10 OctetString | |EUI64-Address TBD 5.7.11 OctetString | |EUI64-Address-Mask TBD 5.7.12 Grouped | |EUI64-Address-Mask-Pattern TBD 5.7.13 OctetString ||VLAN-ID TBD 5.7.14 OctetString ||Port TBD5.7.155.7.14 Integer32 | |Port-Range TBD5.7.165.7.15 Grouped | |Port-Start TBD5.7.175.7.16 Integer32 | |Port-End TBD5.7.185.7.17 Integer32 | |Use-Assigned-Address TBD5.7.195.7.18 Enumerated | |Diffserv-Code-Point TBD 5.8.1 Enumerated | |Fragmentation-Flag TBD 5.8.2 Enumerated | |IP-Option TBD 5.8.3 Grouped | |IP-Option-Type TBD 5.8.4 Enumerated | |IP-Option-Value TBD 5.8.5 OctetString | |TCP-Option TBD 5.8.6 Grouped | |TCP-Option-Type TBD 5.8.7 Enumerated | |TCP-Option-Value TBD 5.8.8 OctetString | |TCP-Flags TBD 5.8.9 Grouped | |TCP-Flag-Type TBD 5.8.10 Enumerated | |ICMP-Type TBD 5.8.11 Grouped | |ICMP-Type-Number TBD 5.8.12 Enumerated | |ICMP-Code TBD 5.8.13 Enumerated | |ETH-Option TBD 5.8.14 Grouped | |ETH-Proto-Type TBD 5.8.15 Grouped | |ETH-Ether-Type TBD 5.8.16 OctetString | |ETH-SAP TBD 5.8.17 OctetString ||ETH-Priority-Range|VLAN-ID-Range TBD 5.8.18 Grouped ||ETH-Low-Priority|S-VID-Start TBD 5.8.19OctetStringUnsigned32 ||ETH-High-Priority|S-VID-End TBD 5.8.20OctetStringUnsigned32 | |C-VID-Start TBD 5.8.21 Unsigned32 | |C-VID-End TBD 5.8.22 Unsigned32 | |ETH-Priority-Range TBD 5.8.23 Grouped | |ETH-Low-Priority TBD 5.8.24 Unsigned32 | |ETH-High-Priority TBD 5.8.25 Unsigned32 | |Time-Of-Day-Condition TBD 6.1 Grouped | |Time-Of-Day-Start TBD 6.2 Grouped | |Time-Of-Day-End TBD 6.3 Unsigned32 | |Day-Of-Week-Mask TBD 6.4 Unsigned32 | |Day-Of-Month-Mask TBD 6.5 Unsigned32 | |Month-Of-Year-Mask TBD 6.6 Unsigned32 | |Absolute-Start-Time TBD 6.7 Time | |Absolute-End-Time TBD 6.8 Time | |Timezone-Flag TBD 6.9 Enumerated | |Timezone-Offset TBD 6.10 Integer32 | +------------------------------------------------------------------+ IANA is also requested to allocate a registry for the QoS-Semantics. 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. A standards track document is required to depreciate, delete, or modify existing values.9.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 3588bis [I-D.ietf-dime-rfc3588bis]. Use of the AVPs defined in this document MUST take into consideration the security issues and requirements of the Diameter Base protocol.10.12. References10.1.12.1. Normative References [DSCP]IANA,,IANA, "Differentiated Services Field Codepoints", http://www.iana.org/assignments/dscp-registry. [I-D.ietf-dime-qos-parameters] Korhonen, J. and H. Tschofenig, "Quality of Service Parameters for Usage with the AAA Framework", draft-ietf-dime-qos-parameters-06 (work in progress), May 2008. [I-D.ietf-dime-rfc3588bis] Fajardo, V., Arkko, J., Loughney, J., and G. Zorn, "Diameter Base Protocol",draft-ietf-dime-rfc3588bis-10draft-ietf-dime-rfc3588bis-12 (work in progress),JanuarySeptember 2008. [ICMPTYPE]IANA,,IANA, "ICMP Type Numbers", http://www.iana.org/assignments/icmp-parameters. [IEEE802.1D] IEEE, "IEEE Standard for Local and metropolitan area networks, Media Access Control (MAC) Bridges", 2004. [IEEE802.1Q] IEEE, "IEEE Standard for Local and metropolitan area networks, Virtual Bridged Local Area Networks", 2005. [IEEE802.1ad] IEEE, "IEEE Standard for Local and metropolitan area networks, Virtual Bridged Local Area Networks, Amendment 4: Provider Bridges", 2005. [IEEE802.2] IEEE, "IEEE Standard for Information technology, Telecommunications and information exchange between systems, Local and metropolitan area networks, Specific requirements, Part 2: Logical Link Control", 1998. [IPOPTIONS]IANA,,IANA, "IP Option Numbers", http://www.iana.org/assignments/ip-parameters. [PROTOCOL]IANA,,IANA, "Protocol Types", http://www.iana.org/assignments/protocol-numbers. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, "Diameter Network Access Server Application", RFC 4005, August 2005. [TCPOPTIONS]IANA,,IANA, "TCP Option Numbers", http://www.iana.org/assignments/tcp-parameters.10.2.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-05draft-ietf-dime-diameter-qos-06 (work in progress),FebruaryJuly 2008. Authors' Addresses Jouni Korhonen TeliaSonera Teollisuuskatu 13 Sonera FIN-00051 Finland Email: jouni.korhonen@teliasonera.com Hannes Tschofenig Nokia Siemens Networks Linnoitustie 6 Espoo 02600 Finland Phone: +358 (50) 4871445 Email: Hannes.Tschofenig@gmx.net URI: http://www.tschofenig.priv.at Mayutan Arumaithurai University of Goettingen Email: mayutan.arumaithurai@gmail.com Mark Jones (editor) Bridgewater Systems 303 Terry FoxDriveDrive, Suite 500 Ottawa, Ontario K2K 3J1 Canada Phone: +1 613-591-6655 Email: mark.jones@bridgewatersystems.com Avi Lior Bridgewater Systems 303 Terry Fox Drive, Suite 500 Ottawa, OntarioCanadaK2K 3J1 Canada Phone: +1 613-591-6655 Email: avi@bridgewatersystems.com Full Copyright Statement Copyright (C) The IETF Trust (2008). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.