Out-of-band data

From Wikipedia, the free encyclopedia
Jump to: navigation, search

In computer networking, data which is distinguishable from any in-band data having the same bit pattern. An out-of-band data mechanism provides a conceptually independent channel, which allows any data sent via that mechanism to be kept separate from in-band data. The out-of-band data mechanism, when it exists, should be provided as an inherent characteristic of the data channel and transmission protocol, rather than requiring a separate channel and endpoints to be established.[1] The term "out-of-band data" probably derives from out-of-band signaling, as used in the telecommunications industry.[2]

Example case[edit]

Consider a networking application that tunnels data from a remote data source to a remote destination. The data being tunneled may consist of any bit patterns. The sending end of the tunnel may at times have conditions that it needs to notify the receiving end about. However, it cannot simply insert a message to the receiving end, because that end will not be able to distinguish the message from data sent by the data source. But using an out-of-band mechanism, the sending end can send the message to the receiving end out of band. The receiving end will be notified in some fashion of the arrival of out-of-band data, and it can read the out of band data and know that this is a message intended for it from the sending end, independent of the data from the data source.

Implementations[edit]

It is possible to implement out-of-band data transmission using a physically separate channel, but most commonly out-of-band data is a feature provided by a transmission protocol; typically such a protocol will divide transmitted data into chunks, which each chunk flagged as to whether it is in-band or out-of-band. A typical protocol might divide the data to be transmitted into blocks, which each block having a header word that identifies the type of data being sent, and a count of the data bytes or words to be sent in the block. The header will identify the data as being in-band or out-of-band, along with other identification and routing information. At the receiving end, the protocol looks at the header and routes the data to the normal reception endpoint if it is in-band, and to a separate mechanism if it is out-of-band. Depending on the implementation, there may be some mechanism for notifying or interrupting the receiving application when out-of-band data has arrived.

The most commonly used protocol containing an out-of-band data mechanism is the Internet's Transmission Control Protocol. It implements out-of-band data using an "urgent pointer", which marks certain data in the transmitted data stream as out-of-band. Unfortunately, a long-existing discrepancy between RFC 793 and RFC 1122 limits the usability of this feature of TCP; nonetheless, it is heavily used by certain standard application protocols, notably the Telnet protocol.

The Serial Advanced Technology Attachment (SATA) protocol commonly used to connect disk drives to computers implements an out-of-band data protocol.[3]

The Consultative Committee for Space Data Systems' Space Data Link Protocol implements an out-of-band mechanism via the "command" flag. When set, the received data is to be interpreted and acted on by the data link receiver, rather than being telemetry/telecommand information to be passed to the destination.[4]

Issues[edit]

Some sources define "out-of-band data" as including the characteristic that out-of-band data should be prioritized ahead of queued in-band data.[5] This is reinforced by TCP's (RFC 793) referring to the out-of-band data mechanism as "urgent data". However, prioritization is not an essential, nor a necessarily desirable, characteristic of out-of-band data. In fact, TCP implementations vary greatly on how they treat the "urgentness" of out-of-band data.[1]

References[edit]

  1. ^ a b Serverframework.com. "Out of band data, TCPUrgent mode and overlapped I/O". Retrieved 21 February 2014. 
  2. ^ "Chapter 11: Signaling Systems". George Mason University. Retrieved 21 February 2014. 
  3. ^ Altera Corporation. "AN-635-1.0 Application Note Implementing SATA and SAS Protocols in Altera Devices". Retrieved 21 February 2014. 
  4. ^ "TC Space Data Link Protocol". CCSDS 232.0-B-1. Consultative Committee for Space Data Systems. Retrieved 21 February 2014. 
  5. ^ Stevens, W. Richard; Rago, Stephen A. (2005). "16.7". Advanced Programming in the Unix Environment: Second Edition. Addison-Wesley Professional. p. 960. ISBN 0201433079. Retrieved 21 February 2014.