draft-ietf-dime-diameter-qos-12.txt   draft-ietf-dime-diameter-qos-13.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: April 25, 2010 H. Tschofenig Expires: April 29, 2010 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.
Network Zen Network Zen
October 22, 2009 October 26, 2009
Diameter Quality of Service Application Diameter Quality of Service Application
draft-ietf-dime-diameter-qos-12.txt draft-ietf-dime-diameter-qos-13.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 41 skipping to change at page 1, line 41
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 April 25, 2010. This Internet-Draft will expire on April 29, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 18, line 44 skipping to change at page 18, line 44
Dynamic Authorization Dynamic Authorization
It MUST be possible for the Diameter QoS application to push It MUST be possible for the Diameter QoS application to push
updates towards the NE(s) from authorizing entities. updates towards the NE(s) from authorizing entities.
Bearer Gating Bearer Gating
The Diameter QoS application MUST allow the AE to gate (i.e., The Diameter QoS application MUST allow the AE to gate (i.e.,
enable/disable) authorized application flows based on, e.g., enable/disable) authorized application flows based on, e.g.,
application state transitions. application state transitions.
Accounting Records Accounting Records
The Diameter QoS application may define QoS accounting records The Diameter QoS application MAY define QoS accounting records
containing duration, volume (byte count) usage information and containing duration, volume (byte count) usage information and
description of the QoS attributes (e.g., bandwidth, delay, loss description of the QoS attributes (e.g., bandwidth, delay, loss
rate) that were supported for the flow. rate) that were supported for the flow.
Sending Accounting Records Sending Accounting Records
The NE SHOULD be able to send accounting records for a particular The NE SHOULD be able to send accounting records for a particular
QoS reservation state to an accounting entity. QoS reservation state to an accounting entity.
Failure Notification Failure Notification
The Diameter QoS application MUST allow the NE to report failures, The Diameter QoS application MUST allow the NE to report failures,
such as loss of connectivity due to movement of a mobile node or such as loss of connectivity due to movement of a mobile node or
other reasons for packet loss, to the authorizing entity. other reasons for packet loss, to the authorizing entity.
Accounting Correlation Accounting Correlation
The Diameter QoS application may support the exchange of The Diameter QoS application MAY support the exchange of
sufficient information to allow for correlation between accounting sufficient information to allow for correlation between accounting
records generated by the NEs and accounting records generated by records generated by the NEs and accounting records generated by
an AppS. an AppS.
Interaction with other AAA Applications Interaction with other AAA Applications
Interaction with other AAA applications such as Diameter Network Interaction with other AAA applications such as Diameter Network
Access (NASREQ) application [RFC4005] is required for exchange of Access (NASREQ) application [RFC4005] is REQUIRED for exchange of
authorization, authentication and accounting information. authorization, authentication and accounting information.
In deployment scenarios where authentication of the QoS reservation In deployment scenarios where authentication of the QoS reservation
requesting entity (e.g., the user) is done by means outside the requesting entity (e.g., the user) is done by means outside the
Diameter QoS application protocol interaction, the AE is contacted Diameter QoS application protocol interaction, the AE is contacted
only with a request for QoS authorization. Authentication might have only with a request for QoS authorization. Authentication might have
taken place already via the interaction with the Diameter NASREQ taken place already via the interaction with the Diameter NASREQ
application or as part of the QoS signaling protocol (e.g., Transport application or as part of the QoS signaling protocol (e.g., Transport
Layer Security (TLS) [RFC5246] in the General Internet Signaling Layer Security (TLS) [RFC5246] in the General Internet Signaling
Transport (GIST) protocol [I-D.ietf-nsis-ntlp]). Transport (GIST) protocol [I-D.ietf-nsis-ntlp]).
skipping to change at page 50, line 8 skipping to change at page 50, line 8
Code Value Name Reference Code Value Name Reference
----------------------------------------------------------- -----------------------------------------------------------
TBD QoS-Authorization-Request (QAR) Section 5.1 TBD QoS-Authorization-Request (QAR) Section 5.1
TBD QoS-Authorization-Answer (QAA) Section 5.2 TBD QoS-Authorization-Answer (QAA) Section 5.2
TBD QoS-Install-Request (QIR) Section 5.3 TBD QoS-Install-Request (QIR) Section 5.3
TBD QoS-Install-Answer (QIA) Section 5.4 TBD QoS-Install-Answer (QIA) Section 5.4
11. Security Considerations 11. Security Considerations
This document describes a mechanism for performing authorization of a This document describes a mechanism for performing authorization of a
QoS reservation at a third party entity. Therefore, sufficient QoS reservation at a third party entity. The Authorizing Entity
information needs to be made available to the Authorizing Entity to needs sufficient information to make such an authorization decision.
make such an authorization decision. Information may come from Information may come from various sources, including the application
various sources, including the application layer signaling, the layer signaling, the Diameter protocol (with its security
Diameter protocol (with its security mechanisms), from policy mechanisms), from policy information stored available with a AAA
information stored available with a AAA server and from a QoS server and from a QoS signaling protocol.
signaling protocol.
Below there is a discussion about considerations for the Diameter QoS Below there is a discussion about considerations for the Diameter QoS
interaction between an Authorizing Entity and a Network Element. interaction between an Authorizing Entity and a Network Element.
Security between the Authorizing Entity and the Network Element has a Security between the Authorizing Entity and the Network Element has a
number of components: authentication, authorization, integrity and number of components: authentication, authorization, integrity and
confidentiality. confidentiality.
Authentication refers to confirming the identity of an originator for Authentication refers to confirming the identity of an originator for
all datagrams received from the originator. Lack of authentication all datagrams received from the originator. Lack of authentication
of Diameter messages between the Authorizing Entity and the Network of Diameter messages between the Authorizing Entity and the Network
skipping to change at page 54, line 12 skipping to change at page 54, line 12
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., Jones, M., Korhonen, J., Tschofenig, H., Arumaithurai, M., Jones, M.,
and A. Lior, "Quality of Service Attributes for Diameter", and A. Lior, "Quality of Service Attributes for Diameter",
draft-ietf-dime-qos-attributes-13 (work in progress), draft-ietf-dime-qos-attributes-14 (work in progress),
July 2009. October 2009.
[I-D.ietf-dime-qos-parameters] [I-D.ietf-dime-qos-parameters]
Korhonen, J., Tschofenig, H., and E. Davies, "Quality of Korhonen, J., Tschofenig, H., and E. Davies, "Quality of
Service Parameters for Usage with Diameter", Service Parameters for Usage with Diameter",
draft-ietf-dime-qos-parameters-11 (work in progress), draft-ietf-dime-qos-parameters-11 (work in progress),
May 2009. May 2009.
[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.
[RFC4234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 4234, October 2005.
14.2. Informative References 14.2. Informative References
[I-D.ietf-nsis-ntlp] [I-D.ietf-nsis-ntlp]
Schulzrinne, H. and M. Stiemerling, "GIST: General Schulzrinne, H. and M. Stiemerling, "GIST: General
Internet Signalling Transport", draft-ietf-nsis-ntlp-20 Internet Signalling Transport", draft-ietf-nsis-ntlp-20
(work in progress), June 2009. (work in progress), June 2009.
[I-D.ietf-nsis-qos-nslp] [I-D.ietf-nsis-qos-nslp]
Manner, J., Karagiannis, G., and A. McDonald, "NSLP for Manner, J., Karagiannis, G., and A. McDonald, "NSLP for
Quality-of-Service Signaling", draft-ietf-nsis-qos-nslp-16 Quality-of-Service Signaling", draft-ietf-nsis-qos-nslp-16
 End of changes. 10 change blocks. 
19 lines changed or deleted 15 lines changed or added

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