IETF Logo Mail Archive

[Hipsec] Please refresh my memory on HIP_SIGNATURE in UPDATE

Robert Moskowitz <rgm@htt-consult.com> Sun, 18 September 2016 18:29 UTC

Return-Path: <rgm@htt-consult.com>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4120712B015 for <hipsec@ietfa.amsl.com>; Sun, 18 Sep 2016 11:29:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.517
X-Spam-Level:
X-Spam-Status: No, score=-6.517 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c0BmRawOKTJx for <hipsec@ietfa.amsl.com>; Sun, 18 Sep 2016 11:29:10 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [50.253.254.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1ED8112B174 for <hipsec@ietf.org>; Sun, 18 Sep 2016 11:20:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id E513162168 for <hipsec@ietf.org>; Sun, 18 Sep 2016 14:19:58 -0400 (EDT)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 5Vvm4bDjU0Pc for <hipsec@ietf.org>; Sun, 18 Sep 2016 14:19:46 -0400 (EDT)
Received: from lx120e.htt-consult.com (unknown [185.34.11.162]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 0912F6212A for <hipsec@ietf.org>; Sun, 18 Sep 2016 14:19:45 -0400 (EDT)
To: hipsec@ietf.org
From: Robert Moskowitz <rgm@htt-consult.com>
Message-ID: <6bdc4938-6381-b69b-3298-b6000ab13926@htt-consult.com>
Date: Sun, 18 Sep 2016 19:19:40 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/iuqPy0j9Jm1mHfQaQBthLxG7cko>
Subject: [Hipsec] Please refresh my memory on HIP_SIGNATURE in UPDATE
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.17
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/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sun, 18 Sep 2016 18:29:12 -0000

I cannot remember why we mandated HIP_SIGNATURE in UPDATE packet, 
particularly when we have the HIP_MAC.  Sec 5.3.5 in 7401.

I am sure we had a good reason, but I am not finding it....

thanks

Bob

v2.23.0 | Report a Bug | By Email