Re: [IPsec] IANA ikev2 registry and FC values
Tero Kivinen <kivinen@iki.fi> Thu, 17 January 2013 17:41 UTC
Return-Path: <kivinen@iki.fi>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F14D221F8B49 for <ipsec@ietfa.amsl.com>; Thu, 17 Jan 2013 09:41:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rQUEMdbhC4gn for <ipsec@ietfa.amsl.com>; Thu, 17 Jan 2013 09:41:43 -0800 (PST)
Received: from mail.kivinen.iki.fi (fireball.kivinen.iki.fi [IPv6:2001:1bc8:100d::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0BE3921F8A11 for <ipsec@ietf.org>; Thu, 17 Jan 2013 09:41:42 -0800 (PST)
Received: from fireball.kivinen.iki.fi (localhost [127.0.0.1]) by mail.kivinen.iki.fi (8.14.5/8.14.5) with ESMTP id r0HHffVw025277 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Jan 2013 19:41:41 +0200 (EET)
Received: (from kivinen@localhost) by fireball.kivinen.iki.fi (8.14.5/8.12.11) id r0HHffG5007595; Thu, 17 Jan 2013 19:41:41 +0200 (EET)
X-Authentication-Warning: fireball.kivinen.iki.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: <20728.14293.844231.917856@fireball.kivinen.iki.fi>
Date: Thu, 17 Jan 2013 19:41:41 +0200
From: Tero Kivinen <kivinen@iki.fi>
To: Dan Harkins <dharkins@lounge.org>
In-Reply-To: <98a68558188e76db21c232a85d12d6cb.squirrel@www.trepanning.net>
References: <20728.12021.834751.712756@fireball.kivinen.iki.fi> <98a68558188e76db21c232a85d12d6cb.squirrel@www.trepanning.net>
X-Mailer: VM 7.19 under Emacs 21.4.1
X-Edit-Time: 3 min
X-Total-Time: 2 min
Cc: ipsec@ietf.org
Subject: Re: [IPsec] IANA ikev2 registry and FC values
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipsec>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jan 2013 17:41:44 -0000
Dan Harkins writes: > I don't actually see what the problem is that this note would solve. > Unless there's a problem then I have an objection to adding this note. > Can you restate the problem? Mostly because then saying integrity protection with SHA-1 is not well defined anymore. Currently it is assumed it always means AUTH_HMAC_SHA1_96, but if implementations start supporting AUTH_HMAC_SHA1_160 too, then the GUI etc needs to be modified to be explicit about the truncation length, and that just causes confusion and interoperability problems. Especially as I do not know any implementation out there that supports AUTH_HMAC_SHA1_160 for IP use... -- kivinen@iki.fi
- [IPsec] IANA ikev2 registry and FC values Tero Kivinen
- Re: [IPsec] IANA ikev2 registry and FC values Yaron Sheffer
- Re: [IPsec] IANA ikev2 registry and FC values Black, David
- Re: [IPsec] IANA ikev2 registry and FC values Dan Harkins
- Re: [IPsec] IANA ikev2 registry and FC values Tero Kivinen
- Re: [IPsec] IANA ikev2 registry and FC values Tero Kivinen
- Re: [IPsec] IANA ikev2 registry and FC values Yaron Sheffer
- Re: [IPsec] IANA ikev2 registry and FC values Tero Kivinen
- Re: [IPsec] IANA ikev2 registry and FC values Yaron Sheffer
- Re: [IPsec] IANA ikev2 registry and FC values Dan Harkins