[Roll] IPv6 multicast scope 0x03 in trickle-mcast

Ralph Droms <rdroms.ietf@gmail.com> Wed, 13 March 2013 13:37 UTC

Return-Path: <rdroms.ietf@gmail.com>
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 B062721F87F9 for <roll@ietfa.amsl.com>; Wed, 13 Mar 2013 06:37:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.048
X-Spam-Status: No, score=-103.048 tagged_above=-999 required=5 tests=[AWL=0.551, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id aqMWWynMRc55 for <roll@ietfa.amsl.com>; Wed, 13 Mar 2013 06:37:18 -0700 (PDT)
Received: from mail-qe0-f49.google.com (mail-qe0-f49.google.com []) by ietfa.amsl.com (Postfix) with ESMTP id 2570F21F87AC for <roll@ietf.org>; Wed, 13 Mar 2013 06:37:18 -0700 (PDT)
Received: by mail-qe0-f49.google.com with SMTP id 1so579597qec.8 for <roll@ietf.org>; Wed, 13 Mar 2013 06:37:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:content-type:content-transfer-encoding:subject:date :message-id:cc:to:mime-version:x-mailer; bh=aw2lW7qquRznIAmnHfH/bzj2sZ3wez4vpUWr0tEuPPk=; b=EKyM8z0RwLoE/fVOyL5t/OARlXmqwIG2wwSDffyC5sMUD5cIDLgRdREuk8VZYSzdqL E+LilCoNY/pCuwWL7Aa17QnkJgQAOqPX3ylqs1lpWT3q70Fv8XZzOdH+cIrsitS1MWhq odcaqVI6+prEEfJsKb6UGYsnumlG9H+MnnqrgtgA7udwud58l0lRwQdCTDU0llDp8mt0 59NIRU2No20VDjQqhkyAzyq7mVh05NLYeUlw36aWyZ4ptELy64i3QaAjEFziliDEyBzz bJGSyHbwNkUbDWHkBJGlRHVkPgjva3Qqfnri7b4D+jzCxP/ggAy4HYTQGBnf9ltbA01o ER+g==
X-Received: by with SMTP id q4mr2834508qer.60.1363181835609; Wed, 13 Mar 2013 06:37:15 -0700 (PDT)
Received: from [] (198-135-0-233.cisco.com. []) by mx.google.com with ESMTPS id ku2sm36660811qeb.4.2013. (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 13 Mar 2013 06:37:14 -0700 (PDT)
From: Ralph Droms <rdroms.ietf@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 13 Mar 2013 09:33:20 -0400
Message-Id: <0CD48245-8B5B-416B-AE6B-F780CB44B89E@gmail.com>
To: "roll@ietf.org" <roll@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Cc: "6man-chairs@tools.ietf.org Chairs" <6man-chairs@tools.ietf.org>, "int-ads@tools.ietf.org" <int-ads@tools.ietf.org>, "roll-chairs@tools.ietf.org" <roll-chairs@tools.ietf.org>
Subject: [Roll] IPv6 multicast scope 0x03 in trickle-mcast
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Wed, 13 Mar 2013 13:37:18 -0000

WG - To help move the trickle multicast spec along for ZigBee, I applied to IANA for the well-known multicast address for ALL_MPL_FORWARDERS.

As part of the review, Stig Venaas (designated expert) pointed out that draft-ietf-roll-trickle-mcast specifies the use of IPv6 multicast scope 0x03, which is currently "reserved" [RFC4291].  Turns out it was never officially defined as "subnet-local scope" in an RFC, although it was identified as such in early IPv6 addressing architecture I-Ds.  So, something has to be done to allow MPL to use scope 0x03.

Stig, the Internet ADs, 6man co-chairs, roll co-chairs and I discussed the issue, and devised a plan to redefine scope 0x03 to be "unassigned" (like the other unused scope values), and then identify scope 0x03 in draft-ietf-roll-trickle-mcast as a special-purpose use for "trickle multicast networks" (rather than a "subnet").

draft-ietf-roll-trickle-mcast-04 will need to be edited a little, but otherwise I think this plan should meet ZA's requirements.  Also, I'll need to publish a 1-paragraph RFC with the new definition of scope 0x03, but that will be a very quick process.

The next revision of draft-ietf-roll-trickle-mcast will include the necessary edits.  I'll start the process to publish the RFC to redefine scope 0x03 next week.

- Ralph