draft-ietf-ipsec-ikev2-12.txt reference section
Tero Kivinen <kivinen@iki.fi> Tue, 13 January 2004 21:43 UTC
Received: from lists.tislabs.com (portal.tislabs.com [192.94.214.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16797 for <ipsec-archive@lists.ietf.org>; Tue, 13 Jan 2004 16:43:08 -0500 (EST)
Received: by lists.tislabs.com (8.9.1/8.9.1) id OAA20174 Tue, 13 Jan 2004 14:21:02 -0500 (EST)
X-Authentication-Warning: fireball.acr.fi: kivinen set sender to kivinen@iki.fi using -f
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <16388.18353.362889.658207@fireball.acr.fi>
Date: Tue, 13 Jan 2004 21:32:01 +0200
From: Tero Kivinen <kivinen@iki.fi>
To: ipsec@lists.tislabs.com
CC: charliek@microsoft.com
Subject: draft-ietf-ipsec-ikev2-12.txt reference section
X-Mailer: VM 7.17 under Emacs 21.3.1
Organization: Helsinki University of Technology
X-Edit-Time: 5 min
X-Total-Time: 4 min
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk
Content-Transfer-Encoding: 7bit
I think the UDP encapsulation draft (draft-ietf-ipsec-udp-encaps-07.txt) reference should be normative not informative. The implementators need to read and implement the encapsulation specified there to implement the NAT traversal. On the other hand it should have informative reference to the draft-ietf-ipsec-nat-reqts-06.txt which describes the NAT traversal requirements and background (and perhaps a reference to there in the beginning of the section 2.23). -- kivinen@safenet-inc.com
- draft-ietf-ipsec-ikev2-12.txt reference section Tero Kivinen