idnits 2.17.1 draft-zorn-dime-doc-set-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.ii or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) 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 and authors Copyright Line does not match the current year == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (July 5, 2009) is 5408 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Obsolete informational reference (is this intentional?): RFC 3588 (Obsoleted by RFC 6733) -- Obsolete informational reference (is this intentional?): RFC 4005 (Obsoleted by RFC 7155) -- Obsolete informational reference (is this intentional?): RFC 4006 (Obsoleted by RFC 8506) Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Zorn 3 Internet-Draft Network Zen 4 Intended status: BCP July 5, 2009 5 Expires: January 6, 2010 7 The Diameter Document Set 8 draft-zorn-dime-doc-set-00 10 Status of this Memo 12 This Internet-Draft is submitted to IETF in full conformance with the 13 provisions of BCP 78 and BCP 79. This document may contain material 14 from IETF Documents or IETF Contributions published or made publicly 15 available before November 10, 2008. The person(s) controlling the 16 copyright in some of this material may not have granted the IETF 17 Trust the right to allow modifications of such material outside the 18 IETF Standards Process. Without obtaining an adequate license from 19 the person(s) controlling the copyright in such materials, this 20 document may not be modified outside the IETF Standards Process, and 21 derivative works of it may not be created outside the IETF Standards 22 Process, except to format it for publication as an RFC or to 23 translate it into languages other than English. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF), its areas, and its working groups. Note that 27 other groups may also distribute working documents as Internet- 28 Drafts. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 The list of current Internet-Drafts can be accessed at 36 http://www.ietf.org/ietf/1id-abstracts.txt. 38 The list of Internet-Draft Shadow Directories can be accessed at 39 http://www.ietf.org/shadow.html. 41 This Internet-Draft will expire on January 6, 2010. 43 Copyright Notice 45 Copyright (c) 2009 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents in effect on the date of 50 publication of this document (http://trustee.ietf.org/license-info). 51 Please review these documents carefully, as they describe your rights 52 and restrictions with respect to this document. 54 Abstract 56 This note contains a brief description of the current Diameter 57 document set. Although the document included are all published RFCs, 58 not all are products of the IETF. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 64 3. The Diameter Document Set . . . . . . . . . . . . . . . . . . . 3 65 3.1. IETF Documents . . . . . . . . . . . . . . . . . . . . . . 3 66 3.1.1. Diameter Base Protocol . . . . . . . . . . . . . . . . 3 67 3.1.2. AAA Transport Profile . . . . . . . . . . . . . . . . . 3 68 3.1.3. Applications . . . . . . . . . . . . . . . . . . . . . 4 69 3.1.3.1. Mobile IPv4 . . . . . . . . . . . . . . . . . . . . 4 70 3.1.3.2. Network Access Server (NASREQ) . . . . . . . . . . 4 71 3.1.3.3. Diameter Credit Control . . . . . . . . . . . . . . 4 72 3.1.3.4. EAP . . . . . . . . . . . . . . . . . . . . . . . . 4 73 3.1.3.5. SIP . . . . . . . . . . . . . . . . . . . . . . . . 4 74 3.1.3.6. Mobile IPv6 . . . . . . . . . . . . . . . . . . . . 4 75 3.2. Other RFCs . . . . . . . . . . . . . . . . . . . . . . . . 4 76 3.2.1. 3GPP EPS Command Codes . . . . . . . . . . . . . . . . 5 77 3.2.2. ITU-T Rw Policy Enforcement Interface . . . . . . . . . 5 78 3.2.3. Diameter Policy Processing Application . . . . . . . . 5 79 3.2.4. 3GPP Release 5 Command Codes . . . . . . . . . . . . . 5 80 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 81 5. IANA considerations . . . . . . . . . . . . . . . . . . . . . . 5 82 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 6 83 7. Informative References . . . . . . . . . . . . . . . . . . . . 6 84 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7 86 1. Introduction 88 This document is intended to provide a stable reference to the 89 dynamic set of RFCs describing the Diameter protocol. As such, it is 90 expected that it will be updated/obsoleted shortly after any new 91 Diameter-related RFC is published. 93 2. Terminology 95 AAA 96 Authentication, Authorization and Accounting 98 3. The Diameter Document Set 100 The Diameter document set has two components: 102 o products of the IETF itself, generally Standards-Track [RFC2026] 103 RFCs 105 and 107 o RFCs relating to Diameter-based protocols developed outside the 108 IETF. 110 3.1. IETF Documents 112 Currently, the IETF Diameter specification consists of the Base 113 protocol specification [RFC3588], Transport Profile [RFC3539] and 114 several applications: Mobile IPv4 [RFC4004], Network Access Server 115 (NASREQ) [RFC4005], Credit Control [RFC4006], Extensible 116 Authentication Protocol (EAP) [RFC4072], Session Initiation Protocol 117 (SIP) [RFC4740], and Mobile IPv6 [RFC5447]. 119 The following subsections briefly summarize the documents included in 120 the present set. 122 3.1.1. Diameter Base Protocol 124 The Base Protocol document [RFC3588] defines the fundamental protocol 125 specification for Diameter AAA, which includes support for 126 accounting. 128 3.1.2. AAA Transport Profile 130 The Transport Profile document [RFC3539] discusses transport layer 131 issues that arise with AAA protocols and contains recommendations on 132 how to overcome these issues. This document also defines the 133 Diameter failover algorithm and state machine. 135 3.1.3. Applications 137 3.1.3.1. Mobile IPv4 139 The Mobile IPv4 [RFC4004] document defines a Diameter application 140 that allows a Diameter server to perform AAA functions for MobileIPv4 141 services to a mobile node. 143 3.1.3.2. Network Access Server (NASREQ) 145 This document [RFC4005] describes the Diameter protocol application 146 used for AAA services in the Network Access Server (NAS) environment. 147 When combined with the Diameter Base protocol [RFC3588], Transport 148 Profile [RFC3539], and EAP [RFC4072] specifications, this application 149 specification satisfies typical network access service requirements. 151 3.1.3.3. Diameter Credit Control 153 This document [RFC4006] specifies a Diameter application that can be 154 used to implement real-time credit-control for a variety of end user 155 services such as network access, Session Initiation Protocol (SIP) 156 [RFC3261] services, messaging services, and download services. 158 3.1.3.4. EAP 160 This document [RFC4072] defines the Diameter Command-Codes and AVPs 161 necessary to carry EAP packets between a Network Access Server (NAS) 162 and a back-end authentication server. 164 3.1.3.5. SIP 166 This application [RFC4740] is designed to be used in conjunction with 167 SIP and provides a Diameter client co-located with a SIP server, with 168 the ability to request the authentication of users and authorization 169 of SIP resources usage from a Diameter server. 171 3.1.3.6. Mobile IPv6 173 This document [RFC5447] describes Mobile IPv6 bootstrapping using the 174 Diameter Network Access Server to home AAA server interface. 176 3.2. Other RFCs 177 3.2.1. 3GPP EPS Command Codes 179 This document [RFC5516] registers a set of Diameter Command Codes to 180 be used in new vendor-specific Diameter applications defined for the 181 Third Generation Partnership Project (3GPP) Evolved Packet System 182 (EPS), specifically those related to the Mobile Management Entity 183 (MME) and Serving GPRS (General Packet Radio Service) Support Node 184 (SGSN) interfaces in the architecture for the Evolved 3GPP Packet 185 Switched Domain. 187 3.2.2. ITU-T Rw Policy Enforcement Interface 189 This document [RFC5431] describes the need for a new pair of IANA 190 Diameter Command Codes to be used in a vendor-specific new 191 application, namely for the ITU-T Rec. Q.3303.3 - Rw interface used 192 to send a request/response for authorizing network Quality of Service 193 (QoS) resources and policy enforcement in a network element, as one 194 of the recommendations of the International Telecommunication Union - 195 Telecommunication Standardization Sector (ITU-T). 197 3.2.3. Diameter Policy Processing Application 199 This document [RFC5224] describes the need for a Diameter Command 200 Code to be used in a vendor-specific application for invocation of 201 Policy Processing (Policy Evaluation, or Evaluation and Enforcement). 202 This application is one of the implementations of the Open Mobile 203 Alliance (OMA) Policy Evaluation, Enforcement and Management (PEEM) 204 enabler. 206 3.2.4. 3GPP Release 5 Command Codes 208 This document [RFC3589] describes the IANA allocation of a block of 209 Diameter Command Codes for the Third Generation Partnership Project 210 (3GPP) Release 5. 212 4. Security Considerations 214 This document has no relevance for security. 216 5. IANA considerations 218 This document makes no requests of IANA. 220 6. Acknowledgments 222 Most of this note was lifted from RFC 3588, Section 1.1.1. 224 7. Informative References 226 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 227 3", BCP 9, RFC 2026, October 1996. 229 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 230 A., Peterson, J., Sparks, R., Handley, M., and E. 231 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 232 June 2002. 234 [RFC3539] Aboba, B. and J. Wood, "Authentication, Authorization and 235 Accounting (AAA) Transport Profile", RFC 3539, June 2003. 237 [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. 238 Arkko, "Diameter Base Protocol", RFC 3588, September 2003. 240 [RFC3589] Loughney, J., "Diameter Command Codes for Third Generation 241 Partnership Project (3GPP) Release 5", RFC 3589, 242 September 2003. 244 [RFC4004] Calhoun, P., Johansson, T., Perkins, C., Hiller, T., and 245 P. McCann, "Diameter Mobile IPv4 Application", RFC 4004, 246 August 2005. 248 [RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, 249 "Diameter Network Access Server Application", RFC 4005, 250 August 2005. 252 [RFC4006] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J. 253 Loughney, "Diameter Credit-Control Application", RFC 4006, 254 August 2005. 256 [RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible 257 Authentication Protocol (EAP) Application", RFC 4072, 258 August 2005. 260 [RFC4740] Garcia-Martin, M., Belinchon, M., Pallares-Lopez, M., 261 Canales-Valenzuela, C., and K. Tammi, "Diameter Session 262 Initiation Protocol (SIP) Application", RFC 4740, 263 November 2006. 265 [RFC5224] Brenner, M., "Diameter Policy Processing Application", 266 RFC 5224, March 2008. 268 [RFC5431] Sun, D., "Diameter ITU-T Rw Policy Enforcement Interface 269 Application", RFC 5431, March 2009. 271 [RFC5447] Korhonen, J., Bournelle, J., Tschofenig, H., Perkins, C., 272 and K. Chowdhury, "Diameter Mobile IPv6: Support for 273 Network Access Server to Diameter Server Interaction", 274 RFC 5447, February 2009. 276 [RFC5516] Jones, M. and L. Morand, "Diameter Command Code 277 Registration for the Third Generation Partnership Project 278 (3GPP) Evolved Packet System (EPS)", RFC 5516, April 2009. 280 Author's Address 282 Glen Zorn 283 Network Zen 284 1310 East Thomas Street 285 #306 286 Seattle, Washington 98102 287 USA 289 Phone: +1 (206) 377-9035 290 Email: gwz@net-zen.net