draft-ietf-dime-qos-attributes-10.txt   draft-ietf-dime-qos-attributes-11.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: July 26, 2009 University of Goettingen Expires: August 27, 2009 University of Goettingen
M. Jones, Ed. M. Jones, Ed.
A. Lior A. Lior
Bridgewater Systems Bridgewater Systems
January 22, 2009 February 23, 2009
Quality of Service Attributes for Diameter Quality of Service Attributes for Diameter
draft-ietf-dime-qos-attributes-10.txt draft-ietf-dime-qos-attributes-11.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.
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.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 July 26, 2009. This Internet-Draft will expire on August 27, 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights 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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Rule Sets and Rules . . . . . . . . . . . . . . . . . . . . . 4 3. Rule Sets and Rules . . . . . . . . . . . . . . . . . . . . . 5
3.1. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 4 3.1. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 5
3.2. Rule AVP . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.2. Rule AVP . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3. Rule-Precedence AVP . . . . . . . . . . . . . . . . . . . 5 3.3. Rule-Precedence AVP . . . . . . . . . . . . . . . . . . . 6
4. Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.1. Traffic Classifiers . . . . . . . . . . . . . . . . . . . 6 4.1. Traffic Classifiers . . . . . . . . . . . . . . . . . . . 7
4.1.1. Classifier AVP . . . . . . . . . . . . . . . . . . . . 8 4.1.1. Classifier AVP . . . . . . . . . . . . . . . . . . . . 9
4.1.2. Classifier-ID AVP . . . . . . . . . . . . . . . . . . 9 4.1.2. Classifier-ID AVP . . . . . . . . . . . . . . . . . . 10
4.1.3. Protocol AVP . . . . . . . . . . . . . . . . . . . . . 9 4.1.3. Protocol AVP . . . . . . . . . . . . . . . . . . . . . 10
4.1.4. Direction AVP . . . . . . . . . . . . . . . . . . . . 9 4.1.4. Direction AVP . . . . . . . . . . . . . . . . . . . . 10
4.1.5. From-Spec AVP . . . . . . . . . . . . . . . . . . . . 9 4.1.5. From-Spec AVP . . . . . . . . . . . . . . . . . . . . 10
4.1.6. To-Spec AVP . . . . . . . . . . . . . . . . . . . . . 10 4.1.6. To-Spec AVP . . . . . . . . . . . . . . . . . . . . . 11
4.1.7. Source and Destination AVPs . . . . . . . . . . . . . 11 4.1.7. Source and Destination AVPs . . . . . . . . . . . . . 12
4.1.8. Header Option AVPs . . . . . . . . . . . . . . . . . . 15 4.1.8. Header Option AVPs . . . . . . . . . . . . . . . . . . 16
4.2. Time Of Day AVPs . . . . . . . . . . . . . . . . . . . . . 21 4.2. Time Of Day AVPs . . . . . . . . . . . . . . . . . . . . . 23
4.2.1. Time-Of-Day-Condition AVP . . . . . . . . . . . . . . 22 4.2.1. Time-Of-Day-Condition AVP . . . . . . . . . . . . . . 23
4.2.2. Time-Of-Day-Start AVP . . . . . . . . . . . . . . . . 22 4.2.2. Time-Of-Day-Start AVP . . . . . . . . . . . . . . . . 24
4.2.3. Time-Of-Day-End AVP . . . . . . . . . . . . . . . . . 22 4.2.3. Time-Of-Day-End AVP . . . . . . . . . . . . . . . . . 24
4.2.4. Day-Of-Week-Mask AVP . . . . . . . . . . . . . . . . . 22 4.2.4. Day-Of-Week-Mask AVP . . . . . . . . . . . . . . . . . 24
4.2.5. Day-Of-Month-Mask AVP . . . . . . . . . . . . . . . . 23 4.2.5. Day-Of-Month-Mask AVP . . . . . . . . . . . . . . . . 25
4.2.6. Month-Of-Year-Mask AVP . . . . . . . . . . . . . . . . 23 4.2.6. Month-Of-Year-Mask AVP . . . . . . . . . . . . . . . . 25
4.2.7. Absolute-Start-Time AVP . . . . . . . . . . . . . . . 24 4.2.7. Absolute-Start-Time AVP . . . . . . . . . . . . . . . 25
4.2.8. Absolute-End-Time AVP . . . . . . . . . . . . . . . . 24 4.2.8. Absolute-End-Time AVP . . . . . . . . . . . . . . . . 26
4.2.9. Timezone-Flag AVP . . . . . . . . . . . . . . . . . . 24 4.2.9. Timezone-Flag AVP . . . . . . . . . . . . . . . . . . 26
4.2.10. Timezone-Offset AVP . . . . . . . . . . . . . . . . . 24 4.2.10. Timezone-Offset AVP . . . . . . . . . . . . . . . . . 26
5. Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 5. Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.1. Action AVP . . . . . . . . . . . . . . . . . . . . . . . . 25 5.1. Action AVP . . . . . . . . . . . . . . . . . . . . . . . . 26
5.2. QoS-Profile-Id AVP . . . . . . . . . . . . . . . . . . . . 26 5.2. QoS-Profile-Id AVP . . . . . . . . . . . . . . . . . . . . 27
5.3. QoS-Profile-Template AVP . . . . . . . . . . . . . . . . . 26 5.3. QoS-Profile-Template AVP . . . . . . . . . . . . . . . . . 28
5.4. QoS-Semantics . . . . . . . . . . . . . . . . . . . . . . 26 5.4. QoS-Semantics . . . . . . . . . . . . . . . . . . . . . . 28
5.5. QoS-Parameters AVP . . . . . . . . . . . . . . . . . . . . 27 5.5. QoS-Parameters AVP . . . . . . . . . . . . . . . . . . . . 29
5.6. Excess-Treatment AVP . . . . . . . . . . . . . . . . . . . 27 5.6. Excess-Treatment AVP . . . . . . . . . . . . . . . . . . . 29
5.7. Excess-Treatment-Action . . . . . . . . . . . . . . . . . 28 5.7. Excess-Treatment-Action . . . . . . . . . . . . . . . . . 30
6. QoS Capability Indication . . . . . . . . . . . . . . . . . . 29 6. QoS Capability Indication . . . . . . . . . . . . . . . . . . 31
7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.1. Diameter EAP with QoS Information . . . . . . . . . . . . 29 7.1. Diameter EAP with QoS Information . . . . . . . . . . . . 31
7.2. Diameter NASREQ with QoS Information . . . . . . . . . . . 30 7.2. Diameter NASREQ with QoS Information . . . . . . . . . . . 32
7.3. QoS Authorization . . . . . . . . . . . . . . . . . . . . 31 7.3. QoS Authorization . . . . . . . . . . . . . . . . . . . . 33
7.4. Diameter Server Initiated Re-authorization of QoS . . . . 32 7.4. Diameter Server Initiated Re-authorization of QoS . . . . 34
7.5. Diameter Credit Control with QoS Information . . . . . . . 33 7.5. Diameter Credit Control with QoS Information . . . . . . . 35
7.6. Classifier Examples . . . . . . . . . . . . . . . . . . . 34 7.6. Classifier Examples . . . . . . . . . . . . . . . . . . . 36
7.7. QoS Examples . . . . . . . . . . . . . . . . . . . . . . . 35 7.7. QoS Examples . . . . . . . . . . . . . . . . . . . . . . . 37
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 36 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 38
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 36 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 38
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38
11. Security Considerations . . . . . . . . . . . . . . . . . . . 39 11. Security Considerations . . . . . . . . . . . . . . . . . . . 41
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 39 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 41
12.1. Normative References . . . . . . . . . . . . . . . . . . . 39 12.1. Normative References . . . . . . . . . . . . . . . . . . . 41
12.2. Informative References . . . . . . . . . . . . . . . . . . 40 12.2. Informative References . . . . . . . . . . . . . . . . . . 42
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 40 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
skipping to change at page 9, line 22 skipping to change at page 10, line 22
4.1.3. Protocol AVP 4.1.3. Protocol AVP
The Protocol AVP (AVP Code TBD) is of type Enumerated and specifies The Protocol AVP (AVP Code TBD) is of type Enumerated and specifies
the protocol being matched. The attributes included in the the protocol being matched. The attributes included in the
Classifier AVP MUST be consistent with the value of the Protocol AVP. Classifier AVP MUST be consistent with the value of the Protocol AVP.
Exactly zero or one Protocol AVP may be contained within a Classifier Exactly zero or one Protocol AVP may be contained within a Classifier
AVP. If the Protocol AVP is omitted from the Classifier, then AVP. If the Protocol AVP is omitted from the Classifier, then
comparison of the protocol of the packet is irrelevant. The values comparison of the protocol of the packet is irrelevant. The values
for this AVP are managed by IANA under the Protocol Numbers registry for this AVP are managed by IANA under the Protocol Numbers registry
[PROTOCOL]. as defined in [RFC2780].
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
skipping to change at page 13, line 15 skipping to change at page 14, line 15
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
range. range.
4.1.7.6. IP-Address-Mask AVP 4.1.7.6. IP-Address-Mask AVP
The IP-Address-Mask AVP (AVP Code TBD) is of type Grouped and The IP-Address-Mask AVP (AVP Code TBD) is of type Grouped and
specifies an IP address range using a base IP address and the bit- specifies an IP address range using a base IP address and the bit-
width of the mask. For example, a range expressed as 1.2.3.0/24 will width of the mask. For example, a range expressed as 192.0.2.0/24
match all IP addresses from 1.2.3.0 up to and including 1.2.3.255. will match all IP addresses from 192.0.2.0 up to and including
The bit-width MUST be valid for the type of IP address. 192.0.2.255. The bit-width MUST be valid for the type of IP address.
IP-Address-Mask ::= < AVP Header: XXX > IP-Address-Mask ::= < AVP Header: XXX >
{ IP-Address } { IP-Address }
{ IP-Bit-Mask-Width } { IP-Bit-Mask-Width }
* [ AVP ] * [ AVP ]
4.1.7.7. IP-Mask-Bit-Mask-Width AVP 4.1.7.7. IP-Mask-Bit-Mask-Width AVP
The IP-Bit-Mask-Width AVP (AVP Code TBD) is of type Unsigned32. The The IP-Bit-Mask-Width AVP (AVP Code TBD) is of type Unsigned32. The
value specifies the width of an IP address bit-mask. value specifies the width of an IP address bit-mask.
skipping to change at page 15, line 50 skipping to change at page 16, line 50
4.1.8. Header Option AVPs 4.1.8. Header Option AVPs
The Classifier AVP may contain one or more of the following AVPs to The Classifier AVP may contain one or more of the following AVPs to
match on the various possible IP, TCP or ICMP header options. match on the various possible IP, TCP or ICMP header options.
4.1.8.1. Diffserv-Code-Point AVP 4.1.8.1. Diffserv-Code-Point AVP
The Diffserv-Code-Point AVP (AVP Code TBD) is of type Enumerated and The Diffserv-Code-Point AVP (AVP Code TBD) is of type Enumerated and
specifies the Differentiated Services Field Codepoints to match in specifies the Differentiated Services Field Codepoints to match in
the IP header. The values are managed by IANA under the the IP header. The values are managed by IANA under the
Differentiated Services Field Codepoints registry [DSCP]. Differentiated Services Field Codepoints registry as defined in
[RFC2474].
4.1.8.2. Fragmentation-Flag AVP 4.1.8.2. Fragmentation-Flag AVP
The Fragmentation-Flag AVP (AVP Code TBD) is of type Enumerated and The Fragmentation-Flag AVP (AVP Code TBD) is of type Enumerated and
specifies the packet fragmentation flags to match in the IP header. specifies the packet fragmentation flags to match in the IP header.
Value | Name and Semantic Value | Name and Semantic
------+------------------------------------------------------------ ------+------------------------------------------------------------
0 | Don't Fragment (DF) 0 | Don't Fragment (DF)
1 | More Fragments (MF) 1 | More Fragments (MF)
skipping to change at page 16, line 39 skipping to change at page 17, line 39
the value is wild carded. the value is wild carded.
The Negated AVP is used in conjunction with the IP-Option-Value AVPs The Negated AVP is used in conjunction with the IP-Option-Value AVPs
to specify IP header options which do not match specific values. The to specify IP header options which do not match specific values. The
Negated AVP is used without the IP-Option-Value AVP to specify IP Negated AVP is used without the IP-Option-Value AVP to specify IP
headers which do not contain the option type. headers which do not contain the option type.
4.1.8.4. IP-Option-Type AVP 4.1.8.4. IP-Option-Type AVP
The IP-Option-Type AVP (AVP Code TBD) is of type Enumerated and the The IP-Option-Type AVP (AVP Code TBD) is of type Enumerated and the
values are managed by IANA under the IP Option Numbers registry values are managed by IANA under the IP Option Numbers registry as
[IPOPTIONS]. defined in [RFC2780].
4.1.8.5. IP-Option-Value AVP 4.1.8.5. IP-Option-Value AVP
The IP-Option-Value AVP (AVP Code TBD) is of type OctetString and The IP-Option-Value AVP (AVP Code TBD) is of type OctetString and
contains the option value that must be matched. contains the option value that must be matched.
4.1.8.6. TCP-Option AVP 4.1.8.6. TCP-Option AVP
The TCP-Option AVP (AVP Code TBD) is of type Grouped and specifies a The TCP-Option AVP (AVP Code TBD) is of type Grouped and specifies a
TCP header option that must be matched. TCP header option that must be matched.
skipping to change at page 17, line 24 skipping to change at page 18, line 24
header but the value is wild carded. header but the value is wild carded.
The Negated AVP is used in conjunction which the TCP-Option-Value The Negated AVP is used in conjunction which the TCP-Option-Value
AVPs to specify TCP header options which do not match specific AVPs to specify TCP header options which do not match specific
values. The Negated AVP is used without the TCP-Option-Value AVP to values. The Negated AVP is used without the TCP-Option-Value AVP to
specify TCP headers which do not contain the option type. specify TCP headers which do not contain the option type.
4.1.8.7. TCP-Option-Type AVP 4.1.8.7. TCP-Option-Type AVP
The TCP-Option-Type AVP (AVP Code TBD) is of type Enumerated and the The TCP-Option-Type AVP (AVP Code TBD) is of type Enumerated and the
values are managed by IANA under the TCP Option Numbers registry values are managed by IANA under the TCP Option Numbers registry as
[TCPOPTIONS]. defined in [RFC2780].
4.1.8.8. TCP-Option-Value AVP 4.1.8.8. TCP-Option-Value AVP
The TCP-Option-Value AVP (AVP Code TBD) is of type OctetString and The TCP-Option-Value AVP (AVP Code TBD) is of type OctetString and
contains the option value that must be matched. contains the option value that must be matched.
4.1.8.9. TCP-Flags AVP 4.1.8.9. TCP-Flags AVP
The TCP-Flags AVP (AVP Code TBD) is of type Grouped and specifies a The TCP-Flags AVP (AVP Code TBD) is of type Grouped and specifies a
set of TCP control flags that must be matched. set of TCP control flags that must be matched.
skipping to change at page 18, line 42 skipping to change at page 19, line 42
specify ICMP codes that do not match specific values. The Negated specify ICMP codes that do not match specific values. The Negated
AVP is used without the ICMP-Code AVP to specify ICMP headers which AVP is used without the ICMP-Code AVP to specify ICMP headers which
do not contain the ICMP type. As such, the Negated AVP feature do not contain the ICMP type. As such, the Negated AVP feature
applies to ICMP-Code AVP if the ICMP-Code AVP is present. If the applies to ICMP-Code AVP if the ICMP-Code AVP is present. If the
ICMP-Code AVP is absent, the Negated AVP feature applies to the ICMP- ICMP-Code AVP is absent, the Negated AVP feature applies to the ICMP-
Type-Number. Type-Number.
4.1.8.12. ICMP-Type-Number AVP 4.1.8.12. ICMP-Type-Number AVP
The ICMP-Type-Number AVP (AVP Code TBD) is of type Enumerated and the The ICMP-Type-Number AVP (AVP Code TBD) is of type Enumerated and the
values are managed by IANA under the ICMP Type Numbers registry values are managed by IANA under the ICMP Type Numbers registry as
[ICMPTYPE]. defined in [RFC2780].
4.1.8.13. ICMP-Code AVP 4.1.8.13. ICMP-Code AVP
The ICMP-Code AVP (AVP Code TBD) is of type Enumerated and the values The ICMP-Code AVP (AVP Code TBD) is of type Enumerated and the values
are managed by IANA under the ICMP Type Numbers registry [ICMPTYPE]. are managed by IANA under the ICMP Type Numbers registry as defined
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 ] * [ ETH-Priority-Range ]
skipping to change at page 20, line 14 skipping to change at page 21, line 14
case. If the VLAN-ID-Range AVP is omitted from the Classifier, then case. If the VLAN-ID-Range AVP is omitted from the Classifier, then
comparison of the VLAN identity of the packet is irrelevant. comparison of the VLAN identity of the packet is irrelevant.
VLAN-ID-Range ::= < AVP Header: XXX > VLAN-ID-Range ::= < AVP Header: XXX >
[ S-VID-Start ] [ S-VID-Start ]
[ S-VID-End ] [ S-VID-End ]
[ C-VID-Start ] [ C-VID-Start ]
[ C-VID-End ] [ C-VID-End ]
* [ AVP ] * [ AVP ]
When the S-VID-Start AVP is present but the S-VID-End AVP is absent, The following is the list of possible combinations of the S-VID-Start
the S-VID-Start AVP value MUST equal the value of the IEEE 802.1ad and S-VID-End AVPs and their inference:
S-VID bits specified in [IEEE802.1ad] for a successful match. When
both S-VID-Start and S-VID-End AVPs are present, the value of the
IEEE 802.1ad S-VID bits MUST be greater than or equal to the S-VID-
Start AVP value and less than or equal to the S-VID-End AVP value for
a successful match. If the S-VID-Start and S-VID-End AVPs are
omitted, then existence of IEEE802.1ad encapsulation or comparison of
the IEEE 802.1ad S-VID bits is irrelevamt for this Classifier. If
the S-VID-Start and S-VID-End AVPs are specified, then Ethernet
packets without IEEE 802.1ad encapsulation MUST NOT match this
Classifier.
When the C-VID-Start AVP is present but the C-VID-End AVP is absent, o If S-VID-Start AVP is present but the S-VID-End AVP is absent, the
the C-VID-Start AVP value MUST equal the value of the IEEE 802.1ad S-VID-Start AVP value MUST equal the value of the IEEE 802.1ad
C-VID bits specified in [IEEE802.1ad] or the IEEE 802.1Q VLAN-ID bits S-VID bits specified in [IEEE802.1ad] for a successful match.
specified in [IEEE802.1Q] for a successful match. When both C-VID- o If S-VID-Start AVP is absent but the S-VID-End AVP is present, the
Start and C-VID-End AVPs are present, the value of the IEEE 802.1ad S-VID-End AVP value MUST equal the value of the IEEE 802.1ad S-VID
C-VID bits or the IEEE 802.1Q VLAN-ID bits MUST be greater than or bits for a successful match.
equal to the C-VID-Start AVP value and less than or equal to the o If both S-VID-Start and S-VID-End AVPs are present and their
C-VID-End AVP value for a successful match. If the C-VID-Start and values are equal, the S-VID-Start AVP value MUST equal the value
C-VID-End AVPs are omitted, then comparison of the IEEE 802.1ad C-VID of the IEEE 802.1ad S-VID bits for a successful match.
bits or IEEE 802.1Q VLAN-ID bits for this Classifier is irrelevant. o If both S-VID-Start and S-VID-End AVPs are present and the value
If the C-VID-Start and C-VID-End AVPs are specified, then Ethernet of S-VID-End AVP is greater than the value of the S-VID-Start AVP,
packets without IEEE 802.1ad or IEEE 802.1Q encapsulation MUST NOT the value of the IEEE 802.1ad S-VID bits MUST be greater than or
match this Classifier. equal to the S-VID- Start AVP value and less than or equal to the
S-VID-End AVP value for a successful match. If the S-VID-Start
and S-VID-End AVPs are specified, then Ethernet packets without
IEEE 802.1ad encapsulation MUST NOT match this Classifier.
o If the S-VID-Start and S-VID-End AVPs are omitted, then existence
of IEEE802.1ad encapsulation or comparison of the IEEE 802.1ad
S-VID bits is irrelevant for this Classifier.
The following is the list of possible combinations of the C-VID-Start
and C-VID-End AVPs and their inference:
o If C-VID-Start AVP is present but the C-VID-End AVP is absent, the
C-VID-Start AVP value MUST equal the value of the IEEE 802.1ad
C-VID bits specified in [IEEE802.1ad] or the IEEE 802.1Q VLAN-ID
bits specified in [IEEE802.1Q] for a successful match.
o If C-VID-Start AVP is absent but the C-VID-End AVP is present, the
C-VID-End AVP value MUST equal the value of the IEEE 802.1ad C-VID
bits or the IEEE 802.1Q VLAN-ID bits for a successful match.
o If both C-VID-Start and C-VID-End AVPs are present and their
values are equal, the C-VID-Start AVP value MUST equal the value
of the IEEE 802.1ad C-VID bits or the IEEE 802.1Q VLAN-ID bits for
a successful match.
o If both C-VID-Start and C-VID-End AVPs are present and the value
of C-VID-End AVP is greater than the value of the C-VID-Start AVP,
the value of the IEEE 802.1ad C-VID bits or the IEEE 802.1Q
VLAN-ID bits MUST be greater than or equal to the C-VID-Start AVP
value and less than or equal to the C-VID-End AVP value for a
successful match. If the C-VID-Start and C-VID-End AVPs are
specified, then Ethernet packets without IEEE 802.1ad or IEEE
802.1Q encapsulation MUST NOT match this Classifier.
o If the C-VID-Start and C-VID-End AVPs are omitted, the comparison
of the IEEE 802.1ad C-VID bits or IEEE 802.1Q VLAN-ID bits for
this Classifier is irrelevant.
4.1.8.19. S-VID-Start AVP 4.1.8.19. S-VID-Start AVP
The S-VID-Start AVP (AVP Code TBD) is of type Unsigned32. The value The S-VID-Start AVP (AVP Code TBD) is of type Unsigned32. The value
MUST be in the range from 0 to 4095. The value of this AVP specifies MUST be in the range from 0 to 4095. The value of this AVP specifies
the start value of the range of S-VID VLAN-IDs to be matched. the start value of the range of S-VID VLAN-IDs to be matched.
4.1.8.20. S-VID-End AVP 4.1.8.20. S-VID-End AVP
The S-VID-End AVP (AVP Code TBD) is of type Unsigned32. The value The S-VID-End AVP (AVP Code TBD) is of type Unsigned32. The value
skipping to change at page 25, line 31 skipping to change at page 27, line 19
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: police:
[RFC2475] describes policing as " the process of discarding [RFC2475] describes policing as "the process of discarding packets
packets (by a dropper) within a traffic stream in accordance with (by a dropper) within a traffic stream in accordance with the
the state of a corresponding meter enforcing a traffic profile.". state of a corresponding meter enforcing a traffic profile". When
When the action is set to 'police', it is expected that the QoS- the action is set to 'police', it is expected that the QoS-
Parameters AVP carries QoS information to describe traffic Parameters AVP carries QoS information to describe traffic
conforming to a traffic profile. Excess traffic is dropped. conforming to a traffic profile. Excess traffic is dropped.
Hence, there is no need to include the Excess-Treatement AVP with Hence, there is no need to include the Excess-Treatement AVP with
the Excess-Treatment-Action AVP set to 'drop' as this the Excess-Treatment-Action AVP set to 'drop' as this
functionality is implied. functionality is implied.
mark: mark:
xref target="RFC2475"/> describes marking as " the process of [RFC2475] describes marking as "the process of setting the DS
setting the DS codepoint in a packet based on defined rules;". codepoint in a packet based on defined rules". When the action is
When the action is set to 'mark', it is expected that the QoS- set to 'mark', it is expected that the QoS-Parameters AVP carries
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.4.
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
skipping to change at page 30, line 34 skipping to change at page 32, line 34
| | | | | |
| EAP Response #N | | | EAP Response #N | |
|------------------------------>| | |------------------------------>| |
| | Diameter-EAP-Request | | | Diameter-EAP-Request |
| | EAP-Payload(EAP Response #N) | | | EAP-Payload(EAP Response #N) |
| |------------------------------->| | |------------------------------->|
| | | | | |
| | Diameter-EAP-Answer | | | Diameter-EAP-Answer |
| | Result-Code=DIAMETER_SUCCESS | | | Result-Code=DIAMETER_SUCCESS |
| | EAP-Payload(EAP Success) | | | EAP-Payload(EAP Success) |
| | [EAP-Master-Session-Key] |
| | (authorization AVPs) | | | (authorization AVPs) |
| | QoS-Resources(QoS-Authorized) | | | QoS-Resources(QoS-Authorized) |
| |<-------------------------------| | |<-------------------------------|
| | | | | |
| EAP Success | | | EAP Success | |
|<------------------------------| | |<------------------------------| |
| | | | | |
Figure 2: Example of a Diameter EAP enhanced with QoS Information Figure 2: Example of a Diameter EAP enhanced with QoS Information
skipping to change at page 34, line 10 skipping to change at page 36, line 10
client) receives the service request. In this case the client uses client) receives the service request. In this case the client uses
the "QoS-Desired" QoS-Semantics parameter in the QoS-Resources AVP the "QoS-Desired" QoS-Semantics parameter in the QoS-Resources AVP
that it sends to the Accounitng server. The server responds with a that it sends to the Accounitng server. The server responds with a
"QoS-Available" QoS-Semantics parameter in the QoS-Resources AVP "QoS-Available" QoS-Semantics parameter in the QoS-Resources AVP
Service Element Service Element
End User (CC Client) B CC Server End User (CC Client) B CC Server
| | | | | | | |
|(1) Service Request | | | |(1) Service Request | | |
|-------------------->| | | |-------------------->| | |
| |(2) CCR (event, DIRECT_DEBITING,| | |(2) CCR (event, DIRECT_DEBITING,|
| | QoS-Resources[QoS-desired]) | | | QoS-Resources(QoS-desired)) |
| |-------------------------------->| | |-------------------------------->|
| |(3) CCA (Granted-Units, QoS- | | |(3) CCA (Granted-Units, QoS- |
| | Resources[QoS-Authorized]) | | | Resources(QoS-Authorized)) |
| |<--------------------------------| | |<--------------------------------|
|(4) Service Delivery | | | |(4) Service Delivery | | |
|<--------------------| | | |<--------------------| | |
|(5) Begin service | | | |(5) Begin service | | |
|<------------------------------------>| | |<------------------------------------>| |
| | | | | | | |
. . . . . . . .
. . . . . . . .
Figure 6: Example for a One-Time Diameter Credit Control Charging Figure 6: Example for a One-Time Diameter Credit Control Charging
Event Event
7.6. Classifier Examples 7.6. Classifier Examples
Example: Classify all packets from hosts on subnet 12.34.56.00/24 to Example: Classify all packets from hosts on subnet 192.0.2.0/24 to
ports 80, 8090 or 443 on web servers 23.45.67.123, 23.45.68.124, ports 80, 8090 or 443 on web servers 192.0.2.123, 192.0.2.124,
23.45.69.125. 192.0.2.125.
Classifier = { Classifier = {
Classifier-Id = "web_svr_example"; Classifier-Id = "web_svr_example";
Protocol = TCP; Protocol = TCP;
Direction = OUT; Direction = OUT;
From-Spec = { From-Spec = {
IP-Address-Mask = { IP-Address-Mask = {
IP-Address = 12.34.56.00; IP-Address = 192.0.2.0;
IP-Bit-Mask-Width = 24; IP-Bit-Mask-Width = 24;
} }
} }
To-Spec = { To-Spec = {
IP-Address = 23.45.67.123; IP-Address = 192.0.2.123;
IP-Address = 23.45.68.124; IP-Address = 192.0.2.124;
IP-Address = 23.45.69.125; IP-Address = 192.0.2.125;
Port = 80; Port = 80;
Port = 8080; Port = 8080;
Port = 443; Port = 443;
} }
} }
Example: Any SIP signalling traffic from a device with a MAC address 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 of 01:23:45:67:89:ab to servers with IP addresses in the range
34.56.78.90 to 34.56.78.190. 192.0.2.90 to 192.0.2.190.
Classifier = { Classifier = {
Classifier-Id = "web_svr_example"; Classifier-Id = "web_svr_example";
Protocol = UDP; Protocol = UDP;
Direction = OUT; Direction = OUT;
From-Spec = { From-Spec = {
MAC-Address = 01:23:45:67:89:ab; MAC-Address = 01:23:45:67:89:ab;
} }
To-Spec = { To-Spec = {
IP-Address-Range = { IP-Address-Range = {
IP-Address-Start = 34.56.78.90; IP-Address-Start = 192.0.2.90;
IP-Address-End = 34.56.78.190; IP-Address-End = 192.0.2.190;
} }
Port = 5060; Port = 5060;
Port = 3478; Port = 3478;
Port-Range = { Port-Range = {
Port-Start = 16348; Port-Start = 16348;
Port-End = 32768; Port-End = 32768;
} }
} }
} }
skipping to change at page 39, line 18 skipping to change at page 41, line 18
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
12.1. Normative References 12.1. Normative References
[DSCP] IANA, "Differentiated Services Field Codepoints",
http://www.iana.org/assignments/dscp-registry.
[ICMPTYPE]
IANA, "ICMP Type Numbers",
http://www.iana.org/assignments/icmp-parameters.
[IEEE802.1D] [IEEE802.1D]
IEEE, "IEEE Standard for Local and metropolitan area IEEE, "IEEE Standard for Local and metropolitan area
networks, Media Access Control (MAC) Bridges", 2004. networks, Media Access Control (MAC) Bridges", 2004.
[IEEE802.1Q] [IEEE802.1Q]
IEEE, "IEEE Standard for Local and metropolitan area IEEE, "IEEE Standard for Local and metropolitan area
networks, Virtual Bridged Local Area Networks", 2005. networks, Virtual Bridged Local Area Networks", 2005.
[IEEE802.1ad] [IEEE802.1ad]
IEEE, "IEEE Standard for Local and metropolitan area IEEE, "IEEE Standard for Local and metropolitan area
networks, Virtual Bridged Local Area Networks, Amendment networks, Virtual Bridged Local Area Networks, Amendment
4: Provider Bridges", 2005. 4: Provider Bridges", 2005.
[IEEE802.2] [IEEE802.2]
IEEE, "IEEE Standard for Information technology, IEEE, "IEEE Standard for Information technology,
Telecommunications and information exchange between Telecommunications and information exchange between
systems, Local and metropolitan area networks, Specific systems, Local and metropolitan area networks, Specific
requirements, Part 2: Logical Link Control", 1998. requirements, Part 2: Logical Link Control", 1998.
[IPOPTIONS]
IANA, "IP Option Numbers",
http://www.iana.org/assignments/ip-parameters.
[PROTOCOL]
IANA, "Protocol Types",
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.
[TCPOPTIONS] [RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black,
IANA, "TCP Option Numbers", "Definition of the Differentiated Services Field (DS
http://www.iana.org/assignments/tcp-parameters. Field) in the IPv4 and IPv6 Headers", RFC 2474,
December 1998.
[RFC2780] Bradner, S. and V. Paxson, "IANA Allocation Guidelines For
Values In the Internet Protocol and Related Headers",
BCP 37, RFC 2780, March 2000.
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-07 (work in progress),
December 2008. December 2008.
[I-D.ietf-dime-qos-parameters] [I-D.ietf-dime-qos-parameters]
Korhonen, J. and H. Tschofenig, "Quality of Service Korhonen, J., Tschofenig, H., and E. Davies, "Quality of
Parameters for Usage with Diameter", Service Parameters for Usage with Diameter",
draft-ietf-dime-qos-parameters-08 (work in progress), draft-ietf-dime-qos-parameters-09 (work in progress),
December 2008. January 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.
[RFC3290] Bernet, Y., Blake, S., Grossman, D., and A. Smith, "An
Informal Management Model for Diffserv Routers", RFC 3290,
May 2002.
[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. [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,
August 2005. August 2005.
Authors' Addresses Authors' Addresses
Jouni Korhonen Jouni Korhonen
 End of changes. 31 change blocks. 
141 lines changed or deleted 163 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/