IETF Logo Mail Archive

Re: [ipwave] Comments for draft-ietf-ipwave-vehicular-networking-14.txt

Michael Richardson <mcr@sandelman.ca> Wed, 15 April 2020 14:18 UTC

Return-Path: <mcr@sandelman.ca>
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 6F77C3A08D1 for <its@ietfa.amsl.com>; Wed, 15 Apr 2020 07:18:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 jroJhYERTxpO for <its@ietfa.amsl.com>; Wed, 15 Apr 2020 07:18:54 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 835423A08CD for <its@ietf.org>; Wed, 15 Apr 2020 07:18:54 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 440A93897B; Wed, 15 Apr 2020 10:17:10 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id DD1CF602; Wed, 15 Apr 2020 10:18:51 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
cc: its <its@ietf.org>
In-Reply-To: <c407ff6c9ffe45c98e74609dae0b1419@boeing.com>
References: <c407ff6c9ffe45c98e74609dae0b1419@boeing.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <31884.1586960331.1@localhost>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 15 Apr 2020 10:18:51 -0400
Message-ID: <31885.1586960331@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/zxoBknDb6JrL968AlLzS0tjIPxA>
Subject: Re: [ipwave] Comments for draft-ietf-ipwave-vehicular-networking-14.txt
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.29
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 Apr 2020 14:18:58 -0000

Templin (US), Fred L <Fred.L.Templin@boeing.com> wrote:
    > Then, on the wireless links themselves, there are no on-link prefixes and no PIOs
    > advertised by access routers. The wireless links therefore carry only link-local or
    > MNP-addressed IPv6 packets, therefore no two vehicles will appear to be on the
    > same subnet and no multi-link issues for subnet partitions and merges occur. Also,
    > DAD is not needed at all due to the unique assignment of MNPs.

I think that this is a really good use of IPv6 technology.

    > This same model could be applied to ipwave vehicles, and would alleviate the problems
    > stated in Section 5. In particular, the link model could adopt the OMNI link model (see
    > the OMNI draft) where all nodes within the transportation system are "neighbors" on
    > a shared NBMA virtual link. IPv6 ND works with no modifications, and the link model is
    > always connected. So, there would be no need for vehicular extensions to IPv6 and ND.
    > Likewise, mobility management services would work the same as the ATN/IPS design
    > and would not require any adaptations for fast-moving vehicles.

+1

v2.23.0 | Report a Bug | By Email