IETF Logo Mail Archive

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> Fri, 11 October 2013 20: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 10D4821F9A70 for <roll@ietfa.amsl.com>; Fri, 11 Oct 2013 13:18:04 -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 zyoV2ida6+fp for <roll@ietfa.amsl.com>; Fri, 11 Oct 2013 13:18:03 -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 2BBD321F9A6D for <roll@ietf.org>; Fri, 11 Oct 2013 13:18:02 -0700 (PDT)
Received: from localhost ([127.0.0.1]:50052 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 1VUj9n-0002UD-7v; Fri, 11 Oct 2013 22:17:55 +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: Fri, 11 Oct 2013 20:17:55 -0000
X-URL: http://tools.ietf.org/wg/roll/
X-Trac-Ticket-URL: https://svn.tools.ietf.org/wg/roll/trac/ticket/132#comment:7
Message-ID: <082.6d923b56e89f979e00a33a1bab8bbfc5@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: Fri, 11 Oct 2013 20:18:04 -0000

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


Comment (by mariainesrobles@gmail.com):

 From: Ralph Droms <rdroms.ietf at gmail.com>
 Date: Fri, 11 Oct 2013 13:09:27 -0400

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

 " draft-ietf-roll-trickle-mcast-05 and draft-ietf-6man-multicast-scopes-00
 are in conflict with each other.

 From draft-ietf-roll-trickle-mcast-05:

    When
    used with MPL, Realm-Local scope is administratively defined and used
    to define the boundaries of multicast message dissemination by MPL.

 From draft-ietf-6man-multicast-scopes-00:

    Realm-Local scope is the largest scope that is automatically
    configured, i.e., automatically derived from physical
    connectivity or other, non-multicast-related configuration.

 Specifically, "administratively defined" seems to me to be in direct
 conflict with "automatically configured".

 I suggest fixing the problem with two updates.  First, the definition
 of "scop 3" in an IP-over-IEEE802.15.4 needs to be published, based on
 this text from draft-ietf-6man-multicast-scopes-00:

    The definition of any Realm-Local scope for a particular network
    technology should be published in an RFC.

 I suggest:

    When used in an IP-over-IEEE802.15.4 network, "scop 3" is defined
    to include all interfaces sharing a PAN ID.

 This text could be added to draft-ietf-roll-trickle-mcast-05, or to
 draft-ietf-6man-multicast-scopes-00 or published separately in yet
 another "world's shortest RFC".

 Second, draft-ietf-roll-trickle-mcast-05 should be changed to read:

    When used with MPL, Realm-local scope is defined according to the
    underlying network technology; for example, [cite the
    IP-over-IEEE802.15.4 definition].

 As a further refinement, I suggest text be added to
 draft-ietf-roll-trickle-mcast-05 to the effect of:

    "scop 4" can also be used with MPL to cover deployments that use
    administratively defined scopes that cover, for example, subnets
    based on different underlying network technologies.

 - Ralph

 PS I originally posted about this issue to the rool WG mailing list:
 http://www.ietf.org/mail-archive/web/roll/current/msg08188.html.
 After a discussion with Kerry Lynn, I made a change to the definition
 of scop 3 for IEEE802.15.4. "

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

v2.23.0 | Report a Bug | By Email