[riot-notifications] [RIOT-OS/RIOT] gnrc_ipv6_ext_opt: initial import (#13275)

Martine Lenders notifications at github.com
Mon May 11 14:23:43 CEST 2020


@miri64 commented on this pull request.



> +/** @} */
+
+/**
+ * @name Processing actions
+ * @see [RFC 8200, section 4.2](https://tools.ietf.org/html/rfc8200#section-4.2)
+ * @{
+ */
+/**
+ * @brief   mask to decode action from type
+ */
+#define IPV6_EXT_OPT_ACTION_MASK            (0xc0)
+/**
+ * @brief   skip over this option and continue processing the header
+ */
+#define IPV6_EXT_OPT_ACTION_SKIP            (0x00)
+#define IPV6_EXT_OPT_ACTION_DISC            (0x40)  /**< discard the packet */

The link in the comment explains how this works: If the handling of an option is not supported by the router, it should handle the packet in accordance to the action bits. So yes, options that indicate that the packet should be discarded, if the first is not supported, the router discards the packet. Those action bits are intrinsic to the option's ID (see [IANA registry](https://www.iana.org/assignments/ipv6-parameters/ipv6-parameters.xhtml#ipv6-parameters-2)), so these bits can't just be picked by the sender at will, but are bound to the options they add to the packet.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/13275#discussion_r423000526
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20200511/6f40bc37/attachment-0001.htm>


More information about the notifications mailing list