draft-ietf-dime-diameter-qos-03.txt   draft-ietf-dime-diameter-qos-04.txt 
Network Working Group D. Sun, Ed. Network Working Group D. Sun, Ed.
Internet-Draft Alcatel-Lucent Internet-Draft Alcatel-Lucent
Intended status: Standards Track P. McCann Intended status: Standards Track P. McCann
Expires: July 26, 2008 Motorola Labs Expires: August 1, 2008 Motorola Labs
H. Tschofenig 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 G. Zorn
January 23, 2008 Aruba Networks
January 29, 2008
Diameter Quality of Service Application Diameter Quality of Service Application
draft-ietf-dime-diameter-qos-03.txt draft-ietf-dime-diameter-qos-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 42 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 July 26, 2008. This Internet-Draft will expire on August 1, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document describes framework, messages and procedures for the This document describes framework, messages and procedures for the
Diameter QoS application. The Diameter QoS application allows Diameter Quality of Service (QoS) application. The Diameter QoS
network elements to interact with Diameter servers when allocating application allows network elements to interact with Diameter servers
QoS resources in the network. In particular, two modes of operation when allocating QoS resources in the network. In particular, two
- Pull and Push are defined. modes of operation - Pull and Push are defined.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Framework . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3. Framework . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1. Network element functional model . . . . . . . . . . . . . 8 3.1. Network element functional model . . . . . . . . . . . . . 8
3.2. Implications of Endpoint QoS Capabilities . . . . . . . . 10 3.2. Implications of Endpoint QoS Capabilities . . . . . . . . 10
3.2.1. Category . . . . . . . . . . . . . . . . . . . . . . . 10 3.2.1. Category . . . . . . . . . . . . . . . . . . . . . . . 10
3.2.2. Interaction modes between authorizing entity and 3.2.2. Interaction modes between authorizing entity and
skipping to change at page 4, line 8 skipping to change at page 4, line 8
13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 53 13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 53
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 54 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 54
14.1. Normative References . . . . . . . . . . . . . . . . . . . 54 14.1. Normative References . . . . . . . . . . . . . . . . . . . 54
14.2. Informative References . . . . . . . . . . . . . . . . . . 54 14.2. Informative References . . . . . . . . . . . . . . . . . . 54
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 56 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 56
Intellectual Property and Copyright Statements . . . . . . . . . . 58 Intellectual Property and Copyright Statements . . . . . . . . . . 58
1. Introduction 1. Introduction
This document describes framework, messages and procedures for the This document describes framework, messages and procedures for the
Diameter QoS Application. The Diameter QoS Application allows Diameter Quality of Service (QoS) Application. The Diameter QoS
network elements (NEs) to interact with Diameter servers when Application allows network elements (NEs) to interact with Diameter
allocating QoS resources in the network. servers when allocating QoS resources in the network.
In particular, two modes of operation are defined. In the first, In particular, two modes of operation are defined. In the first,
called "Pull Mode", the network element pro-actively sends a command called "Pull Mode", the network element pro-actively sends a command
to the Diameter server for QoS authorization based on some trigger to the Diameter server for QoS authorization based on some trigger
(such as a QoS signaling protocol) that arrives along the data path. (such as a QoS signaling protocol) that arrives along the data path.
In the second, called "Push Mode", the Diameter server pro-actively In the second, called "Push Mode", the Diameter server pro-actively
sends a command to the network element(s) to install QoS sends a command to the network element(s) to install QoS
authorization state. This could be triggered, for instance, by off- authorization state. This could be triggered, for instance, by off-
path signaling such as SIP-based call control. path signaling such as SIP-based (Session Initiation Protocol) call
control.
A set of command codes pertinent to this QoS application are A set of command codes pertinent to this QoS application are
specified that allows a single Diameter application to support both specified that allows a single Diameter application to support both
Pull and Push modes based on the requirements of network Pull and Push modes based on the requirements of network
technologies, deployment scenarios and end-host's capabilities. In technologies, deployment scenarios and end-host's capabilities. In
conjunction with parameters defined in [I-D.ietf-dime-qos-attributes] conjunction with parameters defined in [I-D.ietf-dime-qos-attributes]
and in [I-D.ietf-dime-qos-parameters], this document depicts basic and in [I-D.ietf-dime-qos-parameters], this document depicts basic
call flow procedures to establish, modify and terminate a Diameter call flow procedures to establish, modify and terminate a Diameter
QoS application session. QoS application session.
skipping to change at page 9, line 5 skipping to change at page 9, line 5
naturally encompass business relationships such as those between naturally encompass business relationships such as those between
network operators and third-party application providers, enabling network operators and third-party application providers, enabling
flexible intra- or inter-domain authorization, accounting, and flexible intra- or inter-domain authorization, accounting, and
settlement. settlement.
3.1. Network element functional model 3.1. Network element functional model
Figure 2 depicts a logical operational model of resource management Figure 2 depicts a logical operational model of resource management
in a router. in a router.
+--------------------------------------------------------------+ +-------------------------------------------------------+
| DIAMETER Client | | DIAMETER Client |
| Functionality | | Functionality |
| +---------------+ +-----------------+ +---------------+ | | +---------------+ +-----------------+ +---------------+ |
| | User | | QoS Application | | Accounting | | | | User | | QoS Application | | Accounting | |
| | Authentication| | Client | | Client (e.g. | | | | Authentication| | Client | | Client (e.g. | |
| | Client | | (Authorization | |for QoS Traffic| | | | Client | | (Authorization | |for QoS Traffic| |
| +---------------+ | of QoS Requests)| +---------------+ | | +---------------+ | of QoS Requests)| +---------------+ |
| +-----------------+ | | +-----------------+ |
+--------------------------------------------------------------+ +-------------------------------------------------------+
^ ^
v v
+--------------+ +----------+ +--------------+ +----------+
|QoS Signaling | | Resource | |QoS Signaling | | Resource |
|Msg Processing|<<<<<>>>>>>>|Management| |Msg Processing|<<<<<>>>>>>>|Management|
+--------------+ +----------+ +--------------+ +----------+
. ^ | * ^ . ^ | * ^
| v . * ^ | v . * ^
+-------------+ * ^ +-------------+ * ^
|Signaling msg| * ^ |Signaling msg| * ^
skipping to change at page 22, line 25 skipping to change at page 22, line 25
Diameter message sent to the Authorizing Entity. The QAR is sent to Diameter message sent to the Authorizing Entity. The QAR is sent to
a Diameter server that can either be the home server of the QoS a Diameter server that can either be the home server of the QoS
requesting entity or an application server. requesting entity or an application server.
+----------------------------------+-------------------------------+ +----------------------------------+-------------------------------+
| QoS specific Input Data | Diameter QoS AVPs | | QoS specific Input Data | Diameter QoS AVPs |
+----------------------------------+-------------------------------+ +----------------------------------+-------------------------------+
| Authorizing entity ID (e.g., | Destination-Host | | Authorizing entity ID (e.g., | Destination-Host |
| taken from authorization token | Destination-Realm | | taken from authorization token | Destination-Realm |
| or derived based on Network | | | or derived based on Network | |
| Access ID (NAI) [RFC2486] | | | Access ID (NAI) [RFC4282] | |
| of the QoS requesting entity) | | | of the QoS requesting entity) | |
+----------------------------------+-------------------------------+ +----------------------------------+-------------------------------+
| Authorization Token | QoS-Authz-Data | | Authorization Token | QoS-Authz-Data |
| Credentials of | User-Name | | Credentials of | User-Name |
| the QoS requesting entity | | | the QoS requesting entity | |
+----------------------------------+-------------------------------+ +----------------------------------+-------------------------------+
| QoS parameters | QoS-Resources | | QoS parameters | QoS-Resources |
+----------------------------------+-------------------------------+ +----------------------------------+-------------------------------+
Authorization processing starts at the Diameter QoS server when it Authorization processing starts at the Diameter QoS server when it
skipping to change at page 57, line 13 skipping to change at page 57, line 13
Email: tena@huawei.com Email: tena@huawei.com
Avri Doria Avri Doria
Lulea University of Technology Lulea University of Technology
Arbetsvetenskap Arbetsvetenskap
Lulea, SE-97187 Lulea, SE-97187
Sweden Sweden
Email: avri@ltu.se Email: avri@ltu.se
Glen Zorn Glen Zorn
Aruba Networks
1322 Crossman Avenue
Sunnyvale, CA 94089-1113
USA
Email: glenzorn@comcast.net Email: gwz@arubanetworks.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2008). 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
 End of changes. 12 change blocks. 
16 lines changed or deleted 22 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/