Re: Protocol Action: 'A Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address Autoconfiguration (SLAAC)' to Proposed Standard (draft-ietf-6man-stable-privacy-addresses-17.txt)

t.petch <ietfc@btconnect.com> Fri, 31 January 2014 10:04 UTC

Return-Path: <ietfc@btconnect.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B1101A049B for <ipv6@ietfa.amsl.com>; Fri, 31 Jan 2014 02:04:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tl9ZXY-BUjDR for <ipv6@ietfa.amsl.com>; Fri, 31 Jan 2014 02:04:25 -0800 (PST)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe005.messaging.microsoft.com [216.32.180.31]) by ietfa.amsl.com (Postfix) with ESMTP id 28B801A0476 for <ipv6@ietf.org>; Fri, 31 Jan 2014 02:04:24 -0800 (PST)
Received: from mail21-va3-R.bigfish.com (10.7.14.230) by VA3EHSOBE003.bigfish.com (10.7.40.23) with Microsoft SMTP Server id 14.1.225.23; Fri, 31 Jan 2014 10:04:21 +0000
Received: from mail21-va3 (localhost [127.0.0.1]) by mail21-va3-R.bigfish.com (Postfix) with ESMTP id 3C13EE0229; Fri, 31 Jan 2014 10:04:21 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.85; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0710HT003.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -14
X-BigFish: PS-14(zz9371I542I1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h20f7h2189h1d1ah1d2ah21bch1fc6hzz1de098h1033IL17326ah8275dh1de097h186068hz2dh2a8h5a9h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh19f0h1ad9h1b0ah2222h224fh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h2218h2216h226dh22d0h24afh2327h2336h2438h2461h2487h24d7h2516h304l1d11m1155h)
Received: from mail21-va3 (localhost.localdomain [127.0.0.1]) by mail21-va3 (MessageSwitch) id 1391162659459964_8247; Fri, 31 Jan 2014 10:04:19 +0000 (UTC)
Received: from VA3EHSMHS023.bigfish.com (unknown [10.7.14.241]) by mail21-va3.bigfish.com (Postfix) with ESMTP id 584A12A0046; Fri, 31 Jan 2014 10:04:19 +0000 (UTC)
Received: from DB3PRD0710HT003.eurprd07.prod.outlook.com (157.56.253.85) by VA3EHSMHS023.bigfish.com (10.7.99.33) with Microsoft SMTP Server (TLS) id 14.16.227.3; Fri, 31 Jan 2014 10:04:12 +0000
Received: from pc6 (81.159.188.189) by pod51017.outlook.com (10.255.75.38) with Microsoft SMTP Server (TLS) id 14.16.411.0; Fri, 31 Jan 2014 10:04:01 +0000
Message-ID: <00d101cf1e6b$253380e0$4001a8c0@gateway.2wire.net>
From: t.petch <ietfc@btconnect.com>
To: Fernando Gont <fgont@si6networks.com>
References: <20140130235450.3929.82596.idtracker@ietfa.amsl.com>
Subject: Re: Protocol Action: 'A Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address Autoconfiguration (SLAAC)' to Proposed Standard (draft-ietf-6man-stable-privacy-addresses-17.txt)
Date: Fri, 31 Jan 2014 09:59:27 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [81.159.188.189]
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: 6man mailing list <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jan 2014 10:04:27 -0000

Fernando

Congratulations.

When I first saw this I-D, I thought what a sensible idea.  Since then,
I have been surprised, amazed even, at the opposition that has been put
up, on this list, on the IETF list and even by the IESG.  I have
wondered why and have no rational explanation but do believe that you
deserve a special mention for seeing this through, when others might
have given up long ago (well, I would have done:-(

So, congratulations.

Tom Petch


----- Original Message -----
From: "The IESG" <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: "6man chair" <6man-chairs@tools.ietf.org>rg>; "6man mailing list"
<ipv6@ietf.org>rg>; "RFC Editor" <rfc-editor@rfc-editor.org>
Sent: Thursday, January 30, 2014 11:54 PM
Subject: Protocol Action: 'A Method for Generating Semantically Opaque
Interface Identifiers with IPv6 Stateless Address Autoconfiguration
(SLAAC)' to Proposed Standard
(draft-ietf-6man-stable-privacy-addresses-17.txt)


> The IESG has approved the following document:
> - 'A Method for Generating Semantically Opaque Interface Identifiers
with
>    IPv6 Stateless Address Autoconfiguration (SLAAC)'
>   (draft-ietf-6man-stable-privacy-addresses-17.txt) as Proposed
Standard
>
> This document is the product of the IPv6 Maintenance Working Group.
>
> The IESG contact persons are Brian Haberman and Ted Lemon.
>
> A URL of this Internet Draft is:
>
http://datatracker.ietf.org/doc/draft-ietf-6man-stable-privacy-addresses
/
>
>
>
>
> Technical Summary:
>
>    This document specifies a method for generating IPv6 Interface
>    Identifiers to be used with IPv6 Stateless Address
Autoconfiguration
>    (SLAAC), such that addresses configured using this method are
stable
>    within each subnet, but the Interface Identifier changes when hosts
>    move from one network to another.  This method is meant to be an
>    alternative to generating Interface Identifiers based on hardware
>    addresses (e.g., IEEE LAN MAC addresses), such that the benefits of
>    stable addresses can be achieved without sacrificing the privacy of
>    users.  The method specified in this document applies to all
prefixes
>    a host may be employing, including link-local, global, and unique-
>    local addresses.
>
> Working Group Summary:
>
>   This document was sent back to the working group based on the number
of
>   comments received during the IETF last call.  The current document
is
>   significantly improved.   After a long discussion, another working
>   group last call was done with support from the w.g.  The chairs had
two
>   reviewers, Ray Hunter and Mark Smith, did a detailed review of the
>   draft.  This resulted in several changes in the current draft (-14).
>   The reviewers have told us that the new draft resolves the issues
they
>   raised.  The w.g. chairs believe the draft is ready to send to the
IESG
>   again.
>
>   In addition Alissa Cooper revised the document and is working on a
draft
>   that provides an overview of the privacy considerations with all
types of
>   IPv6 addresses.
>
> Document Quality:
>
>    No implementations known.
>
> Personnel:
>
>   Bob Hinden is the Document Shepherd.
>
>   Brian Haberman is the Responsible Area Director.
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>