Basic Socket Interface Extensions for the Host Identity Protocol (HIP)
RFC 6317

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

(Ralph Droms) Yes

(Jari Arkko) No Objection

(Ron Bonica) No Objection

(Ross Callon) No Objection

(Lars Eggert) (was Discuss) No Objection

(Pasi Eronen) (was Discuss) No Objection

(Adrian Farrel) No Objection

Comment (2009-12-01 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
Acronyms used ahead of section 2.
LSI
HIP (Expanded in second paragraph of section 1; used in first paragraph)

---

Acronyms used without expansion
FQDN
RR
HI

---

Might be nice to describe the "experiment" in a little more detail. In 
particular, how will you judge the success of the experiment?

---

Figure 2
Stray character at the start of the ship_hit line.

(Russ Housley) No Objection

Comment (2009-12-02 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
  Several editorial improvements were suggested in the Gen-ART Review
  by Ben Campbell.  Please consider them.

(Cullen Jennings) (was Discuss, No Objection) No Objection

(Alexey Melnikov) No Objection

Comment (2009-11-28 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
A good document. Some examples would be nice though.

Also:

10.  Normative References

   [I-D.ietf-btns-c-api]
              Richardson, M., Williams, N., Komu, M., and S. Tarkoma,
              "C-Bindings for IPsec Application Programming Interfaces",
              draft-ietf-btns-c-api-04 (work in progress), March 2009.

   [I-D.ietf-shim6-proto]
              Nordmark, E. and M. Bagnulo, "Shim6: Level 3 Multihoming
              Shim Protocol for IPv6", draft-ietf-shim6-proto-12 (work
              in progress), February 2009.

The above references look Informative to me.

(Tim Polk) (was No Record, Discuss) No Objection

(Dan Romascanu) No Objection

(Robert Sparks) (was Discuss) No Objection

Comment (2009-12-01)
No email
send info
Per 
http://www.iana.org/assignments/iana-ipv6-special-registry/
ORCHIDs currently have a default sunset in 2014:

2001:10::/28    ORCHID      21 Mar 07        21 Mar 14         Overlay       See RFC             Not Routed     [RFC4843]

Should this document ask an implementor to check to see if that's been
updated? (What will maintenance of the stream look like if something unexpected happens and this ORCHID assignment is not renewed?)

Magnus Westerlund No Objection