Re: [Roll] [6lo] Fwd: New Version Notification for draft-ietf-6man-multicast-scopes-02.txt

"Pascal Thubert (pthubert)" <> Thu, 14 November 2013 23:52 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E794611E8159; Thu, 14 Nov 2013 15:52:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -10.47
X-Spam-Status: No, score=-10.47 tagged_above=-999 required=5 tests=[AWL=0.129, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vCEib7-x3DMh; Thu, 14 Nov 2013 15:52:31 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 1B33221E80E2; Thu, 14 Nov 2013 15:52:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=3682; q=dns/txt; s=iport; t=1384473147; x=1385682747; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=Vyzuw+lEYJ9etDV5M0FmxqXCnnbtQ4nyjYLgV02S98I=; b=iPEY83wo6xkIDkBSOuE/WKWM/IxFnFJZHKY6I/1GzOxK0z7DBf0QIJkA YSR0QxxLBunuQZqymxJumnkYkT8BG1PxtfljU5aIY8Q/KUv/pSpnl0pNg wpnljc+yCXq4lYXWlur4FvfsfIBoFqEBMSpMXIzSXjgJ+of12/9NA4B9h c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="4.93,702,1378857600"; d="scan'208";a="285024770"
Received: from ([]) by with ESMTP; 14 Nov 2013 23:52:26 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id rAENqQqn004842 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 14 Nov 2013 23:52:26 GMT
Received: from ([]) by ([]) with mapi id 14.03.0123.003; Thu, 14 Nov 2013 17:52:26 -0600
From: "Pascal Thubert (pthubert)" <>
To: Tim Chown <>, Brian Haberman <>
Thread-Topic: [6lo] Fwd: New Version Notification for draft-ietf-6man-multicast-scopes-02.txt
Thread-Index: AQHO4RreZ/MxlpffAEipYTllbECB/ZolWRhg
Date: Thu, 14 Nov 2013 23:52:25 +0000
Deferred-Delivery: Thu, 14 Nov 2013 23:50:00 +0000
Message-ID: <>
References: <> <> <> <> <> <> <> <EMEW3|14ec5fdd57568988316140abbd6b7acbpAD9L703tjc||>
In-Reply-To: <EMEW3|14ec5fdd57568988316140abbd6b7acbpAD9L703tjc||>
Accept-Language: fr-FR, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Routing Lossy networks Over Low power and <>, "Ralph Droms (rdroms)" <>, " IPv6 List" <>, "" <>
Subject: Re: [Roll] [6lo] Fwd: New Version Notification for draft-ietf-6man-multicast-scopes-02.txt
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <>
List-Id: Routing Over Low power and Lossy networks <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 14 Nov 2013 23:52:36 -0000

Hello Tim;

The 6TiSCH architecture documents a use case whereby a large (RPL based) LLN is federated by an higher speed backbone such as Ethernet that mostly spans the LLN.
The LLN is partitioned by RPL in multiple DODAGs, and the roots of the DODAGs connect to the backbone to provide end to end connectivity over the formed multilink subnet.
The LLN probably forms a single RPL Domain though we have not discussed that yet. Discussing with Ralph, I understand that the RPL domain is 03 and the whole multilink subnet is 04.
It results that we cannot address a single RPL instance or a single DODAG as a scope. The intersection with 802.15.4 PAN-ID still troubles me a bit but that's another thread. 



-----Original Message-----
From: Tim Chown [] 
Sent: jeudi 14 novembre 2013 03:21
To: Pascal Thubert (pthubert)
Cc: Brian Haberman; Routing Lossy networks Over Low power and;; IPv6 List; Ralph Droms (rdroms)
Subject: Re: [6lo] Fwd: New Version Notification for draft-ietf-6man-multicast-scopes-02.txt

On 14 Nov 2013, at 05:51, Pascal Thubert (pthubert) <> wrote:

> Hello Brian:
> 03 seems to derive from autonomic behavior, whereas 04 derives from admin. I do not see there a direct indication that 03 is contained in 04 though in the deployments I have in mind it would certainly be the case. Whether we want to enforce or on the contrary do not want to enforce the nesting is probably something we want to clarify.

Are there use cases documented somewhere in a 6lo or 6lo-related draft?

I'm interested as we're updating the homenet text about multicast scopes.  We have agreed some text in principle with Brian for that, but it's interesting because we may, indeed are likely to, have 6lo networks within future IPv6 home networks.


> -----Original Message-----
> From: Brian Haberman [] 
> Sent: mercredi 13 novembre 2013 07:22
> To: Pascal Thubert (pthubert)
> Cc: Ralph Droms (rdroms); Routing Lossy networks Over Low power and; IPv6 List;
> Subject: Re: [6lo] Fwd: New Version Notification for draft-ietf-6man-multicast-scopes-02.txt
> Pascal,
> On 11/12/13 5:04 PM, Ralph Droms (rdroms) wrote:
>> The document has been accepted as a WG work item.  Check out 
>> 2.txt
>> On Nov 12, 2013, at 5:00 PM 11/12/13, "Pascal Thubert (pthubert)" <> wrote:
>>> Hello Ralph:
>>> does not seem to contains the section you're inlining. The only diff I found was -specific going -local.
>>> As we are at it, would we be ahead of ourselves if that the draft also specifies that a collection of RPL DODAGs of a same instance federated over an isolated backbone (such as a VLAN) in an 04 ?.
>>> If I may add, there is kind of an habit that scopes are nested. Seems that we are going away from that assumption and maybe it would be good to have a sentence saying that?
> Scopes are still nested.  See RFC 4007.  Are you saying that this document is changing that?
> Regards,
> Brian
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> Administrative Requests:
> --------------------------------------------------------------------