Brian Haberman's Discuss on draft-ietf-6man-stable-privacy-addresses-16: (with DISCUSS)

"Brian Haberman" <> Thu, 23 January 2014 12:34 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 47CDC1A0430; Thu, 23 Jan 2014 04:34:28 -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 cdQEI07gkFKl; Thu, 23 Jan 2014 04:34:26 -0800 (PST)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id AE06E1A03E6; Thu, 23 Jan 2014 04:34:26 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Brian Haberman <>
To: The IESG <>
Subject: Brian Haberman's Discuss on draft-ietf-6man-stable-privacy-addresses-16: (with DISCUSS)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Thu, 23 Jan 2014 04:34:26 -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: Thu, 23 Jan 2014 12:34:28 -0000

Brian Haberman has entered the following ballot position for
draft-ietf-6man-stable-privacy-addresses-16: Discuss

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:


I am taking the somewhat curious route of raising a DISCUSS on a document
that I am shepherding.  I will return to a Yes when these issues are
resolved.  Thomas Narten raised a good point that this document does not
mention the work published in RFCs 4436 and 6059 (from the concluded DNA
WG).  Two of the points he raised are worth addressing in this document
prior to publication.

1. [Resolved] - Storing addresses is going to raise privacy issues.

2. DNA provides some ability to manage the Network_ID component of the
cryptographic hash.  For wired networks, that may be quite useful as long
as the Network_ID can be stored securely.