OOB(out-of-band data)

OOB(out-of-band data)(综合编辑)
传输层协议使用带外数据(out-of-band,OOB)来发送一些重要的数据,如过通信一放有重要的数据需要通知对方时,协议能够将这些数据快速地发送到对方.为了发送这些数据,协议一般不使用与普通数据相同的通道,而是使用另外的通道.linux系统的套接字机制支持低层协议发送和接受带外数据.但是TCP协议没有真正意义上的带外数据.为了发送重要协议,TCP提供了一种称为紧急模式(urgentmode)的机制.TCP协议在数据段中设置URG位,表示进入紧急模式.接收方可以对紧急模式采取特殊的处理.注意OOBD每次只能发送一个字节的数据。
1. 带外数据的发送。
函数： send(fd, 'a', 1, MSG_OOB);
tcp内核：不管什么情况（忽略掉nagle算法和窗口大小等因素），立刻发送一个urg包给对端，告诉对方我要发送OOB了和这个内容的位置。需要注意的是，实际的‘a'内容也是通过正常的发送缓冲区发送出去的。当发送区满的时候或是通告的窗口为0，紧急数据本身实际上也阻塞了，不管怎样至少一个urg通知包是发给对方了。但是此时接收端试图读取该紧急数据时，就会返回一个EWOULDBLOCK错误

2. 带外数据的接收。
默认情况下，带外数据是存放在专门的一个字节的带外数据缓冲区中的。一个tcp连接只有一个带外数据，第二个到来的带外数据会覆盖第一个到来的带外数据（如果程序没有处理第一个到来的带外数据的话）
函数： a. 通过信号处理SIGURG，过程首先设置文件描述字的进程属主，fcntl(sockfd, F_SETOWN,getpid());然后注册SIGURG信号处理句柄并且在句柄里面读取带外数据
b. select的异常条件。当带外数据到达时，sockfd会产生异常。但是需要注意的情况是，sockfd上的异常不会自动清除。当读取过带外数据之后，应该先将sockfd从异常fd_set中移除（否则将会进入死循环，一直检测到异常，然后读取带外数据，但是带外数据已经在第一次时就被读取了，于是就会返回EINVAL的错误），然后等待读取一部分正常数据之后，再设置sockfd到异常fd_set

c. 通过设置SO_OOBINLINE 和sockatmark()函数。首先设置SO_OOBINLINE在普通接收缓冲区中接收带外数据。然后程序读取该缓冲区时结合seockatmark检测是否当前位置属于带外数据区。注意，假设这样的而一个缓冲区内容123456x789.其中x为带外数据。read时内核会将123456和x789中间做标记。程序读取到x时会自动停住。然后下次继续读取剩下的（这是通过sockatmark就会发现处于带外数据区，此时如果read(sockfd,buf, 1)的话buf里面就时带外数据了(x).

Out-of-Band Data

When an application on a connected stream socket needs to send data that is more important than regular data on the stream, it can mark the important data as out-of-band (OOB) data. The application on the other end of a connection can receive and process OOB data through a separate logical channel that is conceptually independent of the data stream.

In TCP, OOB data is implemented via an urgent 1-bit marker (called URG) and a 16-bit pointer in the TCP segment header that identify a specific downstream byte as urgent data. Two specific ways of implementing urgent data currently exist for TCP. RFC 793, which describes TCP and introduces the concept of urgent data, indicates that the urgent pointer in the TCP header is a positive offset to the byte that follows the urgent data byte. However, RFC 1122 describes the urgent offset as pointing to the urgent byte itself.

The Winsock specification uses the term OOB to refer to both protocol-independent OOB data and TCP's implementation of OOB data (urgent data). To check whether pending data contains urgent data, you must call theioctlsocket function with the SIOCATMARK option. Chapter 7 discusses how to use SIOCATMARK.

Winsock provides several methods for obtaining the urgent data. Either the urgent data is inlined so that it appears in the normal data stream, or inlining can be turned off so that a discrete call to a receive function returns only the urgent data. The socket option SO_OOBINLINE, also discussed in detail in Chapter 7, controls the behavior of OOB data.

Telnet and Rlogin use urgent data for several reasons. However, unless you plan to write your own Telnet or Rlogin, you should stay away from urgent data. It's not well defined and might be implemented differently on platforms other than Windows. If you require a method of signaling the peer for urgent reasons, implement a separate control socket for this urgent data and reserve the main socket connection for normal data transfers.