Reference record for OID 2.27

parent
2 (joint-iso-itu-t, joint-iso-ccitt)
node code
27
node name
tag-based
dot oid
2.27
asn1 oid
  • {joint-iso-itu-t(2) tag-based(27)}
  • {joint-iso-ccitt(2) tag-based(27)}
  • iri oid
  • /joint-iso-itu-t/tag-based
  • /joint-iso-ccitt/tag-based
  • iri by oid_info
    /Joint-ISO-ITU-T/Tag-Based
    creation date
    April 11, 2008

    Description by oid_info

    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-info.com

    Information by oid_info

    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

    Children (2)

    OIDNameSub childrenSub Nodes TotalDescription
    2.27.1 mcode 0 0 mCode, micro-mCode and mini-mCode for mobile RFID services
    2.27.2 ucode 0 0 None

    Brothers (37)

    OIDNameSub childrenSub Nodes TotalDescription
    2.0 presentation 0 0 Presentation layer service and protocol
    2.1 asn1 9 65 ASN.1 standards:
    - Rec. ITU-T X.680 | ISO/IEC 8824 series: Information
    Technology - Abstract Syntax Notation One (ASN.1)
    ;
    - R...
    2.2 association-control 4 16 Association Control Service Element (ACSE), Rec. ITU-T X.227 | ISO/IEC 8650-1
    2.3 reliable-transfer 3 3 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-operations 13 28 Remote operations service element (ROSE)
    2.5 ds 38 1165 Directory Services
    2.6 mhs 11 700 Message Handling System (MHS), also known as Message Oriented Text Interchange System (MOTIS) in ISO
    2.7 ccr 2 9 Commitment, Concurrency and Recovery (CCR) service and protocol
    2.8 oda 5 110 Open Document Architecture (ODA)
    2.9 ms 5 1714 OSI network management, and particularly CMIP (Common Management Information Protocol) and GDMO (Guidelines for the Definitio...
    2.10 transaction-processing 3 10 Transaction processing
    2.11 dor 3 4 ISO 10031-2 (withdrawn standard): Information technology -- Text and office systems -- Distributed-office-applications model ...
    2.12 reference-data-transfer 5 19 Reference data transfer
    2.13 network-layer 1 499 Network layer management
    2.14 transport-layer 1 113 Transport layer management
    2.15 datalink-layer 1 97 OSI data link layer management
    2.16 country 202 18410 Joint (ITU-T and ISO/IEC) registration within a country
    2.17 registration-procedures 5 125 ISO/IEC and/or ITU-T activities on registration procedures
    2.18 physical-layer 1 41 Physical layer management
    2.19 mheg 1 10 Multimedia and Hypermedia information coding Expert Group (MHEG)
    2.20 genericULS 6 33 Generic upper layers security (GULS)
    2.21 transport-layer-security-protocol 1 2 Transport layer security protocol
    2.22 network-layer-security-protocol 1 2 Network layer security protocol
    2.23 international-organizations 18 342 International organizations
    2.24 sios 1 5 Security Information Objects (SIOS) for access control
    2.25 uuid 197 245 UUIDs (Universally Unique Identifiers) generated in accordance with Recommendation ITU-T X.667 | ISO/IEC 9834-8
    2.26 odp 1 4 Rec. ITU-T X.900 series | ISO/IEC 10746 & 13235 series: Information technology -- Open Distributed Processing (ODP)
    2.28 its 1 38 Intelligent Transport Systems (ITS)
    2.40 upu 3 12 Universal Postal Union (UPU)
    2.41 bip 1 7 Rec. ITU-T X.1083 | ISO/IEC 24708 "BioAPI Interworking Protocol (BIP)"
    2.42 telebiometrics 4 213 Telebiometrics including telehealth and associated physiological quantities and units
    2.48 cybersecurity 2 2 Cybersecurity information exchange
    2.49 alerting 1 1728 Alerts and alerting agencies according to Recommendation ITU-T X.674
    2.50 ors 1 5 Rec. ITU-T X.672 | ISO/IEC 29168-1 "Information technology -- Open Systems Interconnection -- Object Identifier Resolution Sy...
    2.51 gs1 4 14 GS1
    2.999 example 0 0 Example
    2.16840 16840 1 5 This node IS NOT DESCRIBED YET