idnits 2.17.1 draft-jones-dime-3gpp-eps-command-codes-02.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 date (March 4, 2009) is 5531 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 3588 (Obsoleted by RFC 6733) -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Diameter Maintenance and M. Jones 3 Extensions (DIME) Bridgewater Systems 4 Internet-Draft L. Morand 5 Intended status: Informational Orange Labs 6 Expires: September 5, 2009 March 4, 2009 8 Diameter Command Code Registration for Third Generation Partnership 9 Project (3GPP) Evolved Packet System (EPS) 10 draft-jones-dime-3gpp-eps-command-codes-02 12 Status of this Memo 14 This Internet-Draft is submitted to IETF in full conformance with the 15 provisions of BCP 78 and BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on September 5, 2009. 35 Copyright Notice 37 Copyright (c) 2009 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents in effect on the date of 42 publication of this document (http://trustee.ietf.org/license-info). 43 Please review these documents carefully, as they describe your rights 44 and restrictions with respect to this document. 46 Abstract 48 This document registers a set of IANA Diameter Command Codes to be 49 used in new vendor-specific Diameter applications defined for the 50 Third Generation Partnership Project (3GPP) Evolved Packet System 51 (EPS). These new Diameter applications are defined for Mobile 52 Management Entity (MME) and Serving GPRS Support Node (SGSN) related 53 interfaces in the Release 8 architecture. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 3. Command Codes . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 61 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 62 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 63 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 64 7.1. Normative References . . . . . . . . . . . . . . . . . . . 5 65 7.2. Informative References . . . . . . . . . . . . . . . . . . 5 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 68 1. Introduction 70 The Third Generation Partnership Project (3GPP) is defining the 71 Evolved Packet System (EPS) as part of their Release 8 architecture. 72 As part of this architecture, the interfaces based on the Diameter 73 protocol [RFC3588] require the definition of two new Diameter 74 applications. 76 The 3GPP S6a/S6d application (vendor-specific application id: 77 1677251) enables the transfer of subscriber related data between the 78 Mobile Management Entity (MME) and Home Subscriber Server (HSS) on 79 the S6a interface and between the Serving GPRS Support Node (SGSN) 80 and Home Subscriber Server (HSS) on the S6d interface. 82 The 3GPP S13/S13' application (vendor-specific application id: 83 1677252) enables the Mobile Equipment Identity check procedure 84 between the Mobile Management Entity (MME) and Equipment Identity 85 Register (EIR) on the S13 interface and between the Serving GPRS 86 Support Node (SGSN) and Equipment Identity Register (EIR) on the S13' 87 interface. 89 Both Diameter applications are defined under the 3GPP vendor-id 90 "10415" and are defined in [TS29.272]. This document defines the 91 assigned values of the command codes used in these applications. 93 2. Terminology 95 The base Diameter specification (Section 1.4 of [RFC3588]) defines 96 most of the terminology used in this document. Additionally, the 97 terms and acronyms defined in [TS29.272] are used in this document. 99 3. Command Codes 101 The 3GPP S6a/S6d application described in section 5 of [TS29.272] 102 requires the allocation of command code values for the following 103 command pairs: 105 o 3GPP-Update-Location-Request/Answer (ULR/ULA) 107 o 3GPP-Cancel-Location-Request/Answer (CLR/CLA) 109 o 3GPP-Authentication-Information-Request/ Answer (AIR/AIA) 111 o 3GPP-Insert-Subscriber-Data-Request/Answer (IDR/IDA) 112 o 3GPP-Delete-Subscriber-Data-Request/Answer (DSR/DSA) 114 o 3GPP-Purge-UE-Request/Answer (PUR/PUA) 116 o 3GPP-Reset-Request/Answer (RSR/RSA) 118 o 3GPP-Notify-Request/Answer (NOR/NOA) 120 The 3GPP S13/S13 application described in section 6 of [TS29.272] 121 requires the allocation of a command code value for the following 122 command pair: 124 o 3GPP-ME-Identity-Check-Request/Answer (ECR/ECA) 126 4. IANA Considerations 128 This section provides guidance to the Internet Assigned Numbers 129 Authority (IANA) regarding registration of values related to the 130 Diameter protocol, in accordance with BCP 26 [RFC5226]. 132 This document defines values in the namespace that has been defined 133 in the Diameter Base specification [RFC3588]. Section 11 of 134 [RFC3588] (IANA Considerations) details the assignment criteria. 135 IANA is requested to allocate the following command code values: 137 +----------------------------------------------------------------------+ 138 | Code Command Name Abbrev. Defined in | 139 +----------------------------------------------------------------------+ 140 | tbd 3GPP-Update-Location-Request ULR 3GPP TS 29.272 | 141 | tbd 3GPP-Update-Location-Answer ULA 3GPP TS 29.272 | 142 | tbd 3GPP-Cancel-Location-Request CLR 3GPP TS 29.272 | 143 | tbd 3GPP-Cancel-Location-Answer CLA 3GPP TS 29.272 | 144 | tbd 3GPP-Authentication-Information-Request AIR 3GPP TS 29.272 | 145 | tbd 3GPP-Authentication-Information-Answer AIA 3GPP TS 29.272 | 146 | tbd 3GPP-Insert-Subscriber-Data-Request IDR 3GPP TS 29.272 | 147 | tbd 3GPP-Insert-Subscriber-Data-Answer IDA 3GPP TS 29.272 | 148 | tbd 3GPP-Delete-Subscriber-Data-Request DSR 3GPP TS 29.272 | 149 | tbd 3GPP-Delete-Subscriber-Data-Answer DSA 3GPP TS 29.272 | 150 | tbd 3GPP-Purge-UE-Request PUR 3GPP TS 29.272 | 151 | tbd 3GPP-Purge-UE-Answer PUA 3GPP TS 29.272 | 152 | tbd 3GPP-Reset-Request RSR 3GPP TS 29.272 | 153 | tbd 3GPP-Reset-Answer RSA 3GPP TS 29.272 | 154 | tbd 3GPP-Notify-Request NOR 3GPP TS 29.272 | 155 | tbd 3GPP-Notify-Answer NOA 3GPP TS 29.272 | 156 | tbd 3GPP-ME-Identity-Check-Request ECR 3GPP TS 29.272 | 157 | tbd 3GPP-ME-Identity-Check-Answer ECA 3GPP TS 29.272 | 158 +----------------------------------------------------------------------+ 159 5. Security Considerations 161 This document describes command codes used in applications which 162 build on top of the Diameter base protocol and the same security 163 considerations described in [RFC3588] are applicable to this 164 document. No further extensions are required beyond the security 165 mechanisms offered by [RFC3588]. 167 6. Acknowledgements 169 We would like to thank the 3GPP CT4 delegates, Victor Fajardo and 170 Glen Zorn for their review and comments. We would also like to thank 171 Dan Romascanu for volunteering to be AD sponsor and Hannes Tschofenig 172 for volunteering to be Document Shepherd. 174 7. References 176 7.1. Normative References 178 [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. 179 Arkko, "Diameter Base Protocol", RFC 3588, September 2003. 181 [TS29.272] 182 3rd Generation Partnership Project, "3GPP TS 29.272; 183 Technical Specification Group Core Network and Terminals; 184 Evolved Packet System; Mobility Management Entity (MME) 185 and Serving GPRS Support Node (SGSN) Related Interfaces 186 Based on Diameter Protocol (Release 8)", 187 http://www.3gpp.org/ftp/Specs/html-info/29272.htm. 189 7.2. Informative References 191 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 192 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 193 May 2008. 195 Authors' Addresses 197 Mark Jones 198 Bridgewater Systems 200 Email: mark.jones@bridgewatersystems.com 201 Lionel Morand 202 Orange Labs 204 Email: lionel.morand@orange-ftgroup.com