RFC 8464 on A URN Namespace for Device Identity and Mobile Equipment Identity (MEID)

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 15394130DCB for <ietf-announce@ietfa.amsl.com>; Thu, 13 Sep 2018 09:48:40 -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 vKGyKiQRyFra for <ietf-announce@ietfa.amsl.com>; Thu, 13 Sep 2018 09:48:38 -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 2C0CF130934 for <ietf-announce@ietf.org>; Thu, 13 Sep 2018 09:48:38 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3B8C7B81843; Thu, 13 Sep 2018 09:48:35 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg0NjQgb24gQSBVUk4gTmFtZXNwYWNlIGZvciBEZXZpY2UgSWRlbnRpdHkgYW5kIE1vYmlsZSBFcXVpcG1lbnQgSWRlbnRpdHkgKE1FSUQp?=
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: <20180913164835.3B8C7B81843@rfc-editor.org>
Date: Thu, 13 Sep 2018 09:48:35 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/MwoL9dIDdrGhb_5jBwIC6yauXcM>
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:48:40 -0000

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

        RFC 8464

        Title:      A URN Namespace for Device 
                    Identity and Mobile Equipment Identity (MEID) 
        Author:     R. Atarius
        Status:     Informational
        Stream:     IETF
        Date:       September 2018
        Mailbox:    ratarius@motorola.com
        Pages:      10
        Characters: 21958
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-atarius-dispatch-meid-urn-18.txt

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

        DOI:        10.17487/RFC8464

This document defines a Uniform Resource Name (URN) namespace for the
Third Generation Partnership Project 2 (3GPP2) and a Namespace
Specific String (NSS) for the Mobile Equipment Identity (MEID).  The
structure of an MEID is 15 hexadecimal digits long and is defined in
the 3GPP2 to uniquely identify each individual mobile equipment
(e.g., a handset or mobile phone).  The 3GPP2 has a requirement to be
able to use an MEID as a URN.  This document fulfills that

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