draft-ietf-dime-qos-attributes-08.txt   draft-ietf-dime-qos-attributes-09.txt 
Diameter Maintenance and J. Korhonen Diameter Maintenance and J. Korhonen
Extensions (DIME) TeliaSonera Extensions (DIME) H. Tschofenig
Internet-Draft H. Tschofenig Internet-Draft Nokia Siemens Networks
Intended status: Standards Track Nokia Siemens Networks Intended status: Standards Track M. Arumaithurai
Expires: May 1, 2009 M. Arumaithurai Expires: June 21, 2009 University of Goettingen
University of Goettingen
M. Jones, Ed. M. Jones, Ed.
A. Lior A. Lior
Bridgewater Systems Bridgewater Systems
October 28, 2008 December 18, 2008
Quality of Service Attributes for Diameter Quality of Service Attributes for Diameter
draft-ietf-dime-qos-attributes-08.txt draft-ietf-dime-qos-attributes-09.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
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 Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 1, 2009. This Internet-Draft will expire on June 21, 2009.
Copyright Notice
Copyright (c) 2008 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.
Abstract Abstract
This document extends the IPFilterRule AVP functionality of the This document extends the IPFilterRule AVP functionality of the
Diameter Base protocol and the functionality of the QoS-Filter-Rule Diameter Base protocol and the functionality of the QoS-Filter-Rule
AVP defined in RFC 4005. The ability to convey Quality of Service AVP defined in RFC 4005. The ability to convey Quality of Service
information using the AVPs defined in this document is available to information using the AVPs defined in this document is available to
existing and future Diameter applications where permitted by the existing and future Diameter applications where permitted by the
command ABNF. command ABNF.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Diameter QoS Defined AVPs . . . . . . . . . . . . . . . . . . 4 3. Rule Sets and Rules . . . . . . . . . . . . . . . . . . . . . 4
3.1. QoS-Capability AVP . . . . . . . . . . . . . . . . . . . . 4 3.1. Rule-Set AVP . . . . . . . . . . . . . . . . . . . . . . . 4
3.2. QoS-Profile-Template AVP . . . . . . . . . . . . . . . . . 4 3.2. Rule AVP . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.3. Vendor-Specific-QoS-Profile-Template AVP . . . . . . . . . 4 4. Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.4. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 5 4.1. Traffic Classifiers . . . . . . . . . . . . . . . . . . . 5
3.5. Extended-QoS-Filter-Rule AVP . . . . . . . . . . . . . . . 5 4.1.1. Classifier AVP . . . . . . . . . . . . . . . . . . . . 7
3.6. QoS-Semantics . . . . . . . . . . . . . . . . . . . . . . 5 4.1.2. Classifier-ID AVP . . . . . . . . . . . . . . . . . . 8
3.7. QoS-Parameters AVP . . . . . . . . . . . . . . . . . . . . 6 4.1.3. Protocol AVP . . . . . . . . . . . . . . . . . . . . . 8
3.8. QoS-Rule-Precedence AVP . . . . . . . . . . . . . . . . . 6 4.1.4. Direction AVP . . . . . . . . . . . . . . . . . . . . 8
4. Semantics of QoS Parameters . . . . . . . . . . . . . . . . . 6 4.1.5. From-Spec AVP . . . . . . . . . . . . . . . . . . . . 9
5. Diameter Classifier AVPs . . . . . . . . . . . . . . . . . . . 7 4.1.6. To-Spec AVP . . . . . . . . . . . . . . . . . . . . . 10
5.1. Classifier AVP . . . . . . . . . . . . . . . . . . . . . . 9 4.1.7. Source and Destination AVPs . . . . . . . . . . . . . 11
5.2. Classifier-ID AVP . . . . . . . . . . . . . . . . . . . . 10 4.1.8. Header Option AVPs . . . . . . . . . . . . . . . . . . 15
5.3. Protocol AVP . . . . . . . . . . . . . . . . . . . . . . . 10 4.2. Time Of Day AVPs . . . . . . . . . . . . . . . . . . . . . 21
5.4. Direction AVP . . . . . . . . . . . . . . . . . . . . . . 10 4.2.1. Time-Of-Day-Condition AVP . . . . . . . . . . . . . . 21
5.5. From-Spec AVP . . . . . . . . . . . . . . . . . . . . . . 10 4.2.2. Time-Of-Day-Start AVP . . . . . . . . . . . . . . . . 22
5.6. To-Spec AVP . . . . . . . . . . . . . . . . . . . . . . . 11 4.2.3. Time-Of-Day-End AVP . . . . . . . . . . . . . . . . . 22
5.7. Source and Destination AVPs . . . . . . . . . . . . . . . 12 4.2.4. Day-Of-Week-Mask AVP . . . . . . . . . . . . . . . . . 22
5.7.1. Negated AVP . . . . . . . . . . . . . . . . . . . . . 12 4.2.5. Day-Of-Month-Mask AVP . . . . . . . . . . . . . . . . 23
5.7.2. IP-Address AVP . . . . . . . . . . . . . . . . . . . . 13 4.2.6. Month-Of-Year-Mask AVP . . . . . . . . . . . . . . . . 23
5.7.3. IP-Address-Range AVP . . . . . . . . . . . . . . . . . 13 4.2.7. Absolute-Start-Time AVP . . . . . . . . . . . . . . . 23
5.7.4. IP-Address-Start AVP . . . . . . . . . . . . . . . . . 13 4.2.8. Absolute-End-Time AVP . . . . . . . . . . . . . . . . 24
5.7.5. IP-Address-End AVP . . . . . . . . . . . . . . . . . . 13 4.2.9. Timezone-Flag AVP . . . . . . . . . . . . . . . . . . 24
5.7.6. IP-Address-Mask AVP . . . . . . . . . . . . . . . . . 14 4.2.10. Timezone-Offset AVP . . . . . . . . . . . . . . . . . 24
5.7.7. IP-Mask-Bit-Mask-Width AVP . . . . . . . . . . . . . . 14 5. Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.7.8. MAC-Address AVP . . . . . . . . . . . . . . . . . . . 14 5.1. Action AVP . . . . . . . . . . . . . . . . . . . . . . . . 24
5.7.9. MAC-Address-Mask AVP . . . . . . . . . . . . . . . . . 14 5.2. Diameter QoS Defined AVPs . . . . . . . . . . . . . . . . 25
5.7.10. MAC-Address-Mask-Pattern AVP . . . . . . . . . . . . . 14 5.2.1. QoS-Profile-Id AVP . . . . . . . . . . . . . . . . . . 25
5.7.11. EUI64-Address AVP . . . . . . . . . . . . . . . . . . 15 5.2.2. QoS-Profile-Template AVP . . . . . . . . . . . . . . . 25
5.7.12. EUI64-Address-Mask AVP . . . . . . . . . . . . . . . . 15 5.2.3. QoS-Semantics . . . . . . . . . . . . . . . . . . . . 26
5.7.13. EUI64-Address-Mask-Pattern AVP . . . . . . . . . . . . 15 5.2.4. QoS-Parameters AVP . . . . . . . . . . . . . . . . . . 27
5.7.14. Port AVP . . . . . . . . . . . . . . . . . . . . . . . 15 5.2.5. Rule-Precedence AVP . . . . . . . . . . . . . . . . . 27
5.7.15. Port-Range AVP . . . . . . . . . . . . . . . . . . . . 15 5.2.6. Excess-Treatment AVP . . . . . . . . . . . . . . . . . 28
5.7.16. Port-Start AVP . . . . . . . . . . . . . . . . . . . . 16 5.2.7. Excess-Treatment-Action . . . . . . . . . . . . . . . 28
5.7.17. Port-End AVP . . . . . . . . . . . . . . . . . . . . . 16 6. QoS Capability Indication . . . . . . . . . . . . . . . . . . 29
5.7.18. Use-Assigned-Address AVP . . . . . . . . . . . . . . . 16 7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.8. Header Option AVPs . . . . . . . . . . . . . . . . . . . . 16 7.1. Diameter EAP with QoS Information . . . . . . . . . . . . 30
5.8.1. Diffserv-Code-Point AVP . . . . . . . . . . . . . . . 16 7.2. Diameter NASREQ with QoS Information . . . . . . . . . . . 31
5.8.2. Fragmentation-Flag AVP . . . . . . . . . . . . . . . . 16 7.3. QoS Authorization . . . . . . . . . . . . . . . . . . . . 32
5.8.3. IP-Option AVP . . . . . . . . . . . . . . . . . . . . 17 7.4. Diameter Server Initiated Re-authorization of QoS . . . . 33
5.8.4. IP-Option-Type AVP . . . . . . . . . . . . . . . . . . 17 7.5. Diameter Credit Control with QoS Information . . . . . . . 34
5.8.5. IP-Option-Value AVP . . . . . . . . . . . . . . . . . 17 7.6. Classifier Examples . . . . . . . . . . . . . . . . . . . 35
5.8.6. TCP-Option AVP . . . . . . . . . . . . . . . . . . . . 17 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 36
5.8.7. TCP-Option-Type AVP . . . . . . . . . . . . . . . . . 18 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.8.8. TCP-Option-Value AVP . . . . . . . . . . . . . . . . . 18 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36
5.8.9. TCP-Flags AVP . . . . . . . . . . . . . . . . . . . . 18 11. Security Considerations . . . . . . . . . . . . . . . . . . . 39
5.8.10. TCP-Flag-Type AVP . . . . . . . . . . . . . . . . . . 18 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.8.11. ICMP-Type . . . . . . . . . . . . . . . . . . . . . . 19 12.1. Normative References . . . . . . . . . . . . . . . . . . . 39
5.8.12. ICMP-Type-Number AVP . . . . . . . . . . . . . . . . . 19 12.2. Informative References . . . . . . . . . . . . . . . . . . 40
5.8.13. ICMP-Code AVP . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 41
5.8.14. ETH-Option AVP . . . . . . . . . . . . . . . . . . . . 19
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. VLAN-ID-Range AVP . . . . . . . . . . . . . . . . . . 20
5.8.19. S-VID-Start AVP . . . . . . . . . . . . . . . . . . . 21
5.8.20. S-VID-End AVP . . . . . . . . . . . . . . . . . . . . 21
5.8.21. C-VID-Start AVP . . . . . . . . . . . . . . . . . . . 22
5.8.22. C-VID-End AVP . . . . . . . . . . . . . . . . . . . . 22
5.8.23. ETH-Priority-Range AVP . . . . . . . . . . . . . . . . 22
5.8.24. ETH-Low-Priority AVP . . . . . . . . . . . . . . . . . 22
5.8.25. ETH-High-Priority AVP . . . . . . . . . . . . . . . . 22
6. Time Of Day AVPs . . . . . . . . . . . . . . . . . . . . . . . 22
6.1. Time-Of-Day-Condition AVP . . . . . . . . . . . . . . . . 23
6.2. Time-Of-Day-Start AVP . . . . . . . . . . . . . . . . . . 23
6.3. Time-Of-Day-End AVP . . . . . . . . . . . . . . . . . . . 24
6.4. Day-Of-Week-Mask AVP . . . . . . . . . . . . . . . . . . . 24
6.5. Day-Of-Month-Mask AVP . . . . . . . . . . . . . . . . . . 24
6.6. Month-Of-Year-Mask AVP . . . . . . . . . . . . . . . . . . 24
6.7. Absolute-Start-Time AVP . . . . . . . . . . . . . . . . . 25
6.8. Absolute-End-Time AVP . . . . . . . . . . . . . . . . . . 25
6.9. Timezone-Flag AVP . . . . . . . . . . . . . . . . . . . . 25
6.10. Timezone-Offset AVP . . . . . . . . . . . . . . . . . . . 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 1. Introduction
This document defines a number of Diameter Quality of Service (QoS) This document defines a number of Diameter Quality of Service (QoS)
related AVPs that can be used in existing and future Diameter related AVPs that can be used in existing and future Diameter
applications where permitted by the command ABNF. The Extended-QoS- applications where permitted by the command ABNF. The Rule AVP
Filter-Rule AVP thereby replaces the IPFilterRule, defined in RFC thereby replaces the IPFilterRule AVP, defined in RFC 3588 [RFC3588],
3588bis [I-D.ietf-dime-rfc3588bis], and the QoS-Filter-Rule, defined and the QoS-Filter-Rule AVP, defined in RFC 4005 [RFC4005].
in RFC 4005 [RFC4005].
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.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. Diameter QoS Defined AVPs 3. Rule Sets and Rules
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 As mentioned in the introduction the top-level element is the Rule-
Set AVP that encapsulates one or more Rule AVPs.
The Vendor-Specific-QoS-Profile-Template AVP (AVP Code TBD) is of 3.1. Rule-Set AVP
type Grouped and defines a vendor-specific QoS profile template.
The Vendor-Id AVP contains a 32 bit IANA SMI Network Management The Rule-Set AVP (AVP Code TBD) is of type Grouped and describes a
Private Enterprise Code and the QoS-Profile-Template AVP contains the list of policies..
template identifier assigned by the vendor.
Vendor-Specific-QoS-Profile-Template ::= < AVP Header: XXX > Rule-Set ::= < AVP Header: XXX >
{ Vendor-Id } 1*{ Rule }
{ QoS-Profile-Template }
* [ AVP ] * [ AVP ]
3.4. QoS-Resources AVP 3.2. Rule 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 > TheRule AVP (AVP Code TBD) is of type Grouped and defines a specific
* [ Extended-QoS-Filter-Rule ] condition and action combination. The QoS related actions defined in
* [ AVP ] this document therefore 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.
3.5. Extended-QoS-Filter-Rule AVP Rule ::= < AVP Header: XXX >
The Extended-QoS-Filter-Rule AVP (AVP Code TBD) is of type Grouped ; Condition part of a Rule
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 ] [ Classifier ]
* [ Time-Of-Day-Condition ] * [ Time-Of-Day-Condition ]
* [ AVP ]
Either the QoS-Profile-Template or Vendor-Specific-QoS-Profile- ; Action and Meta-Data
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
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: [ Action ]
[ Rule-Precedence ]
Object Type Direction Semantic ; Info about QoS related Actions
--------------------------------------------------------------------- ; ------------------------------
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: [ QoS-Semantics ]
[ QoS-Profile-Template ]
[ QoS-Parameters ]
[ Excess-Treatment ]
C: Diameter client ; Extension Point
S: Diameter server ; ---------------
NA: Not applicable to this document; * [ AVP ]
no semantic defined in this specification
Notes: 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
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].
(1) QoS-Available is only useful in relationship with QoS-Desired 4. Conditions
(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 This section describe the condition part of a rule.
Classifiers are used in many applications to specify how to classify 4.1. Traffic Classifiers
packets. 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.
The Classifiers are sent to on on-path element (e.g. a router) which Classifiers are used in many applications to specify how to select a
uses the classifier to match packets. Figure 1 shows a typical subset of data packets for subsequent treatment as indicated in the
deployment. 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.
+-----------+ +-----------+
+-----------+| +-----------+|
+--------+ +-------------+ +------------+|| +--------+ +-------------+ +------------+||
| | IN | | | ||| | | IN | | | |||
| +--------->| +------------->| ||| | +--------->| +------------->| |||
|Managed | | Classifying | | Unmanaged ||| |Managed | | Classifying | | Unmanaged |||
|Terminal| OUT | Entity | | Terminal ||| |Terminal| OUT | Entity | | Terminal |||
| |<---------+ |<-------------+ ||+ | |<---------+ |<-------------+ ||+
| | | | | |+ | | | | | |+
+--------+ +-------------+ +------------+ +--------+ +-------------+ +------------+
^ ^
| Classifiers | Classifiers
| |
+------+-------+ +------+------+
| | | |
| AAA | | AAA |
| | | |
+--------------+ +-------------+
Figure 1: Example of a Classifier Architecture Figure 1: Example of a Classifier Architecture
The managed terminal, the terminal for which the classifiers are The managed terminal, the terminal for which the classifiers are
being specified is located on the left of the Classifying Entity. being specified is located on the left of the Classifying Entity.
The unmanaged terminal, the terminal that receives packets from the The unmanaged terminal, the terminal that receives packets from the
Managed terminal or sends packets to the managed terminal is located Managed terminal or sends packets to the managed terminal is located
to the right side of the Classifying Entity. to the right side of the Classifying Entity.
The Classifying Entity is responsible for classifying packets that The Classifying Entity is responsible for classifying packets that
skipping to change at page 9, line 30 skipping to change at page 7, line 34
Options: Options:
Associated with each protocol or layer, or various values specific Associated with each protocol or layer, or various values specific
to the header of the protocol or layer. Options allow matching on to the header of the protocol or layer. Options allow matching on
those values. those values.
Each protocol type will have a specific set of attributes that can be Each protocol type will have a specific set of attributes that can be
used to specify a classifier for that protocol. These attributes used to specify a classifier for that protocol. These attributes
will be grouped under a grouped AVP called a Classifier AVP. will be grouped under a grouped AVP called a Classifier AVP.
5.1. Classifier AVP 4.1.1. Classifier AVP
The Classifier AVP (AVP Code TBD) is a grouped AVP that consists of a The Classifier AVP (AVP Code TBD) is a grouped AVP that consists of a
set of attributes that specify how to match a packet. set of attributes that specify how to match a packet.
Classifier ::= < AVP Header: XXX > Classifier ::= < AVP Header: XXX >
{ Classifier-ID } { Classifier-ID }
{ Protocol } { Protocol }
{ Direction } { Direction }
* [ From-Spec ] * [ From-Spec ]
* [ To-Spec ] * [ To-Spec ]
* [ Diffserv-Code-Point ] * [ Diffserv-Code-Point ]
[ Fragmentation-Flag ] [ Fragmentation-Flag ]
* [ IP-Option ] * [ IP-Option ]
* [ TCP-Option ] * [ TCP-Option ]
[ TCP-Flags ] [ TCP-Flags ]
* [ ICMP-Type ] * [ ICMP-Type ]
* [ ETH-Option ] * [ ETH-Option ]
* [ AVP ] * [ AVP ]
5.2. Classifier-ID AVP 4.1.2. Classifier-ID AVP
The Classifier-ID AVP (AVP Code TBD) is of type OctetString and The Classifier-ID AVP (AVP Code TBD) is of type OctetString and
uniquely identifies the classifier. Each application will define the uniquely identifies the classifier. Each application will define the
uniqueness scope of this identifier, e.g. unique per terminal or uniqueness scope of this identifier, e.g. unique per terminal or
globally unique. Exactly one Classifier-ID AVP MUST be contained globally unique. Exactly one Classifier-ID AVP MUST be contained
within a Classifier AVP. within a Classifier AVP.
5.3. Protocol AVP 4.1.3. Protocol AVP
The Protocol AVP (AVP Code TBD) is of type Enumerated and specifies The Protocol AVP (AVP Code TBD) is of type Enumerated and specifies
the protocol being matched. The attributes included in the the protocol being matched. The attributes included in the
Classifier AVP must be consistent with the value of the Protocol AVP. Classifier AVP must be consistent with the value of the Protocol AVP.
Exactly one Protocol AVP MUST be contained within a Classifier AVP. Exactly one Protocol AVP MUST be contained within a Classifier AVP.
The values for this AVP are managed by IANA under the Protocol The values for this AVP are managed by IANA under the Protocol
Numbers registry [PROTOCOL]. Numbers registry [PROTOCOL].
5.4. Direction AVP 4.1.4. Direction AVP
The Direction AVP (AVP Code TBD) is of type Enumerated that specifies The Direction AVP (AVP Code TBD) is of type Enumerated that specifies
in which direction to apply the Classifier. The values of the in which direction to apply the Classifier. The values of the
enumeration are: "IN","OUT","BOTH". In the "IN" and "BOTH" enumeration are: "IN","OUT","BOTH". In the "IN" and "BOTH"
directions, the From-Spec refers to the address of the Managed directions, the From-Spec refers to the address of the Managed
Terminal and the To-Spec refers to the unmanaged terminal. In the Terminal and the To-Spec refers to the unmanaged terminal. In the
"OUT" direction, the From-Spec refers to the Unmanaged Terminal "OUT" direction, the From-Spec refers to the Unmanaged Terminal
whereas the To-Spec refers to the Managed Terminal. whereas the To-Spec refers to the Managed Terminal.
Value | Name and Semantic Value | Name and Semantic
------+-------------------------------------------------- ------+--------------------------------------------------
0 | RESERVED 0 | RESERVED
1 | IN - The classifier applies to flows from the 1 | IN - The classifier applies to flows from the
| Managed Terminal. | Managed Terminal.
2 | OUT - The classifier applies to flows to the 2 | OUT - The classifier applies to flows to the
| Managed Terminal. | Managed Terminal.
3 | BOTH - The classifier applies to flows both to 3 | BOTH - The classifier applies to flows both to
| and from the Managed Terminal. | and from the Managed Terminal.
5.5. From-Spec AVP 4.1.5. From-Spec AVP
The From-Spec AVP (AVP Code TBD) is a grouped AVP that specifies the The From-Spec AVP (AVP Code TBD) is a grouped AVP that specifies the
Source Specification used to match the packet. Zero or more of these Source Specification used to match the packet. Zero or more of these
AVPs may appear in the Classifier. If this AVP is absent from the AVPs may appear in the Classifier. If this AVP is absent from the
Classifier then all packets are matched regardless of the source Classifier then all packets are matched regardless of the source
address. If more than one instance of this AVP appears in the address. If more than one instance of this AVP appears in the
Classifier then the source of the packet can match any From-Spec AVP. Classifier then the source of the packet can match any From-Spec AVP.
The contents of this AVP are protocol specific. The contents of this AVP are protocol specific.
If more than one instance of the IP address AVPs (IP-Address, IP- If more than one instance of the IP address AVPs (IP-Address, IP-
skipping to change at page 11, line 37 skipping to change at page 10, line 19
* [ MAC-Address ] * [ MAC-Address ]
* [ MAC-Address-Mask] * [ MAC-Address-Mask]
* [ EUI64-Address ] * [ EUI64-Address ]
* [ EUI64-Address-Mask] * [ EUI64-Address-Mask]
* [ Port ] * [ Port ]
* [ Port-Range ] * [ Port-Range ]
[ Negated ] [ Negated ]
[ Use-Assigned-Address ] [ Use-Assigned-Address ]
* [ AVP ] * [ AVP ]
5.6. To-Spec AVP 4.1.6. To-Spec AVP
The To-Spec AVP (AVP Code TBD) is a grouped AVP that specifies the The To-Spec AVP (AVP Code TBD) is a grouped AVP that specifies the
Destination Specification used to match the packet. Zero or more of Destination Specification used to match the packet. Zero or more of
these AVPs may appear in the Classifier. If this AVP is absent from these AVPs may appear in the Classifier. If this AVP is absent from
the Classifier then all packets are matched regardless of the the Classifier then all packets are matched regardless of the
destination address. If more than one instance of this AVP appears destination address. If more than one instance of this AVP appears
in the Classifier then the destination of the packet can match any in the Classifier then the destination of the packet can match any
To-Spec AVP. The contents of this AVP are protocol specific. To-Spec AVP. The contents of this AVP are protocol specific.
If more than one instance of the IP address AVPs (IP-Address, IP- If more than one instance of the IP address AVPs (IP-Address, IP-
skipping to change at page 12, line 33 skipping to change at page 11, line 19
* [ MAC-Address ] * [ MAC-Address ]
* [ MAC-Address-Mask] * [ MAC-Address-Mask]
* [ EUI64-Address ] * [ EUI64-Address ]
* [ EUI64-Address-Mask] * [ EUI64-Address-Mask]
* [ Port ] * [ Port ]
* [ Port-Range ] * [ Port-Range ]
[ Negated ] [ Negated ]
[ Use-Assigned-Address ] [ Use-Assigned-Address ]
* [ AVP ] * [ AVP ]
5.7. Source and Destination AVPs 4.1.7. Source and Destination AVPs
For packet classification the contents of the From-Spec and To-Spec For packet classification the contents of the From-Spec and To-Spec
can contain the following AVPs. can contain the following AVPs.
By combining several of these AVPs within a From-Spec or To-Spec AVP By combining several of these AVPs within a From-Spec or To-Spec AVP
and using more than one From-Spec or To-Spec AVP in the Classifier and using more than one From-Spec or To-Spec AVP in the Classifier
AVP, one can express many different types of address pools. AVP, one can express many different types of address pools.
5.7.1. Negated AVP 4.1.7.1. Negated AVP
The Negated AVP (AVP Code TBD) of type Enumerated containing the The Negated AVP (AVP Code TBD) of type Enumerated containing the
values of True or False. Exactly zero or one of these AVPs may values of True or False. Exactly zero or one of these AVPs may
appear in the From-Spec or To-Spec AVP. When set to True the meaning appear in the From-Spec or To-Spec AVP. When set to True the meaning
of the match in the To-Spec and From-Spec are negated, causing all of the match in the To-Spec and From-Spec are negated, causing all
other addresses to be matched instead. other addresses to be matched instead.
When set to False, or when the AVP is not included in the From-Spec When set to False, 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 or To-Spec AVP then the meaning of the match is not inverted, causing
only the addresses specified to be matched. only the addresses specified to be matched.
Note that the negation does not impact the port comparisons. Note that the negation does not impact the port comparisons.
Value | Name Value | Name
------+-------- ------+--------
0 | False 0 | False
1 | True 1 | True
5.7.2. IP-Address AVP 4.1.7.2. IP-Address AVP
The IP-Address AVP (AVP Code TBD) is of type Address and specifies a The IP-Address AVP (AVP Code TBD) is of type Address and specifies a
single IP address (IPv4 or IPv6) address to match. single IP address (IPv4 or IPv6) address to match.
5.7.3. IP-Address-Range AVP 4.1.7.3. IP-Address-Range AVP
The IP-Address-Range AVP (AVP Code TBD) is of type Grouped and The IP-Address-Range AVP (AVP Code TBD) is of type Grouped and
specifies an inclusive IP address range. specifies an inclusive IP address range.
IP-Address-Range ::= < AVP Header: XXX > IP-Address-Range ::= < AVP Header: XXX >
[ IP-Address-Start ] [ IP-Address-Start ]
[ IP-Address-End ] [ IP-Address-End ]
* [ AVP ] * [ AVP ]
If the IP-Address-Start AVP is not included then the address range If the IP-Address-Start AVP is not included then the address range
skipping to change at page 13, line 40 skipping to change at page 12, line 27
specified IP-Address-End address. specified IP-Address-End address.
If the IP-Address-End AVP is not included then the address range 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 starts at the address specified by the IP-Address-Start AVP and
includes all the remaining valid IP addresses. includes all the remaining valid IP addresses.
For the IP-Address-Range AVP to be valid, the IP-Address-Start AVP 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 MUST contain a value that is less than that of the IP-Address-End
AVP. AVP.
5.7.4. IP-Address-Start AVP 4.1.7.4. IP-Address-Start AVP
The IP-Address-Start AVP (AVP Code TBD) is of type Address and 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 specifies the first IP address (IPv4 or IPv6) address of an IP
address range. address range.
5.7.5. IP-Address-End AVP 4.1.7.5. IP-Address-End AVP
The IP-Address-End AVP (AVP Code TBD) is of type Address and 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 specifies the last IP address (IPv4 or IPv6) address of an address
range. range.
5.7.6. IP-Address-Mask AVP 4.1.7.6. IP-Address-Mask AVP
The IP-Address-Mask AVP (AVP Code TBD) is of type Grouped and The IP-Address-Mask AVP (AVP Code TBD) is of type Grouped and
specifies an IP address range using a base IP address and the bit- specifies an IP address range using a base IP address and the bit-
width of the mask. For example, a range expressed as 1.2.3.0/24 will width of the mask. 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. match all IP addresses from 1.2.3.0 up to and including 1.2.3.255.
The bit-width MUST be valid for the type of IP address. The bit-width MUST be valid for the type of IP address.
IP-Address-Mask ::= < AVP Header: XXX > IP-Address-Mask ::= < AVP Header: XXX >
{ IP-Address } { IP-Address }
{ IP-Bit-Mask-Width } { IP-Bit-Mask-Width }
* [ AVP ] * [ AVP ]
5.7.7. IP-Mask-Bit-Mask-Width AVP 4.1.7.7. IP-Mask-Bit-Mask-Width AVP
The IP-Bit-Mask-Width AVP (AVP Code TBD) is of type OctetString. The The IP-Bit-Mask-Width AVP (AVP Code TBD) is of type OctetString. The
value is a single octet and specifies the width of an IP address bit- value is a single octet and specifies the width of an IP address bit-
mask. mask.
5.7.8. MAC-Address AVP 4.1.7.8. MAC-Address AVP
The MAC-Address AVP (AVP Code TBD) is of type OctetString and 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 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 the frame 6 octets encoding of the address as it would appear in the frame
header. header.
5.7.9. MAC-Address-Mask AVP 4.1.7.9. MAC-Address-Mask AVP
The MAC-Address-Mask AVP (AVP Code TBD) is of type Grouped and The MAC-Address-Mask AVP (AVP Code TBD) is of type Grouped and
specifies a set of MAC addresses using a bit mask to indicate the specifies a set of MAC addresses using a bit mask to indicate the
bits of the MAC addresses which must fit to the specified MAC address bits of the MAC addresses which must fit to the specified MAC address
attribute. For example, a MAC-Address-Mask with the MAC-Address as 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-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 00-00 will match all MAC addresses from 00-10-A4-23-00-00 up to and
including 00-10-A4-23-FF-FF. including 00-10-A4-23-FF-FF.
MAC-Address-Mask ::= < AVP Header: XXX > MAC-Address-Mask ::= < AVP Header: XXX >
{ MAC-Address } { MAC-Address }
{ MAC-Address-Mask-Pattern } { MAC-Address-Mask-Pattern }
* [ AVP ] * [ AVP ]
5.7.10. MAC-Address-Mask-Pattern AVP 4.1.7.10. MAC-Address-Mask-Pattern AVP
The MAC-Address-Mask-Pattern AVP (AVP Code TBD) is of type The MAC-Address-Mask-Pattern AVP (AVP Code TBD) is of type
OctetString. The value is a 6 octets specifying the bit positions of OctetString. The value is a 6 octets specifying the bit positions of
a MAC address, that are taken for matching. a MAC address, that are taken for matching.
5.7.11. EUI64-Address AVP 4.1.7.11. EUI64-Address AVP
The EUI64-Address AVP (AVP Code TBD) is of type OctetString and 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 specifies a single layer 2 address in EUI-64 format. The value is a
8 octets encoding of the address as it would appear in the frame 8 octets encoding of the address as it would appear in the frame
header. header.
5.7.12. EUI64-Address-Mask AVP 4.1.7.12. EUI64-Address-Mask AVP
The EUI64-Address-Mask AVP (AVP Code TBD) is of type Grouped and The EUI64-Address-Mask AVP (AVP Code TBD) is of type Grouped and
specifies a set of EUI64 addresses using a bit mask to indicate the specifies a set of EUI64 addresses using a bit mask to indicate the
bits of the EUI64 addresses which must fit to the specified EUI64 bits of the EUI64 addresses which must fit to the specified EUI64
address attribute. For example, a EUI64-Address-Mask with the 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- 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 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- from 00-10-A4-FF-FE-23-00-00 up to and including 00-10-A4-FF-FE-23-
FF-FF. FF-FF.
EUI64-Address-Mask ::= < AVP Header: XXX > EUI64-Address-Mask ::= < AVP Header: XXX >
{ EUI64-Address } { EUI64-Address }
{ EUI64-Address-Mask-Pattern } { EUI64-Address-Mask-Pattern }
* [ AVP ] * [ AVP ]
5.7.13. EUI64-Address-Mask-Pattern AVP 4.1.7.13. EUI64-Address-Mask-Pattern AVP
The EUI64-Address-Mask-Pattern AVP (AVP Code TBD) is of type The EUI64-Address-Mask-Pattern AVP (AVP Code TBD) is of type
OctetString. The value is a 8 octets specifying the bit positions of OctetString. The value is a 8 octets specifying the bit positions of
a EUI64 address, that are taken for matching. a EUI64 address, that are taken for matching.
5.7.14. Port AVP 4.1.7.14. Port AVP
The Port AVP (AVP Code TBD) is of type Integer32 in the range of 0 to The Port AVP (AVP Code TBD) is of type Integer32 in the range of 0 to
65535 and specifies the TCP or UDP port number to match. 65535 and specifies the TCP or UDP port number to match.
5.7.15. Port-Range AVP 4.1.7.15. Port-Range AVP
The Port-Range AVP (AVP Code TBD) is of type Grouped and specifies an The Port-Range AVP (AVP Code TBD) is of type Grouped and specifies an
inclusive range of ports. inclusive range of ports.
Port-Range ::= < AVP Header: XXX > Port-Range ::= < AVP Header: XXX >
[ Port-Start ] [ Port-Start ]
[ Port-End ] [ Port-End ]
* [ AVP ] * [ AVP ]
If the Port-Start AVP is omitted then port 0 is assumed. If the If the Port-Start AVP is omitted then port 0 is assumed. If the
Port-End AVP is omitted then port 65535 is assumed. Port-End AVP is omitted then port 65535 is assumed.
5.7.16. Port-Start AVP 4.1.7.16. Port-Start AVP
The Port-Start AVP (AVP Code TBD) is of type Integer32 and specifies The Port-Start AVP (AVP Code TBD) is of type Integer32 and specifies
the first port number of an IP port range. the first port number of an IP port range.
5.7.17. Port-End AVP 4.1.7.17. Port-End AVP
The Port-End AVP (AVP Code TBD) is of type Integer32 and specifies The Port-End AVP (AVP Code TBD) is of type Integer32 and specifies
the last port number of an IP port range. the last port number of an IP port range.
5.7.18. Use-Assigned-Address AVP 4.1.7.18. Use-Assigned-Address AVP
In some scenarios, the AAA does not know the IP address assigned to In 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 the Managed Terminal at the time that the Classifier is sent to the
Classifying Entity. The Use-Assigned-Address AVP (AVP Code TBD) is Classifying Entity. The Use-Assigned-Address AVP (AVP Code TBD) is
of type Enumerated containing the values of True or False. When of type Enumerated containing the values of True or False. When
present and set to True, it represents the IP address assigned to the present and set to True, it represents the IP address assigned to the
Managed Terminal. Managed Terminal.
Value | Name Value | Name
------+-------- ------+--------
0 | False 0 | False
1 | True 1 | True
5.8. Header Option AVPs 4.1.8. Header Option AVPs
The Classifier AVP may contain one or more of the following AVPs to The Classifier AVP may contain one or more of the following AVPs to
match on the various possible IP, TCP or ICMP header options. match on the various possible IP, TCP or ICMP header options.
5.8.1. Diffserv-Code-Point AVP 4.1.8.1. Diffserv-Code-Point AVP
The Diffserv-Code-Point AVP (AVP Code TBD) is of type Enumerated and The Diffserv-Code-Point AVP (AVP Code TBD) is of type Enumerated and
specifies the Differentiated Services Field Codepoints to match in specifies the Differentiated Services Field Codepoints to match in
the IP header. The values are managed by IANA under the the IP header. The values are managed by IANA under the
Differentiated Services Field Codepoints registry [DSCP]. Differentiated Services Field Codepoints registry [DSCP].
5.8.2. Fragmentation-Flag AVP 4.1.8.2. Fragmentation-Flag AVP
The Fragmentation-Flag AVP (AVP Code TBD) is of type Enumerated and The Fragmentation-Flag AVP (AVP Code TBD) is of type Enumerated and
specifies the packet fragmentation flags to match in the IP header. specifies the packet fragmentation flags to match in the IP header.
Value | Name and Semantic Value | Name and Semantic
------+------------------------------------------------------------ ------+------------------------------------------------------------
0 | RESERVED 0 | RESERVED
1 | Don't Fragment (DF) 1 | Don't Fragment (DF)
2 | More Fragments (MF) 2 | More Fragments (MF)
5.8.3. IP-Option AVP 4.1.8.3. IP-Option AVP
The IP-Option AVP (AVP Code TBD) is of type Grouped and specifies an The IP-Option AVP (AVP Code TBD) is of type Grouped and specifies an
IP header option that must be matched. IP header option that must be matched.
IP-Option ::= < AVP Header: XXX > IP-Option ::= < AVP Header: XXX >
{ IP-Option-Type } { IP-Option-Type }
* [ IP-Option-Value ] * [ IP-Option-Value ]
[ Negated ] [ Negated ]
* [ AVP ] * [ AVP ]
If one or more IP-Option-Value AVPs are present, one of the values If one or more IP-Option-Value AVPs are present, one of the values
MUST match the value in the IP header option. If the IP-Option-Value MUST match the value in the IP header option. If the IP-Option-Value
AVP is absent, the option type MUST be present in the IP header but AVP is absent, the option type MUST be present in the IP header but
the value is wild carded. the value is wild carded.
The Negated AVP is used in conjunction with the IP-Option-Value AVPs The Negated AVP is used in conjunction with the IP-Option-Value AVPs
to specify IP header options which do not match specific values. The to specify IP header options which do not match specific values. The
Negated AVP is used without the IP-Option-Value AVP to specify IP Negated AVP is used without the IP-Option-Value AVP to specify IP
headers which do not contain the option type. headers which do not contain the option type.
5.8.4. IP-Option-Type AVP 4.1.8.4. IP-Option-Type AVP
The IP-Option-Type AVP (AVP Code TBD) is of type Enumerated and the The IP-Option-Type AVP (AVP Code TBD) is of type Enumerated and the
values are managed by IANA under the IP Option Numbers registry values are managed by IANA under the IP Option Numbers registry
[IPOPTIONS]. [IPOPTIONS].
5.8.5. IP-Option-Value AVP 4.1.8.5. IP-Option-Value AVP
The IP-Option-Value AVP (AVP Code TBD) is of type OctetString and The IP-Option-Value AVP (AVP Code TBD) is of type OctetString and
contains the option value that must be matched. contains the option value that must be matched.
5.8.6. TCP-Option AVP 4.1.8.6. TCP-Option AVP
The TCP-Option AVP (AVP Code TBD) is of type Grouped and specifies a The TCP-Option AVP (AVP Code TBD) is of type Grouped and specifies a
TCP header option that must be matched. TCP header option that must be matched.
TCP-Option ::= < AVP Header: XXX > TCP-Option ::= < AVP Header: XXX >
{ TCP-Option-Type } { TCP-Option-Type }
* [ TCP-Option-Value ] * [ TCP-Option-Value ]
[ Negated ] [ Negated ]
* [ AVP ] * [ AVP ]
If one or more TCP-Option-Value AVPs are present, one of the values If one or more TCP-Option-Value AVPs are present, one of the values
MUST match the value in the TCP header option. If the TCP-Option- MUST match the value in the TCP header option. If the TCP-Option-
Value AVP is absent, the option type MUST be present in the TCP Value AVP is absent, the option type MUST be present in the TCP
header but the value is wild carded. header but the value is wild carded.
The Negated AVP is used in conjunction which the TCP-Option-Value The Negated AVP is used in conjunction which the TCP-Option-Value
AVPs to specify TCP header options which do not match specific AVPs to specify TCP header options which do not match specific
values. The Negated AVP is used without the TCP-Option-Value AVP to values. The Negated AVP is used without the TCP-Option-Value AVP to
specify TCP headers which do not contain the option type. specify TCP headers which do not contain the option type.
5.8.7. TCP-Option-Type AVP 4.1.8.7. TCP-Option-Type AVP
The TCP-Option-Type AVP (AVP Code TBD) is of type Enumerated and the The TCP-Option-Type AVP (AVP Code TBD) is of type Enumerated and the
values are managed by IANA under the TCP Option Numbers registry values are managed by IANA under the TCP Option Numbers registry
[TCPOPTIONS]. [TCPOPTIONS].
5.8.8. TCP-Option-Value AVP 4.1.8.8. TCP-Option-Value AVP
The TCP-Option-Value AVP (AVP Code TBD) is of type OctetString and The TCP-Option-Value AVP (AVP Code TBD) is of type OctetString and
contains the option value that must be matched. contains the option value that must be matched.
5.8.9. TCP-Flags AVP 4.1.8.9. TCP-Flags AVP
The TCP-Flags AVP (AVP Code TBD) is of type Grouped and specifies a The TCP-Flags AVP (AVP Code TBD) is of type Grouped and specifies a
set of TCP control flags that must be matched. set of TCP control flags that must be matched.
TCP-Flags ::= < AVP Header: XXX > TCP-Flags ::= < AVP Header: XXX >
1* { TCP-Flag-Type } 1* { TCP-Flag-Type }
[ Negated ] [ Negated ]
* [ AVP ] * [ AVP ]
If the Negated AVP is not present, the TCP-Flag-Type AVPs specifies If the Negated AVP is not present, the TCP-Flag-Type AVPs specifies
which flags MUST be set. If the Negated AVP is present, the TCP- which flags MUST be set. If the Negated AVP is present, the TCP-
Flag-Type AVPs specifies which flags MUST be cleared. Flag-Type AVPs specifies which flags MUST be cleared.
5.8.10. TCP-Flag-Type AVP 4.1.8.10. TCP-Flag-Type AVP
The TCP-Flag-Type AVP (AVP Code TBD) is of type Enumerated and The TCP-Flag-Type AVP (AVP Code TBD) is of type Enumerated and
specifies a TCP control flag type that must be matched. specifies a TCP control flag type that must be matched.
Value | Name and Semantic Value | Name and Semantic
------+------------------------------------------------------------ ------+------------------------------------------------------------
0 | RESERVED 0 | RESERVED
1 | CWR - Congestion Window Reduced. 1 | CWR - Congestion Window Reduced.
2 | ECE - ECN-Echo. TCP peer is ECN capable. 2 | ECE - ECN-Echo. TCP peer is ECN capable.
3 | URG - URGent pointer field is significant. 3 | URG - URGent pointer field is significant.
4 | ACK - ACKnowledgment field is significant. 4 | ACK - ACKnowledgment field is significant.
5 | PSH - Push function. 5 | PSH - Push function.
6 | RST - Reset the connection. 6 | RST - Reset the connection.
7 | SYN - Synchronize sequence numbers. 7 | SYN - Synchronize sequence numbers.
8 | FIN - No more data from sender. 8 | FIN - No more data from sender.
5.8.11. ICMP-Type 4.1.8.11. ICMP-Type
The ICMP-Type AVP (AVP Code TBD) is of type Grouped and specifies a The ICMP-Type AVP (AVP Code TBD) is of type Grouped and specifies a
ICMP message type that must be matched. ICMP message type that must be matched.
ICMP-Type ::= < AVP Header: XXX > ICMP-Type ::= < AVP Header: XXX >
{ ICMP-Type-Number } { ICMP-Type-Number }
* [ ICMP-Code ] * [ ICMP-Code ]
[ Negated ] [ Negated ]
* [ AVP ] * [ AVP ]
If the ICMP-Code AVP is present, the value MUST match that in the If 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 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. present in the ICMP header but the code is wild carded.
The Negated AVP is used in conjunction which the ICMP-Code AVPs to The Negated AVP is used in conjunction which the ICMP-Code AVPs to
specify ICMP codes which do not match specific values. The Negated specify ICMP codes which do not match specific values. The Negated
AVP is used without the ICMP-Code AVP to specify ICMP headers which AVP is used without the ICMP-Code AVP to specify ICMP headers which
do not contain the ICMP type. do not contain the ICMP type.
5.8.12. ICMP-Type-Number AVP 4.1.8.12. ICMP-Type-Number AVP
The ICMP-Type-Number AVP (AVP Code TBD) is of type Enumerated and the The ICMP-Type-Number AVP (AVP Code TBD) is of type Enumerated and the
values are managed by IANA under the ICMP Type Numbers registry values are managed by IANA under the ICMP Type Numbers registry
[ICMPTYPE]. [ICMPTYPE].
5.8.13. ICMP-Code AVP 4.1.8.13. ICMP-Code AVP
The ICMP-Code AVP (AVP Code TBD) is of type Enumerated and the values The ICMP-Code AVP (AVP Code TBD) is of type Enumerated and the values
are managed by IANA under the ICMP Type Numbers registry [ICMPTYPE]. are managed by IANA under the ICMP Type Numbers registry [ICMPTYPE].
5.8.14. ETH-Option AVP 4.1.8.14. ETH-Option AVP
The ETH-Option AVP (AVP Code TBD) is of type Grouped and specifies The ETH-Option AVP (AVP Code TBD) is of type Grouped and specifies
Ethernet specific attributes. Ethernet specific attributes.
ETH-Option ::= < AVP Header: XXX > ETH-Option ::= < AVP Header: XXX >
{ ETH-Proto-Type } { ETH-Proto-Type }
* [ VLAN-ID-Range ] * [ VLAN-ID-Range ]
* [ ETH-Priority-Range ] * [ ETH-Priority-Range ]
* [ AVP ] * [ AVP ]
5.8.15. ETH-Proto-Type AVP 4.1.8.15. ETH-Proto-Type AVP
The Eth-Proto-Type AVP (AVP Code TBD) is of type Grouped and The Eth-Proto-Type AVP (AVP Code TBD) is of type Grouped and
specifies the encapsulated protocol type. ETH-Ether-Type and ETH-SAP specifies the encapsulated protocol type. ETH-Ether-Type and ETH-SAP
are mutually exclusive. are mutually exclusive.
ETH-Proto-Type ::= < AVP Header: XXX > ETH-Proto-Type ::= < AVP Header: XXX >
* [ ETH-Ether-Type ] * [ ETH-Ether-Type ]
* [ ETH-SAP ] * [ ETH-SAP ]
* [ AVP ] * [ AVP ]
5.8.16. ETH-Ether-Type AVP 4.1.8.16. ETH-Ether-Type AVP
The ETH-Ether-Type AVP (AVP Code TBD) is of type OctetString. The 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 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 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 or if SNAP is present at 802.2 but the ETH-SAP AVP MUST NOT be
present in this case. present in this case.
5.8.17. ETH-SAP AVP 4.1.8.17. ETH-SAP AVP
The ETH-SAP AVP (AVP Code TBD) is of type OctetString. The value is 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 a double octet representing the 802.2 SAP as specified in
[IEEE802.2]. The first octet contains the DSAP and the second the [IEEE802.2]. The first octet contains the DSAP and the second the
SSAP. SSAP.
5.8.18. VLAN-ID-Range AVP 4.1.8.18. VLAN-ID-Range AVP
The VLAN-ID-Range AVP (AVP Code TBD) is of type Grouped and specifies The VLAN-ID-Range AVP (AVP Code TBD) is of type Grouped and specifies
the VLAN range to match. VLAN identities are either specified by a the VLAN range to match. VLAN identities are either specified by a
single VLAN-ID according to [IEEE802.1Q] or by a combination of single VLAN-ID according to [IEEE802.1Q] or by a combination of
Customer and Service VLAN-IDs according to [IEEE802.1ad]. Customer and Service VLAN-IDs according to [IEEE802.1ad].
The single VLAN-ID is represented by the C-VID-Start and C-VID-End The single VLAN-ID is represented by the C-VID-Start and C-VID-End
AVPs and the S-VID-Start and S-VID-End AVPs SHALL be ommitted in this AVPs and the S-VID-Start and S-VID-End AVPs SHALL be ommitted in this
case. If the VLAN-ID-Range AVP is omitted from the Classifier, then case. If the VLAN-ID-Range AVP is omitted from the Classifier, then
comparison of the VLAN identity of the packet is irrelevant. comparison of the VLAN identity of the packet is irrelevant.
skipping to change at page 21, line 39 skipping to change at page 20, line 19
Start and C-VID-End AVPs are present, the value of the IEEE 802.1ad Start and C-VID-End AVPs are present, the value of the IEEE 802.1ad
C-VID bits or the IEEE 802.1Q VLAN-ID bits MUST be greater than or 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 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 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 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 is irrelevant. bits or IEEE 802.1Q VLAN-ID bits for this Classifier is irrelevant.
If the C-VID-Start and C-VID-End AVPs are specified, then Ethernet If the C-VID-Start and C-VID-End AVPs are specified, then Ethernet
packets without IEEE 802.1ad or IEEE 802.1Q encapsulation MUST NOT packets without IEEE 802.1ad or IEEE 802.1Q encapsulation MUST NOT
match this Classifier. match this Classifier.
5.8.19. S-VID-Start AVP 4.1.8.19. S-VID-Start AVP
The S-VID-Start AVP (AVP Code TBD) is of type Unsigned32. The value The S-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 MUST be in the range from 0 to 4095. The value of this AVP specifies
the start value of the range of S-VID VLAN-IDs to be matched. the start value of the range of S-VID VLAN-IDs to be matched.
5.8.20. S-VID-End AVP 4.1.8.20. S-VID-End AVP
The S-VID-End AVP (AVP Code TBD) is of type Unsigned32. The value The S-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 MUST be in the range from 0 to 4095. The value of this AVP specifies
the end value of the range of S-VID VLAN-IDs to be matched. the end value of the range of S-VID VLAN-IDs to be matched.
5.8.21. C-VID-Start AVP 4.1.8.21. C-VID-Start AVP
The C-VID-Start AVP (AVP Code TBD) is of type Unsigned32. The value 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 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. the start value of the range of C-VID VLAN-IDs to be matched.
5.8.22. C-VID-End AVP 4.1.8.22. C-VID-End AVP
The C-VID-End AVP (AVP Code TBD) is of type Unsigned32. The value 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 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. the end value of the range of C-VID VLAN-IDs to be matched.
5.8.23. ETH-Priority-Range AVP 4.1.8.23. ETH-Priority-Range AVP
The ETH-Priority-Range AVP (AVP Code TBD) is of type Grouped and The ETH-Priority-Range AVP (AVP Code TBD) is of type Grouped and
specifies an inclusive range to match the user_priority parameter specifies an inclusive range to match the user_priority parameter
specified in [IEEE802.1D]. An Ethernet packet containing the specified in [IEEE802.1D]. An Ethernet packet containing the
user_priority parameter matches this Classifier if the value is user_priority parameter matches this Classifier if the value is
greater than or equal to ETH-Low-Priority and less than or equal to 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 ETH-High-Priority. If this AVP is omitted, then comparison of the
IEEE 802.1D user_priority parameter for this Classifier is IEEE 802.1D user_priority parameter for this Classifier is
irrelevant. irrelevant.
ETH-Priority-Range ::= < AVP Header: XXX > ETH-Priority-Range ::= < AVP Header: XXX >
* [ ETH-Low-Priority ] * [ ETH-Low-Priority ]
* [ ETH-High-Priority ] * [ ETH-High-Priority ]
* [ AVP ] * [ AVP ]
5.8.24. ETH-Low-Priority AVP 4.1.8.24. ETH-Low-Priority AVP
The ETH-Low-Priority AVP (AVP Code TBD) is of type Unsigned32. The The ETH-Low-Priority AVP (AVP Code TBD) is of type Unsigned32. The
value MUST be in the range from 0 to 7. value MUST be in the range from 0 to 7.
5.8.25. ETH-High-Priority AVP 4.1.8.25. ETH-High-Priority AVP
The ETH-High-Priority AVP (AVP Code TBD) is of type Unsigned32. The The ETH-High-Priority AVP (AVP Code TBD) is of type Unsigned32. The
value MUST be in the range from 0 to 7. value MUST be in the range from 0 to 7.
6. Time Of Day AVPs 4.2. Time Of Day AVPs
In many QoS applications, the QoS specification applied to the In many QoS applications, the QoS specification applied to the
traffic flow is conditional upon the time of day when the flow was traffic flow is conditional upon the time of day when the flow was
observed. The following sections define AVPs that can be used to observed. The following sections define AVPs that can be used to
express one or more time windows which determine when a QoS express one or more time windows which determine when a QoS
specification is applicable to a traffic flow. specification is applicable to a traffic flow.
6.1. Time-Of-Day-Condition AVP 4.2.1. Time-Of-Day-Condition AVP
The Time-Of-Day-Condition AVP (AVP Code TBD) is of type Grouped and The Time-Of-Day-Condition AVP (AVP Code TBD) is of type Grouped and
specifies one or more time windows. specifies one or more time windows.
Time-Of-Day-Condition ::= < AVP Header: XXX > Time-Of-Day-Condition ::= < AVP Header: XXX >
[ Time-Of-Day-Start ] [ Time-Of-Day-Start ]
[ Time-Of-Day-End ] [ Time-Of-Day-End ]
[ Day-Of-Week-Mask ] [ Day-Of-Week-Mask ]
[ Day-Of-Month-Mask ] [ Day-Of-Month-Mask ]
[ Month-Of-Year-Mask ] [ Month-Of-Year-Mask ]
[ Absolute-Start-Time ] [ Absolute-Start-Time ]
[ Absolute-End-Time ] [ Absolute-End-Time ]
[ Timezone-Flag ] [ Timezone-Flag ]
* [ AVP ] * [ AVP ]
If more than one instance of this AVP is present in the Extended-QoS- If more than one instance of this AVP is present in the Rule AVP, the
Filter-Rule AVP, the current time at QoS rule evaluation MUST be current time at QoS rule evaluation MUST be within at least one of
within at least one of the time windows specified in one of the Time- the time windows specified in one of the Time-Of-Day-Condition AVPs.
Of-Day-Condition AVPs.
When the Time-Of-Day-Condition AVP and Classifier AVP are present in When the Time-Of-Day-Condition AVP and Classifier AVP are present in
the same Extended-QoS-Filter-Rule AVP, both the time of day and the same Rule AVP, both the time of day and packet classification
packet classification conditions MUST match for the QoS specification conditions MUST match for the QoS specification to be applied.
to be applied.
For example, a time window for 9am to 5pm (local time) from Monday to For example, a time window for 9am to 5pm (local time) from Monday to
Friday would be expressed as: Friday would be expressed as:
Time-Of-Day-Condition = { Time-Of-Day-Condition = {
Time-Of-Day-Start = 32400; Time-Of-Day-Start = 32400;
Time-Of-Day-End = 61200; Time-Of-Day-End = 61200;
Day-Of-Week-Mask = Day-Of-Week-Mask =
( MONDAY | TUESDAY | WEDNESDAY | THURSDAY | FRIDAY ); ( MONDAY | TUESDAY | WEDNESDAY | THURSDAY | FRIDAY );
Timezone-Flag = LOCAL; Timezone-Flag = LOCAL;
} }
6.2. Time-Of-Day-Start AVP 4.2.2. Time-Of-Day-Start AVP
The Time-Of-Day-Start AVP (AVP Code TBD) is of type Unsigned32. The The Time-Of-Day-Start AVP (AVP Code TBD) is of type Unsigned32. The
value MUST be in the range from 0 to 86400. The value of this AVP value MUST be in the range from 0 to 86400. The value of this AVP
specifies the start of an inclusive time window expressed as the specifies the start of an inclusive time window expressed as the
offset in seconds from midnight. If this AVP is absent from the offset in seconds from midnight. If this AVP is absent from the
Time-Of-Day-Condition AVP, the time window starts at midnight. Time-Of-Day-Condition AVP, the time window starts at midnight.
6.3. Time-Of-Day-End AVP 4.2.3. Time-Of-Day-End AVP
The Time-Of-Day-End AVP (AVP Code TBD) is of type Unsigned32. The The Time-Of-Day-End AVP (AVP Code TBD) is of type Unsigned32. The
value MUST be in the range from 1 to 86400. The value of this AVP value MUST be in the range from 1 to 86400. The value of this AVP
specifies the end of an inclusive time window expressed as the offset specifies the end of an inclusive time window expressed as the offset
in seconds from midnight. If this AVP is absent from the Time-Of- in seconds from midnight. If this AVP is absent from the Time-Of-
Day-Condition AVP, the time window ends one second before midnight. Day-Condition AVP, the time window ends one second before midnight.
6.4. Day-Of-Week-Mask AVP 4.2.4. Day-Of-Week-Mask AVP
The Day-Of-Week-Mask AVP (AVP Code TBD) is of type Unsigned32. The The Day-Of-Week-Mask AVP (AVP Code TBD) is of type Unsigned32. The
value is a bitmask which specifies the day of the week for the time value is a bitmask which specifies the day of the week for the time
window to match. This document specifies the following bits: window to match. This document specifies the following bits:
Bit | Name Bit | Name
------+------------ ------+------------
0 | SUNDAY 0 | SUNDAY
1 | MONDAY 1 | MONDAY
2 | TUESDAY 2 | TUESDAY
3 | WEDNESDAY 3 | WEDNESDAY
4 | THURSDAY 4 | THURSDAY
5 | FRIDAY 5 | FRIDAY
6 | SATURDAY 6 | SATURDAY
The bit MUST be set for the time window to match on the corresponding 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 day of the week. Bit 0 is the most significant bit and unused bits
MUST be cleared. If this AVP is absent from the Time-Of-Day- MUST be cleared. If this AVP is absent from the Time-Of-Day-
Condition AVP, the time windows match on all days of the week. Condition AVP, the time windows match on all days of the week.
6.5. Day-Of-Month-Mask AVP 4.2.5. Day-Of-Month-Mask AVP
The Day-Of-Week-Month AVP (AVP Code TBD) is of type Unsigned32. The The Day-Of-Week-Month AVP (AVP Code TBD) is of type Unsigned32. The
value MUST be in the range from 0 to 2147483647. The value is a value MUST be in the range from 0 to 2147483647. The value is a
bitmask which specifies the days of the month where bit 0 represents bitmask which specifies the days of the month where bit 0 represents
the first day of the month through to bit 30 which represents the 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 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 match on the corresponding day of the month. Bit 0 is the most
significant bit and unused bits MUST be cleared. If this AVP is significant bit and unused bits MUST be cleared. If this AVP is
absent from the Time-Of-Day-Condition AVP, the time windows match on absent from the Time-Of-Day-Condition AVP, the time windows match on
all days of the month. all days of the month.
6.6. Month-Of-Year-Mask AVP 4.2.6. Month-Of-Year-Mask AVP
The Month-Of-Year-Month AVP (AVP Code TBD) is of type Unsigned32. The Month-Of-Year-Month AVP (AVP Code TBD) is of type Unsigned32.
The value is a bitmask which specifies the months of the year for the The value is a bitmask which specifies the months of the year for the
time window to match. This document specifies the following bits: time window to match. This document specifies the following bits:
Bit | Name Bit | Name
------+----------- ------+-----------
0 | JANUARY 0 | JANUARY
1 | FEBRUARY 1 | FEBRUARY
2 | MARCH 2 | MARCH
skipping to change at page 25, line 25 skipping to change at page 23, line 43
8 | SEPTEMBER 8 | SEPTEMBER
9 | OCTOBER 9 | OCTOBER
10 | NOVEMBER 10 | NOVEMBER
11 | DECEMBER 11 | DECEMBER
The bit MUST be set for the time window to match on the corresponding The bit MUST be set for the time window to match on the corresponding
month of the year. Bit 0 is the most significant bit and unused bits month of the year. Bit 0 is the most significant bit and unused bits
MUST be cleared. If this AVP is absent from the Time-Of-Day- MUST be cleared. If this AVP is absent from the Time-Of-Day-
Condition AVP, the time windows match during all months of the year. Condition AVP, the time windows match during all months of the year.
6.7. Absolute-Start-Time AVP 4.2.7. Absolute-Start-Time AVP
The Absolute-Start-Time AVP (AVP Code TBD) is of type Time. The The Absolute-Start-Time AVP (AVP Code TBD) is of type Time. The
value of this AVP specifies the time in seconds since January 1, value of this AVP specifies the time in seconds since January 1,
1900, 00:00 UTC when the time window starts. If this AVP is absent 1900, 00:00 UTC when the time window starts. If this AVP is absent
from the Time-Of-Day-Condition AVP, the time window starts on January from the Time-Of-Day-Condition AVP, the time window starts on January
1, 1900, 00:00 UTC. 1, 1900, 00:00 UTC.
6.8. Absolute-End-Time AVP 4.2.8. Absolute-End-Time AVP
The Time-Of-Day-End AVP (AVP Code TBD) is of type Time. The value of The Time-Of-Day-End AVP (AVP Code TBD) is of type Time. The value of
this AVP specifies the time in seconds since January 1, 1900, 00:00 this AVP specifies the time in seconds since January 1, 1900, 00:00
UTC when the time window ends. If this AVP is absent from the Time- UTC when the time window ends. If this AVP is absent from the Time-
Of-Day-Condition AVP, the time window is open-ended. Of-Day-Condition AVP, the time window is open-ended.
6.9. Timezone-Flag AVP 4.2.9. Timezone-Flag AVP
The Timezone-Flag AVP (AVP Code TBD) is of type Enumerated and The Timezone-Flag AVP (AVP Code TBD) is of type Enumerated and
indicates whether the time windows are specified in UTC, local time indicates whether the time windows are specified in UTC, local time
at the managed terminal or as an offset from UTC. If this AVP is at the managed terminal or as an offset from UTC. If this AVP is
absent from the Time-Of-Day-Condition AVP, the time windows are in absent from the Time-Of-Day-Condition AVP, the time windows are in
UTC. UTC.
This document defines the following values: This document defines the following values:
Value | Name and Semantic Value | Name and Semantic
------+-------------------------------------------------- ------+--------------------------------------------------
0 | RESERVED 0 | RESERVED
1 | UTC - The time windows are expressed in UTC. 1 | UTC - The time windows are expressed in UTC.
2 | LOCAL - The time windows are expressed in local 2 | LOCAL - The time windows are expressed in local
| time at the Managed Terminal. | time at the Managed Terminal.
3 | OFFSET - The time windows are expressed as an 3 | OFFSET - The time windows are expressed as an
| offset from UTC (see Timezone-Offset AVP). | offset from UTC (see Timezone-Offset AVP).
6.10. Timezone-Offset AVP 4.2.10. Timezone-Offset AVP
The Timezone-Offset AVP (AVP Code TBD) is of type Integer32. The The Timezone-Offset AVP (AVP Code TBD) is of type Integer32. The
value of this AVP MUST be in the range from -43200 to 43200. It value of this AVP MUST be in the range from -43200 to 43200. It
specifies the offset in seconds from UTC that was used to express 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- 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 Mask and Month-Of-Year-Mask AVPs. This AVP MUST be present if the
Timezone-Flag AVP is set to OFFSET. 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
The 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: mark
drop:
All traffic that is met by the condition part of a rule MUST be
dropped.
shape:
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.
mark:
When the action is set to 'mark', it is expected that the QoS-
Parameters AVP carries information about the QoS class.
Further action values can be registered, as described in
Section 10.4.
5.2. Diameter QoS Defined AVPs
5.2.1. 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.2.2. 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.
QoS-Profile-Template ::= < AVP Header: XXX >
{ Vendor-Id }
{ QoS-Profile-Id }
* [ AVP ]
5.2.3. 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.
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
in the list above. 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 this specification
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.2.4. QoS-Parameters AVP
The QoS-Parameters AVP (AVP Code TBD) is of type grouped and contains
Quality of Service parameters. These parameters are defined in
separate documents and depend on the indicated QoS profile template
of the QoS-Profile-Template AVP. For an initial QoS parameter
specification see [I-D.ietf-dime-qos-parameters].
QoS-Parameters ::= < AVP Header: XXX >
* [ AVP ]
5.2.5. Rule-Precedence AVP
The Rule-Precedence AVP (AVP Code TBD) is of type Unsigned32 and
specifies the execution order of the rules expressed in the Rule-Set
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 Rule-Set AVP. The
lower the numerical value of Rule-Precedence AVP, the higher the rule
precedence.
5.2.6. Excess-Treatment AVP
The Excess-Treatment AVP (AVP Code TBD) is of type grouped and
indicates how out-of- profile traffic, that is, traffic not covered
by the original QoS-Profile-Template and QoS-Parameters AVPs. 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.
Excess-Treatment ::= < AVP Header: XXX >
{ Excess-Treatment-Action }
[ QoS-Profile-Template ]
[ QoS-Parameters ]
* [ AVP ]
5.2.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: remark
3: no metering or policing is permitted
drop:
When excess treatment action is set to 'drop', all marked traffic
MUST be dropped by a QoS aware node.
shape:
When excess treatment action is set to 'shape', it is expected
that the QoS-Parameters AVP carries QoS information to what QoS
parameter to re-shape the traffic. An example would be to use the
TMOD parameter defined in [I-D.ietf-dime-qos-parameters] and the
excess traffic is then to be shaped to this TMOD. When the
shaping causes unbounded queue growth at the shaper traffic can be
dropped.
remark:
When excess treatment action is set to 'remark', it is expected
that the QoS-Parameters AVP carries information about the QoS
class. For example, packets may be remarked to drop remarked to
pertain to a particular QoS class. In the latter case, remarking
relates to a DiffServ-type model, where packets arrive marked as
belonging to a certain QoS class, and when they are identified as
excess, they should then be remarked to a different QoS Class.
no metering or policing is permitted:
If 'no metering or policing is permitted' is signaled, the QoS
aware node should accept the excess treatment parameter set by the
sender with special care so that excess traffic should not cause a
problem. To request the Null Meter [RFC3290] is especially
strong, and should be used with caution.
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.
QoS-Capability ::= < AVP Header: XXX >
* [ QoS-Profile-Template ]
* [ AVP ]
The QoS-Profile-Template AVP is defined in Section 5.2.2.
7. Examples 7. Examples
This section shows a number of signaling flows where QoS negotiation This section shows a number of signaling flows where QoS negotiation
and authorization is part of the conventional NASREQ, EAP or Credit and authorization is part of the conventional NASREQ, EAP or Credit
Control applications message exchanges. The signalling flows for the Control applications message exchanges. The signalling flows for the
Diameter QoS Application are described in Diameter QoS Application are described in
[I-D.ietf-dime-diameter-qos]. [I-D.ietf-dime-diameter-qos].
7.1. Diameter EAP with QoS Information 7.1. Diameter EAP with QoS Information
Figure 2 shows a simple signaling flow where a NAS (Diameter Client) Figure 2 shows a simple signaling flow where a NAS (Diameter Client)
announces its QoS awareness and capabilities included into the DER announces its QoS awareness and capabilities included into the DER
message and as part of the access authentication procedure. Upon message and as part of the access authentication procedure. Upon
completion of the EAP exchange, the Diameter Server provides a pre- completion of the EAP exchange, the Diameter Server provides a pre-
provisioned QoS profile with the QoS-Semantics in the Extended-QoS- provisioned QoS profile with the QoS-Semantics in the Rule AVP set to
Filter-Rule AVP set to "QoS-Authorized", to the NAS in the final DEA "QoS-Authorized", to the NAS in the final DEA message.
message.
End Diameter Diameter End Diameter Diameter
Host Client Server Host Client Server
| | | | | |
| (initiate EAP) | | | (initiate EAP) | |
|<----------------------------->| | |<----------------------------->| |
| | Diameter-EAP-Request | | | Diameter-EAP-Request |
| | EAP-Payload(EAP Start) | | | EAP-Payload(EAP Start) |
| | QoS-Capability | | | QoS-Capability |
| |------------------------------->| | |------------------------------->|
skipping to change at page 27, line 36 skipping to change at page 31, line 36
|------------------------------>| | |------------------------------>| |
| | Diameter-EAP-Request | | | Diameter-EAP-Request |
| | EAP-Payload(EAP Response #N) | | | EAP-Payload(EAP Response #N) |
| |------------------------------->| | |------------------------------->|
| | | | | |
| | Diameter-EAP-Answer | | | Diameter-EAP-Answer |
| | Result-Code=DIAMETER_SUCCESS | | | Result-Code=DIAMETER_SUCCESS |
| | EAP-Payload(EAP Success) | | | EAP-Payload(EAP Success) |
| | [EAP-Master-Session-Key] | | | [EAP-Master-Session-Key] |
| | (authorization AVPs) | | | (authorization AVPs) |
| | QoS-Resources(QoS-Authorized) | | | Rule-Set(QoS-Authorized) |
| |<-------------------------------| | |<-------------------------------|
| | | | | |
| EAP Success | | | EAP Success | |
|<------------------------------| | |<------------------------------| |
| | | | | |
Figure 2: Example of a Diameter EAP enhanced with QoS Information Figure 2: Example of a Diameter EAP enhanced with QoS Information
7.2. Diameter NASREQ with QoS Information 7.2. Diameter NASREQ with QoS Information
skipping to change at page 28, line 38 skipping to change at page 32, line 38
| Response #N | | | Response #N | |
+----------------->| | +----------------->| |
| | | | | |
| |AA-Request | | |AA-Request |
| |NASREQ-Payload ( Response #N )| | |NASREQ-Payload ( Response #N )|
| +----------------------------->| | +----------------------------->|
| | | | | |
| | AA-Answer| | | AA-Answer|
| | Result-Code=DIAMETER_SUCCESS| | | Result-Code=DIAMETER_SUCCESS|
| | (authorization AVPs)| | | (authorization AVPs)|
| |QoS-Resources(QoS-Authorized) | | | Rule-Set(QoS-Authorized) |
| |<-----------------------------+ | |<-----------------------------+
| | | | | |
| Success | | | Success | |
|<-----------------+ | |<-----------------+ |
| | | | | |
Figure 3: Example of a Diameter NASREQ enhanced with QoS Information Figure 3: Example of a Diameter NASREQ enhanced with QoS Information
7.3. QoS Authorization 7.3. QoS Authorization
Figure 4 shows an example of authorization only QoS signaling as part Figure 4 shows an example of authorization only QoS signaling as part
of the NASREQ message exchange. The NAS provides the Diameter server of the NASREQ message exchange. The NAS provides the Diameter server
with the "QoS-Desired" QoS-Semantics AVP included in the QoS- with the "QoS-Desired" QoS-Semantics AVP included in the Rule-Set
Resources AVP. The Diameter server then either authorizes the AVP. The Diameter server then either authorizes the indicated QoS or
indicated QoS or rejects the request and informs the NAS about the rejects the request and informs the NAS about the result. In this
result. In this scenario the NAS does not need to include the QoS- scenario the NAS does not need to include the QoS-Capability AVP in
Capability AVP in the AAR message as the QoS-Resources AVP implicitly the AAR message as the Rule-Set AVP implicitly does the same and also
does the same and also the NAS is authorizing a specific QoS profile, the NAS is authorizing a specific QoS profile, not a pre-provisioned
not a pre-provisioned one. one.
End Diameter End Diameter
Host NAS Server Host NAS Server
| | | | | |
| | | | | |
| QoS Request | | | QoS Request | |
+----------------->| | +----------------->| |
| | | | | |
| |AA-Request | | |AA-Request |
| |Auth-Request-Type=AUTHORIZE_ONLY | |Auth-Request-Type=AUTHORIZE_ONLY
| |NASREQ-Payload | | |NASREQ-Payload |
| |QoS-Resources(QoS-Desired) | | |Rule-Set(QoS-Desired) |
| +----------------------------->| | +----------------------------->|
| | | | | |
| | AA-Answer| | | AA-Answer|
| | NASREQ-Payload(Success)| | | NASREQ-Payload(Success)|
| | QoS-Resources(QoS-Authorized)| | | Rule-Set(QoS-Authorized)|
| |<-----------------------------+ | |<-----------------------------+
| Accept | | | Accept | |
|<-----------------+ | |<-----------------+ |
| | | | | |
| | | | | |
| | | | | |
Figure 4: Example of an Authorization-Only Message Flow Figure 4: Example of an Authorization-Only Message Flow
7.4. Diameter Server Initiated Re-authorization of QoS 7.4. Diameter Server Initiated Re-authorization of QoS
skipping to change at page 30, line 24 skipping to change at page 34, line 24
| |<-----------------------------+ | |<-----------------------------+
| | | | | |
| |RA-Answer | | |RA-Answer |
| |Result-Code=DIAMETER_SUCCESS | | |Result-Code=DIAMETER_SUCCESS |
| +----------------------------->| | +----------------------------->|
| | | | | |
| | | | | |
| |AA-Request | | |AA-Request |
| |NASREQ-Payload | | |NASREQ-Payload |
| |Auth-Request-Type=AUTHORIZE_ONLY | |Auth-Request-Type=AUTHORIZE_ONLY
| |QoS-Resources(QoS-Desired) | | |Rule-Set(QoS-Desired) |
| +----------------------------->| | +----------------------------->|
| | | | | |
| | AA-Answer| | | AA-Answer|
| | Result-Code=DIAMETER_SUCCESS| | | Result-Code=DIAMETER_SUCCESS|
| | (authorization AVPs)| | | (authorization AVPs)|
| | QoS-Resources(QoS-Authorized)| | | Rule-Set(QoS-Authorized) |
| |<-----------------------------+ | |<-----------------------------+
| | | | | |
Figure 5: Example of a Server-initiated Re-Authorization Procedure Figure 5: Example of a Server-initiated Re-Authorization Procedure
7.5. Diameter Credit Control with QoS Information 7.5. Diameter Credit Control with QoS Information
In this case the User is charged as soon as the Service Element (CC 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 client) receives the service request. In this case the client uses
the "QoS-Desired" QoS-Semantics parameter in the QoS-Resources AVP the "QoS-Desired" QoS-Semantics parameter in the Rule-Set AVP that it
that it sends to the Accounitng server. The server responds with a sends to the Accounitng server. The server responds with a "QoS-
"QoS-Available" QoS-Semantics parameter in the QoS-Resources AVP Available" QoS-Semantics parameter in the Rule-Set AVP
Service Element Service Element
End User (CC Client) B CC Server End User (CC Client) B CC Server
| | | | | | | |
|(1) Service Request | | | |(1) Service Request | | |
|-------------------->| | | |-------------------->| | |
| |(2) CCR (event, DIRECT_DEBITING,| | |(2) CCR (event, DIRECT_DEBITING,|
| | QoS-Resources[QoS-desired]) | | | Rule-Set[QoS-desired]) |
| |-------------------------------->| | |-------------------------------->|
| |(3) CCA (Granted-Units, QoS- | | |(3) CCA (Granted-Units, QoS- |
| | Resources[QoS-Authorized]) | | | Resources[QoS-Authorized]) |
| |<--------------------------------| | |<--------------------------------|
|(4) Service Delivery | | | |(4) Service Delivery | | |
|<--------------------| | | |<--------------------| | |
|(5) Begin service | | | |(5) Begin service | | |
|<------------------------------------>| | |<------------------------------------>| |
| | | | | | | |
. . . . . . . .
skipping to change at page 32, line 43 skipping to change at page 36, line 43
Asveren, Mike Montemurro, Glen Zorn, Avri Doria, Dong Sun, Tina Tsou, Asveren, Mike Montemurro, Glen Zorn, Avri Doria, Dong Sun, Tina Tsou,
Pete McCann, Georgios Karagiannis, Elwyn Davies, Max Riegel and Yong Pete McCann, Georgios Karagiannis, Elwyn Davies, Max Riegel and Yong
Li for their comments. Li for their comments.
9. Contributors 9. Contributors
Max Riegel contributed the VLAN sections. Max Riegel contributed the VLAN sections.
10. IANA Considerations 10. IANA Considerations
10.1. AVP Codes
IANA is requested to allocate AVP codes for the following AVPs that IANA is requested to allocate AVP codes for the following AVPs that
are defined in this document. are defined in this document.
+------------------------------------------------------------------+ +--------------------------------------------------------------------+
| AVP Section | | AVP Section |
| Attribute Name Code Defined Data Type | | Attribute Name Code Defined Data Type |
+------------------------------------------------------------------+ +--------------------------------------------------------------------+
|QoS-Capability TBD 3.1 Grouped | |Rule-Set TBD 3.1 Grouped |
|QoS-Profile-Template TBD 3.2 Unsigned32 | |Rule TBD 3.2 Grouped |
|Vendor-Specific-QoS-Profile-Template TBD 3.3 Grouped | |Classifier TBD 4.1.1 Grouped |
|Extended-QoS-Filter-Rule TBD 3.5 Grouped | |Classifier-ID TBD 4.1.2 OctetString |
|QoS-Semantics TBD 3.6 Enumerated | |Protocol TBD 4.1.3 Enumerated |
|QoS-Parameters TBD 3.7 OctetString | |Direction TBD 4.1.4 Enumerated |
|QoS-Rule-Precedence TBD 3.8 Unsigned32 | |From-Spec TBD 4.1.5 Grouped |
|Classifier TBD 5.1 Grouped | |To-Spec TBD 4.1.6 Grouped |
|Classifier-ID TBD 5.2 OctetString | |Negated TBD 4.1.7.1 Enumerated |
|Protocol TBD 5.3 Enumerated | |IP-Address TBD 4.1.7.2 Address |
|Direction TBD 5.4 Enumerated | |IP-Address-Range TBD 4.1.7.3 Grouped |
|From-Spec TBD 5.5 Grouped | |IP-Address-Start TBD 4.1.7.4 Address |
|To-Spec TBD 5.6 Grouped | |IP-Address-End TBD 4.1.7.5 Address |
|Negated TBD 5.7.1 Enumerated | |IP-Address-Mask TBD 4.1.7.6 Grouped |
|IP-Address TBD 5.7.2 Address | |IP-Mask-Bit-Mask-Width TBD 4.1.7.7 OctetString |
|IP-Address-Range TBD 5.7.3 Grouped | |MAC-Address TBD 4.1.7.8 OctetString |
|IP-Address-Start TBD 5.7.4 Address | |MAC-Address-Mask TBD 4.1.7.9 Grouped |
|IP-Address-End TBD 5.7.5 Address | |MAC-Address-Mask-Pattern TBD 4.1.7.10 OctetString |
|IP-Address-Mask TBD 5.7.6 Grouped | |EUI64-Address TBD 4.1.7.11 OctetString |
|IP-Mask-Bit-Mask-Width TBD 5.7.7 OctetString | |EUI64-Address-Mask TBD 4.1.7.12 Grouped |
|MAC-Address TBD 5.7.8 OctetString | |EUI64-Address-Mask-Pattern TBD 4.1.7.13 OctetString |
|MAC-Address-Mask TBD 5.7.9 Grouped | |Port TBD 4.1.7.14 Integer32 |
|MAC-Address-Mask-Pattern TBD 5.7.10 OctetString | |Port-Range TBD 4.1.7.15 Grouped |
|EUI64-Address TBD 5.7.11 OctetString | |Port-Start TBD 4.1.7.16 Integer32 |
|EUI64-Address-Mask TBD 5.7.12 Grouped | |Port-End TBD 4.1.7.17 Integer32 |
|EUI64-Address-Mask-Pattern TBD 5.7.13 OctetString | |Use-Assigned-Address TBD 4.1.7.18 Enumerated |
|Port TBD 5.7.14 Integer32 | |Diffserv-Code-Point TBD 4.1.8.1 Enumerated |
|Port-Range TBD 5.7.15 Grouped | |Fragmentation-Flag TBD 4.1.8.2 Enumerated |
|Port-Start TBD 5.7.16 Integer32 | |IP-Option TBD 4.1.8.3 Grouped |
|Port-End TBD 5.7.17 Integer32 | |IP-Option-Type TBD 4.1.8.4 Enumerated |
|Use-Assigned-Address TBD 5.7.18 Enumerated | |IP-Option-Value TBD 4.1.8.5 OctetString |
|Diffserv-Code-Point TBD 5.8.1 Enumerated | |TCP-Option TBD 4.1.8.6 Grouped |
|Fragmentation-Flag TBD 5.8.2 Enumerated | |TCP-Option-Type TBD 4.1.8.7 Enumerated |
|IP-Option TBD 5.8.3 Grouped | |TCP-Option-Value TBD 4.1.8.8 OctetString |
|IP-Option-Type TBD 5.8.4 Enumerated | |TCP-Flags TBD 4.1.8.9 Grouped |
|IP-Option-Value TBD 5.8.5 OctetString | |TCP-Flag-Type TBD 4.1.8.10 Enumerated |
|TCP-Option TBD 5.8.6 Grouped | |ICMP-Type TBD 4.1.8.11 Grouped |
|TCP-Option-Type TBD 5.8.7 Enumerated | |ICMP-Type-Number TBD 4.1.8.12 Enumerated |
|TCP-Option-Value TBD 5.8.8 OctetString | |ICMP-Code TBD 4.1.8.13 Enumerated |
|TCP-Flags TBD 5.8.9 Grouped | |ETH-Option TBD 4.1.8.14 Grouped |
|TCP-Flag-Type TBD 5.8.10 Enumerated | |ETH-Proto-Type TBD 4.1.8.15 Grouped |
|ICMP-Type TBD 5.8.11 Grouped | |ETH-Ether-Type TBD 4.1.8.16 OctetString |
|ICMP-Type-Number TBD 5.8.12 Enumerated | |ETH-SAP TBD 4.1.8.17 OctetString |
|ICMP-Code TBD 5.8.13 Enumerated | |VLAN-ID-Range TBD 4.1.8.18 Grouped |
|ETH-Option TBD 5.8.14 Grouped | |S-VID-Start TBD 4.1.8.19 Unsigned32 |
|ETH-Proto-Type TBD 5.8.15 Grouped | |S-VID-End TBD 4.1.8.20 Unsigned32 |
|ETH-Ether-Type TBD 5.8.16 OctetString | |C-VID-Start TBD 4.1.8.21 Unsigned32 |
|ETH-SAP TBD 5.8.17 OctetString | |C-VID-End TBD 4.1.8.22 Unsigned32 |
|VLAN-ID-Range TBD 5.8.18 Grouped | |ETH-Priority-Range TBD 4.1.8.23 Grouped |
|S-VID-Start TBD 5.8.19 Unsigned32 | |ETH-Low-Priority TBD 4.1.8.24 Unsigned32 |
|S-VID-End TBD 5.8.20 Unsigned32 | |ETH-High-Priority TBD 4.1.8.25 Unsigned32 |
|C-VID-Start TBD 5.8.21 Unsigned32 | |Time-Of-Day-Condition TBD 4.2.1 Grouped |
|C-VID-End TBD 5.8.22 Unsigned32 | |Time-Of-Day-Start TBD 4.2.2 Grouped |
|ETH-Priority-Range TBD 5.8.23 Grouped | |Time-Of-Day-End TBD 4.2.3 Unsigned32 |
|ETH-Low-Priority TBD 5.8.24 Unsigned32 | |Day-Of-Week-Mask TBD 4.2.4 Unsigned32 |
|ETH-High-Priority TBD 5.8.25 Unsigned32 | |Day-Of-Month-Mask TBD 4.2.5 Unsigned32 |
|Time-Of-Day-Condition TBD 6.1 Grouped | |Month-Of-Year-Mask TBD 4.2.6 Unsigned32 |
|Time-Of-Day-Start TBD 6.2 Grouped | |Absolute-Start-Time TBD 4.2.7 Time |
|Time-Of-Day-End TBD 6.3 Unsigned32 | |Absolute-End-Time TBD 4.2.8 Time |
|Day-Of-Week-Mask TBD 6.4 Unsigned32 | |Timezone-Flag TBD 4.2.9 Enumerated |
|Day-Of-Month-Mask TBD 6.5 Unsigned32 | |Timezone-Offset TBD 4.2.10 Integer32 |
|Month-Of-Year-Mask TBD 6.6 Unsigned32 | |Action TBD 5.1 Grouped |
|Absolute-Start-Time TBD 6.7 Time | |QoS-Profile-Id TBD 5.2.1 Unsigned32 |
|Absolute-End-Time TBD 6.8 Time | |QoS-Profile-Template TBD 5.2.2 Grouped |
|Timezone-Flag TBD 6.9 Enumerated | |QoS-Semantics TBD 5.2.3 Enumerated |
|Timezone-Offset TBD 6.10 Integer32 | |QoS-Parameters TBD 5.2.4 OctetString |
+------------------------------------------------------------------+ |Rule-Precedence TBD 5.2.5 Unsigned32 |
|Excess-Treatment TBD 5.2.6 Grouped |
|Excess-Treatment-Action TBD 5.2.7 Unsigned32 |
|QoS-Capability TBD 6 Grouped |
+--------------------------------------------------------------------+
IANA is also requested to allocate a registry for the QoS-Semantics. 10.2. QoS-Semantics IANA Registry
The following values are allocated by this specification.
IANA is also requested to allocate a registry for the QoS-Semantics
AVP. The following values are allocated by this specification.
(0): QoS-Desired (0): QoS-Desired
(1): QoS-Available (1): QoS-Available
(2): QoS-Reserved (2): QoS-Reserved
(3): Minimum-QoS (3): Minimum-QoS
(4): QoS-Authorized (4): QoS-Authorized
A specification is required to add a new value to the registry. A A specification is required to add a new value to the registry.
standards track document is required to depreciate, delete, or modify
existing values. 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): remark
(3): no metering or policing is permitted
A specification is required to add a new value to the registry.
10.4. Action
IANA is also requested to allocate a registry for the 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.
11. Security Considerations 11. Security Considerations
This document describes the extension of Diameter for conveying This document describes the extension of Diameter for conveying
Quality of Service information. The security considerations of the Quality of Service information. The security considerations of the
Diameter protocol itself have been discussed in RFC 3588bis Diameter protocol itself have been discussed in RFC 3588 [RFC3588].
[I-D.ietf-dime-rfc3588bis]. Use of the AVPs defined in this document Use of the AVPs defined in this document MUST take into consideration
MUST take into consideration the security issues and requirements of the security issues and requirements of the Diameter Base protocol.
the Diameter Base protocol.
12. References 12. References
12.1. Normative References 12.1. Normative References
[DSCP] IANA, "Differentiated Services Field Codepoints", [DSCP] IANA, "Differentiated Services Field Codepoints",
http://www.iana.org/assignments/dscp-registry. 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-12
(work in progress), September 2008.
[ICMPTYPE] [ICMPTYPE]
IANA, "ICMP Type Numbers", IANA, "ICMP Type Numbers",
http://www.iana.org/assignments/icmp-parameters. http://www.iana.org/assignments/icmp-parameters.
[IEEE802.1D] [IEEE802.1D]
IEEE, "IEEE Standard for Local and metropolitan area IEEE, "IEEE Standard for Local and metropolitan area
networks, Media Access Control (MAC) Bridges", 2004. networks, Media Access Control (MAC) Bridges", 2004.
[IEEE802.1Q] [IEEE802.1Q]
IEEE, "IEEE Standard for Local and metropolitan area IEEE, "IEEE Standard for Local and metropolitan area
skipping to change at page 36, line 6 skipping to change at page 40, line 25
IANA, "IP Option Numbers", IANA, "IP Option Numbers",
http://www.iana.org/assignments/ip-parameters. http://www.iana.org/assignments/ip-parameters.
[PROTOCOL] [PROTOCOL]
IANA, "Protocol Types", IANA, "Protocol Types",
http://www.iana.org/assignments/protocol-numbers. http://www.iana.org/assignments/protocol-numbers.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. 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] [TCPOPTIONS]
IANA, "TCP Option Numbers", IANA, "TCP Option Numbers",
http://www.iana.org/assignments/tcp-parameters. http://www.iana.org/assignments/tcp-parameters.
12.2. Informative References 12.2. Informative References
[I-D.ietf-dime-diameter-qos] [I-D.ietf-dime-diameter-qos]
Sun, D., McCann, P., Tschofenig, H., Tsou, T., Doria, A., Sun, D., McCann, P., Tschofenig, H., Tsou, T., Doria, A.,
and G. Zorn, "Diameter Quality of Service Application", and G. Zorn, "Diameter Quality of Service Application",
draft-ietf-dime-diameter-qos-06 (work in progress), draft-ietf-dime-diameter-qos-06 (work in progress),
July 2008. July 2008.
[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-07 (work in progress),
November 2008.
[RFC3290] Bernet, Y., Blake, S., Grossman, D., and A. Smith, "An
Informal Management Model for Diffserv Routers", RFC 3290,
May 2002.
[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,
August 2005.
Authors' Addresses Authors' Addresses
Jouni Korhonen Jouni Korhonen
TeliaSonera Nokia Siemens Networks
Teollisuuskatu 13 Linnoitustie 6
Sonera FIN-00051 Espoo 02600
Finland Finland
Email: jouni.korhonen@teliasonera.com Email: jouni.korhonen@nsn.com
Hannes Tschofenig Hannes Tschofenig
Nokia Siemens Networks Nokia Siemens Networks
Linnoitustie 6 Linnoitustie 6
Espoo 02600 Espoo 02600
Finland Finland
Phone: +358 (50) 4871445 Phone: +358 (50) 4871445
Email: Hannes.Tschofenig@gmx.net Email: Hannes.Tschofenig@gmx.net
URI: http://www.tschofenig.priv.at URI: http://www.tschofenig.priv.at
skipping to change at page 37, line 4 skipping to change at page 41, line 30
Finland Finland
Phone: +358 (50) 4871445 Phone: +358 (50) 4871445
Email: Hannes.Tschofenig@gmx.net Email: Hannes.Tschofenig@gmx.net
URI: http://www.tschofenig.priv.at URI: http://www.tschofenig.priv.at
Mayutan Arumaithurai Mayutan Arumaithurai
University of Goettingen University of Goettingen
Email: mayutan.arumaithurai@gmail.com Email: mayutan.arumaithurai@gmail.com
Mark Jones (editor) Mark Jones (editor)
Bridgewater Systems Bridgewater Systems
303 Terry Fox Drive, Suite 500 303 Terry Fox Drive, Suite 500
Ottawa, Ontario K2K 3J1 Ottawa, Ontario K2K 3J1
Canada Canada
Phone: +1 613-591-6655 Phone: +1 613-591-6655
Email: mark.jones@bridgewatersystems.com Email: mark.jones@bridgewatersystems.com
Avi Lior Avi Lior
Bridgewater Systems Bridgewater Systems
303 Terry Fox Drive, Suite 500 303 Terry Fox Drive, Suite 500
Ottawa, Ontario K2K 3J1 Ottawa, Ontario K2K 3J1
Canada Canada
Phone: +1 613-591-6655 Phone: +1 613-591-6655
Email: avi@bridgewatersystems.com 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.
 End of changes. 119 change blocks. 
425 lines changed or deleted 564 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/