[Hipsec] New crypto for HIP

Robert Moskowitz <rgm@htt-consult.com> Wed, 28 August 2019 20:43 UTC

Return-Path: <rgm@htt-consult.com>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 20AE6120089 for <hipsec@ietfa.amsl.com>; Wed, 28 Aug 2019 13:43:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id slYHGHeApSOj for <hipsec@ietfa.amsl.com>; Wed, 28 Aug 2019 13:43:38 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com []) (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 E57F012004C for <hipsec@ietf.org>; Wed, 28 Aug 2019 13:43:37 -0700 (PDT)
Received: from localhost (localhost []) by z9m9z.htt-consult.com (Postfix) with ESMTP id 34ED962120 for <hipsec@ietf.org>; Wed, 28 Aug 2019 16:43:35 -0400 (EDT)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([]) by localhost (z9m9z.htt-consult.com []) (amavisd-new, port 10024) with LMTP id GHc9AldIYAN3 for <hipsec@ietf.org>; Wed, 28 Aug 2019 16:43:30 -0400 (EDT)
Received: from lx140e.htt-consult.com (unknown []) (using TLSv1.2 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 185636211D for <hipsec@ietf.org>; Wed, 28 Aug 2019 16:43:28 -0400 (EDT)
To: HIP <hipsec@ietf.org>
From: Robert Moskowitz <rgm@htt-consult.com>
Message-ID: <920b8101-60ac-2ef4-9d9e-e4eb2d65663d@htt-consult.com>
Date: Wed, 28 Aug 2019 16:43:20 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/9UfQQYmVWsVgupdeqSmzoo8vEdA>
Subject: [Hipsec] New crypto for HIP
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 28 Aug 2019 20:43:40 -0000

I am a bit frustrated here on delays on a number of fronts.

I have been working silently to put some final touches on DEX and 
discussions on Native NAT.

But more time on Hierarchical HITs, along with advancements in cryptography.

I am looking for a co-author that is familiar with HIP's crypto use and 
Edward Curves and Keccek.  The goal is to provide all HIP crypto with 
these new algorithms.  A device will not need any of the old asymmetric 
or symmetric crypto if it follows this draft.

Of course that violates some of the MUSTs in BEX, but I am thinking 
about how to finesse that in constrained environments...