The Secure Shell (SSH) Public Key File Format
RFC 4716

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

(Sam Hartman; former steering group member) (was Discuss, Yes) Yes

Yes ()
No email
send info

(Allison Mankin; former steering group member) No Objection

No Objection (2005-09-29 for -)
No email
send info
Eyecatching typo:

   one it's 2nd-preimage resistance, not on it's collision-
   resistance.

(Bert Wijnen; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Bill Fenner; former steering group member) No Objection

No Objection (2005-09-29 for -)
No email
send info
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 steering group member) No Objection

No Objection (2005-09-26 for -)
No email
send info
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 steering group member) No Objection

No Objection ( for -)
No email
send info

(Russ Housley; former steering group member) (was Discuss) No Objection

No Objection ()
No email
send info

(Scott Hollenbeck; former steering group member) (was Discuss) No Objection

No Objection ()
No email
send info

(Ted Hardie; former steering group member) (was Discuss) No Objection

No Objection ()
No email
send info