Re: [Roll] call for consensus for the RPL RPI / RH3 compression

Ralph Droms <> Tue, 06 January 2015 15:31 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id D5BE81A0211; Tue, 6 Jan 2015 07:31:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 8tXwRTcY0kLk; Tue, 6 Jan 2015 07:31:02 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:400d:c04::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A784D1A00DB; Tue, 6 Jan 2015 07:30:56 -0800 (PST)
Received: by with SMTP id i50so16517624qgf.24; Tue, 06 Jan 2015 07:30:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc:reply-to :content-transfer-encoding:message-id:references:to; bh=D79qegj4l2no82i5Hq2/nlbBOzYMBDxby9wBXBYgI3Y=; b=Tf+gjgL7ZCJpE1e0+Q4DdlSX+BFBN8VYBS++31Y7VmTabXYMD6vPZUry2JjEA8V4Hp x++LUPbGTz5Jupqv9aLt27Rn+MLC1GaIv3uvPaOV/WwKHfD1U1eDf459Gy6mXQXBHiWM jKRWVBGOy9S+XcRp2yCy/vrTPZ9djP+h6b3gzcs1U5/9XZbz1u7PJHQ3iJgb8ikVee64 X2d2JJ585FX0REbOOm3M/rKb1JCvKdQd4KGM709SJqRO7I0iH+HUDxPVNlDVzZsVYqsu RyxwiPA9UZ/oUumuYErZSsrLyFSlrfRlsMcy5OlG2IRbDMDJybJc5+O3Y+aOY0eRaV+R e6Gw==
X-Received: by with SMTP id 66mr130317171qgz.16.1420558255516; Tue, 06 Jan 2015 07:30:55 -0800 (PST)
Received: from [] ( []) by with ESMTPSA id 77sm53566540qgx.43.2015. (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 06 Jan 2015 07:30:55 -0800 (PST)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: text/plain; charset="us-ascii"
From: Ralph Droms <>
In-Reply-To: <000701d02815$f43df5f0$dcb9e1d0$>
Date: Tue, 06 Jan 2015 10:30:39 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <> <> <> <> <000701d02815$f43df5f0$dcb9e1d0$>
To: Routing Over Low power and Lossy networks <>
X-Mailer: Apple Mail (2.1878.6)
Cc: 6man Chairs <>,, 6man WG <>,, " WG" <>,,
Subject: Re: [Roll] call for consensus for the RPL RPI / RH3 compression
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <>
List-Id: Routing Over Low power and Lossy networks <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 06 Jan 2015 15:31:05 -0000

On Jan 4, 2015, at 6:59 AM 1/4/15, Adrian Farrel <> wrote:

> Michael,
> Thanks for continuing to try to wrangle this situation.

Agreeing - thanks.

> [...]
>> Please: how do we proceed?
> Consensus can sometimes be hard-won and slow. It is one of the things that makes people claim the IETF is slow. On the other hand, the alternative to consensus is, erm, no consensus.
> In agreeing consensus, however, we may need to declare minority opinions "in the rough" [RFC7282] if there is a body of opinion that one way of doing things is preferred and if the drawbacks of that approach are clearly recognised and accepted.

Yes, and, in this particular case, there are at least 4 working groups involved, which will make determining and declaring consensus even more difficult.

> I see the plugfest as an important way of reaching consensus on this issue. That is, if the plugfest shows that a particular approach is functional and not harmful it provides a strong case for documenting and standardising the mechanism.

Another outcome of the plugfest would be to assess the quality of the existing drafts (can an implementation be built from just the text in the draft) and the impact of the new mechanisms on other parts of the IPv6 suite as well as network operation.

> Beyond that it may be most helpful to note the objections to the "preferred" approach and to write text that explains the concerns and how they are mitigated (for example, not sending traffic out of admin domains without applying some magic policy).

I don't know that we have enough detail and discussion, yet, to have determined a "preferred" approach. 

- Ralph
> Adrian
> _______________________________________________
> Roll mailing list