draft-ietf-dime-priority-avps-04.txt   draft-ietf-dime-priority-avps-05.txt 
Diameter Maintenance and K. Carlberg, Ed. Diameter Maintenance and K. Carlberg, Ed.
Extensions (DIME) G11 Extensions (DIME) G11
Internet-Draft T. Taylor Internet-Draft T. Taylor
Intended status: Standards Track Huawei Technologies Intended status: Standards Track Huawei Technologies
July 5, 2011 Oct 31, 2011
Diameter Priority Attribute Value Pairs Diameter Priority Attribute Value Pairs
draft-ietf-dime-priority-avps-04.txt draft-ietf-dime-priority-avps-05.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 Task Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF). Note that other groups may also distribute working Force (IETF). Note that other groups may also distribute working
documents as Internet-Drafts. The list of current Internet-Drafts is at documents as Internet-Drafts. The list of current Internet-Drafts is at
http://datatracker.ietf.org/drafts/current/. http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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 material time. It is inappropriate to use Internet-Drafts as reference material
or to cite them other than as "work in progress." or to cite them other than as "work in progress."
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the document Copyright (c) 2011 IETF Trust and the persons identified as the
authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions
Relating to IETF Documents in effect on the date of publication of this
document (http://trustee.ietf.org/license-info). Please review these
documents carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this document
must include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions This document is subject to BCP 78 and the IETF Trust's Legal Provisions
Relating to IETF Documents (http://trustee.ietf.org/license-info) in Relating to IETF Documents (http://trustee.ietf.org/license-info) in
effect on the date of publication of this document. Please review these effect on the date of publication of this document. Please review these
documents carefully, as they describe your rights and restrictions with documents carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this document respect to this document. Code Components extracted from this document
must include Simplified BSD License text as described in Section 4.e of must include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November 10,
2008. The person(s) controlling the copyright in some of this material
may not have granted the IETF Trust the right to allow modifications of
such material outside the IETF Standards Process. Without obtaining an
adequate license from the person(s) controlling the copyright in such
materials, this document may not be modified outside the IETF Standards
Process, and derivative works of it may not be created outside the IETF
Standards Process, except to format it for publication as an RFC or to
translate it into languages other than English.
Abstract Abstract
This document defines Attribute-Value Pair (AVP) containers for various This document defines Attribute-Value Pair (AVP) containers for various
priority parameters for use with Diameter and the AAA framework. The priority parameters for use with Diameter and the AAA framework. The
parameters themselves are defined in several different protocols that parameters themselves are defined in several different protocols that
operate at either the network or application layer. operate at either the network or application layer.
1. Introduction 1. Introduction
This document defines a number of Attribute-Value Pairs (AVP) that can This document defines a number of Attribute-Value Pairs (AVP) that can
skipping to change at page 6, line 14 skipping to change at page 6, line 14
4.2. QoS Profile 4.2. QoS Profile
IANA is requested to allocate a new value from the Authentication, IANA is requested to allocate a new value from the Authentication,
Authorization, and Accounting (AAA) Parameters/QoS Profile registry Authorization, and Accounting (AAA) Parameters/QoS Profile registry
defined in [RFC5624] for the QoS profile defined in this document. The defined in [RFC5624] for the QoS profile defined in this document. The
name of the profile is "Resource priority parameters". name of the profile is "Resource priority parameters".
5. Security Considerations 5. Security Considerations
This document describes the extension of Diameter for conveying Quality This document describes an extension for conveying Quality of Service
of Service information. The security considerations of the Diameter information, and therefore follows the same security considerations of
protocol itself have been discussed in [I-D.ietf-dime-rfc3588bis]. Use the Diameter QoS Application [RFC5866]. The values placed in the AVPs
of the AVPs defined in this document MUST take into consideration the are not changed by this draft, nor are they changed in the Diameter QoS
security issues and requirements of the Diameter base protocol. application. The consequences of changing values in the Priority
AVPs may result in an allocation of additional or less resources. If local
policy exists and values placed in the AVPs do not have integrity protection
(e.g., the use of S/MIME with the SIP RPH, or an INTEGRITY object within
a POLICY_DATA object), then changes and their consequences may occur.
Otherwise, integrity protected values SHOULD be ignored with appropriate
protocol specific error messages sent back upstream. Note that we do not
use the term "MUST be ignored" because local policy of an administrative
domain associated with other protocols acts as the final arbiter.
The security considerations of the Diameter protocol itself are discussed
in [I-D.ietf-dime-rfc3588bis]. Use of the AVPs defined in this document
MUST take into consideration the security issues and requirements of the
Diameter base protocol.
The authors also recommend that readers should familiarize themselves The authors also recommend that readers should familiarize themselves
with the security considerations of the various protocols listed in with the security considerations of the various protocols listed in the
the Normative References listed below. Normative References. This is because values placed in the AVPs defined
in this draft are set/changed by other protocols.
6. Acknowledgements 6. Acknowledgements
We would like to thank Lionel Morand, Janet Gunn, Piers O'Hanlon for the We would like to thank Lionel Morand, Janet Gunn, Piers O'Hanlon for the
commenst on the draft, and Lars Eggert, Jan Engelhardt, Francois commenst on the draft, and Lars Eggert, Jan Engelhardt, Francois
LeFaucheur, John Loughney, An Nguyen, Dave Oran, James Polk, Martin LeFaucheur, John Loughney, An Nguyen, Dave Oran, James Polk, Martin
Stiemerling, and Magnus Westerlund for their help with resolving Stiemerling, and Magnus Westerlund for their help with resolving
problems regarding the Admission Priority and the ALRP parameter. problems regarding the Admission Priority and the ALRP parameter.
7. References 7. References
 End of changes. 6 change blocks. 
20 lines changed or deleted 36 lines changed or added

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