Re: [Roll] [roll] #110: trickle-mcast: do applications receive all multicast, or just MPL encapsulated ones

Robert Cragie <robert.cragie@gridmerge.com> Thu, 01 November 2012 18:20 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 30C7721F8E7B for <roll@ietfa.amsl.com>; Thu, 1 Nov 2012 11:20:19 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RcmaQ6acHbvt for <roll@ietfa.amsl.com>; Thu, 1 Nov 2012 11:20:18 -0700 (PDT)
Received: from mail78.extendcp.co.uk (mail78.extendcp.co.uk [79.170.40.78]) by ietfa.amsl.com (Postfix) with ESMTP id 37B2021F8E31 for <roll@ietf.org>; Thu, 1 Nov 2012 11:20:18 -0700 (PDT)
Received: from client-86-25-47-150.midd-bam-1.adsl.virginmedia.com ([86.25.47.150] helo=[192.168.0.2]) by mail78.extendcp.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) id 1TTzNH-0001dZ-BH for roll@ietf.org; Thu, 01 Nov 2012 18:20:16 +0000
Message-ID: <5092BDA4.30607@gridmerge.com>
Date: Thu, 01 Nov 2012 18:21:24 +0000
From: Robert Cragie <robert.cragie@gridmerge.com>
Organization: Gridmerge Ltd.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: roll@ietf.org
References: <058.c053ae172b60ad763a419d3caf1dd7ac@trac.tools.ietf.org> <B50D0F163D52B74DA572DD345D5044AF0F6EFC09@xmb-rcd-x04.cisco.com>
In-Reply-To: <B50D0F163D52B74DA572DD345D5044AF0F6EFC09@xmb-rcd-x04.cisco.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms040605090600030106060709"
X-Authenticated-As: robert.cragie@gridmerge.com
Subject: Re: [Roll] [roll] #110: trickle-mcast: do applications receive all multicast, or just MPL encapsulated ones
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert.cragie@gridmerge.com
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: Thu, 01 Nov 2012 18:20:19 -0000

We could say that address has to be subscribed to by all MPL forwarders 
and SHOULD (MUST?) be used with a MPL Option. If the language in the 
draft were tightened up a bit regarding packet types, this would mean 
that if for some reason a packet to FF0X::MPL was originated without a 
MPL Option, it would be harmlessly (but wastefully) encapsulated and the 
chances are anything beyond the MPL domain would not be subscribed so 
would be ignored for that reason. Of course, if used with a MPL Option, 
no encapsulation is needed, there is a one-to-one mapping between the 
MPL domain and the address scope and it would not be forwarded on 
interfaces which don't understand MPL.

Robert


On 01/11/2012 4:08 PM, Jonathan Hui (johui) wrote:
> The FF0X::MPL multicast address serves to identify a group of MPL forwarders within an MPL domain.
>
> I think if any device sends a packet to FF0X::MPL, it should be delivered to and processed by all devices subscribed to that address.
>
> Thoughts from others?
>
> --
> Jonathan Hui
>
> On Nov 1, 2012, at 7:47 AM, roll issue tracker <trac+roll@trac.tools.ietf.org>; wrote:
>
>> #110: trickle-mcast: do applications receive all multicast, or just MPL
>> encapsulated ones
>>
>> There's still the case that multicasts from non-MPL nodes are received by
>> MPL-forwarder-nodes
>> (presumably). Should there be guidelines here? Example: if an application
>> on my MPL-forwarder node
>> joins multicast group FF05::1234, will the application then receive IP
>> multicasts sent
>> with destination FF05::1234, or will it only receive those IP multicasts
>> to FF05::1234
>> that were delivered encapsulated in an FF0X::MPL packet ?
>>
>> That decision could be out of scope; but on the other hand may lead to
>> different
>> implementers making different choices here.
>>
>> -- 
>> -----------------------------+---------------------------------------------
>> Reporter:  mcr@…            |      Owner:  draft-ietf-roll-trickle-mcast@…
>>      Type:  enhancement      |     Status:  new
>> Priority:  major            |  Milestone:
>> Component:  trickle-mcast    |    Version:
>> Severity:  In WG Last Call  |   Keywords:
>> -----------------------------+---------------------------------------------
>>
>> Ticket URL: <https://svn.tools.ietf.org/wg/roll/trac/ticket/110>
>> roll <http://tools.ietf.org/wg/roll/>
>>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>