Re: [ipwave] RFC 9365 on IPv6 Wireless Access in Vehicular Environments (IPWAVE): Problem Statement and Use Cases

Russ Housley <housley@vigilsec.com> Wed, 15 March 2023 21:49 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: its@ietfa.amsl.com
Delivered-To: its@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D117C15155C for <its@ietfa.amsl.com>; Wed, 15 Mar 2023 14:49:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 ItvFOH7qjH7V for <its@ietfa.amsl.com>; Wed, 15 Mar 2023 14:49:10 -0700 (PDT)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (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 5EC7DC14CF13 for <its@ietf.org>; Wed, 15 Mar 2023 14:49:10 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 427559CC06 for <its@ietf.org>; Wed, 15 Mar 2023 17:49:09 -0400 (EDT)
Received: from [10.196.196.251] (148-196.icannmeeting.org [199.91.196.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 236109CB93 for <its@ietf.org>; Wed, 15 Mar 2023 17:49:09 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Date: Wed, 15 Mar 2023 17:49:08 -0400
References: <20230315210337.B209410D75@rfcpa.amsl.com>
To: its@ietf.org
In-Reply-To: <20230315210337.B209410D75@rfcpa.amsl.com>
Message-Id: <DB3F2AEB-8516-4B97-944E-767F2364BC3A@vigilsec.com>
X-Mailer: Apple Mail (2.3445.104.21)
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/7FlnGAGh3_FOEgVpEc5sJv3zCX0>
Subject: Re: [ipwave] RFC 9365 on IPv6 Wireless Access in Vehicular Environments (IPWAVE): Problem Statement and Use Cases
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF <its.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/its>, <mailto:its-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/its/>
List-Post: <mailto:its@ietf.org>
List-Help: <mailto:its-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/its>, <mailto:its-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Mar 2023 21:49:14 -0000

Congratulations to the author team for finishing the publication process.

Russ


> On Mar 15, 2023, at 5:03 PM, rfc-editor@rfc-editor.org wrote:
> 
> 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