Lines Matching +full:protocol +full:- +full:node

1 .\" Copyright (c) 2001-2002 Maksim Yevmenkin <m_evmenkin@yahoo.com>
32 .Nd Netgraph node type that implements Bluetooth Logical Link Control and
33 Adaptation Protocol (L2CAP)
41 node type is a Netgraph node type that implements Bluetooth Logical Link
42 Control and Adaptation Protocol as per chapter D of the Bluetooth Specification
45 L2CAP provides connection-oriented and connectionless data services to upper
46 layer protocols with protocol multiplexing capability, segmentation and
52 .Bl -enum -offset indent
60 The Baseband always provides the impression of full-duplex communication
62 This does not imply that all L2CAP communications are bi-directional.
75 The Logical Link Control and Adaptation Protocol (L2CAP) is based around the
78 Each channel is bound to a single protocol in a many-to-one fashion.
80 channels can be bound to the same protocol, but a channel cannot be bound to
83 the appropriate higher level protocol.
85 Each one of the end-points of an L2CAP channel is referred to by a channel
88 channel end-point on the device.
92 illegal identifier and must never be used as a destination end-point.
94 CID 0x0002 is reserved for group-oriented channel.
106 .Bl -tag -width foo
116 In this state, the CID represents a local end-point and an L2CAP Connect
120 In this state, the remote end-point exists and an L2CAP Connect Request has
173 .Ss Protocol Multiplexing
174 L2CAP supports protocol multiplexing because the Baseband Protocol does not
177 field identifying the higher layer protocol being multiplexed above it.
179 Discovery Protocol, RFCOMM and Telephony Control.
181 The data packets defined by the Baseband Protocol are limited in size.
191 The Baseband Protocol supports the concept of a piconet, a group of devices
194 abstraction permits implementations to efficiently map protocol groups on to
198 .Bl -dash -offset indent
210 This node type supports the following hooks:
211 .Bl -tag -width ".Va hci"
215 Upper layer protocol upstream hook.
224 L2CAP node uses
227 The upper layer protocol must populate
229 L2CAP node will queue request and start processing.
231 ready or timeout has occurred, L2CAP node will create new Netgraph message, set
244 .Bl -tag -width foo
248 Input parameters are the target protocol (PSM) and remote
249 device's 48-bit address (BD_ADDR).
263 are the remote device's 48-bit address, Identifier sent in the request, local
272 incoming receivable MTU (InMTU), new outgoing flow spec-ification, and flush
298 is zero if an L2CAP Disconnect Response is received, otherwise a non-zero value
309 .Bd -literal -offset indent
327 .Bf -emphasis
332 .Bf -emphasis
340 .Bf -emphasis
348 .Bf -emphasis
358 .Bf -emphasis
381 This node type supports the generic control messages, plus the following:
382 .Bl -tag -width foo
384 Returns current state for the node.
386 Returns an integer containing the current debug level for the node.
389 for the node.
403 This node shuts down upon receipt of an
415 node type was implemented in