…th a tunnel protocol, providing that the method satisfies the requirements in [ RFC6936 ]. The application MUST implement mechanisms and/or usage restrictions when enabling this mode. This includes defining the scope for usage and measures to prevent leakage of traffic to other U…
…puted for IPv4 and IPv6. (See [ RFC0768 ] regarding IPv4; see [ RFC2460 ] and [ RFC6936 ] regarding IPv6.) Although UDP with a zero checksum over IPv6 is allowed under certain constraints [ RFC6936 ], this document does not specify mechanisms for this mode. Deployed support may b…
… undermined when using UDP as a tunnel with no UDP checksum (as per [ RFC6935 ][RFC6936]) when fragmentation occurs because the egress has no checksum with which to validate reassembly. For this reason, it is safe to use UDP with a zero checksum for atomic tunnel link packets onl…
…ich is out of this document's scope. (UDP-lite [RFC3828] and UDP zero checksum [RFC6936] are not supported by CoAP.) CoAP messages are encoded in a simple binary format. The message format starts with a fixed-size 4-byte header. This is followed by a variable-length Token value, …
…Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums" [RFC6936]. It should say: Middleboxes supporting IPv6 MUST follow requirements 8, 9, and 10 of the usage requirements specified in Section 5 of "Applicability Statement for the Use of IPv6 UDP Datagram…
…Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums" [RFC6936]. It should say: Middleboxes supporting IPv6 MUST follow requirements 8, 9, and 10 of the usage requirements specified in Section 5 of "Applicability Statement for the Use of IPv6 UDP Datagram…