Using the Host Identity Protocol with Legacy Applications
draft-ietf-hip-applications-04

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: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    hip mailing list <hipsec@ietf.org>, 
    hip chair <hip-chairs@tools.ietf.org>
Subject: Document Action: 'Using the Host Identity Protocol with 
         Legacy Applications' to Experimental RFC 

The IESG has approved the following document:

- 'Using the Host Identity Protocol with Legacy Applications '
   <draft-ietf-hip-applications-05.txt> as an Experimental RFC

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

The IESG contact persons are Mark Townsley and Jari Arkko.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-hip-applications-05.txt

Ballot Text

Technical Summary

The Host Identity Protocol (HIP) and architecture proposes to add a
cryptographic name space for network stack names. From an
application viewpoint, HIP-enabled systems support a new address
family of host identifiers, but it may be a long time until such HIP-
aware applications are widely deployed even if host systems are
upgraded. This informational document discusses implementation and
API issues relating to using HIP in situations in which the system is
HIP-aware but the applications are not.


Working Group Summary

Was there anything in WG process that is worth noting? For
example, was there controversy about particular points or
were there decisions where the consensus was particularly
rough?

No.

Document Quality

This document is based on the experiences of several HIP implementors.

The Document PROTO Shepherd is Gonzalo Camarillo

RFC Editor Note