[Hipsec] Document Action: 'Host Identity Protocol (HIP) Multi-hop Routing Extension' to Experimental RFC
The IESG <iesg-secretary@ietf.org> Mon, 19 July 2010 16:14 UTC
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: hipsec@ietf.org
Delivered-To: hipsec@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id B631E3A6B35; Mon, 19 Jul 2010 09:14:12 -0700 (PDT)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <20100719161412.B631E3A6B35@core3.amsl.com>
Date: Mon, 19 Jul 2010 09:14:12 -0700
X-Mailman-Approved-At: Thu, 22 Jul 2010 00:06:30 -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: 'Host Identity Protocol (HIP) Multi-hop Routing Extension' 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/mail-archive/web/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>
X-List-Received-Date: Mon, 19 Jul 2010 16:14:12 -0000
The IESG has approved the following document: - 'Host Identity Protocol (HIP) Multi-hop Routing Extension ' <draft-ietf-hip-via-03.txt> as an Experimental RFC This document is the product of the Host Identity Protocol Working Group. The IESG contact persons are Ralph Droms and Jari Arkko. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hip-via-03.txt Technical Summary This document specifies two extensions to HIP to implement multi-hop routing. The first extension allows implementing source routing in HIP. That is, a host sending a HIP packet can define a set of hosts that the HIP packet should traverse. The second extension allows a HIP packet to carry and record the list of hosts that forwarded it. Working Group Summary There was strong consensus on this document. Document Quality There are prototype implementations of this spec. A few vendors have expressed interest in implementing this in the context of HIP BONE overlays. Personnel David Ward is the document shepherd for this document. Ralph Droms is the responsible AD for this document.