Re: [Hipsec] HIP - TM-RID meeting in Singapore

Robert Moskowitz <> Thu, 03 October 2019 14:01 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5F23C12090D for <>; Thu, 3 Oct 2019 07:01:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id dcjQucBfIZnM for <>; Thu, 3 Oct 2019 07:00:59 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8B6A8120912 for <>; Thu, 3 Oct 2019 07:00:59 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4B05C62124 for <>; Thu, 3 Oct 2019 10:00:58 -0400 (EDT)
X-Virus-Scanned: amavisd-new at
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with LMTP id uFHajYLR06Zw for <>; Thu, 3 Oct 2019 10:00:53 -0400 (EDT)
Received: from (unknown []) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 9297F62116 for <>; Thu, 3 Oct 2019 10:00:50 -0400 (EDT)
From: Robert Moskowitz <>
To: HIP <>
References: <>
Message-ID: <>
Date: Thu, 3 Oct 2019 10:00:42 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <>
Subject: Re: [Hipsec] HIP - TM-RID meeting in Singapore
X-Mailman-Version: 2.1.29
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: Thu, 03 Oct 2019 14:01:03 -0000

OK, lets get some discussion here...

Only 32 people signed up for tm-rid list.  Of course if things work out, 
the discussion moves here; hopefully that will be a good thing.

I have requested a tm-rid BOF; I would appreciate it if I were to get 
some interest in others here and commitments to attend the BOF. Here is 
a rough agenda:

5 min Agenda bashing (ya got to bash at the agenda.  Its a tradition).
10 min UAS background (RemoteID, NetworkID, and Command & Control)
10 min UAS/HIP use case
10 min Hierarchical HITs and HIT Registries
5 min New Crypto in HIP (and new ESP Transform: Diet-ESP and Keyak cipher)
10 min RemoteID HIP Authenticated Messages
5 min Hackathon report (If we can get some people working on those 
messages and C2 protection)
5 min Next steps (updated HIP charter) and Q&A

Is that too packed?  Did I leave anything out?  Should I ask for 90min?

The IESG will be looking for activity here to gauge the interest/activity.


On 9/20/19 4:45 PM, Robert Moskowitz wrote:
> Dear HIPsters,
> I am in discussion with Ganzalo and Eric about a HIP session in 
> Singapore.
> The focus is the new work to support "Trustworthy Multipurpose 
> RemoteID" with the target user of UAS.
> This week I attended the UAS Symposium outside of Syracuse 
> NY and received considerable support for HITs as RemoteIDs (along with 
> the other expected formats).  This effort has funding from CLUE (I was 
> told what that means and what piece of legislation set it up, but...).
> I have the 1st versions of the 1st 3 drafts.  More to follow.
> I would like to see hackathon efforts at Singapore (unfortunately we 
> cannot fly drones in the hackathon room, perhaps we can get them 
> suspended from the ceiling).  Also including HIPv2 software interop 
> testing.
> It is early to actually have an agenda, but the question is:
> When during the week.
> How long a session.
> Eric was thinking a short session on Friday.
> I will be there for the whole week, so Friday morning works for me. 
> Who would also be there.  Who could not.
> A short session at the end of the week SHOULD be ok.
> What about earlier in the week?  Who would attend?  What are conflicts 
> Eric needs to move forward on scheduling deadlines are coming up. 
> Please chime in.
> Bob
> _______________________________________________
> Hipsec mailing list