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

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

Lars Eggert No Objection

(Russ Housley; former steering group member) Yes

Yes ()
No email
send info

(Tim Polk; former steering group member) Yes

Yes ()
No email
send info

(Chris Newman; former steering group member) (was Discuss, No Objection, Discuss) No Objection

No Objection (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?

(Cullen Jennings; former steering group member) No Objection

No Objection ()
No email
send info

(Dan Romascanu; former steering group member) No Objection

No Objection (2007-05-08)
No email
send info

(David Ward; former steering group member) No Objection

No Objection ()
No email
send info

(Jari Arkko; former steering group member) No Objection

No Objection ()
No email
send info

(Jon Peterson; former steering group member) No Objection

No Objection ()
No email
send info

(Lisa Dusseault; former steering group member) No Objection

No Objection ()
No email
send info

(Magnus Westerlund; former steering group member) No Objection

No Objection ()
No email
send info

(Ron Bonica; former steering group member) No Objection

No Objection ()
No email
send info

(Ross Callon; former steering group member) No Objection

No Objection ()
No email
send info

(Sam Hartman; former steering group member) No Objection

No Objection ()
No email
send info