IrLAP fast connect appnote V1.0 errata

Errata for IrLAP Fast Connect Version 1.0

(April 2, 2003)

Following are a list of errata to IrLAP Fast Connect version 1.

The points are classified according to the following scheme:

•CORRECTION: a change required to correct an error in the existing document. Corrections may change the specified behavior of the protocol to match, that which was originally intended by the authors.

•CLARIFICATION: textual enhancement that provides clearer explanation of a protocol element without changing any behavior.

•MODIFICATION: a modification of the currently specified behavior that adds but does not delete any function from the protocol.

•CHANGE: a modification of the currently specified protocol that may add and or delete function from the protocol.

•PROBLEM: a known problem for which an alteration to the document has yet to be proposed.

Proposed Errata

Section 3

MODIFICATION

The fourth paragraph of Section 3 describes the use of a 1-slot discovery procedure as the basis for a Fast Connect profile. The modification proposed by these errata is to change the XID command format used in the 1-slot discovery from the standard discovery XID command to a Fast Connect XID command. The picture below shows the format of a standard discovery XID command frame.

	1 byte	4 bytes	4 bytes	1 byte	1 byte	1 byte	32 bytes
	FI	Source	Destination	Discovery	Slot	Version	Discovery Info
	X’01’	Device Address	Device Address	Flags	Number	Number

The Fast Connect XID frame follows the same format. The only change is in the Discovery Flags field. In the standard XID command frame bits 3 – 7 are reserved and must be set to 0 (as defined in IrLAP version 1.1). Devices receiving the XID command frame must ignore bits 3 – 7. The Fast Connect XID command frame sets bit 3 of the Discovery Flags to 1 so that it can be distinguished from the standard XID command frame. Devices adhering to IrLAP version 1.1 will interpret the Fast Connect XID command frame as a standard discovery XID frame and respond appropriately. Devices supporting Fast Connect will be able to identify the Fast Connect XID command frame.

All places in the version 1.0 document that reference the XID command frame must be changed to reference the new Fast Connect XID command frame.

Section 2

MODIFICATION

The service IrLAP_FAST_CONNECT.setMode will be modified as follows:

Original:

IrLAP_FAST_CONNECT.setMode(mode, Responder Profile)

New:

IrLAP_FAST_CONNECT.setProfile(Responder Profile)

All references to setMode throughout the document will be changed to setProfile. There is no need to change to a different state machine so all references to state machine change will be deleted. The changes are as follows:

Original:

Description: The request primitive is used to request that a fast IrLAP connection be established to the first station which responds to any of the command messages (frames) specified in the Initiator Profile. The Initiator Profile specifies the sequence of commands to send including the timing between commands, the acceptable responses and the baud rate at which to send the command and then listen for the response. The setMode primitive is used by a responder to switch from the normal NDM state machines to the Fast Connect state machine. Fast Connect uses many of the same frames used in standard IrLAP discovery and connect procedures so it is necessary to explicitly change to a Fast Connect state machine. The mode flag is used to switch between the standard NDM and Fast Connect state machines. The Responder Profile specifies the acceptable commands to which the responder will respond. It also specifies the response messages for each command, the baud rates at which to listen/respond and the number of times to retry a failed response before responding to the required XID command. The indication primitive indicates an IrLAP connection has been completed and provides the Device Address, Source-Device-Adr, of the station acting as the primary. The confirm primitive is returned on successful establishment of the connection and provides the Device Address, Destination-Device-Adr of the station acting as the secondary. After this, all primitives refer to the established connection by the Connection-Handle.

New:

Description: The request primitive is used to request that a fast IrLAP connection be established to the first station which responds to any of the command messages (frames) specified in the Initiator Profile. The Initiator Profile specifies the sequence of commands to send including the timing between commands, the acceptable responses and the baud rate at which to send the command and then listen for the response. The setProfile primitive is used by a responder to specify the responder’s profile. The Responder Profile specifies the acceptable commands to which the responder will respond. It also specifies the response messages for each command, the baud rates at which to listen/respond and the number of times to retry a failed response before responding to the required Fast Connect XID command frame. The indication primitive indicates an IrLAP connection has been completed and provides the Device Address, Source- Device-Adr, of the station acting as the primary. The confirm primitive is returned on successful establishment of the connection and provides the Device Address, Destination-Device-Adr of the station acting as the secondary. After this, all primitives refer to the established connection by the ConnectionHandle.

Section 3.4

MODIFICATION

Add the following statement:

The responder (station sending the UA response) must generate a random connection address following the standard rules for connection addresses found in IrLAP version 1.1. The responder will use this connection address as the connection address in the UA response and it will be used by both stations for the duration of the IrLAP connection.

Also need to update the state chart with this information.

Rest of the Document

All references to the XID command frame will be modified to Fast Connect XID command frame and all references to the setMode service will be modified to setProfile. All references to the mode parameter of the setMode service will be removed.