[Ipsec] Finishing up on rfc3664bis (AES-XCBC-PRF-128)
Paul Hoffman <paul.hoffman@vpnc.org> Thu, 26 May 2005 21:01 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DbPTh-0004Mu-D4; Thu, 26 May 2005 17:01:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DbPTf-0004Mn-F2 for ipsec@megatron.ietf.org; Thu, 26 May 2005 17:01:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12165 for <ipsec@ietf.org>; Thu, 26 May 2005 17:01:13 -0400 (EDT)
Received: from above.proper.com ([208.184.76.39]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DbPmJ-0006bt-Nm for ipsec@ietf.org; Thu, 26 May 2005 17:20:33 -0400
Received: from [10.20.30.249] (dsl2-63-249-92-231.cruzio.com [63.249.92.231]) (authenticated bits=0) by above.proper.com (8.12.11/8.12.9) with ESMTP id j4QL16Ff091261 for <ipsec@ietf.org>; Thu, 26 May 2005 14:01:06 -0700 (PDT) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0621029ebebbe38b45db@[10.20.30.249]>
Date: Thu, 26 May 2005 14:01:02 -0700
To: IPsec WG <ipsec@ietf.org>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Subject: [Ipsec] Finishing up on rfc3664bis (AES-XCBC-PRF-128)
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP Security <ipsec.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
Sender: ipsec-bounces@ietf.org
Errors-To: ipsec-bounces@ietf.org
Greetings again. I have not heard any comments on the latest version of the revision to RFC 3664, which is currently <http://www.ietf.org/internet-drafts/draft-hoffman-rfc3664bis-02.txt>. If I don't hear anything in the coming days, I'll ask for it to be published as an RFC. FWIW, this draft would be greatly enhanced by having worked-out examples of the three different key lengths, similar to those in RFC 3556. If any implementer of AES-XCBC-MAC-96 can do this in the near future, please let me know so I can add them (and an acknowledgement, of course) to the document. --Paul Hoffman, Director --VPN Consortium _______________________________________________ Ipsec mailing list Ipsec@ietf.org https://www1.ietf.org/mailman/listinfo/ipsec
- [Ipsec] Finishing up on rfc3664bis (AES-XCBC-PRF-… Paul Hoffman