draft-ietf-dime-qos-attributes-06.txt   draft-ietf-dime-qos-attributes-07.txt 
Diameter Maintenance and J. Korhonen, Ed. Diameter Maintenance and J. Korhonen
Extensions (DIME) TeliaSonera Extensions (DIME) TeliaSonera
Internet-Draft H. Tschofenig Internet-Draft H. Tschofenig
Intended status: Standards Track Nokia Siemens Networks Intended status: Standards Track Nokia Siemens Networks
Expires: November 27, 2008 M. Arumaithurai Expires: December 28, 2008 M. Arumaithurai
University of Goettingen University of Goettingen
M. Jones M. Jones, Ed.
A. Lior A. Lior
Bridgewater Systems Bridgewater Systems
May 26, 2008 June 26, 2008
Quality of Service Attributes for Diameter Quality of Service Attributes for Diameter
draft-ietf-dime-qos-attributes-06.txt draft-ietf-dime-qos-attributes-07.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 November 27, 2008. This Internet-Draft will expire on December 28, 2008.
Abstract Abstract
This document extends the QoSFilterRule AVP functionality of the This document extends the IPFilterRule AVP functionality of the
Diameter Base protocol and the functionality of the QoS-Filter-Rule Diameter Base protocol and the functionality of the QoS-Filter-Rule
AVP defined in RFC 4005. The ability to convey Quality of Service AVP defined in RFC 4005. The ability to convey Quality of Service
information using the AVPs defined in this document is available to information using the AVPs defined in this document is available to
existing and future Diameter applications where permitted by the existing and future Diameter applications where permitted by the
command ABNF. command ABNF.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Diameter QoS Defined AVPs . . . . . . . . . . . . . . . . . . 4 3. Diameter QoS Defined AVPs . . . . . . . . . . . . . . . . . . 4
3.1. QoS-Capability AVP . . . . . . . . . . . . . . . . . . . . 4 3.1. QoS-Capability AVP . . . . . . . . . . . . . . . . . . . . 4
3.2. QoS-Profile-Template AVP . . . . . . . . . . . . . . . . . 5 3.2. QoS-Profile-Template AVP . . . . . . . . . . . . . . . . . 4
3.3. Vendor-Specific-QoS-Profile-Template AVP . . . . . . . . . 5 3.3. Vendor-Specific-QoS-Profile-Template AVP . . . . . . . . . 4
3.4. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 5 3.4. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 5
3.5. Extended-QoS-Filter-Rule AVP . . . . . . . . . . . . . . . 5 3.5. Extended-QoS-Filter-Rule AVP . . . . . . . . . . . . . . . 5
3.6. QoS-Semantics . . . . . . . . . . . . . . . . . . . . . . 6 3.6. QoS-Semantics . . . . . . . . . . . . . . . . . . . . . . 5
3.7. QoS-Parameters AVP . . . . . . . . . . . . . . . . . . . . 6 3.7. QoS-Parameters AVP . . . . . . . . . . . . . . . . . . . . 6
3.8. QoS-Rule-Precedence AVP . . . . . . . . . . . . . . . . . 6 3.8. QoS-Rule-Precedence AVP . . . . . . . . . . . . . . . . . 6
4. Semantics of QoS Parameters . . . . . . . . . . . . . . . . . 6 4. Semantics of QoS Parameters . . . . . . . . . . . . . . . . . 6
5. Diameter Classifier AVPs . . . . . . . . . . . . . . . . . . . 7 5. Diameter Classifier AVPs . . . . . . . . . . . . . . . . . . . 7
5.1. Classifier AVP . . . . . . . . . . . . . . . . . . . . . . 10 5.1. Classifier AVP . . . . . . . . . . . . . . . . . . . . . . 9
5.2. Classifier-ID AVP . . . . . . . . . . . . . . . . . . . . 11 5.2. Classifier-ID AVP . . . . . . . . . . . . . . . . . . . . 10
5.3. Protocol AVP . . . . . . . . . . . . . . . . . . . . . . . 11 5.3. Protocol AVP . . . . . . . . . . . . . . . . . . . . . . . 10
5.4. Direction AVP . . . . . . . . . . . . . . . . . . . . . . 11 5.4. Direction AVP . . . . . . . . . . . . . . . . . . . . . . 10
5.5. From-Spec AVP . . . . . . . . . . . . . . . . . . . . . . 12 5.5. From-Spec AVP . . . . . . . . . . . . . . . . . . . . . . 10
5.6. To-Spec AVP . . . . . . . . . . . . . . . . . . . . . . . 12 5.6. To-Spec AVP . . . . . . . . . . . . . . . . . . . . . . . 11
5.7. Source and Destination AVPs . . . . . . . . . . . . . . . 13 5.7. Source and Destination AVPs . . . . . . . . . . . . . . . 12
5.7.1. Negated AVP . . . . . . . . . . . . . . . . . . . . . 13 5.7.1. Negated AVP . . . . . . . . . . . . . . . . . . . . . 13
5.7.2. IP-Address AVP . . . . . . . . . . . . . . . . . . . . 14 5.7.2. IP-Address AVP . . . . . . . . . . . . . . . . . . . . 13
5.7.3. IP-Address-Range AVP . . . . . . . . . . . . . . . . . 14 5.7.3. IP-Address-Range AVP . . . . . . . . . . . . . . . . . 13
5.7.4. IP-Address-Start AVP . . . . . . . . . . . . . . . . . 14 5.7.4. IP-Address-Start AVP . . . . . . . . . . . . . . . . . 14
5.7.5. IP-Address-End AVP . . . . . . . . . . . . . . . . . . 15 5.7.5. IP-Address-End AVP . . . . . . . . . . . . . . . . . . 14
5.7.6. IP-Address-Mask AVP . . . . . . . . . . . . . . . . . 15 5.7.6. IP-Address-Mask AVP . . . . . . . . . . . . . . . . . 14
5.7.7. IP-Mask-Bit-Mask-Width AVP . . . . . . . . . . . . . . 15 5.7.7. IP-Mask-Bit-Mask-Width AVP . . . . . . . . . . . . . . 14
5.7.8. MAC-Address AVP . . . . . . . . . . . . . . . . . . . 15 5.7.8. MAC-Address AVP . . . . . . . . . . . . . . . . . . . 14
5.7.9. Port AVP . . . . . . . . . . . . . . . . . . . . . . . 15 5.7.9. MAC-Address-Mask AVP . . . . . . . . . . . . . . . . . 14
5.7.10. Port-Range AVP . . . . . . . . . . . . . . . . . . . . 15 5.7.10. MAC-Address-Mask-Pattern AVP . . . . . . . . . . . . . 15
5.7.11. Port-Start AVP . . . . . . . . . . . . . . . . . . . . 16 5.7.11. EUI64-Address AVP . . . . . . . . . . . . . . . . . . 15
5.7.12. Port-End AVP . . . . . . . . . . . . . . . . . . . . . 16 5.7.12. EUI64-Address-Mask AVP . . . . . . . . . . . . . . . . 15
5.7.13. Use-Assigned-Address AVP . . . . . . . . . . . . . . . 16 5.7.13. EUI64-Address-Mask-Pattern AVP . . . . . . . . . . . . 15
5.8. Header Option AVPs . . . . . . . . . . . . . . . . . . . . 16 5.7.14. VLAN-ID AVP . . . . . . . . . . . . . . . . . . . . . 15
5.8.1. Diffserv-Code-Point AVP . . . . . . . . . . . . . . . 16 5.7.15. Port AVP . . . . . . . . . . . . . . . . . . . . . . . 16
5.8.2. Fragmentation-Flag AVP . . . . . . . . . . . . . . . . 16 5.7.16. Port-Range AVP . . . . . . . . . . . . . . . . . . . . 16
5.7.17. Port-Start AVP . . . . . . . . . . . . . . . . . . . . 16
5.7.18. Port-End AVP . . . . . . . . . . . . . . . . . . . . . 16
5.7.19. Use-Assigned-Address AVP . . . . . . . . . . . . . . . 16
5.8. Header Option AVPs . . . . . . . . . . . . . . . . . . . . 17
5.8.1. Diffserv-Code-Point AVP . . . . . . . . . . . . . . . 17
5.8.2. Fragmentation-Flag AVP . . . . . . . . . . . . . . . . 17
5.8.3. IP-Option AVP . . . . . . . . . . . . . . . . . . . . 17 5.8.3. IP-Option AVP . . . . . . . . . . . . . . . . . . . . 17
5.8.4. IP-Option-Type AVP . . . . . . . . . . . . . . . . . . 17 5.8.4. IP-Option-Type AVP . . . . . . . . . . . . . . . . . . 18
5.8.5. IP-Option-Value AVP . . . . . . . . . . . . . . . . . 17 5.8.5. IP-Option-Value AVP . . . . . . . . . . . . . . . . . 18
5.8.6. TCP-Option AVP . . . . . . . . . . . . . . . . . . . . 17 5.8.6. TCP-Option AVP . . . . . . . . . . . . . . . . . . . . 18
5.8.7. TCP-Option-Type AVP . . . . . . . . . . . . . . . . . 18 5.8.7. TCP-Option-Type AVP . . . . . . . . . . . . . . . . . 18
5.8.8. TCP-Option-Value AVP . . . . . . . . . . . . . . . . . 18 5.8.8. TCP-Option-Value AVP . . . . . . . . . . . . . . . . . 18
5.8.9. TCP-Flags AVP . . . . . . . . . . . . . . . . . . . . 18 5.8.9. TCP-Flags AVP . . . . . . . . . . . . . . . . . . . . 18
5.8.10. TCP-Flag-Type AVP . . . . . . . . . . . . . . . . . . 18 5.8.10. TCP-Flag-Type AVP . . . . . . . . . . . . . . . . . . 19
5.8.11. ICMP-Type . . . . . . . . . . . . . . . . . . . . . . 19 5.8.11. ICMP-Type . . . . . . . . . . . . . . . . . . . . . . 19
5.8.12. ICMP-Type-Number AVP . . . . . . . . . . . . . . . . . 19 5.8.12. ICMP-Type-Number AVP . . . . . . . . . . . . . . . . . 20
5.8.13. ICMP-Code AVP . . . . . . . . . . . . . . . . . . . . 19 5.8.13. ICMP-Code AVP . . . . . . . . . . . . . . . . . . . . 20
6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 5.8.14. ETH-Option AVP . . . . . . . . . . . . . . . . . . . . 20
6.1. Diameter EAP with QoS Information . . . . . . . . . . . . 20 5.8.15. ETH-Proto-Type AVP . . . . . . . . . . . . . . . . . . 20
6.2. Diameter NASREQ with QoS Information . . . . . . . . . . . 21 5.8.16. ETH-Ether-Type AVP . . . . . . . . . . . . . . . . . . 20
6.3. QoS Authorization . . . . . . . . . . . . . . . . . . . . 22 5.8.17. ETH-SAP AVP . . . . . . . . . . . . . . . . . . . . . 20
6.4. Diameter Server Initiated Re-authorization of QoS . . . . 23 5.8.18. ETH-Priority-Range AVP . . . . . . . . . . . . . . . . 21
6.5. Diameter Credit Control with QoS Information . . . . . . . 24 5.8.19. ETH-Low-Priority AVP . . . . . . . . . . . . . . . . . 21
6.6. Classifier mapping from IPFilterRule type . . . . . . . . 25 5.8.20. ETH-High-Priority AVP . . . . . . . . . . . . . . . . 21
6.7. Complex Classifier . . . . . . . . . . . . . . . . . . . . 25 6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 25 6.1. Diameter EAP with QoS Information . . . . . . . . . . . . 21
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 6.2. Diameter NASREQ with QoS Information . . . . . . . . . . . 22
9. Security Considerations . . . . . . . . . . . . . . . . . . . 26 6.3. QoS Authorization . . . . . . . . . . . . . . . . . . . . 23
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 26 6.4. Diameter Server Initiated Re-authorization of QoS . . . . 24
10.1. Normative References . . . . . . . . . . . . . . . . . . . 26 6.5. Diameter Credit Control with QoS Information . . . . . . . 25
10.2. Informative References . . . . . . . . . . . . . . . . . . 27 6.6. Classifier Examples . . . . . . . . . . . . . . . . . . . 26
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 27 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 27
Intellectual Property and Copyright Statements . . . . . . . . . . 29 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
9. Security Considerations . . . . . . . . . . . . . . . . . . . 29
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29
10.1. Normative References . . . . . . . . . . . . . . . . . . . 29
10.2. Informative References . . . . . . . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 30
Intellectual Property and Copyright Statements . . . . . . . . . . 32
1. Introduction 1. Introduction
This document defines a number of Diameter Quality of Service (QoS) This document defines a number of Diameter Quality of Service (QoS)
related AVPs that can be used in existing and future Diameter related AVPs that can be used in existing and future Diameter
applications where permitted by the command ABNF. The Extended-QoS- applications where permitted by the command ABNF. The Extended-QoS-
Filter-Rule AVP thereby replaces the QoSFilterRule, defined in RFC Filter-Rule AVP thereby replaces the IPFilterRule, defined in RFC
3588 [RFC3588], and the QoS-Filter-Rule, defined in RFC 4005 3588bis [I-D.ietf-dime-rfc3588bis], and the QoS-Filter-Rule, defined
[RFC4005]. in RFC 4005 [RFC4005].
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. Diameter QoS Defined AVPs 3. Diameter QoS Defined AVPs
The following table lists the Diameter AVPs used by this document,
their AVP code values, types and possible flag values.
+------------------+
| AVP Flag Rules |
+------------------------------------------------|----+---+----+----+
| AVP Section |MUST|MAY|SHLD|MUST|
| Attribute Name Code Defined Data Type | | | NOT| NOT|
+------------------------------------------------+----+---+----+----+
|QoS-Capability TBD 3.1 Grouped | | P | |M,V |
|QoS-Profile-Template TBD 3.2 Unsigned32 | | P | |M,V |
|Vendor-Specific- | | | | |
| QoS-Profile-Template TBD 3.3 Grouped | | P | |M,V |
|QoS-Resources TBD 3.4 Grouped | | P | |M,V |
|Extended-QoS-Filter-Rule TBD 3.5 Grouped | | P | |M,V |
|QoS-Semantics TBD 3.6 Enumerated | | P | |M,V |
|QoS-Parameters TBD 3.7 OctetString| | P | |M,V |
|QoS-Rule-Precedence TBD 3.8 Unsigned32 | | P | |M,V |
+------------------------------------------------+----+---+----+----+
3.1. QoS-Capability AVP 3.1. QoS-Capability AVP
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
QoS capabilities and QoS profiles supported by a peer. It may also
be used to negotiate a mutually supported set of QoS capabilities and
QoS profiles between two peers.
QoS-Capability ::= < AVP Header: XXX > QoS-Capability ::= < AVP Header: XXX >
1* { QoS-Profile-Template } * [ QoS-Profile-Template ]
* [ Vendor-Specific-QoS-Profile-Template ]
* [ AVP ] * [ AVP ]
3.2. QoS-Profile-Template AVP 3.2. QoS-Profile-Template AVP
The QoS-Profile-Template AVP (AVP Code TBD) is of type Unsigned32 and The QoS-Profile-Template 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 is described in template is defined with value of 0 and is described 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.
skipping to change at page 6, line 7 skipping to change at page 5, line 34
3.5. Extended-QoS-Filter-Rule AVP 3.5. Extended-QoS-Filter-Rule AVP
The Extended-QoS-Filter-Rule AVP (AVP Code TBD) is of type Grouped The Extended-QoS-Filter-Rule AVP (AVP Code TBD) is of type Grouped
and defines one or more traffic flows together with a set of QoS and defines one or more traffic flows together with a set of QoS
parameters that should be applied to the flow(s) by the Resource parameters that should be applied to the flow(s) by the Resource
Management Function. This AVP uses the Classifier AVP (see Management Function. This AVP uses the Classifier AVP (see
Section 5) to describe traffic flows. Section 5) to describe traffic flows.
Extended-QoS-Filter-Rule ::= < AVP Header: XXX > Extended-QoS-Filter-Rule ::= < AVP Header: XXX >
{ QoS-Semantics } { QoS-Semantics }
{ QoS-Profile-Template } [ QoS-Profile-Template ]
[ Vendor-Specific-QoS-Profile-Template ]
[ QoS-Parameters ] [ QoS-Parameters ]
[ QoS-Rule-Precedence ] [ QoS-Rule-Precedence ]
[ Classifier ] [ Classifier ]
* [ AVP ] * [ AVP ]
Either the QoS-Profile-Template or Vendor-Specific-QoS-Profile-
Template AVP MUST appear in the Extended-QoS-Filter-Rule AVP.
3.6. QoS-Semantics 3.6. 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 Extended-QoS-Filter-Rule AVP. Parameters AVPs in the Extended-QoS-Filter-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
skipping to change at page 6, line 41 skipping to change at page 6, line 27
in a separate document, see [I-D.ietf-dime-qos-parameters]. in a separate document, see [I-D.ietf-dime-qos-parameters].
3.8. QoS-Rule-Precedence AVP 3.8. QoS-Rule-Precedence AVP
The QoS-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. Rules with equal precedence MAY be executed in
parallel if supported by the Resource Management Function. If the parallel if supported by the Resource Management Function. If the
QoS-Rule-Precedence AVP is absent from the Extended-QoS-Filter-Rule QoS-Rule-Precedence AVP is absent from the Extended-QoS-Filter-Rule
AVP, the rules SHOULD be executed in the order in which they appear AVP, the rules SHOULD be executed in the order in which they appear
in the QoS-Resources AVP. in the QoS-Resources AVP. The lower the numerical value of QoS-Rule-
Precedence AVP, the higher the rule precedence.
4. Semantics of QoS Parameters 4. Semantics of QoS Parameters
The QoS parameters carried in the QoS-Resources AVP may appear in The QoS parameters carried in the QoS-Resources AVP may appear in
different messages. The semantic of the QoS parameters depend on the different messages. The semantic of the QoS parameters depend on the
information provided in the QoS-Semantics AVP which currently defines information provided in the QoS-Semantics AVP which currently defines
5 values, namely QoS-Desired (0), QoS-Available (1), QoS-Reserved 5 values, namely QoS-Desired (0), QoS-Available (1), QoS-Reserved
(2), Minimum-QoS (3), and QoS-Authorized (4). (2), Minimum-QoS (3), and QoS-Authorized (4).
The semantics of the different values are as follows: The semantics of the different values are as follows:
Object Type Direction Semantic Object Type Direction Semantic
--------------------------------------------------------------------- ---------------------------------------------------------------------
QoS-Desired C->S Please authorize the indicated QoS QoS-Desired C->S Please authorize the indicated QoS
QoS-Desired C<-S NA QoS-Desired C<-S NA
QoS-Available C->S Admission Control at router indicates QoS-Available C->S Admission Control at interface indicates
that this QoS is available. (note 1) that this QoS is available. (note 1)
QoS-Available C<-S Indicated QoS is available. (note 2) QoS-Available C<-S Indicated QoS is available. (note 2)
QoS-Reserved C->S Used for reporting during accounting. QoS-Reserved C->S Used for reporting during accounting.
QoS-Reserved C<-S NA QoS-Reserved C<-S NA
Minimum-QoS C->S Indicates that the client is not Minimum-QoS C->S Indicates that the client is not
interested in authorizing QoS that is interested in authorizing QoS that is
lower than Min. QoS. lower than Min. QoS.
Minimum-QoS C<-S The client must not provide QoS Minimum-QoS C<-S The client must not provide QoS
guarantees lower than Min. QoS. guarantees lower than Min. QoS.
QoS-Authorized C->S NA QoS-Authorized C->S NA
skipping to change at page 9, line 30 skipping to change at page 9, line 30
Options: Options:
Associated with each protocol or layer, or various values specific Associated with each protocol or layer, or various values specific
to the header of the protocol or layer. Options allow matching on to the header of the protocol or layer. Options allow matching on
those values. those values.
Each protocol type will have a specific set of attributes that can be Each protocol type will have a specific set of attributes that can be
used to specify a classifier for that protocol. These attributes used to specify a classifier for that protocol. These attributes
will be grouped under a grouped AVP called a Classifier AVP. will be grouped under a grouped AVP called a Classifier AVP.
The following table lists the Classifer AVPs used by this document,
their AVP code values, types and possible flag values.
+------------------+
| AVP Flag Rules |
+------------------------------------------------|----+---+----+----+
| AVP Section |MUST|MAY|SHLD|MUST|
| Attribute Name Code Defined Data Type | | | NOT| NOT|
+------------------------------------------------+----+---+----+----+
|Classifier TBD 5.1 Grouped | | P | |M,V |
|Classifier-ID TBD 5.2 OctetString| | P | |M,V |
|Protocol TBD 5.3 Enumerated | | P | |M,V |
|Direction TBD 5.4 Enumerated | | P | |M,V |
|From-Spec TBD 5.5 Grouped | | P | |M,V |
|To-Spec TBD 5.6 Grouped | | P | |M,V |
|Negated TBD 5.7.1 Enumerated | | P | |M,V |
|IP-Address TBD 5.7.2 Address | | P | |M,V |
|IP-Address-Range TBD 5.7.3 Grouped | | P | |M,V |
|IP-Address-Start TBD 5.7.4 Address | | P | |M,V |
|IP-Address-End TBD 5.7.5 Address | | P | |M,V |
|IP-Address-Mask TBD 5.7.6 Grouped | | P | |M,V |
|IP-Mask-Bit-Mask-Width TBD 5.7.7 OctetString| | P | |M,V |
|MAC-Address TBD 5.7.8 OctetString| | P | |M,V |
|Port TBD 5.7.9 Integer32 | | P | |M,V |
|Port-Range TBD 5.7.10 Grouped | | P | |M,V |
|Port-Start TBD 5.7.11 Integer32 | | P | |M,V |
|Port-End TBD 5.7.12 Integer32 | | P | |M,V |
|Use-Assigned-Address TBD 5.7.13 Enumerated | | P | |M,V |
|Diffserv-Code-Point TBD 5.8.1 Enumerated | | P | |M,V |
|Fragmentation-Flag TBD 5.8.2 Enumerated | | P | |M,V |
|IP-Option TBD 5.8.3 Grouped | | P | |M,V |
|IP-Option-Type TBD 5.8.4 Enumerated | | P | |M,V |
|IP-Option-Value TBD 5.8.5 OctetString| | P | |M,V |
|TCP-Option TBD 5.8.6 Grouped | | P | |M,V |
|TCP-Option-Type TBD 5.8.7 Enumerated | | P | |M,V |
|TCP-Option-Value TBD 5.8.8 OctetString| | P | |M,V |
|TCP-Flags TBD 5.8.9 Grouped | | P | |M,V |
|TCP-Flag-Type TBD 5.8.10 Enumerated | | P | |M,V |
|ICMP-Type TBD 5.8.11 Grouped | | P | |M,V |
|ICMP-Type-Number TBD 5.8.12 Enumerated | | P | |M,V |
|ICMP-Code TBD 5.8.13 Enumerated | | P | |M,V |
+------------------------------------------------+----+---+----+----+
5.1. Classifier AVP 5.1. Classifier AVP
The Classifier AVP (AVP Code TBD) is a grouped AVP that consists of a The Classifier AVP (AVP Code TBD) is a grouped AVP that consists of a
set of attributes that specify how to match a packet. set of attributes that specify how to match a packet.
Classifier ::= < AVP Header: XXX > Classifier ::= < AVP Header: XXX >
{ Classifier-ID } { Classifier-ID }
{ Protocol } { Protocol }
{ Direction } { Direction }
* [ From-Spec ] * [ From-Spec ]
* [ To-Spec ] * [ To-Spec ]
* [ Diffserv-Code-Point ] * [ Diffserv-Code-Point ]
[ Fragmentation-Flag ] [ Fragmentation-Flag ]
* [ IP-Option ] * [ IP-Option ]
* [ TCP-Option ] * [ TCP-Option ]
[ TCP-Flags ] [ TCP-Flags ]
* [ ICMP-Type ] * [ ICMP-Type ]
* [ ETH-Option ]
* [ AVP ] * [ AVP ]
5.2. Classifier-ID AVP 5.2. Classifier-ID AVP
The Classifier-ID AVP (AVP Code TBD) is of type OctetString and The Classifier-ID AVP (AVP Code TBD) is of type OctetString and
uniquely identifies the classifier. Each application will define the uniquely identifies the classifier. Each application will define the
uniqueness scope of this identifier, e.g. unique per terminal or uniqueness scope of this identifier, e.g. unique per terminal or
globally unique. Exactly one Classifier-ID AVP MUST be contained globally unique. Exactly one Classifier-ID AVP MUST be contained
within a Classifier AVP. within a Classifier AVP.
skipping to change at page 11, line 47 skipping to change at page 10, line 33
The Direction AVP (AVP Code TBD) is of type Enumerated that specifies The Direction AVP (AVP Code TBD) is of type Enumerated that specifies
in which direction to apply the Classifier. The values of the in which direction to apply the Classifier. The values of the
enumeration are: "IN","OUT","BOTH". In the "IN" and "BOTH" enumeration are: "IN","OUT","BOTH". In the "IN" and "BOTH"
directions, the From-Spec refers to the address of the Managed directions, the From-Spec refers to the address of the Managed
Terminal and the To-Spec refers to the unmanaged terminal. In the Terminal and the To-Spec refers to the unmanaged terminal. In the
"OUT" direction, the From-Spec refers to the Unmanaged Terminal "OUT" direction, the From-Spec refers to the Unmanaged Terminal
whereas the To-Spec refers to the Managed Terminal. whereas the To-Spec refers to the Managed Terminal.
Value | Name and Semantic Value | Name and Semantic
------+------------------------------------------------------------ ------+--------------------------------------------------
0 | RESERVED 0 | RESERVED
1 | IN - The classifier applies to downlink flows only. 1 | IN - The classifier applies to flows from the
2 | OUT - The classifier applies to uplink flows only. | Managed Terminal.
3 | BOTH - The classifier applies to both downlink 2 | OUT - The classifier applies to flows to the
| and uplink flows. | Managed Terminal.
3 | BOTH - The classifier applies to flows both to
| and from the Managed Terminal.
5.5. From-Spec AVP 5.5. From-Spec AVP
The From-Spec AVP (AVP Code TBD) is a grouped AVP that specifies the The From-Spec AVP (AVP Code TBD) is a grouped AVP that specifies the
Source Specification used to match the packet. Zero or more of these Source Specification used to match the packet. Zero or more of these
AVPs may appear in the Classifier. If this AVP is absent from the AVPs may appear in the Classifier. If this AVP is absent from the
Classifier then all packets are matched regardless of the source Classifier then all packets are matched regardless of the source
address. If more than one instance of this AVP appears in the address. If more than one instance of this AVP appears in the
Classifier then the source of the packet can match any From-Spec AVP. Classifier then the source of the packet can match any From-Spec AVP.
The contents of this AVP are protocol specific. The contents of this AVP are protocol specific.
If more than one instance of the IP address AVPs (IP-Address, IP- If more than one instance of the IP address AVPs (IP-Address, IP-
Address-Range, IP-Address-Mask, Use-Assigned-Address) appear in the Address-Range, IP-Address-Mask, Use-Assigned-Address) appear in the
From-Spec AVP then the source IP address of the packet must match one From-Spec AVP then the source IP address of the packet must match one
of the addresses represented by these AVPs. of the addresses represented by these AVPs.
If more that one instance of the MAC-Address AVP appears in the From- If more that one instance of the layer 2 address AVPs (MAC-Address,
Spec then the the source MAC address of the packet must match one of MAC-Address-Mask, EUI64-Address, EUI64-Address-Mask) appears in the
the addresses represented in these AVPs. From-Spec then the the source layer 2 address of the packet must
match one of the addresses represented in these AVPs.
If more that one instance of the VLAN-ID AVP appears in the From-Spec
then the VLAN-ID of the packet must match one of the VLAN-IDs
represented in these AVPs.
If more that one instance of the port AVPs (Port, Port-Range) appears If more that one instance of the port AVPs (Port, Port-Range) appears
in the From-Spec AVP then the source port number must match one of in the From-Spec AVP then the source port number must match one of
the port numbers represented in these AVPs. the port numbers represented in these AVPs.
If the IP address, MAC address and port AVPs appear in the same From- If the IP address, MAC address and port AVPs appear in the same From-
Spec AVP then the source packet must match all the specifications, Spec AVP then the source packet must match all the specifications,
i.e. match the IP address AND MAC address AND port number. i.e. match the IP address AND MAC address AND port number.
From-Spec ::= < AVP Header: XXX > From-Spec ::= < AVP Header: XXX >
* [ IP-Address ] * [ IP-Address ]
* [ IP-Address-Range ] * [ IP-Address-Range ]
* [ IP-Address-Mask ] * [ IP-Address-Mask ]
* [ MAC-Address ] * [ MAC-Address ]
* [ MAC-Address-Mask]
* [ EUI64-Address ]
* [ EUI64-Address-Mask]
* [ VLAN-ID ]
* [ Port ] * [ Port ]
* [ Port-Range ] * [ Port-Range ]
[ Negated ] [ Negated ]
[ Use-Assigned-Address ] [ Use-Assigned-Address ]
* [ AVP ] * [ AVP ]
5.6. To-Spec AVP 5.6. To-Spec AVP
The To-Spec AVP (AVP Code TBD) is a grouped AVP that specifies the The To-Spec AVP (AVP Code TBD) is a grouped AVP that specifies the
Destination Specification used to match the packet. Zero or more of Destination Specification used to match the packet. Zero or more of
skipping to change at page 13, line 12 skipping to change at page 12, line 10
the Classifier then all packets are matched regardless of the the Classifier then all packets are matched regardless of the
destination address. If more than one instance of this AVP appears destination address. If more than one instance of this AVP appears
in the Classifier then the destination of the packet can match any in the Classifier then the destination of the packet can match any
To-Spec AVP. The contents of this AVP are protocol specific. To-Spec AVP. The contents of this AVP are protocol specific.
If more than one instance of the IP address AVPs (IP-Address, IP- If more than one instance of the IP address AVPs (IP-Address, IP-
Address-Range, IP-Address-Mask, Use-Assigned-Address) appear in the Address-Range, IP-Address-Mask, Use-Assigned-Address) appear in the
To-Spec AVP then the destination IP address of the packet must match To-Spec AVP then the destination IP address of the packet must match
one of the addresses represented by these AVPs. one of the addresses represented by these AVPs.
If more that one instance of the MAC-Address AVP appears in the To- If more that one instance of the layer 2 address AVPs (MAC-Address,
Spec then the the destination MAC address of the packet must match MAC-Address-Mask, EUI64-Address, EUI64-Address-Mask) appears in the
one of the addresses represented in these AVPs. To-Spec then the the destination layer 2 address of the packet must
match one of the addresses represented in these AVPs.
If more that one instance of the VLAN-ID AVP appears in the From-Spec
then the VLAN-ID of the packet must match one of the VLAN-IDs
represented in these AVPs.
If more that one instance of the port AVPs (Port, Port-Range) appears If more that one instance of the port AVPs (Port, Port-Range) appears
in the To-Spec AVP then the destination port number must match one of in the To-Spec AVP then the destination port number must match one of
the port numbers represented in these AVPs. the port numbers represented in these AVPs.
If the IP address, MAC address and port AVPs appear in the same To- If the IP address, MAC address and port AVPs appear in the same To-
Spec AVP then the destination packet must match all the Spec AVP then the destination packet must match all the
specifications, i.e. match the IP address AND MAC address AND port specifications, i.e. match the IP address AND MAC address AND port
number. number.
To-Spec ::= < AVP Header: XXX > To-Spec ::= < AVP Header: XXX >
* [ IP-Address ] * [ IP-Address ]
* [ IP-Address-Range ] * [ IP-Address-Range ]
* [ IP-Address-Mask ] * [ IP-Address-Mask ]
* [ MAC-Address ] * [ MAC-Address ]
* [ MAC-Address-Mask]
* [ EUI64-Address ]
* [ EUI64-Address-Mask]
* [ VLAN-ID ]
* [ Port ] * [ Port ]
* [ Port-Range ] * [ Port-Range ]
[ Negated ] [ Negated ]
[ Use-Assigned-Address ] [ Use-Assigned-Address ]
* [ AVP ] * [ AVP ]
5.7. Source and Destination AVPs 5.7. Source and Destination AVPs
For packet classification the contents of the From-Spec and To-Spec For packet classification the contents of the From-Spec and To-Spec
can contain the following AVPs. can contain the following AVPs.
skipping to change at page 15, line 33 skipping to change at page 14, line 39
5.7.7. IP-Mask-Bit-Mask-Width AVP 5.7.7. IP-Mask-Bit-Mask-Width AVP
The IP-Bit-Mask-Width AVP (AVP Code TBD) is of type OctetString. The The IP-Bit-Mask-Width AVP (AVP Code TBD) is of type OctetString. The
value is a single octet and specifies the width of an IP address bit- value is a single octet and specifies the width of an IP address bit-
mask. mask.
5.7.8. MAC-Address AVP 5.7.8. MAC-Address AVP
The MAC-Address AVP (AVP Code TBD) is of type OctetString and The MAC-Address AVP (AVP Code TBD) is of type OctetString and
specifies a single MAC address. The value is a 6 octets encoding of specifies a single layer 2 address in MAC-48 format. The value is a
the MAC address as it would appear in the frame header. 6 octets encoding of the address as it would appear in the frame
header.
5.7.9. Port AVP 5.7.9. MAC-Address-Mask AVP
The MAC-Address-Mask AVP (AVP Code TBD) is of type Grouped and
specifies a set of MAC addresses using a bit mask to indicate the
bits of the MAC addresses which must fit to the specified MAC address
attribute. For example, a MAC-Address-Mask with the MAC-Address as
00-10-A4-23-00-00 and with a MAC-Address-Mask-Pattern of FF-FF-FF-FF-
00-00 will match all MAC addresses from 00-10-A4-23-00-00 up to and
including 00-10-A4-23-FF-FF.
MAC-Address-Mask ::= < AVP Header: XXX >
{ MAC-Address }
{ MAC-Address-Mask-Pattern }
* [ AVP ]
5.7.10. MAC-Address-Mask-Pattern AVP
The MAC-Address-Mask-Pattern AVP (AVP Code TBD) is of type
OctetString. The value is a 6 octets specifying the bit positions of
a MAC address, that are taken for matching.
5.7.11. EUI64-Address AVP
The EUI64-Address AVP (AVP Code TBD) is of type OctetString and
specifies a single layer 2 address in EUI-64 format. The value is a
8 octets encoding of the address as it would appear in the frame
header.
5.7.12. EUI64-Address-Mask AVP
The EUI64-Address-Mask AVP (AVP Code TBD) is of type Grouped and
specifies a set of EUI64 addresses using a bit mask to indicate the
bits of the EUI64 addresses which must fit to the specified EUI64
address attribute. For example, a EUI64-Address-Mask with the EUI64-
Address as 00-10-A4-FF-FE-23-00-00 and with a EUI64-Address-Mask-
Pattern of FF-FF-FF-FF-FF-FF-00-00 will match all EUI64 addresses
from 00-10-A4-FF-FE-23-00-00 up to and including 00-10-A4-FF-FE-23-
FF-FF.
EUI64-Address-Mask ::= < AVP Header: XXX >
{ EUI64-Address }
{ EUI64-Address-Mask-Pattern }
* [ AVP ]
5.7.13. EUI64-Address-Mask-Pattern AVP
The EUI64-Address-Mask-Pattern AVP (AVP Code TBD) is of type
OctetString. The value is a 8 octets specifying the bit positions of
a EUI64 address, that are taken for matching.
5.7.14. VLAN-ID AVP
VLAN-ID AVP (AVP Code TBD) is of type OctetString. The value is a
double octet encoded in Network Byte Order. The value of this field
specifies the matching value for the IEEE 802.1Q VLAN-ID bits. Only
the lower (i.e., rightmost) 12 bits of the specified 2 octet VLAN-ID
field are significant; the upper four bits shall be ignored for
comparison. If this field is omitted, then comparison of the IEEE
802.1Q VLAN-ID bits for this entry is irrelevant. If this parameter
is specified for an entry, then Ethernet packets without IEEE 802.1Q
encapsulation shall not match this entry.
5.7.15. Port AVP
The Port AVP (AVP Code TBD) is of type Integer32 in the range of 0 to The Port AVP (AVP Code TBD) is of type Integer32 in the range of 0 to
65535 and specifies the TCP or UDP port number to match. 65535 and specifies the TCP or UDP port number to match.
5.7.10. Port-Range AVP 5.7.16. Port-Range AVP
The Port-Range AVP (AVP Code TBD) is of type Grouped and specifies an The Port-Range AVP (AVP Code TBD) is of type Grouped and specifies an
inclusive range of ports. inclusive range of ports.
Port-Range ::= < AVP Header: XXX > Port-Range ::= < AVP Header: XXX >
[ Port-Start ] [ Port-Start ]
[ Port-End ] [ Port-End ]
* [ AVP ] * [ AVP ]
If the Port-Start AVP is omitted then port 0 is assumed. If the If the Port-Start AVP is omitted then port 0 is assumed. If the
Port-End AVP is omitted then port 65535 is assumed. Port-End AVP is omitted then port 65535 is assumed.
5.7.11. Port-Start AVP 5.7.17. Port-Start AVP
The Port-Start AVP (AVP Code TBD) is of type Integer32 and specifies The Port-Start AVP (AVP Code TBD) is of type Integer32 and specifies
the first port number of an IP port range. the first port number of an IP port range.
5.7.12. Port-End AVP 5.7.18. Port-End AVP
The Port-End AVP (AVP Code TBD) is of type Integer32 and specifies The Port-End AVP (AVP Code TBD) is of type Integer32 and specifies
the last port number of an IP port range. the last port number of an IP port range.
5.7.13. Use-Assigned-Address AVP 5.7.19. Use-Assigned-Address AVP
In some scenarios, the AAA does not know the IP address assigned to In some scenarios, the AAA does not know the IP address assigned to
the Managed Terminal at the time that the Classifier is sent to the the Managed Terminal at the time that the Classifier is sent to the
Classifying Entity. The Use-Assigned-Address AVP (AVP Code TBD) is Classifying Entity. The Use-Assigned-Address AVP (AVP Code TBD) is
of type Enumerated containing the values of True or False. When of type Enumerated containing the values of True or False. When
present and set to True, it represents the IP address assigned to the present and set to True, it represents the IP address assigned to the
Managed Terminal. Managed Terminal.
Value | Name Value | Name
------+-------- ------+--------
skipping to change at page 18, line 38 skipping to change at page 19, line 6
The TCP-Option-Value AVP (AVP Code TBD) is of type OctetString and The TCP-Option-Value AVP (AVP Code TBD) is of type OctetString and
contains the option value that must be matched. contains the option value that must be matched.
5.8.9. TCP-Flags AVP 5.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 >
* [ TCP-Flag-Type ] 1* { TCP-Flag-Type }
[ Negated ] [ Negated ]
* [ AVP ] * [ AVP ]
If the Negated AVP is not present, the TCP-Flag-Type AVPs specifies If the Negated AVP is not present, the TCP-Flag-Type AVPs specifies
which flags MUST be set. If the Negated AVP is present, the TCP- which flags MUST be set. If the Negated AVP is present, the TCP-
Flag-Type AVPs specifies which flags MUST be cleared. Flag-Type AVPs specifies which flags MUST be cleared.
5.8.10. TCP-Flag-Type AVP 5.8.10. TCP-Flag-Type AVP
The TCP-Flag-Type AVP (AVP Code TBD) is of type Enumerated and The TCP-Flag-Type AVP (AVP Code TBD) is of type Enumerated and
skipping to change at page 19, line 48 skipping to change at page 20, line 16
The ICMP-Type-Number AVP (AVP Code TBD) is of type Enumerated and the The ICMP-Type-Number AVP (AVP Code TBD) is of type Enumerated and the
values are managed by IANA under the ICMP Type Numbers registry values are managed by IANA under the ICMP Type Numbers registry
[ICMPTYPE]. [ICMPTYPE].
5.8.13. ICMP-Code AVP 5.8.13. ICMP-Code AVP
The ICMP-Code AVP (AVP Code TBD) is of type Enumerated and the values The ICMP-Code AVP (AVP Code TBD) is of type Enumerated and the values
are managed by IANA under the ICMP Type Numbers registry [ICMPTYPE]. are managed by IANA under the ICMP Type Numbers registry [ICMPTYPE].
5.8.14. ETH-Option AVP
The ETH-Option AVP (AVP Code TBD) is of type Grouped and specifies
Ethernet specific classifiers.
ETH-Option ::= < AVP Header: XXX >
{ ETH-Proto-Type }
* [ ETH-VLAN-ID ]
* [ ETH-Priority-Range ]
* [ AVP ]
5.8.15. ETH-Proto-Type AVP
The Eth-Proto-Type AVP (AVP Code TBD) is of type Grouped and
specifies the encapsulated protocol type. ETH-Ether-Type and ETH-SAP
are mutually exclusive.
ETH-Proto-Type ::= < AVP Header: XXX >
* [ ETH-Ether-Type ]
* [ ETH-SAP ]
* [ AVP ]
5.8.16. ETH-Ether-Type AVP
The ETH-Ether-Type AVP (AVP Code TBD) is of type OctetString. The
value is a double octet the contains the value of the Ethertype that
the packet shall match in order to match the rule. It might be
present in case of DIX or if SNAP is present at 802.2 (SAP shall not
be present in this case).
5.8.17. ETH-SAP AVP
The ETH-SAP AVP (AVP Code TBD) is of type OctetString. The value is
a double octet representing the 802.2 SAP as specified in "IEEE
Standards for Local Area Networks: Logical Link Control". The first
octet contains the DSAP and the second the SSAP.
5.8.18. ETH-Priority-Range AVP
The ETH-Priority-Range AVP (AVP Code TBD) is of type Grouped and
specifies a valid priority range in between the Low-priority AVP to
the High-priority AVP specified. An Ethernet packet with IEEE 802.1D
user_priority value "priority" matches these parameters if priority
is greater than or equal to pri-low and priority is less than or
equal to pri-high. If this field is omitted, then comparison of the
IEEE 802.1D user_priority bits for this entry is irrelevant.
ETH-Priority-Range ::= < AVP Header: XXX >
* [ ETH-Low-Priority ]
* [ ETH-High-Priority ]
* [ AVP ]
5.8.19. ETH-Low-Priority AVP
The ETH-Low-Priority AVP (AVP Code TBD) is of type OctetString. The
value is a single octet with a valid range from 0 to 7.
5.8.20. ETH-High-Priority AVP
The ETH-High-Priority AVP (AVP Code TBD) is of type OctetString. The
value is a single octet with a valid range from 0 to 7.
6. Examples 6. Examples
This section shows a number of signaling flows where QoS negotiation This section shows a number of signaling flows where QoS negotiation
and authorization is part of the conventional NASREQ, EAP or Credit and authorization is part of the conventional NASREQ, EAP or Credit
Control applications message exchanges. The signalling flows for the Control applications message exchanges. The signalling flows for the
Diameter QoS Application are described in Diameter QoS Application are described in
[I-D.ietf-dime-diameter-qos]. [I-D.ietf-dime-diameter-qos].
6.1. Diameter EAP with QoS Information 6.1. Diameter EAP with QoS Information
skipping to change at page 25, line 26 skipping to change at page 26, line 26
|<--------------------| | | |<--------------------| | |
|(5) Begin service | | | |(5) Begin service | | |
|<------------------------------------>| | |<------------------------------------>| |
| | | | | | | |
. . . . . . . .
. . . . . . . .
Figure 6: Example for a One-Time Diameter Credit Control Charging Figure 6: Example for a One-Time Diameter Credit Control Charging
Event Event
6.6. Classifier mapping from IPFilterRule type 6.6. Classifier Examples
6.7. Complex Classifier Example: Classify all packets from hosts on subnet 12.34.56.00/24 to
ports 80, 8090 or 443 on web servers 23.45.67.123, 23.45.68.124,
23.45.69.125.
Classifer = {
Classifier-Id = "web_svr_example";
Protocol = TCP;
Direction = OUT;
From-Spec = {
IP-Address-Mask = {
IP-Address = 12.34.56.00;
IP-Bit-Mask-Width = 24;
}
}
To-Spec = {
IP-Address = 23.45.67.123;
IP-Address = 23.45.68.124;
IP-Address = 23.45.69.125;
Port = 80;
Port = 8080;
Port = 443;
}
}
Example: Any SIP signalling traffic from a device with a MAC address
of 01:23:45:67:89:ab to servers with IP addresses in the range
34.56.78.90 to 34.56.78.190.
Classifer = {
Classifier-Id = "web_svr_example";
Protocol = UDP;
Direction = OUT;
From-Spec = {
MAC-Address = 01:23:45:67:89:ab;
}
To-Spec = {
IP-Address-Range = {
IP-Address-Start = 34.56.78.90;
IP-Address-End = 34.56.78.190;
}
Port = 5060;
Port = 3478;
Port-Range = {
Port-Start = 16348;
Port-End = 32768;
}
}
}
7. Acknowledgments 7. 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 and Elwyn Davies for their Pete McCann, Georgios Karagiannis and Elwyn Davies for their
comments. comments.
8. IANA Considerations 8. IANA Considerations
This specification requests IANA to assignment of new AVPs from the IANA is requested to allocate AVP codes for the following AVPs that
AVP Code namespace defined in RFC 3588 [RFC3588]. Section 3 and are defined in this document.
Section 5 list the newly defined AVPs.
IANA is requested to allocate a registry for the QoS-Semantics. The +------------------------------------------------------------------+
following values are allocated by this specification. | AVP Section |
| Attribute Name Code Defined Data Type |
+------------------------------------------------------------------+
|QoS-Capability TBD 3.1 Grouped |
|QoS-Profile-Template TBD 3.2 Unsigned32 |
|Vendor-Specific-QoS-Profile-Template TBD 3.3 Grouped |
|Extended-QoS-Filter-Rule TBD 3.5 Grouped |
|QoS-Semantics TBD 3.6 Enumerated |
|QoS-Parameters TBD 3.7 OctetString |
|QoS-Rule-Precedence TBD 3.8 Unsigned32 |
|Classifier TBD 5.1 Grouped |
|Classifier-ID TBD 5.2 OctetString |
|Protocol TBD 5.3 Enumerated |
|Direction TBD 5.4 Enumerated |
|From-Spec TBD 5.5 Grouped |
|To-Spec TBD 5.6 Grouped |
|Negated TBD 5.7.1 Enumerated |
|IP-Address TBD 5.7.2 Address |
|IP-Address-Range TBD 5.7.3 Grouped |
|IP-Address-Start TBD 5.7.4 Address |
|IP-Address-End TBD 5.7.5 Address |
|IP-Address-Mask TBD 5.7.6 Grouped |
|IP-Mask-Bit-Mask-Width TBD 5.7.7 OctetString |
|MAC-Address TBD 5.7.8 OctetString |
|MAC-Address-Mask TBD 5.7.9 Grouped |
|MAC-Address-Mask-Pattern TBD 5.7.10 OctetString |
|EUI64-Address TBD 5.7.11 OctetString |
|EUI64-Address-Mask TBD 5.7.12 Grouped |
|EUI64-Address-Mask-Pattern TBD 5.7.13 OctetString |
|VLAN-ID TBD 5.7.14 OctetString |
|Port TBD 5.7.15 Integer32 |
|Port-Range TBD 5.7.16 Grouped |
|Port-Start TBD 5.7.17 Integer32 |
|Port-End TBD 5.7.18 Integer32 |
|Use-Assigned-Address TBD 5.7.19 Enumerated |
|Diffserv-Code-Point TBD 5.8.1 Enumerated |
|Fragmentation-Flag TBD 5.8.2 Enumerated |
|IP-Option TBD 5.8.3 Grouped |
|IP-Option-Type TBD 5.8.4 Enumerated |
|IP-Option-Value TBD 5.8.5 OctetString |
|TCP-Option TBD 5.8.6 Grouped |
|TCP-Option-Type TBD 5.8.7 Enumerated |
|TCP-Option-Value TBD 5.8.8 OctetString |
|TCP-Flags TBD 5.8.9 Grouped |
|TCP-Flag-Type TBD 5.8.10 Enumerated |
|ICMP-Type TBD 5.8.11 Grouped |
|ICMP-Type-Number TBD 5.8.12 Enumerated |
|ICMP-Code TBD 5.8.13 Enumerated |
|ETH-Option TBD 5.8.14 Grouped |
|ETH-Proto-Type TBD 5.8.15 Grouped |
|ETH-Ether-Type TBD 5.8.16 OctetString |
|ETH-SAP TBD 5.8.17 OctetString |
|ETH-Priority-Range TBD 5.8.18 Grouped |
|ETH-Low-Priority TBD 5.8.19 OctetString |
|ETH-High-Priority TBD 5.8.20 OctetString |
+------------------------------------------------------------------+
IANA is also requested to allocate a registry for the QoS-Semantics.
The following values are allocated by this specification.
(0): QoS-Desired (0): QoS-Desired
(1): QoS-Available (1): QoS-Available
(2): QoS-Reserved (2): QoS-Reserved
(3): Minimum-QoS (3): Minimum-QoS
(4): QoS-Authorized (4): QoS-Authorized
A specification is required to add a new value to the registry. A A specification is required to add a new value to the registry. A
standards track document is required to depreciate, delete, or modify standards track document is required to depreciate, delete, or modify
existing values. existing values.
9. Security Considerations 9. 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 3588bis
Use of the AVPs defined in this document MUST take into consideration [I-D.ietf-dime-rfc3588bis]. Use of the AVPs defined in this document
the security issues and requirements of the Diameter Base protocol. MUST take into consideration the security issues and requirements of
the Diameter Base protocol.
10. References 10. References
10.1. Normative References 10.1. Normative References
[DSCP] IANA,, "Differentiated Services Field Codepoints", [DSCP] IANA,, "Differentiated Services Field Codepoints",
http://www.iana.org/assignments/dscp-registry. http://www.iana.org/assignments/dscp-registry.
[I-D.ietf-dime-qos-parameters] [I-D.ietf-dime-qos-parameters]
Korhonen, J. and H. Tschofenig, "Quality of Service Korhonen, J. and H. Tschofenig, "Quality of Service
Parameters for Usage with the AAA Framework", Parameters for Usage with the AAA Framework",
draft-ietf-dime-qos-parameters-03 (work in progress), draft-ietf-dime-qos-parameters-06 (work in progress),
February 2008. May 2008.
[I-D.ietf-dime-rfc3588bis]
Fajardo, V., Arkko, J., Loughney, J., and G. Zorn,
"Diameter Base Protocol", draft-ietf-dime-rfc3588bis-10
(work in progress), January 2008.
[ICMPTYPE] [ICMPTYPE]
IANA,, "ICMP Type Numbers", IANA,, "ICMP Type Numbers",
http://www.iana.org/assignments/icmp-parameters. http://www.iana.org/assignments/icmp-parameters.
[IPOPTIONS] [IPOPTIONS]
IANA,, "IP Option Numbers", IANA,, "IP Option Numbers",
http://www.iana.org/assignments/ip-parameters. http://www.iana.org/assignments/ip-parameters.
[PROTOCOL] [PROTOCOL]
IANA,, "Protocol Types", IANA,, "Protocol Types",
http://www.iana.org/assignments/protocol-numbers. http://www.iana.org/assignments/protocol-numbers.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[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.
[TCPOPTIONS] [TCPOPTIONS]
IANA,, "TCP Option Numbers", IANA,, "TCP Option Numbers",
http://www.iana.org/assignments/tcp-parameters. http://www.iana.org/assignments/tcp-parameters.
10.2. Informative References 10.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-05 (work in progress), draft-ietf-dime-diameter-qos-05 (work in progress),
February 2008. February 2008.
Authors' Addresses Authors' Addresses
Jouni Korhonen (editor) Jouni Korhonen
TeliaSonera TeliaSonera
Teollisuuskatu 13 Teollisuuskatu 13
Sonera FIN-00051 Sonera FIN-00051
Finland Finland
Email: jouni.korhonen@teliasonera.com Email: jouni.korhonen@teliasonera.com
Hannes Tschofenig Hannes Tschofenig
Nokia Siemens Networks Nokia Siemens Networks
Linnoitustie 6 Linnoitustie 6
Espoo 02600 Espoo 02600
Finland Finland
Phone: +358 (50) 4871445 Phone: +358 (50) 4871445
Email: Hannes.Tschofenig@gmx.net Email: Hannes.Tschofenig@gmx.net
URI: http://www.tschofenig.priv.at URI: http://www.tschofenig.priv.at
skipping to change at page 28, line 4 skipping to change at page 31, line 18
Finland Finland
Phone: +358 (50) 4871445 Phone: +358 (50) 4871445
Email: Hannes.Tschofenig@gmx.net Email: Hannes.Tschofenig@gmx.net
URI: http://www.tschofenig.priv.at URI: http://www.tschofenig.priv.at
Mayutan Arumaithurai Mayutan Arumaithurai
University of Goettingen University of Goettingen
Email: mayutan.arumaithurai@gmail.com Email: mayutan.arumaithurai@gmail.com
Mark Jones
Mark Jones (editor)
Bridgewater Systems Bridgewater Systems
303 Terry Fox Drive 303 Terry Fox Drive
Ottawa, Ontario K2K 3J1 Ottawa, Ontario K2K 3J1
Canada Canada
Email: mark.jones@bridgewatersystems.com Email: mark.jones@bridgewatersystems.com
Avi Lior Avi Lior
Bridgewater Systems Bridgewater Systems
303 Terry Fox Drive, Suite 500 303 Terry Fox Drive, Suite 500
 End of changes. 50 change blocks. 
160 lines changed or deleted 373 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/