... | ... | @@ -35,12 +35,26 @@ A transport record describes how to connect to a device over a short-range trans |
|
|
|
|
|
The following transports have been defined so far:
|
|
|
|
|
|
**0: Bluetooth** - The device registers a Bluetooth service to accept RFCOMM connections. The service UUID is generated by converting the first 16 bytes of the public key commitment into a UUID as specified in section 4.4 of [RFC 4122](https://tools.ietf.org/html/rfc4122). The record body consists of one chunk containing the device's Bluetooth MAC address (6 bytes).
|
|
|
**0: Bluetooth** - The device registers a Bluetooth service to accept RFCOMM connections. The service UUID is generated by converting the first 16 bytes of the public key commitment into a UUID as specified in section 4.4 of [RFC 4122](https://tools.ietf.org/html/rfc4122). The record body contains one chunk:
|
|
|
|
|
|
**1: LAN** - The device connects to a local area network and opens a port to accept TCP connections. The record body consists of two chunks: (i) the device's link-local or site-local IPv4 or IPv6 address (4 or 16 bytes); (ii) the port number as a 16-bit integer (2 bytes).
|
|
|
* The device's Bluetooth MAC address (6 bytes)
|
|
|
|
|
|
**2: Wi-Fi** - The device connects to a Wi-Fi network and opens a port to accept TCP connections. The record body consists of three chunks: (i) the device's link-local or site-local IPv4 or IPv6 address (4 or 16 bytes); (ii) the port number as a 16-bit integer (2 bytes); (iii) the SSID of the Wi-Fi network (variable length).
|
|
|
**1: LAN** - The device connects to a local area network and opens a port to accept TCP connections. The record body contains two chunks:
|
|
|
|
|
|
**3: Wi-Fi Direct** - The device creates a Wi-Fi Direct legacy mode access point and opens a port to accept TCP connections. The record body consists of four chunks: (i) the device's link-local or site-local IPv4 or IPv6 address (4 or 16 bytes); (ii) the port number as a 16-bit integer (2 bytes); (iii) the SSID of the access point (variable length); (iv) the password of the access point (variable length).
|
|
|
* The device's link-local or site-local IPv4 or IPv6 address (4 or 16 bytes)
|
|
|
* The port number as a 16-bit integer (2 bytes)
|
|
|
|
|
|
This list of transports may be extended in future without incrementing the protocol version; devices must ignore any transports they do not recognise. |
|
|
**2: Wi-Fi** - The device connects to a Wi-Fi network and opens a port to accept TCP connections. The record body contains three chunks:
|
|
|
|
|
|
* The device's link-local or site-local IPv4 or IPv6 address (4 or 16 bytes)
|
|
|
* The port number as a 16-bit integer (2 bytes)
|
|
|
* The SSID of the Wi-Fi network (variable length)
|
|
|
|
|
|
**3: Wi-Fi Direct** - The device creates a Wi-Fi Direct legacy mode access point and opens a port to accept TCP connections. The record body contains four chunks:
|
|
|
|
|
|
* The device's link-local or site-local IPv4 or IPv6 address (4 or 16 bytes)
|
|
|
* The port number as a 16-bit integer (2 bytes)
|
|
|
* The SSID of the access point (variable length)
|
|
|
* The password of the access point (variable length)
|
|
|
|
|
|
New transports may be defined in future without incrementing the protocol version; devices must ignore any transports they do not recognise. |