Re: [Roll] Dissenting technical arguments unwelcome

Richard Kelsey <Richard.Kelsey@silabs.com> Fri, 26 July 2013 13:55 UTC

Return-Path: <Richard.Kelsey@silabs.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E61FA21F9929; Fri, 26 Jul 2013 06:55:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9jcPzLMUgli6; Fri, 26 Jul 2013 06:55:09 -0700 (PDT)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0188.outbound.messaging.microsoft.com [213.199.154.188]) by ietfa.amsl.com (Postfix) with ESMTP id 3C70721F979E; Fri, 26 Jul 2013 06:55:09 -0700 (PDT)
Received: from mail206-db8-R.bigfish.com (10.174.8.247) by DB8EHSOBE010.bigfish.com (10.174.4.73) with Microsoft SMTP Server id 14.1.225.22; Fri, 26 Jul 2013 13:55:08 +0000
Received: from mail206-db8 (localhost [127.0.0.1]) by mail206-db8-R.bigfish.com (Postfix) with ESMTP id E4BAE2E0404; Fri, 26 Jul 2013 13:55:07 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.238.53; KIP:(null); UIP:(null); IPV:NLI; H:BY2PRD0712HT002.namprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -4
X-BigFish: PS-4(zz9371IfadId79ah1432I217bIzz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1de097hz2fh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1155h)
Received-SPF: pass (mail206-db8: domain of silabs.com designates 157.56.238.53 as permitted sender) client-ip=157.56.238.53; envelope-from=Richard.Kelsey@silabs.com; helo=BY2PRD0712HT002.namprd07.prod.outlook.com ; .outlook.com ;
Received: from mail206-db8 (localhost.localdomain [127.0.0.1]) by mail206-db8 (MessageSwitch) id 1374846906442076_5477; Fri, 26 Jul 2013 13:55:06 +0000 (UTC)
Received: from DB8EHSMHS005.bigfish.com (unknown [10.174.8.254]) by mail206-db8.bigfish.com (Postfix) with ESMTP id 5D94C20046; Fri, 26 Jul 2013 13:55:06 +0000 (UTC)
Received: from BY2PRD0712HT002.namprd07.prod.outlook.com (157.56.238.53) by DB8EHSMHS005.bigfish.com (10.174.4.15) with Microsoft SMTP Server (TLS) id 14.16.227.3; Fri, 26 Jul 2013 13:55:03 +0000
Received: from BY2PRD0712MB672.namprd07.prod.outlook.com ([169.254.9.196]) by BY2PRD0712HT002.namprd07.prod.outlook.com ([10.255.246.35]) with mapi id 14.16.0329.000; Fri, 26 Jul 2013 13:55:03 +0000
From: Richard Kelsey <Richard.Kelsey@silabs.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] Dissenting technical arguments unwelcome
Thread-Index: AQHOiW8hRTZW/S68x06bEju446IrDpl2p3iAgABT8b4=
Date: Fri, 26 Jul 2013 13:55:02 +0000
Message-ID: <E2B1032886993B4A92464C7BA66218211C0AFF9B@BY2PRD0712MB672.namprd07.prod.outlook.com>
References: <CAK=bVC_Fdq9=bEg1+_2bqFgV_3EmMQ12vt8_+0mS1coxotsf-g@mail.gmail.com> <23549.1374781215@sandelman.ca>, <CANK0pbYTMjS-u9tft52sGtijJT0YtLfQTTiOY2zF28LUcrQpbw@mail.gmail.com>
In-Reply-To: <CANK0pbYTMjS-u9tft52sGtijJT0YtLfQTTiOY2zF28LUcrQpbw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [173.48.253.81]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: silabs.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-Mailman-Approved-At: Fri, 26 Jul 2013 10:58:04 -0700
Cc: "6man@ietf.org" <6man@ietf.org>
Subject: Re: [Roll] Dissenting technical arguments unwelcome
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jul 2013 13:55:16 -0000

From: Emmanuel Baccelli [Emmanuel.Baccelli@inria.fr]
Sent: Friday, July 26, 2013 4:50 AM

> As Ulrich mentioned, the conclusion of AUTOCONF was that IP links as
> we know them do *not* make sense in a spontaneous wireless multi-hop
> environment.
> 
> This conclusion was documented in RFC 5889, which essentially bans
> the use of subnet prefixes in this environment. And without subnet
> prefixes, what is the purpose of an IP link? Not much...

Hi Emmanuel,

While I generally agree with what RFC 5889 says, its focus is on
autoconfiguration.  For example, the statement

   o  There is no mechanism to ensure that IPv6 link-local addresses
      are unique across multiple links, hence they can not be used to
      reliably identify routers.

is true only if restricted to autoconfiguration mechanisms.

To the extent that RFC 5889, which is informational, bans anything,
it bans using autoconfiguration to configure addresses with subnet
prefixes in this sort of network.  It says nothing one way or the
other about using, say, DHCPv6 or 6LoWPAN ND to do so.

The whole multi-link subnet discussion is difficult because the term
'subnet' has different implications in different contexts.  For
example, RFC 5889 says:

   Subnet prefix configuration on such interfaces must thus not make any
   promises in terms of direct (one hop) IP connectivity to IP addresses
   other than that of the interface itself.  This suggests the following
   principle:

   o  no two such interfaces in the network should be configured with
      the same subnet prefix.

An equally valid principle would have been:

   o  subnet prefixes should not be used for on-link determination
      for such interfaces.

Which you prefer depends on how much you consider on-link determination
to be a fundamental aspect of subnet prefixes.  For autoconfiguration
it is a fundamental aspect; for routing, perhaps not.

I think it makes sense to follow RFC 5889's recommendation and assign
only /128 subnet prefixes to interfaces in an ad-hoc radio network.  I
also think it makes sense to arrange for those subnet prefixes to share
a single /64 prefix and to use that fact at the routing layer.  Whether
or not this is a multi-link subnet depends on who you ask.

-Richard Kelsey

This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product.  If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and  destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication.  
Thank you.