Re: [Drip] RID Updates for IETF#113
"Card, Stu" <stu.card@axenterprize.com> Tue, 22 March 2022 19:28 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 570BC3A0B72
for <tm-rid@ietfa.amsl.com>; Tue, 22 Mar 2022 12:28:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001,
RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001,
T_SCC_BODY_TEXT_LINE=-0.01, 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 EnIIM8Lv6BRz for <tm-rid@ietfa.amsl.com>;
Tue, 22 Mar 2022 12:28:54 -0700 (PDT)
Received: from mail-ej1-x62f.google.com (mail-ej1-x62f.google.com
[IPv6:2a00:1450:4864:20::62f])
(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 4732E3A0B64
for <tm-rid@ietf.org>; Tue, 22 Mar 2022 12:28:54 -0700 (PDT)
Received: by mail-ej1-x62f.google.com with SMTP id bg10so38408703ejb.4
for <tm-rid@ietf.org>; Tue, 22 Mar 2022 12:28:54 -0700 (PDT)
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=PBDkwQQssy088zVIbrKKUL+esmW0T+1GCwVCZve28I8=;
b=VLfXZPCTqMeE6rp/9PHje/QedhV8eedBWfkisNa4V8QBDpLseEgj236TEdwGIb9KJN
wWLaTI5PFGQMAsF89qnui7zC7DXO9puLYt00kAO0Q8MWp/kuJRPUXqDqThB9/SmR5S6S
6vHTsDR+3cRZSxI8twY1cWmBXk4ev/pp4oAII=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20210112;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to:cc;
bh=PBDkwQQssy088zVIbrKKUL+esmW0T+1GCwVCZve28I8=;
b=7Z4vLldJyt0vR/SCu+5tsh1+dC9KPa8I5MA76oXs38rJsSIEtRC0CHrImYGTX2krKH
eSQhHjSFdU2GfJ8bULfNmGJsXgD7s9E1bssWnUcVter3LSqEzsftCjtGp8NKW9hf30Yq
hIfJ3xvkjRZEtGMYVRGRoGYEybSdp4YndkQHvQzp2+fGcJid1CAjSi4wFekHZyO8s6Oo
p4fkG7F1S9c4xcOJMTfHKhPn45YOb0bR1GDvOPVOyQr8WDZpULxeAKvoFqpQeqweeKhZ
GoPjV3B5wLZ3PZ/yrUBAVDhTudubmw4ijk1L1ZTZ0yd/Sh+YjiM7LDjkD9SxhejgzccN
/zwA==
X-Gm-Message-State: AOAM531hI0SEE/XTxya61zoAkSGk2Iz1lLyeaK2Re159sZ/+sWZMpAFi
1mOlnjRe+ETSuCxFWioRxDWgyY0Eb0GJbflXw2GBLw==
X-Google-Smtp-Source: ABdhPJy8kYI0zXOAMfMDv8x6nXG9T1iXnLRMJQQYD+/c6wEm2d59xWghAEI+VwNQba1b15FPbC9S492hOGupvCVxMYo=
X-Received: by 2002:a17:906:1804:b0:6d6:dc46:d9ed with SMTP id
v4-20020a170906180400b006d6dc46d9edmr27273398eje.288.1647977332056; Tue, 22
Mar 2022 12:28:52 -0700 (PDT)
MIME-Version: 1.0
References: <331_1647942573_62399BAD_331_204_1_073a22a7e2984a0abd2c8992646b54a0@orange.com>
<25ea27a7-d509-fb83-7697-5742025e3e11@labs.htt-consult.com>
In-Reply-To: <25ea27a7-d509-fb83-7697-5742025e3e11@labs.htt-consult.com>
From: "Card, Stu" <stu.card@axenterprize.com>
Date: Tue, 22 Mar 2022 15:28:37 -0400
Message-ID: <CAKM0pYO8eZL4xMNsCSBL9PzaAfvnQBsfphvRJAtMk_8bu2m2Lw@mail.gmail.com>
To: Robert Moskowitz <rgm@labs.htt-consult.com>
Cc: Mohamed Boucadair <mohamed.boucadair@orange.com>,
"tm-rid@ietf.org" <tm-rid@ietf.org>,
"drip-chairs@ietf.org" <drip-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000079ce4b05dad39f9d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/Qt4hcas9hXqdB6LOL9oz2f9_ZdM>
Subject: Re: [Drip] RID Updates for IETF#113
X-BeenThere: tm-rid@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Drone Remote Identification Protocol <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: Tue, 22 Mar 2022 19:29:00 -0000
The only point on the slides on which I would love to hear some discussion from someone other than Adam, Bob and myself is the breakdown of HID and HHIT Suite ID. I don't care if the HHIT Suite ID is 4 bits or 8 bits. What I objected to is the use of 8 bits to represent just under 5 bits worth of possibilities. Given the discussion in RFC 7401 Appendix E of rotating use of the available space (re-using deprecated values), 4 bits are likely enough. With a 28 bit prefix, that would make 32 (rather than 28) available for the HID, presumably 16 for RAA and 16 for HDA (until we move to CIDR style allocation). Would anyone like to chime in here? Thanks all, especially Bob! On Tue, Mar 22, 2022 at 5:53 AM Robert Moskowitz <rgm@labs.htt-consult.com> wrote: > Yes, I was going to use any time to say: > > "Please download and look at my slides and comment on the list. Thank > you." > > :) > > On 3/22/22 05:49, mohamed.boucadair@orange.com wrote: > > Hi all, > > > > FWIW, Bob kindly prepared the following the slides to report the status of > the RID draft: > > > https://raw.githubusercontent.com/ietf-wg-drip/draft-ietf-drip-rid/main/slides-113-drip-drip-uas-remote-id-updates-ss1921.pdf > > > > For better use of the meeting time, we won’t be displaying these slides > during the session. > > > > Thank you. > > > > Cheers, > > Med > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > This message and its attachments may contain confidential or privileged information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > Thank you. > > > > -- > Robert Moskowitz > Owner > HTT Consulting > C: 248-219-2059 > F: 248-968-2824 > E: rgm@labs.htt-consult.com > > There's no limit to what can be accomplished if it doesn't matter who gets > the credit > -- > Tm-rid mailing list > Tm-rid@ietf.org > https://www.ietf.org/mailman/listinfo/tm-rid >
- [Drip] RID Updates for IETF#113 mohamed.boucadair
- Re: [Drip] RID Updates for IETF#113 Robert Moskowitz
- Re: [Drip] RID Updates for IETF#113 Card, Stu