ISO/IEC 4396-6:2023 PDF
Telecommunications and information exchange between systems — Recursive inter-network architecture — Part 6: RINA data transfer service
Telecommunications and information exchange between systems — Recursive inter-network architecture — Part 6: RINA data transfer service
- Статус документа:
- Действующий
- Формат:
- Электронный (PDF)
- Количество страниц:
- 14
- Дата публикации:
- 5 декабря 2023 г.
- Издание:
- ISO/IEC IS 4396 edition 1 version 1
- ICS:
- 35.100.30
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.
Abstract
Overview
ISO/IEC 4396-6:2023 - RINA data transfer service - defines an abstract, implementation‑independent service description for data transfer between Application Processes using a distributed inter‑process communication facility (DIF) in the Recursive Inter‑Network Architecture (RINA). The standard specifies the sequence of interaction primitives (locally invoked submit and deliver primitives) that an Application Process observes when allocating flows, transferring SDUs, modifying QoS, querying status and deallocating resources. It is explicitly a service definition, not a concrete API design and not intended for conformance testing.
Key topics and technical requirements
- Abstract API primitives: Defines Allocate_Request, Allocate_Response, Transfer.submit/deliver, Deallocate.submit/deliver, Modify_Request/Response, Status primitives - all modeled as local submit (cause an action) and deliver (inform of state).
- Flow management: Introduces the Flow Allocator and Flow Allocator Instance (FAI / port-id) concept to manage the lifecycle of IPC flows (allocation, transfer, deallocation).
- Quality of Service (QoS): Supports symmetric and asymmetric flows and a detailed QoS‑List (average SDU rate, peak rates, burst parameters, delay, jitter, error rate, ordering, partial delivery, cost metrics, max SDU gap).
- Access control: Parameters for access control (e.g., capabilities) are included in allocation primitives.
- Local semantics emphasis: Primitives are defined to ensure participants act only on locally observable events - no assumptions about remote state.
- Design constraints: The document states APIs are system‑specific; actual APIs may expose different parameter sets or additional local primitives. It is not an implementation or conformance test specification.
Applications and who uses it
- Network architects and protocol designers implementing RINA-based networks or researching RINA concepts.
- Middleware and operating‑system developers designing or mapping distributed IPC APIs to platform‑specific interfaces.
- Developers of flow and QoS management modules (Flow Allocator implementations) and policy designers for DIFs.
- Academic and industry researchers studying recursive networking, flow allocation, and application‑level QoS control.
Practical uses include designing the interaction model between applications and IPC layers, specifying required information for flow control and QoS negotiation, and informing implementations that must preserve the defined sequence of primitives when mapping to system APIs.
Related standards
- ISO/IEC 4396-1 - RINA Reference Model
- ISO/IEC 4396-8 - Flow Allocator (referenced)
- ISO/IEC 4396-9 - Error and Flow Control Protocol (referenced)
Keywords: ISO/IEC 4396-6, RINA data transfer service, distributed IPC, DIF, Flow Allocator, QoS, Allocate_Request, Transfer.submit, port-id.
Технические детали
- Технический комитет
- ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
- SKU
- ISO/IEC 4396-6:2023
Похожие стандарты
Стандарты, упомянутые в описании
ISO/IEC 4396-1:2023
ДействующийTelecommunications and information exchange between systems — Recursive inter-network architecture — Part 1:…
Overview ISO/IEC 4396-1:2023 - "Telecommunications and information exchange between systems - Recursive inter-network architecture - Part 1: Reference model" is the authoritative, high‑level referenc…
ISO/IEC 4396-8:2023
ДействующийTelecommunications and information exchange between systems — Recursive inter-network architecture — Part 8:…
Overview ISO/IEC 4396-8:2023 is an international standard under the Recursive Inter-Network Architecture (RINA) series that specifies general delimiting procedures for telecommunications and informat…
ISO/IEC 4396-9:2023
ДействующийTelecommunications and information exchange between systems — Recursive inter-network architecture — Part 9:…
Overview ISO/IEC 4396-9:2023 specifies the Error and Flow Control Protocol (EFCP) for the Recursive Inter-Network Architecture (RINA). EFCP is designed to provide robust inter-process communication (…