Re: [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local

"roll issue tracker" <trac+roll@trac.tools.ietf.org> Mon, 14 October 2013 18:18 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 043BE11E81A5 for <roll@ietfa.amsl.com>; Mon, 14 Oct 2013 11:18:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O26zehcqcTZk for <roll@ietfa.amsl.com>; Mon, 14 Oct 2013 11:18:02 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 745F611E8152 for <roll@ietf.org>; Mon, 14 Oct 2013 11:18:02 -0700 (PDT)
Received: from localhost ([127.0.0.1]:48502 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+roll@trac.tools.ietf.org>) id 1VVmiK-0005M1-HR; Mon, 14 Oct 2013 20:17:56 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: roll issue tracker <trac+roll@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: johui@cisco.com, mariainesrobles@gmail.com, rdroms@cisco.com, mcr@sandelman.ca
X-Trac-Project: roll
Date: Mon, 14 Oct 2013 18:17:56 -0000
X-URL: http://tools.ietf.org/wg/roll/
X-Trac-Ticket-URL: https://svn.tools.ietf.org/wg/roll/trac/ticket/132#comment:8
Message-ID: <082.0e60a05a9e9a33903054243f518f8668@trac.tools.ietf.org>
References: <067.7473226c34e99536104b136c326ce300@trac.tools.ietf.org>
X-Trac-Ticket-ID: 132
In-Reply-To: <067.7473226c34e99536104b136c326ce300@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: johui@cisco.com, mariainesrobles@gmail.com, rdroms@cisco.com, 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
Cc: roll@ietf.org
Subject: Re: [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local
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: Mon, 14 Oct 2013 18:18:06 -0000

#132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local


Comment (by mariainesrobles@gmail.com):

 From: Robert Cragie <robert.cragie at gridmerge.com>
 Date: Mon, 14 Oct 2013 15:06:25 +0100

 Source: http://www.ietf.org/mail-archive/web/roll/current/msg08224.html

 "I would propose adding the language to draft-ietf-roll-trickle-mcast.
 There doesn't seem much point to doing another "world's shortest RFC".

 Here's an attempt at combining Ralph's text with the terminology in the
 draft:

 =================


 OLD


 By default, an MPL Forwarder SHOULD participate in an MPL Domain
 identified by the ALL_MPL_FORWARDERS multicast address with a scope value
 of 3 (Realm-Local) [I-D.droms-6man-multicast-scopes]. When used with MPL,
 Realm-Local scope is administratively defined and used to define the
 boundaries of multicast message dissemination by MPL.



 NEW


 By default, an MPL Forwarder SHOULD participate in an MPL Domain where the
 MPL Domain Address is the ALL_MPL_FORWARDERS multicast address with a
 scope value of 3 (Realm-Local) [I-D.droms-6man-multicast-scopes]. When
 used with MPL, Realm-Local scope is defined according to the underlying
 network technology; for example, when used in an IP-over-IEEE802.15.4
 network, Realm-Local scope is defined to include the set of MPL Interfaces
 sharing a PAN ID.

 An MPL Forwarder MAY participate in an MPL Domain where the MPL Domain
 Address uses a scope value of 4 (Admin-Local) [I-D.droms-6man-multicast-
 scopes]. When used with MPL, Admin-Local scope can be used in deployments
 that use administratively defined scopes that cover, for example, subnets
 based on different underlying network technologies.
 =================

 Robert "

-- 
---------------------------------------+------------------------------
 Reporter:  mariainesrobles@gmail.com  |       Owner:  johui@cisco.com
     Type:  defect                     |      Status:  reopened
 Priority:  major                      |   Milestone:
Component:  trickle-mcast              |     Version:
 Severity:  In WG Last Call            |  Resolution:
 Keywords:                             |
---------------------------------------+------------------------------

Ticket URL: <https://svn.tools.ietf.org/wg/roll/trac/ticket/132#comment:8>
roll <http://tools.ietf.org/wg/roll/>