Host Identity Protocol-Based Overlay Networking Environment (HIP BONE) Instance Specification for REsource LOcation And Discovery (RELOAD)
draft-ietf-hip-reload-instance-10

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: RFC Editor <rfc-editor@rfc-editor.org>,
    hip mailing list <hipsec@ietf.org>,
    hip chair <hip-chairs@tools.ietf.org>
Subject: Document Action: 'Host Identity Protocol-Based Overlay Networking Environment (HIP BONE) Instance Specification for REsource LOcation And Discovery (RELOAD)' to Experimental RFC (draft-ietf-hip-reload-instance-10.txt)

The IESG has approved the following document:
- 'Host Identity Protocol-Based Overlay Networking Environment (HIP BONE)
   Instance Specification for REsource LOcation And Discovery (RELOAD)'
  (draft-ietf-hip-reload-instance-10.txt) as Experimental RFC

This document is the product of the Host Identity Protocol Working Group.

The IESG contact persons are Ted Lemon and Brian Haberman.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-hip-reload-instance/

Ballot Text

Technical Summary:

This document is the Host Identity Protocol-Based Overlay Networking
Environment (HIP BONE) instance specification for the REsource
LOcation And Discovery (RELOAD) protocol.  The document provides the
details needed to build a RELOAD-based overlay that uses HIP.


Working Group Summary:

There is WG consensus behind this draft. The WG actively worked on
this draft at the same time as RELOAD was being developed (this draft
was also discussed in the P2PSIP WG, where RELOAD was developed, so
that RELOAD had enough hooks to be able to run with HIP). This draft
was put on hold when the RELOAD specification got stuck (for a long
time) during its IESG review. Now that RELOAD has been published, this
spec can be published as well (RELOAD is, obviously, an essential
dependency for this draft).


Document Quality:

There is at least one implementation of this draft. The delay in the
publication of RELOAD has a negative impact in the number of people
implementing RELOAD-related specs. Nevertheless, now that RELOAD has
been published, the interest seems to be growing again.


Personnel:

Who is the Document Shepherd? Who is the Responsible Area Director?

Miika Komu is the document shepherd.
Ted Lemon is the responsible AD.

RFC Editor Note