RFC 7254
A Uniform Resource Name Namespace for the Global System for Mobile Communications Association (GSMA) and the International Mobile station Equipment Identity (IMEI)
RFC 7254: A Uniform Resource Name Namespace for the GSMA and the IMEI 🎀
Okay bestie, the header is giving Informational 💅. This is not a Standards Track spec, it's published "for informational purposes" 📚. It came out in May 2014 and has ISSN 2070-1721 ✨. The editor is M. Montemurro, and the co-authors are A. Allen (Blackberry), D. McDonald (Eircom), and P. Gosden (GSM Association) 🫶. The header doesn't list anything it obsoletes or updates, so it's standing on its own 🌸.
Abstract
okay so this spec defines a Uniform Resource Name (URN) namespace for the Global System for Mobile Communications Association (GSMA) 🌈. It also defines a Namespace Specific String (NSS) for the International Mobile station Equipment Identity (IMEI), plus an associated parameter for the International Mobile station Equipment Identity and Software Version number (IMEISV) 📱. The IMEI and IMEISV started out in the GSM specs, and the 3rd Generation Partnership Project (3GPP) has since folded them into its specs for GSM, Universal Mobile Telecommunications System (UMTS), and 3GPP Long Term Evolution (LTE) networks 🦋. These IDs uniquely identify Mobile Equipment across all of those systems, and the GSMA manages them 💜.
⚠️ Heads up, bestie: URNs from this namespace almost always contain personally identifiable information, so they need to be treated accordingly 🙈.
Status of This Memo
This document is not an Internet Standards Track specification. It's published for informational purposes 🎀.
It's a product of the Internet Engineering Task Force (IETF) and represents the consensus of the IETF community 🫶. It went through public review and was approved for publication by the Internet Engineering Steering Group (IESG) ✨. Not every IESG-approved document is a candidate for any level of Internet Standard, so check Section 2 of RFC 5741 if you're curious 🧚.
For the current status, any errata, and how to send feedback, go to http://www.rfc-editor.org/info/rfc7254 🔗.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved 💖.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info), as they stand on the publication date. Read these carefully because they spell out your rights and restrictions for this doc 📜. Code Components pulled out of this document must include Simplified BSD License text, as described in Section 4.e of the Trust Legal Provisions, and they come with no warranty, as described in the Simplified BSD License 💅.
This document may include material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008 🌸. The people who control the copyright in some of that material may not have let the IETF Trust allow modifications outside the IETF Standards Process 🙈. Unless you get a proper license from those copyright holders, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process. The exceptions are formatting it for publication as an RFC or translating it into languages other than English 🦋.
Table of Contents
1. Introduction ....................................................3
2. Terminology .....................................................4
3. Namespace Registration Template .................................4
4. Specification ...................................................8
4.1. IMEI Parameters ............................................8
4.2. IMEI Format ................................................9
4.2.1. Type Allocation Code (TAC) ..........................9
4.2.2. Serial Number (SNR) .................................9
4.2.3. Spare ..............................................10
4.2.4. Binary Encoding ....................................10
4.3. IMEISV Format .............................................10
4.3.1. Type Allocation Code (TAC) .........................10
4.3.2. Serial Number (SNR) ................................11
4.3.3. Software Version Number (SVN) ......................11
4.3.4. Binary Encoding ....................................11
5. Community Considerations .......................................11
6. Namespace Considerations .......................................12
7. IANA Considerations ............................................12
8. Security and Privacy Considerations ............................12
9. Acknowledgements ...............................................14
10. References ....................................................14
10.1. Normative References .....................................14
10.2. Informative References ...................................151. Introduction ✨
okay so this spec defines a Uniform Resource Name (URN) namespace for the Global System for Mobile Communications Association (GSMA), plus a Namespace Specific String (NSS) for the International Mobile station Equipment Identity (IMEI) 🎀. It also defines an associated parameter for the International Mobile station Equipment Identity and Software Version number (IMEISV). This all follows the namespace registration requirement in RFC 3406 [1] 💅. The Namespace Identifier (NID) 'gsma' is for identities used in GSM, Universal Mobile Telecommunications System (UMTS), and Long Term Evolution (LTE) networks 📱. The GSMA manages the IMEI and IMEISV, so it also manages this NID 🫶.
For now, this spec only defines the 'imei' NSS under the 'gsma' NID. The GSMA may add more NSS under 'gsma' later, using the procedure for URN NSS changes and additions. Right now that procedure is publishing future Informational RFCs approved by IETF consensus 🌈.
The IMEI is 15 decimal digits long 🔢. It has a Type Allocation Code (TAC) of 8 decimal digits, a Serial Number (SNR) of 6 decimal digits, and then one Spare decimal digit 💖. The TAC tells you the type of the Mobile Equipment. It's picked from a range allocated to the Mobile Equipment manufacturer, so it identifies the model 🦋. The SNR is an individual serial number that uniquely identifies each device within its TAC ✨. The Spare digit works as a Check digit to validate the IMEI, and the Mobile Equipment always sends it as 0 🧚.
The IMEISV is 16 decimal digits long 🔢. It has the same TAC and SNR as the IMEI, plus a 2 decimal digit Software Version Number (SVN) 🌸. The manufacturer of the Mobile Equipment allocates the SVN to identify the software version of the device 💜.
This doc is meant to be a concise guide for people who want to use the IMEI and IMEISV as URNs 📚. Nothing in it should be read as overriding 3GPP Technical Specification (TS) 23.003 [2], which is the spec that defines the IMEI and IMEISV 🙈.
The GSMA is a global trade association representing nearly 800 mobile phone operators across 220 territories and countries 🌍. Its main goals are making sure mobile phones and wireless services work globally and are easy to access 💅. If you want more on the GSMA's role in allocating the IMEI and IMEISV, plus the allocation guidelines, check GSMA Permanent Reference Document (PRD) TS.06 [3] 🎀.
2. Terminology 🦋
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [4] 💖.
to be continued in part 2 🎀💜
3. Namespace Registration Template 🎀
Okay bestie, this is the registration form for the gsma namespace, and it's giving very official paperwork energy 📋💅
- Namespace ID:
'gsma' - Registration version number: 1
- Registration date: 2014-01-12
- Declared registrant of the namespace: the registering organization below
Registering organization:
- Name: GSM Association
- Address: 1st Floor, Mid City Place, 71 High Holborn, London, England
Designated contact person:
- Name: Paul Gosden
- Coordinates: pgosden@gsma.com
Declaration of syntactic structure: the identifier is written in American Standard Code for Information Interchange (ASCII) characters and has a hierarchical structure, written in Augmented Backus-Naur Form (ABNF) as defined in RFC 5234 [5]. Here's the grammar 🧚
gsma-urn = "urn:" gsma-NID ":" gsma-NSS
gsma-NID = "gsma"
gsma-NSS = imei-specifier / future-gsma-specifier
imei-specifier = "imei:" ( imeival / ext-imei )
[ ";" sw-version-param ]
[ ";" imei-version-param ]
ext-imei = gsma-defined-nonempty ;GSMA defined and
;IETF consensus
;required
sw-version-param = "svn=" software-version
imei-version-param = "vers=" imei-version-val
software-version = 2DIGIT
imei-version-val = DIGIT
future-gsma-specifier = future-specifier
*( ";" future-param )
future-specifier = gsma-defined-nonempty ;GSMA defined
future-param = par-name [ EQUAL par-value ]
par-name = gsma-defined-nonempty
par-value = gsma-defined-nonempty
EQUAL = "="
gsma-defined-nonempty = 1*gsma-urn-char
gsma-urn-char = ALPHA / DIGIT
/ "-" / "." / "_" / "%" / ":"An NSS for the IMEI is defined under the 'gsma' NID. An IMEI is an identifier under the 'gsma' NID that uniquely identifies the mobile devices used in the GSM, UMTS, and LTE networks 📱✨
The representation of the IMEI is defined in 3GPP TS 23.003 [2]. To represent an IMEI that arrives in a cellular signaling message (see 3GPP TS 24.008 [6]) as a URN, you have to convert the received binary (Binary Coded Decimal (BCD)) encoded bit sequence into a decimal digit string. Each field gets its human-readable form as a decimal digit string, with the most significant digit first 🔢
The following ABNF includes the set of core rules in RFC 5234 [5], and the core rules are not repeated here. A URN with the imei NSS contains one imeival, and its formal definition is given by this ABNF (RFC 5234) [5]:
imeival = tac "-" snr "-" spare
tac = 8DIGIT
snr = 6DIGIT
spare = DIGIT<future-gsma-specifier> and <gsma-defined-nonempty> can be made up of any ASCII characters that follow the ABNF above 🌈
The GSMA will take responsibility for the 'gsma' namespace, including the imei NSS. Additional NSS may be added for future identifiers the GSMA needs, at their discretion. Only URNs with the imei NSS count as "GSMA IMEI URNs". Using other NSS that might be defined in the future in IETF protocols will require IETF consensus 🤝
Relevant ancillary documentation: see IMEI Allocation and Approval Guidelines (GSMA PRD TS.06) [3] and 3GPP TS 23.003 [2].
Identifier uniqueness considerations: identifiers under the 'gsma' NID are defined and assigned by the GSMA, after making sure the URNs being assigned are unique. Uniqueness is checked against the IANA registry of previously assigned names 🔍
Procedures are in place so that each IMEI is uniquely assigned by the Mobile Equipment manufacturer, which guarantees it uniquely identifies that particular Mobile Equipment device. Procedures are also in place so that each IMEISV is uniquely assigned by the Mobile Equipment manufacturer, which guarantees it uniquely identifies that particular Mobile Equipment device and the specific software version installed 💖
Identifier persistence considerations: the GSMA is committed to keeping every resource identified by an assigned URN unique and persistent 💜
Since the NID sought is 'gsma', and "GSMA" is the long-standing acronym for the trade association representing the mobile phone operators, the URN should also persist indefinitely (at least as long as there is a need for its use). The assignment process makes sure names are never reassigned, and the binding between the name and its resource is permanent 🦋
The TAC and SNR portions of the IMEI and IMEISV are permanently stored in the Mobile Equipment, so they stay persistent for as long as the Mobile Equipment exists. The process for TAC and SNR assignment is documented in GSMA PRD TS.06 [3], and once assigned, TAC and SNR values are not reassigned to other Mobile Equipment devices. The SVN portion of the IMEISV may be changed by software when new versions are installed, but it should stay persistent for the whole life of that specific software version installation 🌸
Process of identifier assignment: the GSMA will manage the <NSS> (including imei) and <future-gsma-specifier> identifier resources to keep everything unique. The process for IMEI and IMEISV assignment is documented in GSMA PRD TS.06 [3] 🎀
Process for identifier resolution: since the 'gsma' NSS is not currently globally resolvable, this one is not applicable 🙈
Rules for Lexical Equivalence: two GSMA IMEI URNs are equivalent if they have the same imeival value and the same parameter values in the same sequential order. The one exception is that the vers=0 parameter gets ignored for comparison purposes. All of these comparisons are case insensitive 🔤
Any identifier in the 'gsma' NSS can be compared using the normal mechanisms for percent-encoded UTF-8 strings (see RFC 3629 [7]) 🧁
Conformance with URN Syntax: the string representation of the 'gsma' NID and the imei NSS is fully compatible with the URN syntax (see RFC 2141 [8]) ✅
Validation mechanism: the IMEI can be validated using the mechanism defined in Annex B of 3GPP TS 23.003 [2]. There's no mechanism defined to validate the SVN field of the IMEISV 🙃
Scope: the GSMA URN is global in scope 🌍
4. Specification ✨
4.1. IMEI Parameters 🌷
Okay so the optional vers parameter and the ext-imei field in the ABNF are there for extensibility of the imei NSS. For example, if the IMEI format gets extended in the future (like with extra digits or hex digits), the vers parameter would hold a non-zero value and ext-imei would be further defined to represent the syntax of the extended IMEI format. A vers value of 0, or no vers parameter at all, means the URN format complies with the format specified here 💅
Any change to the format of the imei NSS requires the procedure for URN NSS changes and additions (currently done through the publication of future Informational RFCs approved by IETF consensus). The vers parameter was picked for extensibility instead of defining a new NSS (like imei2) because lots of applications will probably only need to do string compares of the imeival. So even if the format or length of the imeival changes later, those applications should keep working without needing an update to understand a new NSS 🫶
RFC 7255 [10] specifies how the GSMA IMEI URN can be used as an instance ID, as specified in RFC 5626 [11]. Any future value of the vers parameter other than 0, or the definition of extra parameters meant to be part of an instance ID, will require an update to RFC 7255 [10] 🔥
For example:
urn:gsma:imei:90420156-025763-0;vers=0The IMEISV is an identifier that uniquely identifies mobile devices and their associated software versions used in the GSM, UMTS, and LTE networks. The representation of the IMEISV is defined in 3GPP TS 23.003 [2] 📲
To represent the IMEISV, the URN parameter svn is appended to the GSMA IMEI URN and set equal to the decimal string representation of the two software version number (svn) digits in the IMEISV. The Spare digit in the IMEI imeival is set to zero 🍓
For example:
urn:gsma:imei:90420156-025763-0;svn=424.2. IMEI Format 🧚♀️
4.2.1. Type Allocation Code (TAC) 🦋
The TAC is an 8 decimal digit value. It identifies the type of the Mobile Equipment and is chosen from a range of values allocated to the Mobile Equipment manufacturer, so it can uniquely identify the model of the Mobile Equipment 🌸
4.2.2. Serial Number (SNR) 🔢
The SNR is a 6 decimal digit value. It's an individual serial number that uniquely identifies each Mobile Equipment device within the TAC 💜
4.2.3. Spare ⚠️
The Spare is a single decimal digit. When the IMEI is stored on the Mobile Equipment and on network equipment, it holds a value used as a Check digit, which is meant to avoid manual reporting errors (for example, when customers register stolen mobiles at the operator's customer care desk) and to help guard against incorrect entries being provisioned in the network equipment. The Spare is always set to zero when transmitted by the Mobile Equipment (including in the IMEI URN format). Annex B of 3GPP TS 23.003 [2] specifies a mechanism for computing the actual Check digit in order to validate the TAC and SNR 🫧
4.2.4. Binary Encoding 💾
When included in a cellular signaling message, the IMEI format is 15 decimal digits encoded in 8 octets, using BCD as defined in 3GPP TS 24.008 [6]. Figure 1 is an abstract representation of a BCD-encoded IMEI stored in memory (the actual storage format in memory is implementation specific). In Figure 1, the most significant digit of the TAC is coded in the least significant bits of octet 1. The most significant digit of the SNR is coded in the least significant bits of octet 5. The Spare digit is coded in the least significant bits of octet 8. When included in an identity element in a cellular signaling message, the most significant digit of the TAC is included in digit 1 of the identity element in Figure 10.5.4 of 3GPP TS 24.008 [6] 🎀
14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Decimal Digits
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| | | S|
| T | S | p|
| A | N | a|
| C | R | r|
| | | e|
+--+-----+-----+-----+--+--+-----+-----+--+--+
1 2 3 4 5 6 7 8 Octets
Figure 1: IMEI Format4.3. IMEISV Format 🌈
4.3.1. Type Allocation Code (TAC) 🫶
The TAC is the same as the TAC in the IMEI (see Section 4.2.1) ✨
4.3.2. Serial Number (SNR) 🌷
The SNR is the same as the SNR in the IMEI (see Section 4.2.2) 💖
4.3.3. Software Version Number (SVN) 🎀
okay so the Software Version Number is the bit the mobile device manufacturer hands out to say which software version the device is running 💖
4.3.4. Binary Encoding 🧚
okay this part is giving math nerd energy ✨ when the IMEISV shows up in a cellular signaling message, it's 16 decimal digits squished into 8 octets using BCD, as defined in 3GPP TS 24.008 [6] 🔢 Figure 2 is an abstract picture of a BCD-encoded IMEISV stored in memory (how it actually gets stored is up to each implementation, so don't stress 🙈). In Figure 2, the most significant digit of the TAC lives in the most significant bits of octet 1, the most significant digit of the SNR lives in the most significant bits of octet 5, and the most significant digit of the SVN lives in the most significant bits of octet 8. When it's included in an identity element in a cellular signaling message, the most significant digit of the TAC goes in digit 1 of the identity element in Figure 10.5.4 of 3GPP TS 24.008 [6] 🦋
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Decimal Digits
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| | | |
| T | S | S |
| A | N | V |
| C | R | N |
| | | |
+-----+-----+-----+-----+-----+-----+-----+-----+
1 2 3 4 5 6 7 8 Octets
Figure 2: IMEISV Format5. Community Considerations 🌈
okay so GSM, UMTS, and LTE mobile devices are going to be vibing with Internet devices for all kinds of voice and data services 📱 To make that work, they need Internet protocols that operate end to end between devices in GSM/UMTS/LTE networks and devices on the general Internet. Some of these protocols need URNs as identifiers. Inside GSM/UMTS/LTE networks, mobile devices are identified by their IMEI or IMEISV. Internet users need to be able to receive and include the GSMA URN in various Internet protocol elements so pure Internet devices and GSM/UMTS/LTE mobile devices can talk to each other 🫶 That means the existence and syntax of these namespaces need to be available to the general Internet community, and the namespace needs to be reserved with IANA so it's guaranteed unique and avoids namespace conflicts both on the Internet and inside GSM/UMTS/LTE networks 🔒 On the flip side, Internet implementations generally won't have IMEI identifiers. The identifiers those implementations generate will typically be URNs in namespaces other than 'gsma', and depending on context they might even be non-URN URIs ✨ Implementations are advised to be ready to process URIs other than 'gsma' namespaced URNs, which helps interoperability 💅
6. Namespace Considerations 💜
a URN was picked as the most appropriate URI to represent the IMEI and IMEISV 🦋 The reason is that these identifiers can be used and transported similarly to the Universally Unique Identifier (UUID), which is defined as a URN in RFC 4122 [12]. Protocols that transport device identifiers often require the device identifier to be globally unique and in URN format, so the URN formats have to be defined to represent the IMEI and IMEISV 🌸
7. IANA Considerations 🦋
okay so in accordance with BCP 66 (RFC 3406) [1], IANA has registered the Formal URN Namespace 'gsma' in the "Uniform Resource Names (URN) Namespaces" registry, using the registration template presented in Section 3 of this document 🎀
8. Security and Privacy Considerations 💀
okay this is the serious section, bestie, so read it slowly 🙈 IMEIs (but with the Spare value set to the value of the Check digit) are displayable on most mobile devices, and in lots of cases they're printed on the case inside the battery compartment. Anyone with brief physical access to the mobile device can easily get the IMEI. So IMEIs MUST NOT be used as security capabilities (identifiers whose mere possession grants access). Unfortunately, some applications are currently using the IMEI for authorization, and some service provider customer service departments have been known to treat knowing the IMEI as "proof" that the caller is the legit owner of the device 😤 Both of these are inappropriate uses of the IMEI 🙅♀️
Next, the specific software version of the mobile device only identifies the lower-layer software that passed certification testing. It doesn't identify the operating system or application software. Even so, the software version could identify software that's vulnerable to attacks or known to contain security holes 👀
🚨 So the IMEISV MUST only be delivered to trusted entities within carrier networks and not provided to the Internet at large, because it could help a malicious device figure out that the mobile device is running software known to be vulnerable to certain attacks. This concern is similar to the concerns about the User-Agent header in the Session Initiation Protocol (SIP) as specified in RFC 3261 [13]. Therefore, the IMEISV (that is, the IMEI URN with a 'svn' parameter) MUST NOT be delivered to devices that are not trusted. IMEIs are almost always personally identifiable information, so these URNs MUST be treated as personally identifiable information in all cases. To prevent violating a user's privacy, the IMEI URN MUST NOT be included in messages intended to convey any level of anonymity. 🚨
Since the IMEI is permanently assigned to the mobile device and isn't modified when the ownership of the device changes (even after a complete software reload), the IMEI URN MUST NOT be used as a user identifier or user address by an application 🙅♀️ Using the IMEI to identify a user or as a user address could mean communications meant for a previous owner end up with the new owner, or could let the new owner access information or services belonging to the previous owner 😬
Also, since the IMEI identifies the mobile device, it could potentially be used to track users and for surveillance and call data mining if it's sent in the clear 👁️
Since the IMEI is personally identifiable information, uses of the IMEI URN with IETF protocols require a specification and IETF Expert Review [14] so privacy concerns get addressed properly 🫧 Protocols carrying the IMEI URN SHOULD at a minimum use channels that are strongly hop-by-hop encrypted, and it is RECOMMENDED that end-to-end encryption be used 🔐
Additional security considerations are specified in 3GPP TS 22.016 [9]. Specifically, the IMEI is supposed to be incorporated in a module 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) 🛡️
9. Acknowledgements 🫶
this document draws heavily on the 3GPP work on Numbering, Addressing, and Identification in 3GPP TS 23.003 [2], and also on the style and structure used in RFC 4122 [12]. The authors want to thank Cullen Jennings, Lisa Dusseault, Dale Worley, Ivo Sedlacek, Atle Monrad, James Yu, Mary Barnes, Tim Bray, S. Moonesamy, Alexey Melnikov, Martin Duerst, John Klensin, Paul Kyzivat, Christer Holmberg, Barry Leiba, and Stephen Farrell for their help and comments 💖
10. References 📚
10.1. Normative References
- [1] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, "Uniform Resource Names (URN) Namespace Definition Mechanisms", BCP 66, RFC 3406, October 2002.
- [2] 3GPP, "Numbering, addressing and identification", 3GPP TS 23.003 (Release 8), March 2014,
ftp://ftp.3gpp.org/Specs/archive/23_series/23.003/. - [3] GSM Association, "IMEI Allocation and Approval Guidelines", PRD TS.06 (DG06) Version 6.0, July 2011,
<http://www.gsma.com/newsroom/wp-content/uploads/2012/06/ts0660tacallocationprocessapproved.pdf>. - [4] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
- [5] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008.
- [6] 3GPP, "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3", 3GPP TS 24.008 (Release 8), June 2013,
ftp://ftp.3gpp.org/Specs/archive/24_series/24.008/. - [7] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003.
- [8] Moats, R., "URN Syntax", RFC 2141, May 1997.
- [9] 3GPP, "International Mobile station Equipment Identities (IMEI)", 3GPP TS 22.016 (Release 8), December 2009,
ftp://ftp.3gpp.org/Specs/archive/22_series/22.016/.
10.2. Informative References
- [10] Allen, A., Ed., "Using the International Mobile station Equipment Identity (IMEI) Uniform Resource Name (URN) as an Instance ID", RFC 7255, May 2014.
- [11] Jennings, C., Mahy, R., and F. Audet, "Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)", RFC 5626, October 2009.
- [12] Leach, P., Mealling, M., and R. Salz, "A Universally Unique IDentifier (UUID) URN Namespace", RFC 4122, July 2005.
- [13] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP: Session Initiation Protocol", RFC 3261, June 2002.
- [14] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
Authors' Addresses 🎀
Michael Montemurro (editor) Blackberry 4701 Tahoe Dr. Mississauga, Ontario L4W 0B4 Canada
EMail: mmontemurro@blackberry.com
Andrew Allen Blackberry 1200 Sawgrass Corporate Parkway Sunrise, Florida 33323 USA
EMail: aallen@blackberry.com
David McDonald Eircom
EMail: David.McDonald@meteor.ie
Paul Gosden GSM Association 1st Floor, Mid City Place, 71 High Holborn London England
EMail: pgosden@gsma.com
📦 where this page comes from
- ietf: rfc7254 2014-05
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms