IETF Logo Mail Archive

[ipwave] Route Information Options in IPv6 Neighbor Discovery

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Sun, 23 December 2018 16:24 UTC

Return-Path: <Fred.L.Templin@boeing.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 2DFAC12426E for <its@ietfa.amsl.com>; Sun, 23 Dec 2018 08:24:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 466rglPwjYd7 for <its@ietfa.amsl.com>; Sun, 23 Dec 2018 08:24:04 -0800 (PST)
Received: from clt-mbsout-02.mbs.boeing.net (clt-mbsout-02.mbs.boeing.net [130.76.144.163]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D8E112426A for <its@ietf.org>; Sun, 23 Dec 2018 08:24:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id wBNGO1db016262; Sun, 23 Dec 2018 11:24:01 -0500
Received: from XCH16-07-09.nos.boeing.com (xch16-07-09.nos.boeing.com [144.115.66.111]) by clt-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id wBNGNsnF015885 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL) for <its@ietf.org>; Sun, 23 Dec 2018 11:23:54 -0500
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-09.nos.boeing.com (144.115.66.111) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1591.10; Sun, 23 Dec 2018 08:23:52 -0800
Received: from XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8]) by XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8%2]) with mapi id 15.01.1591.012; Sun, 23 Dec 2018 08:23:52 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "its@ietf.org" <its@ietf.org>
Thread-Topic: Route Information Options in IPv6 Neighbor Discovery
Thread-Index: AdSa21+6FGreYgSCSK+NUPNEsCdBFA==
Date: Sun, 23 Dec 2018 16:23:52 +0000
Message-ID: <7492e4cc1b2140f09b37071b3e85d549@boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: B1ACD570458355DC346E65F5388A22C1149233C88D587F57F98756B9FD8567232000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/7Q5jLd2vuIV7kphiuQocd8mxuQw>
Subject: [ipwave] Route Information Options in IPv6 Neighbor Discovery
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: Sun, 23 Dec 2018 16:24:06 -0000

Here is a draft on including Route Information Options in IPv6 Neighbor
Discovery Messages:

https://datatracker.ietf.org/doc/draft-templin-6man-rio-redirect/

It allows for including Route Information Options (RIOs) in IPv6 ND
messages other than RAs. This is useful for vehicular nodes when the
node needs to inform neighbors of its delegated prefixes using NS
and NA messages (and sometimes also RS and Redirect). With this
method, an established IPv6 ND option is used for carrying routing
information without having to define a new IPv6 ND option type.
The draft also allows for the inclusion of "attributes" with the route
in case the RIO needs to include ancillary information besides just
prefix and prefix length.

We use this for our AERO proposal which has been discussed
widely for use in Unmanned Aerial Vehicles but also have
obvious implications for other vehicular applications. Please
review the draft and post any comments or insights.

Thanks - Fred

v2.23.0 | Report a Bug | By Email