Re: [Roll] WG Last Call draft-ietf-roll-trickle-mcast-04

Ralph Droms <rdroms.ietf@gmail.com> Mon, 01 April 2013 15:13 UTC

Return-Path: <rdroms.ietf@gmail.com>
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 3D97C21F9359 for <roll@ietfa.amsl.com>; Mon, 1 Apr 2013 08:13:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 n0O0vLd-05-q for <roll@ietfa.amsl.com>; Mon, 1 Apr 2013 08:13:05 -0700 (PDT)
Received: from mail-ve0-f169.google.com (mail-ve0-f169.google.com [209.85.128.169]) by ietfa.amsl.com (Postfix) with ESMTP id 099E521F9357 for <roll@ietf.org>; Mon, 1 Apr 2013 08:13:04 -0700 (PDT)
Received: by mail-ve0-f169.google.com with SMTP id d10so2657823vea.28 for <roll@ietf.org>; Mon, 01 Apr 2013 08:13:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=DsWSXwIt09OfYTcCt4Zz/r0yQSJZTDQD5lJMJL2qQ48=; b=wL9+2v9/ORhCAHPGeZ6Z5aUEz2BYcnmnrhsJBw/5S2OQqWYmopm9MFrpJRJLaD5TYO FTE1AC9t/PMO7qM7gOqmMmiid5hivcyVctughSxYya35FbL5ywtHPJuY1ltRLI8DmZM6 qbBjfo4ZYzrYelLLgzfDBwHyLfTkSiit8FhmD05m1jSJIXKhHr0cVFZSZLOcru24qcy+ ELL1gUgg7Q7G1TeXYZ5ni7YcSkn6eAvvSq5jvJeEFHtwENZQZ7nhdcXXfYMls4+0bRCh AiFMwgS73gOE+Bcn5t/P8LafAyhpZ0+Tq7LxWlDWRF0T8cPYwC8yKpnPV1njx5sVpI7B BKXQ==
X-Received: by 10.58.224.101 with SMTP id rb5mr9651932vec.17.1364829184372; Mon, 01 Apr 2013 08:13:04 -0700 (PDT)
Received: from [10.131.33.85] (rtp-isp-nat1.cisco.com. [64.102.254.33]) by mx.google.com with ESMTPS id xu4sm14024719vdb.11.2013.04.01.08.13.02 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Apr 2013 08:13:03 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <03B78081B371D44390ED6E7BADBB4A772333BC0D@xmb-rcd-x02.cisco.com>
Date: Mon, 01 Apr 2013 11:13:00 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9FD3690D-148B-4EF6-AE57-731CA249D9EE@gmail.com>
References: <03B78081B371D44390ED6E7BADBB4A77220226E7@xmb-rcd-x02.cisco.com> <03B78081B371D44390ED6E7BADBB4A772333BC0D@xmb-rcd-x02.cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
X-Mailer: Apple Mail (2.1499)
Subject: Re: [Roll] WG Last Call draft-ietf-roll-trickle-mcast-04
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Apr 2013 15:13:07 -0000

I apologize for the late feedback...

Section 8 seems somewhat out of place, as well as redundant with the definition of "MPL Domain" in section 2 and the contents of section 5.1.

Multicast scope 0x03 has never been formally defined as "subnet-local".  Delete the references to "subnet-local" in sections 5.1 and 8, leaving just "scope value of 3".  Note that scope value 3 is currently defined as "reserved" in RFC 4291.  I am working on publication of an RFC that will re-define scope value 3 as "(unassigned)" so it can be used as specified in draft-ietf-roll-trickle-mcast-04.

In section 10.1, "the MPL Domain Address" is a little confusing.  Does a device belong to just a single MPL Domain, in which case it might be clearer to write "the MPL Domain Address to which the source interface belongs".  Otherwise - and I don't think I see any text in the document that explicitly constrains an interface to belonging to one MPL domain - the text should read "an MPL Domain Address to which the source interface belongs".

- Ralph