IETF Logo Mail Archive

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

"roll issue tracker" <trac+roll@trac.tools.ietf.org> Wed, 31 October 2012 14:37 UTC

Return-Path: <trac+roll@trac.tools.ietf.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 E808F21F87F9 for <roll@ietfa.amsl.com>; Wed, 31 Oct 2012 07:37:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.044
X-Spam-Level:
X-Spam-Status: No, score=-102.044 tagged_above=-999 required=5 tests=[AWL=0.555, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 nG1MQ4lxqLh8 for <roll@ietfa.amsl.com>; Wed, 31 Oct 2012 07:37:28 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 4860E21F86A2 for <roll@ietf.org>; Wed, 31 Oct 2012 07:37:28 -0700 (PDT)
Received: from localhost ([127.0.0.1]:47211 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from <trac+roll@trac.tools.ietf.org>) id 1TTZQ2-0004Hx-Ub; Wed, 31 Oct 2012 15:37:22 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: roll issue tracker <trac+roll@trac.tools.ietf.org>
X-Trac-Version: 0.12.2
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.2, by Edgewall Software
To: draft-ietf-roll-trickle-mcast@tools.ietf.org, mcr@sandelman.ca
X-Trac-Project: roll
Date: Wed, 31 Oct 2012 14:37:22 -0000
X-URL: http://tools.ietf.org/wg/roll/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/roll/trac/ticket/105
Message-ID: <058.e817419e990e1afb26be9aa25d5cfc21@trac.tools.ietf.org>
X-Trac-Ticket-ID: 105
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-roll-trickle-mcast@tools.ietf.org, mcr@sandelman.ca, roll@ietf.org
X-SA-Exim-Mail-From: trac+roll@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: jonhui@cisco.com, richard.kelsey@silabs.com
Resent-Message-Id: <20121031143728.4860E21F86A2@ietfa.amsl.com>
Resent-Date: Wed, 31 Oct 2012 07:37:28 -0700
Resent-From: trac+roll@trac.tools.ietf.org
Cc: roll@ietf.org
Subject: [Roll] [roll] #105: trickle-mcast: how to determine scope of MPL domain
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: 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: Wed, 31 Oct 2012 14:37:29 -0000

#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/>

v2.23.0 | Report a Bug | By Email