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

(Stephen Farrell) Yes

(Ron Bonica) No Objection

(Stewart Bryant) No Objection

(Gonzalo Camarillo) No Objection

(Benoît Claise) No Objection

(Ralph Droms) (was Discuss) No Objection

Thank you for addressing the issues in my previous Discuss position.

Figures 9 and 10 contain minor typos, including the capitalization
of "cryptosuite" and missing " " (space characters) that affect
the alignment of the ASCII-art.

(Wesley Eddy) No Objection

(Adrian Farrel) No Objection

I have no objection to thepublication of this document.

Please supply a short section "Changes from RFC 5296"

Pleasecheck that all Erratahave also been applied to this revision
http://www.rfc-editor.org/errata_search.php?rfc=5296

(Brian Haberman) No Objection

(Russ Housley) No Objection

(Barry Leiba) (was Discuss) No Objection

[Updated 17 May 2012, to clear my DISCUSS after the posting of -07.]

Glen,
Thanks for including my text for the IANA Considerations; I'm clearing my DISCUSS.

In section 10, I would have thought
   s/insisted/stamped his foot petulantly and insisted/
so thanks for your restraint.  In any case, I'm happy to stand behind what's in section 9.

In section 11, the backhanded compliment to your colleagues, "(mostly)", is quite unnecessary.

(Pete Resnick) No Objection

Pedantic nits:

4.1 (and similarly in 4.3 and 4.6):

   The rIK Label is the 8-bit ASCII string:

What is an "8-bit ASCII string"? Do you mean "the following string of US-ASCII characters encoded in octets" or something like that?

5.2 (also 5.3.2 and 5.3.3):

      a 16-bit sequence number

Any issue about byte order or sign/unsigned with these?

5.3.3:

         The value
         field is a 32-bit field and contains the lifetime of the [...] in
         seconds.
         
Again, any issue with byte order or sign/unsigned with these?

(Robert Sparks) No Objection

(Sean Turner) No Objection

Nice job folks.  Only nits:

s3.2: r/5shows/5 shows
s4.1: 4th bullet r/must/MUST ?