Re: [Hipsec] Status of HIP DEX

Robert Moskowitz <> Wed, 20 January 2016 15:18 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 18A271A8AC0 for <>; Wed, 20 Jan 2016 07:18:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.802
X-Spam-Status: No, score=-2.802 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 2gVI_o1fRiRt for <>; Wed, 20 Jan 2016 07:18:23 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B58671A8AB8 for <>; Wed, 20 Jan 2016 07:18:23 -0800 (PST)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 72F7460D1B for <>; Wed, 20 Jan 2016 10:18:22 -0500 (EST)
X-Virus-Scanned: amavisd-new at
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with LMTP id 9iboeS+WeMdc for <>; Wed, 20 Jan 2016 10:18:19 -0500 (EST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 9308D60971 for <>; Wed, 20 Jan 2016 10:18:18 -0500 (EST)
References: <>
From: Robert Moskowitz <>
Message-ID: <>
Date: Wed, 20 Jan 2016 10:18:16 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [Hipsec] Status of HIP DEX
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 20 Jan 2016 15:18:26 -0000

I just posted ver 05.  I only reved the dates.  I am seriously 
considering adding Curve25519 as it 'works' much better in constrained 
systems than p256.  But I would need a published reference for it.

On 01/20/2016 08:59 AM, Robert Moskowitz wrote:
> Although draft-moskowitz-hip-dex-04 expired yesterday, I have been 
> active with it as follows:
> IEEE 802.15.9 references both HIP BEX and DEX.  This Recommended 
> Standard will be starting IEEE Sponsor Ballot recirculation #2 Jan 21 
> on a 10 day voting cycle.  We anticipate our one NO voter to switch to 
> YES (as he contributed to the editorial changes and said they 
> satisfied his concerns) and no new NO votes.  That is it is done 
> balloting.  It is tightly timed, but this will get it on RevCom Feb 2 
> to be approved for publication.  But,,,
> No Internet Drafts in an IEEE document.  So HIP DEX would hold up the 
> publication.
> For those not familiar with DEX, it is a reduction on BEXv2 and the 
> text is closely aligned, thanks to Rene's editing.
> I plan on reving DEX-04 as DEX-05 as soon as possible.  Like this week 
> still.  The question is where does this go to be moved forward.  ISE 
> submission is not good, as then it could only be Informational or 
> Experimental.  So either this workgroup does a last call and moves it 
> forward, or I go the AD submission route. I have been discussing this 
> with Stephen Farrell as Security AD, and regardless, he would be 
> reviewing it.  The question is what route to IESG.  This wg, this wg 
> AD, or security AD?
> Please help me out here.
> HIP DEX is also referenced in:
> draft-ohba-6lo-mle-hip-dex-01.txt
> as used by Zigbee and a further reduction of DEX (because even it was 
> too many bytes over the air) is in a product I cannot name.
> I look forward to your assistance.
> On a personal note:
> I am being funded by Huawei to work on DOTS/I2NSF/MILE/SACM.  Look for 
> a number of IDs coming from me (or my joining others) in those areas.  
> Look for HIP being referenced in a place or two.  Along with SSE.  I 
> plan on attending the next IETF, but will not be arriving until Mon 
> noon.  My youngest son is engaged and the wedding is the week prior 
> and thus I cannot split for IETF until Sunday.
> I am working on another contract that I soon hope to share with you here.
> _______________________________________________
> Hipsec mailing list