RE: [EME] Traversing HIP-aware NATs and Firewalls: Problem Statement andRequirements

Paul Francis <francis@cs.cornell.edu> Mon, 18 June 2007 21:30 UTC

Return-path: <eme-bounces@irtf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I0Oo4-0007GM-Pp; Mon, 18 Jun 2007 17:30:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I0Oo4-0007GH-9l for eme@irtf.org; Mon, 18 Jun 2007 17:30:40 -0400
Received: from mail-hub-1.cs.cornell.edu ([128.84.103.138] helo=exch-hub1.cs.cornell.edu) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0Oo2-0003RA-R4 for eme@irtf.org; Mon, 18 Jun 2007 17:30:40 -0400
Received: from exchfe1.cs.cornell.edu (128.84.97.33) by mail-hub.cs.cornell.edu (128.84.103.140) with Microsoft SMTP Server id 8.0.700.0; Mon, 18 Jun 2007 17:30:38 -0400
Received: from EXCHANGE2.cs.cornell.edu ([128.84.96.44]) by exchfe1.cs.cornell.edu with Microsoft SMTPSVC(6.0.3790.1830); Mon, 18 Jun 2007 17:24:19 -0400
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: [EME] Traversing HIP-aware NATs and Firewalls: Problem Statement andRequirements
Date: Mon, 18 Jun 2007 17:24:14 -0400
Message-ID: <E6F7A586E0A3F94D921755964F6BE006C9806B@EXCHANGE2.cs.cornell.edu>
In-Reply-To: <4676E66D.3030702@gmx.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [EME] Traversing HIP-aware NATs and Firewalls: Problem Statement andRequirements
Thread-Index: Acex5JBTActOxHitTXO/AA1dtbyLZQAB1OFg
From: Paul Francis <francis@cs.cornell.edu>
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>, <eme@irtf.org>
X-OriginalArrivalTime: 18 Jun 2007 21:24:19.0745 (UTC) FILETIME=[0845F110:01C7B1EF]
Received-SPF: None (mail-hub.cs.cornell.edu: francis@cs.cornell.edu does not designate permitted sender hosts)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc:
X-BeenThere: eme@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: end-middle-end research group <eme.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/eme>, <mailto:eme-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/eme>
List-Post: <mailto:eme@irtf.org>
List-Help: <mailto:eme-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/eme>, <mailto:eme-request@irtf.org?subject=subscribe>
Errors-To: eme-bounces@irtf.org

Hi Hannes,

I'm responding to your emails out of order...

This draft certainly is relevant.  I would not claim to have been intimately
familiar with it when we wrote the EME drafts, but speaking for myself I was
vaguely aware of it.  (As you can see, we were quite lazy about citing much
of anything.  Especially the design draft is meant to trigger getting
feedback...it is certainly our intent to do a better job with citations once
we think we are on the right track.)

As far as the HIP nat traversal stuff relates to NUTSS, Am I right in saying
that it suffers from the problem of assymetric paths (i.e. with multihomed
sites)?  If this is the case, then NUTSS seems very complimentary to HIP (as
Tom and others are suggesting).

Sorry if this is a stupid question, but am I right in assuming that with hip
nat/fw traversal, the middleboxes can authenticate the HIP setup, but not
data packets themselves (which after all are vanilla IPSec packets)?

PF

 

> -----Original Message-----
> From: Hannes Tschofenig [mailto:Hannes.Tschofenig@gmx.net] 
> Sent: Monday, June 18, 2007 4:09 PM
> To: eme@irtf.org
> Subject: [EME] Traversing HIP-aware NATs and Firewalls: 
> Problem Statement andRequirements
> 
> This document might be related and relevant:
> http://www.tschofenig.com/drafts/draft-tschofenig-hiprg-hip-na
> tfw-traversal-04.txt
> 
> I wonder whether someone ever looked at it.
> 
> 
> 
> _______________________________________________
> EME mailing list
> EME@irtf.org
> https://www1.ietf.org/mailman/listinfo/eme
> 

_______________________________________________
EME mailing list
EME@irtf.org
https://www1.ietf.org/mailman/listinfo/eme