idnits 2.17.1 draft-montemurro-gsma-imei-urn-12.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. 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 : ---------------------------------------------------------------------------- ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. 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, and may have content which was first submitted before 10 November 2008. The disclaimer is necessary when there are original authors that you have been unable to contact, or if some do not wish to grant the BCP78 rights to the IETF Trust. If you are able to get all authors (current and original) to grant those rights, 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 (February 7, 2013) is 4095 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: '7' is defined on line 516, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3406 (ref. '1') (Obsoleted by RFC 8141) ** Obsolete normative reference: RFC 2141 (ref. '7') (Obsoleted by RFC 8141) Summary: 3 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Montemurro, Ed. 3 Internet-Draft A. Allen 4 Intended status: Informational Research in Motion (RIM) 5 Expires: August 11, 2013 D. McDonald 6 unaffiliated 7 P. Gosden 8 GSM Association 9 February 7, 2013 11 A Uniform Resource Name Namespace for the GSM Association (GSMA) and the 12 International Mobile station Equipment Identity (IMEI) 13 draft-montemurro-gsma-imei-urn-12 15 Abstract 17 This specification defines a Uniform Resource Name namespace for the 18 GSMA (GSM Association)and a sub-namespace for the IMEI (International 19 Mobile station Equipment Identity), and associated parameter for the 20 IMEISV (International Mobile station Equipment Identity and Software 21 Version number). The IMEI is 15 decimal digits long and the IMEISV 22 is 16 decimal digits long and both are encoded using Binary Encoded 23 Decimal (BCD). The IMEI and IMEISV were introduced as part of the 24 specification for Global System for Mobile communications(GSM) and 25 are also now incorporated by the 3rd Generation Partnership Project 26 (3GPP) as part of the 3GPP specification for GSM, the Universal 27 Mobile Telecommunications System (UMTS) and 3GPP LTE (Long Term 28 Evolution). The IMEI and IMEISV are used to uniquely identify Mobile 29 Equipment within these systems and are managed by the GSMA. 31 Status of this Memo 33 This Internet-Draft is submitted in full conformance with the 34 provisions of BCP 78 and BCP 79. 36 Internet-Drafts are working documents of the Internet Engineering 37 Task Force (IETF). Note that other groups may also distribute 38 working documents as Internet-Drafts. The list of current Internet- 39 Drafts is at http://datatracker.ietf.org/drafts/current/. 41 Internet-Drafts are draft documents valid for a maximum of six months 42 and may be updated, replaced, or obsoleted by other documents at any 43 time. It is inappropriate to use Internet-Drafts as reference 44 material or to cite them other than as "work in progress." 46 This Internet-Draft will expire on August 11, 2013. 48 Copyright Notice 49 Copyright (c) 2013 IETF Trust and the persons identified as the 50 document authors. All rights reserved. 52 This document is subject to BCP 78 and the IETF Trust's Legal 53 Provisions Relating to IETF Documents 54 (http://trustee.ietf.org/license-info) in effect on the date of 55 publication of this document. Please review these documents 56 carefully, as they describe your rights and restrictions with respect 57 to this document. Code Components extracted from this document must 58 include Simplified BSD License text as described in Section 4.e of 59 the Trust Legal Provisions and are provided without warranty as 60 described in the Simplified BSD License. 62 This document may contain material from IETF Documents or IETF 63 Contributions published or made publicly available before November 64 10, 2008. The person(s) controlling the copyright in some of this 65 material may not have granted the IETF Trust the right to allow 66 modifications of such material outside the IETF Standards Process. 67 Without obtaining an adequate license from the person(s) controlling 68 the copyright in such materials, this document may not be modified 69 outside the IETF Standards Process, and derivative works of it may 70 not be created outside the IETF Standards Process, except to format 71 it for publication as an RFC or to translate it into languages other 72 than English. 74 Table of Contents 76 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 78 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 80 3. Namespace Registration Template . . . . . . . . . . . . . . . 5 81 3.1. GSMA . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 83 4. Specification . . . . . . . . . . . . . . . . . . . . . . . . 9 84 4.1. IMEI Format . . . . . . . . . . . . . . . . . . . . . . . 9 85 4.1.1. Type Allocation Code (TAC) . . . . . . . . . . . . . . 9 86 4.1.2. Serial Number (SNR) . . . . . . . . . . . . . . . . . 9 87 4.1.3. Spare . . . . . . . . . . . . . . . . . . . . . . . . 9 88 4.2. IMEISV Format . . . . . . . . . . . . . . . . . . . . . . 10 89 4.2.1. Type Allocation Code (TAC) . . . . . . . . . . . . . . 10 90 4.2.2. Serial Number (SNR) . . . . . . . . . . . . . . . . . 10 91 4.2.3. Software Version Number (SVN) . . . . . . . . . . . . 10 93 5. Community considerations . . . . . . . . . . . . . . . . . . . 10 95 6. Namespace considerations . . . . . . . . . . . . . . . . . . . 11 97 7. IANA considerations . . . . . . . . . . . . . . . . . . . . . 11 99 8. Security considerations . . . . . . . . . . . . . . . . . . . 11 101 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 103 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 104 10.1. Normative references . . . . . . . . . . . . . . . . . . . 12 105 10.2. Informative references . . . . . . . . . . . . . . . . . . 13 107 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 109 1. Introduction 111 This specification defines a Uniform Resource Name namespace for the 112 GSMA (GSM Association) and a sub-namespace for the IMEI 113 (International Mobile station Equipment Identity), and associated 114 parameter for the Software Version number from the IMEISV 115 (International Mobile station Equipment Identity and Software Version 116 number) as per the namespace registration requirement found in [1]. 117 The namespace gsma is a namespace for identities used by Mobile 118 Equipment used in GSM, UMTS and LTE networks. The IMEI and the 119 IMEISV are managed by the GSMA, so this namespace would be managed by 120 the GSMA. Whilst this specification currently specifies only the 121 IMEI sub-namespace under the GSMA URN namespace additional sub- 122 namespaces under the GSMA namespace may be specified in the future by 123 the GSMA through the publication of future informational RFCs. 125 The IMEI is 15 decimal digits long and includes a Type Allocation 126 Code (TAC) of 8 decimal digits and the Serial Number (SNR) of 6 127 decimal digits plus a Spare decimal digit. The TAC identifies the 128 type of the Mobile Equipment and is chosen from a range of values 129 allocated to the Mobile Equipment manufacturer in order to uniquely 130 identify the model of the Mobile Equipment. The SNR is an individual 131 serial number that uniquely identifies each Mobile Equipment within 132 the TAC. The Spare digit is used as a security check to combat 133 potential spoofing and is always set to the value 0 when transmitted 134 by the Mobile Equipment. 136 The IMEISV is 16 decimal digits long and includes the TAC and SNR 137 same as for the IMEI but also a 2 decimal digit Software Version 138 Number (SVN) which is allocated by the Mobile Equipment manufacturer 139 to identify the software version of the Mobile Equipment. 141 The information here is meant to be a concise guide for those wishing 142 to use the IMEI and IMEISV as URNs. Nothing in this document should 143 be construed to override 3GPP TS 23.003 [2] that defines the IMEI and 144 IMEISV. 146 The GSM Association (GSMA) is a global trade association representing 147 more than 750 GSM mobile phone operators across 220 territories and 148 countries of the world. The primary goals of the GSMA are to ensure 149 mobile phones and wireless services work globally and are easily 150 accessible. Further details about the GSMA role in allocating the 151 IMEI and the IMEISV and the IMEI and IMEISV allocation guidelines can 152 be found in GSMA TS 06 [3] 154 2. Terminology 156 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 157 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 158 document are to be interpreted as described in [4]. 160 3. Namespace Registration Template 162 3.1. GSMA 164 Namespace ID: "gsma" requested 166 Registration Information: 168 Registration version number: 1 170 Registration date: 2011-07-08 172 Declared registrant of the namespace: GSM Association, 1st Floor, 173 Mid City Place, 71 High Holborn, London, England 175 Declaration of syntactic structure: 176 The identifier is expressed in ASCII characters and has a 177 hierarchical structure expressed using the augmented Backus-Naur 178 Form (ABNF) defined in [8] as follows: 180 gsma-urn = "urn:gsma:" gsma-specifier 181 *(":" gsma-specifier-defined-substring) 182 *(";" gsma-specifier-param) 184 gsma-specifier = "imei" / gsma-specifier-defined-string 185 gsma-specifier-defined-string = gsma-approved-nonempty-string 186 gsma-specifier-defined-substring = gsma-approved-nonempty-string 187 gsma-specifier-defined-param-name = gsma-approved-nonempty-string 188 gsma-specifier-defined-param-val = gsma-approved-string 189 gsma-specifier-param = 190 "svn" "=" software-version-string / 191 "vers" "=" gsma-format-version-string / 192 gsma-specifier-defined-param-name "=" 193 gsma-specifier-defined-param-val 194 software-version-string = 2DIGIT 195 gsma-format-version-string = DIGIT 196 gsma-approved-string = *unreserved 197 gsma-approved-nonempty-string = 1*unreserved 198 unreserved = ALPHA / DIGIT / "-" / "." / "_" 200 The GSMA namespace includes a predefined namespace for IMEI and 201 may be in the future extended to include other identifiers used by 202 Mobile Equipment used in GSM, UMTS or LTE networks or future 203 networks deployed by members of the GSMA. 205 An IMEI is an identifier under the GSMA namespace that uniquely 206 identifies Mobile Equipment used in GSM, UMTS and LTE networks. 208 The internal representation of a IMEI is a specific sequence of 209 bits in memory, as described in 3GPP TS 23.003 [2]. To accurately 210 represent a IMEI as a URN, it is necessary to convert the BCD bit 211 sequence to a string representation. Each field BCD bit sequence 212 has its value printed as a decimal digit string with the most 213 significant digit first. 215 The following augmented Backus-Naur Form (ABNF) includes the set 216 of core rules in RFC 5234 [8], and are not repeated here. 218 A URN with the "imei" gsma-specifier contains exactly one gsma- 219 specifier-defined-substring, and its formal definition is provided 220 by the following ABNF [8]: 222 IMEI = tac "-" snr "-" spare 223 tac = 8DIGIT 224 snr = 6DIGIT 225 spare = 1DIGIT 226 For example: 227 urn:gsma:imei:90420156-025763-0;vers=0 229 The optional "vers" parameter is included for extensibility of the 230 namespace, for example if the IMEI format is extended in the 231 future (such as with additional digits or using hex digits). A 232 value of "vers" equal to 0 or the absence of the "vers" parameter 233 means the URN format is compliant with the format specified here. 234 Any change to the format specified here requires the publication 235 of a future informational RFC. 237 The IMEISV is an identifier that uniquely identifies Mobile 238 Equipment and associated software versions used in GSM and UMTS 239 networks. The internal representation of a IMEISV is a specific 240 sequence of bits in memory, as described in 3GPP TS 23.003 [2] 241 To represent the IMEISV the URN parameter "svn" is appended to the 242 IMEI URN and set equal to the decimal string representation of the 243 two software version number (svn) bits in the IMEISV and the spare 244 digit in the IMEI gsma-specifier-defined-substring is set to zero. 246 For example: 247 urn:gsma:imei:90420156-025763-0;svn=42 249 The , , , 251 and can comprise any ASCII 252 characters compliant with the above ABNF. The exclusion of the 253 colon from the list of other characters means that the colon can 254 only occur as a delimiter between string values. The exclusion of 255 the semicolon from the list of other characters means that the 256 semicolon can only occur as a delimiter for parameter values. The 257 exclusion of the "=" character from the list of other characters 258 means that the "=" character can only occur as an operator for 259 parameter values. 261 The GSMA will take responsibility for the gsma-specifier "imei" 262 and manage the URNs in its sub-namespace. 264 Additional gsma-specifiers may be added in the future through 265 informational RFCs. 267 Relevant ancillary documentation: 268 See IMEI Allocation and Approval Guidelines [3] and 3GPP TS 23.003 269 [2]. 271 Identifier uniqueness considerations: 272 Identifiers in the "gsma" namespace are defined and assigned in 273 the requested namespace by the GSMA after ensuring that the URNs 274 to be assigned are unique. Uniqueness is achieved by checking 275 against the registry of previously assigned names. 277 Procedures are in place to ensure that each IMEI is uniquely 278 assigned by the Mobile Equipment manufacturer so that it is 279 guaranteed to uniquely identify that particular Mobile Equipment. 280 Procedures are in place to ensure that each IMEISV is uniquely 281 assigned by the Mobile Equipment manufacturer so that it is 282 guaranteed to uniquely identify that particular Mobile Equipment 283 and the specific software version installed. 285 Identifier persistence considerations: 286 The GSMA is committed to maintaining uniqueness and persistence of 287 all resources identified by assigned URNs. 289 As the NID sought is "gsma" and GSMA is the long standing acronym 290 for the trade association that represents the mobile phone 291 operators the URN should also persist indefinitely (at least as 292 long as there is a need for its use). The assignment process 293 guarantees that names are not reassigned. The binding between the 294 name and its resource is permanent. 296 The TAC and SNR portions of IMEISVs are stored in the Mobile 297 Equipment so they remain persistent. The SVN may be modified by 298 software when new versions are installed but should be persistent 299 for the duration of the installation of that specific version of 300 software. 302 Process of identifier assignment: 303 GSMA will manage the (including "imei"), , , , and identifier resources to maintain 307 uniqueness. 309 The process for IMEI and IMEISV assignment is documented in GSMA 310 TS 06[3] 312 Process for identifier resolution: 313 Since the GSMA namespace is not globally resolvable, this is not 314 applicable. 316 Rules for Lexical Equivalence: 317 Two IMEI URNs are equivalent if the single gsma-defined-substrings 318 in the two URNs are the same, and the sequences of gsma-specifier- 319 params are the same and in the same order, with the exception that 320 the gsma-specifier-param "vers=0" is to be ignored for purposes of 321 comparison. All of these comparisons are to be case-insensitive. 323 Any identifier in GSMA namespaces can be compared using the normal 324 mechanisms for percent-encoded UTF-8 strings. 326 Conformance with URN Syntax: 327 The string representation of the GSMA URN and of the IMEI sub- 328 namespace is fully compatible with the URN syntax. 330 Validation Mechanism: 331 The IMEI can be validated using the mechanism defined in Annex B 332 of 3GPP TS 23.003 [2]. There is no mechanism defined to validate 333 the SVN field of the IMEISV. 335 Scope: GSMA URN is global in scope. 337 4. Specification 339 4.1. IMEI Format 341 The IMEI format is 15 decimal digits encoded in 8 octets using BCD as 342 defined in 3GPP TS 24.008 [5]. The most significant digit is coded 343 in the most significant bits of octet 1. The least significant digit 344 is coded in the least significant bits of octet 8. 346 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Decimal Digits 347 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 348 | | | S| 349 | T | S | p| 350 | A | N | a| 351 | C | R | r| 352 | | | e| 353 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 354 1 2 3 4 5 6 7 8 Octets 356 4.1.1. Type Allocation Code (TAC) 358 The TAC is a 8 decimal digit value. The TAC identifies the type of 359 the Mobile Equipment and is chosen from a range of values allocated 360 to the Mobile Equipment manufacturer in order to uniquely identify 361 the model of the Mobile Equipment. 363 4.1.2. Serial Number (SNR) 365 The SNR is a 6 decimal digit value. The SNR is an individual serial 366 number that uniquely identifies each Mobile Equipment within the TAC. 368 4.1.3. Spare 370 The Spare is a single decimal digit. When the IMEI is stored on the 371 Mobile Equipment and network equipment it contains a value that is 372 used as a Check Digit and is intended to avoid manual reporting 373 errors, (e.g. when customers register stolen mobiles at the 374 operator's customer care desk) and also to help guard against the 375 possibility of incorrect entries being provisioned in the network 376 equipment. The Spare is always set to zero when transmitted by the 377 Mobile Equipment, (including when in the IMEI URN format). Annex B 378 of 3GPP TS 23.003 [2] defines a mechanism for computing the actual 379 check digit in order to validate the TAC and SNR. 381 4.2. IMEISV Format 383 The IMEISV format is 16 decimal digits encoded in 8 octets using BCD 384 as defined in 3GPP TS 24.008 [5]. The most significant digit is 385 coded in the most significant bits of octet 1. The least significant 386 digit is coded in the least significant bits of octet 8. 388 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Decimal Digits 389 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 390 | | | | 391 | T | S | S | 392 | A | N | V | 393 | C | R | N | 394 | | | | 395 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 396 1 2 3 4 5 6 7 8 Octets 398 4.2.1. Type Allocation Code (TAC) 400 The TAC is the same as for the IMEI in Section 5.1.1. 402 4.2.2. Serial Number (SNR) 404 The SNR is the same as for the IMEI in Section 5.1.2. 406 4.2.3. Software Version Number (SVN) 408 The Software Version Number is allocated by the Mobile Equipment 409 manufacturer to identify the software version of the Mobile 410 Equipment. 412 5. Community considerations 414 GSM, UMTS and LTE mobile devices will be interoperating with Internet 415 devices for a variety of voice and data services. To do this, they 416 need to make use of Internet protocols that will operate end to end 417 between devices in GSM/UMTS/LTE networks and those in the general 418 internet. Some of these protocols require the use of URN's as 419 identifiers. Within the GSM/UMTS/LTE networks, mobile devices are 420 identified by their IMEI and IMEISV. Internet users will need to be 421 able to receive and include the GSMA URN in various Internet protocol 422 elements to facilitate communication between pure internet based 423 devices and GSM/UMTS/LTE mobile devices. Thus the existence and 424 syntax of these namespaces needs to be available to the general 425 internet community and the namespace needs to be reserved with IANA 426 in order to guarantee uniqueness and prevent potential namespace 427 conflicts both within the internet and within GSM/UMTS/LTE networks. 428 Conversely, Internet implementations will not generally possess IMEI 429 identifiers. The identifiers generated by such implementations will 430 typically be URNs within namespaces other than "gsma," and may, 431 depending on context, even be non-URN URIs. Implementations are 432 advised to be ready to process URIs other than "gsma"-namespaced 433 URNs, so as to aid in interoperability. 435 6. Namespace considerations 437 A URN was considered the most appropriate URI to represent the IMEI 438 and IMEISV as these identifiers may be used and transported similarly 439 to the Universally Unique Identifier (UUID)which is defined as a URN 440 in [9]. Since specifications for protocols that are used to 441 transport device identifiers often require the device identifier to 442 be globally unique and in the URN format it is necessary that the URN 443 formats are defined to represent the IMEI and IMEISV. 445 7. IANA considerations 447 In accordance with BCP 66 [1], IANA is asked to register the Formal 448 URN Namespace 'GSMA' in the Registry of URN Namespaces, using the 449 registration template presented in Section 3 of this document. 451 8. Security considerations 453 IMEIs (but with the Spare value set to the value of the Check Digit) 454 are displayable on most Mobile Equipment; therefore, they must not be 455 used as security capabilities (identifiers whose mere possession 456 grants access), for example. 458 Revealing the specific software version of the terminal might make 459 the terminal more vulnerable to attacks against software that is 460 known to contain security holes. Care therefore SHOULD be taken 461 regarding use of the IMEISV as it could help a malicious device 462 identify Mobile Equipment running software that is known to be 463 vulnerable to certain attacks. This is a similar concern to the use 464 of the User-Agent header in SIP as specified in RFC 3261 [10]. It is 465 therefore RECOMMENDED that the IMEISV (that is, the IMEI URN with svn 466 parameter) is not delivered to devices that are not trusted. 467 Further, because IMEIs can be loosely correlated to a user, they need 468 to be treated as any other personally identifiable information. In 469 particular, the IMEI URN MUST NOT be included in messages intended to 470 convey any level of anonymity. 472 Additional security considerations are specified in 3GPP TS 22.016 473 [6]. Specifically the IMEI is to be incorporated in a module which 474 is contained within the terminal. The IMEI SHALL NOT be changed 475 after the terminal's production process. It SHALL resist tampering, 476 i.e. manipulation and change, by any means (e.g. physical, electrical 477 and software). 479 9. Acknowledgements 481 This document draws heavily on the 3GPP work on Numbering, Addressing 482 and Identification in 3GPP TS 23.003 [2] and also on the style and 483 structure used in RFC 4122 [9]. The authors would like to thank 484 Cullen Jennings, Lisa Dusseault, Dale Worley, and Ivo Sedlacek for 485 their help and comments. 487 10. References 489 10.1. Normative references 491 [1] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, 492 "Uniform Resource Names (URN) Namespace Definition Mechanisms", 493 BCP 66, RFC 3406, October 2002. 495 [2] 3GPP, "TS 23.003: Numbering, addressing and identification 496 (Release 8)", 3GPP 23.003, September 2008, 497 . 499 [3] GSMA Association, "IMEI Allocation and Approval Guidelines", 500 PRD TS.06 (DG06) version 6.0, July 2011, . 504 [4] Bradner, S., "Key words for use in RFCs to Indicate Requirement 505 Levels", BCP 14, RFC 2119, March 1997. 507 [5] 3GPP, "TS 24.008: Mobile radio interface Layer 3 specification; 508 Core network protocols; Stage 3 (Release 8)", 3GPP 24.008, 509 September 2008, 510 . 512 [6] 3GPP, "TS 22.016: International Mobile station Equipment 513 Identities (IMEI)(Release 7)", 3GPP 22.016, May 2007, 514 . 516 [7] Moats, R., "URN Syntax", RFC 2141, May 1997. 518 10.2. Informative references 520 [8] Crocker, D. and P. Overell, "Augmented BNF for Syntax 521 Specifications: ABNF", STD 68, RFC 5234, January 2008. 523 [9] Leach, P., Mealling, M., and R. Salz, "A Universally Unique 524 IDentifier (UUID) URN Namespace", RFC 4122, July 2005. 526 [10] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., 527 Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP: 528 Session Initiation Protocol", RFC 3261, June 2002. 530 Authors' Addresses 532 Michael Montemurro (editor) 533 Research in Motion (RIM) 534 4701 Tahoe Dr 535 Mississauga, Ontario L4W 0B4 536 Canada 538 Phone: unlisted 539 Fax: unlisted 540 Email: mmontemurro@rim.com 542 Andrew Allen 543 Research in Motion (RIM) 544 1200 Sawgrass Corporate Parkway 545 Sunrise, Florida 33323 546 USA 548 Phone: unlisted 549 Fax: unlisted 550 Email: aallen@rim.com 552 David McDonald 553 unaffiliated 555 Phone: unlisted 556 Fax: unlisted 557 Email: mcdonalddm@hotmail.com 558 Paul Gosden 559 GSM Association 560 1st Floor, Mid City Place, 71 High Holborn, 561 London 562 England 564 Phone: unlisted 565 Fax: unlisted 566 Email: pgosden@gsm.org