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

rfc-editor@rfc-editor.org Thu, 13 September 2018 16:48 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 20DE9130ECC for <ietf-announce@ietfa.amsl.com>; Thu, 13 Sep 2018 09:48:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id FmbuVLlBufT4 for <ietf-announce@ietfa.amsl.com>; Thu, 13 Sep 2018 09:48:55 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35A59130E9D for <ietf-announce@ietf.org>; Thu, 13 Sep 2018 09:48:55 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 484B7B8184E; Thu, 13 Sep 2018 09:48:52 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg0NjUgb24gVXNpbmcgdGhlIE1vYmlsZSBFcXVpcG1lbnQgSWRlbnRpdHkgKE1FSUQpIFVSTiBhcyBhbiBJbnN0YW5jZSBJRA==?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20180913164852.484B7B8184E@rfc-editor.org>
Date: Thu, 13 Sep 2018 09:48:52 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/y3JJgJ72VZ6qTFTQRi97G7hSSyE>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Sep 2018 16:49:02 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 8465

        Title:      Using the Mobile Equipment Identity 
                    (MEID) URN as an Instance ID 
        Author:     R. Atarius, Ed.
        Status:     Informational
        Stream:     IETF
        Date:       September 2018
        Mailbox:    r_atarius@motorola.com
        Pages:      8
        Characters: 19952
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-atarius-dispatch-meid-urn-as-instanceid-08.txt

        URL:        https://www.rfc-editor.org/info/rfc8465

        DOI:        10.17487/RFC8465

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.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC