RE: [Hipsec] Rechartering items?

"Henderson, Thomas R" <thomas.r.henderson@boeing.com> Tue, 01 November 2005 17:52 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EX0JO-0006NE-DF; Tue, 01 Nov 2005 12:52:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EX0JJ-0006Fs-DN for hipsec@megatron.ietf.org; Tue, 01 Nov 2005 12:52:38 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04824 for <hipsec@ietf.org>; Tue, 1 Nov 2005 12:52:16 -0500 (EST)
Received: from stl-smtpout-01.boeing.com ([130.76.96.56]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EX0Xh-0002EZ-Ol for hipsec@ietf.org; Tue, 01 Nov 2005 13:07:32 -0500
Received: from stl-av-01.boeing.com ([192.76.190.6]) by stl-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id LAA03353; Tue, 1 Nov 2005 11:51:49 -0600 (CST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id jA1HpnY19483; Tue, 1 Nov 2005 11:51:49 -0600 (CST)
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); Tue, 1 Nov 2005 09:51:45 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
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] Rechartering items?
Date: Tue, 01 Nov 2005 09:51:44 -0800
Message-ID: <77F357662F8BFA4CA7074B0410171B6DC9E5B7@XCH-NW-5V1.nw.nos.boeing.com>
Thread-Topic: [Hipsec] Rechartering items?
Thread-Index: AcXe2LGyf5u5V57nTIGAeoOIr9PC5gAMOD4Q
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: Pekka Nikander <pekka.nikander@nomadiclab.com>, HIP <hipsec@ietf.org>
X-OriginalArrivalTime: 01 Nov 2005 17:51:45.0588 (UTC) FILETIME=[ECD48740:01C5DF0C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: quoted-printable
Cc: David Ward <dward@bgp.nu>
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>
Sender: hipsec-bounces@lists.ietf.org
Errors-To: hipsec-bounces@lists.ietf.org

 

> -----Original Message-----
> From: Pekka Nikander [mailto:pekka.nikander@nomadiclab.com] 
> Sent: Tuesday, November 01, 2005 2:53 AM
> To: HIP
> Cc: David Ward
> Subject: [Hipsec] Rechartering items?
> 
> Now that we have time for starting HIP WG re-chartering 
> discussion at our agenda next week, I'd like to hear people's 
> ideas of what should be the next items.  As far as I can see, 
> it may take a while before mobility and multi-homing 
> stabilises, so that might need to continue.  But other than that?
> 
> Some things that I would consider important:
> 
>   - making HIP to work with legacy NATs (and firewalls when feasible)

This topic has seen significant interest from the RG side, and in fact
there has been discussion in the RG that this topic might be a candidate
to push into the WG if there were charter interest there.  The RG
decided to make the following draft into a RG document-- it is a problem
statement discussing the problem of traversing legacy NATs and
firewalls:
http://www.ietf.org/internet-drafts/draft-irtf-hiprg-nat-00.txt

An implementation draft was worked on about a year ago, but it has since
expired.  I do not know of any implementation, although I have heard
that InfraHIP is working on it.
https://datatracker.ietf.org/public/idindex.cgi?command=id_detail&id=129
56

The RG is also considering solutions involving HIP-aware firewalls and
NATs, but IMO that type of work (as well as native HIP API) is not ready
for a WG.

> 
>   - invisible HIP, or using HIP with IP addresses as LSIs, similar to
> SHIM6 ULIDs
> 
A draft that discusses this topic is at:
http://www.ietf.org/internet-drafts/draft-henderson-hip-applications-01.
txt

It has not generated any mailing list or meeting discussion.  I was
thinking of submitting it to RFC Editor as an individual submission.
This topic is not one that necessarily involves interoperability, so I
would like to understand better what is left to do (as a possible WG
item) beyond the present draft.

> What else would be both important and mature enough for WG side work?
> 

The integration of SIP and HIP has received a lot of attention in the
RG, but I don't know whether there are any implementations:
i)
http://www.ietf.org/internet-drafts/draft-tschofenig-hiprg-hip-srtp-01.t
xt
ii)
http://www.ietf.org/internet-drafts/draft-tschofenig-hiprg-host-identiti
es-02.txt
iii)
http://www.ietf.org/internet-drafts/draft-papadoglou-hiprg-hit-presence-
00.txt

Tom

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