search

zephyriot / zephyr-issues

0 stars 0 forks source link

Thread requirements in RFC4291 #781

Open nashif opened 8 years ago

nashif commented 8 years ago

Reported by Gajinder Vij:

The Thread Protocol imposes the following requirements on RFC4291: RFC4291.2: IPv6 Addressing RFC4291.2.1: Addressing Model RFC4291.2.2: Text Representation of Addresses RFC4291.2.3: Text Representation of Address Prefixes RFC4291.2.4: Address Type Identification RFC4291.2.5: Unicast Addresses RFC4291.2.5.1: Interface Identifiers RFC4291.2.5.2: The Unspecified Address RFC4291.2.5.3: The Loopback Address RFC4291.2.5.4: Global Unicast Addresses RFC4291.2.5.6: Link-Local IPv6 Unicast Addresses RFC4291.2.6: Anycast Addresses RFC4291.2.8: A Node�s Required Addresses � Note: A Node MAY recognize the loopback address RFC4291.2.6.1: Required Anycast Address RFC4291.2.7: Multicast Addresses RFC4291.2.7.1: Pre-Defined Multicast Addresses

(Imported from Jira ZEP-836)

nashif commented 7 years ago

by Jukka Rissanen:

While we likely have most of underlying enablers done for 1.7, the verification is still pending.

nashif commented 7 years ago

by ethan gao:

This is protocol base for upper Thread, and marked it as "Testable" to check from Thread application layer once Thread protocol implemented in Zephyr

nashif commented 7 years ago

by Andrei Laperie:

This item will be indirectly verified by Thread implementation, which is targeted past 1.7

nashif commented 7 years ago

by Mark Linkmeyer:

Per feedback from Andrei on its status and per review with Anas, this story will not make it into 1.8 so it's being removed from the list of stories planned for 1.8. Andrei to break up the story, as needed.

nashif commented 7 years ago

Related to GH-785