RE: [Hipsec] Start re-chartering discussion in Vancouver?

"Henderson, Thomas R" <thomas.r.henderson@boeing.com> Thu, 02 March 2006 22:16 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FEw5p-0004ea-Or; Thu, 02 Mar 2006 17:16:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FEw5o-0004eG-Ef for hipsec@ietf.org; Thu, 02 Mar 2006 17:16:16 -0500
Received: from stl-smtpout-01.boeing.com ([130.76.96.56]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FEw5n-0008Br-5t for hipsec@ietf.org; Thu, 02 Mar 2006 17:16:16 -0500
Received: from blv-av-01.boeing.com ([192.42.227.216]) by stl-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id QAA22733; Thu, 2 Mar 2006 16:16:08 -0600 (CST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id k22MG7i28089; Thu, 2 Mar 2006 14:16:07 -0800 (PST)
Received: from XCH-NW-5V1.nw.nos.boeing.com ([130.247.55.44]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 2 Mar 2006 14:16:02 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Hipsec] Start re-chartering discussion in Vancouver?
Date: Thu, 02 Mar 2006 14:15:49 -0800
Message-ID: <77F357662F8BFA4CA7074B0410171B6D01A2EDD7@XCH-NW-5V1.nw.nos.boeing.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Hipsec] Start re-chartering discussion in Vancouver?
Thread-Index: AcY3iS31eBf4KoAERl2NCA2RRtJB8AGvQZqg
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: Lars Eggert <lars.eggert@netlab.nec.de>
X-OriginalArrivalTime: 02 Mar 2006 22:16:02.0557 (UTC) FILETIME=[E44DBAD0:01C63E46]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: hipsec-rg@honor.trusecure.com, HIP <hipsec@ietf.org>
X-BeenThere: hipsec@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/hipsec>
List-Post: <mailto:hipsec@lists.ietf.org>
List-Help: <mailto:hipsec-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@lists.ietf.org?subject=subscribe>
Errors-To: hipsec-bounces@lists.ietf.org

 

> -----Original Message-----
> From: Lars Eggert [mailto:lars.eggert@netlab.nec.de] 
> Sent: Wednesday, February 22, 2006 12:20 AM
> Cc: HIP
> Subject: Re: [Hipsec] Start re-chartering discussion in Vancouver?
> 
> Hi,
> 
> so we started the rechartering discussion in Vancouver, but 
> it didn't  
> carry over onto the mailing list. Has anyone started to put together  
> a revised charter proposal?
> 
> Lars

Pekka and I would like to propose that advancing the following
informational draft be considered as one of the new charter items.

Tom

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] 
Sent: Wednesday, March 01, 2006 12:50 PM
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-henderson-hip-applications-02.txt 

A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: Using HIP with Legacy Applications
	Author(s)	: T. Henderson, P. Nikander
	Filename	: draft-henderson-hip-applications-02.txt
	Pages		: 12
	Date		: 2006-3-1
	
The Host Identity Protocol and architecture (HIP) proposes to add a
cryptographic name space for network stack names.  From an
application viewpoint, HIP-enabled systems support a new address
family (e.g., AF_HOST), 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.

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

_______________________________________________
Hipsec mailing list
Hipsec@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/hipsec