3 Protocol Details

As described in section 1.3, this protocol defines the following roles:

  • Enumerator: This role MAY<6> be supported by implementations of this protocol.

  • Mapper: This role MAY<7> be supported by implementations of this protocol. If supported, the implementation MUST also support the Enumerator role.

  • QoS Controller: This role MAY<8> be supported by implementations of this protocol. If supported, the implementation MUST also support the Enumerator role.

  • Cross-Traffic Analysis Initiator: This role MAY<9> be supported by implementations of this protocol. If supported, the implementation MUST also support the Enumerator role.

  • Responder (Quick Discovery): This role MUST be supported by implementations of this protocol.

  • Responder (Topology Discovery): This role MUST be supported by implementations of this protocol.

  • QoS Sink: This role MUST be supported by implementations of this protocol.

  • Responder (QoS Cross-Traffic): This role MUST be supported by implementations of this protocol.

Each role is described in the following sections.

An implementation MUST be able to execute all roles that it supports at the same time, but only as allowed by the following limitations and dependencies among the different roles:

  • An initiator (enumerator, mapper, QoS controller, or Cross-Traffic Analysis initiator) MUST at the same time act as responder (Quick Discovery, Topology Discovery, QoS Sink, or QoS Cross-Traffic).

  • All responder roles MUST be able to execute simultaneously, with the exception that the state machine of the Quick Discovery responder impacts the Topology Discovery as specified in the corresponding sections (see specification of Session Table in sections 3.5.1 and 3.6.1). Specifically, the Topology Discovery responder is associated with the mapper that is selected by the Quick Discovery responder as the current mapper (see section 3.5.5.1).

This specification covers processing rules for error conditions, such as out-of-memory conditions, to ensure that all roles maintain a consistent state. However, error conditions in one role might impact the functionality of other roles, including the ability to discover all LLTD-capable stations on the network.

Show: