[Drip] RFC 9434 on Drone Remote Identification Protocol (DRIP) Architecture
rfc-editor@rfc-editor.org Tue, 18 July 2023 05:33 UTC
Return-Path: <wwwrun@rfcpa.amsl.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 7E9A5C15107B; Mon, 17 Jul 2023 22:33:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.853
X-Spam-Level:
X-Spam-Status: No, score=-0.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8gvJWgHGT9Yj; Mon, 17 Jul 2023 22:33:37 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F6C9C169508; Mon, 17 Jul 2023 22:33:30 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id EA09B19E2DF1; Mon, 17 Jul 2023 22:33:29 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, tm-rid@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230718053329.EA09B19E2DF1@rfcpa.amsl.com>
Date: Mon, 17 Jul 2023 22:33:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/elarCY68ZirqJyKqZzoTjL6BZ5g>
Subject: [Drip] RFC 9434 on Drone Remote Identification Protocol (DRIP) Architecture
X-BeenThere: tm-rid@ietf.org
X-Mailman-Version: 2.1.39
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, 18 Jul 2023 05:33:37 -0000
A new Request for Comments is now available in online RFC libraries. RFC 9434 Title: Drone Remote Identification Protocol (DRIP) Architecture Author: S. Card, A. Wiethuechter, R. Moskowitz, S. Zhao, Ed., A. Gurtov Status: Informational Stream: IETF Date: July 2023 Mailbox: stu.card@axenterprize.com, adam.wiethuechter@axenterprize.com, rgm@labs.htt-consult.com, shuai.zhao@ieee.org, gurtov@acm.org Pages: 28 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-drip-arch-31.txt URL: https://www.rfc-editor.org/info/rfc9434 DOI: 10.17487/RFC9434 This document describes an architecture for protocols and services to support Unmanned Aircraft System Remote Identification and tracking (UAS RID), plus UAS-RID-related communications. This architecture adheres to the requirements listed in the Drone Remote Identification Protocol (DRIP) Requirements document (RFC 9153). This document is a product of the Drone Remote ID Protocol Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC
- [Drip] RFC 9434 on Drone Remote Identification Pr… rfc-editor
- Re: [Drip] RFC 9434 on Drone Remote Identificatio… mohamed.boucadair