[rfc-dist] RFC 9365 on IPv6 Wireless Access in Vehicular Environments (IPWAVE): Problem Statement and Use Cases
rfc-editor@rfc-editor.org Wed, 15 March 2023 21:03 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2E95C14F747; Wed, 15 Mar 2023 14:03:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.648
X-Spam-Level:
X-Spam-Status: No, score=-6.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 2iJ5b3su_tug; Wed, 15 Mar 2023 14:03:37 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [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 E2C68C14CE38; Wed, 15 Mar 2023 14:03:37 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id B209410D75; Wed, 15 Mar 2023 14:03:37 -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, its@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230315210337.B209410D75@rfcpa.amsl.com>
Date: Wed, 15 Mar 2023 14:03:37 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/JtPKu-goSlWUFvNUJ7EL-mFA2Hc>
Subject: [rfc-dist] RFC 9365 on IPv6 Wireless Access in Vehicular Environments (IPWAVE): Problem Statement and Use Cases
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Mar 2023 21:03:42 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9365
Title: IPv6 Wireless Access in Vehicular
Environments (IPWAVE): Problem Statement and
Use Cases
Author: J. Jeong, Ed.
Status: Informational
Stream: IETF
Date: March 2023
Mailbox: pauljeong@skku.edu
Pages: 47
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ipwave-vehicular-networking-30.txt
URL: https://www.rfc-editor.org/info/rfc9365
DOI: 10.17487/RFC9365
This document discusses the problem statement and use cases of
IPv6-based vehicular networking for Intelligent Transportation
Systems (ITS). The main scenarios of vehicular communications are
vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and
vehicle-to-everything (V2X) communications. First, this document
explains use cases using V2V, V2I, and V2X networking. Next, for
IPv6-based vehicular networks, it makes a gap analysis of current
IPv6 protocols (e.g., IPv6 Neighbor Discovery, mobility management,
as well as security and privacy).
This document is a product of the IP Wireless Access in Vehicular Environments 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