Re: [Tm-rid] Proposed WG Charter v2
"Card, Stu" <stu.card@axenterprize.com> Mon, 02 December 2019 17:31 UTC
Return-Path: <stu.card@axenterprize.com>
X-Original-To: tm-rid@ietfa.amsl.com
Delivered-To: tm-rid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0B40120099 for <tm-rid@ietfa.amsl.com>; Mon, 2 Dec 2019 09:31:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=axenterprize.com
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 HLM89OQtgRCc for <tm-rid@ietfa.amsl.com>; Mon, 2 Dec 2019 09:31:27 -0800 (PST)
Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com [IPv6:2607:f8b0:4864:20::d35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F33051201EA for <tm-rid@ietf.org>; Mon, 2 Dec 2019 09:31:26 -0800 (PST)
Received: by mail-io1-xd35.google.com with SMTP id f82so166068ioa.9 for <tm-rid@ietf.org>; Mon, 02 Dec 2019 09:31:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=axenterprize.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=b21GRp1tFxzPCbqPkInFflWMIMAOkT4yeF0CQ3toeKs=; b=OE1waAgMZkfRKTzWPgwLH+VBy7YZm35emQFmyfYauJa4GpTyI0Qxc2vIGJ7lVsuLlS 8fBPQDTHtsZLQIgYHNZh+vk3mu7awsF2omti/vZyS7UbdxpKNLQH0fRkw8z+YhxClDLz gNkCsdzpEhsZfbX5VPT+yv0DCu/HPwnxamg2M=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=b21GRp1tFxzPCbqPkInFflWMIMAOkT4yeF0CQ3toeKs=; b=comVOWPTrwdbANst9SKMNGviST2y4RZ7TP7HFeXFKpli1bmEwYS/PTV4W2IC08BE0w 0DD4NqLvrin3LhkLuiUniMOT4GPMvRR8oicijlhOMGx5kVWpjwGbcKNJS19dw55IRw/x xcNny6Jcd7UORXngVk0LLb0dlQrQdXG2tarMFhbGbBP+p7GtMAc/BQUOHYbjLG41TN2f yV1D7s/bY02acMVCDbP3fzbMG81JxFXWzNdqIjcBl7iMXLnquDpMEenVmRJDc9WaM7Nj RipbQgEU+HjxO6LSEH9soCmVBIn+RSIQfi915bcSWXKmOK8txW10Fcq7rMJ4pFpplkuq 830g==
X-Gm-Message-State: APjAAAWqq5ZE2R8iPBnryNzyWbOvd/JhLvxD6G04+7QesnMEH8X2K0F8 3hM83Nn7ux0w1molNZhOjtyJN5aDq/NeIbEIoKJtNQ==
X-Google-Smtp-Source: APXvYqw2mOd72Zrt4zEBmQEn4FiHWJrU9tTzArUoYi5x6tcdo4NgXNVrwE/4u0UgeYpP5FxlMEx+lWxxZw0dTIYEcjM=
X-Received: by 2002:a5d:8743:: with SMTP id k3mr2806853iol.144.1575307886217; Mon, 02 Dec 2019 09:31:26 -0800 (PST)
MIME-Version: 1.0
References: <579d29aa-e3d7-9886-91b6-46641eb1f944@labs.htt-consult.com> <5feb3288-b366-3580-0b1d-1134769bb305@labs.htt-consult.com> <22730.1575295477@localhost>
In-Reply-To: <22730.1575295477@localhost>
From: "Card, Stu" <stu.card@axenterprize.com>
Date: Mon, 02 Dec 2019 12:31:13 -0500
Message-ID: <CAKM0pYPm0avmt3ULQX4j2PJC2d-f7GtjLgezQO1WB6L3uF4OgA@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: tm-rid@ietf.org
Content-Type: multipart/alternative; boundary="000000000000f87f710598bbf24b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/aPyxgttgE-3hN7DLxBVCAaR_HwY>
Subject: Re: [Tm-rid] Proposed WG Charter v2
X-BeenThere: tm-rid@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Trustworthy Multipurpose RemoteID <tm-rid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tm-rid>, <mailto:tm-rid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tm-rid/>
List-Post: <mailto:tm-rid@ietf.org>
List-Help: <mailto:tm-rid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tm-rid>, <mailto:tm-rid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Dec 2019 17:31:30 -0000
I will try wordsmithing this week. On Mon, Dec 2, 2019, 09:04 Michael Richardson <mcr+ietf@sandelman.ca> wrote: > > I am enthusiatic about this work, although I don't anticipate being able to > be more than a bystandard on this. > > Robert Moskowitz <rgm@labs.htt-consult.com> wrote: > > TM-RID will build upon the Host Identity Tag (HIT) from the Host > Identity > > Protocol (HIP) as an RID and augment it and supporting HIP and other > IETF > > technologies to add trustworthiness to the ASTM messaging suite. > > I think that this sentence needs editing. Too many ".. and" > > > The goal is > > to provide trustworthiness both in an Internet connected environment > and > > emergency, unconnected situations within the highly constrained > environment > > of UAS. > > I think that a reference for the nature of the constrained environment > might > be in order. > > > The Host Identity Tag (HIT) is ideally, in fact uniquely, suited to > work > > within this RID effort. The Host Identity (HI) behind the HIT can > be used to > > sign Broadcast Authentication Messages, thus proving ownership of > the RID > > (HIT) and signed messages. HITs provide significantly superior > privacy > > compared to other allowed RID types while providing greater > assurance to > > authorized observers that they are accessing the proper PII for the > UA. > > This wanders into solution space, and I think it would be better to omit > this. > > > TM-RID will create specifications for HIP-augmented ASTM RID > messages.. > > Initially this will consist of additional RID Authentication > Messages that > > use the HI in public key signing operations: to prove UAS ownership > of a > > Hierarchical HIT (HHIT); to authenticate other claims made via RID, > such as > > position and velocity, as having been made by the owner of that > HHIT; and to > > provide observers lacking current Internet connectivity with locally > > verifiable UAS proof-of-registration objects. > > removing some of the solutions, leaving the requirements: > > TM-RID will create specifications to prove UAS ownership of a > Hierarchical HIT (HHIT); providing a framework to authenticate other > claims, such as > position and velocity, as having been made by the owner of that HHIT; and > to > provide observers lacking current Internet connectivity with locally > verifiable UAS proof-of-registration objects. > > I would have written this as numbered points. > > > For this, HIP would be amended to be used effectively in this > environment: > > I think you could put a period instead of : and omit the next three > paragraphs. > > > HHITs are envisioned to identify all components in the UAS/UTM (UAS > Traffic > > Management) environment: UA, Command Consoles, Observer devices, and > > Registries. This will entail further work as experience is gained > in using > > HIP for UAS RID. For example, some (UTM) systems envision using > OAuth for > > Ground Control Systems (GCS) and authorized safety personnel. HIP > as an > > OAuth method may help in merging HIP into these systems. > > > The workgroup will need to liaison with the various SDOs working in > the UAS > > regulation space. > > Please if you could list those SDOs? > Do we need to do liason agreements with them? I would be happier if that > was > part of the plan. > > How will we engage with implementers? I.e. how are we going to get > running-code? > > > > -- > Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works > -= IPv6 IoT consulting =- > > > > -- > Tm-rid mailing list > Tm-rid@ietf.org > https://www.ietf.org/mailman/listinfo/tm-rid >
- [Tm-rid] Proposed WG Charter Robert Moskowitz
- [Tm-rid] Proposed WG Charter v2 Robert Moskowitz
- Re: [Tm-rid] Proposed WG Charter v2 Michael Richardson
- Re: [Tm-rid] Proposed WG Charter v2 Card, Stu
- Re: [Tm-rid] Proposed WG Charter v2 Card, Stu
- Re: [Tm-rid] Proposed WG Charter v2 Eric Vyncke (evyncke)
- Re: [Tm-rid] Proposed WG Charter v2 Michael Richardson
- Re: [Tm-rid] Proposed WG Charter v2 Eric Vyncke (evyncke)
- Re: [Tm-rid] Proposed WG Charter v2 Card, Stu