Reference |
Year |
Title |
Summary |
SIB Status |
C14B |
two thousand and seventeen |
Open Messaging Interface (O-MI), an Open Group Internet of Things (IoT) Standard |
The Open Messaging Interface (O-MI), an Open Group Internet of Things (IoT) Standard, fulfills the same purpose in the IoT Standards as HTTP does for the Internet. Typical examples of exchanged data are sensor readings, alarm or lifecycle events, requests for historical data, notifications about availability of new data, changes to existing data, etc. Just as HTTP can be used for transporting payloads in other formats as well as HTML, O-MI can be used for transporting payloads in almost any format. XML might currently be the most common text-based payload format but others, such as JSON, CSV, etc. may also be used. A defining characteristic of O-MI is that O-MI nodes do not have predefined roles, as it follows a peer-to-peer communications model. |
Adopted |
C173 |
two thousand and seventeen |
Technology Base Reference Models for Open Platform 3.0 ™ |
The objective of this Open Group Standard is to assist Enterprise and IT architects by specifying basic architecture models in which platforms interact with each other and with other system components, and to assist digital platform vendors to produce interoperable platforms. |
Adopted |
C195 |
one thousand nine hundred and ninety-two |
IPC Mechanisms for SMB |
This document is intended to assist application programmers designing distributed client/server applications whose server component is portable to all conformant systems. Readers must be experienced C-language programmers. Programmers writing applications to implement an LMX server should have read the complementary volume Protocols for X/Open PC Interworking: SMB, Version 2 (C209).
Registered Products (Product Standards) conforming to this Specification: LMX Server .
|
Adopted |
C209 |
one thousand nine hundred and ninety-two |
Protocols for X/Open PC Interworking: SMB, Version 2 |
This specification defines protocols that have been adopted by X/Open as the means of interoperability between personal computers (PCs) and X/Open-compliant systems. Server Message Block (SMB) is intended for use in situations where X/Open-compliant systems are added to an existing LAN consisting primarily of personal computers.
Registered Products (Product Standards) conforming to this Specification: LMX Server .
|
Adopted |
C303 |
one thousand nine hundred and ninety-three |
ACSE/Presentation Services API (XAP) |
This document defines an application programming interface (API) to the connection-oriented services of the Presentation Layer of the OSI protocol stack, including access to the ACSE application service element from the Application Layer. This API has been defined as an interface to support portable implementations of application-specific OSI services and non-OSI applications. This specification describes the XAP API and defines the functions and data structures which it provides for use by applications. |
Adopted |
C305 |
one thousand nine hundred and ninety-three |
Message Store API |
Developed and published in conjunction with the X.400 API Association, this document describes an API to the message store functions in an X.400 Message Handling System. The Message Store Abstract Service is described in X.413 and acts as an intermediary between the Message Transfer System and the User Agent. |
Adopted |
C310 |
one thousand nine hundred and ninety-four |
DCE 1.1: Time Services |
The title of this specification was changed from DCE: Time Services in October 1996 but the content is unchanged. This document specifies the Distributed Time Service (DTS) time representations, RPC interfaces to the DTS, and application programming interfaces to the DTS. The purpose of this document is to provide a portability guide for DTS application programs and a conformance specification for DTS implementations. This document includes text excerpted and/or derived from the Technology (AES) Specification (F013). |
Adopted |
C311 |
one thousand nine hundred and ninety-seven |
DCE 1.1: Authentication and Security Services |
This document specifies the DCE security model, services, interfaces, and protocols. Its purpose is to provide a portability guide for security programs and a conformance specification for DCE implementations. It is written for security application programmers and developers of DCE security implementations. This document includes text excerpted and/or derived from the Technology (AES) Specification. |
Adopted |
C316 |
one thousand nine hundred and ninety-four |
API to Electronic Mail (X.400), Issue 2 |
This document (X.400) defines the application programming interfaces (APIs) to Electronic Mail (X.400). These APIs provide for access to, and interconnection of, messaging systems whose architecture is in accordance with the CCITT/ISO X.400 Series of standards. This Issue 2 includes revisions to align with the IEEE X.400 API group of standards that are based on the previous version of this specification. All new implementation work by API providers should follow Issue 2. The previous specification will be retained for only as long as branding is available for products based on it. X.400 is one of several specifications that were originally developed in collaboration with the X.400 API Association. The other documents are XOM, XDS, XMS, XEDI, and Guide to Selected X.400 and Directory Services APIs. The XOM and XDS specifications are also the basis for corresponding IEEE standards and have been upgraded to Issue 2 for IEEE alignment. |
Adopted |
C403 |
one thousand nine hundred and ninety-five |
Federated Naming: The XFN Specification |
This document defines the model of a federated naming service together with an associated programmatic interface, and specifies the naming policies to be used in conjunction with this service. |
Adopted |
C408 |
one thousand nine hundred and ninety-five |
Remote Operations Service Element (XAP-ROSE) API |
This document specifies a superset of available services for those applications requiring a consistent method of access to the Remote Operations Service Application Service Element (ASE). The main benefit provided by these extensions is elimination of redundant code within applications using the ISO ROSE access method for OSI user applications as defined in ISO 9072-2 and ISO 9072-2. The exposed library interface (XAP-ROSE) comprises a set of ROSE primitives and attributes which are designed to be used along with the X/Open ACSE/Presentation Services (XAP) Service Library. A ROSE-Service user of this specification is presumed to be familiar with the X/Open ACSE/Presentation Services (XAP) API specification (C303). The target readers are system vendors (API implementors) who wish to implement the ISO 7-layer protocol stack which includes the ISO ROSE, and also independent software vendors (application implementors) who require to use an Invoke/Response paradigm for application in an ISO OSI (network)-compliant environment. |
Adopted |
C411 |
one thousand nine hundred and ninety-five |
X.25 Programming Interface using XTI (XX25) |
This document defines an Application Program Interface (API) for access to X.25 using the established X/Open Transport Interface (XTI). The OSI X.25 service is an international standard used throughout the world for wide area networks. The X.25 service interface defined in this specification is independent of any underlying X.25 provider, by its use of the existing XTI functions. |
Adopted |
C415 |
one thousand nine hundred and ninety-five |
FTAM High-level API (XFTAM), Version 2 |
This document defines the X/Open FTAM API, Version 2, a programming interface to the OSI File Transfer, Access, and Management protocol. Version 2 includes alignment with the IEEE FTAM Standard (P1238), which in turn includes support for context-sensitive mode of operation. XFTAM's functions implement high-level file transfer and file management operations using the service of an FTAM initiator and service provider which underlie the API. This specification is useful for implementors of applications which use the set of functions and data structures defined for this API to produce an application which is portable across OSI protocol stacks from a range of system vendors. |
Adopted |
C438 |
one thousand nine hundred and ninety-four |
Networking Services, Issue 4 |
This document contains the Technical Standards of both the X/Open Transport Interface (XTI) and X/Open Sockets Interface. Support for both XTI and Sockets interfaces is a requirement for conformance to the Single UNIX Specification and use of the associated UNIX Brand. The XTI Specification is technically identical to that contained in X/Open Transport Interface (XTI), Version 2 (C318), and either document can be used as the basis for XTI branding on an XPG4 Base platform. Registered Products (Product Standards) conforming to this specification: UNIX 95 , Sockets .
|
Adopted |
C520 |
one thousand nine hundred and ninety-six |
Multiprotocol Transport Networking (XMPTN): Address Mapper |
This specification defines the XMPTN Address Mapper, which provides dynamic address mapping services to nodes in a mixed transport protocol network. It gives a general solution for address mapping which would otherwise have to be provided by multiple protocol-specific address mapping schemes. |
Adopted |
C521 |
one thousand nine hundred and ninety-six |
Multiprotocol Transport Networking (XMPTN): Access Node |
This specification defines the XMPTN Access Node through which the mixed protocol networking services provided by XMPTN are accessed by applications. |
Adopted |
C522 |
one thousand nine hundred and ninety-six |
Multiprotocol Transport Networking (XMPTN): Data Formats |
This specification defines the XMPTN Data Formats; that is, formats of message and data structures used by XMPTN. |
Adopted |
C523 |
one thousand nine hundred and ninety-seven |
Networking Services, Issue 5 |
The Networking Services (XNS), Issue 5 specification describes the industry-standard open systems interfaces to communication services. These include two APIs to transport-level process-to-process communications: Sockets and XTI. Both Sockets and XTI are specified for use over Internet protocols (TCP, UDP, and IP) and ISO Transport protocols. They also include a set of Internet address resolution interfaces which are commonly used in conjunction with Sockets. XTI support for many other protocols is described in appendixes included in this specification. This document forms part of the Single UNIX Specification, Version 2 (T912) required for UNIX 98. It includes revisions to align with IEEE Standard 1003.1:1990 (Portable Operating System Interface). Registered Products (Product Standards) conforming to this specification: UNIX 98 , UNIX 98 Workstation , Transport Service (XTI) V2 , Sockets V2 .
|
Adopted |
C607 |
one thousand nine hundred and ninety-six |
OSI-Abstract-Data Manipulation API (XOM), Issue 3 |
This document defines the application programming interfaces (APIs) to management of Open Systems Interconnection (OSI) objects. This interface is needed by other APIs specific to particular OSI services. Currently, these include the APIs to Directory Services (XDS), X.400 Electronic Mail (XMHS), and Systems Management Protocol (XMP). Issue 3 includes revisions to align with the ISO OSI Object Management group of standards, which in turn was based on the previous issue of this specification. All new implementation work by API providers should be based on Issue 3. XOM is one of several specifications originally developed in collaboration with the XAPI Association. |
Adopted |
C609 |
one thousand nine hundred and ninety-six |
API to Electronic Mail (X.400), Issue 3 |
This document (XMHS Issue 3) defines the application programming interfaces (APIs) to Electronic Mail (X.400). These APIs provide for access to, andinterconnection of, messaging systems whose architecture isin accordance with the CCITT/ISO X.400 Series ofRecommendations. This 'Issue 3' of the XMHS CAE Specification includes revisions to align with the ISO MHS API group of Standards, which in turn were based on the previous issue of this XMHS Specification. All new implementation work by API providers should be based on XHMS Issue 3. XMHS is one of several specifications originally developed in collaboration with the XAPI Association. The other documents are OSI-Abstract-Data Manipulation (XOM) (C607), Directory Services (XDS) (C608), Message Storage (C305) and EDI specifications (P150). A Guide to Selected X.400 and Directory Services APIs is also available (G150). The XOM (C607) and XDS (C608) Specifications have also been aligned with the corresponding ISO Standards. |
Adopted |
C702 |
one thousand nine hundred and ninety-eight |
Protocols for Interworking: XNFS, Version 3W |
This Technical Standard is aligned with Sun's NFS Version 3, and incorporates the Sun WebNFS ™ extensions. The process of accessing remote files and directories as though they were part of the local file system hierarchy is commonly known as Transparent File Access (TFA). The most widely used heterogeneous TFS architecture is the Network File System (NFS), originally developed by Sun Microsytems. The Open Group XNFS offers a complete solution to transparent file access between open system-compliant systems, through the XNFS protocols for interoperability, and The Open Group XSI interfaces for application/user portability (as identified in several XNFS appendixes). |
Adopted |
C706 |
one thousand nine hundred and ninety-seven |
DCE 1.1: Remote Procedure Call |
This document specifies Remote Procedure Call (RPC) services, interface, protocols, encoding rules, and the Interface Definition Language (IDL). The purpose of this document is to provide a portability guide for RPC application programs and a conformance specification for RPC implementations. This document includes text excerpted and/or derived from the Technology (AES) Specification. |
Adopted |
C808 |
two thousand |
Networking Services, Issue 5.2 |
The Networking Services (XNS), Issue 5.2 specification defines the industry-standard open systems interfaces to communication services, including IPv6. These comprise the Sockets Interface and the X/Open Transport Interface (XTI). The Sockets Interface (part 2 of this document) is now the main industry-standard interface. XTI (part 3 of this document) is now considered to be obsolete, so writers of new applications using the Internet Protocol Suite (IPS) are recommended to use Sockets rather than XTI. Where protocols for which there is no Sockets support are in use, XTI is still recommended in preference to proprietary APIs. XNS Issue 5.2 is a new version of XNS Issue 5 (C523). (Please note, however, that C523 remains the requirement for UNIX 98.) The most important new feature is the inclusion of Internet Protocol version 6 (IPv6) functionality, in a manner which is aligned with the relevant IETF IPv6 standard (RFC 2553). |
Adopted |
C809 |
one thousand nine hundred and ninety-eight |
Resource Reservation Setup Protocol API (RAPI) |
This Technical Standard is based on the Internet Engineering Task Force (IETF) Internet Draft version 5 for RAPI, which is a specific Application Programming Interface (API) for the Resource ReSerVation Protocol (RSVP). Rather than develop this into an IETF RFC document, the IETF have deferred to The Open Group to develop RAPI into an open systems standard. The RAPI interface is one realization of the generic API contained in the RSVP Functional Specification (IETF RFC 2205). |
Adopted |
C810 |
two thousand |
Transport Provider Interface (TPI), Version 2 |
The Transport Provider Interface (TPI) Standard defines an interface for drivers that provide transport services in a networking environment. The TPI defines the set of messages and their formats that the driver must generate and process. This specification is firmly based on the TPI specification originally produced by UNIX International (UI). |
Adopted |
C811 |
two thousand |
Data Link Provider Interface (DLPI) Version 2 |
The Data Link Provider Interface (DLPI) Standard defines a STREAMS kernel-level instantiation of the ISO Data Link Service Definition DIS 8886 and Logical Link Control DIS 8802/2 (LLC). Where the two standards are not aligned, DIS 8886 prevails. The DLPI interface enables a data link service user to access and use any of a variety of conforming data link service providers without special knowledge of the provider's protocol. Specifically, the interface is intended to support X.25 LAPB, BX.25 level 2, SDL C, ISDN LAPD, Ethernet, CSMA/CD, FDDI, token ring, token bus, Bisync, Frame Relay, ATM, Fiber Channel and HIPPI. This list will be added to as new protocols are deployed. |
Adopted |
G110 |
one thousand nine hundred and ninety-one |
Guide to the Internet Protocol Suite |
This guide is aimed at both implementers and decision-makers and presents a detailed look at the scope of implementations of IPS available on UNIX and derivative systems. It bridges the gap between the official requirements and the reality of current products by presenting current common practice for such implementations. |
Adopted |
G143 |
two thousand and fourteen |
DirecNet ® Waveform Overview and Architecture |
The DirecNet Waveform Overview and Architecture Guide provides an overview to the DirecNet Family of Waveform and Network Management Interoperability Standards (the DirecNet Standards) that collectively define the requirements necessary to ensure interoperability at a specified level of performance between DirecNet terminals. The DirecNet Standards are open and vendor-neutral interoperability standards for an advanced IP-enabled, directional, high-capacity [or throughput] (4Gbps), ad hoc , mobile, mesh networking waveform as well as a policy-based network management interoperability standard for heterogeneous wireless networks.
Adherence to the protocols and procedures defined in the DirecNet Standards will enable a manufacturer’s terminal products to obtain DirecNet certification and interoperate with any other manufacturer’s terminal that has the same certification.
|
Adopted |
G506 |
one thousand nine hundred and ninety-six |
Multiprotocol Transport Networking (MPTN) Architecture, Version 2 |
This Guide introduces the concepts and the benefits to the user community of the Multiprotocol Transport Networking (MPTN) architecture. MPTN allows an application associated with one networking protocol to run without change over a different networking protocol. The impact of the MPTN architecture on the user community is anticipated in achievement of true transport independence for the communications interfaces (such as XTI, sockets, CPI-C), removal of restrictions on networks where applications can run, and increased connectivity between applications in different networks. This Guide explains the rationale for using MPTN, and describes an architecture model. As background information, it includes a summary of concerns that have commonly arisen regarding the MPTN approach to mixed-protocol networking, along with responses to those concerns. The Open Group has published specifications for Multiprotocol Transport Networking. |
Adopted |
INTERNET_STD_10 |
|
Simple Mail Transfer Protocol |
A set of RFCs which define the Simple Mail Transfer Protocol (SMTP). The objective of SMTP is to transfer mail reliably and efficiently. SMTP is independent of the particular transmission subsystem and requires only a reliable ordered data stream channel. An SMTP is its capability to relay mail across transport service environments. |
Adopted |
INTERNET_STD_11 |
|
Format of Electronic Mail Messages |
This Internet Standard provides the standard for the format of ARPA Internet messages. |
Adopted |
INTERNET_STD_12 |
|
Network Time Protocol (Version 2) Specification and Implementation |
This Internet Standard specifies the Network Time Protocol (NTP) which is used to synchronize timekeeping among a set of distributed time servers and clients. |
Adopted |
INTERNET_STD_13 |
one thousand nine hundred and eighty-seven |
Domain Name System |
A set of RFCs – 1034 and 1035 – that together define the Domain Name System (DNS). |
Adopted |
INTERNET_STD_3 |
one thousand nine hundred and eighty-nine |
Requirements for Internet Hosts |
A pair of RFCs – 1122 and 1123 – that together define the requirements for Internet host software. |
Adopted |
INTERNET_STD_33 |
one thousand nine hundred and ninety-two |
The TFTP Protocol (Revision 2) |
This Internet Standard defines the Trivial File Transfer Protocol (TFTP). It is a very simple protocol used to transfer files. Each non-terminal packet is acknowledged separately. |
Adopted |
INTERNET_STD_47 |
one thousand nine hundred and eighty-eight |
Serial Line Internet Protocol (SLIP) |
The Serial Line Internet Protocol (SLIP) is commonly used for point-to-point serial connections running TCP/IP. |
Adopted |
INTERNET_STD_5 |
one thousand nine hundred and eighty-one |
Internet Protocol version 4 (IPv4) |
A set of RFCs – 791, 792, 919, 922, 950, 1112 – that together define the standard for the Internet Protocol version 4 (IPv4). |
Adopted |
INTERNET_STD_51 |
one thousand nine hundred and ninety-four |
Point-to-Point Protocol (PPP) |
A set of RFCs that together define the Point-to-Point Protocol (PPP). |
Adopted |
INTERNET_STD_53 |
one thousand nine hundred and ninety-six |
Post Office Protocol - Version 3 |
This Internet Standard defines the Post Office Protocol, Version 3 (POP3). It consists of IETF RFC 1939. |
Adopted |
INTERNET_STD_6 |
one thousand nine hundred and eighty |
User Datagram Protocol |
An RFC – 768 – that defines the User Datagram Protocol (UDP), a datagram mode of packet-switched communication. UDP assumes that the Internet Protocol (IP) is used as the underlying protocol. |
Adopted |
INTERNET_STD_7 |
one thousand nine hundred and eighty-one |
Transmission Control Protocol |
An RFC – 793 – that defines the US DoD Standard Transmission Control Protocol (TCP). |
Adopted |
INTERNET_STD_8 |
one thousand nine hundred and eighty-three |
Telnet Protocol |
A set of RFCs – 854 and 855 – that together define the Telnet Protocol. |
Adopted |
INTERNET_STD_9 |
one thousand nine hundred and eighty-five |
File Transfer Protocol |
This Internet Standard defines commands and rules for the Internet File Transfer Protocol (FTP). |
Adopted |
ISO_10148 |
one thousand nine hundred and ninety-one |
Information Processing Systems - Open Systems Interconnection - Basic Remote Procedure Call (RPC) using OSI Remote Operations |
This standard defines the basic Remote Procedure Call (RPC) using OSI remote operations. It is an ISO adoption of the X/Open RPC Specification (C309). |
Withdrawn |
ISO_10607 |
one thousand nine hundred and ninety |
Information Technology - International Standardized Profiles AFTnn - File Transfer, Access, and Management |
This IPS defines profiles of service elements and data types applying to FTAM. |
Withdrawn |
ISO_8072 |
one thousand nine hundred and ninety-six |
Information Technology - Open Systems Interconnection - Transport Service Definition |
ISO/IEC 8072 defines the Open Systems Interconnection (OSI) transport service. It describes connectionless-mode transport services. |
Adopted |
ISO_8073 |
one thousand nine hundred and ninety-seven |
Information Technology - Open Systems Interconnection - Protocol for Providing the Connection-mode Transport Service |
ISO/IEC 8073 describes connection-oriented transport layer services and protocols. |
Adopted |
ISO_8327 |
one thousand nine hundred and ninety-six |
Information Technology - Open Systems Interconnection - Connection-oriented Session Protocol: Protocol Specification |
ISO/IEC 8327-1 describes connection-oriented Session Layer services, protocols, and formats. |
Adopted |
ISO_8571 |
one thousand nine hundred and eighty-eight |
Information Processing Systems - Open Systems Interconnection - File Transfer, Access, and Management |
ISO 8571 consists of four parts containing: introduction, definitions of virtual file store and file service, and protocol specification. |
Adopted |
ISO_8602 |
one thousand nine hundred and ninety-five |
Information Technology - Protocol for Providing the OSI Connectionless-mode Transport Service |
This standard 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; and the encoding of the transport protocol data units used for the transmission of data and control information. |
Adopted |
ISO_8649 |
one thousand nine hundred and ninety-six |
Information Technology - Open Systems Interconnection - Service Definition for the Association Control Service Element |
ISO/IEC 8649 defines the connection-oriented and connectionless Application Layer Association Control Service Element (ACSE). It defines service primitives which map directly to the equivalent primitives of the Presentation and Session Layers (with a number of additional parameters). |
Withdrawn |
ISO_8650 |
one thousand nine hundred and eighty-eight |
Information Processing Systems - Open Systems Interconnection - Protocol Specification for the Association Control Service Element |
ISO 8650 specifies the OSI Association Control Service Element (ACSE). |
Withdrawn |
ISO_8802-3 |
two thousand |
Information Technology - Telecommunications and Information Exchange Between Systems - Local and Metropolitan Area Networks - Specific Requirements - Part 3: CSMA/CD Access Method and Physical Layer Specifications |
ISO/IEC 8802-3 specifies the Carrier Sense Multiple Access with Collision Detection (CSMA/CD) access method and Physical Layer specifications. |
Adopted |
ISO_8802-4 |
one thousand nine hundred and ninety |
Information Technology - Telecommunications and Information Exchange Between Systems - Local and Metropolitan Area Networks - Specific Requirements - Part 4: Token-passing Bus Access Method and Physical Layer Specifications |
ISO/IEC 8802-4 specifies connection to a token bus LAN. |
Withdrawn |
ISO_8802-5 |
one thousand nine hundred and ninety-eight |
Information Technology - Telecommunications and Information Exchange Between Systems - Local and Metropolitan Area Networks - Specific Requirements - Part 5: Token Ring Access Method and Physical Layer Specifications |
ISO/IEC 8802-5 specifies connection to a token ring LAN. |
Adopted |
ISO_8823-1 |
one thousand nine hundred and ninety-four |
Information Technology - Open Systems Interconnection - Connection-oriented Presentation Protocol: Protocol Specification |
ISO/IEC 8823-1 cancels and replaces the first edition (1988). It specifies procedures for the transfer of data and control information from one presentation-entity to a peer presentation-entity; the means of selecting, by means of functional units, the procedures to be used by the presentation-entities; the structure and encoding of the presentation-protocol-data-units used for the transfer of data and control information. These procedures are applicable to instances of communication between systems which support the presentation layer of the OSI reference model and which wish to interconnect in an OSI environment. Also specifies conformance criteria for systems implementing these procedures. Does not contain tests which can be used to demonstrate this conformance. |
Adopted |
ISO_8824 |
one thousand nine hundred and ninety |
Information Technology - Open Systems Interconnection - Specification of Abstract Syntax Notation One (ASN.1) |
This standard specifies the Abstract Syntax Notation One (ASN.1). |
Withdrawn |
ISO_8825 |
one thousand nine hundred and ninety |
Information Technology - Open Systems Interconnection - Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1) |
This standard specifies a set of basic encoding rules that may be used to derive the specification of a transfer syntax for values of types defined using the notation specified in ISO/IEC 8824. These basic encoding rules are used at the time of communication (by the presentation service provider when required by a presentation context). Annex A gives an example of encoding. Annex B indicates the assignment of object identifier values. |
Withdrawn |
ISO_9040 |
one thousand nine hundred and ninety-seven |
Information Technology - Open Systems Interconnection - Virtual Terminal Basic Class Service |
ISO/IEC 9040 defines the Virtual Terminal Protocol. |
Adopted |
ISO_9041-1 |
one thousand nine hundred and ninety-seven |
Information Technology - Open Systems Interconnection - Virtual Terminal Basic Class Protocol - Part 1: Specification |
ISO/IEC 9041-1 specifies the Open Systems Interconnection (OSI) virtual terminal basic class protocol. |
Adopted |
ISO_9548 |
one thousand nine hundred and ninety-five |
Information Technology - Open Systems Interconnection - Connectionless Session Protocol |
This standard defines the connectionless session protocol. |
Adopted |
ISO_9576 |
one thousand nine hundred and ninety-one |
Information Technology - Open Systems Interconnection - Connectionless Presentation Protocol Specification |
This standard describes the Open Systems Interconnection (OSI) connectionless presentation protocol specification. |
Withdrawn |
ISO_ISP_10608-2 |
one thousand nine hundred and ninety-two |
Information Technology - International Standardized Profile TAnnnn - Connection-mode Transport Service over Connectionless-mode Network Service - Part 2: TA51 Profile |
This ISP is the TA51 Profile, which includes subnetwork-dependent requirements for CSMA/CD Local Area Networks (LANs). |
Adopted |
ISO_ISP_10608-5 |
one thousand nine hundred and ninety-two |
Information Technology - International Standardized Profile TAnnnn - Connection-mode Transport Service over Connectionless-mode Network Service - Part 5: TA1111/TA1121 Profiles |
This ISP defines Profile TA1111 and Profile TA1121. It includes subnetwork-dependent requirements for X.25 packet-switched data networks using virtual calls. |
Adopted |
ISO_ISP_10609-6 |
one thousand nine hundred and ninety-two |
Information Technology - International Standardized Profiles TB, TC, TD, and TE - Connection-mode Transport Service over Connection-mode Network Service - Part 6: Definition of Profiles TC1111/TC1121 |
This ISP defines Profile TC1111 and Profile TC1121. |
Adopted |
ISO_ISP_10609-7 |
one thousand nine hundred and ninety-two |
Information Technology - International Standardized Profiles TB, TC, TD, and TE - Connection-mode Transport Service over connection-mode Network Service - Part 7: Definition of Profiles TD1111/TD1121 |
This ISP defines Profile TD1111 and Profile TD1121. |
Adopted |
ITU-T_T.4 |
two thousand and three |
Standardization of Group 3 Facsimile Terminals for Document Transmission |
ITU-T Recommendation T.4 defines how telephone facsimile data is encoded. |
Adopted |
ITU-T_X.25 |
one thousand nine hundred and ninety-six |
Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) |
ITU-T Recommendation X.25 defines the X.25 Packet Layer Protocol. Specifically, it defines the interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and connected to public data networks by a dedicated circuit. |
Adopted |
ITU-T_X.400 |
one thousand nine hundred and ninety-nine |
Message Handling Services: Message Handling System and Service Overview |
This revision of ITU-T Recommendation X.400/F.400 (ISO/IEC 10021-1:2003) is a consolidation of Recommendation X.400/F.400 (07/96) and Amendment 1 (09/98). It provides an overview of system and services of Message Handling Systems (MHS). It should be considered in conjunction with the F.400-series and X.400-series of Recommendations. |
Adopted |
ITU-T_X.680 |
two thousand and eight |
Information Technology - Abstract Syntax Notation One (ASN.1): Specification of Basic Notation |
ITU-T Recommendation X.680 (ISO/IEC 8824-1) provides a notation called Abstract Syntax Notation One (ASN.1) for defining the syntax of information data. It defines a number of simple data types and specifies a notation for referencing these types and for specifying values of these types. The ASN.1 notations can be applied whenever it is necessary to define the abstract syntax of information without constraining in any way how the information is encoded for transmission. |
Adopted |
ITU-T_X.690 |
two thousand and eight |
Information Technology - ASN.1 Encoding Rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER), and Distinguished Encoding Rules (DER) |
ITU-T Recommendation X.690 (ISO/IEC 8825-1) defines a set of Basic Encoding Rules (BER) that may be applied to values of types defined using the ASN.1 notation. Application of these encoding rules produces a transfer syntax for such values. It is implicit in the specification of these encoding rules that they are also used for decoding. This Recommendation (pipe) International Standard also defines a set of Distinguished Encoding Rules (DER) and a set of Canonical Encoding Rules (CER), both of which provide constraints on the Basic Encoding Rules (BER). |
Adopted |
RFC_1014 |
one thousand nine hundred and eighty-seven |
XDR: External Data Representation Standard |
XDR is a standard for the description and encoding of data. |
Adopted |
RFC_1034 |
one thousand nine hundred and eighty-seven |
Domain Names - Concepts and Facilities |
This RFC is an introduction to the Internet Domain Name System (DNS). It describes domain style names – their use for Internet mail and host address support – and the protocols and servers used to implement domain name facilities. |
Adopted |
RFC_1035 |
one thousand nine hundred and eighty-seven |
Domain Names - Implementation and Specification |
This RFC describes the details of the Domain Name System (DNS) and protocol, and assumes that the reader is familiar with the concepts discussed in RFC 1034. |
Adopted |
RFC_1049 |
one thousand nine hundred and eighty-eight |
Content Type Header Field |
This RFC specifies a standardized Content-type field which allows mail reading systems to automatically identify the type of a structured message body and to process it for display accordingly. |
Adopted |
RFC_1050 |
one thousand nine hundred and eighty-eight |
RPC: Remote Procedure Call Protocol Specification |
Specifies a message protocol used in implementing the Sun Microsystems Remote Procedure Call (RPC) package. |
Adopted |
RFC_1094 |
one thousand nine hundred and eighty-nine |
NFS: Network File System Protocol Specification |
The Network File System (NFS) protocol provides transparent remote access to shared files across networks. The NFS protocol is designed to be portable across different machines, operating systems, network architectures, and transport protocols. This portability is achieved through the use of Remote Procedure Call (RPC) primitives built on top of an eXternal Data Representation (XDR). |
Superseded |
RFC_1112 |
one thousand nine hundred and eighty-nine |
Host Extensions for IP Multicasting |
This RFC specifies the extensions required of a host implementation of the Internet Protocol (IP) to support multicasting. It is the recommended standard for IP multicasting in the Internet. |
Adopted |
RFC_1119 |
one thousand nine hundred and eighty-nine |
Network Time Protocol (Version 2) Specification and Implementation |
This RFC specifies the Network Time Protocol (NTP) which is used to synchronize timekeeping among a set of distributed time servers and clients. |
Superseded |
RFC_1122 |
one thousand nine hundred and eighty-nine |
Requirements for Internet Hosts - Communication Layers |
This is one RFC of a pair that defines and discusses the requirements for Internet host software. This RFC covers the communications protocol layers: link layer, IP layer, and transport layer; its companion RFC 1123 covers the application and support protocols. |
Adopted |
RFC_1123 |
one thousand nine hundred and eighty-nine |
Requirements for Internet Hosts - Application and Support |
This RFC is one of a pair that defines and discusses the requirements for Internet host software. This RFC covers the application and support protocols; its companion RFC 1122 covers the communication protocol layers: link layer, IP layer, and transport layer. |
Adopted |
RFC_1155 |
one thousand nine hundred and ninety |
Structure and Identification of Management Information for TCP/IP-based Internets |
This RFC provides common definitions for the structure and identification of management information for TCP/IP-based Internets. In particular, it provides a simple, workable architecture and system for managing TCP/IP-based Internets. |
Adopted |
RFC_1179 |
one thousand nine hundred and ninety |
Line Printer Daemon Protocol |
This RFC describes an existing print server protocol widely used on the Internet for communicating between line printer daemons (both clients and servers). |
Adopted |
RFC_1213 |
one thousand nine hundred and ninety-one |
Management Information Base for Network Management of TCP/IP-based Internets |
This RFC defines the second version of the Management Information Base (MIB-II) for use with network management protocols in TCP/IP-based Internets. In particular, it provides a simple, workable architecture and system for managing TCP/IP-based Internets. |
Adopted |
RFC_1305 |
one thousand nine hundred and ninety-two |
Network Time Protocol (Version 3) Specification, Implementation, and Analysis |
This RFC describes the Network Time Protocol (NTP), specifies its formal structure, and summarizes information useful for its implementation. The NTP provides the mechanisms to synchronize time and coordinate time distribution in a large, diverse Internet operating at rates from mundane to lightwave. |
Adopted |
RFC_1327 |
one thousand nine hundred and ninety-two |
Mapping between X.400(1988) / ISO 10021 and RFC 822 |
This standard describes a set of mappings which will enable inter-working between systems operating the CCITT X.400 (1988) Recommendations on Message Handling Systems / ISO IEC 10021 Message-Oriented Text Interchange Systems (MOTIS), and systems using the RFC 822 mail protocol or protocols derived from RFC 822. |
Adopted |
RFC_1350 |
one thousand nine hundred and ninety-two |
The TFTP Protocol (Revision 2) |
This RFC defines the Trivial File Transfer Protocol (TFTP), which is a very simple protocol used to transfer files. Each non-terminal packet is acknowledged separately. This RFC describes the protocol and its types of packets. |
Adopted |
RFC_1521 |
one thousand nine hundred and ninety-three |
MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies |
RFC 822 (Internet Standard 11) defines a message representation protocol which specifies considerable detail about message headers, but which leaves the message content, or message body, as flat ASCII text. This document redefines the format of message bodies to allow multi-part textual and non-textual message bodies to be represented and exchanged without loss of information. |
Adopted |
RFC_1522 |
one thousand nine hundred and ninety-three |
MIME (Multipurpose Internet Mail Extensions) Part Two: Message Header Extensions for Non-ASCII Text |
This standard describes an extension to the message format defined in RFC 1521 to allow the representation of character sets other than ASCII in RFC 822 (Internet Standard 11) message headers. The extensions described were designed to be highly compatible with existing Internet mail handling software, and to be easily implemented in mail readers that support RFC 1521. |
Adopted |
RFC_1647 |
one thousand nine hundred and eighty-seven |
TN3270 Enhancements |
A protocol that more fully supports 3270 devices than do existing TN3270 practices. Defines a method of emulating both the terminal and printer members of the 3270 family of devices via Telnet. |
Withdrawn |
RFC_1661 |
one thousand nine hundred and ninety-four |
Point-to-Point Protocol (PPP) |
The Point-to-Point Protocol (PPP) is designed for simple links which transport packets between two peers. These links provide full-duplex simultaneous bi-directional operation, and are assumed to deliver packets in order. It is intended that PPP provides a common solution for easy connection of a wide variety of hosts, bridges, and routers. |
Adopted |
RFC_1662 |
one thousand nine hundred and ninety-four |
PPP in HDLC-like Framing |
The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. This document describes the use of HDLC-like framing for PPP encapsulated packets. |
Adopted |
RFC_1730 |
one thousand nine hundred and ninety-four |
Internet Message Access Protocol - Version 4 |
Defines the Internet Message Access Protocol, Version 4 (IMAP4), which allows a client to access and manipulate electronic mail messages on a server. |
Adopted |
RFC_1731 |
one thousand nine hundred and ninety-four |
IMAP4 Authentication Mechanisms |
The Internet Message Access Protocol, Version 4 (IMAP4) contains the AUTHENTICATE command, for identifying and authenticating a user to an IMAP4 server and for optionally negotiating a protection mechanism for subsequent protocol interactions. This document describes several authentication mechanisms for use by the IMAP4 AUTHENTICATE command. |
Adopted |
RFC_1734 |
one thousand nine hundred and ninety-four |
POP3 AUTHentication Command |
Describes the optional POP3 AUTH command for indicating an authentication mechanism to the server, performing an authentication protocol exchange, and optionally negotiating a protection mechanism for subsequent protocol interactions. The authentication and protection mechanisms used by the POP3 AUTH command are those used by IMAP4. |
Adopted |
RFC_1757 |
one thousand nine hundred and ninety-five |
Remote Network Monitoring Management Information Base |
This RFC defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based Internets. In particular, it defines objects for managing remote network monitoring devices. |
Adopted |
RFC_1869 |
one thousand nine hundred and ninety-five |
SMTP Service Extensions |
This RFC defines a framework for extending the SMTP service by defining a means whereby a server SMTP can inform a client SMTP as to the service extensions it supports. |
Superseded |
RFC_1870 |
one thousand nine hundred and ninety-five |
SMTP Service Extension for Message Size Declaration |
Defines an extension to the SMTP service whereby an SMTP client and server may interact to give the server an opportunity to decline to accept a message (perhaps temporarily) based on the client's estimate of the message size. |
Adopted |
RFC_1939 |
one thousand nine hundred and ninety-six |
Post Office Protocol - Version 3 |
This RFC defines the Post Office Protocol, Version 3 (POP3). POP3 is intended to permit a workstation to dynamically access a maildrop on a server host in a useful fashion. |
Adopted |
RFC_2001 |
one thousand nine hundred and ninety-seven |
TCP Slow Start, Congestion Avoidance, Fast Retransmit, and Fast Recovery Algorithms |
Modern implementations contain four intertwined algorithms for slow start, congestion avoidance, fast transmit, and fast recovery. This RFC documents these algorithms and refers to the requirements of RFC 1122. |
Adopted |
RFC_2008 |
one thousand nine hundred and ninety-six |
Implications of Various Address Allocation Policies for Internet Routing |
IP unicast address allocation and management are essential operational functions for the public Internet. This document addresses relevant fundamental technical issues, and makes recommendations with respect to policies for address allocation and management. |
Adopted |
RFC_2054 |
one thousand nine hundred and ninety-six |
WebNFS Client Specification |
This RFC describes a lightweight binding mechanism that allows NFS clients to obtain service from WebNFS-enabled servers with a minimum of protocol overhead. |
Adopted |
RFC_2055 |
one thousand nine hundred and ninety-six |
WebNFS Server Specification |
This RFC describes the specifications for a server of WebNFS clients. WebNFS extends the semantics of Versions 2 and 3 of the NFS protocols to allow clients to obtain file handles more easily, without recourse to the portmap or MOUNT protocols. |
Adopted |
RFC_2060 |
one thousand nine hundred and ninety-six |
Internet Message Access Protocol - Version 4rev1 |
This RFC specifies the Internet Message Access Protocol, Version 4rev1 (IMAP4rev1), which allows a client to access and manipulate electronic mail messages on a server. |
Adopted |
RFC_2065 |
one thousand nine hundred and ninety-seven |
Domain Name System Security Extensions |
Describes extensions to the Domain Name System (DNS) that provide these services to security-aware resolvers or applications through the use of cryptographic digital signatures. Same as RFC 1035 and RFC 2137. |
Adopted |
RFC_2131 |
one thousand nine hundred and ninety-seven |
Dynamic Host Configuration Protocol |
This RFC defines the Dynamic Host Configuration Protocol (DHCP) which provides a framework for passing configuration information to hosts on a TCP/IP network. DHCP is based on the Bootstrap Protocol (BOOTP). |
Adopted |
RFC_2132 |
one thousand nine hundred and ninety-seven |
DHCP Options and BOOTP Vendor Extensions |
This RFC specifies a set of Dynamic Host Configuration Protocol (DHCP) options. All of the DHCP options defined in this document, except for those specific to DHCP, may be used as BOOTP vendor information extensions. |
Adopted |
RFC_2136 |
one thousand nine hundred and ninety-seven |
Dynamic Updates in the Domain Name System (DNS Update) |
Specifies the UPDATE opcode of the Domain Name System (DNS) which provides for addition or deletion of RRs or RRsets from a specified zone. |
Adopted |
RFC_2137 |
one thousand nine hundred and ninety-seven |
Secure Domain Name System Update |
Covers security for the DNS update operation (Same as RFC 1035) |
Adopted |
RFC_2355 |
one thousand nine hundred and ninety-eight |
TN3270 Enhancements |
A protocol that more fully supports 3270 devices than does existing tn3270 practices. Defines a method of emulating both the terminal and printer members of the 3270 family of devices via Telnet. |
Adopted |
RFC_2460 |
one thousand nine hundred and ninety-eight |
Internet Protocol, Version 6 (IPv6) Specification |
This RFC specifies version 6 of the Internet Protocol (IPv6), also sometimes referred to as IP Next Generation or IPng. |
Adopted |
RFC_2461 |
one thousand nine hundred and ninety-eight |
Neighbor Discovery for IP Version 6 (IPv6) |
This RFC specifies the Neighbor Discovery protocol for IP Version 6 (IPv6). IPv6 nodes on the same link use Neighbor Discovery to discover each others' presence, to determine each others' link-layer addresses, to find routers, and to maintain reachability information about the paths to active neighbors. |
Adopted |
RFC_2462 |
one thousand nine hundred and ninety-eight |
IPv6 Stateless Address Autoconfiguration |
This RFC specifies the steps a host takes in deciding how to autoconfigure its interfaces in IPv6. The autoconfiguration process includes creating a link-local address and verifying its uniqueness on a link, determining what information should be autoconfigured (addresses, other information, or both), and in the case of addresses, whether they should be obtained through the stateless mechanism, the stateful mechanism, or both. |
Adopted |
RFC_2463 |
one thousand nine hundred and ninety-eight |
Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification |
This RFC specifies a set of Internet Control Message Protocol (ICMP) messages for use with version 6 of the Internet Protocol (IPv6). |
Adopted |
RFC_2487 |
one thousand nine hundred and ninety-nine |
SMTP Service Extension for Secure SMTP over TLS |
This RFC describes an extension to the SMTP service that allows an SMTP server and client to use transport-layer security to provide private, authenticated communication over the Internet. This gives SMTP agents the ability to protect some or all of their communications from eavesdroppers and attackers. |
Adopted |
RFC_2554 |
one thousand nine hundred and ninety-nine |
SMTP Service Extension for Authentication |
This RFC defines an SMTP service extension (ESMTP) whereby an SMTP client may indicate an authentication mechanism to the server, perform an authentication protocol exchange, and optionally negotiate a security layer for subsequent protocol interactions. This extension is a profile of the Simple Authentication and Security Layer (SASL). |
Adopted |
RFC_2569 |
one thousand nine hundred and ninety-nine |
Mapping between LPD and IPP Protocols |
This RFC defines an experimental protocol mapping between LPD and IPP for the Internet community. |
Adopted |
RFC_2616 |
one thousand nine hundred and ninety-nine |
Hypertext Transfer Protocol - HTTP/1.1 |
The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. It is a generic, stateless protocol which can be used for many tasks beyond its use for hypertext, such as name servers and distributed object management systems, through extension of its request methods, error codes, and headers. |
Adopted |
RFC_2910 |
two thousand |
Internet Printing Protocol 1.1: Encoding and Transport |
This RFC is one of a set which together describe all aspects of the Internet Printing Protocol (IPP). IPP is an application-level protocol that can be used for distributed printing using Internet tools and technologies. |
Adopted |
RFC_2911 |
two thousand |
Internet Printing Protocol 1.1: Model and Semantics |
This RFC is one of a set which together describe all aspects of the Internet Printing Protocol (IPP). IPP is an application-level protocol that can be used for distributed printing using Internet tools and technologies. |
Adopted |
RFC_3010 |
two thousand |
NFS version 4 Protocol |
The Network File System (NFS) version 4 is a distributed file system protocol. Version 4 is a revision of the NFS protocol defined by RFC 1094 (version 2) and RFC 1813 (version 3). Unlike earlier versions, the NFS version 4 protocol supports traditional file access while integrating support for file locking and the mount protocol. |
Adopted |
RFC_3513 |
two thousand and three |
Internet Protocol Version 6 (IPv6) Addressing Architecture |
This RFC defines the addressing architecture of the Internet Protocol Version 6 (IPv6). |
Adopted |
RFC_5321 |
two thousand and eight |
Simple Mail Transfer Protocol |
This RFC specifies the basic protocol for Internet electronic mail transport. It consolidates, updates, and clarifies several previous documents, making all or parts of most of them obsolete. It covers the SMTP extension mechanisms and best practices for the contemporary Internet. |
Pending |
RFC_5322 |
two thousand and eight |
Internet Message Format |
This RFC specifies the Internet Message Format (IMF), a syntax for text messages that are sent between computer users, within the framework of electronic mail messages. |
Pending |
RFC_768 |
one thousand nine hundred and eighty |
User Datagram Protocol |
This RFC defines the User Datagram Protocol (UDP) – a datagram mode of packet-switched communication. UDP assumes that the Internet Protocol (IP) is used as the underlying protocol. |
Adopted |
RFC_791 |
one thousand nine hundred and eighty-one |
Internet Protocol |
This RFC specifies the DoD Standard Internet Protocol. It is based on six earlier editions of the ARPA Internet Protocol Specification, and the present text draws heavily from them. |
Adopted |
RFC_792 |
one thousand nine hundred and eighty-one |
Internet Control Message Protocol |
Defines ICMP – a control protocol forming an integral part of IP that is used for communication by a gateway or destination host with a source host; for example, to report an error in datagram processing. |
Adopted |
RFC_793 |
one thousand nine hundred and eighty-one |
Transmission Control Protocol |
This RFP defines the US DoD Standard Transmission Control Protocol (TCP). |
Adopted |
RFC_821 |
one thousand nine hundred and eighty-two |
Simple Mail Transfer Protocol |
This RFC defines the Simple Mail Transfer Protocol (SMTP). The objective of SMTP is to transfer mail reliably and efficiently. SMTP is independent of the particular transmission subsystem and requires only a reliable ordered data stream channel. |
Superseded |
RFC_822 |
one thousand nine hundred and eighty-two |
Standard for the Format of ARPA Internet Text Messages |
Specifies a syntax for text messages that are sent among computer users within the framework of electronic mail. Supersedes RFC 733. |
Superseded |
RFC_854 |
one thousand nine hundred and eighty-three |
Telnet Protocol Specification |
This RFC defines commands and rules for the Internet virtual terminal protocol (Telnet). Its primary goal is to allow a standard method of interfacing terminal devices and terminal-oriented processes to each other. |
Adopted |
RFC_855 |
one thousand nine hundred and eighty-three |
Telnet Option Specifications |
This RFC specifies a method of Telnet option code assignment and standards for documentation of options. |
Adopted |
RFC_919 |
one thousand nine hundred and eighty-four |
Broadcasting Internet Datagrams |
This RFC defines simple rules for broadcasting Internet datagrams on local networks that support broadcast, for addressing broadcasts, and for how gateways should handle them. |
Adopted |
RFC_922 |
one thousand nine hundred and eighty-four |
Broadcasting Internet Datagrams in the Presence of Subnets |
This RFP defines simple rules for broadcasting Internet datagrams on local networks that support broadcast, for addressing broadcasts, and for how gateways should handle them. |
Adopted |
RFC_950 |
one thousand nine hundred and eighty-five |
Internet Standard Subnetting Procedure |
This RFC defines the recommended procedures for the use of subnets in the Internet. These procedures are for hosts (e.g., workstations). |
Adopted |
RFC_959 |
one thousand nine hundred and eighty-five |
File Transfer Protocol (FTP) |
This RFC is the official specification of the File Transfer Protocol (FTP). It defines commands and rules for FTP. |
Adopted |
RFC_974 |
one thousand nine hundred and eighty-six |
Mail Routing and the Domain System |
Describes how mailers are to decide how to route a message addressed to a given Internet domain name involving interpretation of MX RRs (host-specific resource records), which are used for message routing. |
Adopted |
X04IP |
two thousand and four |
Internet Protocol Version 6 |
This Product Standard defines a set of programming APIs and services in support of the Internet Protocol Version 6. |
Adopted |
X04PS |
two thousand and four |
Internet Server V2 |
This Product Standard defines a set of services in support of Internet and intranet technologies. This includes support of network clients and the presence of a mandatory Java Runtime Environment. |
Adopted |
X98GG |
one thousand nine hundred and ninety-eight |
X.400 Gateway |
This Product Standard provides facilities for the construction of portable gateway applications that allow messages from one messaging system (e.g., email) to be converted and forwarded according to the formats and conventions of another messaging system. |
Adopted |
X98GM |
one thousand nine hundred and ninety-eight |
X.400 Message Access |
This Product Standard provides facilities for the construction of portable X.400 messaging systems (e.g., email) by making the services of a message transfer system (MTS) available to applications implementing either a user agent (UA) or message store (MS). |
Adopted |
X98GN |
one thousand nine hundred and ninety-eight |
Network File System |
This Product Standard provides an application program acting as a client in a client/server configuration with transparent access to files held on the remote server. For more detail, refer to the Summary of this Product Standard . |
Adopted |
X98GP |
one thousand nine hundred and ninety-eight |
Sockets |
This Product Standard provides applications with the sockets interface to the underlying communications system. It is required for UNIX 95. For more detail, refer to the Summary of this Product Standard . |
Adopted |
X98GQ |
one thousand nine hundred and ninety-eight |
Sockets V2 |
This Product Standard provides applications with the sockets interface to the underlying communications system. It is an enhancement of the Sockets Product Standard, and is required for UNIX 98. For more detail, refer to the Summary of this Product Standard . |
Adopted |
X98GS |
one thousand nine hundred and ninety-eight |
Transport Service (XTI) |
This Product Standard provides a single programming interface to a variety of transport services: OSI, TCP/IP, UDP/IP, and NetBIOS. It is required for UNIX 95. For more detail, refer to the Summary of this Product Standard . |
Adopted |
X98GV |
one thousand nine hundred and ninety-eight |
Transport Service (XTI) V2 |
This Product Standard provides a single programming interface to a variety of transport services: OSI, TCP/IP, UDP/IP, and NetBIOS. It is an enhancement of the Transport Service (XTI) Product Standard, and is required for UNIX 98. For more detail, refer to the Summary of this Product Standard . |
Adopted |
X98PL |
one thousand nine hundred and ninety-eight |
LMX Server |
This Product Standard provides LMX server facilities which allow a conformant system to act as a file and print server to a network of DOS-based PCs. |
Adopted |
X98PN |
one thousand nine hundred and ninety-eight |
(PC)NFS Server |
This Product Standard provides (PC)NFS server facilities which allow a conforming system to act as a file and print server for a network of DOS-based PCs. For more detail, refer to the Summary of this Product Standard . |
Adopted |
X98PS |
one thousand nine hundred and ninety-eight |
Internet Server |
This Product Standard defines a set of services in support of Internet and intranet technologies, including support of network computer devices and the presence of a mandatory Java Runtime Environment (JRE). For more detail, refer to the Summary of this Product Standard . |
Adopted |