-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi, Sam,
Sam Hartman wrote:
I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG. These comments were written primarily for the benefit of the
security area directors. Document editors and WG chairs should treat
these comments just like any other last call comments.
...
Section 8 proposes that AH is the mandatory-to-implement security
mechanism for this option. Do we still believe that is
appropriate given RFC 4301's move away from AH as a
mandatory-to-implement service?
I was wondering about that; it seems inconsistent to have this document
require something that is optional in RFC 4301.
Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkjlBj0ACgkQE5f5cImnZrt/3gCdH5b4r0ClHZYPrIrHoWO4znVT
Kk4AnReHumU/rH+cxvA/+7gTdpNxncgK
=/GpO
-----END PGP SIGNATURE-----
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf