This form contains a series of questions that need to be answered. As you go about answering the questions, please keep the following things in mind:

• While it is not required that each question be answered at this time, all questions must have answers before the response is submitted to The Open Group for review and publication.
• Press the "Save" button at any time to save work in progress. Once the work has been saved, there is the option to continue editing if required.
• Many questions have instructions to assist in development of answers. They are marked with the indicator. Please look at the instructions carefully.
• Although HTML markup can be included in answers, this is not recommended apart from basic tags such as <p> and <br>, since incorrect markup could effect the format of other items in the document.
• Questions on this system should be addressed to the Conformance Statement manager at The Open Group.

Enter the name of the Organization that produced the implementation and the name of the author of the Conformance Statement.

1. Sockets

Product Information

Environment Specification

Answer the questions for each binary-compatible family. Alternately, provide the answers in the Appendix at the end of this document.

	Testing Environment	Binary-compatible Family	Portability Environment	Indicator of Compliance	Compliance Details
			Select from this list Internationalised System Calls and Libraries Extended	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			Select from this list Internationalised System Calls and Libraries Extended	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			Select from this list Internationalised System Calls and Libraries Extended	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			Select from this list Internationalised System Calls and Libraries Extended	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			Select from this list Internationalised System Calls and Libraries Extended	Select from this list Test Report from Test Suite	Test Suite: Test Report:

Temporary Waivers

1.1 Supported Features

1.1.1 Socket Domains

Question 1: Which socket domains are supported by the implementation?

Response

The following table contains three columns of information. The first column lists the supported address families (domains), the second column identifies the socket types within an address family, and the third column lists the protocols supported for each domain/socket-type combination. ("N/A" = not applicable)

The included entries are mandatory for conformance to this Product Standard. Add any additional domain/type/protocol combinations supported by the implementation.



	Domain	Type	Protocol

Rationale

The CAE Specification, Networking Services, Issue 4, defines that the domains, socket types and protocols supported by a conforming system are implementation-dependent. Component Definitions, Issue 2, states that products conforming to the Sockets Product Standard definition shall be available in configurations that support the following socket domains:

• AF_INET, with at least SOCK_STREAM and SOCK_DGRAM socket types
• AF_UNIX, with at least the SOCK_STREAM socket type.

Reference

CAE Specification, Networking Services, Issue 4, Chapter 8, Sockets Interfaces, socket().

Sockets Product Standard Definition.

1.2 Limits

1.2.1 Listen Queues

Question 2: What is the limit the implementation places on the length of a socket's listen queue?

Response

Indicate the implementation's limit on the length of the socket's listen queue, or "None" if no limit is imposed.

Rationale

The specification states that an implementation may limit the length of a socket's listen queue, and that this limit may be imposed if the setting of the backlog argument exceeds an implementation-dependent maximum value.

Reference

CAE Specification, Networking Services, Issue 4, Chapter 8, Sockets Interfaces, listen().

1.3 Reference Manual Pages

1.3.1 Error Numbers

Question 3: Which of the following optional errors listed in the Reference Manual Pages are detected in the circumstances specified?

Response

Function	Error	Detected
accept()	ENOMEM	Yes   No
	ENOBUFS	Yes   No
	ENOSR	Yes   No
	EPROTO	Yes   No
bind()	EINVAL	Yes   No
	EISCONN	Yes   No
	ENAMETOOLONG	Yes   No
	ENOBUFS	Yes   No
	ENOSR	Yes   No
connect()	EADDRINUSE	Yes   No
	ECONNRESET	Yes   No
	EHOSTUNREACH	Yes   No
	EINVAL	Yes   No
	ENAMETOOLONG	Yes   No
	ENETDOWN	Yes   No
	ENOBUFS	Yes   No
	ENOSR	Yes   No
	EOPNOTSUPP	Yes   No
fgetpos()	ESPIPE	Yes   No
fsetpos()	ESPIPE	Yes   No
ftell()	ESPIPE	Yes   No
getpeername()	ENOBUFS	Yes   No
	ENOSR	Yes   No
getsockname()	EINVAL	Yes   No
	ENOBUFS	Yes   No
	ENOSR	Yes   No
getsockopt()	EINVAL	Yes   No
	ENOBUFS	Yes   No
	ENOSR	Yes   No
listen()	EINVAL	Yes   No
	ENOBUFS	Yes   No
recv()	EIO	Yes   No
	ENOBUFS	Yes   No
	ENOMEM	Yes   No
	ENOSR	Yes   No
recvfrom()	EIO	Yes   No
	ENOBUFS	Yes   No
	ENOMEM	Yes   No
	ENOSR	Yes   No
recvmsg()	EINVAL	Yes   No
	EIO	Yes   No
	ENOBUFS	Yes   No
	ENOMEM	Yes   No
	ENOSR	Yes   No
send()	ENETDOWN	Yes   No
	EHOSTUNREACH	Yes   No
	ENOBUFS	Yes   No
	ENOSR	Yes   No
	EIO	Yes   No
sendmsg()	EDESTADDRREQ	Yes   No
	EHOSTUNREACH	Yes   No
	EINVAL	Yes   No
	EIO	Yes   No
	EISCONN	Yes   No
	ENAMETOOLONG	Yes   No
	ENETDOWN	Yes   No
	ENETUNREACH	Yes   No
	ENOBUFS	Yes   No
	ENOMEM	Yes   No
	ENOSR	Yes   No
sendto()	EDESTADDRREQ	Yes   No
	EHOSTUNREACH	Yes   No
	EINVAL	Yes   No
	EIO	Yes   No
	EISCONN	Yes   No
	ENAMETOOLONG	Yes   No
	ENETDOWN	Yes   No
	ENETUNREACH	Yes   No
	ENOBUFS	Yes   No
	ENOMEM	Yes   No
	ENOSR	Yes   No
setsockopt()	ENOMEM	Yes   No
	ENOBUFS	Yes   No
	ENOSR	Yes   No
shutdown()	ENOBUFS	Yes   No
	ENOSR	Yes   No
socket()	ENOBUFS	Yes   No
	EMNOMEM	Yes   No
	ENOSR	Yes   No
socketpair()	EACCES	Yes   No
	ENOMEM	Yes   No
	ENOBUFS	Yes   No
	ENOSR	Yes   No

Rationale

Each of the above error conditions is marked as optional in the Reference Manual Pages and an implementation may return this error in the circumstances specified or may not provide the error indication.

Reference

CAE Specification, Networking Services, Issue 4, Chapter 8, Sockets Interfaces, ERRORS.

2. Appendix

Copyright © 
All rights reserved.

3. Change History