`
`IEEE Std 1003.1-2001
`(Revision of IEEE Std 1003.1-1996
`and IEEE Std 1003.2-1992)
`
`Open Group Technical Standard
`Base Specifications, Issue 6
`
`1003.1TM
`Standard for Information Technology —
`Portable Operating System Interface (POSIX
`
`®
`
`)
`
`System Interfaces, Issue 6
`
`Approved 12 September 2001
`The Open Group
`
`IEEE Sponsor
`Portable Applications Standards Committee
`of the
`IEEE Computer Society
`
`Approved 6 December 2001
`IEEE-SA Standards Board
`
`SPRINGPATH
`EXHIBIT 1014
`
`
`
`(cid:70)(cid:114)(cid:115)(cid:124)(cid:117)(cid:108)(cid:106)(cid:107)(cid:119)(cid:104)(cid:103)(cid:35)(cid:112)(cid:100)(cid:119)(cid:104)(cid:117)(cid:108)(cid:100)(cid:111)(cid:35)(cid:111)(cid:108)(cid:102)(cid:104)(cid:113)(cid:118)(cid:104)(cid:103)(cid:35)(cid:119)(cid:114)(cid:35)(cid:87)(cid:107)(cid:104)(cid:114)(cid:103)(cid:114)(cid:117)(cid:114)(cid:118)(cid:35)(cid:78)(cid:114)(cid:113)(cid:118)(cid:119)(cid:100)(cid:113)(cid:119)(cid:100)(cid:110)(cid:114)(cid:115)(cid:114)(cid:120)(cid:111)(cid:114)(cid:118)(cid:35)(cid:114)(cid:113)(cid:35)(cid:53)(cid:51)(cid:52)(cid:57)(cid:48)(cid:51)(cid:59)(cid:48)(cid:54)(cid:51)(cid:35)(cid:105)(cid:114)(cid:117)(cid:35)(cid:111)(cid:108)(cid:102)(cid:104)(cid:113)(cid:118)(cid:104)(cid:104)(cid:42)(cid:118)(cid:35)(cid:120)(cid:118)(cid:104)(cid:35)(cid:114)(cid:113)(cid:111)(cid:124)(cid:49)(cid:35)(cid:35)(cid:70)(cid:114)(cid:115)(cid:124)(cid:117)(cid:108)(cid:106)(cid:107)(cid:119)(cid:104)(cid:103)(cid:35)(cid:100)(cid:113)(cid:103)(cid:35)(cid:68)(cid:120)(cid:119)(cid:107)(cid:114)(cid:117)(cid:108)(cid:125)(cid:104)(cid:103)(cid:35)(cid:101)(cid:124)(cid:35)(cid:76)(cid:72)(cid:72)(cid:72)(cid:49)(cid:35)(cid:35)(cid:85)(cid:104)(cid:118)(cid:119)(cid:117)(cid:108)(cid:102)(cid:119)(cid:108)(cid:114)(cid:113)(cid:118)(cid:35)(cid:68)(cid:115)(cid:115)(cid:111)(cid:124)(cid:49)
`
`Sockets
`
`General Information
`
`2685
`2686
`2687
`2688
`2689
`
`2690
`2691
`2692
`2693
`2694
`2695
`2696
`2697
`
`2698
`2699
`2700
`
`process no data if flow control does not allow the smaller of the send low water mark value or
`the entire request to be processed. A select( ) operation testing the ability to write to a socket shall
`return true only if the send low water mark could be processed. The default value for
`SO_SNDLOWAT is implementation-defined and protocol-specific. It is implementation-defined
`whether the SO_SNDLOWAT option can be set.
`The SO_SNDTIMEO option is an option to set a timeout value for the amount of time that an
`output function shall block because flow control prevents data from being sent. As noted in
`Table 2-2 (on page 64), the option value is a timeval structure with the number of seconds and
`microseconds specifying the limit on how long to wait for an output operation to complete. If a
`send operation has blocked for this much time, it shall return with a partial count or errno set to
`[EWOULDBLOCK] if no data were sent. The default for this option is the value zero, which
`indicates that a send operation will not time out. It is implementation-defined whether the
`SO_SNDTIMEO option can be set.
`The SO_TYPE option is used only on getsockopt( ). When this option is specified, getsockopt( )
`shall return the type of the socket (for example, SOCK_STREAM). This option is useful to
`servers that inherit sockets on start-up. SO_TYPE has no default value.
`
`2701 2.10.17 Use of Sockets for Local UNIX Connections
`Support for UNIX domain sockets is mandatory.
`UNIX domain sockets provide process-to-process communication in a single system.
`
`2702
`
`2703
`
`2705
`2706
`2707
`2708
`
`2704 2.10.17.1 Headers
`The symbolic constant AF_UNIX defined in the <sys/socket.h> header is used to identify the
`UNIX domain address family. The <sys/un.h> header contains other definitions used in
`connection with UNIX domain sockets. See the Base Definitions volume of IEEE Std 1003.1-2001,
`Chapter 13, Headers.
`The sockaddr_storage structure defined in <sys/socket.h> shall be large enough to
`accommodate a sockaddr_un structure (see the <sys/un.h> header defined in the Base
`Definitions volume of IEEE Std 1003.1-2001, Chapter 13, Headers) and shall be aligned at an
`appropriate boundary so that pointers to it can be cast as pointers to sockaddr_un structures
`and used to access the fields of those structures without alignment problems. When a
`sockaddr_storage structure is cast as a sockaddr_un structure, the ss_family field maps onto the
`sun_family field.
`
`2709
`2710
`2711
`2712
`2713
`2714
`2715
`
`2717
`2718
`
`2719
`
`2720
`
`2721 RS
`
`2716 2.10.18 Use of Sockets over Internet Protocols
`When a socket is created in the Internet family with a protocol value of zero, the implementation
`shall use the protocol listed below for the type of socket created.
`SOCK_STREAM
`IPPROTO_TCP.
`SOCK_DGRAM
`IPPROTO_UDP.
`SOCK_RAW
`IPPROTO_RAW.
`SOCK_SEQPACKET Unspecified.
`A raw interface to IP is available by creating an Internet socket of type SOCK_RAW. The default
`protocol
`for
`type SOCK_RAW shall be identified in the IP header with the value
`IPPROTO_RAW. Applications should not use the default protocol when creating a socket with
`type SOCK_RAW, but should identify a specific protocol by value. The ICMP control protocol is
`accessible from a raw socket by specifying a value of IPPROTO_ICMP for protocol.
`
`2722
`
`2723 RS
`2724
`2725
`2726
`2727
`
`66
`
`System Interfaces, Issue 6 — Copyright © 2001, IEEE and The Open Group. All rights reserved.
`
`2/2

Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ ChargeStill Working On It
This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.
Give it another minute or two to complete, and then try the refresh button.
A few More Minutes ... Still Working
It can take up to 5 minutes for us to download a document if the court servers are running slowly.
Thank you for your continued patience.

This document could not be displayed.
We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.
You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.
Set your membership
status to view this document.
With a Docket Alarm membership, you'll
get a whole lot more, including:
- Up-to-date information for this case.
- Email alerts whenever there is an update.
- Full text search for other cases.
- Get email alerts whenever a new case matches your search.

One Moment Please
The filing “” is large (MB) and is being downloaded.
Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!
If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document
We are unable to display this document, it may be under a court ordered seal.
If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.
Access Government Site