ISO/IEC JTC 1/SC 6/WG 7 - Network, transport and future network

The concept of this document considers the FNQoS related to the FNProxy based in ISO/IEC TR 29181-8. The protocol mechanism given in this document supports both the interaction between two FNProxies of a basic FNQoS system (BFS) and the interaction among multiple FNProxies in a synthetic FNQoS system (SFS).

This document describes the architectural aspects of Future Network (FN) Quality of Service (QoS) based on an FNProxy model, taking into account the requirements described on ISO/IEC TR 29181-8. It describes: — the concept of future network QoS (FNQoS), — the architectural model of FNQoS system, — the usage of FNQoS system.

This document focuses on networking issues for integrating various networking technologies for integrating various networking techniques to provide the thing-user centric communication service. This document specifies: — the architectural model of the Future Network – Networking of Everything (FN-NoE); — the functional procedure for providing advanced FN-NoE services that integrate various networks.

This document specifies: — functional procedures to provide thing-user social networking and proximity defined networking; — service access interfaces and protocols to support the FN-NoE functional procedure.

This document specifies protocols and mechanisms for use within systems conforming to the future network (FN) architecture specified in ISO/IEC 21558-1.

This document specifies the switching and routing architecture of the Future Network (FN).

ISO/IEC TR 29189-9:2017 describes the general characteristics of Networking of Everything (NoE), which can be applied to Future Networks, especially from an Internet of Things (IoT) perspective. This document specifies: - a conceptual model of NoE and its definition; - problem statements in conventional networking; - standardization activities of other standards-development organizations; - requirements for NoE from an IoT perspective; - technical aspects. NOTE: Since networking issues are an integral part of IoT and Future Networks, while standards of IoT or Future Networks are under development in other standards-development organizations, this document focuses on networking issues to integrate diverse networking techniques to provide users' service and/or things requirement.

ISO/IEC TR 29181-8:2017 describes the problem statements of current networks and the requirements for Future Network (FN) in the Quality of Service (QoS) perspective. This document mainly specifies: - problems of the current networks for QoS; - requirements for QoS support in Future Network.

ISO/IEC TR 29181-2:2014 describes the general characteristics of Future Network naming and addressing schemes, including problem statements, requirements, design objectives, gap analysis, and development directions. Problem Statements: The characteristics and problems of existing NAS in existing network will be discussed. Technical Challenges: A list of major technical challenges to assure that the FN-NAS will be able to provide solid Requirements: The general characteristics of Future Network are discussed and their impact on NAS design. Gap analysis: Examines the gap between existing network NAS and future network performance expectations. FN-NAS Standardization Plan, design objectives, gap analysis, development guidance, chronological scenarios for future network naming, and addressing guidance are described in detail. Though ISO/IEC TR 29181-2:2014 mainly presents a list of up-to-date surveyed problems, requirements, and plausible techniques for Future Network, it does not mean that all of those would be applied to a single Future Network in common, since the naming and addressing scheme can be applied to the various networks, such as global networks, local networks, access networks, mobile networks, etc. If a specific Future Network is designed and implemented, some appropriate parts of ISO/IEC TR 29181 would be considered depending on its network usage and its characteristics.

ISO/IEC TR 29181-5:2014 describes the problem statements of current network and the requirements for Future Network in the security perspective. It mainly specifies problems of the current network in security environment, and requirements for security support in Future Network.

ISO/IEC TR 29181-4:2013 describes the problem statements of current network and the requirements for Future Network in the mobility perspective. It mainly specifies problems of the current network in mobile environment, and requirements for mobility support in Future Network. In addition, ISO/IEC TR 29181-4:2013 gives information on existing mobility control schemes in the current network, examples of high-level mobility control architecture for Future Network, distributed mobility control in the Proxy Mobile IPv6 networks, and additional considerations for Future Network mobility.

The recent advancement of wireless-based communication technology and electronics has facilitated the implementation of a low-cost, low-power sensor network. Basically, a ubiquitous sensor network (USN) consists of three parts: a sensor network consisting of a large number of sensor nodes, a base station (also known as a gateway) interfacing between the sensor network and an application server, and the application server controlling the sensor node in the sensor network or collecting the sensed information from the sensor nodes in the sensor network. ISO/IEC 29180:2012 describes the security threats to and security requirements of the USN. In addition, it categorizes the security technologies according to the security functions that satisfy the said security requirements and where the security technologies are applied in the security model of the USN. Finally, the security functional requirements and security technologies for the USN are presented.

ISO/IEC TR 20002:2012: a) classifies problems of P2P networking; b) defines taxonomy and concept of managed P2P; c) specifies requirements to support managed P2P; d) specifies framework for managed P2P; e) specifies information flows to support various features of managed P2P. ISO/IEC TR 20002:2012 does not define new P2P protocol or P2P-based applications. ISO/IEC TR 20002:2012 does not define manageability features for interoperation with conventional P2P-based applications. The goal of ISO/IEC TR 20002:2012 is to define a framework to provide manageability to the conventional P2P-based application.

ISO/IEC TR 29181-1:2012 describes the definition, general concept, problems and requirements for Future Network (FN). It also discusses a milestone for standardization on FN. The scope of ISO/IEC TR 29181-1:2012 includes: motivation of FN; definition, general concept, and terminologies of FN; services and applications in FN; problems with current networks; design goals and high-level requirements for FN; milestones for standardization on FN.

ISO/IEC 24793 specifies mobile multicast communications (MMC), which can be used to support a variety of multimedia multicasting services in IP-based wireless mobile networks as well as wired fixed networks. MMC targets real-time, one-to-many multicast services and applications over mobile communications networks. This implies that MMC focuses on multicast services rather than broadcast services, and that only authenticated users could be allowed in the multicast session. MMC also considers the one-to-many multicast session wherein a single multicast sender is allowed in the session rather than many-to-many multicast services. In addition, MMC is targeted in the real-time multicast session rather than the reliable multicast session; the timely delivery of multicast data is considered a key factor. ISO/IEC 24793-1:2010 specifies the MMC framework as part of the MMC standard describing the framework and functional architecture of MMC. Based on this framework, the two protocols for MMC will be developed in two parts of the MMC project: protocol over native IP multicast networks and protocol over overlay multicast networks.

ISO/IEC 24793-2:2010 specifies mobile multicast control protocol (MMCP) over native IP multicast networks for mobile multicast communications. The MMCP can be used to support a variety of multimedia multicasting services in the IP-based wireless mobile networks. The MMC is targeted at the real-time one-to-many multicast services and applications over mobile communications networks. ISO/IEC 24793-2:2010 specifies the procedures and packet formats of the MMCP protocol.

ISO/IEC 14476-6:2010 provides a specification of QoS management for accomplishing a desired quality of service in n-plex multicast transport connections. For this purpose, it describes the QoS management operations in n-plex multicast transport connections such as QoS negotiation, QoS monitoring and QoS maintenance. ISO/IEC 14476-6:2010 is an integral part of ECTP-5 (ITU-T Rec. X.608 | ISO/IEC 14476-5). All of the protocol components, including packet formats and protocol procedures specified in ITU-T Rec. X.608 | ISO/IEC 14476-5, are also valid in ISO/IEC 14476-6:2010.

ISO/IEC 14476-4:2010 provides a specification of QoS management for accomplishing desirable QoS for a duplex multicast transport connection. For this purpose, it describes the QoS management operations in duplex multicast transport connection such as QoS negotiation, QoS monitoring and QoS maintenance. ISO/IEC 14476-4:2010 is an integral part of ECTP-3 (ITU-T Rec. X.607 | ISO/IEC 14476-3). All of the protocol components, including packet formats and protocol procedures specified in ITU-T Rec. X.607 | ISO/IEC 14476-3 are also valid in ISO/IEC 14476-4:2010.

ISO/IEC 14476-5:2008 defines a protocol for N-plex multicast transport over the Internet where IP multicast is supported. It provides the mechanisms of session control and error control. For session control, one participant is designated to manage creation/termination of a connection; join/leave of a participant; and tokens which allow the specific participants to send data. For error control, it provides the mechanisms of tree-based loss recovery; control tree construction with two-layer logical tree; and logical tree adaptation with packet delivery status. ISO/IEC 14476-5:2008 specifies the protocol details such as packet format, procedures, and parameter values. This protocol can be used for the applications which require many-to-many reliable data delivery service.

ISO/IEC 14476-3:2008 defines a protocol for duplex multicast transport over the Internet where IP multicast is supported. A control tree mechanism for scalability and an error control mechanism for reliable multicast data delivery are specified. Protocol details such as packet format, parameter values and procedures are specified. This protocol can be used for applications that require one-to-many as well as many-to-one data delivery services.

ISO/IEC 9834-6:2005 specifies the procedures applicable to the registration of application processes and application entities. No requirement for an international registration authority has been identified; therefore these procedures apply to registration at any point in the ASN.1 object identifier tree. ISO/IEC 9834-6:2005 does not cover the registration of application-process types or application-entity types. No requirement for such registration has been identified.

ISO/IEC 16513:2005 provides a specification of a Group Management Protocol (GMP), which is an application-layer control protocol for creating a group session and for managing the group's participating members. The GMP consists of session management (SM), membership management (MM), and the function of exchanging information between SM and MM. SM is responsible for session creation and deletion. MM manages the member lists based on session information retrieved from SM.

ISO/IEC 14476-2:2003 is an integral part of ITU-T Recommendation X.ectp | ISO/IEC 14476 having the main title of Enhanced communications transport protocol, which is a family of protocol specifications designed to support multicast transport services. ISO/IEC 14476-1 provides a specification of various protocol operations for simplex multicast transport. Those protocol operations include connection management such as connection creation/termination and connection pause/resume, membership management such as late join, user leave and membership tracking, and error control for multicast data transport such as error detection and recovery. ISO/IEC 14476-2:2003 provides a specification of QoS management for accomplishing desirable quality of service in simplex multicast transport connection. ISO/IEC 14476-2:2003 describes the following QoS management operations: a) QoS negotiation For QoS negotiation, this specification assumes that a desired QoS level for multicast application service can be expressed in terms of a set of QoS parameters. QoS negotiation is performed via exchange of control packets between sender and receivers. Sender proposes the target values of QoS parameters obtained from the application's requirements, and then each receiver can propose modified values based on its system and/or network capacity. Sender arbitrates the modified values proposed by receivers. Target values for QoS parameters can be used as input parameters for reservation of network resources. b) QoS monitoring QoS control in ECTP is based on feedback of control packets from receivers. The feedback messages from receivers enable the sender to keep track of the number of active receivers and also to monitor the connection status for multicast data transport. QoS monitoring is designed to allow the sender to diagnose the connection status in terms of QoS parameter values, and thus to take the necessary actions for maintaining the connection status at a desired QoS level. The monitored connection status will be reported to the application at the sender side. The information conveyed could provide statistics useful for billing purposes, for example. c) QoS maintenance Based on feedback information from receivers, the sender takes one or more actions so as to maintain the connection status at a desired QoS level. These QoS maintenance actions include adjustment of the data transmission rate, connection pause and resume, troublemaker ejection and connection termination operations. These QoS monitoring and maintenance functions, based on monitored parameter status, provide rate-based congestion control. ISO/IEC 14476-2:2003 is an integral part of ITU-T draft Recommendation X.ectp | ISO/IEC 14476, which has 6 parts. All the protocol components, including packet formats and protocol procedures specified in ITU-T draft Recommendation X.606 | ISO/IEC 14476-1, are also valid in ISO/IEC 14476-2:2003.

ISO/IEC TR 18016:2003 identifies documents that specify how implementations of the MHS defined in the ITU-T X.400 series Recommendations | ISO/IEC 10021 may interwork with implementations of Internet e-mail. No requirements for conformance to this Technical Report are imposed.

This International Standard specifies a protocol which is used by Network Layer entities operating the protocol specified in ISO 8473 in Intermediate Systems to maintain routeing information for the purpose of routeing within a single routeing domain. The protocol specified in this International Standard relies upon the provision of a connectionless-mode underlying service.1) This International Standard specifies: a) procedures for the transmission of configuration and routeing information between network entities residing in Intermediate Systems within a single routeing domain; b) the encoding of the protocol data units used for the transmission of the configuration and routeing information; c) procedures for the correct interpretation of protocol control information; and d) the functional requirements for implementations claiming conformance to this International Standard. The procedures are defined in terms of a) the interactions between Intermediate system Network entities through the exchange of protocol data units; b) the interactions between a Network entity and an underlying service provider through the exchange of subnetwork service primitives; and c) the constraints on route determination which must be observed by each Intermediate system when each has a routeing information base which is consistent with the others.

ISO/IEC 8348:2002 defines the set of capabilities, in terms of abstract service definition, provided by the Network Layer to the Transport Layer. For designers of Transport Layer protocols, it provides a definition of the Network service to allow design and implementation independent of details of the Network Layer protocol. For designers of Network Layer protocols, it defines the set of capabilities to be made available through the action of the protocol.

This Recommendation | International Standard specifies the Enhanced Communications Transport Protocol (ECTP), which is a transport protocol designed to support Internet multicast applications over multicast-capable IP networks. This Recommendation | International Standard specifies the ECTP for the simplex multicast transport connection that consists of one sender and many receivers. This Recommendation | International Standard specifies the protocol procedures for the following protocol operations: a) connection creation with tree creation; b) multicast data transmission; c) tree-based reliability control with error detection, retransmission request and retransmission; d) late join and leave; e) tree membership maintenance; and f) connection termination.

This International Standard specifies the procedures, formats and facilities at the Packet Layer for Data Terminal Equipment (DTE) operating in conformance with ITU-T Recommendation X.25. Both Virtual Call and Permanent Virtual Circuit modes of operation are covered. The Packet Layer protocol specified herein can be used in both Open Systems Interconnection (OSI) and non-OSI environments. When used within the context of OSI, the Packet Layer protocol is encompassed in the Network Layer of the OSI Reference Model, ITU-T Rec. X.200 | ISO/IEC 7498-1. This International Standard covers DTE operation at the Packet Layer when accessing a public or private packet-switched network conforming to ITU-T Recommendation X.25 by means of a dedicated path or a circuit-switched connection. It also covers the additional Packet Layer procedures necessary for two DTEs conforming to this International Standard to communicate directly (i.e., without an intervening packet-switched network) over a dedicated path, a circuit-switched connection, or a local area network (LAN). This International Standard also covers private networks that use ITU-T Recommendation X.25 to connect to packet-switched public data networks and that may also offer an X.25 interface to a DTE (see annex A). To evaluate conformance of a particular implementation, it is necessary to have a statement of which capabilities and options have been implemented. Such a statement is called a Protocol Implementation Conformance Statement (PICS), as defined in ITU-T Rec. X.290 | ISO/IEC 9646-1. Annex B provides the PICS proforma in accordance with the relevant guidance given in ITUT Rec. X.296 | ISO/IEC 9646-7. The first edition of this International Standard was based on the 1984 CCITT Red Book text of Recommendation X.25. It also contained the necessary provisions for compatibility with the earlier 1980 CCITT Yellow Book text of Recommendation X.25. The second edition was based on the 1988 CCITT Blue Book text of Recommendation X.25. The third edition is based upon the 1993 version of X.25. This fourth edition is based on the 1996 version of X.25. Retained within this fourth edition are the necessary provisions for compatibility with the 1993, 1988, 1984 and 1980 versions of X.25. The differences between various editions of this International Standard are summarized in annex C. CCITT Recommendation X.613 (1992) | ISO/IEC 10588 : 1993, Information technology Use of X.25 Packet Layer Protocol in conjunction with X.21/X.21bis to provide the OSI connectionmode Network Service CCITT Recommendation X.614 (1992) | ISO/IEC 10732 : 1993, Information technology Use of X.25 Packet Layer Protocol to provide the OSI connection-mode Network Service over the telephone network

This part of ISO/IEC 8882 specifies a set of abstract tests for verifying that the implementation of X.25 protocols for use by Data Terminal Equipment (DTE), conforms to the requirements of International Standards that specify those protocols. Testing of a DCE is not subject of this test suite. Testing of a DTE in DCE mode is covered in test group 28 of this test suite a) specifies a PIXIT proforma; b) describes the relationship of the PICS to the test suite, c) describes the relationship of the PIXIT to the test suite, d) specifies a set of abstract tests using TTCN Graphical notation. This part of ISO/IEC 8882 defines the testing of a DTE operating at the packet layer designed to access a public or private packet-switched network conforming to CCITT respectively ITU-T Recommendation X.25 (1980, 1984, 1988, 1993) or another DTE conforming to ISO 8208. The specification of test cases in executable/machine processable TTCN is outside the scope of this part of ISO/IEC 8882.

This Recommendation | Technical Report provides: a) the description of a means to permit a protocol to be identified; b) a record of the structure and allowable ranges of protocol identifier(s) which can be assigned by ITU-T, ISO/IEC and other authorities; c) a record of the values of protocol identifiers used by OSI Network layer protocols and non-OSI protocols occupying a similar position: in particular, protocols with protocol control information commencing in octet 1 of the protocol data unit (header-oriented protocols), and protocols with protocol control information commencing in the final octet of the protocol data unit (trailer-oriented protocols), are covered; and d) a record of the values that are in use as protocol control information in non-Network layer protocols where they impact on Network layer protocol identification. The application of this Recommendation | Technical Report is: a) in the identification of internationally standardized Network layer protocols operating directly above the Data Link service; b) in the identification of protocols used in conjunction with internationally standardized Network layer protocols that operate directly above the Data Link service; and c) to distinguish between Internationally standardized Network layer protocols, and other internationally standardized protocols used in conjunction with internationally standardized Network layer protocols. This Recommendation | Technical Report is for use by ITU-T Study Groups, ISO/IEC Technical Committees and other authorities in applying the principles contained in clause 4, and in selecting an unused value or values from the range of values permitted in clauses 5 or 6, as appropriate. When a new value is selected, that value and its usage should be brought to the attention of ITU-T Study Group 7 or ISO/IEC JTC 1 SC6 so that this Recommendation | Technical Report can be amended.

This Recommendation | International Standard defines in an abstract way the externally visible service provided by the Transport Layer in terms of: a) the primitive actions and events of the service; b) the parameter data associated with each primitive action and event; c) the relationship between, and the valid sequences of, these actions and events. The service defined in this Recommendation | International Standard is that which is provided by the Enhanced Communications Transport Protocol (in conjunction with the Network Service) and which may be used by any application protocol. The service can also be provided by other protocols possibly each supporting a subset of the services defined herein. The primitives specified in this Recommendation | International Standard support a connection-mode service and a connectionless service. In some cases of connectionless-mode service supporting enhanced communications, certain operations may also be necessary prior to the commencement of data transfer, e.g. agreement on quality of service. For the data transfer phase of either connection-mode or connectionless-mode services, there may be a range of dataordering characteristics. No implication is made in this Recommendation | International Standard regarding the inclusion or exclusion of any of the above characteristics given the service primitives specified herein.

This Recommendation | International Standard provides the specification of management information within an Open System related to those operations of the OSI Network Layer. Specifics on how Network layer management is accomplished is beyond the scope of this Recommendation | International Standard. Network Layer management information is defined by specifying: ? the managed object class definition of Network Layer Managed Objects following guidelines put forth by the Structure of Management Information (see Recommendations X.720-X.724 and ISO/IEC 10165); ? the relationship of the Managed Objects and attributes to both the operation of the layer and to other objects and attributes of the layer; and ? the action type operations on the attributes of Network Layer Managed Objects that are available to OSI Systems Management. Annexes D, E, F and G, which are integral parts of this Recommendation | International Standard, provide ICS proformas associated with Network Layer management information.

This Recommendation | International Standard provides the specification of management information within an Open System related to those operations of the OSI Transport Layer specified by ITU-T Recommendations and ISO/IEC International Standards. Specifics on how Transport Layer management is accomplished is beyond the scope of this Recommendation | International Standard. Transport Layer management information is defined by specifying: ? the managed object class definition of Transport Layer Managed Objects following guidelines put forth by the Structure of Management Information (ITU-T Recommendations X.720-X.724 and ISO/IEC 10165); ? the relationship of the Managed Objects and attributes to both the operation of the layer and to other objects and attributes of the layer; and ? the action type operations on the attributes of Transport Layer Managed Objects that are available to OSI Systems Management. Annexes D, E, F and G, which are integral parts of this Recommendation | International Standard, provide ICS proformas associated with Transport Layer management information.

This Recommendation | International Standard specifies a protocol that is used to provide the connectionless-mode Network service described in ITU-T Rec. X.213 | ISO/IEC 8348 and to perform certain Network layer management functions. The protocol relies upon the provision of an underlying connectionless-mode service by real subnetworks and/or data links. The underlying connectionless-mode service assumed by the protocol may be obtained either directly, from a connectionless-mode real subnetwork, or indirectly, through the operation of an appropriate Subnetwork Dependent Convergence Function (SNDCF) or Protocol (SNDCP) over a connection-mode real subnetwork, as described in ISO/IEC 8648. This Recommendation | International Standard specifies the operation of the protocol with respect to a uniform, abstract "underlying subnetwork service". Other Recommendations | International Standards specify the way in which this "underlying subnetwork service" is obtained from real subnetworks, such as those which conform to ISO/IEC 8802 or ISO/IEC 8208. The "underlying subnetwork service" may be obtained from real subnetworks other than those that are specifically covered by the other Recommendations | International Standards. This Recommendation | International Standard specifies: a) procedures for the connectionless transmission of data and control information from one Network entity to one or more peer Network entities; b) the encoding of the Protocol Data Units (PDUs) used for the transmission of data and control information, comprising a variable-length protocol header format; c) procedures for the correct interpretation of protocol control information; and d) the functional requirements for implementations claiming conformance to this Recommendation | International Standard. The procedures are defined in terms of: a) the interactions among peer Network entities through the exchange of protocol data units; b) the interactions between a Network entity and a Network service user through the exchange of Network service primitives; and c) the interactions between a Network entity and an abstract underlying service provider through the exchange of service primitives. This Recommendation | International Standard also provides the PICS proforma for this protocol, in compliance with the relevant requirements, and in accordance with the relevant guidance, given in ITU-T Rec. X.290 | ISO/IEC 9646-1

Defines additional assumptions concerning the services optionally provided by the Network layer and adds no new functions of its own. The identical text is published as ITU-T Rec. X.234/Amd. 1.

Defines the testing of a DTE operating at the Data Link Layer and at the Packet Layer when accessing, by means of a dedicated path connection, switched or permanent, a public or private packet-switched network conforming to CCITT Recommendation X.25 or another DTE conforming to ISO/IEC 7776 and ISO/IEC 8208.

Differs from the other related International Standards by the layers defined in ISO/IEC 7498-1. In particular, it defines the way in which a local area network that conforms to ISO/IEC 8802 may be used as a subnetwork within the network layer to provide the abstract underlying service with respect to which the protocol defined by ISO/IEC 8473-1 is specified.

Describes the cross layer aspects of the revision of security services in the lower layers of the OSI reference Model (transport, network, data link, physical). Describes the architectural concepts common to these layers, the basis for interactions relating to security between layers and the placement of security protocols in the lower layers.

Provides a framework in which OSI protocols for routeing may be developed and to expedite the progression of routeing protocols through the standardisation process. Reflects the current state of OSI routeing and does not preclude future extensions and developments. Replaces the first edition, which has been technically revised.

Specifies a protocol to be used by End Systems and Intermediate Systems in order to provide security services in the Network layer, which is defined by CCITT Rec. X.213, ISO/IEC 8348 and ISO 8648. The protocol defined herein is called the Network Layer Security Protocol (NLSP).

Cancels and replaces the first edition (1990). Defines a protocol for the exchange of routeing information between an End System and a Subnetwork Address Resolution Entity, and between an Intermediate System and a Subnetwork Address Resolution Entity. Applicable to: End Systems which operate according to the main body of ISO/IEC 8878 to provide and support the OSI Connection-mode Network Service using ISO/IEC 8208; Subnetwork Address Resolution Entities which operate ISO/IEC 8208; Intermediate Systems which operate ISO/IEC 8208.

Cancels and replaces the first edition (1987). Specifies procedures for the connectionless-mode transmission of data and protocol control information; procedures for the correct interpretation of transport protocol control information; the functional requirements for implementations claiming conformance to this standard; the encoding of the transport-protocol-data-units used for the transmission of data and control information.