Small clarification to the draft-ietf-ipsec-nat-t-ike-02.txt
Tero Kivinen <kivinen@ssh.fi> Wed, 24 April 2002 18:41 UTC
Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g3OIfpa22785; Wed, 24 Apr 2002 11:41:51 -0700 (PDT)
Received: by lists.tislabs.com (8.9.1/8.9.1) id NAA18910 Wed, 24 Apr 2002 13:59:50 -0400 (EDT)
X-Authentication-Warning: ryijy.hel.fi.ssh.com: kivinen set sender to <kivinen@ssh.fi> using -f
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <15558.62812.263836.248212@ryijy.hel.fi.ssh.com>
Date: Wed, 24 Apr 2002 21:11:40 +0300
From: Tero Kivinen <kivinen@ssh.fi>
To: ipsec@lists.tislabs.com
Subject: Small clarification to the draft-ietf-ipsec-nat-t-ike-02.txt
X-Mailer: VM 6.89 under Emacs 20.7.1
Organization: SSH Communications Security Oy
X-Edit-Time: 5 min
X-Total-Time: 4 min
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk
There is small typo in the draft-ietf-ipsec-nat-t-ike-02.txt. The Vendor ID hex and the string specified in the draft-ietf-ipsec-nat-t-ike-02.txt does not match exactly. This is because when I calculated the md5 hash of the string I accidently appended newline character to the string. This means that if you are using the md5 of the string use "draft-ietf-ipsec-nat-t-ike-02\n". This will give out the hex string given in the document. If you are using the hex string given in the document there is no need to do anything. As this string and the hex value of it will change when the document goes out as an RFC, I don't think we need to issue new draft just to fix that typo. -- kivinen@ssh.fi SSH Communications Security http://www.ssh.fi/ SSH IPSEC Toolkit http://www.ssh.fi/ipsec/
- Small clarification to the draft-ietf-ipsec-nat-t… Tero Kivinen