IETF Logo Mail Archive

Re: [Drip] The remote ID and/or FAA?

"Card, Stu" <stu.card@axenterprize.com> Fri, 26 March 2021 12:46 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 2AC3C3A1DC0 for <tm-rid@ietfa.amsl.com>; Fri, 26 Mar 2021 05:46:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 uB260y88gxK7 for <tm-rid@ietfa.amsl.com>; Fri, 26 Mar 2021 05:45:58 -0700 (PDT)
Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (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 ECDCD3A1EAB for <tm-rid@ietf.org>; Fri, 26 Mar 2021 05:45:35 -0700 (PDT)
Received: by mail-ed1-x536.google.com with SMTP id y6so6186906eds.1 for <tm-rid@ietf.org>; Fri, 26 Mar 2021 05:45:35 -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=mOvYXU0OQUofrHILj7rsUi/o3x7JbOG0J/1cO3wBJ0o=; b=Eb4pGo1nON9lvsQzLxg0P3MYF44SbmYakGTmeasBr3UJvkQtN4Aeus9fTySBaXDlkW DQ6UGTrSXakeVKZtbMQ32W6W+TtSrId3x+lONqpp1mIgFavvRxlQ7wOhMjC5tt0cG0wD kGJEC2zSBZXHoPcA3irmpaigxy647/eLGQPnE=
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=mOvYXU0OQUofrHILj7rsUi/o3x7JbOG0J/1cO3wBJ0o=; b=CjcmuVRKZVJjvZ6q3mbdeB7l+JQY+u50CnGpzNIltrZ/z/h7wagtTU8dY+FYO4YiXY 45ejgmLml3SEL1VV464fOJW9oAwxKgdNU/ShHgs0b+rK1qGFS17aFb8B3kNDMr6mksoH XzuHhZh4MPlopJDJkX/mCdAukNXg/TQATXkQAtnxULNrFxsjrNg7vSC0pHNGXvNi8D9V RAixxgVeLg3/F4tt4PBUTS0E7kWjOdpaTEirI0BgfEUEowTz9+PWeAQfMNBH4r2Bj9fC p/XBggE9D0SxyiL4Y8t7FKObABpGejozOO5ATRV7nmoaw4yVaYspOTwruKl0inmO8cCS +gaA==
X-Gm-Message-State: AOAM530STiukmv9GMHGMbhBiqSwnMv+NQ5t6UK/q2s0p6glw1YUSe7GC wVGZguvxTXBAAqmUmv0YKfR7z8VRBoaTK9EU8s/JrA==
X-Google-Smtp-Source: ABdhPJwfD4JkDbg2xsUMf958sz8ThzETkmNKju+V56Zy7xqALrXzM4cjuDsslVk7WTLKwfP12KMHw1IgEanka5rBWlc=
X-Received: by 2002:aa7:c857:: with SMTP id g23mr14935603edt.86.1616762732551; Fri, 26 Mar 2021 05:45:32 -0700 (PDT)
MIME-Version: 1.0
References: <53c9e415-faa4-732f-37ee-41c9303cd977@gmail.com>
In-Reply-To: <53c9e415-faa4-732f-37ee-41c9303cd977@gmail.com>
From: "Card, Stu" <stu.card@axenterprize.com>
Date: Fri, 26 Mar 2021 08:45:23 -0400
Message-ID: <CAKM0pYPc_yFM0Kk6Yhar1Dwa1fUAOEhx3ELx=Z=+23WR85yFsA@mail.gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: "tm-rid@ietf.org" <tm-rid@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005c35a305be6fe803"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/xkaWQiR57bheQuF3x2Gpd8zb8Q4>
Subject: Re: [Drip] The remote ID and/or FAA?
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: Fri, 26 Mar 2021 12:46:03 -0000

Yes, we are attempting to satisfy that rule with DRIP, using a HHIT as the
UAS ID.
FAA has already published their "final" rule in the Federal Register, so
won't be referring to our draft.
Once DRIP has at least one published RFC, we may be able to get ASTM and/or
CAAs (inc. FAA) to refer to it,
not as a baseline standard, but as at least a means for providing the
Session ID type of UAS ID, and maybe more.


On Fri, Mar 26, 2021 at 7:07 AM Alexandre Petrescu <
alexandre.petrescu@gmail.com> wrote:

> Hi,
>
> I got pointed to a regulation from FAA which seems to be saying "The
> required message elements include: (1) a unique identifier to establish
> the identity of the unmanned aircraft; (2) an indication of the..."
>
> Maybe what they say "unique id" relates the one considered here in DRIP
> draft-ietf-drip-rid-07 or maybe in the future or so.
>
> https://www.faa.gov/news/media/attachments/RemoteID_Final_Rule.pdf
>
> Ideally FAA would simply refer to the draft - it would be easier to find.
>
> Alex
>
> --
> Tm-rid mailing list
> Tm-rid@ietf.org
> https://www.ietf.org/mailman/listinfo/tm-rid
>

v2.23.0 | Report a Bug | By Email