IETF Logo Mail Archive

Re: [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local

Carsten Bormann <cabo@tzi.org> Tue, 24 September 2013 08:56 UTC

Return-Path: <cabo@tzi.org>
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 6FD6A21E8064 for <roll@ietfa.amsl.com>; Tue, 24 Sep 2013 01:56:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.16
X-Spam-Level:
X-Spam-Status: No, score=-106.16 tagged_above=-999 required=5 tests=[AWL=0.089, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 cB2Azul-KFYR for <roll@ietfa.amsl.com>; Tue, 24 Sep 2013 01:56:10 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 588F011E80D3 for <roll@ietf.org>; Tue, 24 Sep 2013 01:56:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r8O8u8WJ007983 for <roll@ietf.org>; Tue, 24 Sep 2013 10:56:08 +0200 (CEST)
Received: from [192.168.217.105] (p548903C6.dip0.t-ipconnect.de [84.137.3.198]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 13054CA4; Tue, 24 Sep 2013 10:56:08 +0200 (CEST)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <4518F39EB578034D8C99A9B7776CDBA301B6762F@xmb-aln-x04.cisco.com>
Date: Tue, 24 Sep 2013 10:56:07 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <267C5CE2-8424-431B-A680-93EA1E725AE3@tzi.org>
References: <067.7473226c34e99536104b136c326ce300@trac.tools.ietf.org> <082.43d952a80486426da0d4499c38c22294@trac.tools.ietf.org> <5691.1379703742@sandelman.ca> <4518F39EB578034D8C99A9B7776CDBA301B6762F@xmb-aln-x04.cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
X-Mailer: Apple Mail (2.1510)
Subject: Re: [Roll] [roll] #132: draft-ietf-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: 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: Tue, 24 Sep 2013 08:56:16 -0000

On Sep 24, 2013, at 10:49, "Ralph Droms (rdroms)" <rdroms@cisco.com> wrote:

>>>  When used in an IP-over-IEEE802.15.4 network, "scop 3" is defined to
>>> include all interfaces participating in the IEEE802.15.4 multi-link
>>> subnet.

While this solves the special case of a 6LoWPAN (it might actually want to use the term 6LoWPAN for that), I always understood the RPL approach to go beyond networks delimited by the use of a specific link layer technology.

Wouldn't it be natural to have a MPL scope be congruent with the network covered by a RPL scope?
(Now, there may be several of those around in a network, but I'd at least try to start from there.)

Again, this is a natural thing to do in a 6LoWPAN, we just seem to lack the term for a scope that happens to include other than 802.15.4 radios.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email