Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP)
draft-ietf-hip-rfc5202-bis-07
Yes
(Spencer Dawkins)
(Ted Lemon)
No Objection
(Adrian Farrel)
(Alissa Cooper)
(Benoît Claise)
(Brian Haberman)
(Jari Arkko)
(Joel Jaeggli)
(Martin Stiemerling)
Note: This ballot was opened for revision 05 and is now closed.
Spencer Dawkins Former IESG member
Yes
Yes
(for -05)
Unknown
Ted Lemon Former IESG member
Yes
Yes
(for -05)
Unknown
Adrian Farrel Former IESG member
No Objection
No Objection
(for -05)
Unknown
Alissa Cooper Former IESG member
No Objection
No Objection
(for -05)
Unknown
Barry Leiba Former IESG member
No Objection
No Objection
(2014-06-23 for -05)
Unknown
-- 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 IESG member
No Objection
No Objection
(for -05)
Unknown
Brian Haberman Former IESG member
No Objection
No Objection
(for -05)
Unknown
Jari Arkko Former IESG member
No Objection
No Objection
(for -05)
Unknown
Joel Jaeggli Former IESG member
No Objection
No Objection
(for -05)
Unknown
Kathleen Moriarty Former IESG member
No Objection
No Objection
(2014-06-26 for -05)
Unknown
I support Stephen's discuss
Martin Stiemerling Former IESG member
(was Discuss)
No Objection
No Objection
(for -05)
Unknown
Stephen Farrell Former IESG member
(was Discuss)
No Objection
No Objection
(2014-09-05)
Unknown
Thanks for handling my discuss