…he TCP/IP checksum is inside the UDP encapsulated IPsec packet.) The document [ RFC3948 ] describes the details of UDP encapsulation, and [ RFC3715 ] provides background information and motivation of NAT- Traversal in general. In combination with [ RFC3948 ], this document repres…

…mally detect the presence of the translator and encapsulate ESP in UDP packets [RFC3948]. 9. References 9.1. Normative References [RFC768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, DOI 10.17487/RFC0768, August 1980, <http://www.rfc-editor.org/info/rfc768>. [RFC791] Po…

…ally detect the presence of the translator and encapsulate ESP in UDP packets [ RFC3948 ]. 9 . References 9.1 . Normative References [ RFC768 ] Postel, J., "User Datagram Protocol", STD 6, RFC 768 , DOI 10.17487/RFC0768, August 1980, < http://www.rfc-editor.org/info/rfc768 >. [ R…

…ally detect the presence of the translator and encapsulate ESP in UDP packets [ RFC3948 ]. 9 . References 9.1 . Normative References [ RFC768 ] Postel, J., "User Datagram Protocol", STD 6, RFC 768 , DOI 10.17487/RFC0768, August 1980, < http://www.rfc-editor.org/info/rfc768 >. [ R…

… be added that explains which fields are updated similar to what is done in the RFC3948: The Total Length, Protocol, and Header Checksum (for IPv4) fields in the IP header are edited to match the resulting IP packet. As ESP is still used the IPsecME WG might want to make a RFC430…

… be added that explains which fields are updated similar to what is done in the RFC3948: The Total Length, Protocol, and Header Checksum (for IPv4) fields in the IP header are edited to match the resulting IP packet. As ESP is still used the IPsecME WG might want to make a RFC430…