--- 1/draft-ietf-dime-qos-parameters-03.txt 2008-05-26 14:12:11.000000000 +0200 +++ 2/draft-ietf-dime-qos-parameters-04.txt 2008-05-26 14:12:11.000000000 +0200 @@ -1,19 +1,19 @@ Diameter Maintenance and J. Korhonen, Ed. Extensions (DIME) TeliaSonera Internet-Draft H. Tschofenig Intended status: Standards Track Nokia Siemens Networks -Expires: August 28, 2008 February 25, 2008 +Expires: November 27, 2008 May 26, 2008 Quality of Service Parameters for Usage with the AAA Framework - draft-ietf-dime-qos-parameters-03.txt + draft-ietf-dime-qos-parameters-04.txt Status of this Memo By submitting this Internet-Draft, each author represents that any 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 aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that @@ -24,25 +24,21 @@ and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. - This Internet-Draft will expire on August 28, 2008. - -Copyright Notice - - Copyright (C) The IETF Trust (2008). + This Internet-Draft will expire on November 27, 2008. Abstract This document defines a number of Quality of Service (QoS) parameters that can be reused for conveying QoS information within RADIUS and Diameter. The payloads used to carry these QoS parameters are opaque for the AAA client and the AAA server itself and interpreted by the respective Resource Management Function. @@ -811,24 +807,24 @@ We would like to thank Francois Le Faucheur, John Loughney, Martin Stiemerling, Dave Oran, An Nguyen, Ken Carlberg, James Polk, Lars Eggert, and Magnus Westerlund for their help with resolving problems regarding the Admission Priority and the ALRP parameter. 9. References 9.1. Normative References [I-D.ietf-tsvwg-emergency-rsvp] - Faucheur, F., "Resource ReSerVation Protovol (RSVP) - Extensions for Emergency Services", - draft-ietf-tsvwg-emergency-rsvp-05 (work in progress), - January 2008. + Faucheur, F., Polk, J., and K. Carlberg, "Resource + ReSerVation Protovol (RSVP) Extensions for Emergency + Services", draft-ietf-tsvwg-emergency-rsvp-08 (work in + progress), May 2008. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2210] Wroclawski, J., "The Use of RSVP with IETF Integrated Services", RFC 2210, September 1997. [RFC2212] Shenker, S., Partridge, C., and R. Guerin, "Specification of Guaranteed Quality of Service", RFC 2212, September 1997. @@ -879,22 +875,22 @@ [Y.1541] "Network Performance Objectives for IP-Based Services", , 2006. [Y.1571] "Admission Control Priority Levels in Next Generation Networks", , July 2006. 9.2. Informative References [I-D.ietf-nsis-qspec] Ash, G., Bader, A., Kappler, C., and D. Oran, "QoS NSLP - QSPEC Template", draft-ietf-nsis-qspec-18 (work in - progress), October 2007. + QSPEC Template", draft-ietf-nsis-qspec-20 (work in + progress), April 2008. [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. [Y.1540] "Internet Protocol Data Communication Service - IP Packet Transfer and Availability Performance Parameters", , December 2002. Authors' Addresses @@ -902,26 +898,27 @@ Jouni Korhonen (editor) TeliaSonera Teollisuuskatu 13 Sonera FIN-00051 Finland Email: jouni.korhonen@teliasonera.com Hannes Tschofenig Nokia Siemens Networks - Otto-Hahn-Ring 6 - Munich, Bavaria 81739 - Germany + Linnoitustie 6 + Espoo 02600 + Finland + Phone: +358 (50) 4871445 Email: Hannes.Tschofenig@nsn.com - URI: http://www.tschofenig.com + URI: http://www.tschofenig.priv.at Full Copyright Statement Copyright (C) The IETF Trust (2008). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an @@ -948,15 +945,10 @@ attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. - -Acknowledgment - - Funding for the RFC Editor function is provided by the IETF - Administrative Support Activity (IASA).