idnits 2.17.1 draft-montemurro-gsma-imei-urn-06.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 are 2 instances of too long lines in the document, the longest one being 9 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHALL not' in this paragraph: Additional security considerations are specified in 3GPP TS 22.016 [7]. Specifically the IMEI is to be incorporated in a module which is contained within the terminal. The IMEI SHALL not be changed after the terminal's production process. It SHALL resist tampering, i.e. manipulation and change, by any means (e.g. physical, electrical and software). -- 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 (January 7, 2011) is 4850 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 3406 (ref. '1') (Obsoleted by RFC 8141) ** Obsolete normative reference: RFC 2141 (ref. '5') (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: July 11, 2011 D. McDonald 6 unaffiliated 7 P. Gosden 8 GSM Association 9 January 7, 2011 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-06 15 Abstract 17 This specification defines a Uniform Resource Name namespace for the 18 GSMA and a sub namespace for the IMEI (International Mobile station 19 Equipment Identity), and associated parameter for the IMEISV 20 (International Mobile station Equipment Identity and Software Version 21 number). The IMEI is 15 decimal digits long and the IMEISV is 16 22 decimal digits long and both are encoded using Binary Encoded Decimal 23 (BCD). The IMEI and IMEISV were introduced as part of the 24 specification for Global System for Mobile (GSM) and are also now 25 incorporated by the 3rd Generation Partnership Project (3GPP) as part 26 of the 3GPP specification for GSM, the Universal Mobile 27 Telecommunications System (UMTS) and 3GPP LTE (Long Term Evolution). 28 The IMEI and IMEISV are used to uniquely identify Mobile Equipment 29 within these systems and are managed by the GSMA (GSM Association). 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 July 11, 2011. 48 Copyright Notice 49 Copyright (c) 2011 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 . . . . . . . . . . . . . . . . . . 12 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 GSMA is an identifier for 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 218 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 PRD DG.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: 2006-10-11 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-param-name *1("=" gsma-specifier-param-val) 193 software-version-string = 2DIGIT 194 gsma-format-version-string = DIGIT 195 gsma-approved-string = *unreserved 196 gsma-approved-nonempty-string = 1*unreserved 197 unreserved = ALPHA / DIGIT / "-" / "." / "_" 199 The GSMA namespace includes a predefined namespace for IMEI and 200 may be in the future extended to include other identifiers used by 201 Mobile Equipment used in GSM, UMTS or LTE networks or future 202 networks deployed by members of the GSMA. 204 A IMEI is an identifier under the GSMA namespace that uniquely 205 identifies Mobile Equipment used in GSM, UMTS and LTE networks. 207 The internal representation of a IMEI is a specific sequence of 208 bits in memory, as described in 3GPP TS 23.003 [2]. To accurately 209 represent a IMEI as a URN, it is necessary to convert the BCD bit 210 sequence to a string representation. Each field BCD bit sequence 211 has its value printed as a decimal digit string with the most 212 significant digit first. 214 The following augmented Backus-Naur Form (ABNF) includes the set 215 of core rules in RFC 5234 [8], and are not repeated here. 217 The formal definition of the IMEI string representation for the 218 gsma-specifier-defined-substring for the "imei" gsma-specifier is 219 provided by the following ABNF [8]: 221 IMEI = tac "-" snr "-" spare 222 tac = 8DIGIT 223 snr = 6DIGIT 224 spare = 1DIGIT 225 For example: 226 urn:gsma:imei:90420156-025763-0;vers=0 228 The optional "vers" parameter is included for extensibility of the 229 namespace, for example if the IMEI format is extended in the 230 future (such as with additional digits or using hex digits). A 231 value of "vers" equal to 0 or the absence of the "vers" parameter 232 means the URN format is compliant with the format specified here. 233 Any change to the format specified here requires the publication 234 of a future informational RFC. 236 The IMEISV is an identifier that uniquely identifies Mobile 237 Equipment and associated software versions used in GSM and UMTS 238 networks. The internal representation of a IMEISV is a specific 239 sequence of bits in memory, as described in 3GPP TS 23.003 [2] 240 To represent the IMEISV the URN parameter "svn" is appended to the 241 IMEI URN and set equal to the decimal string representation of the 242 two software version number (svn) bits in the IMEISV and the spare 243 digit in the IMEI gsma-specifier-defined-substring is set to zero. 245 For example: 246 urn:gsma:imei:90420156-025763-0;svn=42 248 The , , , , and can 251 comprise any ASCII characters compliant with URN syntax and must 252 not contain the ":" character or ";" character or "=" 253 character(see STD 66, RFC 2141 [5]). The exclusion of the colon 254 from the list of other characters means that the colon can only 255 occur as a delimiter between string values. The exclusion of the 256 semicolon from the list of other characters means that the 257 semicolon can only occur as a delimiter for parameter values. The 258 exclusion of the "=" character from the list of other characters 259 means that the "=" chanracter can only occur as an operator for 260 parameter values. 262 The GSMA will take responsibility for the gsma-specifier "imei" 263 and manage the sub level. 265 Additional gsma-specifiers may be added in the future through 266 informational RFCs. 268 Relevant ancillary documentation: 269 See IMEI Allocation and Approval Guidelines [3] and 3GPP TS 23.003 270 [2]. 272 Identifier uniqueness considerations: 273 Identifiers in the "gsma" namespace are defined and assigned in 274 the requested namespace by the GSMA after ensuring that the URNs 275 to be assigned are unique. Uniqueness is achieved by checking 276 against the registry of previously assigned names. 278 Procedures are in place to ensure that each IMEI is uniquely 279 assigned by the Mobile Equipment manufacturer so that it is 280 guaranteed to uniquely identify that particular Mobile Equipment. 281 Procedures are in place to ensure that each IMEISV is uniquely 282 assigned by the Mobile Equipment manufacturer so that it is 283 guaranteed to uniquely identify that particular Mobile Equipment 284 and the specific software version installed. 286 Identifier persistence considerations: 287 The GSMA is committed to maintaining uniqueness and persistence of 288 all resources identified by assigned URNs. 290 As the NID sought is "gsma" and GSMA is the long standing acronym 291 for the trade association that represents the mobile phone 292 operators the URN should also persist indefinitely (at least as 293 long as there is a need for its use). The assignment process 294 guarantees that names are not reassigned. The binding between the 295 name and its resource is permanent. 297 The TAC and SNR portions of IMEISVs are stored in the Mobile 298 Equipment so they remain persistent. The SVN may be modified by 299 software when new versions are installed but should be persistent 300 for the duration of the installation of that specific version of 301 software. 303 Process of identifier assignment: 304 GSMA will manage the (including "imei"), , , , and identifier resources to maintain uniqueness. 309 The process for IMEI and IMEISV assignment is documented in GSMA 310 PRD DG.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 Consider each field of the IMEI gsma-defined substring to be a 318 sequence of decimial digits. Then, to compare a pair of IMEIs, 319 arithmetically compare the corresponding fields of the gsma- 320 defined substring from each IMEI in order of significance and 321 according to their data type. Two IMEIs are equal if and only if 322 all the corresponding fields are equal. 324 The lexical equivalence of the GSMA namespace-specific strings 325 (NSSs) is defined as an exact, but not case-sensitive, string 326 match. 328 Any identifier in GSMA namespaces can be compared using the normal 329 mechanisms for percent-encoded UTF-8 strings. 331 Conformance with URN Syntax: 332 The string representation of the GSMA URN and of the IMEI sub 333 namespace is fully compatible with the URN syntax. 335 Validation Mechanism: 336 The IMEI can be validated using the mechanism defined in Annex B 337 of 3GPP TS 23.003 [2]. There is no mechanism defined to validate 338 the SVN field of the IMEISV. 340 Scope: GSMA URN is global in scope. 342 4. Specification 344 4.1. IMEI Format 346 The IMEI format is 15 decimal digits encoded in 8 octets using BCD as 347 defined in 3GPP TS 24.008 [6]. The most significant digit is coded 348 in the most significant bits of octet 1. The least significant digit 349 is coded in the least significant bits of octet 8. 351 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Decimal Digits 352 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 353 | | | S| 354 | T | S | p| 355 | A | N | a| 356 | C | R | r| 357 | | | e| 358 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 359 1 2 3 4 5 6 7 8 Octets 361 4.1.1. Type Allocation Code (TAC) 363 The TAC is a 8 decimal digit value. The TAC identifies the type of 364 the Mobile Equipment and is chosen from a range of values allocated 365 to the Mobile Equipment manufacturer in order to uniquely identify 366 the model of the Mobile Equipment. 368 4.1.2. Serial Number (SNR) 370 The SNR is a 6 decimal digit value. The SNR is an individual serial 371 number that uniquely identifies each Mobile Equipment within the TAC. 373 4.1.3. Spare 375 The Spare is a single decimal digit that is used as a security check 376 digit to combat potential spoofing. The Spare is always set to zero 377 when transmitted by the Mobile Equipment. Annex B of 3GPP TS 23.003 378 [2] defines a mechanism for computing the actual check digit in order 379 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 [6]. 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. Many 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. 429 6. Namespace considerations 431 A URN was considered the most appropriate URI to represent the IMEI 432 and IMEISV as these identifiers may be used and transported similarly 433 to the Universally Unique Identifier (UUID)which is defined as a URN 434 in [9]. Since specifications for protocols that are used to 435 transport device identifiers often require the device identifier to 436 be globally unique and in the URN format it is necessary that the URN 437 formats are defined to represent the IMEI and IMEISV. 439 7. IANA considerations 441 In accordance with BCP 66 [1], IANA is asked to register the Formal 442 URN Namespace 'GSMA' in the Registry of URN Namespaces, using the 443 registration template presented in Section 3 of this document. 445 8. Security considerations 447 IMEIs (with the Spare value set to zero) are displayable on most 448 Mobile Equipment; therefore, they must not be used as security 449 capabilities (identifiers whose mere possession grants access), for 450 example. 452 Revealing the specific software version of the terminal might make 453 the terminal more vulnerable to attacks against software that is 454 known to contain security holes. Care therefore should be taken 455 regarding use of the IMEISV as it could help a malicious device 456 identify Mobile Equipment running software that is known to be 457 vulnerable to certain attacks. This is a similar concern to the use 458 of the User-Agent header in SIP as specified in RFC 3261 [10]. It is 459 therefore RECOMMENDED that the IMEISV is not delivered to devices 460 that are not trusted. 462 Additional security considerations are specified in 3GPP TS 22.016 463 [7]. Specifically the IMEI is to be incorporated in a module which 464 is contained within the terminal. The IMEI SHALL not be changed 465 after the terminal's production process. It SHALL resist tampering, 466 i.e. manipulation and change, by any means (e.g. physical, electrical 467 and software). 469 9. Acknowledgements 471 This document draws heavily on the 3GPP work on Numbering, Addressing 472 and Identification in 3GPP TS 23.003 [2] and also on the style and 473 structure used in RFC 4122 [9]. The authors would like to thank 474 Cullen Jennings, Lisa Dusseault, and Dale Worley for their help and 475 comments. 477 10. References 479 10.1. Normative references 481 [1] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, 482 "Uniform Resource Names (URN) Namespace Definition Mechanisms", 483 BCP 66, RFC 3406, October 2002. 485 [2] 3GPP, "TS 23.003: Numbering, addressing and identification 486 (Release 8)", 3GPP 23.003, September 2008, 487 . 489 [3] GSMA Association, "IMEI Allocation and Approval Guidelines", 490 PRD DG.06 version 3.6, February 2008, 491 . 493 [4] Bradner, S., "Key words for use in RFCs to Indicate Requirement 494 Levels", BCP 14, RFC 2119, March 1997. 496 [5] Moats, R., "URN Syntax", RFC 2141, May 1997. 498 [6] 3GPP, "TS 24.008: Mobile radio interface Layer 3 specification; 499 Core network protocols; Stage 3 (Release 8)", 3GPP 24.008, 500 September 2008, 501 . 503 [7] 3GPP, "TS 22.016: International Mobile station Equipment 504 Identities (IMEI)(Release 7)", 3GPP 22.016, May 2007, 505 . 507 10.2. Informative references 509 [8] Crocker, D. and P. Overell, "Augmented BNF for Syntax 510 Specifications: ABNF", STD 68, RFC 5234, January 2008. 512 [9] Leach, P., Mealling, M., and R. Salz, "A Universally Unique 513 IDentifier (UUID) URN Namespace", RFC 4122, July 2005. 515 [10] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., 516 Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP: 517 Session Initiation Protocol", RFC 3261, June 2002. 519 Authors' Addresses 521 Michael Montemurro (editor) 522 Research in Motion (RIM) 523 4701 Tahoe Dr 524 Mississauga, Ontario L4W 0B4 525 Canada 527 Phone: unlisted 528 Fax: unlisted 529 Email: mmontemurro@rim.com 531 Andrew Allen 532 Research in Motion (RIM) 533 2550 West Golf Road 534 Rolling Meadows, Illinois 60008 535 USA 537 Phone: unlisted 538 Fax: unlisted 539 Email: aallen@rim.com 541 David McDonald 542 unaffiliated 544 Phone: unlisted 545 Fax: unlisted 546 Email: mcdonalddm@hotmail.com 548 Paul Gosden 549 GSM Association 550 1st Floor, Mid City Place, 71 High Holborn, 551 London 552 England 554 Phone: unlisted 555 Fax: unlisted 556 Email: pgosden@gsm.org