draft-ietf-dime-qos-attributes-11.txt   draft-ietf-dime-qos-attributes-12.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: August 27, 2009 University of Goettingen Expires: December 7, 2009 University of Goettingen
M. Jones, Ed. M. Jones, Ed.
A. Lior A. Lior
Bridgewater Systems Bridgewater Systems
February 23, 2009 June 5, 2009
Quality of Service Attributes for Diameter Quality of Service Attributes for Diameter
draft-ietf-dime-qos-attributes-11.txt draft-ietf-dime-qos-attributes-12.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. provisions of BCP 78 and BCP 79. This document may contain material
from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
Internet-Drafts are working documents of the Internet Engineering 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 August 27, 2009. This Internet-Draft will expire on December 7, 2009.
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 Provisions Relating to IETF Documents in effect on the date of
(http://trustee.ietf.org/license-info) in effect on the date of publication of this document (http://trustee.ietf.org/license-info).
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document.
to this document.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
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 . . . . . . . . . . . . . . . . . . . . . . . . . 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. Rule AVP . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.2. QoS-Rule AVP . . . . . . . . . . . . . . . . . . . . . . . 6
3.3. Rule-Precedence AVP . . . . . . . . . . . . . . . . . . . 6 3.3. QoS-Rule-Precedence AVP . . . . . . . . . . . . . . . . . 6
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
skipping to change at page 3, line 35 skipping to change at page 3, line 35
4.2.2. Time-Of-Day-Start AVP . . . . . . . . . . . . . . . . 24 4.2.2. Time-Of-Day-Start AVP . . . . . . . . . . . . . . . . 24
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 . . . . . . . . . . . . . . . . 25
4.2.6. Month-Of-Year-Mask AVP . . . . . . . . . . . . . . . . 25 4.2.6. Month-Of-Year-Mask AVP . . . . . . . . . . . . . . . . 25
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-End-Time AVP . . . . . . . . . . . . . . . . 26
4.2.9. Timezone-Flag AVP . . . . . . . . . . . . . . . . . . 26 4.2.9. Timezone-Flag AVP . . . . . . . . . . . . . . . . . . 26
4.2.10. Timezone-Offset AVP . . . . . . . . . . . . . . . . . 26 4.2.10. Timezone-Offset AVP . . . . . . . . . . . . . . . . . 26
5. Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 5. Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.1. 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 . . . . . . . . . . . . . . . . . 28 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
5.7. Excess-Treatment-Action . . . . . . . . . . . . . . . . . 30 6. QoS Capability Indication . . . . . . . . . . . . . . . . . . 30
6. QoS Capability Indication . . . . . . . . . . . . . . . . . . 31 7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 7.1. Diameter EAP with QoS Information . . . . . . . . . . . . 30
7.1. Diameter EAP with QoS Information . . . . . . . . . . . . 31 7.2. Diameter NASREQ with QoS Information . . . . . . . . . . . 31
7.2. Diameter NASREQ with QoS Information . . . . . . . . . . . 32 7.3. QoS Authorization . . . . . . . . . . . . . . . . . . . . 32
7.3. QoS Authorization . . . . . . . . . . . . . . . . . . . . 33 7.4. Diameter Server Initiated Re-authorization of QoS . . . . 33
7.4. Diameter Server Initiated Re-authorization of QoS . . . . 34 7.5. Diameter Credit Control with QoS Information . . . . . . . 34
7.5. Diameter Credit Control with QoS Information . . . . . . . 35 7.6. Classifier Examples . . . . . . . . . . . . . . . . . . . 35
7.6. Classifier Examples . . . . . . . . . . . . . . . . . . . 36 7.7. QoS Examples . . . . . . . . . . . . . . . . . . . . . . . 36
7.7. QoS Examples . . . . . . . . . . . . . . . . . . . . . . . 37 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 37
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 38 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 37
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 38 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38 11. Security Considerations . . . . . . . . . . . . . . . . . . . 39
11. Security Considerations . . . . . . . . . . . . . . . . . . . 41 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 40
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 41 12.1. Normative References . . . . . . . . . . . . . . . . . . . 40
12.1. Normative References . . . . . . . . . . . . . . . . . . . 41 12.2. Informative References . . . . . . . . . . . . . . . . . . 40
12.2. Informative References . . . . . . . . . . . . . . . . . . 42 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 41
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 42
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 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 structure of a rule in the entire rule set defined in this The QoS-Resources AVP represents a complete rule set with each rule
document consist of a conditions part and corresponding actions. The represented by a QoS-Rule AVP. Each rule consists of a conditions
AVPs responsible for expressing a condition are defined in Section 4. part and the corresponding actions to be performed if the conditions
Capabilities to match all or a subset of the data traffic is are satisfied. The AVPs responsible for expressing a condition are
provided. Additionally, time-based conditions can be expressed based defined in Section 4. Capabilities to match all or a subset of the
on the functionality offered in Section 4.2. The action part of a data traffic is provided. Additionally, time-based conditions can be
rule contains information for handling conflict resolution, such as a expressed based on the functionality offered in Section 4.2. The
priority value for each individual rule within a rule set, and action part of a rule contains information for handling conflict
further description regarding QoS related actions. 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. 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 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 describes
a list of policies. a list of policies.
QoS-Resources ::= < AVP Header: XXX > QoS-Resources ::= < AVP Header: XXX >
1*{ Rule } 1*{ QoS-Rule }
* [ AVP ] * [ AVP ]
3.2. Rule AVP 3.2. QoS-Rule AVP
The Rule AVP (AVP Code TBD) is of type Grouped and defines a specific The QoS-Rule AVP (AVP Code TBD) is of type Grouped and defines a
condition and action combination. specific condition and action combination.
Rule ::= < AVP Header: XXX > QoS-Rule ::= < AVP Header: XXX >
[ Rule-Precedence ] [ QoS-Rule-Precedence ]
; Condition part of a Rule ; Condition part of a Rule
; ------------------------ ; ------------------------
[ Classifier ] [ Classifier ]
* [ Time-Of-Day-Condition ] * [ Time-Of-Day-Condition ]
; Action and Meta-Data ; Action and Meta-Data
; -------------------- ; --------------------
[ Action ] [ QoS-Action ]
; Info about QoS related Actions ; Info about QoS related Actions
; ------------------------------ ; ------------------------------
[ QoS-Semantics ] [ QoS-Semantics ]
[ QoS-Profile-Template ] [ QoS-Profile-Template ]
[ QoS-Parameters ] [ QoS-Parameters ]
[ Excess-Treatment ] [ Excess-Treatment ]
; Extension Point ; Extension Point
; --------------- ; ---------------
* [ AVP ] * [ AVP ]
If the QoS-Profile-Template AVP is not included in the Rule AVP then If the QoS-Profile-Template AVP is not included in the Qos-Rule AVP
the default setting is assumed, namely a setting of the Vendor-Id AVP then the default setting is assumed, namely a setting of the
to 0 (for IETF) and the QoS-Profile-Id AVP to zero (0) (for the Vendor-Id AVP to 0 (for IETF) and the QoS-Profile-Id AVP to zero (0)
profile defined in [I-D.ietf-dime-qos-parameters]). Note that the (for the profile defined in [I-D.ietf-dime-qos-parameters]). Note
content of the QoS-Parameters are defined in the respective that the content of the QoS-Parameters are defined in the respective
specification defining the QoS parameters. When the Vendor-Id AVP is 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) 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 then the AVPs included in the QoS-Parameters AVP are the AVPs defined
in [I-D.ietf-dime-qos-parameters]. in [I-D.ietf-dime-qos-parameters].
3.3. Rule-Precedence AVP 3.3. QoS-Rule-Precedence AVP
The Rule-Precedence AVP (AVP Code TBD) is of type Unsigned32 and The QoS-Rule-Precedence AVP (AVP Code TBD) is of type Unsigned32 and
specifies the execution order of the rules expressed in the QoS- specifies the execution order of the rules expressed in the QoS-
Resources AVP. Rules with equal precedence MAY be executed in Resources AVP. The lower the numerical value of QoS-Rule-Precedence
parallel if supported by the Resource Management Function. If the AVP, the higher the rule precedence. Rules with equal precedence MAY
Rule-Precedence AVP is absent from the Rule AVP, the rules SHOULD be be executed in parallel if supported by the Resource Management
executed in the order in which they appear in the QoS-Resources AVP. Function. If the QoS-Rule-Precedence AVP is absent from the QoS-Rule
The lower the numerical value of Rule-Precedence AVP, the higher the AVP, the rules SHOULD be executed in the order in which they appear
rule precedence. in the QoS-Resources AVP.
4. Conditions 4. Conditions
This section describes the condition part of a rule. Two condition This section describes the condition part of a rule. Two condition
types are introduced by this document: packet classification types are introduced by this document: packet classification
conditions represented by the Classifier AVP and time of day conditions represented by the Classifier AVP and time of day
conditions represented by the Time-Of-Day-Condition AVP. conditions represented by the Time-Of-Day-Condition AVP.
If more than one instance of the Time-Of-Day-Condition AVP is present If more than one instance of the Time-Of-Day-Condition AVP is present
in the Rule AVP, the current time at QoS rule evaluation MUST be in the QoS-Rule AVP, the current time at QoS rule evaluation MUST be
within at least one of the time windows specified in one of the Time- within at least one of 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 Rule AVP, both the time of day and packet classification the same QoS-Rule AVP, both the time of day and packet classification
conditions MUST match for the QoS specification action to be applied. conditions MUST match for the QoS specification action to be applied.
4.1. Traffic Classifiers 4.1. Traffic Classifiers
Classifiers are used in many applications to specify how to select a Classifiers are used in many applications to specify how to select a
subset of data packets for subsequent treatment as indicated in the subset of data packets for subsequent treatment as indicated in the
action part of a rule. For example in a QoS application, if a packet 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 matches a classifier then that packet will be treated in accordance
with a QoS specification associated with that classifier. Figure 1 with a QoS specification associated with that classifier. Figure 1
shows a typical deployment. shows a typical deployment.
skipping to change at page 8, line 28 skipping to change at page 8, line 28
+------+------+ +------+------+
| | | |
| 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 terminals, the terminals that receive packets from the
Managed terminal or sends packets to the managed terminal is located Managed terminal or send packets to the managed terminal are 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
are incoming (IN) from the Managed Terminal or packets outgoing (OUT) are incoming (IN) from the Managed Terminal or packets outgoing (OUT)
to the Managed Terminal. to the Managed Terminal.
A Classifier consists of a group of attributes that specify how to A Classifier consists of a group of attributes that specify how to
match a packet. Each set of attributes expresses values about match a packet. Each set of attributes expresses values about
aspects of the packet - typically the packet header. Different aspects of the packet - typically the packet header. Different
protocols therefore would use different attributes. protocols therefore would use different attributes.
skipping to change at page 10, line 34 skipping to change at page 10, line 34
4.1.4. Direction AVP 4.1.4. Direction AVP
The Direction AVP (AVP Code TBD) is of type Enumerated and specifies The Direction AVP (AVP Code TBD) is of type Enumerated and 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. If the Direction whereas the To-Spec refers to the Managed Terminal. If the Direction
AVP is omitted, the Classifier matches packets flowing in both AVP is omitted, the Classifier matches packets flowing in both
direction. directions.
Value | Name and Semantic Value | Name and Semantic
------+-------------------------------------------------- ------+--------------------------------------------------
0 | IN - The classifier applies to flows from the 0 | IN - The classifier applies to flows from the
| Managed Terminal. | Managed Terminal.
1 | OUT - The classifier applies to flows to the 1 | OUT - The classifier applies to flows to the
| Managed Terminal. | Managed Terminal.
2 | BOTH - The classifier applies to flows both to 2 | BOTH - The classifier applies to flows both to
| and from the Managed Terminal. | and from the Managed Terminal.
skipping to change at page 13, line 39 skipping to change at page 13, line 39
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.
If the IP-Address-Start AVP is empty then the semantic is equivalent
to not having the IP-Address-Start AVP included in the command.
4.1.7.4. IP-Address-Start AVP 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.
4.1.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
skipping to change at page 16, line 13 skipping to change at page 16, line 5
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.
If the Port-Start AVP is empty then this is equivalent to not
carrying a Port-Start AVP in the command.
4.1.7.16. Port-Start AVP 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
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.
skipping to change at page 20, line 13 skipping to change at page 20, line 13
in [RFC2780]. in [RFC2780].
4.1.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 ] * [ User-Priority-Range ]
* [ AVP ] * [ AVP ]
4.1.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 ]
4.1.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 that contains the value of the Ethertype
in the packet to match. This AVP MAY be present in the case of DIX field in the packet to match. This AVP MAY be present in the case of
or if SNAP is present at 802.2 but the ETH-SAP AVP MUST NOT be DIX or if SNAP is present at 802.2 but the ETH-SAP AVP MUST NOT be
present in this case. present in this case.
4.1.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.
4.1.8.18. VLAN-ID-Range AVP 4.1.8.18. VLAN-ID-Range AVP
skipping to change at page 22, line 41 skipping to change at page 22, line 41
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.
4.1.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.
4.1.8.23. ETH-Priority-Range AVP 4.1.8.23. User-Priority-Range AVP
The ETH-Priority-Range AVP (AVP Code TBD) is of type Grouped and The User-Priority-Range AVP (AVP Code TBD) is of type Grouped and
specifies an inclusive range to match the user_priority parameter 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 Low-User-Priority and less than or equal to
ETH-High-Priority. If this AVP is omitted, then comparison of the High-User-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 > User-Priority-Range ::= < AVP Header: XXX >
* [ ETH-Low-Priority ] * [ Low-User-Priority ]
* [ ETH-High-Priority ] * [ High-User-Priority ]
* [ AVP ] * [ AVP ]
4.1.8.24. ETH-Low-Priority AVP 4.1.8.24. Low-User-Priority AVP
The ETH-Low-Priority AVP (AVP Code TBD) is of type Unsigned32. The The Low-User-Priority AVP (AVP Code TBD) is of type Unsigned32. The
value MUST be in the range from 0 to 7. value MUST be in the range from 0 to 7.
4.1.8.25. ETH-High-Priority AVP 4.1.8.25. High-User-Priority AVP
The ETH-High-Priority AVP (AVP Code TBD) is of type Unsigned32. The The High-User-Priority AVP (AVP Code TBD) is of type Unsigned32. The
value MUST be in the range from 0 to 7. value MUST be in the range from 0 to 7.
4.2. 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.
skipping to change at page 26, line 45 skipping to change at page 26, line 45
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 illustrates 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. Action AVP 5.1. QoS-Action AVP
The Action AVP (AVP Code TBD) is of type Enumerated and lists the The QoS-Action AVP (AVP Code TBD) is of type Enumerated and lists the
actions that are associated with the condition part of a rule. The 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
1: shape 1: shape
2: police
2: mark 2: mark
drop: drop:
All traffic that is met by the condition part of a rule MUST be All traffic that is met by the condition part of a rule MUST be
dropped. This action implements firewalling functionality. dropped. This action implements firewalling functionality.
shape: shape:
[RFC2475] describes shaping as "the process of delaying packets [RFC2475] describes shaping as "the process of delaying packets
within a traffic stream to cause it to conform to some defined within a traffic stream to cause it to conform to some defined
traffic profile". When the action is set to 'shape', it is traffic profile". When the action is set to 'shape', it is
expected that the QoS-Parameters AVP carries QoS information to expected that the QoS-Parameters AVP carries QoS information to
indicate how to shape the traffic indicated in the condition part indicate how to shape the traffic indicated in the condition part
of the rule. of the rule.
police:
[RFC2475] describes policing as "the process of discarding packets
(by a dropper) within a traffic stream in accordance with the
state of a corresponding meter enforcing a traffic profile". When
the action is set to 'police', it is expected that the QoS-
Parameters AVP carries QoS information to describe traffic
conforming to a traffic profile. Excess traffic is dropped.
Hence, there is no need to include the Excess-Treatement AVP with
the Excess-Treatment-Action AVP set to 'drop' as this
functionality is implied.
mark: mark:
[RFC2475] describes marking as "the process of setting the DS [RFC2475] describes marking as "the process of setting the DS
codepoint in a packet based on defined rules". When the action is codepoint in a packet based on defined rules". When the action is
set to 'mark', it is expected that the QoS-Parameters AVP carries set to 'mark', it is expected that the QoS-Parameters AVP carries
information about the DiffServ marking. information about the DiffServ marking.
Further action values can be registered, as described in Further action values can be registered, as described in
Section 10.4. Section 10.3.
[RFC2475] also describes an action called "policing" as "the process
of discarding packets (by a dropper) within a traffic stream in
accordance with the state of a corresponding meter enforcing a
traffic profile". This behavior in modeled in the QoS-Rule through
the inclusion of the Excess-Treatment AVP containing a QoS-Action AVP
set to "drop".
5.2. QoS-Profile-Id AVP 5.2. QoS-Profile-Id AVP
The QoS-Profile-Id AVP (AVP Code TBD) is of type Unsigned32 and The QoS-Profile-Id AVP (AVP Code TBD) is of type Unsigned32 and
contains a QoS profile template identifier. An initial QoS profile contains a QoS profile template identifier. An initial QoS profile
template is defined with value of 0 and can be found in template is defined with value of 0 and can be found in
[I-D.ietf-dime-qos-parameters]. The registry for the QoS profile [I-D.ietf-dime-qos-parameters]. The registry for the QoS profile
templates is created with the same document. templates is created with the same document.
5.3. QoS-Profile-Template AVP 5.3. QoS-Profile-Template AVP
The QoS-Profile-Template AVP (AVP Code TBD) is of type Grouped and 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 defines the namespace of the QoS profile (indicated in the Vendor-ID
AVP) followed by the specific value for the profile. AVP) followed by the specific value for the profile.
The Vendor-Id AVP contains a 32 bit IANA SMI Network Management The Vendor-Id AVP contains a 32 bit IANA Private Enterprise Number
Private Enterprise Code and the QoS-Profile-Id AVP contains the (PEN) and the QoS-Profile-Id AVP contains the template identifier
template identifier assigned by the vendor. The vendor identifier of assigned by the vendor. The vendor identifier of zero (0) is used
zero (0) is used for the IETF. for the IETF.
QoS-Profile-Template ::= < AVP Header: XXX > QoS-Profile-Template ::= < AVP Header: XXX >
{ Vendor-Id } { Vendor-Id }
{ QoS-Profile-Id } { QoS-Profile-Id }
* [ AVP ] * [ AVP ]
5.4. QoS-Semantics 5.4. QoS-Semantics
The QoS-Semantics AVP (AVP Code TBD) is of type Enumerated and The QoS-Semantics AVP (AVP Code TBD) is of type Enumerated and
provides the semantics for the QoS-Profile-Template and QoS- provides the semantics for the QoS-Profile-Template and QoS-
Parameters AVPs in the Rule AVP. Parameters AVPs in the QoS-Rule AVP.
This document defines the following values: This document defines the following values:
(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 semantic of the QoS parameters depend on the information provided The semantic of the QoS parameters depend on the information provided
skipping to change at page 30, line 5 skipping to change at page 30, line 5
QoS-Parameters ::= < AVP Header: XXX > QoS-Parameters ::= < AVP Header: XXX >
* [ AVP ] * [ AVP ]
5.6. Excess-Treatment AVP 5.6. Excess-Treatment AVP
The Excess-Treatment AVP (AVP Code TBD) is of type grouped and The Excess-Treatment AVP (AVP Code TBD) is of type grouped and
indicates how out-of-profile traffic, i.e. traffic not covered by the indicates how out-of-profile traffic, i.e. traffic not covered by the
original QoS-Profile-Template and QoS-Parameters AVPs, is treated. original QoS-Profile-Template and QoS-Parameters AVPs, is treated.
The additional QoS-Profile-Template and QoS-Parameters AVPs carried The additional QoS-Action, QoS-Profile-Template and QoS-Parameters
inside the Excess-Treatment AVP provide information about the QoS AVPs carried inside the Excess-Treatment AVP provide information
treatment of the excess traffic. In case the Excess-Treatment AVP is about the QoS treatment of the excess traffic. In case the Excess-
absent then the treatment of the out-of-profile traffic is left to Treatment AVP is absent then the treatment of the out-of-profile
the discretion of the node performing QoS treatment. traffic is left to the discretion of the node performing QoS
treatment.
Excess-Treatment ::= < AVP Header: XXX > Excess-Treatment ::= < AVP Header: XXX >
{ Excess-Treatment-Action } { QoS-Action }
[ QoS-Profile-Template ] [ QoS-Profile-Template ]
[ QoS-Parameters ] [ QoS-Parameters ]
* [ AVP ] * [ AVP ]
5.7. Excess-Treatment-Action
The Excess-Treatment-Action AVP (AVP Code TBD) is of type Enumerated
and lists the actions about how the out-of-traffic regarding a
specific QoS profile is treated.
0: drop
1: shape
2: mark
drop:
When excess treatment action is set to 'drop', excess traffic is
dropped.
shape:
When excess treatment action is set to 'shape', it is expected
that the QoS-Parameters AVP carries information on how to shape
the excess traffic. For example, the TMOD AVP, defined in
[I-D.ietf-dime-qos-parameters], carried inside the QoS-Parameters
AVP of the Excess-Treatment AVP indicates how to shape the excess
traffic. Note that shaping might cause unbounded queue growth at
the shaper and consequently traffic may still get dropped.
mark:
When excess treatment action is set to 'mark', it is expected that
the QoS-Parameters AVP carries information about the QoS class.
For example, excess traffic may need to get marked differently to
the traffic conformant to the traffic profile.
When the Excess-Treatment AVP is omitted then excess treatment is
essentially unspecified and there are no guaranted behavior with
regard to excess traffic, i.e., a QoS aware node can do what it finds
suitable.
Further values can be registered, as described in Section 10.3.
6. QoS Capability Indication 6. QoS Capability Indication
The QoS-Capability AVP (AVP Code TBD) is of type Grouped and contains The QoS-Capability AVP (AVP Code TBD) is of type Grouped and contains
a list of supported Quality of Service profile templates (and a list of supported Quality of Service profile templates (and
therefore the support of the respective parameter AVPs). therefore the support of the respective parameter AVPs).
The QoS-Capability AVP may be used for a simple announcement of the 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 QoS capabilities and QoS profiles supported by a peer. It may also
be used to negotiate a mutually supported set of QoS capabilities and be used to negotiate a mutually supported set of QoS capabilities and
QoS profiles between two peers. In such a case, handling of failed QoS profiles between two peers. In such a case, handling of failed
skipping to change at page 31, line 42 skipping to change at page 31, line 5
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 Rule AVP set to provisioned QoS profile with the QoS-Semantics in the QoS-Rule AVP
"QoS-Authorized", to the NAS in the final DEA message. set to "QoS-Authorized", to the NAS in the final DEA 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 37, line 39 skipping to change at page 36, line 39
7.7. QoS Examples 7.7. QoS Examples
The following high level description aims to illustrate the The following high level description aims to illustrate the
interworking between the Diameter QoS AVPs defined in this document interworking between the Diameter QoS AVPs defined in this document
and the QoS parameters defined in [I-D.ietf-dime-qos-parameters]. and the QoS parameters defined in [I-D.ietf-dime-qos-parameters].
Consider the following example where a rule should be installed that Consider the following example where a rule should be installed that
limits traffic to 1 Mbit/sec and where out-of-profile traffic shall limits traffic to 1 Mbit/sec and where out-of-profile traffic shall
be dropped.The Classifers are ignored in this example. be dropped.The Classifers are ignored in this example.
This would require the Action AVP to be set to 'police' (which also This would require the QoS-Action AVP to be set to 'shape' and the
implies the Excess-Treatment-Action AVP to be set to 'drop' and QoS-Parameters AVP carries the Bandwidth AVP indicating the 1 Mbit/
explicitly including the Excess-Treatment-Action AVP is not sec limit. The QoS-Action carried inside the Excess-Treatment AVP
necessary). The QoS-Parameters AVP carries the Bandwidth AVP would be set to 'drop'.
indicating the 1 Mbit/sec limit.
In a second, more complex scenario, we consider traffic marking with In a second, more complex scenario, we consider traffic marking with
DiffServ. In-profile traffic (of 5 Mbits/sec in our example) shall DiffServ. In-profile traffic (of 5 Mbits/sec in our example) shall
be associated with a particular PHB-Class "X". Out-of-profile be associated with a particular PHB-Class "X". Out-of-profile
traffic shall belong to a different PHB-Class, in our example "Y". traffic shall belong to a different PHB-Class, in our example "Y".
This configuration would require the Action AVP to be set to 'mark'. This configuration would require the QoS-Action AVP to be set to
'mark'. The QoS-Parameters AVPs for the traffic conforming of the
The QoS-Parameters AVPs for the traffic conforming of the profile profile contains two AVPs, namely the TMOD-1 AVP and the PHB-Class
contains two AVPs, namely the TMOD-1 AVP and the PHB-Class AVP. The AVP. The TMOD-1 AVP describes the traffic characteristics, namely 5
TMOD-1 AVP describes the traffic characteristics, namely 5 Mbit/sec, Mbit/sec, and the PHB-Class AVP is set to class "X". Then, the
and the PHB-Class AVP is set to class "X". Then, the Excess- Excess-Treatment AVP has to be included with the QoS-Action AVP set
Treatment AVP has to be included with the Excess-Treatment-Action AVP to 'mark' and the QoS-Parameters AVP to carry another PHB-Class AVP
set to 'mark' and the QoS-Parameters AVP to carry another PHB-Class indicating PHB-Class AVP setting to class "Y".
AVP indicating PHB-Class AVP setting to class "Y".
8. Acknowledgments 8. Acknowledgments
We would like to thank Victor Fajardo, Tseno Tsenov, Robert Hancock, We would like to thank Victor Fajardo, Tseno Tsenov, Robert Hancock,
Jukka Manner, Cornelia Kappler, Xiaoming Fu, Frank Alfano, Tolga Jukka Manner, Cornelia Kappler, Xiaoming Fu, Frank Alfano, Tolga
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. We thank Victor Fajardo for his job as PROTO Li for their comments. We thank Victor Fajardo for his job as PROTO
document shepherd. document shepherd.
skipping to change at page 38, line 38 skipping to change at page 37, line 36
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 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-Resources TBD 3.1 Grouped | |QoS-Resources TBD 3.1 Grouped |
|Rule TBD 3.2 Grouped | |QoS-Rule TBD 3.2 Grouped |
|QoS-Rule-Precedence TBD 3.3 Unsigned32 |
|Classifier TBD 4.1.1 Grouped | |Classifier TBD 4.1.1 Grouped |
|Classifier-ID TBD 4.1.2 OctetString | |Classifier-ID TBD 4.1.2 OctetString |
|Protocol TBD 4.1.3 Enumerated | |Protocol TBD 4.1.3 Enumerated |
|Direction TBD 4.1.4 Enumerated | |Direction TBD 4.1.4 Enumerated |
|From-Spec TBD 4.1.5 Grouped | |From-Spec TBD 4.1.5 Grouped |
|To-Spec TBD 4.1.6 Grouped | |To-Spec TBD 4.1.6 Grouped |
|Negated TBD 4.1.7.1 Enumerated | |Negated TBD 4.1.7.1 Enumerated |
|IP-Address TBD 4.1.7.2 Address | |IP-Address TBD 4.1.7.2 Address |
|IP-Address-Range TBD 4.1.7.3 Grouped | |IP-Address-Range TBD 4.1.7.3 Grouped |
|IP-Address-Start TBD 4.1.7.4 Address | |IP-Address-Start TBD 4.1.7.4 Address |
skipping to change at page 39, line 40 skipping to change at page 38, line 40
|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 |
|C-VID-Start TBD 4.1.8.21 Unsigned32 | |C-VID-Start TBD 4.1.8.21 Unsigned32 |
|C-VID-End TBD 4.1.8.22 Unsigned32 | |C-VID-End TBD 4.1.8.22 Unsigned32 |
|ETH-Priority-Range TBD 4.1.8.23 Grouped | |User-Priority-Range TBD 4.1.8.23 Grouped |
|ETH-Low-Priority TBD 4.1.8.24 Unsigned32 | |Low-User-Priority TBD 4.1.8.24 Unsigned32 |
|ETH-High-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-End-Time TBD 4.2.8 Time |
|Timezone-Flag TBD 4.2.9 Enumerated | |Timezone-Flag TBD 4.2.9 Enumerated |
|Timezone-Offset TBD 4.2.10 Integer32 | |Timezone-Offset TBD 4.2.10 Integer32 |
|Action TBD 5.1 Grouped | |QoS-Action TBD 5.1 Grouped |
|QoS-Profile-Id TBD 5.2.1 Unsigned32 | |QoS-Profile-Id TBD 5.2 Unsigned32 |
|QoS-Profile-Template TBD 5.2.2 Grouped | |QoS-Profile-Template TBD 5.3 Grouped |
|QoS-Semantics TBD 5.2.3 Enumerated | |QoS-Semantics TBD 5.4 Enumerated |
|QoS-Parameters TBD 5.2.4 Grouped | |QoS-Parameters TBD 5.5 Grouped |
|Rule-Precedence TBD 5.2.5 Unsigned32 | |Excess-Treatment TBD 5.6 Grouped |
|Excess-Treatment TBD 5.2.6 Grouped |
|Excess-Treatment-Action TBD 5.2.7 Unsigned32 |
|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 registry for the QoS-Semantics
AVP. The following values are allocated by this specification. 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. The definition of new values is subject to the Specification Required
policy [RFC5226].
10.3. Excess Treatment Action
IANA is also requested to allocate a registry for the Excess-
Treatment-Action AVP. The following values are allocated by this
specification:
(0): drop
(1): shape
(2): mark
A specification is required to add a new value to the registry.
10.4. Action 10.3. Action
IANA is also requested to allocate a registry for the Action AVP. IANA is also requested to allocate a registry for the QoS-Action AVP.
The following values are allocated by this specification: The following values are allocated by this specification:
0: drop 0: drop
1: shape 1: shape
2: police
2: mark 2: mark
A specification is required to add a new value to the registry.
The definition of new values is subject to the Specification Required
policy [RFC5226].
11. Security Considerations 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 3588 [RFC3588]. Diameter protocol itself have been discussed in RFC 3588 [RFC3588].
Use of the AVPs defined in this document MUST take into consideration Use of the AVPs defined in this document MUST take into consideration
the security issues and requirements of the Diameter Base protocol. the security issues and requirements of the Diameter Base protocol.
12. References 12. References
skipping to change at page 42, line 5 skipping to change at page 40, line 38
[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.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
12.2. Informative References 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-07 (work in progress), draft-ietf-dime-diameter-qos-08 (work in progress),
December 2008. May 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-09 (work in progress), draft-ietf-dime-qos-parameters-11 (work in progress),
January 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. [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
Arkko, "Diameter Base Protocol", RFC 3588, September 2003. 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,
 End of changes. 63 change blocks. 
216 lines changed or deleted 154 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/