IETF Logo Mail Archive

Re: [Roll] [roll] #105: trickle-mcast: how to determine scope of MPL domain

Dario Tedeschi <dat@exegin.com> Fri, 02 November 2012 00:59 UTC

Return-Path: <dat@exegin.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 4802121F98A1 for <roll@ietfa.amsl.com>; Thu, 1 Nov 2012 17:59:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.565
X-Spam-Level:
X-Spam-Status: No, score=-2.565 tagged_above=-999 required=5 tests=[AWL=1.034, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 SIAZbNFqDXlm for <roll@ietfa.amsl.com>; Thu, 1 Nov 2012 17:59:22 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id CD6B221F98A5 for <roll@ietf.org>; Thu, 1 Nov 2012 17:59:21 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id ro8so2096384pbb.31 for <roll@ietf.org>; Thu, 01 Nov 2012 17:59:21 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=eZu/XvzO5F+WnRrAnp/U8ybuBhU7eIHSyc0hnjdJRm8=; b=h7Pg6JhC7j5DkJnST77rZfpRYn1y+QExsJmJ4h5AMEFjD7RZ3IIZBnqDnXUWSpveGJ FlYzZ84dqaVfBkCF1qCL6NRVDruYbyHid/NRXkFHyq356Sio9M7Wun6JYMpIQfkJE9Tx ECjpijzsqiMo5Z6/n67eIOB3bqOB9BnZen662mpQ1OCMvUguJKXELY6ba7n9etCOFRzM bNFbVbUh3p6GkbI0whRX/OylXYo1cuAKDrevqBDinMijAdKkqTk9IzWo4675Rpp4qadI hkmmP0c65UvAGZONnEjW2Sp0Gw2Kv46XhTHWS6Wl37kLk5XzKCxxajN1nMtRnz1D26VC sWDg==
Received: by 10.66.83.201 with SMTP id s9mr328940pay.74.1351817961440; Thu, 01 Nov 2012 17:59:21 -0700 (PDT)
Received: from [172.16.1.52] ([184.71.143.130]) by mx.google.com with ESMTPS id j10sm4778030pax.8.2012.11.01.17.59.19 (version=SSLv3 cipher=OTHER); Thu, 01 Nov 2012 17:59:20 -0700 (PDT)
Message-ID: <50931AE9.9030800@exegin.com>
Date: Thu, 01 Nov 2012 17:59:21 -0700
From: Dario Tedeschi <dat@exegin.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0) Gecko/20110922 Thunderbird/7.0
MIME-Version: 1.0
To: "Jonathan Hui (johui)" <johui@cisco.com>
References: <058.e817419e990e1afb26be9aa25d5cfc21@trac.tools.ietf.org> <B50D0F163D52B74DA572DD345D5044AF0F6EF7A3@xmb-rcd-x04.cisco.com>
In-Reply-To: <B50D0F163D52B74DA572DD345D5044AF0F6EF7A3@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Gm-Message-State: ALoCoQnAXoP68QPp/nx1hQFb6t4CLaBg6cxEqwiKYpvaCJdnZPGpE4wUhdvArAVV2Idp0OjNsMdu
Cc: "<roll@ietf.org>" <roll@ietf.org>, "<draft-ietf-roll-trickle-mcast@tools.ietf.org>" <draft-ietf-roll-trickle-mcast@tools.ietf.org>, "<mcr@sandelman.ca>" <mcr@sandelman.ca>
Subject: Re: [Roll] [roll] #105: trickle-mcast: how to determine scope of MPL domain
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Fri, 02 Nov 2012 00:59:23 -0000

I'm not so sure. What if, for example, I connected my BR to an existing 
network that already had say scope 4 (admin-scope) configured to cover a 
wider domain than just the PAN. I then could not configure the BR to 
report 4 as the scope of the PAN (the "MPL scope"). Yes, one could use 
scope 3, but it is currently reserved. Besides, it wouldn't really solve 
the problem, if you consider that scope 3 could quite easily also cover 
a wider domain than just the PAN.

This is where unicast-prefix-based multicast addressing would become 
useful. It would remove the need for an "MPL scope", since the MPL 
domain would be defined by the PAN's prefix.

- Dario


On 01/11/2012 8:28 AM, Jonathan Hui (johui) wrote:
> If the draft indicates that the MPL domain scope is a required configuration parameter, would that be sufficient?
>
> --
> Jonathan Hui
>
> On Oct 31, 2012, at 7:37 AM, roll issue tracker<trac+roll@trac.tools.ietf.org>  wrote:
>
>> #105: trickle-mcast: how to determine scope of MPL domain
>>
>> There's no explanation on how a node would determine what scope
>> corresponds
>> to a MPL domain. How would it do that without being given some additional
>> information from the edge-router/s. I think what is needed, here, is some
>> multicast routing information from the edge-router/s.
>>
>> -- 
>> -----------------------------+---------------------------------------------
>> Reporter:  mcr@…            |      Owner:  draft-ietf-roll-trickle-mcast@…
>>      Type:  defect           |     Status:  new
>> Priority:  major            |  Milestone:
>> Component:  trickle-mcast    |    Version:
>> Severity:  In WG Last Call  |   Keywords:
>> -----------------------------+---------------------------------------------
>>
>> Ticket URL:<http://trac.tools.ietf.org/wg/roll/trac/ticket/105>
>> roll<http://tools.ietf.org/wg/roll/>
>>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll

v2.23.0 | Report a Bug | By Email