Reference record for OID 2.27

Parent
2 (joint-iso-itu-t, joint-iso-ccitt)
Node code
27
Node name
tag-based
Numeric OID
2.27
URN notation
urn:oid:2.27
ASN.1 notation

{2 27}

  • {joint-iso-itu-t(2) tag-based(27)}
  • {joint-iso-ccitt(2) tag-based(27)}
OID-IRI notation
  • /2/27
  • /Joint-ISO-ITU-T/Tag-Based
  • /Joint-ISO-ITU-T/27
Named path variants
  • /joint-iso-itu-t/tag-based
  • /joint-iso-ccitt/tag-based
Creation date
April 11, 2008

Descriptions

Descriptions may differ between sources. The primary description is shown first.

Primary description: OID Repository

Tag-based identifications (identification mechanisms for which identifiers are stored in a memory-limited area of a tag like an RFID, 1D or 2D barcode, etc.)
View at oid-base.com
Identification schemes can be registered at Korean Internet & Security Agency (KISA) dedicated web page. Note: KISA performs the administrative role of the Registration Authority while the technical role is performed by the ITU-T Rapporteur and ISO/IEC Convenor in charge of the maintenance of that standard. The technical and administrative roles are defined in Rec. ITU-T X.660 | ISO/IEC 9834-1.

Child OIDs are limited to 127 so that the OID can encode in 2 octets.

The procedures for the Registration Authority (RA) and the criteria for acceptance of a identification scheme are specified in Rec. ITU-T X.668 | ISO/IEC 9834-9 "Procedures for the operation of OSI Registration Authorities: Registration of object identifier arcs for applications and services using tag-based identification."

Clause 7 defines the criteria of acceptance for the registration of an identification scheme:
-----
7.1 An application shall be accepted if, in the technical judgment of the [ITU-T Rapporteur and ISO/IEC Convenor in charge of the maintenance of Rec. ITU-T X.668 | ISO/IEC 9834-9], the allocation requested is to be used for an identification scheme supporting one or more ID-based applications or services.
7.2 It is a requirement that the identification scheme be identified in a publicly available specification produced by a standardization body recognized by ITU-T, ISO or IEC, or by an internationally recognized consortium.
Note: This excludes specifications produced by a single company or organization.
7.3 The applications shall identify the timescale within which the relevant identification scheme is to be applied within applications or services. The application shall be rejected if the timescale exceeds 12 months, and can be voided if it is not in use within that time-scale.
7.4 The applications or services for which the allocation is requested shall be applications or services which require interchange between multiple vendors in an open environment.
7.5 An application for registration, containing the information [specified below] shall be sent to the organization providing the administrative role for the RA. The application shall be submitted by the standardization body (recognized by ITU-T, ISO or IEC), or by the internationally recognized consortium (see 7.2).
-----

The application shall include at least the following information:
a) name of organization submitting the application;
b) name, postal mail address, e-mail address, and optionally telephone and fax numbers for the contact point within the requesting organization;
c) full identification of the person submitting the application (including their role in the organization);
d) a hreference to an openly accessible specification (see 7.2) of the identification scheme for the ID-based application or service for which an arc is being requested; and
e) (optionally) desired secondary identifier(s) [i.e., an alphanumeric word beginning with a lowercase letter].

It is not expected that subsequent (grand-child) arcs will be created under the OIDs assigned under this arc, as this would be evidence that there is no requirement for the short OID that is provided by Rec. ITU-T X.668 | ISO/IEC 9834-9.

This OID arc was created by a Resolution of ISO/IEC JTC 1/SC 6 and of ITU-T SG 17 at their joint April 2008 meeting. The nomination of KISA (previously known as NIDA) as the Registration Authority is contained in document ISO/IEC JTC 1/SC 6 N14004 which was approved as ISO/IEC JTC 1 Resolution 51. It was further approved by ISO Technical Management Board (TMB) Resolution 80/2010 and IEC Standardization Management Board (SMB) Decision 137/18.

Note: The term "NID" was originally used as an abbreviation for "Network aspects of identification systems (including RFID)" but is now more generally used for identification-based applications and services.

First Registration Authority

National Internet Development Agency of Korea (NIDA)

Address: 3F, 398, Seochoro
Seocho-gu
Seoul, 137-857
Republic of Korea

Phone: +82 2 2186 4668

Current Registration Authority

Dong Oun Kim

Address: Korean Internet & Security Agency (KISA)
12F Daedong Building
79-3 Garak-dong
Songpa-gu
Seoul, 138-950
Republic of Korea

Direct children (2)

OIDNameDirect childrenDescendantsDescription
2.27.1 mcode00 mCode, micro-mCode and mini-mCode for mobile RFID services
2.27.2 ucode00

Siblings (38)

OIDNameDirect childrenDescendantsDescription
2.0 presentation00 Presentation layer service and protocol
2.1 asn11179 ASN.1 standards:
- Rec. ITU-T X.680 | ISO/IEC 8824 series: Information
Technology - Abstract Syntax Notation One (ASN.1)
;
- Rec…
2.2 association-control416 Association Control Service Element (ACSE), Rec. ITU-T X.227 | ISO/IEC 8650-1
2.3 reliable-transfer33 Reliable transfer service element (Rec. ITU-T X.218 | ISO/IEC 9066-1 and Rec. ITU-T X.228 | ISO/IEC 9066-2)
2.4 remote-operations1328 Remote operations service element (ROSE)
2.5 ds421576 Directory Services
2.6 mhs111505 Message Handling System (MHS), also known as Message Oriented Text Interchange System (MOTIS) in ISO
2.7 ccr, joint-CCR29 Commitment, Concurrency and Recovery (CCR) service and protocol
2.8 oda5110 Open Document Architecture (ODA)
2.9 ms61950 OSI network management, and particularly CMIP (Common Management Information Protocol) and GDMO (Guidelines for the Definition …
2.10 transaction-processing310 Transaction processing
2.11 dor, dorx34 ISO 10031-2 (withdrawn standard): Information technology -- Text and office systems -- Distributed-office-applications model --…
2.12 reference-data-transfer519 Reference data transfer
2.13 network-layer1537 Network layer management
2.14 transport-layer1116 Transport layer management
2.15 datalink-layer198 OSI data link layer management
2.16 country20533195 Joint (ITU-T and ISO/IEC) registration within a country
2.17 registration-procedures5125 ISO/IEC and/or ITU-T activities on registration procedures
2.18 physical-layer141 Physical layer management
2.19 mheg110 Multimedia and Hypermedia information coding Expert Group (MHEG)
2.20 genericULS633 Generic upper layers security (GULS)
2.21 transport-layer-security-protocol12 Transport layer security protocol
2.22 network-layer-security-protocol12 Network layer security protocol
2.23 international-organizations19494 International organizations
2.24 sios15 Security Information Objects (SIOS) for access control
2.25 uuid197245 UUIDs (Universally Unique Identifiers) generated in accordance with Recommendation ITU-T X.667 | ISO/IEC 9834-8
2.26 odp14 Rec. ITU-T X.900 series | ISO/IEC 10746 & 13235 series: Information technology -- Open Distributed Processing (ODP)
2.28 its138 Intelligent Transport Systems (ITS)
2.40 upu312 Universal Postal Union (UPU)
2.41 bip17 Rec. ITU-T X.1083 | ISO/IEC 24708 "BioAPI Interworking Protocol (BIP)"
2.42 telebiometrics, id-telebio54439 Telebiometrics including telehealth and associated physiological quantities and units
2.48 cybersecurity22 Cybersecurity information exchange
2.49 alerting11728 Alerts and alerting agencies according to Recommendation ITU-T X.674
2.50 ors15 Rec. ITU-T X.672 | ISO/IEC 29168-1 "Information technology -- Open Systems Interconnection -- Object Identifier Resolution Syst…
2.51 gs1414 GS1
2.100 id-trader469
2.999 example00 Example
2.16840 1684015 This node IS NOT DESCRIBED YET