Re: [Hipsec] Finalizing the TM-RID BoF at IETF-106/Singapore

Robert Moskowitz <rgm@htt-consult.com> Thu, 24 October 2019 13:57 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 F19D912086A for <hipsec@ietfa.amsl.com>; Thu, 24 Oct 2019 06:57:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 OuPXugrX463F for <hipsec@ietfa.amsl.com>; Thu, 24 Oct 2019 06:57:35 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (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 269D21201E3 for <hipsec@ietf.org>; Thu, 24 Oct 2019 06:57:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 3BFD3620D4 for <hipsec@ietf.org>; Thu, 24 Oct 2019 09:57:34 -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 3MocmbqU2aze for <hipsec@ietf.org>; Thu, 24 Oct 2019 09:57:25 -0400 (EDT)
Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (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 9E3A460D1B for <hipsec@ietf.org>; Thu, 24 Oct 2019 09:57:25 -0400 (EDT)
To: HIP <hipsec@ietf.org>
References: <53408B4E-608B-4354-89FB-11260FFA141F@cisco.com>
From: Robert Moskowitz <rgm@htt-consult.com>
Message-ID: <37751412-42c2-a084-6164-1dabf1772837@htt-consult.com>
Date: Thu, 24 Oct 2019 09:57:20 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.1
MIME-Version: 1.0
In-Reply-To: <53408B4E-608B-4354-89FB-11260FFA141F@cisco.com>
Content-Type: multipart/alternative; boundary="------------4F5EFD216BB0C5AF5E2EECA7"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/NnxedAgsCHf24F0uQqAPadlF6CY>
Subject: Re: [Hipsec] Finalizing the TM-RID BoF at IETF-106/Singapore
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: Thu, 24 Oct 2019 13:57:37 -0000

Eric,

I will update the agenda.  Work in Progress with also reving Dex draft.

Michael Richardson is triple booked on this time slot, so maybe Carsten 
or Henk.  Or Daniel Migault.

I will ask around.

I posted a message here on the basics of why HIP (it starts with the 
HIT).  Stu is working on his UAS draft that will have a section on why 
HIP and will be in his slides.  But I will add this to the charter and 
agenda.

Privacy of PII is clearly called out in the FAA requirements and Stu 
will cover that as well.  But it will be clearer in the charter. 
Actually a couple ballots on the ASTM doc noted that the use of Serial # 
or CAA registration probably violates PII requirements and HITs can well 
protect PII and still provide strong ID.

But I need to update the BOF info.

Bob


On 10/24/19 3:31 AM, Eric Vyncke (evyncke) wrote:
>
> Bob and Stu,
>
> Are we all set for this BoF?
>
> For instance, currently there is a single chair Gonzalo Camarillo 
> while it may be useful to have two.
>
> The agenda should also have a point about privacy (even if, as 
> previously discussed, there is no real privacy on purpose) and why IP 
> and HIP rather than another technique.
>
> Beside the discussion on the charter for a potential WG, it would be 
> safer to reserve 10 minutes at the end to probe the participants about 
> the questions of RFC 5434 that are required in order to form a WG.
>
> Unsure whether you can still update the BoF page on your own, else, 
> send me the changes and I will apply them
>
> Regards
>
> -éric
>
>
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec