Re: [Roll] Last Call: <draft-ietf-roll-trickle-mcast-06.txt> (Multicast Protocol for Low power and Lossy Networks (MPL)) to Proposed Standard

Kerry Lynn <kerlyn@ieee.org> Mon, 10 February 2014 19:44 UTC

Return-Path: <kerlyn2001@gmail.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8A8E1A0863; Mon, 10 Feb 2014 11:44:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.027
X-Spam-Level:
X-Spam-Status: No, score=-1.027 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sYZTFIipEj6a; Mon, 10 Feb 2014 11:44:36 -0800 (PST)
Received: from mail-oa0-x236.google.com (mail-oa0-x236.google.com [IPv6:2607:f8b0:4003:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id 812F21A03C9; Mon, 10 Feb 2014 11:44:36 -0800 (PST)
Received: by mail-oa0-f54.google.com with SMTP id i4so8029826oah.41 for <multiple recipients>; Mon, 10 Feb 2014 11:44:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=+l5MMlxfcTnmu3jCJZZG/V2FsAccXTcdA9SQDuYOavw=; b=pDF34w7glcnLIyc5nk8oDkOITWTeJumk9qLjBF6TFK21dUhKMaFsVbjZzA01OnrXAf PzcsRkX4rFTnXxUVYQUvsmXACfiHJZExOzCPLIU3TzHoLblyNarekpgfdStwDx1xW5pw SbSTUteZc2D9Pu50EsxkzgllMdmB40lo8a4J1p3XvLOddopqsk5uPAjP0/7fzXNrUTAi kq1qrwD3Y3EB/ZX7UA/T1doLI62r2IzWbh+m/dam5oxrX6I55uKEch1JRCRZbfWg0OeA r7e5ZGV1Mua74sz4m/u/milZiaxG4qG3cuiMm8llKRFT0B0GQLu4Uojp3bE1EjqaZYc9 cyQg==
MIME-Version: 1.0
X-Received: by 10.182.148.106 with SMTP id tr10mr2167834obb.65.1392061476095; Mon, 10 Feb 2014 11:44:36 -0800 (PST)
Sender: kerlyn2001@gmail.com
Received: by 10.60.83.10 with HTTP; Mon, 10 Feb 2014 11:44:36 -0800 (PST)
In-Reply-To: <20140124201637.988.3372.idtracker@ietfa.amsl.com>
References: <20140124201637.988.3372.idtracker@ietfa.amsl.com>
Date: Mon, 10 Feb 2014 14:44:36 -0500
X-Google-Sender-Auth: KeKhyEm9k2Y5uMX3zv8_-hpAx9I
Message-ID: <CABOxzu1PQ0kDTapvALbiARfDqECSamC8urZm6+B4HjnSTJ3Yqw@mail.gmail.com>
From: Kerry Lynn <kerlyn@ieee.org>
To: ietf@ietf.org, Routing Over Low power and Lossy networks <roll@ietf.org>, Jonathan Hui <jonhui@cisco.com>
Content-Type: multipart/alternative; boundary="089e012940d8c9d00804f2129155"
Subject: Re: [Roll] Last Call: <draft-ietf-roll-trickle-mcast-06.txt> (Multicast Protocol for Low power and Lossy Networks (MPL)) to Proposed Standard
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <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, 10 Feb 2014 19:44:39 -0000

Hi Jonathan,

I apologize for the fact that these comments/questions are late but offer
them anyway...


3. Applicability Statement

OLD:

   Operationally, the scope of this protocol is administratively
   determined.  In other words, the scope of dissemination is determined
   by routers configured to disallow transmission or reception of MPL
   messages on a subset of interfaces.


This language predates the alignment with I-D.ietf-6man-multicast-scopes
and I suspect
it is no longer generally true.  I recommend deleting it.


4.1.  MPL Domains

OLD:

   When MPL is used in deployments that use administratively defined
   scopes that cover, for example, multiple subnets based on different
   underlying network technologies, Admin-Local scope (scop value 4) and
   /or Site-Local scope (scop value 5) SHOULD be used.


I'm not clear on whether, in deployments where scop values 4 and/or 5 are
in use, a node
should participate in the ALL_MPL_FORWARDERS multicast address for each
multicast
scope in use or just the highest scope in use.


5.4  MPL Forwarder Parameters

OLD:

   PROACTIVE_FORWARDING  A boolean value that indicates whether the MPL
      Forwarder schedules MPL Data Message transmissions after receiving
      them for the first time.  It is RECOMMENDED that all MPL
      Interfaces attached to the same link of a given MPL Domain use the
      same value for PROACTIVE_FORWARDING and has a default value of
      TRUE.  The mechanism for setting PROACTIVE_FORWARDING is not
      specified within this document.

   SEED_SET_ENTRY_LIFETIME  The minimum lifetime for an entry in the
      Seed Set.  SEED_SET_ENTRY_LIFETIME has a default value of 30
      minutes.  It is RECOMMENDED that all MPL Forwarders use the same
      value for SEED_SET_ENTRY_LIFETIME for a given MPL Domain and has a
      default value of 30 minutes.  The mechanism for setting
      SEED_SET_ENTRY_LIFETIME is not specified within this document.


NEW:

      ...
      PROACTIVE_FORWARDING has a default value of TRUE.

      ...
      It is RECOMMENDED that all MPL Forwarders use the same
      value for SEED_SET_ENTRY_LIFETIME for a given MPL Domain and *use* a
      default value of 30 minutes.

I think you were already planning to delete the RECOMMEND that all MPL
Interfaces
on the same link use the same value for PROACTIVE_FORWARDING.  The second
suggestion is just grammatical.

Regards, -K-




On Fri, Jan 24, 2014 at 3:16 PM, The IESG <iesg-secretary@ietf.org> wrote:

> The IESG has received a request from the Routing Over Low power and Lossy
> networks WG (roll) to consider the following document:
> - 'Multicast Protocol for Low power and Lossy Networks (MPL)'
>   <draft-ietf-roll-trickle-mcast-06.txt> as Proposed Standard
>
> This is a second last call, the first one having been abandoned to send
> the document back to the working group. But the latest revision addresses
> comments that were received during the first last call.
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2014-02-07. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>    This document specifies the Multicast Protocol for Low power and
>    Lossy Networks (MPL) that provides IPv6 multicast forwarding in
>    constrained networks.  MPL avoids the need to construct or maintain
>    any multicast forwarding topology, disseminating messages to all MPL
>    Forwarders in an MPL Domain.  MPL uses the Trickle algorithm to
>    manage message transmissions for both control and data-plane
>    messages.  Different Trickle parameter configurations allow MPL to
>    trade between dissemination latency and transmission efficiency.
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-roll-trickle-mcast/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-roll-trickle-mcast/ballot/
>
>
> The following IPR Declarations may be related to this I-D:
>
>    http://datatracker.ietf.org/ipr/1858/
>
>
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>