mirror of
https://github.com/espressif/openthread.git
synced 2026-09-14 21:20:11 +00:00
[devsite] add clarifications to multicast addressing primer (#5160)
This commit is contained in:
@@ -226,10 +226,12 @@ Key Point: A major difference between FTDs and MTDs are that FTDs subscribe to
|
|||||||
the `ff03::2` multicast address. MTDs do not.
|
the `ff03::2` multicast address. MTDs do not.
|
||||||
|
|
||||||
You might notice that Sleepy End Devices (SEDs) are not included as a
|
You might notice that Sleepy End Devices (SEDs) are not included as a
|
||||||
recipient in the multicast table above. There is an additional unicast
|
recipient in the multicast table above. Instead, Thread defines
|
||||||
prefix-based multicast address used for All Thread Nodes, including SEDs. This
|
link-local and realm-local scope unicast prefix-based IPv6 multicast
|
||||||
multicast address varies by Thread network, because it is built on the
|
address used for All Thread Nodes, including SEDs. These multicast
|
||||||
unicast Mesh-Local prefix.
|
addresses vary by Thread network, because it is built on the unicast
|
||||||
|
Mesh-Local prefix (see [RFC 3306](https://tools.ietf.org/html/rfc3306)
|
||||||
|
for more details on unicast-prefix-based IPv6 multicast addresses).
|
||||||
|
|
||||||
Arbitrary scopes beyond those already listed are also supported for Thread
|
Arbitrary scopes beyond those already listed are also supported for Thread
|
||||||
devices.
|
devices.
|
||||||
|
|||||||
@@ -50,8 +50,9 @@ An FTD can operate as a Router (Parent) or an End Device (Child).
|
|||||||
|
|
||||||
### Minimal Thread Device
|
### Minimal Thread Device
|
||||||
|
|
||||||
A Minimal Thread Device does not subscribe to multicast traffic and forwards all
|
A Minimal Thread Device does not subscribe to the all-routers
|
||||||
messages to its Parent. There are two types of MTDs:
|
multicast address and forwards all messages to its Parent. There are
|
||||||
|
two types of MTDs:
|
||||||
|
|
||||||
* Minimal End Device (MED) — transceiver always on, does not need to poll for
|
* Minimal End Device (MED) — transceiver always on, does not need to poll for
|
||||||
messages from its parent
|
messages from its parent
|
||||||
|
|||||||
Reference in New Issue
Block a user