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

Ralph Droms <rdroms.ietf@gmail.com> Tue, 24 September 2013 09:09 UTC

Return-Path: <rdroms.ietf@gmail.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 60E5F21F9C90 for <roll@ietfa.amsl.com>; Tue, 24 Sep 2013 02:09:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 gMgMesyBj1Pj for <roll@ietfa.amsl.com>; Tue, 24 Sep 2013 02:09:02 -0700 (PDT)
Received: from mail-qe0-x22b.google.com (mail-qe0-x22b.google.com [IPv6:2607:f8b0:400d:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 8E3DD21F9C05 for <roll@ietf.org>; Tue, 24 Sep 2013 02:09:02 -0700 (PDT)
Received: by mail-qe0-f43.google.com with SMTP id gh4so2900740qeb.2 for <roll@ietf.org>; Tue, 24 Sep 2013 02:08:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=D9JpE/FvP6n4vo0VwwrNJCklHN2yV/nWa+dcrmWrY6Q=; b=e0xoMEIo2jRa9DbMAqNEWy3VT19sy9PKX5rhYtJW9SV+DlV1yHWVP73in6eSqJa2Mj Np67xoSM5MiP4FAIyQVVYSKJTKoTIjTxN9RMXLsMdv3XWOMn0xABul5stStmgp+SRRkr BKhl47mjB1aMcaoufUEnOsQ3BS5qPbrdOliw7hrZUzmOkfm0FNFVrkbKgdIyzytcDEJ1 UpobClLXi9RWUr3Bzy9mNXDbfJGWLoBvz3doSIFS31NwQA4iXV1zkHiFKIY/7MSsOixD GiVkSgfaDQIHNv58YWx7e7lYh708CfF8OpNpsimfyXOOSn9fAb0jw1dsYWoHpmdh0YeG 1C9A==
X-Received: by 10.224.29.10 with SMTP id o10mr5130276qac.119.1380013738034; Tue, 24 Sep 2013 02:08:58 -0700 (PDT)
Received: from [10.86.255.218] (198-135-0-233.cisco.com. [198.135.0.233]) by mx.google.com with ESMTPSA id f5sm50548935qev.8.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 24 Sep 2013 02:08:57 -0700 (PDT)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <267C5CE2-8424-431B-A680-93EA1E725AE3@tzi.org>
Date: Tue, 24 Sep 2013 10:08:54 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <1A0F1183-B576-4CE0-90FF-1D3D2B811FED@gmail.com>
References: <067.7473226c34e99536104b136c326ce300@trac.tools.ietf.org> <082.43d952a80486426da0d4499c38c22294@trac.tools.ietf.org> <5691.1379703742@sandelman.ca> <4518F39EB578034D8C99A9B7776CDBA301B6762F@xmb-aln-x04.cisco.com> <267C5CE2-8424-431B-A680-93EA1E725AE3@tzi.org>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
X-Mailer: Apple Mail (2.1508)
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 09:09:03 -0000

On Sep 24, 2013, at 9:56 AM 9/24/13, Carsten Bormann <cabo@tzi.org> wrote:

> 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.)

Yeah, that issue came to mind when I thought about congruence between MPL and RPL scopes: how is some MPL message, marked as "scop 3", associated with a specific RPL scope when there are overlapping RPL scopes?

- Ralph

> 
> 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
> 
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll