Re: [Hipsec] HIP_TRANSFORM and NULL Encryption
Robert Moskowitz <rgm@htt-consult.com> Mon, 10 May 2010 13:08 UTC
Return-Path: <rgm@htt-consult.com>
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 87DB93A68A0 for <hipsec@core3.amsl.com>; Mon, 10 May 2010 06:08:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.21
X-Spam-Level: **
X-Spam-Status: No, score=2.21 tagged_above=-999 required=5 tests=[AWL=0.371, BAYES_20=-0.74, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_SORBS_WEB=0.619]
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 CvdzAv4dx2JU for <hipsec@core3.amsl.com>; Mon, 10 May 2010 06:08:39 -0700 (PDT)
Received: from klovia.htt-consult.com (klovia.htt-consult.com [208.83.67.149]) by core3.amsl.com (Postfix) with ESMTP id CC3D43A684D for <hipsec@ietf.org>; Mon, 10 May 2010 06:08:39 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by klovia.htt-consult.com (Postfix) with ESMTP id 6CC2F68B25; Mon, 10 May 2010 13:02:04 +0000 (UTC)
Received: from klovia.htt-consult.com ([127.0.0.1]) by localhost (klovia.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6SJedu+pEApe; Mon, 10 May 2010 09:01:55 -0400 (EDT)
Received: from nc2400.htt-consult.com (unknown [12.173.204.197]) (Authenticated sender: rgm@htt-consult.com) by klovia.htt-consult.com (Postfix) with ESMTPSA id 6AB2D68B24; Mon, 10 May 2010 09:01:55 -0400 (EDT)
Message-ID: <4BE80540.9080501@htt-consult.com>
Date: Mon, 10 May 2010 09:08:16 -0400
From: Robert Moskowitz <rgm@htt-consult.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.0.4-1.fc12 Thunderbird/3.0.4
MIME-Version: 1.0
To: Tobias Heer <heer@cs.rwth-aachen.de>
References: <4BE802F4.9070005@htt-consult.com> <E4E003A4-1D8E-4BD9-B1DD-9671374BC490@cs.rwth-aachen.de>
In-Reply-To: <E4E003A4-1D8E-4BD9-B1DD-9671374BC490@cs.rwth-aachen.de>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: HIP WG <hipsec@ietf.org>
Subject: Re: [Hipsec] HIP_TRANSFORM and NULL Encryption
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: Mon, 10 May 2010 13:08:40 -0000
On 05/10/2010 09:02 AM, Tobias Heer wrote: > Hi, > > Am 10.05.2010 um 14:58 schrieb Robert Moskowitz: > > >> If no one can provide a compelling argument for the NULL cipher for HIP_TRANSFORM, I am pulling it. Of course it makes sense for ESP_TRANSFORM, but not HIP_TRANSFORM. The only argument I have come up with is for testing the HIP encryption process; but that seems very weak. >> > I think it would only affect the HIP_ENCRYPTED part of the packet, right? This seems more like a debugging feature than something that we need in the protocol specs. I am fine with removing it. > That is the only place I see it used. And I don't see that changing, perhaps more things in HIP_ENCRYPTED with plans for DIET HIP, but still only makes sense for testing.
- [Hipsec] HIP_TRANSFORM and NULL Encryption Robert Moskowitz
- Re: [Hipsec] HIP_TRANSFORM and NULL Encryption Tobias Heer
- Re: [Hipsec] HIP_TRANSFORM and NULL Encryption Robert Moskowitz
- Re: [Hipsec] HIP_TRANSFORM and NULL Encryption Ahrenholz, Jeffrey M
- Re: [Hipsec] HIP_TRANSFORM and NULL Encryption Robert Moskowitz
- Re: [Hipsec] HIP_TRANSFORM and NULL Encryption Ahrenholz, Jeffrey M