draft-ietf-dime-qos-attributes-03.txt   draft-ietf-dime-qos-attributes-04.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: May 21, 2008 M. Arumaithurai Expires: July 24, 2008 M. Arumaithurai
University of Goettingen University of Goettingen
M. Jones M. Jones
Bridgewater Systems Bridgewater Systems
November 18, 2007 January 21, 2008
Quality of Service Attributes for Diameter Quality of Service Attributes for Diameter
draft-ietf-dime-qos-attributes-03.txt draft-ietf-dime-qos-attributes-04.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 39 skipping to change at page 1, line 39
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 May 21, 2008. This Internet-Draft will expire on July 24, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document extends the QoSFilterRule AVP functionality of the This document extends the QoSFilterRule 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 Diameter applications where permitted by the command ABNF existing Diameter applications where permitted by the command ABNF
and to all new applications. and to all new applications.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Diameter QoS Defined AVPs . . . . . . . . . . . . . . . . . . 3 3. Diameter QoS Defined AVPs . . . . . . . . . . . . . . . . . . 3
3.1. QoS-Capability AVP . . . . . . . . . . . . . . . . . . . . 3 3.1. QoS-Capability AVP . . . . . . . . . . . . . . . . . . . . 3
3.2. QoS-Profile-Template AVP . . . . . . . . . . . . . . . . . 4 3.2. QoS-Profile-Template AVP . . . . . . . . . . . . . . . . . 4
3.3. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 4 3.3. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 4
3.4. Extended-QoS-Filter-Rule AVP . . . . . . . . . . . . . . . 5 3.4. Extended-QoS-Filter-Rule AVP . . . . . . . . . . . . . . . 5
3.5. QoS-Profile AVP . . . . . . . . . . . . . . . . . . . . . 5 3.5. QoS-Semantics . . . . . . . . . . . . . . . . . . . . . . 5
3.6. QoS-Profile-ID AVP . . . . . . . . . . . . . . . . . . . . 5 3.6. QoS-Parameters AVP . . . . . . . . . . . . . . . . . . . . 5
3.7. QoS-Semantics . . . . . . . . . . . . . . . . . . . . . . 5 3.7. QoS-Rule-Precedence AVP . . . . . . . . . . . . . . . . . 5
3.8. QoS-Parameters AVP . . . . . . . . . . . . . . . . . . . . 6 3.8. QoS-Flow-State AVP . . . . . . . . . . . . . . . . . . . . 6
3.9. QoS-Flow-State AVP . . . . . . . . . . . . . . . . . . . . 6 3.9. QoS-Flow-Direction AVP . . . . . . . . . . . . . . . . . . 6
3.10. QoS-Flow-Direction AVP . . . . . . . . . . . . . . . . . . 6 4. Semantics of QoS Parameters . . . . . . . . . . . . . . . . . 6
4. Semantics of QoS Parameters . . . . . . . . . . . . . . . . . 7 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 5.1. Diameter EAP with QoS Information . . . . . . . . . . . . 7
5.1. Diameter EAP with QoS Information . . . . . . . . . . . . 8
5.2. Diameter NASREQ with QoS Information . . . . . . . . . . . 9 5.2. Diameter NASREQ with QoS Information . . . . . . . . . . . 9
5.3. QoS Authorization . . . . . . . . . . . . . . . . . . . . 10 5.3. QoS Authorization . . . . . . . . . . . . . . . . . . . . 10
5.4. Diameter Server Initiated Re-authorization of QoS . . . . 11 5.4. Diameter Server Initiated Re-authorization of QoS . . . . 10
5.5. Diameter Credit Control with QoS Information . . . . . . . 12 5.5. Diameter Credit Control with QoS Information . . . . . . . 11
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
8. Security Considerations . . . . . . . . . . . . . . . . . . . 14 8. Security Considerations . . . . . . . . . . . . . . . . . . . 13
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
9.1. Normative References . . . . . . . . . . . . . . . . . . . 14 9.1. Normative References . . . . . . . . . . . . . . . . . . . 13
9.2. Informative References . . . . . . . . . . . . . . . . . . 15 9.2. Informative References . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
Intellectual Property and Copyright Statements . . . . . . . . . . 16 Intellectual Property and Copyright Statements . . . . . . . . . . 15
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 Diameter applications where related AVPs that can be used in existing Diameter applications where
permitted by the command ABNF and in all new applications. The permitted by the command ABNF and in all new applications. The
Extended-QoS-Filter-Rule AVP thereby replaces the QoSFilterRule, Extended-QoS-Filter-Rule AVP thereby replaces the QoSFilterRule,
defined in RFC 3588 [RFC3588], and the QoS-Filter-Rule, defined in defined in RFC 3588 [RFC3588], and the QoS-Filter-Rule, defined in
RFC 4005 [RFC4005]. RFC 4005 [RFC4005].
skipping to change at page 3, line 36 skipping to change at page 3, line 36
+------------------+ +------------------+
| 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-Capability TBD 3.1 Grouped | |M,P| | V | |QoS-Capability TBD 3.1 Grouped | |M,P| | V |
|QoS-Profile-Template TBD 3.2 Unsigned64 | |M,P| | V | |QoS-Profile-Template TBD 3.2 Unsigned64 | |M,P| | V |
|QoS-Resources TBD 3.3 Grouped | |M,P| | V | |QoS-Resources TBD 3.3 Grouped | |M,P| | V |
|Extended-QoS-Filter-Rule TBD 3.4 Grouped | |M,P| | V | |Extended-QoS-Filter-Rule TBD 3.4 Grouped | |M,P| | V |
|QoS-Profile TBD 3.5 Grouped | |M,P| | V | |QoS-Semantics TBD 3.5 Enumerated | |M,P| | V |
|QoS-Profile-ID TBD 3.6 Unsigned32 | |M,P| | V | |QoS-Parameters TBD 3.6 OctetString| |M,P| | V |
|QoS-Semantics TBD 3.7 Enumerated | |M,P| | V | |QoS-Rule-Precedence TBD 3.7 Unsigned32 | |M,P| | V |
|QoS-Parameters TBD 3.8 OctetString| |M,P| | V | |QoS-Flow-State TBD 3.8 Enumerated | |M,P| | V |
|QoS-Flow-State TBD 3.9 Enumerated | |M,P| | V | |QoS-Flow-Direction TBD 3.9 Enumerated | |M,P| | V |
|QoS-Flow-Direction TBD 3.10 Enumerated | |M,P| | V |
+-------------------------------------------------+----+---+----+----+ +-------------------------------------------------+----+---+----+----+
3.1. QoS-Capability AVP 3.1. QoS-Capability AVP
The QoS-Capability AVP (AVP Code TBD) is of type Grouped and contains The QoS-Capability AVP (AVP Code TBD) is of type Grouped and contains
a list of supported Quality of Service profile templates (and a list of supported Quality of Service profile templates (and
therefore the support of the respective parameter AVPs). therefore the support of the respective parameter AVPs).
QoS-Capability ::= < AVP Header: XXX > QoS-Capability ::= < AVP Header: XXX >
1* { QoS-Profile-Template } 1* { QoS-Profile-Template }
skipping to change at page 4, line 46 skipping to change at page 4, line 46
templates is created with the same document. templates is created with the same document.
3.3. QoS-Resources AVP 3.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
a description of the Quality of Service resources for policing a description of the Quality of Service resources for policing
traffic flows. traffic flows.
QoS-Resources ::= < AVP Header: XXX > QoS-Resources ::= < AVP Header: XXX >
0* [ Extended-QoS-Filter-Rule ] 0* [ Extended-QoS-Filter-Rule ]
[ QoS-Profile ]
[ QoS-Flow-State ] [ QoS-Flow-State ]
* [ AVP ] * [ AVP ]
3.4. Extended-QoS-Filter-Rule AVP 3.4. Extended-QoS-Filter-Rule AVP
The Extended-QoS-Filter-Rule AVP (AVP Code TBD) is of type Grouped The Extended-QoS-Filter-Rule AVP (AVP Code TBD) is of type Grouped
and defines one or more traffic flows together with the QoS profile and defines one or more traffic flows together with a set of QoS
that should be applied to the flow(s) by the Resource Management parameters that should be applied to the flow(s) by the Resource
Function. This AVP re-uses the RADIUS NAS-Traffic-Rule AVP Management Function. This AVP re-uses the RADIUS NAS-Traffic-Rule
[I-D.ietf-radext-filter-rules] to describe traffic flows. The AVP [I-D.ietf-radext-filter-rules] to describe traffic flows. At
Extended-QoS-Filter-Rule AVP ties a specific traffic filter to a QoS- least either one of the NAS-Traffic-Rule or the QoS-Flow-Direction
Profile-ID that in turn refers to a specific set of QoS parameters.
At least either one of the NAS-Traffic-Rule or the QoS-Flow-Direction
AVPs SHOULD be included. AVPs SHOULD be included.
Extended-QoS-Filter-Rule ::= < AVP Header: XXX > Extended-QoS-Filter-Rule ::= < AVP Header: XXX >
[ QoS-Profile-ID ]
[ NAS-Traffic-Rule ]
[ QoS-Flow-Direction ]
* [ AVP ]
3.5. QoS-Profile AVP
The QoS-Profile AVP (AVP Code TBD) is of type Grouped and ties the
QoS-Profile-ID AVP to a set of QoS-Parameters AVPs. All parameters
refer to the same QoS model/profile described by the QoS-Profile-
Template AVP.
QoS-Profile ::= < AVP Header: XXX >
[ QoS-Profile-ID ]
{ QoS-Semantics } { QoS-Semantics }
{ QoS-Profile-Template } { QoS-Profile-Template }
[ QoS-Parameters ] [ QoS-Parameters ]
[ QoS-Rule-Precedence ]
[ NAS-Traffic-Rule ]
[ QoS-Flow-Direction ]
* [ AVP ] * [ AVP ]
3.6. QoS-Profile-ID AVP 3.5. QoS-Semantics
The QoS-Profile-ID AVP (AVP Code TBD) is of type Unsigned32 and
references a set of QoS-Parameters AVPs.
3.7. QoS-Semantics
The QoS-Semantics AVP (AVP Code TBD) is of type Enumerated and The QoS-Semantics AVP (AVP Code TBD) is of type Enumerated and
provides the semantics for the content of the QoS-Profile AVP. provides the semantics for the QoS-Profile-Template and QoS-
Parameters AVPs in the Extended-QoS-Filter-Rule AVP.
This document defines the following values: This document defines the following values:
(0): QoS-Desired (0): QoS-Desired
(1): QoS-Available (1): QoS-Available
(2): QoS-Reserved (2): QoS-Reserved
(3): Minimum-QoS (3): Minimum-QoS
(4): QoS-Authorized (4): QoS-Authorized
3.8. QoS-Parameters AVP 3.6. QoS-Parameters AVP
The QoS-Parameters AVP (AVP Code TBD) is of type OctetString and The QoS-Parameters AVP (AVP Code TBD) is of type OctetString and
contains Quality of Service parameters. These parameters are defined contains Quality of Service parameters. These parameters are defined
in a separate document, see [I-D.ietf-dime-qos-parameters]. in a separate document, see [I-D.ietf-dime-qos-parameters].
3.9. QoS-Flow-State AVP 3.7. QoS-Rule-Precedence AVP
The QoS-Rule-Precedence AVP (AVP Code TBD) is of type Unsigned32 and
specifies the execution order of the rules expressed in the QoS-
Resources AVP. Rules with equal precedence MAY be executed in
parallel if supported by the Resource Management Function. If the
QoS-Rule-Precedence AVP is absent from the Extended-QoS-Filter-Rule
AVP, the rules SHOULD be executed in the order in which they appear
in the QoS-Resources AVP.
3.8. QoS-Flow-State AVP
The QoS-Flow-State AVP (AVP Code TBD) is of type Enumerated. It 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 gives an indication as to how the flow has to be treated. The
Extended-QoS-Filter-Rule already provides an indicate whether a flow Extended-QoS-Filter-Rule already provides an indicate whether a flow
is permitted or denied. This optional AVP provides additional is permitted or denied. This optional AVP provides additional
information about the treatment. Currently, a single value is information about the treatment. Currently, a single value is
defined; further values are available via IANA registration. defined; further values are available via IANA registration.
Value | Name and Semantic Value | Name and Semantic
------+------------------------------------------------------------ ------+------------------------------------------------------------
0 | QOS_FLOW_STATE_PENDING - The QoS reservation is kept 0 | QOS_FLOW_STATE_PENDING - The QoS reservation is kept
| pending. The QoS resources are not installed and subsequent | pending. The QoS resources are not installed and subsequent
| QoS signaling is necessary to active them. | QoS signaling is necessary to active them.
3.10. QoS-Flow-Direction AVP 3.9. QoS-Flow-Direction AVP
The QoS-Flow-Direction AVP (AVP Code TBD) is of type Enumerated. It The QoS-Flow-Direction AVP (AVP Code TBD) is of type Enumerated. It
gives an indication of the direction the provided QoS information gives an indication of the direction the provided QoS information
should be applied to. The QoS information can be applied to downlink 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 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 conjunction with the NAS-Traffic-Rule AVP. In a case conflicting
definitions between the QoS-Flow-Direction and the NAS-Traffic-Rule, definitions between the QoS-Flow-Direction and the NAS-Traffic-Rule,
the QoS-Flow-Direction has precedence meaning the filter rules are the QoS-Flow-Direction has precedence meaning the filter rules are
applied only to the flows going to the direction indicated by the 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 QoS-Flow-Direction AVP. In the absence of the QoS-Flow-Direction the
skipping to change at page 8, line 15 skipping to change at page 7, line 48
5. Examples 5. Examples
This section shows a number of signaling flows where QoS negotiation This section shows a number of signaling flows where QoS negotiation
and authorization is part of the conventional NASREQ, EAP or Credit and authorization is part of the conventional NASREQ, EAP or Credit
Control applications message exchanges. The signalling flows for the Control applications message exchanges. The signalling flows for the
Diameter QoS Application are described in Diameter QoS Application are described in
[I-D.ietf-dime-diameter-qos]. [I-D.ietf-dime-diameter-qos].
5.1. Diameter EAP with QoS Information 5.1. Diameter EAP with QoS Information
Figure 11 shows a simple signaling flow where a NAS (Diameter Client) Figure 10 shows a simple signaling flow where a NAS (Diameter Client)
announces its QoS awareness and capabilities included into the DER announces its QoS awareness and capabilities included into the DER
message and as part of the access authentication procedure. Upon message and as part of the access authentication procedure. Upon
completion of the EAP exchange, the Diameter Server provides a pre- completion of the EAP exchange, the Diameter Server provides a pre-
provisioned QoS profile with the QoS-Semantics in the QoS-Profile AVP provisioned QoS profile with the QoS-Semantics in the Extended-QoS-
set to "QoS-Authorized", to the NAS in the final DEA message. Filter-Rule 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 9, line 43 skipping to change at page 8, line 46
| | EAP-Payload(EAP Success) | | | EAP-Payload(EAP Success) |
| | [EAP-Master-Session-Key] | | | [EAP-Master-Session-Key] |
| | (authorization AVPs) | | | (authorization AVPs) |
| | QoS-Resources(QoS-Authorized) | | | QoS-Resources(QoS-Authorized) |
| |<-------------------------------| | |<-------------------------------|
| | | | | |
| EAP Success | | | EAP Success | |
|<-------------------------------| | |<-------------------------------| |
| | | | | |
Figure 11: Example of a Diameter EAP enhanced with QoS Information Figure 10: Example of a Diameter EAP enhanced with QoS Information
5.2. Diameter NASREQ with QoS Information 5.2. Diameter NASREQ with QoS Information
Figure 12 shows a similar pre-provisioned QoS signaling as in Figure 11 shows a similar pre-provisioned QoS signaling as in
Figure 11 but using the NASREQ application instead of EAP Figure 10 but using the NASREQ application instead of EAP
application. application.
End Diameter End Diameter
Host NAS Server Host NAS Server
| | | | | |
| Start Network | | | Start Network | |
| Attachment | | | Attachment | |
|<---------------->| | |<---------------->| |
| | | | | |
| |AA-Request | | |AA-Request |
skipping to change at page 10, line 45 skipping to change at page 9, line 51
| | AA-Answer| | | AA-Answer|
| | Result-Code=DIAMETER_SUCCESS| | | Result-Code=DIAMETER_SUCCESS|
| | (authorization AVPs)| | | (authorization AVPs)|
| |QoS-Resources(QoS-Authorized) | | |QoS-Resources(QoS-Authorized) |
| |<-----------------------------+ | |<-----------------------------+
| | | | | |
| Success | | | Success | |
|<-----------------+ | |<-----------------+ |
| | | | | |
Figure 12: Example of a Diameter NASREQ enhanced with QoS Information Figure 11: Example of a Diameter NASREQ enhanced with QoS Information
5.3. QoS Authorization 5.3. QoS Authorization
Figure 13 shows an example of authorization only QoS signaling as Figure 12 shows an example of authorization only QoS signaling as
part of the NASREQ message exchange. The NAS provides the Diameter part of the NASREQ message exchange. The NAS provides the Diameter
server with the "QoS-Desired" QoS-Semantics AVP included in the QoS- server with the "QoS-Desired" QoS-Semantics AVP included in the QoS-
Resources AVP. The Diameter server then either authorizes the Resources AVP. The Diameter server then either authorizes the
indicated QoS or rejects the request and informs the NAS about the indicated QoS or rejects the request and informs the NAS about the
result. In this scenario the NAS does not need to include the QoS- result. In this scenario the NAS does not need to include the QoS-
Capability AVP in the AAR message as the QoS-Resources AVP implicitly 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, does the same and also the NAS is authorizing a specific QoS profile,
not a pre-provisioned one. not a pre-provisioned one.
End Diameter End Diameter
skipping to change at page 11, line 33 skipping to change at page 10, line 40
| | AA-Answer| | | AA-Answer|
| | NASREQ-Payload(Success)| | | NASREQ-Payload(Success)|
| | QoS-Resources(QoS-Authorized)| | | QoS-Resources(QoS-Authorized)|
| |<-----------------------------+ | |<-----------------------------+
| Accept | | | Accept | |
|<-----------------+ | |<-----------------+ |
| | | | | |
| | | | | |
| | | | | |
Figure 13: Example of an Authorization-Only Message Flow Figure 12: Example of an Authorization-Only Message Flow
5.4. Diameter Server Initiated Re-authorization of QoS 5.4. Diameter Server Initiated Re-authorization of QoS
Figure 14 shows a message exchange for a Diameter server initiated Figure 13 shows a message exchange for a Diameter server initiated
QoS re-authorization procedure. The Diameter server sends the NAS a QoS re-authorization procedure. The Diameter server sends the NAS a
RAR message requesting re-authorization for an existing session and RAR message requesting re-authorization for an existing session and
the NAS acknowledges it with a RAA message. The NAS is aware of its 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 existing QoS profile and information for the ongoing session that the
Diameter server requested for re-authorization. Thus, the NAS must Diameter server requested for re-authorization. Thus, the NAS must
initiate re-authorization of the existing QoS profile. The re- initiate re-authorization of the existing QoS profile. The re-
authorization procedure is the same as in Figure 13. authorization procedure is the same as in Figure 12.
End Diameter End Diameter
Host NAS Server Host NAS Server
| | | | | |
| | | | | |
: : : : : :
: <<<Initial Message Exchanges>>> : : <<<Initial Message Exchanges>>> :
: : : : : :
| | | | | |
| | RA-Request | | | RA-Request |
skipping to change at page 12, line 34 skipping to change at page 11, line 34
| |QoS-Resources(QoS-Desired) | | |QoS-Resources(QoS-Desired) |
| +----------------------------->| | +----------------------------->|
| | | | | |
| | AA-Answer| | | AA-Answer|
| | Result-Code=DIAMETER_SUCCESS| | | Result-Code=DIAMETER_SUCCESS|
| | (authorization AVPs)| | | (authorization AVPs)|
| | QoS-Resources(QoS-Authorized)| | | QoS-Resources(QoS-Authorized)|
| |<-----------------------------+ | |<-----------------------------+
| | | | | |
Figure 14: Example of a Server-initiated Re-Authorization Procedure Figure 13: Example of a Server-initiated Re-Authorization Procedure
5.5. Diameter Credit Control with QoS Information 5.5. Diameter Credit Control with QoS Information
In this case the User is charged as soon as the Service Element (CC In this case the User is charged as soon as the Service Element (CC
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
skipping to change at page 13, line 23 skipping to change at page 12, line 23
| | Resources[QoS-Authorized]) | | | Resources[QoS-Authorized]) |
| |<--------------------------------| | |<--------------------------------|
|(4) Service Delivery | | | |(4) Service Delivery | | |
|<--------------------| | | |<--------------------| | |
|(5) Begin service | | | |(5) Begin service | | |
|<------------------------------------>| | |<------------------------------------>| |
| | | | | | | |
. . . . . . . .
. . . . . . . .
Figure 15: Example for a One-Time Diameter Credit Control Charging Figure 14: Example for a One-Time Diameter Credit Control Charging
Event Event
6. Acknowledgments 6. Acknowledgments
We would like to thank Victor Fajardo, Tseno Tsenov, Robert Hancock, We would like to thank Victor Fajardo, Tseno Tsenov, Robert Hancock,
Jukka Manner, Cornelia Kappler, Xiaoming Fu, Frank Alfano, Avi Lior, Jukka Manner, Cornelia Kappler, Xiaoming Fu, Frank Alfano, Avi Lior,
Tolga Asveren, Mike Montemurro, Glen Zorn, Avri Doria, Dong Sun, Tina Tolga Asveren, Mike Montemurro, Glen Zorn, Avri Doria, Dong Sun, Tina
Tsou, Pete McCann, Georgios Karagiannis and Elwyn Davies for their Tsou, Pete McCann, Georgios Karagiannis and Elwyn Davies for their
comments. comments.
skipping to change at page 15, line 8 skipping to change at page 14, line 8
[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.
9.2. Informative References 9.2. Informative References
[I-D.ietf-dime-diameter-qos] [I-D.ietf-dime-diameter-qos]
Zorn, G., "Diameter Quality of Service Application", Zorn, G., McCann, P., Tschofenig, H., Tsou, T., Doria, A.,
draft-ietf-dime-diameter-qos-01 (work in progress), and D. Sun, "Protocol for Diameter Quality of Service
July 2007. Application", draft-ietf-dime-diameter-qos-02 (work in
progress), November 2007.
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
skipping to change at page 16, line 7 skipping to change at page 15, line 7
Mark Jones Mark Jones
Bridgewater Systems Bridgewater Systems
303 Terry Fox Drive 303 Terry Fox Drive
Ottawa, Ontario K2K 3J1 Ottawa, Ontario K2K 3J1
Canada Canada
Email: mark.jones@bridgewatersystems.com Email: mark.jones@bridgewatersystems.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
 End of changes. 30 change blocks. 
79 lines changed or deleted 71 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/