Re: [Hipsec] Conflicting text in RFC5201 - RFC5201-bis
Samu Varjonen <samu.varjonen@hiit.fi> Wed, 26 May 2010 10:59 UTC
Return-Path: <samu.varjonen@hiit.fi>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7AF563A68CE for <hipsec@core3.amsl.com>; Wed, 26 May 2010 03:59:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bygPKDrumuDF for <hipsec@core3.amsl.com>; Wed, 26 May 2010 03:59:47 -0700 (PDT)
Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by core3.amsl.com (Postfix) with ESMTP id 61C3D3A68AE for <hipsec@ietf.org>; Wed, 26 May 2010 03:59:46 -0700 (PDT)
Received: from [128.214.113.196] (sutherland.hiit.fi [128.214.113.196]) by argo.otaverkko.fi (Postfix) with ESMTP id 3EE9825ED0E; Wed, 26 May 2010 13:59:37 +0300 (EEST)
Message-ID: <4BFCFF0D.10309@hiit.fi>
Date: Wed, 26 May 2010 13:59:25 +0300
From: Samu Varjonen <samu.varjonen@hiit.fi>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: Tobias Heer <heer@cs.rwth-aachen.de>
References: <AB42DFE2-0673-41DE-A40D-7D727D4A6BF3@cs.rwth-aachen.de>
In-Reply-To: <AB42DFE2-0673-41DE-A40D-7D727D4A6BF3@cs.rwth-aachen.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: HIP WG <hipsec@ietf.org>
Subject: Re: [Hipsec] Conflicting text in RFC5201 - RFC5201-bis
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 May 2010 10:59:48 -0000
Tobias Heer wrote:
> Hello,
>
> I have a question regarding some text in RFC5201 that conflicts with the crypto agility that we envisioned.
>
> The new BEX will have to start the negotiations of the DH groups already in I1 to allow the Responder to pick a sensible DH group (there are simple countermeasures against downgrade attacks, too, so don't worry).
> Therefore, the I1 becomes slightly more important than it was (although it stays unsigned and cheap).
>
>
> In Section 4.1 RFC5201 states:
>
> ...
> 705 The Initiator first sends a trigger packet, I1, to the
> 706 Responder. The packet contains the HIT of the Initiator
> 707 and possibly the HIT of the Responder, if it is known.
> 708 Moreover, it contains a list of Diffie Hellman Group IDs
> 709 supported by the Initiator. Note
> 710 that in some cases it may be possible to replace this trigger
> 711 packet by some other form of a trigger, in which case the
> 712 protocol starts with the Responder sending the R1 packet.
> ...
>
> With the DH group negotiations already starting in I1 it becomes difficult to omit the I1 (you can do it but you lose DH crypto agility).
> Moreover, I doubt that omitting the I1 works well even without considering the DH group negotiations because some of the measures to keep the Responder stateless until I2 rely on having information from the I1 (IP address or HIT) for the puzzle/ opaque data field.
>
>
> My questions are:
> Is anyone using or does anyone intent to use this omission of the I1?
Check out draft-ietf-hip-hiccups-02 Section 5.3
"
A host receiving a HIP DATA packet makes decision whether to process
the packet or not. If the host, following its local policy, suspects
that this packet could be part of a DoS attack. The host MAY respond
with an R1 packet to the HIP DATA packet...
"
> Is there any specification on how to do it (at least this is the only place in 5201 where it is mentioned).
> Do we need this feature because there are cases where you cannot send an I1?
> And finally: can we live without that note?
>
> Of course, even if we skip it there is nothing that will keep someone defining it as an extension to the base specs if it is needed in the future.
>
> Thanks for any input.
>
> Tobias
>
>
- [Hipsec] Conflicting text in RFC5201 - RFC5201-bis Tobias Heer
- Re: [Hipsec] Conflicting text in RFC5201 - RFC520… Samu Varjonen
- Re: [Hipsec] Conflicting text in RFC5201 - RFC520… René Hummen
- Re: [Hipsec] Conflicting text in RFC5201 - RFC520… Tobias Heer
- Re: [Hipsec] Conflicting text in RFC5201 - RFC520… Ari Keranen
- Re: [Hipsec] Conflicting text in RFC5201 - RFC520… Tobias Heer
- Re: [Hipsec] Conflicting text in RFC5201 - RFC520… Ari Keranen
- Re: [Hipsec] Conflicting text in RFC5201 - RFC520… Tobias Heer