⌕ Поиск по атласу

IETF · RFC · RFC8465

RFC8465 · Using the Mobile Equipment Identity (MEID) URN as an Instance ID

Using the Mobile Equipment Identity (MEID) URN as an Instance ID

This document specifies how the Uniform Resource Name (URN) namespace reserved for the Third Generation Partnership Project 2 (3GPP2) identities and its Namespace Specific String (NSS) for the Mobile Equipment Identity (MEID) can be used as an Instance ID. The purpose of this Instance ID 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.

Официальная английская аннотация

This document specifies how the Uniform Resource Name (URN) namespace reserved for the Third Generation Partnership Project 2 (3GPP2) identities and its Namespace Specific String (NSS) for the Mobile Equipment Identity (MEID) can be used as an Instance ID. The purpose of this Instance ID 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.

Связи документа

Официальный источник · 2018-09-01

Полные импортированные сведения карточки
{
  "id": "RFC8465",
  "number": 8465,
  "title_en": "Using the Mobile Equipment Identity (MEID) URN as an Instance ID",
  "title_ru": "",
  "summary_ru": "",
  "purpose_ru": "",
  "use_ru": "",
  "full_translation_path": "",
  "full_translation_checked_at": "",
  "full_translation_source_sha256": "",
  "architect_note_ru": "",
  "topics_ru": [],
  "translation_state": "not_prepared",
  "verification_level": "not_prepared",
  "verification_level_ru": "Русская выжимка не подготовлена",
  "verification_note_ru": "",
  "abstract_en": "This document specifies how the Uniform Resource Name (URN) namespace reserved for the Third Generation Partnership Project 2 (3GPP2) identities and its Namespace Specific String (NSS) for the Mobile Equipment Identity (MEID) can be used as an Instance ID. The purpose of this Instance ID 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.",
  "authors": [
    "R. Atarius"
  ],
  "organizations": [],
  "publication_date": "2018-09-01",
  "current_status": "INFORMATIONAL",
  "current_status_ru": "Информационный",
  "publication_status": "INFORMATIONAL",
  "publication_status_ru": "Информационный",
  "lifecycle": "informational",
  "lifecycle_ru": "Справочный",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "",
  "area_ru": "",
  "working_group": "NON WORKING GROUP",
  "source_draft": "draft-atarius-dispatch-meid-urn-as-instanceid-08",
  "page_count": 8,
  "doi": "10.17487/RFC8465",
  "keywords": [
    "MEID",
    "instance ID",
    "IMS"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8465/",
    "html": "https://www.rfc-editor.org/rfc/rfc8465.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8465.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8465/"
  }
}