Module rustun::message

STUN messages.

STUN is a client-server protocol. It supports two types of transactions. One is a request/response transaction in which a client sends a request to a server, and the server returns a response. The second is an indication transaction in which either agent – client or server – sends an indication that generates no response. Both types of transactions include a transaction ID, which is a randomly selected 96-bit number. For request/response transactions, this transaction ID allows the client to associate the response with the request that generated it; for indications, the transaction ID serves as a debugging aid.

All STUN messages start with a fixed header that includes a method, a class, and the transaction ID. The method indicates which of the various requests or indications this is; this specification defines just one method, Binding, but other methods are expected to be defined in other documents. The class indicates whether this is a request, a success response, an error response, or an indication. Following the fixed header comes zero or more attributes, which are Type-Length-Value extensions that convey additional information for the specific message.

RFC 5389 – 3. Overview of Operation

Structs

• ErrorResponse
  Error response message.
• Indication
  Indication message.
• InvalidMessage
  Invalid message.
• MessageError
  Message level error.
• Request
  Request message.
• SuccessResponse
  Success response message.

Enums

• MessageErrorKind
  Possible error kinds.

Type Aliases

• MessageResult
  A specialized Result type for message-level operations.
• Response
  Response message.