The Secure Shell (SSH) Public Key File Format
RFC 4716
Yes
(Sam Hartman)
No Objection
(Bert Wijnen)
(Margaret Cullen)
(Russ Housley)
(Scott Hollenbeck)
(Ted Hardie)
Note: This ballot was opened for revision 13 and is now closed.
Sam Hartman Former IESG member
(was Discuss, Yes)
Yes
Yes
()
Unknown
Allison Mankin Former IESG member
No Objection
No Objection
(2005-09-29)
Unknown
Eyecatching typo: one it's 2nd-preimage resistance, not on it's collision- resistance.
Bert Wijnen Former IESG member
No Objection
No Objection
()
Unknown
Bill Fenner Former IESG member
No Objection
No Objection
(2005-09-29)
Unknown
It's not clear to the casual reader that understanding the referred section 6.6 of secsh-transport requires understanding section 5 of secsh-arch. If someone is just trying to implement the public key format and starts with publickeyfile, they will just see the relatively opaque "string", "mpint", etc. and not understand what those translate to in the actual file format.
Brian Carpenter Former IESG member
No Objection
No Objection
(2005-09-26)
Unknown
Joel Halpern noted in his Gen-ART review: ...given that it identifies two header names, and calls for IETF consensus for creating more, if this were a PS it would seem to require an IANA registry.
Margaret Cullen Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
(was Discuss)
No Objection
No Objection
()
Unknown
Scott Hollenbeck Former IESG member
(was Discuss)
No Objection
No Objection
()
Unknown
Ted Hardie Former IESG member
(was Discuss)
No Objection
No Objection
()
Unknown