…ypted IP and TCP packet header (e.g., no use of IPSec with payload encryption [ RFC2406 ]). (ii) Knowledge of IP/TCP options and ability to inspect packets with tunnel encapsulations (e.g., [ RFC2784 ]) or to suspend processing of packets with unknown formats. (iii) Ability to de…

…use is similar to the Sequence Number field defined in the IPsec ESP protocol [ RFC2406 ]. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ! Next Payload ! RESERVED ! Payload Length ! +-+-+-…

… more involved. Consequently, off-the-shelf solutions (e.g., taken from IPsec [ RFC2406 ]) may be sufficient for encryption and group authentication. For source authentication, however, special-purpose transformations are necessary. See [ CCPRRS ] for further elaboration on the c…

…Kent, S. and R. Atkinson, "IP Authentication Header", RFC 2401, November 1998. [RFC2406] Kent, S. and R. Atkinson, "IP Encapsulating Security Payload (ESP)", RFC 2401, November 1998. It should say: [RFC2402] Kent, S. and R. Atkinson, "IP Authentication Header", RFC 2402, November…

…Kent, S. and R. Atkinson, "IP Authentication Header", RFC 2401, November 1998. [RFC2406] Kent, S. and R. Atkinson, "IP Encapsulating Security Payload (ESP)", RFC 2401, November 1998. It should say: [RFC2402] Kent, S. and R. Atkinson, "IP Authentication Header", RFC 2402, November…