<Dt> Integrity Check Value (multiple of 32 bits) </Dt> <Dd> Variable length check value . It may contain padding to align the field to an 8 - octet boundary for IPv6, or a 4 - octet boundary for IPv4 . </Dd> <P> The IP Encapsulating Security Payload (ESP) was researched at the Naval Research Laboratory starting in 1992 as part of a DARPA - sponsored research project, and was openly published by IETF SIPP Working Group drafted in December 1993 as a security extension for SIPP . This ESP was originally derived from the US Department of Defense SP3D protocol, rather than being derived from the ISO Network - Layer Security Protocol (NLSP). The SP3D protocol specification was published by NIST in the late 1980s, but designed by the Secure Data Network System project of the US Department of Defense . Encapsulating Security Payload (ESP) is a member of the IPsec protocol suite . It provides origin authenticity through source authentication, data integrity through hash functions and confidentiality through encryption protection for IP packets . ESP also supports encryption - only and authentication - only configurations, but using encryption without authentication is strongly discouraged because it is insecure . </P> <P> Unlike Authentication Header (AH), ESP in transport mode does not provide integrity and authentication for the entire IP packet . However, in Tunnel Mode, where the entire original IP packet is encapsulated with a new packet header added, ESP protection is afforded to the whole inner IP packet (including the inner header) while the outer header (including any outer IPv4 options or IPv6 extension headers) remains unprotected . ESP operates directly on top of IP, using IP protocol number 50 . </P>

What is encapsulating security payload (esp)
find me the text answering this question