Re: [Roll] trickle-mcast-04 - Clarify scope value of 3 - subnet-local

Robert Cragie <robert.cragie@gridmerge.com> Wed, 24 July 2013 16:47 UTC

Return-Path: <robert.cragie@gridmerge.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 50EB011E8115 for <roll@ietfa.amsl.com>; Wed, 24 Jul 2013 09:47:30 -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 z5QfNaBCNOdI for <roll@ietfa.amsl.com>; Wed, 24 Jul 2013 09:47:25 -0700 (PDT)
Received: from mail41.extendcp.co.uk (mail41.extendcp.co.uk [79.170.44.41]) by ietfa.amsl.com (Postfix) with ESMTP id 3CBC611E8151 for <roll@ietf.org>; Wed, 24 Jul 2013 09:47:23 -0700 (PDT)
Received: from [94.116.37.204] (helo=[10.38.244.130]) by mail41.extendcp.com with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) id 1V22Dh-0006VO-Nr for roll@ietf.org; Wed, 24 Jul 2013 17:47:21 +0100
Message-ID: <51F00519.1020604@gridmerge.com>
Date: Wed, 24 Jul 2013 17:47:21 +0100
From: Robert Cragie <robert.cragie@gridmerge.com>
Organization: Gridmerge Ltd.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: roll@ietf.org
References: <067.7473226c34e99536104b136c326ce300@trac.tools.ietf.org> <082.6ab8f10970432e6f2bb367aa0b632dda@trac.tools.ietf.org> <23575.1373577247@sandelman.ca> <4518F39EB578034D8C99A9B7776CDBA3793403@xmb-aln-x04.cisco.com> <4874.1373906541@sandelman.ca> <E045AECD98228444A58C61C200AE1BD841374DAF@xmb-rcd-x01.cisco.com> <38A9423D-BBD7-48E9-846F-C1360BEFEE85@gmail.com> <51EEC0F2.9010601@gridmerge.com> <1374658706.80014.YahooMailNeo@web142503.mail.bf1.yahoo.com> <18208.1374677909@sandelman.ca> <CAK=bVC9jA=p3dMVRLXCnrCN6b2-rmhYK_GKJk-rKVsEX3napRQ@mail.gmail.com>
In-Reply-To: <CAK=bVC9jA=p3dMVRLXCnrCN6b2-rmhYK_GKJk-rKVsEX3napRQ@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms050409090607080805010602"
X-Authenticated-As: robert.cragie@gridmerge.com
Subject: Re: [Roll] trickle-mcast-04 - Clarify scope value of 3 - subnet-local
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert.cragie@gridmerge.com, 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: Wed, 24 Jul 2013 16:47:30 -0000

Can you provide a practical example of how you would configure IPv6 
addresses for a simple RPL network comprised of, say, a DODAG root and 
two RPL routers at a rank above? And generally how route-over networks 
would work where interfaces are assigned solely a /128 prefix? 
Forbidding the use of a subnet prefix on the basis that link 
connectivity cannot be guaranteed seems rather odd to me.

Robert

On 24/07/2013 16:32, Ulrich Herberg wrote:
> I have pointed out two documents in my earlier email that explain in
> long detail why I believe that multi-hop subnets are a really bad
> idea. The AUTOCONF RFC 5889 presents an architecture for avoiding all
> these problems by using /128 prefixes. In that regards, a subnet wide
> flooding would be fairly uninteresting, as it would not go beyond a
> single router.
>
> Regards
> Ulrich
>
> On Wed, Jul 24, 2013 at 7:58 AM, Michael Richardson
> <mcr+ietf@sandelman.ca> wrote:
>> I would still like an explanation of why "subnet" is the wrong term.
>>
>> When would scope-3 would be used such that it would not correspond to the set
>> of links on which a "/64" (or other size) is used?
>>
>> --
>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>>
>>
>>
>> _______________________________________________
>> Roll mailing list
>> Roll@ietf.org
>> https://www.ietf.org/mailman/listinfo/roll
>>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>