draft-ietf-dime-qos-attributes-01.txt   draft-ietf-dime-qos-attributes-02.txt 
Diameter Maintenance and J. Korhonen, Ed. Diameter Maintenance and J. Korhonen, Ed.
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: January 10, 2008 M. Arumaithurai Expires: April 1, 2008 M. Arumaithurai
University of Goettingen University of Goettingen
July 9, 2007 September 29, 2007
Quality of Service Attributes for Diameter and RADIUS Quality of Service Attributes for Diameter
draft-ietf-dime-qos-attributes-01.txt draft-ietf-dime-qos-attributes-02.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 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 January 10, 2008. This Internet-Draft will expire on April 1, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document extends the functionality of the Diameter Base protocol This document extends the QoSFilterRule AVP functionality of the
and other Diameter applications with respect to their ability to Diameter Base protocol and the functionality of the QoS-Filter-Rule
convey Quality of Service information. The AVPs defined in this AVP defined in RFC 4005. The ability to convey Quality of Service
document are also available for Remote Authentication Dial In User information is made available to the Diameter Network Access Server
Service (RADIUS). Application, the Diameter Credit Control Application and the Diameter
Extensible Authentication Protocol (EAP) Application. Future
Diameter applications can easily integrate Quality of Service support
in addition to packet filtering.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Commands, AVPs and Advertising Application Support . . . . . . 3 3. Commands, AVPs and Advertising Application Support . . . . . . 3
3.1. Command Codes . . . . . . . . . . . . . . . . . . . . . . 3 3.1. Command Codes . . . . . . . . . . . . . . . . . . . . . . 3
3.2. Diameter-EAP-Request (DER) . . . . . . . . . . . . . . . . 4 3.2. Diameter-EAP-Request (DER) . . . . . . . . . . . . . . . . 4
3.3. Diameter-EAP-Answer (DEA) . . . . . . . . . . . . . . . . 4 3.3. Diameter-EAP-Answer (DEA) . . . . . . . . . . . . . . . . 4
3.4. Credit-Control-Request (CCR) . . . . . . . . . . . . . . . 5 3.4. Credit-Control-Request (CCR) . . . . . . . . . . . . . . . 5
3.5. Credit-Control-Answer (CCA) . . . . . . . . . . . . . . . 6 3.5. Credit-Control-Answer (CCA) . . . . . . . . . . . . . . . 6
3.6. AA-Request (AAR) . . . . . . . . . . . . . . . . . . . . . 7 3.6. AA-Request (AAR) . . . . . . . . . . . . . . . . . . . . . 7
3.7. AA-Answer (AAA) . . . . . . . . . . . . . . . . . . . . . 8 3.7. AA-Answer (AAA) . . . . . . . . . . . . . . . . . . . . . 8
4. Diameter QoS Defined AVPs . . . . . . . . . . . . . . . . . . 9 4. Diameter QoS Defined AVPs . . . . . . . . . . . . . . . . . . 9
4.1. QoS-ID AVP . . . . . . . . . . . . . . . . . . . . . . . . 9 4.1. QoS-Capability AVP . . . . . . . . . . . . . . . . . . . . 9
4.2. QoS-Flow-State AVP . . . . . . . . . . . . . . . . . . . . 9 4.2. QoS-Profile AVP . . . . . . . . . . . . . . . . . . . . . 9
4.3. QSPEC AVP . . . . . . . . . . . . . . . . . . . . . . . . 9 4.3. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 10
4.4. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 10 4.4. Extended-QoS-Filter-Rule AVP . . . . . . . . . . . . . . . 10
4.5. QoS-Parameter AVP . . . . . . . . . . . . . . . . . . . . 10 4.5. QoSBlob-Group AVP . . . . . . . . . . . . . . . . . . . . 11
4.6. Extended-QoS-Filter-Rule AVP . . . . . . . . . . . . . . . 10 4.6. QoS-ID AVP . . . . . . . . . . . . . . . . . . . . . . . . 11
4.7. QoS-Capability AVP . . . . . . . . . . . . . . . . . . . . 10 4.7. QoS-ObjectType . . . . . . . . . . . . . . . . . . . . . . 11
4.8. QSPEC-Type AVP . . . . . . . . . . . . . . . . . . . . . . 11 4.8. QoSBlob AVP . . . . . . . . . . . . . . . . . . . . . . . 11
5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.9. QoS-Flow-State AVP . . . . . . . . . . . . . . . . . . . . 12
5.1. Diameter EAP with QoS Information . . . . . . . . . . . . 11 4.10. QoS-Flow-Direction AVP . . . . . . . . . . . . . . . . . . 12
5.2. QoS Authorization . . . . . . . . . . . . . . . . . . . . 12 5. Semantics of QoS Parameters . . . . . . . . . . . . . . . . . 12
5.3. Diameter NASREQ with QoS Information . . . . . . . . . . . 13 6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.4. Diameter Server Initiated Re-authorization of QoS . . . . 14 6.1. Diameter EAP with QoS Information . . . . . . . . . . . . 13
5.5. Diameter Credit-Control with QoS Information . . . . . . . 15 6.2. Diameter NASREQ with QoS Information . . . . . . . . . . . 14
5.6. Diameter Server Initiated Credit Re-authorization . . . . 16 6.3. QoS Authorization . . . . . . . . . . . . . . . . . . . . 15
5.7. QoS and Credit-Control as Part of Authentication and 6.4. Diameter Server Initiated Re-authorization of QoS . . . . 16
Authorization . . . . . . . . . . . . . . . . . . . . . . 17 6.5. Diameter Credit Control with QoS Information . . . . . . . 17
6. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . 19 7. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . 18
6.1. DER and DEA Commands AVP Table . . . . . . . . . . . . . . 19 7.1. DER and DEA Commands AVP Table . . . . . . . . . . . . . . 18
6.2. CCR and CCA Commands AVP Table . . . . . . . . . . . . . . 19 7.2. CCR and CCA Commands AVP Table . . . . . . . . . . . . . . 18
6.3. AAR and AAA Commands AVP Table . . . . . . . . . . . . . . 19 7.3. AAR and AAA Commands AVP Table . . . . . . . . . . . . . . 19
7. Diameter RADIUS Interoperability . . . . . . . . . . . . . . . 20 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 19
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 20 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
10. Security Considerations . . . . . . . . . . . . . . . . . . . 20 10. Security Considerations . . . . . . . . . . . . . . . . . . . 20
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21
11.1. Normative References . . . . . . . . . . . . . . . . . . . 21 11.1. Normative References . . . . . . . . . . . . . . . . . . . 21
11.2. Informative References . . . . . . . . . . . . . . . . . . 21 11.2. Informative References . . . . . . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21
Intellectual Property and Copyright Statements . . . . . . . . . . 23 Intellectual Property and Copyright Statements . . . . . . . . . . 23
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 with the Diameter Base protocol, and related AVPs that can be used with the Diameter Base protocol, and
Diameter Credit Control, Diameter EAP and Diameter NASREQ the Diameter Credit Control Application, the Diameter Extensible
applications to convey Quality of Service information. The Extended- Authentication Protocol (EAP) Application and the Diameter Network
QoS-Filter-Rule AVP thereby replaces the QoSFilterRule, defined in Access Server Application to convey Quality of Service information.
RFC 3588 [RFC3588], and the QoS-Filter-Rule, defined in RFC 4005 The Extended-QoS-Filter-Rule AVP thereby replaces the QoSFilterRule,
[RFC4005]. defined in RFC 3588 [RFC3588], and the QoS-Filter-Rule, defined in
RFC 4005 [RFC4005].
The AVPs defined in this document are also available for Remote
Authentication Dial In User Service (RADIUS).
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. Commands, AVPs and Advertising Application Support 3. Commands, AVPs and Advertising Application Support
3.1. Command Codes 3.1. Command Codes
This document re-uses the Diameter Base protocol [RFC3588], and This document re-uses the Diameter Base protocol [RFC3588], Diameter
Diameter Credit-Control [RFC4006], Diameter NASREQ [RFC4072] and Credit Control [RFC4006], Diameter NASREQ [RFC4005] and Diameter EAP
Diameter EAP [RFC4005] application commands. The following commands [RFC4072] application commands. The following commands are re-used
are re-used to carry QoS related AVPs: to carry QoS related AVPs:
Command-Name Abbrev. Code Reference Command-Name Abbrev. Code Reference
Diameter-EAP-Request DER 268 RFC 4072 Diameter-EAP-Request DER 268 RFC 4072
Diameter-EAP-Answer DEA 268 RFC 4072 Diameter-EAP-Answer DEA 268 RFC 4072
Credit-Control-Request CCR 272 RFC 4006 Credit-Control-Request CCR 272 RFC 4006
Credit-Control-Answer CCA 272 RFC 4006 Credit-Control-Answer CCA 272 RFC 4006
AA-Request AAR 265 RFC 4005 AA-Request AAR 265 RFC 4005
AA-Answer AAA 265 RFC 4005 AA-Answer AAA 265 RFC 4005
Figure 1: Command Codes Figure 1: Command Codes
When the Re-Auth-Request (RAR), Re-Auth-Answer (RAA), Session- When the Re-Auth-Request (RAR), Re-Auth-Answer (RAA), Session-
Termination-Request (STR), Session-Termination-Answer (STA), Abort- Termination-Request (STR), Session-Termination-Answer (STA), Abort-
Session-Request (ASR), Abort-Session-Answer (ASA), Accounting-Request Session-Request (ASR), Abort-Session-Answer (ASA), Accounting-Request
(ACR), and Accounting-Answer (ACA) commands are used together with (ACR), and Accounting-Answer (ACA) commands are used together with
this specification they follow the rules in Diameter NASREQ this specification they follow the rules in Diameter NASREQ
[RFC4005], Diameter EAP [RFC4072], Credit-Control [RFC4006] and [RFC4005], Diameter EAP [RFC4072], Credit Control [RFC4006] and
Diameter Base Protocol [RFC3588]. The accounting commands use the Diameter Base Protocol [RFC3588]. The accounting commands use the
Application Identifier value of the respective application. Application Identifier value of the respective application.
3.2. Diameter-EAP-Request (DER) 3.2. Diameter-EAP-Request (DER)
The Diameter-EAP-Request (DER) command [RFC4072], indicated by the The Diameter-EAP-Request (DER) command [RFC4072], indicated by the
Command-Code field set to 268 and the 'R' bit set in the Command Command-Code field set to 268 and the 'R' bit set in the Command
Flags field, may be sent by the NAS to the Diameter server providing Flags field, may be sent by the NAS to the Diameter server providing
network access authentication and authorization services. At the network access authentication and authorization services. At the
same time as the network access authentication and authorization, the same time as the network access authentication and authorization, the
NAS MAY request the Diameter server to authorize provisioning of QoS NAS MAY request the Diameter server to authorize provisioning of QoS
resources. resources.
The message format is the same as defined in [RFC4072] with an The message format is the same as defined in [RFC4072] with an
addition of Diameter QoS specific AVPs. Figure 2 shows the DER addition of QoS specific AVPs. Figure 2 shows the DER message used
message used with the Diameter QoS AVPs: with the QoS specific AVPs:
<Diameter-EAP-Request> ::= < Diameter Header: 268, REQ, PXY > <Diameter-EAP-Request> ::= < Diameter Header: 268, REQ, PXY >
< Session-Id > < Session-Id >
{ Auth-Application-Id } { Auth-Application-Id }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
{ Destination-Realm } { Destination-Realm }
{ Auth-Request-Type } { Auth-Request-Type }
[ Destination-Host ] [ Destination-Host ]
skipping to change at page 5, line 8 skipping to change at page 5, line 6
3.3. Diameter-EAP-Answer (DEA) 3.3. Diameter-EAP-Answer (DEA)
The Diameter-EAP-Answer (DEA) message defined in [RFC4072], indicated The Diameter-EAP-Answer (DEA) message defined in [RFC4072], indicated
by the Command- Code field set to 268 and 'R' bit cleared in the by the Command- Code field set to 268 and 'R' bit cleared in the
Command Flags field is sent in response to the Diameter-EAP-Request Command Flags field is sent in response to the Diameter-EAP-Request
message (DER). If the QoS service is successfully authorized and the message (DER). If the QoS service is successfully authorized and the
Diameter server was able to fulfill the QoS Authorization request (if Diameter server was able to fulfill the QoS Authorization request (if
needed) then the response MAY include the QoS-Resources AVPs. needed) then the response MAY include the QoS-Resources AVPs.
The message format is the same as defined in [RFC4072] with an The message format is the same as defined in [RFC4072] with an
addition of Diameter QoS specific AVPs. Figure 3 shows the DEA addition of QoS specific AVPs. Figure 3 shows the DEA message used
message used with the Diameter QoS AVPs: with the QoS specific AVPs:
<Diameter-EAP-Answer> ::= < Diameter Header: 268, PXY > <Diameter-EAP-Answer> ::= < Diameter Header: 268, PXY >
< Session-Id > < Session-Id >
{ Auth-Application-Id } { Auth-Application-Id }
{ Auth-Request-Type } { Auth-Request-Type }
{ Result-Code } { Result-Code }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
* [ QoS-Resources ] * [ QoS-Resources ]
skipping to change at page 5, line 38 skipping to change at page 5, line 36
3.4. Credit-Control-Request (CCR) 3.4. Credit-Control-Request (CCR)
The Credit-Control-Request (CCR) command [RFC4006], indicated by the The Credit-Control-Request (CCR) command [RFC4006], indicated by the
Command-Code field set to 272 and the 'R' bit set in the Command Command-Code field set to 272 and the 'R' bit set in the Command
Flags field, may be sent by the NAS to the Diameter-QoS server to Flags field, may be sent by the NAS to the Diameter-QoS server to
request QoS credit authorization for a given QoS provisioning request QoS credit authorization for a given QoS provisioning
request. In that case the CCR command MAY also carry the QoS- request. In that case the CCR command MAY also carry the QoS-
Resources AVPs. Resources AVPs.
The message format is the same as defined in [RFC4006] with an The message format is the same as defined in [RFC4006] with an
addition of Diameter QoS specific AVPs. Figure 4 shows the CCR addition of QoS specific AVPs. Figure 4 shows the CCR message used
message used with the Diameter QoS AVPs: with the QoS specific AVPs:
<Credit-Control-Request> ::= < Diameter Header: 272, REQ, PXY > <Credit-Control-Request> ::= < Diameter Header: 272, REQ, PXY >
< Session-Id > < Session-Id >
{ Auth-Application-Id } { Auth-Application-Id }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
{ Destination-Realm } { Destination-Realm }
{ Auth-Request-Type } { Auth-Request-Type }
{ Service-Context-Id } { Service-Context-Id }
{ CC-Request-Type } { CC-Request-Type }
skipping to change at page 6, line 36 skipping to change at page 6, line 36
3.5. Credit-Control-Answer (CCA) 3.5. Credit-Control-Answer (CCA)
The Credit-Control-Answer (CCA) command [RFC4006], indicated by the The Credit-Control-Answer (CCA) command [RFC4006], indicated by the
Command-Code field set to 272 and the 'R' bit set in the Command Command-Code field set to 272 and the 'R' bit set in the Command
Flags field is sent in response to the CC-Request (CCR) message to Flags field is sent in response to the CC-Request (CCR) message to
acknowledge a CC-Request command. If the Diameter QoS server was acknowledge a CC-Request command. If the Diameter QoS server was
able to fulfill the QoS request (if needed) then the response MAY able to fulfill the QoS request (if needed) then the response MAY
include the QoS-Resources AVPs. include the QoS-Resources AVPs.
The message format is the same as defined in [RFC4006] with an The message format is the same as defined in [RFC4006] with an
addition of Diameter QoS specific AVPs. Figure 5 shows the CCA addition of QoS specific AVPs. Figure 5 shows the CCA message used
message used with the Diameter QoS AVPs: with the QoS specific AVPs:
<Credit-Control-Answer> ::= < Diameter Header: 272, PXY > <Credit-Control-Answer> ::= < Diameter Header: 272, PXY >
< Session-Id > < Session-Id >
{ Result-Code } { Result-Code }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
{ Auth-Application-Id } { Auth-Application-Id }
{ CC-Request-Type } { CC-Request-Type }
{ CC-Request-Number } { CC-Request-Number }
[ User-Name ] [ User-Name ]
skipping to change at page 7, line 37 skipping to change at page 7, line 37
3.6. AA-Request (AAR) 3.6. AA-Request (AAR)
The AA-Request (AAR) message, indicated by the Command-Code field set The AA-Request (AAR) message, indicated by the Command-Code field set
to 265 and 'R' bit set in the Command Flags field, may be sent by the to 265 and 'R' bit set in the Command Flags field, may be sent by the
NAS to the Diameter server providing network access configuration NAS to the Diameter server providing network access configuration
services. At the same time as the network access authentication and services. At the same time as the network access authentication and
authorization, the NAS MAY request the Diameter server to authorize authorization, the NAS MAY request the Diameter server to authorize
provisioning of QoS resources. provisioning of QoS resources.
The message format is the same as defined in [RFC4005] with an The message format is the same as defined in [RFC4005] with an
addition of Diameter QoS specific AVPs. Figure 6 shows the AAR addition of QoS specific AVPs. Figure 6 shows the AAR message used
message used with the Diameter QoS AVPs: with the QoS specific AVPs:
<AA-Request> ::= < Diameter Header: 265, REQ, PXY > <AA-Request> ::= < Diameter Header: 265, REQ, PXY >
< Session-Id > < Session-Id >
{ Auth-Application-Id } { Auth-Application-Id }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
{ Destination-Realm } { Destination-Realm }
{ Auth-Request-Type } { Auth-Request-Type }
[ QoS-Capability ] [ QoS-Capability ]
skipping to change at page 8, line 33 skipping to change at page 8, line 33
The AA-Answer (AAA) message, indicated by the Command-Code field set The AA-Answer (AAA) message, indicated by the Command-Code field set
to 265 and 'R' bit cleared in the Command Flags field is sent in to 265 and 'R' bit cleared in the Command Flags field is sent in
response to the AA-Request (AAR) message for confirmation of the response to the AA-Request (AAR) message for confirmation of the
result of QoS provisioning. If the QoS service is successfully result of QoS provisioning. If the QoS service is successfully
authorized and the Diameter server was able to fulfill the QoS authorized and the Diameter server was able to fulfill the QoS
provisioning request (if needed) then the response MAY include the provisioning request (if needed) then the response MAY include the
QoS-Resources AVPs. QoS-Resources AVPs.
The message format is the same as defined in [RFC4005] with an The message format is the same as defined in [RFC4005] with an
addition of Diameter QoS specific AVPs. Figure 7 shows the AAA addition of QoS specific AVPs. Figure 7 shows the AAA message used
message used with the Diameter QoS AVPs: with the QoS specific AVPs:
<AA-Answer> ::= < Diameter Header: 265, PXY > <AA-Answer> ::= < Diameter Header: 265, PXY >
< Session-Id > < Session-Id >
{ Auth-Application-Id } { Auth-Application-Id }
{ Auth-Request-Type } { Auth-Request-Type }
{ Result-Code } { Result-Code }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
* [ QoS-Resources ] * [ QoS-Resources ]
skipping to change at page 9, line 18 skipping to change at page 9, line 18
The following table lists the Diameter AVPs used by this document, The following table lists the Diameter AVPs used by this document,
their AVP code values, types, possible flag values, and whether the their AVP code values, types, possible flag values, and whether the
AVP may be encrypted. AVP may be encrypted.
+------------------+ +------------------+
| AVP Flag Rules | | AVP Flag Rules |
+-------------------------------------------------|----+---+----+----+ +-------------------------------------------------|----+---+----+----+
| AVP Section |MUST|MAY|SHLD|MUST| | AVP Section |MUST|MAY|SHLD|MUST|
| Attribute Name Code Defined Data Type | | | NOT| NOT| | Attribute Name Code Defined Data Type | | | NOT| NOT|
+-------------------------------------------------+----+---+----+----+ +-------------------------------------------------+----+---+----+----+
|QoS-Flow-State TBD 4.2 Enumerated | |M,P| | V | |QoS-Capability TBD 4.1 Grouped | |M,P| | V |
|QSPEC TBD 4.3 OctetSTring| |M,P| | V | |QoS-Profile TBD 4.2 Unsigned32 | |M,P| | V |
|QoS-ID TBD 4.1 Unsigned32 | |M,P| | V | |QoS-Resources TBD 4.3 Grouped | |M,P| | V |
|Extended-QoS-Filter-Rule TBD 4.6 Grouped | |M,P| | V | |Extended-QoS-Filter-Rule TBD 4.4 Grouped | |M,P| | V |
|QoS-Resources TBD 4.4 Grouped | |M,P| | V | |QoSBlob-Group TBD 4.5 Grouped | |M,P| | V |
|QoS-Parameter TBD 4.5 Grouped | |M,P| | V | |QoS-ID TBD 4.6 Unsigned32 | |M,P| | V |
|QoS-Capability TBD 4.7 Grouped | |M,P| | V | |QoS-ObjectType TBD 4.7 Enumerated | |M,P| | V |
|QSPEC-Type TBD 4.8 Unsigned32 | |M,P| | V | |QoSBlob TBD 4.8 OctetString| |M,P| | V |
|QoS-Flow-State TBD 4.9 Enumerated | |M,P| | V |
|QoS-Flow-Direction TBD 4.10 Enumerated | |M,P| | V |
+-------------------------------------------------+----+---+----+----+ +-------------------------------------------------+----+---+----+----+
4.1. QoS-ID AVP 4.1. QoS-Capability AVP
The QoS-ID AVP (AVP Code TBD) is of type Unsigned32 and references The QoS-Capability AVP (AVP Code TBD) is of type Grouped and contains
the QSPEC. a list of supported Quality of Service profiles (and therefore the
support of respective AVPs).
4.2. QoS-Flow-State AVP QoS-Capability ::= < AVP Header: XXX >
1* { QoS-Profile }
* [ AVP ]
The QoS-Flow-State AVP (AVP Code TBD) is of type Enumerated. It 4.2. QoS-Profile AVP
gives an indication as to how the flow MUST be treated. The
Extended-QoS-Filter-Rule already provides an indicate whether a flow
is permitted or denied. This optional AVP provides additional
information about the treatment. Currently a single value is
defined; further values are available via IANA registration.
0 Pending: The filter rules are not installed but kept pending. The QoS-Profile AVP (AVP Code TBD) is of type Unsigned64 and contains
Subsequent signaling is necessary to active them. the vendor and a specifier field. The 64-bit value in the QoS-
Profile AVP is structured as shown below.
4.3. QSPEC AVP 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vendor |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Specifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The QSPEC AVP (AVP Code TBD) is of type OctetString and contains Vendor Field:
Quality of Service parameters. These parameters are defined in a
separate document, see [I-D.ietf-dime-qos-parameters].
4.4. QoS-Resources AVP 32 bits of IANA SMI Network Management Private Enterprise Code.
The Vendor-ID 0x00000000 is reserved for IANA registered QoS
profiles.
Specifier Field:
32-bit unsigned integer, representing the defined profile value.
An initial QoS profile is defined with vendor field set to 0x00000000
and the specifier field set to 0, as described in
[I-D.ietf-dime-qos-parameters]. The registry for the QoS profiles is
created with the same document.
4.3. QoS-Resources AVP
The QoS-Resources AVP (AVP Code TBD) is of type Grouped and includes The QoS-Resources AVP (AVP Code TBD) is of type Grouped and includes
description of the resources that have been authorized or requested. description of the Quality of Service resources.
More than one QoS-Resources AVP MAY be included in a single message.
QoS-Resources ::= < AVP Header: XXX > QoS-Resources ::= < AVP Header: XXX >
1* [ Extended-QoS-Filter-Rule ] 0* [ Extended-QoS-Filter-Rule ]
1* [ QoS-Parameter ] 0* [ QoSBlob-Group ]
[ QoS-Flow-State ] [ QoS-Flow-State ]
* [ AVP ] * [ AVP ]
4.5. QoS-Parameter AVP 4.4. Extended-QoS-Filter-Rule AVP
The QoS-Parameter AVP (AVP Code TBD) is of type Grouped and ties the TheExtended-QoS-Filter-Rule AVP (AVP Code TBD) is of type Grouped.
QoS-ID AVP together to the QSPEC AVP. All parameters followed by the The QoS filter rule associated with the QoS-ID re-uses the RADIUS
QSPEC-Type AVP refer to the same QoS model/profile. NAS-Traffic-Rule AVP [I-D.ietf-radext-filter-rules]. This AVP ties a
specific filter to a QoS-ID that in turn refers to a specific
QoSBlob-Group. At least either one of the NAS-Traffic-Rule or the
QoS-Flow-Direction AVPs SHOULD be included.
QoS-Parameter ::= < AVP Header: XXX > Extended-QoS-Filter-Rule ::= < AVP Header: XXX >
{ QoS-ID } { QoS-ID }
{ QSPEC-Type } [ NAS-Traffic-Rule ]
1* [ QSPEC ] [ QoS-Flow-Direction ]
* [ AVP ] * [ AVP ]
4.6. Extended-QoS-Filter-Rule AVP 4.5. QoSBlob-Group AVP
TheExtended-QoS-Filter-Rule AVP (AVP Code TBD) is of type Grouped. The QoSBlob-Group AVP (AVP Code TBD) is of type Grouped and ties the
The QoS filter rule associated with the QoS-ID re-uses the RADIUS QoS-ID AVP together to the QoSBlob AVP. All parameters followed by
NAS-Traffic-Rule AVP [I-D.ietf-radext-filter-rules]. This AVP ties a the QoSBlob-Type AVP refer to the same QoS model/profile.
specific filter to a QoS-ID that in turn refers to a specific QoS-
Parameter.
Extended-QoS-Filter-Rule ::= < AVP Header: XXX > QoSBlob-Group ::= < AVP Header: XXX >
{ QoS-ID } { QoS-ID }
{ NAS-Traffic-Rule } { QoS-ObjectType }
{ QoS-Profile }
0* [ QoSBlob ]
* [ AVP ] * [ AVP ]
4.7. QoS-Capability AVP It is possible to have predefined QoS profiles that contains very
specific QoS values and refer to it only using a specifically
assigned QoS-Profile AVP value. In this case including QoSBlob AVP
is not needed.
The QoS-Capability AVP (AVP Code TBD) is of type Grouped and contains 4.6. QoS-ID AVP
a list of supported QSPEC-Types and respective AVPs.
The NAS SHOULD include this AVP from the NAS to the Diameter server The QoS-ID AVP (AVP Code TBD) is of type Unsigned32 and references
to indicate the support for this specification and for the specific the QoSBlob.
QoS models.
QoS-Capability ::= < AVP Header: XXX > 4.7. QoS-ObjectType
1* { QSPEC-Type }
* [ AVP ]
4.8. QSPEC-Type AVP The QoS-ObjectType AVP (AVP Code TBD) is of type Enumerated and
provides the semantic for the content of the QoSBlob AVP.
The QSPEC-Type AVP (AVP Code TBD) is of type Unsigned32 and contains This document defines the following values:
the supported QoS model or QoS profile. The value of 0 refers to the
QoS parameters described in [I-D.ietf-dime-qos-parameters]. The
values are taken from the registry defined in [I-D.ietf-nsis-qspec].
5. Examples (0): QoS-Desired
(1): QoS-Available
(2): QoS-Reserved
(3): Minimum-QoS
(4): QoS-Authorized
4.8. QoSBlob AVP
The QoSBlob AVP (AVP Code TBD) is of type OctetString and contains
Quality of Service parameters. These parameters are defined in a
separate document, see [I-D.ietf-dime-qos-parameters].
4.9. QoS-Flow-State AVP
The QoS-Flow-State AVP (AVP Code TBD) is of type Enumerated. It
gives an indication as to how the flow has to be treated. The
Extended-QoS-Filter-Rule already provides an indicate whether a flow
is permitted or denied. This optional AVP provides additional
information about the treatment. Currently, a single value is
defined; further values are available via IANA registration.
Value | Name and Semantic
------+------------------------------------------------------------
0 | QOS_FLOW_STATE_PENDING - The QoS reservation is kept
| pending. The QoS resources are not installed and subsequent
| QoS signaling is necessary to active them.
4.10. QoS-Flow-Direction AVP
The QoS-Flow-Direction AVP (AVP Code TBD) is of type Enumerated. It
gives an indication of the direction the provided QoS information
should be applied to. The QoS information can be applied to downlink
flows or to uplink flows. The QoS-Flow-Direction AVP may be used in
conjunction with the NAS-Traffic-Rule AVP. In a case conflicting
definitions between the QoS-Flow-Direction and the NAS-Traffic-Rule,
the QoS-Flow-Direction has precedence meaning the filter rules are
applied only to the flows going to the direction indicated by the
QoS-Flow-Direction AVP. In the absence of the QoS-Flow-Direction the
default treatment is to both directions. Currently, three values are
defined; further values are available via IANA registration.
Value | Name and Semantic
------+------------------------------------------------------------
0 | QOS_FLOW_DIRECTION_BOTH - The QoS information in applied to
| both downlink and uplink flows. This is also the default.
1 | QOS_FLOW_DIRECTION_DL - The QoS information in applied to
| downlink flows only.
2 | QOS_FLOW_DIRECTION_UL - The QoS information in applied to
| uplink flows only.
5. Semantics of QoS Parameters
The QoS parameters carried in the QoS-Resources AVP may appear in
different messages. The semantic of the QoS parameters depend on the
information provided in the Object Type defined in
[I-D.ietf-dime-qos-parameters]. The Object Type currently lists 5
values, namely QoS-Desired (0), QoS-Available (1), QoS-Reserved (2),
Minimum-QoS (3), and QoS-Authorized (4).
The semantics of the different Object Types are as follows:
Object Type Direction Semantic
----------------------------------------------------------------------
QoS-Desired C->S Please authorize the indicated QoS
QoS-Desired C<-S NA
QoS-Available C->S Adminission Control at router indicates
that this QoS is available. (note 1)
QoS-Available C<-S Indicated QoS is available. (note 2)
QoS-Reserved C->S Used for reporting during accounting.
QoS-Reserved C<-S NA
Minimum-QoS C->S Indicates that the client is not interested
interested in authorizing QoS that is
lower than Min. QoS
Minimum-QoS C<-S The client must not provide QoS guarantees
lower than Min. QoS
QoS-Authorized C->S NA
QoS-Authorized C<-S Indicated QoS authorized
Legend:
C: Diameter client
S: Diameter server
NA: Not applicable to this document;
no semantic defined in this specification
Notes:
(1) QoS-Available is only useful in relationship with QoS-Desired
(and optionally with Minimum-QoS).
(2) QoS-Available is only useful when the AAA server performs
admission control and knows about the resources in the network.
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. These signaling flows are Control applications message exchanges.
meant to be examples only.
5.1. Diameter EAP with QoS Information 6.1. Diameter EAP with QoS Information
Figure 8 shows a simple signaling flow where a NAS (Diameter Client) Figure 18 shows a simple signaling flow where a NAS (Diameter Client)
announces its QoS awareness and capabilities included into the DER announces its QoS awareness and capabilities included into the DER
message and as part of the access authentication procedure. Upon message and as part of the access authentication procedure. Upon
completion of the EAP negotiation, the Diameter Server provides a completion of the EAP exchange, the Diameter Server provides a pre-
pre-provisioned QoS profile to the NAS in the final DEA message. provisioned QoS profile with the QoS-ObjectType in the QoSBlob-Group
AVP set to "QoS-Authorized", to the NAS in the final DEA message.
End Diameter Diameter End Diameter Diameter
Host Client server Host Client server
| | | | | |
| (initiate EAP) | | | (initiate EAP) | |
|<------------------------------>| | |<------------------------------>| |
| | Diameter-EAP-Request | | | Diameter-EAP-Request |
| | EAP-Payload(EAP Start) | | | EAP-Payload(EAP Start) |
| | QoS-Capability | | | QoS-Capability |
| |------------------------------->| | |------------------------------->|
skipping to change at page 12, line 36 skipping to change at page 14, line 36
|------------------------------->| | |------------------------------->| |
| | Diameter-EAP-Request | | | Diameter-EAP-Request |
| | EAP-Payload(EAP Response #N) | | | EAP-Payload(EAP Response #N) |
| |------------------------------->| | |------------------------------->|
| | | | | |
| | Diameter-EAP-Answer | | | Diameter-EAP-Answer |
| | Result-Code=DIAMETER_SUCCESS | | | Result-Code=DIAMETER_SUCCESS |
| | EAP-Payload(EAP Success) | | | EAP-Payload(EAP Success) |
| | [EAP-Master-Session-Key] | | | [EAP-Master-Session-Key] |
| | (authorization AVPs) | | | (authorization AVPs) |
| | QoS-Resources | | | QoS-Resources(QoS-Authorized) |
| |<-------------------------------| | |<-------------------------------|
| | | | | |
| EAP Success | | | EAP Success | |
|<-------------------------------| | |<-------------------------------| |
| | | | | |
Figure 8: Example of a Diameter EAP enhanced with QoS Information Figure 18: Example of a Diameter EAP enhanced with QoS Information
5.2. QoS Authorization
Figure 9 shows an example of authorization only QoS signaling as part
of the NASREQ message exchange. The NAS provides the Diameter Server
with the QoS profile it wishes to use in the AAR message. The
Diameter Server then either authorizes the proposed QoS profile or
reject the authorization, and then informs the NAS about the
authorization result in the AAA message. In this scenario the NAS
does not need to include the QoS-Capability AVP in the AAR message as
the QoS-Resources AVP implicitly does the same and also the NAS is
authorizing a specific QoS profile, not a pre-provisioned one.
End Diameter
Host NAS Server
| | |
| | |
| QoS Request | |
+----------------->| |
| | |
| |AA-Request |
| |Auth-Request-Type=AUTHORIZE_ONLY
| |NASREQ-Payload |
| |QoS-Resources |
| +----------------------------->|
| | |
| | AA-Answer|
| | NASREQ-Payload(Success)|
| | QoS-Resources|
| |<-----------------------------+
| Accept | |
|<-----------------+ |
| | |
| | |
| | |
Figure 9: Example of an Authorization-Only Message Flow
5.3. Diameter NASREQ with QoS Information 6.2. Diameter NASREQ with QoS Information
Figure 10 shows a similar pre-provisioned QoS signaling as in Figure 19 shows a similar pre-provisioned QoS signaling as in
Figure 8 but using the NASREQ application instead of EAP application. Figure 18 but using the NASREQ application instead of EAP
application.
End Diameter End Diameter
Host NAS Server Host NAS Server
| | | | | |
| Start Network | | | Start Network | |
| Attachment | | | Attachment | |
|<---------------->| | |<---------------->| |
| | | | | |
| |AA-Request | | |AA-Request |
| |NASREQ-Payload | | |NASREQ-Payload |
skipping to change at page 14, line 38 skipping to change at page 15, line 38
| Response #N | | | Response #N | |
+----------------->| | +----------------->| |
| | | | | |
| |AA-Request | | |AA-Request |
| |NASREQ-Payload ( Response #N )| | |NASREQ-Payload ( Response #N )|
| +----------------------------->| | +----------------------------->|
| | | | | |
| | AA-Answer| | | AA-Answer|
| | Result-Code=DIAMETER_SUCCESS| | | Result-Code=DIAMETER_SUCCESS|
| | (authorization AVPs)| | | (authorization AVPs)|
| | QoS-Resources | | |QoS-Resources(QoS-Authorized) |
| |<-----------------------------+ | |<-----------------------------+
| | | | | |
| Success | | | Success | |
|<-----------------+ | |<-----------------+ |
| | | | | |
Figure 10: Example of a Diameter NASREQ enhanced with QoS Information Figure 19: Example of a Diameter NASREQ enhanced with QoS Information
5.4. Diameter Server Initiated Re-authorization of QoS 6.3. QoS Authorization
Figure 11 shows a message exchange for a Diameter Server initiated Figure 20 shows an example of authorization only QoS signaling as
QoS profile re-authorization procedure. The Diameter Server sends part of the NASREQ message exchange. The NAS provides the Diameter
the NAS a RAR message requesting re-authorization for an existing server with the "QoS-Desired" QoS-ObjectType AVP included in the QoS-
session and the NAS acknowledges it with a RAA message. The NAS that Resources AVP. The Diameter server then either authorizes the
is aware of its existing QoS profile and information for the ongoing indicated QoS or rejects the request and informs the NAS about the
session that the Diameter Server requested for re-authorization. result. In this scenario the NAS does not need to include the QoS-
Thus the NAS must initiate re-authorization of the existing QoS Capability AVP in the AAR message as the QoS-Resources AVP implicitly
profile. The re-authorization procedure is the same as in Figure 9. does the same and also the NAS is authorizing a specific QoS profile,
not a pre-provisioned one.
End Diameter
Host NAS Server
| | |
| | |
| QoS Request | |
+----------------->| |
| | |
| |AA-Request |
| |Auth-Request-Type=AUTHORIZE_ONLY
| |NASREQ-Payload |
| |QoS-Resources(QoS-Desired) |
| +----------------------------->|
| | |
| | AA-Answer|
| | NASREQ-Payload(Success)|
| | QoS-Resources(QoS-Authorized)|
| |<-----------------------------+
| Accept | |
|<-----------------+ |
| | |
| | |
| | |
Figure 20: Example of an Authorization-Only Message Flow
6.4. Diameter Server Initiated Re-authorization of QoS
Figure 21 shows a message exchange for a Diameter server initiated
QoS re-authorization procedure. The Diameter server sends the NAS a
RAR message requesting re-authorization for an existing session and
the NAS acknowledges it with a RAA message. The NAS is aware of its
existing QoS profile and information for the ongoing session that the
Diameter server requested for re-authorization. Thus, the NAS must
initiate re-authorization of the existing QoS profile. The re-
authorization procedure is the same as in Figure 20.
End Diameter End Diameter
Host NAS Server Host NAS Server
| | | | | |
| | | | | |
: : : : : :
: <<<Initial Messag Exchanges>>> : : <<<Initial Messag Exchanges>>> :
: : : : : :
| | | | | |
| | RA-Request | | | RA-Request |
| |<-----------------------------+ | |<-----------------------------+
| | | | | |
| |RA-Answer | | |RA-Answer |
| |Result-Code=DIAMETER_SUCCESS | | |Result-Code=DIAMETER_SUCCESS |
| +----------------------------->| | +----------------------------->|
| | | | | |
| | | | | |
| |AA-Request | | |AA-Request |
| |NASREQ-Payload | | |NASREQ-Payload |
| |Auth-Request-Type=AUTHORIZE_ONLY | |Auth-Request-Type=AUTHORIZE_ONLY
| |QoS-Capability | | |QoS-Resources(QoS-Desired) |
| +----------------------------->| | +----------------------------->|
| | | | | |
| | AA-Answer| | | AA-Answer|
| | Result-Code=DIAMETER_SUCCESS| | | Result-Code=DIAMETER_SUCCESS|
| | (authorization AVPs)| | | (authorization AVPs)|
| | QoS-Resources | | | QoS-Resources(QoS-Authorized)|
| |<-----------------------------+ | |<-----------------------------+
| | | | | |
Figure 11: Example of a Server-initiated Re-Authorization Procedure Figure 21: Example of a Server-initiated Re-Authorization Procedure
5.5. Diameter Credit-Control with QoS Information
In this case the authorization and authentication take place at the
beginning and then when a new service request comes in the accounting
is done as per the required QoS. It's a 3GPP scenario.
Diameter
End User Service Element Server CC Server
(CC Client)
| Registration | AA request/answer(accounting,cc or both)|
|<----------------->|<------------------>| |
| : | | |
| : | | |
| Service Request | | |
|------------------>| | |
| | CCR(Initial,Credit-Control AVPs, |
| | QoS-capability) |
| +|---------------------------------------->|
| CC stream|| | CCA(Granted-Units)|
| || | QoS-Resources |
| +|<----------------------------------------|
| Service Delivery | | |
|<----------------->| ACR(start,Accounting AVPs) |
| : |------------------->|+ |
| : | ACA || Accounting stream |
| |<-------------------|+ |
| : | | |
| : | | |
| | CCR(Update,Used-Units) |
| |---------------------------------------->|
| | | CCA(Granted-Units)|
| | | QoS-Resources |
| |<----------------------------------------|
| : | | |
| : | | |
| End of Service | | |
|------------------>| CCR(Termination, Used-Units) |
| |---------------------------------------->|
| | | CCA |
| |<----------------------------------------|
| | ACR(stop) | |
| |------------------->| |
| | ACA | |
| |<-------------------| |
Figure 12: Example with first interrogation after user's
authorization/authentication
5.6. Diameter Server Initiated Credit Re-authorization
This example shows a Diameter Credit Control interaction whereby the 6.5. Diameter Credit Control with QoS Information
server initiates a re-authorization exchange.
Service Element Diameter In this case the User is charged as soon as the Service Element (CC
End User (CC Client) Server CC Server client) receives the service request. In this case the client uses
| | | | the "QoS-Desired" QoS-ObjectType parameter in the QoS-Resources AVP
| | | | that it sends to the Accounitng server. The server responds with a
: : : : "QoS-Available" QoS-ObjectType parameter in the QoS-Resources AVP
: <<<<<< Initial Message Exchanges >>>>>> : Service Element
: : : : End User (CC Client) B CC Server
| | | |
| | Re-Auth-Request|
| | Auth-Application-ID = CREDIT_CONTROL|
| |Re-Auth-Request-Type = AUTHORIZE_ONLY|
| | Session-ID|
| |<------------------------------------+
| | | |
| | Re-Auth-Answer | |
| | Session-ID | |
| | Result-Code = DIAMETER_LIMITED_SUCCESS
| +------------------------------------>|
| | | | | | | |
| | CCR | |(1) Service Request | | |
| | CC-Request-Type = UPDATE_REQUEST | |-------------------->| | |
| | Used-Units | | | |(2) CCR (event, DIRECT_DEBITING,|
| |-------------------+---------------->| | | QoS-Resources[QoS-desired]) |
| | CCA(Granted-Units)| | |-------------------------------->|
| | Result-Code = DIAMETER_SUCCESS| | |(3) CCA (Granted-Units, QoS- |
| | QoS-Resources| | | Resources[QoS-Authorized]) |
| |<------------------+-----------------| | |<--------------------------------|
|(4) Service Delivery | | |
|<--------------------| | |
|(5) Begin service | | |
|<------------------------------------>| |
| | | | | | | |
. . . .
. . . .
Figure 13: Server-Initiated Credit Re-Authorization Figure 22: Example for a One-Time Diameter Credit Control Charging
Event
5.7. QoS and Credit-Control as Part of Authentication and Authorization
In this example, the Credit control is performed along with the
Authentication/Authorization message. This is usually the case in
NAS scenario.
Service Element Diameter
End User (CC Client) server CC Server
| (e.g. NAS) | |
| | | |
| Service Request | AA Request (CC AVPs) |
| | Credit-Control=CREDIT_AUTHORIZATION |
| | QoS-Resources | |
|------------------>|------------------->| |
| | | CCR(Initial, CC AVPs)
| | | QoS-Resources |
| | |------------------->|
| | | CCA(Granted-Units) |
| | | QoS-Resources |
| | |<-------------------|
| | AA Answer(Granted-Units) |
| | QoS-Resources | |
| Service Delivery |<-------------------| |
|<----------------->| | |
| | ACR(start,Accounting AVPs) |
| |------------------->|+ |
| | ACA || Accounting stream |
| |<-------------------|+ |
| | | |
| | | |
| | | |
| | | |
| | CCR(Update,Used-Units) |
| | QoS-Resources | CCR(Update,Used-Units)
| |------------------->| QoS-Resources |
| | |------------------->|
| | | CCA(Granted-Units) |
| | | QoS-Resources |
| | CCA(Granted-Units) |<-------------------|
| | QoS-Resources | |
| |<-------------------| |
| | | |
| | | |
| End of Service | | |
|------------------>| CCR(Termination,Used-Units) |
| |------------------->| CCR(Term.,Used-Units)
| | |------------------->|
| | | CCA |
| | CCA |<-------------------|
| |<-------------------| |
| | ACR(stop) | |
| |------------------->| |
| | ACA | |
| |<-------------------| |
Figure 14: Example with use of the authorization messages for the
first Diameter Credit Control interrogation
6. AVP Occurrence Tables 7. AVP Occurrence Tables
6.1. DER and DEA Commands AVP Table 7.1. DER and DEA Commands AVP Table
The following table lists the Quality of Service specific AVPs The following table lists the Quality of Service specific AVPs
defined in this document that may be present in the DER and DEA defined in this document that may be present in the DER and DEA
Commands, as defined in this document and in [RFC4072]. Commands, as defined in this document and in [RFC4072].
+---------------+ +---------------+
| Command-Code | | Command-Code |
|-------+-------+ |-------+-------+
Attribute Name | DER | DEA | Attribute Name | DER | DEA |
-------------------------------+-------+-------+ -------------------------------+-------+-------+
QoS-Capability | 0-1 | 0 | QoS-Capability | 0-1 | 0 |
QoS-Resources | 0+ | 0+ | QoS-Resources | 0+ | 0+ |
+-------+-------+ +-------+-------+
Figure 15: DER and DEA Commands AVP table Figure 23: DER and DEA Commands AVP table
6.2. CCR and CCA Commands AVP Table 7.2. CCR and CCA Commands AVP Table
The following table lists the Quality of Service specific AVPs The following table lists the Quality of Service specific AVPs
defined in this document that may be present in the CCR and CCA defined in this document that may be present in the CCR and CCA
Commands, as defined in this document and in [RFC4006]. Commands, as defined in this document and in [RFC4006].
+---------------+ +---------------+
| Command-Code | | Command-Code |
|-------+-------+ |-------+-------+
Attribute Name | CCR | CCA | Attribute Name | CCR | CCA |
-------------------------------+-------+-------+ -------------------------------+-------+-------+
QoS-Capability | 0-1 | 0 | QoS-Capability | 0-1 | 0 |
QoS-Resources | 0+ | 0+ | QoS-Resources | 0+ | 0+ |
+-------+-------+ +-------+-------+
Figure 16: CCR and CCA Commands AVP table Figure 24: CCR and CCA Commands AVP table
6.3. AAR and AAA Commands AVP Table 7.3. AAR and AAA Commands AVP Table
The following table lists the Quality of Service specific AVPs The following table lists the Quality of Service specific AVPs
defined in this document that may be present in the AAR and AAA defined in this document that may be present in the AAR and AAA
Commands, as defined in this document and in [RFC4005]. Commands, as defined in this document and in [RFC4005].
+---------------+ +---------------+
| Command-Code | | Command-Code |
|-------+-------+ |-------+-------+
Attribute Name | AAR | AAA | Attribute Name | AAR | AAA |
-------------------------------+-------+-------+ -------------------------------+-------+-------+
QoS-Capability | 0-1 | 0 | QoS-Capability | 0-1 | 0 |
QoS-Resources | 0+ | 0+ | QoS-Resources | 0+ | 0+ |
+-------+-------+ +-------+-------+
Figure 17: AAR and AAA Commands AVP table Figure 25: AAR and AAA Commands AVP table
7. Diameter RADIUS Interoperability
[Editor's Note: Text will be provided in a future version of this
document.]
8. Acknowledgments 8. Acknowledgments
We would like to thank Victor Fajardo for his comments. We would like to thank Victor Fajardo, Tseno Tsenov, Robert Hancock,
Jukka Manner, Cornelia Kappler, Xiaoming Fu, Frank Alfano, Avi Lior,
Tolga Asveren, Mike Montemurro, Glen Zorn, Avri Doria, Dong Sun, Tina
Tsou, Pete McCann, Georgios Karagiannis and Elwyn Davies for their
comments.
9. IANA Considerations 9. IANA Considerations
Diameter reserves the AVP Codes 0 - 255 for RADIUS functions that are This specification requests IANA to assignment of new AVPs from the
implemented in Diameter. AVPs new to Diameter have code values of AVP Code namespace defined in RFC 3588 [RFC3588]. Section 4 lists
256 and greater. the newly defined AVPs.
This specification assigns the values TBD-1 to TBD-2 from the AVP IANA is requested to allocate a registry for the QoS-ObjectType. The
Code namespace defined in RFC 3588 [RFC3588]. See Section 4 for the following values are allocated by this specification.
newly defined AVPs.
This specification also specifies the use of AVPs in the 0 - 255 (0): QoS-Desired
range, which are defined in 'RADIUS Types', see (1): QoS-Available
http://www.iana.org/assignments/radius-types. These values are (2): QoS-Reserved
assigned by the policy in Section 6 of RFC 2865 [RFC2865] and are (3): Minimum-QoS
amended by RFC 3575 [RFC3575]. (4): QoS-Authorized
A specification is required to add a new value to the registry. A
standards track document is required to depreciate, delete, or modify
existing values.
IANA is requested to allocate a registry for the QoS-Flow-State. The
following values are allocated by this specification.
Value | Name
------+------------------------------------------------------------
0 | QOS_FLOW_STATE_PENDING
A specification is required to add a new value to the registry. A
standards track document is required to depreciate, delete, or modify
existing values.
IANA is requested to allocate a registry for the QoS-Flow-Direction.
The following values are allocated by this specification.
Value | Name
------+------------------------------------------------------------
0 | QOS_FLOW_DIRECTION_BOTH
1 | QOS_FLOW_DIRECTION_DL
2 | QOS_FLOW_DIRECTION_UL
A specification is required to add a new value to the registry. A
standards track document is required to depreciate, delete, or modify
existing values.
10. Security Considerations 10. Security Considerations
This document describes the extension of Diameter for conveying This document describes the extension of Diameter for conveying
Quality of Service information. The security considerations of the Quality of Service information. The security considerations of the
Diameter protocol itself have been discussed in RFC 3588 [RFC3588]. Diameter protocol itself have been discussed in RFC 3588 [RFC3588].
Use of the AVPs defined in this document MUST take into consideration Use of the AVPs defined in this document MUST take into consideration
the security issues and requirements of the Diameter Base protocol. the security issues and requirements of the Diameter Base protocol.
11. References 11. References
skipping to change at page 21, line 23 skipping to change at page 21, line 21
June 2007. June 2007.
[I-D.ietf-radext-filter-rules] [I-D.ietf-radext-filter-rules]
Congdon, P., "RADIUS Attributes for Filtering and Congdon, P., "RADIUS Attributes for Filtering and
Redirection", draft-ietf-radext-filter-rules-03 (work in Redirection", draft-ietf-radext-filter-rules-03 (work in
progress), July 2007. progress), July 2007.
[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.
[RFC3575] Aboba, B., "IANA Considerations for RADIUS (Remote [RFC2234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Authentication Dial In User Service)", RFC 3575, Specifications: ABNF", RFC 2234, November 1997.
July 2003.
[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.
[RFC4006] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J. [RFC4006] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J.
Loughney, "Diameter Credit-Control Application", RFC 4006, Loughney, "Diameter Credit-Control Application", RFC 4006,
August 2005. August 2005.
11.2. Informative References
[I-D.ietf-nsis-qspec]
Ash, J., "QoS NSLP QSPEC Template",
draft-ietf-nsis-qspec-17 (work in progress), July 2007.
[RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,
"Remote Authentication Dial In User Service (RADIUS)",
RFC 2865, June 2000.
[RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible [RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible
Authentication Protocol (EAP) Application", RFC 4072, Authentication Protocol (EAP) Application", RFC 4072,
August 2005. August 2005.
11.2. Informative References
Authors' Addresses Authors' Addresses
Jouni Korhonen (editor) Jouni Korhonen (editor)
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
Otto-Hahn-Ring 6 Otto-Hahn-Ring 6
Munich, Bavaria 81739 Munich, Bavaria 81739
Germany Germany
Email: Hannes.Tschofenig@nsn.com Email: Hannes.Tschofenig@nsn.com
URI: http://www.tschofenig.com URI: http://www.tschofenig.com
Mayutan Arumaithurai Mayutan Arumaithurai
 End of changes. 77 change blocks. 
356 lines changed or deleted 370 lines changed or added

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