draft-ietf-dime-qos-attributes-12.txt   draft-ietf-dime-qos-attributes-13.txt 
Diameter Maintenance and J. Korhonen Diameter Maintenance and J. Korhonen
Extensions (DIME) H. Tschofenig Extensions (DIME) H. Tschofenig
Internet-Draft Nokia Siemens Networks Internet-Draft Nokia Siemens Networks
Intended status: Standards Track M. Arumaithurai Intended status: Standards Track M. Arumaithurai
Expires: December 7, 2009 University of Goettingen Expires: January 14, 2010 University of Goettingen
M. Jones, Ed. M. Jones, Ed.
A. Lior A. Lior
Bridgewater Systems Bridgewater Systems
June 5, 2009 July 13, 2009
Quality of Service Attributes for Diameter Quality of Service Attributes for Diameter
draft-ietf-dime-qos-attributes-12.txt draft-ietf-dime-qos-attributes-13.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79. This document may contain material
from IETF Documents or IETF Contributions published or made publicly from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from IETF Standards Process. Without obtaining an adequate license from
skipping to change at page 1, line 47 skipping to change at page 1, line 47
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 December 7, 2009. This Internet-Draft will expire on January 14, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. and restrictions with respect to this document.
skipping to change at page 3, line 12 skipping to change at page 3, line 12
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 . . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Rule Sets and Rules . . . . . . . . . . . . . . . . . . . . . 5 3. Rule Sets and Rules . . . . . . . . . . . . . . . . . . . . . 5
3.1. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 5 3.1. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 5
3.2. QoS-Rule AVP . . . . . . . . . . . . . . . . . . . . . . . 6 3.2. QoS-Rule AVP . . . . . . . . . . . . . . . . . . . . . . . 6
3.3. QoS-Rule-Precedence AVP . . . . . . . . . . . . . . . . . 6 3.3. QoS-Rule-Precedence AVP . . . . . . . . . . . . . . . . . 7
4. Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4. Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.1. Traffic Classifiers . . . . . . . . . . . . . . . . . . . 7 4.1. Traffic Classifiers . . . . . . . . . . . . . . . . . . . 7
4.1.1. Classifier AVP . . . . . . . . . . . . . . . . . . . . 9 4.1.1. Classifier AVP . . . . . . . . . . . . . . . . . . . . 9
4.1.2. Classifier-ID AVP . . . . . . . . . . . . . . . . . . 10 4.1.2. Classifier-ID AVP . . . . . . . . . . . . . . . . . . 10
4.1.3. Protocol AVP . . . . . . . . . . . . . . . . . . . . . 10 4.1.3. Protocol AVP . . . . . . . . . . . . . . . . . . . . . 10
4.1.4. Direction AVP . . . . . . . . . . . . . . . . . . . . 10 4.1.4. Direction AVP . . . . . . . . . . . . . . . . . . . . 10
4.1.5. From-Spec AVP . . . . . . . . . . . . . . . . . . . . 10 4.1.5. From-Spec AVP . . . . . . . . . . . . . . . . . . . . 10
4.1.6. To-Spec AVP . . . . . . . . . . . . . . . . . . . . . 11 4.1.6. To-Spec AVP . . . . . . . . . . . . . . . . . . . . . 11
4.1.7. Source and Destination AVPs . . . . . . . . . . . . . 12 4.1.7. Source and Destination AVPs . . . . . . . . . . . . . 12
4.1.8. Header Option AVPs . . . . . . . . . . . . . . . . . . 16 4.1.8. Header Option AVPs . . . . . . . . . . . . . . . . . . 16
4.2. Time Of Day AVPs . . . . . . . . . . . . . . . . . . . . . 23 4.2. Time Of Day AVPs . . . . . . . . . . . . . . . . . . . . . 23
4.2.1. Time-Of-Day-Condition AVP . . . . . . . . . . . . . . 23 4.2.1. Time-Of-Day-Condition AVP . . . . . . . . . . . . . . 23
4.2.2. Time-Of-Day-Start AVP . . . . . . . . . . . . . . . . 24 4.2.2. Time-Of-Day-Start AVP . . . . . . . . . . . . . . . . 23
4.2.3. Time-Of-Day-End AVP . . . . . . . . . . . . . . . . . 24 4.2.3. Time-Of-Day-End AVP . . . . . . . . . . . . . . . . . 24
4.2.4. Day-Of-Week-Mask AVP . . . . . . . . . . . . . . . . . 24 4.2.4. Day-Of-Week-Mask AVP . . . . . . . . . . . . . . . . . 24
4.2.5. Day-Of-Month-Mask AVP . . . . . . . . . . . . . . . . 25 4.2.5. Day-Of-Month-Mask AVP . . . . . . . . . . . . . . . . 24
4.2.6. Month-Of-Year-Mask AVP . . . . . . . . . . . . . . . . 25 4.2.6. Month-Of-Year-Mask AVP . . . . . . . . . . . . . . . . 24
4.2.7. Absolute-Start-Time AVP . . . . . . . . . . . . . . . 25 4.2.7. Absolute-Start-Time AVP . . . . . . . . . . . . . . . 25
4.2.8. Absolute-End-Time AVP . . . . . . . . . . . . . . . . 26 4.2.8. Absolute-Start-Fractional-Seconds AVP . . . . . . . . 25
4.2.9. Timezone-Flag AVP . . . . . . . . . . . . . . . . . . 26 4.2.9. Absolute-End-Time AVP . . . . . . . . . . . . . . . . 25
4.2.10. Timezone-Offset AVP . . . . . . . . . . . . . . . . . 26 4.2.10. Absolute-End-Fractional-Seconds AVP . . . . . . . . . 25
4.2.11. Timezone-Flag AVP . . . . . . . . . . . . . . . . . . 26
4.2.12. Timezone-Offset AVP . . . . . . . . . . . . . . . . . 26
5. Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 5. Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.1. QoS-Action AVP . . . . . . . . . . . . . . . . . . . . . . 26 5.1. QoS-Action AVP . . . . . . . . . . . . . . . . . . . . . . 26
5.2. QoS-Profile-Id AVP . . . . . . . . . . . . . . . . . . . . 27 5.2. QoS-Profile-Id AVP . . . . . . . . . . . . . . . . . . . . 27
5.3. QoS-Profile-Template AVP . . . . . . . . . . . . . . . . . 27 5.3. QoS-Profile-Template AVP . . . . . . . . . . . . . . . . . 27
5.4. QoS-Semantics . . . . . . . . . . . . . . . . . . . . . . 28 5.4. QoS-Semantics . . . . . . . . . . . . . . . . . . . . . . 28
5.5. QoS-Parameters AVP . . . . . . . . . . . . . . . . . . . . 29 5.5. QoS-Parameters AVP . . . . . . . . . . . . . . . . . . . . 29
5.6. Excess-Treatment AVP . . . . . . . . . . . . . . . . . . . 29 5.6. Excess-Treatment AVP . . . . . . . . . . . . . . . . . . . 29
6. QoS Capability Indication . . . . . . . . . . . . . . . . . . 30 6. QoS Capability Indication . . . . . . . . . . . . . . . . . . 30
7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
7.1. Diameter EAP with QoS Information . . . . . . . . . . . . 30 7.1. Diameter EAP with QoS Information . . . . . . . . . . . . 30
skipping to change at page 4, line 7 skipping to change at page 4, line 9
7.4. Diameter Server Initiated Re-authorization of QoS . . . . 33 7.4. Diameter Server Initiated Re-authorization of QoS . . . . 33
7.5. Diameter Credit Control with QoS Information . . . . . . . 34 7.5. Diameter Credit Control with QoS Information . . . . . . . 34
7.6. Classifier Examples . . . . . . . . . . . . . . . . . . . 35 7.6. Classifier Examples . . . . . . . . . . . . . . . . . . . 35
7.7. QoS Examples . . . . . . . . . . . . . . . . . . . . . . . 36 7.7. QoS Examples . . . . . . . . . . . . . . . . . . . . . . . 36
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 37 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 37
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 37 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 37
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37
11. Security Considerations . . . . . . . . . . . . . . . . . . . 39 11. Security Considerations . . . . . . . . . . . . . . . . . . . 39
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 40 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 40
12.1. Normative References . . . . . . . . . . . . . . . . . . . 40 12.1. Normative References . . . . . . . . . . . . . . . . . . . 40
12.2. Informative References . . . . . . . . . . . . . . . . . . 40 12.2. Informative References . . . . . . . . . . . . . . . . . . 41
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 41 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 41
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 ABNF of a command. The applications where permitted by the ABNF of a command. The
IPFilterRule AVP, defined in RFC 3588 [RFC3588], and the QoS-Filter- IPFilterRule AVP, defined in RFC 3588 [RFC3588], and the QoS-Filter-
Rule AVP, defined in RFC 4005 [RFC4005], provide basic support for Rule AVP, defined in RFC 4005 [RFC4005], provide basic support for
classification and QoS already. The classification rule syntax is a classification and QoS already. The classification rule syntax is a
modified subset of FreeBSD ipfw packet filter implementation. The modified subset of FreeBSD ipfw packet filter implementation. The
QoS functionality provided by the IPFilterRule AVP was updated by the QoS functionality provided by the IPFilterRule AVP was updated by the
QoS-Filter-Rule AVP. The QoS-Rule AVP offers an extended way of QoS-Filter-Rule AVP. The QoS-Rule AVP offers an extended way of
expressing classification and QoS capabilities. expressing classification and QoS capabilities.
The QoS-Resources AVP represents a complete rule set with each rule The QoS-Resources AVP represents a complete rule set with each rule
represented by a QoS-Rule AVP. Each rule consists of a conditions represented by a QoS-Rule AVP. Each rule consists of a conditions
part and the corresponding actions to be performed if the conditions part and the corresponding actions to be performed if the conditions
are satisfied. The AVPs responsible for expressing a condition are are satisfied. The AVPs responsible for expressing a condition are
defined in Section 4. Capabilities to match all or a subset of the defined in Section 4. The capability to match all or a subset of the
data traffic is provided. Additionally, time-based conditions can be data traffic is provided and this includes the ability to match on
Ethernet specific attributes which was not possible with the QoS-
Filter-Rule AVP. Additionally, time-based conditions can be
expressed based on the functionality offered in Section 4.2. The expressed based on the functionality offered in Section 4.2. The
action part of a rule contains information for handling conflict action part of a rule contains information for handling conflict
resolution, such as a priority value for each individual rule within resolution, such as a priority value for each individual rule within
a rule set, and further description regarding QoS related actions. a rule set, and further description regarding QoS related actions.
The QoS policy rules are defined as Diameter encoded Attribute Value
Pairs (AVPs) described using a modified version of the Augmented
Backus-Naur Form (ABNF), see [RFC3588]. The AVP datatypes are also
taken from [RFC3588].
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. Rule Sets and Rules 3. Rule Sets and Rules
As mentioned in the introduction the top-level element is the QoS- As mentioned in the introduction the top-level element is the QoS-
Resources AVP that encapsulates one or more QoS-Rule AVPs. Resources AVP that encapsulates one or more QoS-Rule AVPs.
3.1. QoS-Resources AVP 3.1. QoS-Resources AVP
The QoS-Resources AVP (AVP Code TBD) is of type Grouped and describes The QoS-Resources AVP (AVP Code TBD) is of type Grouped and contains
a list of policies. a list of QoS policy rules.
QoS-Resources ::= < AVP Header: XXX > QoS-Resources ::= < AVP Header: XXX >
1*{ QoS-Rule } 1*{ QoS-Rule }
* [ AVP ] * [ AVP ]
3.2. QoS-Rule AVP 3.2. QoS-Rule AVP
The QoS-Rule AVP (AVP Code TBD) is of type Grouped and defines a The QoS-Rule AVP (AVP Code TBD) is of type Grouped and defines a
specific condition and action combination. specific condition and action combination.
skipping to change at page 15, line 37 skipping to change at page 15, line 37
4.1.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.
4.1.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 port numbers to match. 65535 and specifies port numbers to match. The type of port is
indicated by the value of the Protocol AVP, i.e. if Procotol AVP
value is 6 (TCP) then the Port AVP represents a TCP port.
4.1.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. The type of the ports is indicated by the
value of the Protocol AVP, i.e. if Procotol AVP value is 6 (TCP) then
the Port-Range AVP represents an inclusive range of TCP 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.
4.1.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.
4.1.7.17. Port-End AVP 4.1.7.17. Port-End AVP
skipping to change at page 18, line 28 skipping to change at page 18, line 33
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.
4.1.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 } { TCP-Flag-Type }
[ Negated ] [ Negated ]
* [ AVP ] * [ AVP ]
If the Negated AVP is not present or present but set to False, the If the Negated AVP is not present or present but set to False, the
TCP-Flag-Type AVPs specifies which flags MUST be set. If the Negated TCP-Flag-Type AVP specifies which flags MUST be set. If the Negated
AVP is set to True, the TCP-Flag-Type AVPs specifies which flags MUST AVP is set to True, the TCP-Flag-Type AVP specifies which flags MUST
be cleared. be cleared.
4.1.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 Unsigned32 and
specifies a TCP control flag type that must be matched. specifies the TCP control flag types that must be matched. The first
16 bits match the TCP header format defined in [RFC3168] and the
Value | Name and Semantic subsequent 16 bits are unused. Within the first 16 bits, bits 0 to 3
------+------------------------------------------- are unused and bits 4 to 15 are managed by IANA under the TCP Header
0 | CWR - Congestion Window Reduced. Flag registry as defined in [RFC3168].
1 | ECE - ECN-Echo. TCP peer is ECN capable.
2 | URG - URGent pointer field is significant.
3 | ACK - ACKnowledgment field is significant.
4 | PSH - Push function.
5 | RST - Reset the connection.
6 | SYN - Synchronize sequence numbers.
7 | FIN - No more data from sender.
4.1.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 ]
skipping to change at page 25, line 7 skipping to change at page 24, line 36
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.
4.2.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-Month AVP (AVP Code TBD) is of type Unsigned32. The value
value MUST be in the range from 0 to 2147483647. The value is a MUST be in the range from 0 to 2147483647. The value is a bitmask
bitmask which specifies the days of the month where bit 0 represents which specifies the days of the month where bit 0 represents the
the first day of the month through to bit 30 which represents the first day of the month through to bit 30 which represents the last
last day of the month. The bit MUST be set for the time window to day of the month. The bit MUST be set for the time window to match
match on the corresponding day of the month. Bit 0 is the most on the corresponding day of the month. Bit 0 is the most significant
significant bit and unused bits MUST be cleared. If this AVP is bit and unused bits MUST be cleared. If this AVP is absent from the
absent from the Time-Of-Day-Condition AVP, the time windows match on Time-Of-Day-Condition AVP, the time windows match on all days of the
all days of the month. month.
4.2.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-Mask AVP (AVP Code TBD) is of type Unsigned32. The
The value is a bitmask which specifies the months of the year for 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
3 | APRIL 3 | APRIL
4 | MAY 4 | MAY
5 | JUNE 5 | JUNE
skipping to change at page 26, line 5 skipping to change at page 25, line 33
Condition AVP, the time windows match during all months of the year. Condition AVP, the time windows match during all months of the year.
4.2.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.
4.2.8. Absolute-End-Time AVP 4.2.8. Absolute-Start-Fractional-Seconds AVP
The Absolute-Start-Fractional-Seconds AVP (AVP Code TBD) is of type
Unsigned32. The value specifies the fractional seconds that are
added to Absolute-Start-Time value in order to deterimine when the
time window starts. If this AVP is absent from the Time-Of-Day-
Condition AVP then the fractional seconds are assumed to be zero.
4.2.9. 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.
4.2.9. Timezone-Flag AVP 4.2.10. Absolute-End-Fractional-Seconds AVP
The Absolute-End-Fractional-Seconds AVP (AVP Code TBD) is of type
Unsigned32. The value specifies the fractional seconds that are
added to Absolute-End-Time value in order to deterimine when the time
window ends. If this AVP is absent from the Time-Of-Day-Condition
AVP then the fractional seconds are assumed to be zero.
4.2.11. 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 | UTC - The time windows are expressed in UTC. 0 | UTC - The time windows are expressed in UTC.
1 | LOCAL - The time windows are expressed in local 1 | LOCAL - The time windows are expressed in local
| time at the Managed Terminal. | time at the Managed Terminal.
2 | OFFSET - The time windows are expressed as an 2 | OFFSET - The time windows are expressed as an
| offset from UTC (see Timezone-Offset AVP). | offset from UTC (see Timezone-Offset AVP).
4.2.10. Timezone-Offset AVP 4.2.12. 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 5. Actions
This section illustrates the actions associated with a rule. This This section defines the actions associated with a rule. This
document only defines QoS specific actions but further actions can be document only defines QoS specific actions but further actions can be
specified as extensions. specified as extensions.
5.1. QoS-Action AVP 5.1. QoS-Action AVP
The QoS-Action AVP (AVP Code TBD) is of type Enumerated and lists the The QoS-Action AVP (AVP Code TBD) is of type Enumerated and lists the
actions that are associated with the condition part of a rule. The actions that are associated with the condition part of a rule. The
following actions are defined in this document: following actions are defined in this document:
0: drop 0: drop
skipping to change at page 37, line 28 skipping to change at page 37, line 28
document shepherd. document shepherd.
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 10.1. AVP Codes
IANA is requested to allocate AVP codes for the following AVPs that IANA is requested to allocate codes from the "AVP Codes" registry
are defined in this document. under Authentication, Authorization, and Accounting (AAA) Parameters
for the following AVPs that are defined in this document.
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| AVP Section | | AVP Section |
| Attribute Name Code Defined Data Type | | Attribute Name Code Defined Data Type |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
|QoS-Resources TBD 3.1 Grouped | |QoS-Resources TBD 3.1 Grouped |
|QoS-Rule TBD 3.2 Grouped | |QoS-Rule TBD 3.2 Grouped |
|QoS-Rule-Precedence TBD 3.3 Unsigned32 | |QoS-Rule-Precedence TBD 3.3 Unsigned32 |
|Classifier TBD 4.1.1 Grouped | |Classifier TBD 4.1.1 Grouped |
|Classifier-ID TBD 4.1.2 OctetString | |Classifier-ID TBD 4.1.2 OctetString |
skipping to change at page 38, line 27 skipping to change at page 38, line 28
|Use-Assigned-Address TBD 4.1.7.18 Enumerated | |Use-Assigned-Address TBD 4.1.7.18 Enumerated |
|Diffserv-Code-Point TBD 4.1.8.1 Enumerated | |Diffserv-Code-Point TBD 4.1.8.1 Enumerated |
|Fragmentation-Flag TBD 4.1.8.2 Enumerated | |Fragmentation-Flag TBD 4.1.8.2 Enumerated |
|IP-Option TBD 4.1.8.3 Grouped | |IP-Option TBD 4.1.8.3 Grouped |
|IP-Option-Type TBD 4.1.8.4 Enumerated | |IP-Option-Type TBD 4.1.8.4 Enumerated |
|IP-Option-Value TBD 4.1.8.5 OctetString | |IP-Option-Value TBD 4.1.8.5 OctetString |
|TCP-Option TBD 4.1.8.6 Grouped | |TCP-Option TBD 4.1.8.6 Grouped |
|TCP-Option-Type TBD 4.1.8.7 Enumerated | |TCP-Option-Type TBD 4.1.8.7 Enumerated |
|TCP-Option-Value TBD 4.1.8.8 OctetString | |TCP-Option-Value TBD 4.1.8.8 OctetString |
|TCP-Flags TBD 4.1.8.9 Grouped | |TCP-Flags TBD 4.1.8.9 Grouped |
|TCP-Flag-Type TBD 4.1.8.10 Enumerated | |TCP-Flag-Type TBD 4.1.8.10 Unsigned32 |
|ICMP-Type TBD 4.1.8.11 Grouped | |ICMP-Type TBD 4.1.8.11 Grouped |
|ICMP-Type-Number TBD 4.1.8.12 Enumerated | |ICMP-Type-Number TBD 4.1.8.12 Enumerated |
|ICMP-Code TBD 4.1.8.13 Enumerated | |ICMP-Code TBD 4.1.8.13 Enumerated |
|ETH-Option TBD 4.1.8.14 Grouped | |ETH-Option TBD 4.1.8.14 Grouped |
|ETH-Proto-Type TBD 4.1.8.15 Grouped | |ETH-Proto-Type TBD 4.1.8.15 Grouped |
|ETH-Ether-Type TBD 4.1.8.16 OctetString | |ETH-Ether-Type TBD 4.1.8.16 OctetString |
|ETH-SAP TBD 4.1.8.17 OctetString | |ETH-SAP TBD 4.1.8.17 OctetString |
|VLAN-ID-Range TBD 4.1.8.18 Grouped | |VLAN-ID-Range TBD 4.1.8.18 Grouped |
|S-VID-Start TBD 4.1.8.19 Unsigned32 | |S-VID-Start TBD 4.1.8.19 Unsigned32 |
|S-VID-End TBD 4.1.8.20 Unsigned32 | |S-VID-End TBD 4.1.8.20 Unsigned32 |
skipping to change at page 38, line 50 skipping to change at page 38, line 51
|User-Priority-Range TBD 4.1.8.23 Grouped | |User-Priority-Range TBD 4.1.8.23 Grouped |
|Low-User-Priority TBD 4.1.8.24 Unsigned32 | |Low-User-Priority TBD 4.1.8.24 Unsigned32 |
|High-User-Priority TBD 4.1.8.25 Unsigned32 | |High-User-Priority TBD 4.1.8.25 Unsigned32 |
|Time-Of-Day-Condition TBD 4.2.1 Grouped | |Time-Of-Day-Condition TBD 4.2.1 Grouped |
|Time-Of-Day-Start TBD 4.2.2 Unsigned32 | |Time-Of-Day-Start TBD 4.2.2 Unsigned32 |
|Time-Of-Day-End TBD 4.2.3 Unsigned32 | |Time-Of-Day-End TBD 4.2.3 Unsigned32 |
|Day-Of-Week-Mask TBD 4.2.4 Unsigned32 | |Day-Of-Week-Mask TBD 4.2.4 Unsigned32 |
|Day-Of-Month-Mask TBD 4.2.5 Unsigned32 | |Day-Of-Month-Mask TBD 4.2.5 Unsigned32 |
|Month-Of-Year-Mask TBD 4.2.6 Unsigned32 | |Month-Of-Year-Mask TBD 4.2.6 Unsigned32 |
|Absolute-Start-Time TBD 4.2.7 Time | |Absolute-Start-Time TBD 4.2.7 Time |
|Absolute-End-Time TBD 4.2.8 Time | |Absolute-Start-Fractional-Seconds TBD 4.2.8 Unsigned32 |
|Timezone-Flag TBD 4.2.9 Enumerated | |Absolute-End-Time TBD 4.2.9 Time |
|Timezone-Offset TBD 4.2.10 Integer32 | |Absolute-End-Fractional-Seconds TBD 4.2.10 Unsigned32 |
|Timezone-Flag TBD 4.2.11 Enumerated |
|Timezone-Offset TBD 4.2.12 Integer32 |
|QoS-Action TBD 5.1 Grouped | |QoS-Action TBD 5.1 Grouped |
|QoS-Profile-Id TBD 5.2 Unsigned32 | |QoS-Profile-Id TBD 5.2 Unsigned32 |
|QoS-Profile-Template TBD 5.3 Grouped | |QoS-Profile-Template TBD 5.3 Grouped |
|QoS-Semantics TBD 5.4 Enumerated | |QoS-Semantics TBD 5.4 Enumerated |
|QoS-Parameters TBD 5.5 Grouped | |QoS-Parameters TBD 5.5 Grouped |
|Excess-Treatment TBD 5.6 Grouped | |Excess-Treatment TBD 5.6 Grouped |
|QoS-Capability TBD 6 Grouped | |QoS-Capability TBD 6 Grouped |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
10.2. QoS-Semantics IANA Registry 10.2. QoS-Semantics IANA Registry
IANA is also requested to allocate a registry for the QoS-Semantics IANA is also requested to allocate a new registry under
AVP. The following values are allocated by this specification. Authentication, Authorization, and Accounting (AAA) Parameters 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
The definition of new values is subject to the Specification Required The definition of new values is subject to the Specification Required
policy [RFC5226]. policy [RFC5226].
10.3. Action 10.3. Action
IANA is also requested to allocate a registry for the QoS-Action AVP. IANA is also requested to allocate a new registry under
The following values are allocated by this specification: Authentication, Authorization, and Accounting (AAA) Parameters for
the QoS-Action AVP. The following values are allocated by this
specification:
0: drop 0: drop
1: shape 1: shape
2: mark 2: mark
The definition of new values is subject to the Specification Required The definition of new values is subject to the Specification Required
policy [RFC5226]. policy [RFC5226].
11. Security Considerations 11. Security Considerations
skipping to change at page 40, line 38 skipping to change at page 40, line 44
[RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, [RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black,
"Definition of the Differentiated Services Field (DS "Definition of the Differentiated Services Field (DS
Field) in the IPv4 and IPv6 Headers", RFC 2474, Field) in the IPv4 and IPv6 Headers", RFC 2474,
December 1998. December 1998.
[RFC2780] Bradner, S. and V. Paxson, "IANA Allocation Guidelines For [RFC2780] Bradner, S. and V. Paxson, "IANA Allocation Guidelines For
Values In the Internet Protocol and Related Headers", Values In the Internet Protocol and Related Headers",
BCP 37, RFC 2780, March 2000. BCP 37, RFC 2780, March 2000.
[RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition
of Explicit Congestion Notification (ECN) to IP",
RFC 3168, September 2001.
[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
Arkko, "Diameter Base Protocol", RFC 3588, September 2003.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
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-08 (work in progress), draft-ietf-dime-diameter-qos-09 (work in progress),
May 2009. July 2009.
[I-D.ietf-dime-qos-parameters] [I-D.ietf-dime-qos-parameters]
Korhonen, J., Tschofenig, H., and E. Davies, "Quality of Korhonen, J., Tschofenig, H., and E. Davies, "Quality of
Service Parameters for Usage with Diameter", Service Parameters for Usage with Diameter",
draft-ietf-dime-qos-parameters-11 (work in progress), draft-ietf-dime-qos-parameters-11 (work in progress),
May 2009. May 2009.
[RFC2475] Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z., [RFC2475] Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z.,
and W. Weiss, "An Architecture for Differentiated and W. Weiss, "An Architecture for Differentiated
Services", RFC 2475, December 1998. Services", RFC 2475, December 1998.
[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
Arkko, "Diameter Base Protocol", RFC 3588, September 2003.
[RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, [RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton,
"Diameter Network Access Server Application", RFC 4005, "Diameter Network Access Server Application", RFC 4005,
August 2005. August 2005.
Authors' Addresses Authors' Addresses
Jouni Korhonen Jouni Korhonen
Nokia Siemens Networks Nokia Siemens Networks
Linnoitustie 6 Linnoitustie 6
Espoo 02600 Espoo 02600
 End of changes. 32 change blocks. 
65 lines changed or deleted 97 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/