IETF Logo Mail Archive

Re: [Hipsec] HIP_TRANSFORM and NULL Encryption

Tobias Heer <heer@cs.rwth-aachen.de> Mon, 10 May 2010 13:03 UTC

Return-Path: <heer@informatik.rwth-aachen.de>
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 2C6103A68D1 for <hipsec@core3.amsl.com>; Mon, 10 May 2010 06:03:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.526
X-Spam-Level:
X-Spam-Status: No, score=-2.526 tagged_above=-999 required=5 tests=[AWL=-0.325, BAYES_50=0.001, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, RCVD_IN_DNSWL_MED=-4]
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 t1ll5FZL1NK8 for <hipsec@core3.amsl.com>; Mon, 10 May 2010 06:03:08 -0700 (PDT)
Received: from mta-2.ms.rz.rwth-aachen.de (mta-2.ms.rz.RWTH-Aachen.DE [134.130.7.73]) by core3.amsl.com (Postfix) with ESMTP id B24423A6927 for <hipsec@ietf.org>; Mon, 10 May 2010 06:03:04 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: text/plain; charset="us-ascii"
Received: from ironport-out-2.rz.rwth-aachen.de ([134.130.5.41]) by mta-2.ms.rz.RWTH-Aachen.de (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008)) with ESMTP id <0L2700JXRG8SGWG0@mta-2.ms.rz.RWTH-Aachen.de> for hipsec@ietf.org; Mon, 10 May 2010 15:02:52 +0200 (CEST)
X-IronPort-AV: E=Sophos;i="4.52,362,1270418400"; d="scan'208";a="30124480"
Received: from relay-auth-1.ms.rz.rwth-aachen.de (HELO relay-auth-1) ([134.130.7.78]) by ironport-in-2.rz.rwth-aachen.de with ESMTP; Mon, 10 May 2010 15:02:51 +0200
Received: from umic-137-226-154-185.nn.rwth-aachen.de ([unknown] [137.226.154.185]) by relay-auth-1.ms.rz.rwth-aachen.de (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 9 2008)) with ESMTPA id <0L27002QCG8RAZ80@relay-auth-1.ms.rz.rwth-aachen.de> for hipsec@ietf.org; Mon, 10 May 2010 15:02:52 +0200 (CEST)
From: Tobias Heer <heer@cs.rwth-aachen.de>
In-reply-to: <4BE802F4.9070005@htt-consult.com>
Date: Mon, 10 May 2010 15:02:51 +0200
Message-id: <E4E003A4-1D8E-4BD9-B1DD-9671374BC490@cs.rwth-aachen.de>
References: <4BE802F4.9070005@htt-consult.com>
To: Robert Moskowitz <rgm@htt-consult.com>
X-Mailer: Apple Mail (2.1077)
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:03:11 -0000

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.

Tobias

> 
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec




--  

Dipl.-Inform. Tobias Heer, Ph.D. Student
Distributed Systems Group 
RWTH Aachen University, Germany
tel: +49 241 80 207 76
web: http://ds.cs.rwth-aachen.de/members/heer

v2.28.0 | Report a Bug | By Email | System Status