RFC 7255: Using the International Mobile station Equipment Identity (IMEI) Uniform Resource Name (URN) as an Instance ID
In plain English — editorial summary, not part of the RFC
This specification defines how the Uniform Resource Name (URN) reserved for the Global System for Mobile Communications Association (GSMA) identities and its sub-namespace for the International Mobile station Equipment Identity (IMEI) can be used as an instance-id. Its purpose is to fulfill the requirements for defining how a specific URN needs to be constructed and used in the '+sip.instance' Contact header field parameter for outbound behavior.
Document record
- Document ID
- RFC7255
- Published
- May 2014
- Authors
- A. Allen
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7254A Uniform Resource Name Namespace for the Global System for Mobile Communications Association (GSMA) and the International Mobile station Equipment Identity (IMEI)Current
May 2014
- RFC 8498A P-Served-User Header Field Parameter for an Originating Call Diversion (CDIV) Session Case in the Session Initiation Protocol (SIP)Current
February 2019
- RFC 75493GPP SIP URI Inter-Operator Traffic Leg ParameterCurrent
May 2015
- RFC 7913P-Access-Network-Info ABNF UpdateCurrent
June 2016
- RFC 7976Updates to Private Header (P-Header) Extension Usage in Session Initiation Protocol (SIP) Requests and ResponsesObsoleted
September 2016
- RFC 8101IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespace for Mission Critical Push To Talk ServiceCurrent
March 2017
- RFC 8464A URN Namespace for Device Identity and Mobile Equipment Identity (MEID)Current
September 2018
- RFC 8465Using the Mobile Equipment Identity (MEID) URN as an Instance IDCurrent
September 2018
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?