…nisms have been defined by the IETF, such as those defined in [ RFC6146 ] and [ RFC7915 ]. These mechanisms target various different use cases. An operator might therefore wish to make use of several of them simultaneously. The WKP is reserved specifically for use with the algori…

…nisms have been defined by the IETF, such as those defined in [ RFC6146 ] and [ RFC7915 ]. These mechanisms target various different use cases. An operator might therefore wish to make use of several of them simultaneously. The WKP is reserved specifically for use with the algori…

…how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7915. Copyright Notice Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provision…

… alternate behavior and MUST NOT do anything else for the reasons detailed in [ RFC7915 ] . The TURN server solely relies on the DF bit in the IPv4 header and the Fragment header in the IPv6 header to handle fragmentation using the approach described in [ RFC7915 ] and does not r…

…y IPv4 UDP datagrams where the checksum is zero as described in Section 4.5 of [RFC7915]. Notes: Also add normative reference to RFC 7915 in the references section. --- Verifier note (Éric Vyncke) --- The appended text is correct (as verified in real life deployments), but does n…

…y IPv4 UDP datagrams where the checksum is zero as described in Section 4.5 of [RFC7915]. Notes: Also add normative reference to RFC 7915 in the references section. --- Verifier note (Éric Vyncke) --- The appended text is correct (as verified in real life deployments), but does n…