datatracker.ietf.org
Sign in
Version 5.12.0.p1, 2015-03-01
Report a bug

A URN Namespace for ucode
RFC 6588

Document type: RFC - Informational (April 2012; Errata)
Was draft-ishikawa-yrpunl-ucode-urn (individual in app area)
Document stream: IETF
Last updated: 2013-02-12
Other versions: plain text, pdf, html

IETF State: (None)
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC 6588 (Informational)
Responsible AD: Barry Leiba
Send notices to: chiaki.ishikawa@ubin.jp, draft-ishikawa-yrpunl-ucode-urn@ietf.org, stpeter@stpeter.im

Internet Engineering Task Force (IETF)                       C. Ishikawa
Request for Comments: 6588                 YRP Ubiquitous Networking Lab
Category: Informational                                       April 2012
ISSN: 2070-1721

                       A URN Namespace for ucode

Abstract

   This document describes a Uniform Resource Name (URN) namespace for
   ucode, an identifier system for objects and places.  ucode technology
   is used in many applications, and this document provides a URN
   namespace for ucode to enable its use in Internet-related devices and
   software.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6588.

Copyright Notice

   Copyright (c) 2012 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) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Ishikawa                      Informational                     [Page 1]
RFC 6588                 URN Namespace for ucode              April 2012

1.  Introduction

   ucode [UCODE] is an identifier to be stored in many types of tags
   (not limited to Radio Frequency Identification (RFID) tags).  Its
   allocation and management is handled by the Ubiquitous ID Center
   [UIDC].  The embedding of ucode in many types of tags (RFID tags,
   optical code, infrared markers, and even sound source) is also
   specified by the Ubiquitous ID Center.

   The basic length of ucode is 128 bits, but it is extensible in units
   of 128 bits if necessary.

   ucode has been devised to identify objects and places where existing
   standards do not fit the application needs or the scope of the
   applications or where the allocation policy of existing standards is
   too limited for Small and Medium Enterprises (SMEs), small-scale
   research laboratories at academic institutions, or individual users.

   Applications that use ucode take advantage of the Internet
   extensively.  Use of ucode is open to anybody.  Those who wish to
   have ucode allocated can do so either by having ucode subspace
   allocated to them directly from the Ubiquitous ID Center [UIDC] or by
   obtaining tags that have pre-stored ucode from so called "providers"
   [UCDMIP].  Such tags are certified as ucode tags [UIDTAG], and the
   reader specifications are published so that there will be many
   readers available for such tags.

   By having a URN for ucode, we can facilitate the use of ucode in many
   Internet-related devices and software for the benefit of existing and
   future users of ucode and people who will access such tags attached
   to objects and places.  Since an application based on ucode can run
   across organizational boundaries and spread across regions and
   countries, a formal URN Namespace Identifier (NID) assignment for
   'ucode' is requested.

2.  'ucode' Registration Template

   Namespace ID:

   'ucode' requested

   Registration Information:

   Registration Version Number: 1
   Registration Date: 2011-12-21

Ishikawa                      Informational                     [Page 2]
RFC 6588                 URN Namespace for ucode              April 2012

   Declared registrant of the namespace:

   T-Engine Forum
   2-20-1, Nishi-Gotanda
   Shinagawa, Tokyo, 141-0031
   Japan
   office@t-engine.org
   Tel: +81-3-5437-0572

   Declaration of syntactic structure:

   The structure of the namespace for 'ucode' using the hexadecimal
   representation of the identifier is as follows using ABNF [RFC5234].

   UCODE-URN = "urn:ucode:" ucode-name
   ucode-name = "_" ucode-number
   ucode-number = 1*ucode-value

[include full document text]