Enhanced Security Services (ESS) Update: Adding CertID Algorithm Agility
RFC 5035

Note: This ballot was opened for revision 06 and is now closed.

(Russ Housley) Yes

(Tim Polk) Yes

(Jari Arkko) No Objection

(Ron Bonica) No Objection

(Ross Callon) No Objection

(Lisa Dusseault) No Objection

(Lars Eggert) No Objection

(Sam Hartman) No Objection

(Cullen Jennings) No Objection

(Chris Newman) (was Discuss, No Objection, Discuss) No Objection

Comment (2007-05-10)
No email
send info
Shouldn't section 6 mention that the hash algorithm in the certHash field of ESSCertID (v1) is SHA-1?  Perhaps this could be fixed with a simple RFC Editor note?

Given one of the purposes of this change is to introduce hash function agility, should there be a discussion of that in section 7?  Perhaps an informative reference to RFC 4270 and a caution that implementations plan ahead for algorithm changes?

(Jon Peterson) No Objection

(Dan Romascanu) No Objection

(David Ward) No Objection

Magnus Westerlund No Objection