ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems

This document specifies the mechanisms and criteria to be applied for the selection and approval of the object identifier resolution system (ORS) operational agency and includes procedures that the operational agency is required to follow. It also addresses any future modification of the procedures and the procedures for any change of the operational agency. This document: — lists the object identifier (OID) nodes for which the operational agency is required to provide ORS support and gives the required level of support for these nodes; — gives the procedures by which lower-level nodes can apply for ORS support (class A, class B, or class C) and the role of the operational agency in providing these levels of support; — determines the basis for charges that can be levied for these levels of support.

This document specifies procedures and managed objects for quality of service (QoS) features specified in IEEE Std 802.1Q, such as Per-Stream Filtering and Policing, queuing, transmission selection, stream control, and frame preemption, in a network system that is not a Bridge.

A physical layer (PHY) and medium access control (MAC) sublayer for short-range optical wireless communications (OWC) in optically transparent media using light wavelengths from 10 000 nm to 190 nm are defined. The standard is capable of delivering data rates sufficient to support audio and video multimedia services and also considers mobility of the optical link, compatibility with various light infrastructures, impairments due to noise and interference from sources like ambient light, and a MAC sublayer that accommodates the unique needs of visible links as well as the other targeted light wavelengths. It also accommodates optical communications for cameras where transmitting devices incorporate light-emitting sources and receivers are digital cameras with a lens and image sensor. The standard adheres to applicable eye safety regulations.

This document provides guidance on how to prepare new and old protocols for cryptographic algorithm migration and defines auxiliary cryptographic algorithms to be used for migration purposes. This document specifies a general wrapper protocol that provides authentication, integrity and confidentiality (encryption) protection for other protocols. This wrapper protocol includes a migration path for cryptographic algorithms allowing for smooth migration to stronger cryptographic algorithms as such requirements evolve. This will allow migration to quantum-safe cryptographic algorithms. Protected protocols can then be developed without taking security and cryptographic algorithms into consideration. This document also includes some protocols to be protected by the wrapper protocol primarily for support of public-key infrastructure (PKI). Other specifications, e.g., Recommendations or International Standards, may also develop protocols designed to be protected by the wrapper protocol.

This Recommendation | International Standard supplements Rec. ITU-T X.509 | ISO/IEC 9594-8 and Rec. ITU-T X.510 | ISO/IEC 9594-11 by providing an extended description of cryptographic algorithms and guidance in establishment and maintenance of a public-key infrastructure (PKI). It is outside the scope of this Recommendation | International Standard to define new cryptographic algorithms, but it is within scope to discuss already-defined cryptographic algorithms that provide optimal protection, including future protection against attacks using powerful quantum computers. This Recommendation | International Standard specifies how public-key infrastructure (PKI) may be adapted to support machine-to-machine (M2M) communication, e.g., smart grid and Internet of things (IoT), to allow interworking. This Recommendation | International Standard specifies the procedures for establishment and maintenance of a PKI supporting new areas, such as intelligent electricity network (smart grid) and industrial Internet of things.

This document defines security key management extensions to address session key generation (both 128-bit and 256-bit key lengths), the creation and/or transport of broadcast/multicast keys, and security algorithm agility. This document maintains backwards compatibility with IEEE Std 802.15.9-2016.

This document specifies test methods for ISO/IEC 21481 in addition to applicable test methods specified in ISO/IEC 10373-6, ISO/IEC 10373-7 and ISO/IEC 23917.

This document specifies Bridges that interconnect individual LANs, each supporting the IEEE 802 MAC Service using a different or identical media access control method, to provide Bridged Networks and VLANs.

ISO/IEC/IEEE 8802-15-4:2018 defines the physical layer (PHY) and medium access control (MAC) sublayer specifications for low-data-rate wireless connectivity with fixed, portable, and moving devices with no battery or very limited battery consumption requirements. In addition, the standard provides modes that allow for precision ranging. PHYs are defined for devices operating various license-free bands in a variety of geographic regions.

This document defines: — communication modes for Near Field Communication Interface and Protocol 1 (NFCIP-1) using inductive coupled devices operating at the centre frequency of 13,56 MHz for interconnection of computer peripherals; — both the active and the passive communication modes of NFCIP-1 to realize a communication network using Near Field Communication (NFC) devices for networked products and for consumer equipment; — a transport protocol including protocol activation and data exchange methods. This document specifies: — modulation schemes; — codings; — bit rates; — frame format of the radio frequency (RF) interface; — initialisation schemes and conditions required for data collision control during initialisation. Information interchange between systems is based on agreement between the interchange parties upon the interchange codes and the data structure.

This document specifies protocol test methods for Near Field Communication Interface and Protocol 1 (NFCIP-1), as defined in ISO/IEC 18092 (the base standard). The radio frequency (RF) test methods for NFCIP-1 (also defined in ISO/IEC 18092) are specified in ISO/IEC 22536.

This document provides the reference model for the Recursive Inter-Network Architecture (RINA). It describes: — the basic concepts of distributed systems and distributed applications; — distributed management systems (DMSs); — the fundamental structure of distributed Inter-Process Communications; — the Distributed Inter-Process Facility (DIF) operations.

This document provides the flow allocator (FA) specification. It includes an overview of the flow allocator, its service definition, and its specification.

This document is a service definition that provides an abstract description of the application programming interface (API) seen by an Application Process using a distributed inter-process communication (IPC) facility (DIF). APIs reflect the specific constraints and conventions of an operating system or programming language. This document does not do that. A service definition specifies the interactions between an Application Process and IPC independent of such specifics. The application process may be an IPC process and the member of a (N+1)-DIF. Actual APIs will be system specific (or may not exist at all), but this sequence of interaction will be maintained. The notation here is used to emphasize that the participants can only act on what they see and must not make assumptions about any events that may have occurred elsewhere. Hence the primitives are described in terms of primitives invoked locally to cause an action, submit, and primitives locally invoked to deliver information on state. This is not a design for an API. It cannot be as a basis for any conformance tests. An actual API may make some, all or none of the parameters noted here visible to the user and may add additional primitives of local significance. The purpose of this service definition is to specify information that must or may be available by whatever means, explicit or implicit, to drive the operation of the DIF.

This document provides the Error and Flow Control Protocol (EFCP) specification. EFCP provides an inter-process communication (IPC) service to an application process, which can be a (N+1)-IPC process (IPCP), with the requested Quality of Service (QoS). One or more service data units (SDUs) are passed on the (N)-port-id to the (N)-DIF (distributed IPC facility) to be sent to the destination application process. Protocol data units (PDUs) transferred by the (N)-DIF are delivered to the (N)-port-id for the using Application Process. This document describes the placement of EFCP within RINA, the components EFCP consists of, and the mechanisms and policies that are involved in EFCP’s work, and the timers and control mechanisms required to manage the connection. EFCP comprises two logical components, the data transfer procedures (DTP), providing tightly bound mechanisms and the data transfer control procedures (DTCP), which provides loosely bound mechanisms. This document provides: — the service definition; — an overview of EFCP; — a description of the placement of EFCP within recursive internetwork architecture (RINA); — the common elements of data transfer protocol (DTP) and data transfer control protocol (DTCP); — DTP structure and functions; — DTCP structure and functions; — an informative list of all policies in EFCP.en

This document defines the procedure executed by a Member of a distributed inter-process communication (IPC) facility (DIF) or distributed application facility (DAF) to initialize a New Member as a fully functioning Member. This procedure is used when it is likely the new Member has not previously been a Member of the DIF or DAF in the near past. This document is defined for use with DIFs, but can be used equally well by a DAF that wants to assign synonyms with a scope limited to the DAF.

This document provides a delimiting module that defines a mechanism for encoding Service Data Units (SDUs), the amount of data passed across the layer boundary within Protocol Data Units (PDUs), the amount of data sent to its peer. It is not necessary to use this document if each PDU carries precisely one SDU.

This document defines the procedure executed by a Member of a distributed inter-process communication (IPC) facility (DIF) or distributed application facility (DAF) to initialize a new Member as a fully functioning Member. This document defines the procedure for a new Member to enrol when the new Member was recently a Member of the DIF or DAF. This document is defined for use with DIFs, but it can be used equally well by a DAF that wants to assign synonyms with a scope limited to the DAF.

This document provides the common distributed application protocol (CDAP) specification. CDAP enables distributed applications to deal with communications at an object level, rather than forcing applications to explicitly deal with serialization and input/output operations. CDAP provides the application protocol component of a distributed application facility (DAF). CDAP provides a straightforward and unifying approach to sharing data over a network without having to create specialized protocols. This document provides: — an overview of CDAP; — the specification of CDAP; — a description of policies, in the specific sense introduced in the text; — notes on the context of CDAP.

This document provides the common application connection establishment procedure (CACEP) specification. It includes an overview of CACEP, its specification, the syntax of the protocol data units (PDUs), and the policies available.

This document defines the function, interfaces (IFs), and operating mechanism of CADP and defines the AP association, cloud AC switchover, cloud AC backup and CADP hot backup methods. This document applies to public wireless local area network (WLAN) networking scenarios.

This document specifies a cloud AC based wireless local area network (WLAN) networking architecture, defines the cloud access controller dispatch platform (CADP) operating mechanism and the interaction between the network elements such as CADPs, access points (APs), cloud access controllers (ACs) and the WLAN network management system (NMS), and specifies the main functional requirements of each network element. This document applies to public WLAN networking scenarios.

Profiles that select features, options, configurations, defaults, protocols and procedures of bridges, stations and LANs that are necessary to build networks that are capable of transporting time-sensitive audio and/or video data streams are defined in this standard.

This document describes a communication model and requirements for unmanned aircraft area network (UAAN), which is a wireless distributed communication network for units related with UA services in level II. It describes: — the communication structure and operation; — the purpose of the three types of communication and related services; — the interoperation of the three types of communication; — the interworking with upper layers.

This document specifies communication protocols for the physical and data link layer of video communication, which is a wireless distributed communication network for units related with unmanned aircrafts (UAs) in level II. This document describes video communication, which is one-to-one communication that transmits video from a UA to a video receiver. For the specific use of video communication, video can be transmitted from a UA to multiple receivers.

This document specifies communication protocols for the physical and data link layer for control communication, which is wireless distributed communication network for units related with unmanned aircrafts (UAs) in level II. This document describes control communication, which is one-to-one communication between a UA and a controller.

This document describes communication protocols for the physical and data link layer of shared communication, which is a wireless distributed communication network for units related with UAs in level II. Physical layer includes frame structure, encoding procedure, physical layer procedure and coexistence operations. Data link layer includes channel and slot, resource management, broadcast and exchange of data, synchronization, security, and interface with upper layer and other communication layers.

This document specifies the OID resolution system, including the overall architecture and a DNS-based resolution mechanism. It specifies the means for inserting any application-defined information associated with an OID node into the DNS (see clause 6) and the means of retrieval of that information using the ORS (see clause 7). It does not restrict the number of applications it can support. It specifies the required operation of an ORS client (see clause 7), including the mapping of an OID-IRI value by the ORS client into a DNS name to produce a DNS query for the specified application information and the processing of any returned information. The ORS has no role in the allocation or registration of OID nodes. The required behaviour of an ORS client is specified, but the interfaces to it are specified only in terms of the semantics of the interaction. A bit-level application program interface is platform and software dependent, and is not in the scope of this document. A special behaviour of an ORS client is specified to cache OID information in order to reduce the response time of OID resolution. This document also specifies a mechanism to resolve an OID node when one of its superior OID nodes is not ORS-supported. It does not include a tutorial or complete specification on the management of DNS zone files (for that, see IETF RFC 1035 and IETF RFC 3403); it specifies (only) the DNS resource records (see 6.3) that need to be inserted in the zone files in order to support ORS access to the information associated with an OID node. This document specifies required DNS zone file resource records, and prohibits the use of other resource records of a similar form but with different semantics (in DNS zone files in the ORS domain) – see 6.2. It does not otherwise restrict the general use of DNS zone files.