Re: Wireless ND was: about violation of standards

Ole Troan <otroan@employees.org> Mon, 29 April 2019 08:56 UTC

Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 127FA1200F8 for <ipv6@ietfa.amsl.com>; Mon, 29 Apr 2019 01:56:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 zUoQTs2NauKC for <ipv6@ietfa.amsl.com>; Mon, 29 Apr 2019 01:56:46 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B01C012008A for <ipv6@ietf.org>; Mon, 29 Apr 2019 01:56:46 -0700 (PDT)
Received: from astfgl.hanazo.no (unknown [173.38.220.62]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id C6412FECBF9F; Mon, 29 Apr 2019 08:56:45 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id 87ED5143E189; Mon, 29 Apr 2019 10:56:42 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Subject: Re: Wireless ND was: about violation of standards
From: Ole Troan <otroan@employees.org>
In-Reply-To: <m1hKoNd-0000IQC@stereo.hq.phicoh.net>
Date: Mon, 29 Apr 2019 10:56:42 +0200
Cc: 6man WG <ipv6@ietf.org>, "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <36910145-BFD1-40D6-B62A-B8EC70B692F6@employees.org>
References: <bb7f7606-2adf-e669-8bcd-e41f17800782@gmail.com> <CAJE_bqd9frqX5-yeVPj8MYXpZ4737HqK1gmfD9cQV3A-Ea5HrQ@mail.gmail.com> <6bd5db47-408a-727e-5c13-f34a3465f986@si6networks.com> <CAJE_bqfTLqRbLp4fLu2ASZuZ+4G5c2G+RXkO92kXfLgPTqBnng@mail.gmail.com> <EEF00EA7-2AAF-403F-99AD-1D53ED18E8B3@cisco.com> <47631828-121F-402D-8165-969684C1101B@employees.org> <MN2PR11MB35655B36540829AEE5275964D8230@MN2PR11MB3565.namprd11.prod.outlook.com> <1066F69A-824F-4D6D-B221-8EFBAD15E15A@employees.org> <018c407a-b127-8724-d1ee-e19e3b084a60@gmail.com> <CABNhwV1jWHc1SMm=-xX0Oo5V4bo4VQBeQ5-CztJhP3y9006HRw@mail.gmail.com> <alpine.DEB.2.20.1904240659270.3490@uplift.swm.pp.se> <602A5CC5-170D-4E67-8907-A4D26606DB03@cisco.com> <m1hKoNd-0000IQC@stereo.hq.phicoh.net>
To: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/RmjT9bVHmYYdkPzMf5ZQURpjilQ>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2019 08:56:48 -0000

>> I started an informational draft for 6MAN on WiND (wireless ND) to
>> explain what physical models it serves and how it can be used over
>> several MAC layer abstractions.
> 
> I read draft-thubert-6man-ipv6-over-wireless-00. I quite like the
> description of the issues with wireless media.
> 
> There is however one thing I miss: The abstract says "This document describes
> how the original IPv6 Neighbor Discovery and Wireless ND (WiND) can be applied
> on various abstractions of wireless media."
> 
> I'm also interested in *why* WiND should be applied. In particular, Figure 2
> shows a complex multi-layered setup.
> 
> So my question is, why not use routing and keep subnets restricted to one
> link?
> 
> I hope there is a clear set of arguments why routing is not sufficient. 
> Right now it reads too much like a primitive routing protocol on top of ND.
> 
> Another issue that often shows up with registration based systems (such as
> quite common with IPv4 and wireless) is what happens if a host has more
> addresses than supported by the registration system?
> 
> I.e., it might scale better to have lots of point-to-point links and prefix
> delegation than to have a single big subnet and a hierarchical registration
> system.

That was my thinking too. If you have a set of p2p links, you don't need very little of ND.

Cheers,
Ole