Stephen Farrell's No Objection on draft-ietf-6man-stable-privacy-addresses-17: (with COMMENT)

"Stephen Farrell" <> Wed, 29 January 2014 01:58 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id C33FA1A048B; Tue, 28 Jan 2014 17:58:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 2_NYIddP6wQf; Tue, 28 Jan 2014 17:58:49 -0800 (PST)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 65BA81A0483; Tue, 28 Jan 2014 17:58:49 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Stephen Farrell <>
To: The IESG <>
Subject: Stephen Farrell's No Objection on draft-ietf-6man-stable-privacy-addresses-17: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Tue, 28 Jan 2014 17:58:49 -0800
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 29 Jan 2014 01:58:51 -0000

Stephen Farrell has entered the following ballot position for
draft-ietf-6man-stable-privacy-addresses-17: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)

Please refer to
for more information about IESG DISCUSS and COMMENT positions.

The document, along with other ballot positions, can be found here:


Thanks for those changes.

One new comment. It'd be better to reference HMAC-SHA1 and
HMAC-SHA256 as the examples and not SHA1 and SHA256.
There are relevant security differences between those, 
depending on how you provide and process the inputs to F().
(I've not tried to figure out if ther're significant here, but the
HMAC flavours are just better and if you did use them then
I'd not even need to think about it:-)

If you're not happy to do that then rather than say that SHA1
or SHA256 can be used "for" F(), it'd be better to say that F() 
can be "baeed upon" SHA1, as that'd encompass HMAC-SHA1
or HMAC-SHA256.