draft-ietf-dime-diameter-qos-05.txt   draft-ietf-dime-diameter-qos-06.txt 
Diameter Maintenance and D. Sun, Ed. Diameter Maintenance and D. Sun, Ed.
Extensions (DIME) Alcatel-Lucent Extensions (DIME) Alcatel-Lucent
Internet-Draft P. McCann Internet-Draft P. McCann
Intended status: Standards Track Motorola Labs Intended status: Standards Track Motorola Labs
Expires: August 25, 2008 H. Tschofenig Expires: January 14, 2009 H. Tschofenig
Nokia Siemens Networks Nokia Siemens Networks
T. Tsou T. Tsou
Huawei Huawei
A. Doria A. Doria
Lulea University of Technology Lulea University of Technology
G. Zorn, Ed. G. Zorn, Ed.
Aruba Networks Aruba Networks
February 22, 2008 July 13, 2008
Diameter Quality of Service Application Diameter Quality of Service Application
draft-ietf-dime-diameter-qos-05.txt draft-ietf-dime-diameter-qos-06.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 43 skipping to change at page 1, line 43
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 25, 2008. This Internet-Draft will expire on January 14, 2009.
Copyright Notice
Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document describes the framework, messages and procedures for This document describes the framework, messages and procedures for
the Diameter Quality of Service (QoS) application. The Diameter QoS the Diameter Quality of Service (QoS) application. The Diameter QoS
application allows network elements to interact with Diameter servers application allows network elements to interact with Diameter servers
when allocating QoS resources in the network. In particular, two when allocating QoS resources in the network. In particular, two
modes of operation -- Pull and Push -- are defined. modes of operation -- Pull and Push -- are defined.
Table of Contents Table of Contents
skipping to change at page 43, line 44 skipping to change at page 43, line 44
| | | | | |
/------------------+--Data Flow---------------------------\ /------------------+--Data Flow---------------------------\
\------------------+--------------------------------------/ \------------------+--------------------------------------/
| | | | | |
.-.-.-.-. SIP signaling .-.-.-.-. SIP signaling
--------- QoS NSLP signaling --------- QoS NSLP signaling
- - - - - Diameter QoS Application messages - - - - - Diameter QoS Application messages
========= Mapping of objects between QoS and AAA protocol ========= Mapping of objects between QoS and AAA protocol
Figure 22: QoS Authorization Example - Pull Mode Figure 12: QoS Authorization Example - Pull Mode
The communication starts with SIP signaling between the two end The communication starts with SIP signaling between the two end
points and the SIP server for negotiation and authorization of the points and the SIP server for negotiation and authorization of the
requested service and its parameters (see Figure 22). As a part of requested service and its parameters (see Figure 12). As a part of
the process, the SIP server verifies whether the user at Host A is the process, the SIP server verifies whether the user at Host A is
authorized to use the requested service (and potentially the ability authorized to use the requested service (and potentially the ability
to be charged for the service usage). Negotiated session parameters to be charged for the service usage). Negotiated session parameters
are provided to the end host. are provided to the end host.
Subsequently, Host A initiates a QoS signaling message towards Host Subsequently, Host A initiates a QoS signaling message towards Host
B. It sends a QoS NSLP Reserve message, in which it includes B. It sends a QoS NSLP Reserve message, in which it includes
description of the required QoS (QSPEC object) and authorization data description of the required QoS (QSPEC object) and authorization data
for negotiated service session (part of the POLICY_DATA object). for negotiated service session (part of the POLICY_DATA object).
Authorization data includes, as a minimum, the identity of the AE Authorization data includes, as a minimum, the identity of the AE
skipping to change at page 46, line 13 skipping to change at page 46, line 13
. <.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.+ | . . <.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.+ | .
| | | | | |
/------------------+-----Data Flow---------------------------\ /------------------+-----Data Flow---------------------------\
\------------------+-----------------------------------------/ \------------------+-----------------------------------------/
| | | | | |
.-.-.-.-. SIP signaling .-.-.-.-. SIP signaling
- - - - - Diameter QoS Application messages - - - - - Diameter QoS Application messages
Figure 23: QoS Authorization Example - Push Mode Figure 13: QoS Authorization Example - Push Mode
The communication starts with SIP signaling between the two end The communication starts with SIP signaling between the two end
points and the SIP server for negotiation and authorization of the points and the SIP server for negotiation and authorization of the
requested service and its parameters (see Figure 23). As a part of requested service and its parameters (see Figure 13). As a part of
the process, the SIP server verifies whether the user at Host A is the process, the SIP server verifies whether the user at Host A is
authorized to use the requested service (and potentially the ability authorized to use the requested service (and potentially the ability
to be charged for the service usage). The DQA server is triggered to to be charged for the service usage). The DQA server is triggered to
authorize the QoS request based on session parameters (i.e., SDP authorize the QoS request based on session parameters (i.e., SDP
offer), initiate a Diameter QoS authorization session and install offer), initiate a Diameter QoS authorization session and install
authorized QoS state to the Network Element via QIR message. authorized QoS state to the Network Element via QIR message.
The DQA server may obtain the info of peer DQA client from pre- The DQA server may obtain the info of peer DQA client from pre-
configured information or query the DNS based on Host A's identity or configured information or query the DNS based on Host A's identity or
IP address (In this case a DQA server is co-located with a SIP server IP address (In this case a DQA server is co-located with a SIP server
skipping to change at page 52, line 10 skipping to change at page 52, line 10
The authors would like to thank Tseno Tsenov and Frank Alfano for The authors would like to thank Tseno Tsenov and Frank Alfano for
starting the Diameter Quality of Service work within the IETF, for starting the Diameter Quality of Service work within the IETF, for
your significant draft contributions and for being the driving force your significant draft contributions and for being the driving force
for the first few draft versions. for the first few draft versions.
14. References 14. References
14.1. Normative References 14.1. Normative References
[I-D.ietf-dime-qos-attributes] [I-D.ietf-dime-qos-attributes]
Korhonen, J., Tschofenig, H., Arumaithurai, M., and M. Korhonen, J., Tschofenig, H., Arumaithurai, M., Jones, M.,
Jones, "Quality of Service Attributes for Diameter", and A. Lior, "Quality of Service Attributes for Diameter",
draft-ietf-dime-qos-attributes-04 (work in progress), draft-ietf-dime-qos-attributes-07 (work in progress),
January 2008. June 2008.
[I-D.ietf-dime-qos-parameters] [I-D.ietf-dime-qos-parameters]
Korhonen, J. and H. Tschofenig, "Quality of Service Korhonen, J. and H. Tschofenig, "Quality of Service
Parameters for Usage with the AAA Framework", Parameters for Usage with the AAA Framework",
draft-ietf-dime-qos-parameters-01 (work in progress), draft-ietf-dime-qos-parameters-06 (work in progress),
September 2007. May 2008.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. [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.
skipping to change at page 54, line 32 skipping to change at page 54, line 32
Phone: +1 847 576 3440 Phone: +1 847 576 3440
Email: pete.mccann@motorola.com Email: pete.mccann@motorola.com
Hannes Tschofenig Hannes Tschofenig
Nokia Siemens Networks Nokia Siemens Networks
Linnoitustie 6 Linnoitustie 6
Espoo 02600 Espoo 02600
Finland Finland
Phone: +358 (50) 4871445 Phone: +358 (50) 4871445
Email: Hannes.Tschofenig@nsn.com Email: Hannes.Tschofenig@gmx.net
URI: http://www.tschofenig.com URI: http://www.tschofenig.priv.at
Tina Tsou Tina Tsou
Huawei Huawei
Shenzhen, Shenzhen,
P.R.C P.R.C
Email: tena@huawei.com Email: tena@huawei.com
Avri Doria Avri Doria
Lulea University of Technology Lulea University of Technology
Arbetsvetenskap Arbetsvetenskap
skipping to change at page 56, line 44 skipping to change at line 2173
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 12 change blocks. 
20 lines changed or deleted 16 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/