[Hipsec] Document Action: 'Using the Host Identity Protocol with Legacy Applications' to Experimental RFC
The IESG <iesg-secretary@ietf.org> Thu, 31 July 2008 06:58 UTC
Return-Path: <hipsec-bounces@ietf.org>
X-Original-To: hip-archive@lists.ietf.org
Delivered-To: ietfarch-hip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AAD4D3A6C21; Wed, 30 Jul 2008 23:58:40 -0700 (PDT)
X-Original-To: hipsec@ietf.org
Delivered-To: hipsec@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id F152128C114; Fri, 25 Jul 2008 02:47:25 -0700 (PDT)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <20080725094725.F152128C114@core3.amsl.com>
Date: Fri, 25 Jul 2008 02:47:25 -0700
X-Mailman-Approved-At: Wed, 30 Jul 2008 23:58:38 -0700
Cc: hip mailing list <hipsec@ietf.org>, Internet Architecture Board <iab@iab.org>, hip chair <hip-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Hipsec] Document Action: 'Using the Host Identity Protocol with Legacy Applications' to Experimental RFC
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: hipsec-bounces@ietf.org
Errors-To: hipsec-bounces@ietf.org
The IESG has approved the following document: - 'Using the Host Identity Protocol with Legacy Applications ' <draft-ietf-hip-applications-04.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-04.txt 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 _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec