re: Call for agenda topics for Pittsburgh IETF

Markus Stenberg <mstenber@ssh.com> Fri, 21 July 2000 15:14 UTC

Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id IAA01750; Fri, 21 Jul 2000 08:14:16 -0700 (PDT)
Received: by lists.tislabs.com (8.9.1/8.9.1) id JAA02936 Fri, 21 Jul 2000 09:39:07 -0400 (EDT)
To: tytso@mit.edu, ipsec@lists.tislabs.com
Subject: re: Call for agenda topics for Pittsburgh IETF
From: Markus Stenberg <mstenber@ssh.com>
Date: Fri, 21 Jul 2000 12:54:32 +0900
Message-ID: <87itu06suf.fsf@porsas.jp.ssh.com>
Lines: 34
User-Agent: Gnus/5.0806 (Gnus v5.8.6) XEmacs/21.1 (Capitol Reef)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk

We submitted a draft last Friday that details our approach for IPsec
NAT-traversal, in hope of getting a standard for this some day. NATs are
here to stay, regrettably, and many vendors, each of them making their own
version of NAT-traversal, is suboptimal solution to getting IPsec to work
with NATs.

Ted hadn't reacted to my previous mail, but this is a FYI to WG about my
desire to get a chance to give a presentation regarding it (in the IETF
Pittsburgh meeting) to the IPsec WG.

In short, the draft details UDP encapsulation of IPsec SAs and how to probe
for need of encapsulation in the IKE P1.

(and then cut-n-pasted parts of I-D Announce)

------------------------------------------------------------------------------
Title		: IPsec NAT-Traversal
Author(s)	: M. Stenberg, S. Paavolainen, T. Ylonen, T. Kivinen
Filename	: draft-stenberg-ipsec-nat-traversal-00.txt
Pages		: 16
Date		: 18-Jul-00
	
This draft details the changes needed in order to make both initial IKE
negotiation and subsequent authenticated/encrypted communications across
IPsec AH/ESP SAs work despite the changes in the headers, and possible
protocol transformations.

The draft is at 
<http://www.ietf.org/internet-drafts/draft-stenberg-ipsec-nat-traversal-00.txt>
------------------------------------------------------------------------------

-- 
              Markus Stenberg <markus.stenberg@ssh.com>
         SSH Communications Security Corp (http://www.ssh.com)