[Roll] [roll] #109: trickle-mcast: should all MPL packets be destined to all-MPL-forwarders

"roll issue tracker" <trac+roll@trac.tools.ietf.org> Thu, 01 November 2012 14:34 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 1170721F8DC3 for <roll@ietfa.amsl.com>; Thu, 1 Nov 2012 07:34:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.46
X-Spam-Status: No, score=-102.46 tagged_above=-999 required=5 tests=[AWL=0.139, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id R9tv6n-Jo7gv for <roll@ietfa.amsl.com>; Thu, 1 Nov 2012 07:34:24 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org []) by ietfa.amsl.com (Postfix) with ESMTP id 7458B21F8DC2 for <roll@ietf.org>; Thu, 1 Nov 2012 07:34:24 -0700 (PDT)
Received: from localhost ([]:39587 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 1TTvqP-0003vR-4o; Thu, 01 Nov 2012 15:34:20 +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: Thu, 01 Nov 2012 14:34:05 -0000
X-URL: http://tools.ietf.org/wg/roll/
X-Trac-Ticket-URL: https://svn.tools.ietf.org/wg/roll/trac/ticket/109
Message-ID: <058.17a4c61a0b0575298f48df9ded41bd6b@trac.tools.ietf.org>
X-Trac-Ticket-ID: 109
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: <20121101143424.7458B21F8DC2@ietfa.amsl.com>
Resent-Date: Thu, 01 Nov 2012 07:34:24 -0700
Resent-From: trac+roll@trac.tools.ietf.org
Cc: roll@ietf.org
Subject: [Roll] [roll] #109: trickle-mcast: should all MPL packets be destined to all-MPL-forwarders
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: Thu, 01 Nov 2012 14:34:25 -0000

#109: trickle-mcast: should all MPL packets be destined to all-MPL-forwarders

 > 4. Destination address:

 Is there a reason to restrict the destination address of the MPL packet to
 the "all-MPL-forwarders" multicast address? Nodes that receives an MPL
 but don't understand the MPL option will discard it anyway.

 I think the most compelling reason is to remove yet another configuration
 parameter.  But allowing arbitrary multicast addresses to identify MPL
 would be necessary to support multiple MPL scope zones using the IPv6
 Address.  If we require encapsulation with link-local multicast, then an
 all-MPL-forwarders address would be ok.

 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/109>
roll <http://tools.ietf.org/wg/roll/>