idnits 2.17.1 draft-ietf-dime-qos-attributes-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 18. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 638. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 649. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 656. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 662. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (July 2, 2007) is 6143 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'EAP-Master-Session-Key' is mentioned on line 456, but not defined == Outdated reference: A later version (-11) exists of draft-ietf-dime-qos-parameters-00 == Outdated reference: A later version (-03) exists of draft-ietf-radext-filter-rules-02 -- Possible downref: Normative reference to a draft: ref. 'I-D.ietf-radext-filter-rules' ** Obsolete normative reference: RFC 3588 (Obsoleted by RFC 6733) ** Obsolete normative reference: RFC 4005 (Obsoleted by RFC 7155) ** Obsolete normative reference: RFC 4006 (Obsoleted by RFC 8506) == Outdated reference: A later version (-24) exists of draft-ietf-nsis-qspec-16 Summary: 4 errors (**), 0 flaws (~~), 5 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Diameter Maintenance and J. Korhonen, Ed. 3 Extensions (DIME) TeliaSonera 4 Internet-Draft H. Tschofenig 5 Intended status: Standards Track Nokia Siemens Networks 6 Expires: January 3, 2008 M. Arumaithurai 7 University of Goettingen 8 July 2, 2007 10 Quality of Service Attributes for Diameter and RADIUS 11 draft-ietf-dime-qos-attributes-00.txt 13 Status of this Memo 15 By submitting this Internet-Draft, each author represents that any 16 applicable patent or other IPR claims of which he or she is aware 17 have been or will be disclosed, and any of which he or she becomes 18 aware will be disclosed, in accordance with Section 6 of BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on January 3, 2008. 38 Copyright Notice 40 Copyright (C) The IETF Trust (2007). 42 Abstract 44 This document extends the functionality of the Diameter Base protocol 45 and other Diameter applications with respect to their ability to 46 convey Quality of Service information. The AVPs defined in this 47 document are also available for Remote Authentication Dial In User 48 Service (RADIUS). 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 3. Commands, AVPs and Advertising Application Support . . . . . . 3 55 3.1. Command Codes . . . . . . . . . . . . . . . . . . . . . . 3 56 3.2. Diameter-EAP-Request (DER) . . . . . . . . . . . . . . . . 4 57 3.3. Diameter-EAP-Answer (DEA) . . . . . . . . . . . . . . . . 4 58 3.4. Credit-Control-Request (CCR) . . . . . . . . . . . . . . . 5 59 3.5. Credit-Control-Answer (CCA) . . . . . . . . . . . . . . . 6 60 3.6. AA-Request (AAR) . . . . . . . . . . . . . . . . . . . . . 7 61 3.7. AA-Answer (AAA) . . . . . . . . . . . . . . . . . . . . . 8 62 4. Diameter QoS Defined AVPs . . . . . . . . . . . . . . . . . . 9 63 4.1. QoS-ID AVP . . . . . . . . . . . . . . . . . . . . . . . . 9 64 4.2. QoS-Flow-State AVP . . . . . . . . . . . . . . . . . . . . 9 65 4.3. QSPEC AVP . . . . . . . . . . . . . . . . . . . . . . . . 9 66 4.4. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 10 67 4.5. QoS-Parameter AVP . . . . . . . . . . . . . . . . . . . . 10 68 4.6. Extended-QoS-Filter-Rule AVP . . . . . . . . . . . . . . . 10 69 4.7. QoS-Capability AVP . . . . . . . . . . . . . . . . . . . . 10 70 4.8. QSPEC-Type AVP . . . . . . . . . . . . . . . . . . . . . . 11 71 5. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 72 6. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . 12 73 6.1. DER and DEA Commands AVP Table . . . . . . . . . . . . . . 12 74 6.2. CCR and CCA Commands AVP Table . . . . . . . . . . . . . . 13 75 6.3. AAR and AAA Commands AVP Table . . . . . . . . . . . . . . 13 76 7. Diameter RADIUS Interoperability . . . . . . . . . . . . . . . 14 77 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14 78 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 79 10. Security Considerations . . . . . . . . . . . . . . . . . . . 14 80 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 81 11.1. Normative References . . . . . . . . . . . . . . . . . . . 14 82 11.2. Informative References . . . . . . . . . . . . . . . . . . 15 83 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 84 Intellectual Property and Copyright Statements . . . . . . . . . . 17 86 1. Introduction 88 This document defines a number of Diameter Quality of Service (QoS) 89 related AVPs that can be used with the Diameter Base protocol, and 90 Diameter Credit Control, Diameter EAP and Diameter NASREQ 91 applications to convey Quality of Service information. The Extended- 92 QoS-Filter-Rule AVP thereby replaces the QoSFilterRule, defined in 93 RFC 3588 [RFC3588], and the QoS-Filter-Rule, defined in RFC 4005 94 [RFC4005]. 96 The AVPs defined in this document are also available for Remote 97 Authentication Dial In User Service (RADIUS). 99 2. Terminology 101 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 102 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 103 document are to be interpreted as described in RFC 2119 [RFC2119]. 105 3. Commands, AVPs and Advertising Application Support 107 3.1. Command Codes 109 This document re-uses the Diameter Base protocol [RFC3588], and 110 Diameter Credit-Control [RFC4006], Diameter NASREQ [RFC4072] and 111 Diameter EAP [RFC4005] application commands. The following commands 112 are re-used to carry QoS related AVPs: 114 Command-Name Abbrev. Code Reference 116 Diameter-EAP-Request DER 268 RFC 4072 117 Diameter-EAP-Answer DEA 268 RFC 4072 119 Credit-Control-Request CCR 272 RFC 4006 120 Credit-Control-Answer CCA 272 RFC 4006 122 AA-Request AAR 265 RFC 4005 123 AA-Answer AAA 265 RFC 4005 125 Figure 1: Command Codes 127 When the Re-Auth-Request (RAR), Re-Auth-Answer (RAA), Session- 128 Termination-Request (STR), Session-Termination-Answer (STA), Abort- 129 Session-Request (ASR), Abort-Session-Answer (ASA), Accounting-Request 130 (ACR), and Accounting-Answer (ACA) commands are used together with 131 this specification they follow the rules in Diameter NASREQ 132 [RFC4005], Diameter EAP [RFC4072], Credit-Control [RFC4006] and 133 Diameter Base Protocol [RFC3588]. The accounting commands use the 134 Application Identifier value of the respective application. 136 3.2. Diameter-EAP-Request (DER) 138 The Diameter-EAP-Request (DER) command [RFC4072], indicated by the 139 Command-Code field set to 268 and the 'R' bit set in the Command 140 Flags field, may be sent by the NAS to the Diameter server providing 141 network access authentication and authorization services. At the 142 same time as the network access authentication and authorization, the 143 NAS MAY request the Diameter server to authorize provisioning of QoS 144 resources. 146 The message format is the same as defined in [RFC4072] with an 147 addition of Diameter QoS specific AVPs. Figure 2 shows the DER 148 message used with the Diameter QoS AVPs: 150 ::= < Diameter Header: 268, REQ, PXY > 151 < Session-Id > 152 { Auth-Application-Id } 153 { Origin-Host } 154 { Origin-Realm } 155 { Destination-Realm } 156 { Auth-Request-Type } 158 [ Destination-Host ] 159 [ User-Name ] 161 [ QoS-Capability ] 162 * [ QoS-Resources ] 164 ... 165 * [ AVP ] 167 Figure 2: Diameter EAP Request Command 169 3.3. Diameter-EAP-Answer (DEA) 171 The Diameter-EAP-Answer (DEA) message defined in [RFC4072], indicated 172 by the Command- Code field set to 268 and 'R' bit cleared in the 173 Command Flags field is sent in response to the Diameter-EAP-Request 174 message (DER). If the QoS service is successfully authorized and the 175 Diameter server was able to fulfill the QoS Authorization request (if 176 needed) then the response MAY include the QoS-Resources AVPs. 178 The message format is the same as defined in [RFC4072] with an 179 addition of Diameter QoS specific AVPs. Figure 3 shows the DEA 180 message used with the Diameter QoS AVPs: 182 ::= < Diameter Header: 268, PXY > 183 < Session-Id > 184 { Auth-Application-Id } 185 { Auth-Request-Type } 186 { Result-Code } 187 { Origin-Host } 188 { Origin-Realm } 190 * [ QoS-Resources ] 192 [ Session-Timeout ] 193 [ User-Name ] 194 ... 195 * [ AVP ] 197 Figure 3: Diameter EAP Answer Command 199 3.4. Credit-Control-Request (CCR) 201 The Credit-Control-Request (CCR) command [RFC4006], indicated by the 202 Command-Code field set to 272 and the 'R' bit set in the Command 203 Flags field, may be sent by the NAS to the Diameter-QoS server to 204 request QoS credit authorization for a given QoS provisioning 205 request. In that case the CCR command MAY also carry the QoS- 206 Resources AVPs. 208 The message format is the same as defined in [RFC4006] with an 209 addition of Diameter QoS specific AVPs. Figure 4 shows the CCR 210 message used with the Diameter QoS AVPs: 212 ::= < Diameter Header: 272, REQ, PXY > 213 < Session-Id > 214 { Auth-Application-Id } 215 { Origin-Host } 216 { Origin-Realm } 217 { Destination-Realm } 218 { Auth-Request-Type } 219 { Service-Context-Id } 220 { CC-Request-Type } 221 { CC-Request-Number } 222 [ Destination-Host ] 223 [ User-Name ] 225 [ QoS-Capability ] 226 * [ QoS-Resources ] 228 ... 229 * [ AVP ] 231 Figure 4: Credit Control Request Command 233 3.5. Credit-Control-Answer (CCA) 235 The Credit-Control-Answer (CCA) command [RFC4006], indicated by the 236 Command-Code field set to 272 and the 'R' bit set in the Command 237 Flags field is sent in response to the CC-Request (CCR) message to 238 acknowledge a CC-Request command. If the Diameter QoS server was 239 able to fulfill the QoS request (if needed) then the response MAY 240 include the QoS-Resources AVPs. 242 The message format is the same as defined in [RFC4006] with an 243 addition of Diameter QoS specific AVPs. Figure 5 shows the CCA 244 message used with the Diameter QoS AVPs: 246 ::= < Diameter Header: 272, PXY > 247 < Session-Id > 248 { Result-Code } 249 { Origin-Host } 250 { Origin-Realm } 251 { Auth-Application-Id } 252 { CC-Request-Type } 253 { CC-Request-Number } 254 [ User-Name ] 255 [ CC-Session-Failover ] 256 [ CC-Sub-Session-Id ] 257 [ Acct-Multi-Session-Id ] 258 [ Origin-State-Id ] 259 [ Event-Timestamp ] 261 * [ QoS-Resources ] 263 ... 264 * [ AVP ] 266 Figure 5: Credit Control Answer Command 268 3.6. AA-Request (AAR) 270 The AA-Request (AAR) message, indicated by the Command-Code field set 271 to 265 and 'R' bit set in the Command Flags field, may be sent by the 272 NAS to the Diameter server providing network access configuration 273 services. At the same time as the network access authentication and 274 authorization, the NAS MAY request the Diameter server to authorize 275 provisioning of QoS resources. 277 The message format is the same as defined in [RFC4005] with an 278 addition of Diameter QoS specific AVPs. Figure 6 shows the AAR 279 message used with the Diameter QoS AVPs: 281 ::= < Diameter Header: 265, REQ, PXY > 282 < Session-Id > 283 { Auth-Application-Id } 284 { Origin-Host } 285 { Origin-Realm } 286 { Destination-Realm } 287 { Auth-Request-Type } 289 [ QoS-Capability ] 290 * [ QoS-Resources ] 292 [ Destination-Host ] 293 ... 294 * [ AVP ] 296 Figure 6: AA Request Command 298 3.7. AA-Answer (AAA) 300 The AA-Answer (AAA) message, indicated by the Command-Code field set 301 to 265 and 'R' bit cleared in the Command Flags field is sent in 302 response to the AA-Request (AAR) message for confirmation of the 303 result of QoS provisioning. If the QoS service is successfully 304 authorized and the Diameter server was able to fulfill the QoS 305 provisioning request (if needed) then the response MAY include the 306 QoS-Resources AVPs. 308 The message format is the same as defined in [RFC4005] with an 309 addition of Diameter QoS specific AVPs. Figure 7 shows the AAA 310 message used with the Diameter QoS AVPs: 312 ::= < Diameter Header: 265, PXY > 313 < Session-Id > 314 { Auth-Application-Id } 315 { Auth-Request-Type } 316 { Result-Code } 317 { Origin-Host } 318 { Origin-Realm } 320 * [ QoS-Resources ] 322 [ User-Name ] 323 [ Session-Timeout ] 324 ... 325 * [ AVP ] 326 Figure 7: AA Answer Command 328 4. Diameter QoS Defined AVPs 330 The following table lists the Diameter AVPs used by this document, 331 their AVP code values, types, possible flag values, and whether the 332 AVP may be encrypted. 334 +------------------+ 335 | AVP Flag Rules | 336 +-------------------------------------------------|----+---+----+----+ 337 | AVP Section |MUST|MAY|SHLD|MUST| 338 | Attribute Name Code Defined Data Type | | | NOT| NOT| 339 +-------------------------------------------------+----+---+----+----+ 340 |QoS-Flow-State TBD 4.2 Enumerated | |M,P| | V | 341 |QSPEC TBD 4.3 OctetSTring| |M,P| | V | 342 |QoS-ID TBD 4.1 Unsigned32 | |M,P| | V | 343 |Extended-QoS-Filter-Rule TBD 4.6 Grouped | |M,P| | V | 344 |QoS-Resources TBD 4.4 Grouped | |M,P| | V | 345 |QoS-Parameter TBD 4.5 Grouped | |M,P| | V | 346 |QoS-Capability TBD 4.7 Grouped | |M,P| | V | 347 |QSPEC-Type TBD 4.8 Unsigned32 | |M,P| | V | 348 +-------------------------------------------------+----+---+----+----+ 350 4.1. QoS-ID AVP 352 The QoS-ID AVP (AVP Code TBD) is of type Unsigned32 and references 353 the QSPEC. 355 4.2. QoS-Flow-State AVP 357 The QoS-Flow-State AVP (AVP Code TBD) is of type Enumerated. It 358 gives an indication as to how the flow MUST be treated. The 359 Extended-QoS-Filter-Rule already provides an indicate whether a flow 360 is permitted or denied. This optional AVP provides additional 361 information about the treatment. Currently a single value is 362 defined; further values are available via IANA registration. 364 0 Pending: The filter rules are not installed but kept pending. 365 Subsequent signaling is necessary to active them. 367 4.3. QSPEC AVP 369 The QSPEC AVP (AVP Code TBD) is of type OctetString and contains 370 Quality of Service parameters. These parameters are defined in a 371 separate document, see [I-D.ietf-dime-qos-parameters]. 373 4.4. QoS-Resources AVP 375 The QoS-Resources AVP (AVP Code TBD) is of type Grouped and includes 376 description of the resources that have been authorized or requested. 377 More than one QoS-Resources AVP MAY be included in a single message. 379 QoS-Resources ::= < AVP Header: XXX > 380 1* [ Extended-QoS-Filter-Rule ] 381 1* [ QoS-Parameter ] 382 [ QoS-Flow-State ] 383 * [ AVP ] 385 4.5. QoS-Parameter AVP 387 The QoS-Parameter AVP (AVP Code TBD) is of type Grouped and ties the 388 QoS-ID AVP together to the QSPEC AVP. All parameters followed by the 389 QSPEC-Type AVP refer to the same QoS model/profile. 391 QoS-Parameter ::= < AVP Header: XXX > 392 { QoS-ID } 393 { QSPEC-Type } 394 1* [ QSPEC ] 395 * [ AVP ] 397 4.6. Extended-QoS-Filter-Rule AVP 399 TheExtended-QoS-Filter-Rule AVP (AVP Code TBD) is of type Grouped. 400 The QoS filter rule associated with the QoS-ID re-uses the RADIUS 401 NAS-Traffic-Rule AVP [I-D.ietf-radext-filter-rules]. This AVP ties a 402 specific filter to a QoS-ID that in turn refers to a specific QoS- 403 Parameter. 405 Extended-QoS-Filter-Rule ::= < AVP Header: XXX > 406 { QoS-ID } 407 { NAS-Traffic-Rule } 408 * [ AVP ] 410 4.7. QoS-Capability AVP 412 The QoS-Capability AVP (AVP Code TBD) is of type Grouped and contains 413 a list of supported QSPEC-Types and respective AVPs. 415 The NAS SHOULD include this AVP from the NAS to the Diameter server 416 to indicate the support for this specification and for the specific 417 QoS models. 419 QoS-Capability ::= < AVP Header: XXX > 420 1* { QSPEC-Type } 421 * [ AVP ] 423 4.8. QSPEC-Type AVP 425 The QSPEC-Type AVP (AVP Code TBD) is of type Unsigned32 and contains 426 the supported QoS model or QoS profile. The value of 0 refers to the 427 QoS parameters described in [I-D.ietf-dime-qos-parameters]. The 428 values are taken from the registry defined in [I-D.ietf-nsis-qspec]. 430 5. Example 431 User AAA Client AAA server 432 | | | 433 | (initiate EAP) | | 434 |<------------------------------>| | 435 | | Diameter-EAP-Request | 436 | | EAP-Payload(EAP Start) | 437 | | QoS-Capability | 438 | |------------------------------->| 439 | | | 440 | | Diameter-EAP-Answer | 441 | Result-Code=DIAMETER_MULTI_ROUND_AUTH | 442 | | EAP-Payload(EAP Request #1) | 443 | |<-------------------------------| 444 | EAP Request(Identity) | | 445 |<-------------------------------| | 446 | | | 447 | EAP Response #N | | 448 |------------------------------->| | 449 | | Diameter-EAP-Request | 450 | | EAP-Payload(EAP Response #N) | 451 | |------------------------------->| 452 | | | 453 | | Diameter-EAP-Answer | 454 | | Result-Code=DIAMETER_SUCCESS | 455 | | EAP-Payload(EAP Success) | 456 | | [EAP-Master-Session-Key] | 457 | | (authorization AVPs) | 458 | | QoS-Resources | 459 | |<-------------------------------| 460 | | | 461 | EAP Success | | 462 |<-------------------------------| | 463 | | | 465 Figure 8: Example of AAA Server providing QoS Information to AAA 466 Client 468 6. AVP Occurrence Tables 470 6.1. DER and DEA Commands AVP Table 472 The following table lists the Quality of Service specific AVPs 473 defined in this document that may be present in the DER and DEA 474 Commands, as defined in this document and in [RFC4072]. 476 +---------------+ 477 | Command-Code | 478 |-------+-------+ 479 Attribute Name | DER | DEA | 480 -------------------------------+-------+-------+ 481 QoS-Capability | 0-1 | 0 | 482 QoS-Resources | 0+ | 0+ | 483 +-------+-------+ 485 Figure 9: DER and DEA Commands AVP table 487 6.2. CCR and CCA Commands AVP Table 489 The following table lists the Quality of Service specific AVPs 490 defined in this document that may be present in the CCR and CCA 491 Commands, as defined in this document and in [RFC4006]. 493 +---------------+ 494 | Command-Code | 495 |-------+-------+ 496 Attribute Name | CCR | CCA | 497 -------------------------------+-------+-------+ 498 QoS-Capability | 0-1 | 0 | 499 QoS-Resources | 0+ | 0+ | 500 +-------+-------+ 502 Figure 10: CCR and CCA Commands AVP table 504 6.3. AAR and AAA Commands AVP Table 506 The following table lists the Quality of Service specific AVPs 507 defined in this document that may be present in the AAR and AAA 508 Commands, as defined in this document and in [RFC4005]. 510 +---------------+ 511 | Command-Code | 512 |-------+-------+ 513 Attribute Name | AAR | AAA | 514 -------------------------------+-------+-------+ 515 QoS-Capability | 0-1 | 0 | 516 QoS-Resources | 0+ | 0+ | 517 +-------+-------+ 519 Figure 11: AAR and AAA Commands AVP table 521 7. Diameter RADIUS Interoperability 523 [Editor's Note: Text will be provided in a future version of this 524 document.] 526 8. Acknowledgments 528 We would like to thank Victor Fajardo for his comments. 530 9. IANA Considerations 532 Diameter reserves the AVP Codes 0 - 255 for RADIUS functions that are 533 implemented in Diameter. AVPs new to Diameter have code values of 534 256 and greater. 536 This specification assigns the values TBD-1 to TBD-2 from the AVP 537 Code namespace defined in RFC 3588 [RFC3588]. See Section 4 for the 538 newly defined AVPs. 540 This specification also specifies the use of AVPs in the 0 - 255 541 range, which are defined in 'RADIUS Types', see 542 http://www.iana.org/assignments/radius-types. These values are 543 assigned by the policy in Section 6 of RFC 2865 [RFC2865] and are 544 amended by RFC 3575 [RFC3575]. 546 10. Security Considerations 548 This document describes the extension of Diameter for conveying 549 Quality of Service information. The security considerations of the 550 Diameter protocol itself have been discussed in RFC 3588 [RFC3588]. 551 Use of the AVPs defined in this document MUST take into consideration 552 the security issues and requirements of the Diameter Base protocol. 554 11. References 556 11.1. Normative References 558 [I-D.ietf-dime-qos-parameters] 559 Korhonen, J. and H. Tschofenig, "Quality of Service 560 Parameters for Usage with the AAA Framework", 561 draft-ietf-dime-qos-parameters-00 (work in progress), 562 June 2007. 564 [I-D.ietf-radext-filter-rules] 565 Congdon, P., "RADIUS Attributes for Filtering and 566 Redirection", draft-ietf-radext-filter-rules-02 (work in 567 progress), March 2007. 569 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 570 Requirement Levels", BCP 14, RFC 2119, March 1997. 572 [RFC3575] Aboba, B., "IANA Considerations for RADIUS (Remote 573 Authentication Dial In User Service)", RFC 3575, 574 July 2003. 576 [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. 577 Arkko, "Diameter Base Protocol", RFC 3588, September 2003. 579 [RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, 580 "Diameter Network Access Server Application", RFC 4005, 581 August 2005. 583 [RFC4006] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J. 584 Loughney, "Diameter Credit-Control Application", RFC 4006, 585 August 2005. 587 11.2. Informative References 589 [I-D.ietf-nsis-qspec] 590 Ash, J., "QoS NSLP QSPEC Template", 591 draft-ietf-nsis-qspec-16 (work in progress), March 2007. 593 [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, 594 "Remote Authentication Dial In User Service (RADIUS)", 595 RFC 2865, June 2000. 597 [RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible 598 Authentication Protocol (EAP) Application", RFC 4072, 599 August 2005. 601 Authors' Addresses 603 Jouni Korhonen (editor) 604 TeliaSonera 605 Teollisuuskatu 13 606 Sonera FIN-00051 607 Finland 609 Email: jouni.korhonen@teliasonera.com 610 Hannes Tschofenig 611 Nokia Siemens Networks 612 Otto-Hahn-Ring 6 613 Munich, Bavaria 81739 614 Germany 616 Email: Hannes.Tschofenig@nsn.com 617 URI: http://www.tschofenig.com 619 Mayutan Arumaithurai 620 University of Goettingen 622 Email: mayutan.arumaithurai@gmail.com 624 Full Copyright Statement 626 Copyright (C) The IETF Trust (2007). 628 This document is subject to the rights, licenses and restrictions 629 contained in BCP 78, and except as set forth therein, the authors 630 retain all their rights. 632 This document and the information contained herein are provided on an 633 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 634 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 635 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 636 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 637 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 638 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 640 Intellectual Property 642 The IETF takes no position regarding the validity or scope of any 643 Intellectual Property Rights or other rights that might be claimed to 644 pertain to the implementation or use of the technology described in 645 this document or the extent to which any license under such rights 646 might or might not be available; nor does it represent that it has 647 made any independent effort to identify any such rights. Information 648 on the procedures with respect to rights in RFC documents can be 649 found in BCP 78 and BCP 79. 651 Copies of IPR disclosures made to the IETF Secretariat and any 652 assurances of licenses to be made available, or the result of an 653 attempt made to obtain a general license or permission for the use of 654 such proprietary rights by implementers or users of this 655 specification can be obtained from the IETF on-line IPR repository at 656 http://www.ietf.org/ipr. 658 The IETF invites any interested party to bring to its attention any 659 copyrights, patents or patent applications, or other proprietary 660 rights that may cover technology that may be required to implement 661 this standard. Please address the information to the IETF at 662 ietf-ipr@ietf.org. 664 Acknowledgment 666 Funding for the RFC Editor function is provided by the IETF 667 Administrative Support Activity (IASA).