Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP)
draft-ietf-hip-rfc5202-bis-07

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

(Spencer Dawkins; former steering group member) Yes

Yes ( for -05)
No email
send info

(Ted Lemon; former steering group member) Yes

Yes ( for -05)
No email
send info

(Adrian Farrel; former steering group member) No Objection

No Objection ( for -05)
No email
send info

(Alissa Cooper; former steering group member) No Objection

No Objection ( for -05)
No email
send info

(Barry Leiba; former steering group member) No Objection

No Objection (2014-06-23 for -05)
No email
send info
-- Section 5.1.2 --

The table of suite IDs includes "NULL-ENCRYPT with HMAC-SHA-256", but NULL encryption is referred to as just "NULL" everywhere else in the document, as well as in RFC 2410.  Should the table be consistent with the text, or should there be an explanation of why it isn't?

(Benoît Claise; former steering group member) No Objection

No Objection ( for -05)
No email
send info

(Brian Haberman; former steering group member) No Objection

No Objection ( for -05)
No email
send info

(Jari Arkko; former steering group member) No Objection

No Objection ( for -05)
No email
send info

(Joel Jaeggli; former steering group member) No Objection

No Objection ( for -05)
No email
send info

(Kathleen Moriarty; former steering group member) No Objection

No Objection (2014-06-26 for -05)
No email
send info
I support Stephen's discuss

(Martin Stiemerling; former steering group member) (was Discuss) No Objection

No Objection ( for -05)
No email
send info

(Stephen Farrell; former steering group member) (was Discuss) No Objection

No Objection (2014-09-05)
No email
send info
Thanks for handling my discuss