Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)
draft-ietf-ipsec-esp-ah-algorithms-02
Yes
(Allison Mankin)
(Jon Peterson)
(Russ Housley)
No Objection
(Bert Wijnen)
(Bill Fenner)
(David Kessens)
(Scott Hollenbeck)
(Ted Hardie)
Note: This ballot was opened for revision 02 and is now closed.
Allison Mankin Former IESG member
Yes
Yes
()
Unknown
Jon Peterson Former IESG member
Yes
Yes
()
Unknown
Russ Housley Former IESG member
Yes
Yes
()
Unknown
Steven Bellovin Former IESG member
Yes
Yes
(2004-08-14)
Unknown
3.1.1 is actually rather odd -- there are no mandated confidentiality algorithms defined that are both required today and expected to be required in the near future.
Bert Wijnen Former IESG member
No Objection
No Objection
()
Unknown
Bill Fenner Former IESG member
No Objection
No Objection
()
Unknown
David Kessens Former IESG member
No Objection
No Objection
()
Unknown
Harald Alvestrand Former IESG member
No Objection
No Objection
(2004-08-19)
Unknown
Reviewed by Brian Carpenter, Gen-ART Personally, I think the use of SHOULD+ and MUST- are good additions to the repertoire of "conformance verbs". My preference would be to have the document mention an expected date for the conformance change (like "the first version emitted after January 2006, unless we learn something new"), but I can easily live with the document as written.
Margaret Cullen Former IESG member
No Objection
No Objection
(2004-08-18)
Unknown
Ideally the mandatory to implement algorithm of tomorrow should already be available in most implementations of IPSEC by the time it is made mandatory. s/IPSEC/IPsec If the security folks can't get this right, how can we expect the rest of us to do so? :-)
Scott Hollenbeck Former IESG member
No Objection
No Objection
()
Unknown
Ted Hardie Former IESG member
No Objection
No Objection
()
Unknown
Thomas Narten Former IESG member
(was Discuss)
No Objection
No Objection
(2004-08-19)
Unknown
s/IPSEC/IPsec/ throughout. s/mandatory to implement algorithms/mandatory-to-implement algorithms/ > a MAY or worse in a future version of this document. s/or worse/or weaker/ ?? 4 normative references to IDs; are those IDs done?