Re: Consensus call on adopting: <draft-gont-6man-stable-privacy-addresses-01>

Bob Hinden <bob.hinden@gmail.com> Thu, 10 May 2012 11:37 UTC

Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14AA921F8541 for <ipv6@ietfa.amsl.com>; Thu, 10 May 2012 04:37:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.229
X-Spam-Level:
X-Spam-Status: No, score=-103.229 tagged_above=-999 required=5 tests=[AWL=0.370, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RCAieWJktJLk for <ipv6@ietfa.amsl.com>; Thu, 10 May 2012 04:37:00 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6EC5E21F8503 for <ipv6@ietf.org>; Thu, 10 May 2012 04:37:00 -0700 (PDT)
Received: by yhq56 with SMTP id 56so1655429yhq.31 for <ipv6@ietf.org>; Thu, 10 May 2012 04:37:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=Z8aHvJMod5tuicxu9a56p9CZEOkQQGZ420KZD3loW2I=; b=gnjxaWvc6HnDlzONpkPzP9Hy2GXfekF1mYpMemq47IKjMUoV5VvjcfIr3Mn4zXlT4C ekVIT9nTFwV2udGjSAKSu5Y82+qinR2xV58z/D1zVpTapUFK3qyhYR+Bl0ZDsiURlnwW BmXqWaPWksowMwDQvijtKn7BtejXlYp4wwRiwUVpMTJbk6Yui309xaLjNV5XGwPvRpOl VoqkmcAAk4iqOY90pyB2jFpjGMGj178WRqykpZirpAgj++sPecnZK4oFPSu0PGCVNCW3 aXWq/4AJLMepzu8BQcs/ubF26nrt191tnu3T8gSTA4Ldk+FiLU/1mZjp7CwXUvAln8Ng Vm9g==
Received: by 10.42.141.72 with SMTP id n8mr1828577icu.47.1336649819599; Thu, 10 May 2012 04:36:59 -0700 (PDT)
Received: from [172.16.35.37] ([38.100.136.98]) by mx.google.com with ESMTPS id k4sm1445974igq.16.2012.05.10.04.36.57 (version=SSLv3 cipher=OTHER); Thu, 10 May 2012 04:36:58 -0700 (PDT)
Subject: Re: Consensus call on adopting: <draft-gont-6man-stable-privacy-addresses-01>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="iso-8859-1"
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <4FAB02D5.9090300@gont.com.ar>
Date: Thu, 10 May 2012 07:36:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C2475E14-3A32-4A2F-839B-A61497E43B3C@gmail.com>
References: <E7607B61-9889-43A9-B86B-133BD4238BA2@gmail.com> <60CF6942-0D99-422A-8BEB-87A98B7F233D@employees.org> <4FAB02D5.9090300@gont.com.ar>
To: Fernando Gont <fernando@gont.com.ar>
X-Mailer: Apple Mail (2.1084)
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, IPv6 WG Mailing List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, draft-gont-6man-stable-privacy-addresses@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 10 May 2012 11:37:01 -0000

Fernando,

On May 9, 2012, at 7:50 PM, Fernando Gont wrote:

> Hi, Ole,
> 
> On 05/08/2012 02:42 PM, Ole Trøan wrote:
>> The discussion brought up some issues that we will work with the author to
>> resolve, in particular:
>> 
>> - The current draft is written to not allow the IETF to create derivative works.
>>   This is incompatible with the IETF standards process.
>>   See section 4 of http://www.ietf.org/id-info/1id-guidelines.txt
> 
> My understanding is that this is perfectly compatible with the IETF
> standards process, as long as this restriction is removed before posting
> as draft-ietf (for instance, I guess that's why it's allowed in the
> first place). (this restriction will be removed in the upcoming
> draft-ietf version, accordingly)


It is allowed and I don't want to start a big IPR thread here, but I think the intent for this clause (no derivative works) is for work that someone wants to present to a w.g. that was not intended to be an IETF work item.  My opinion is that it's not appropriate for documents intended to become an IETF work item as yours was.

> 
> 
> 
>> - The draft should not replace modified EUI-64 IIDs. It intents to provide an alternative to
>>   IEEE MAC based modified EUI-64 IIDs.
> 
> Agreed.
> 
> 
>>   The draft should not update RFC4191 and RFC4862
> 
> Agreed. However, it looks like this document should update RFC2464, though.
> 
> Thoughts?

Perhaps at some point in the future if the working group wants to require stable privacy addresses, but not at this point.  I think we will need operational experience before making that change.

Bob


> 
> 
>> - The proposed mechanism has merit separately from the perceived "security" benefits,
>>   because it creates modified EUI-64 Internet Identifiers that are not IEEE Mac based and
>>   eliminates any concern about host tracking based on the IEEE MAC addresses.
> 
> I agree with this -- e.g. using the interface index in the hash leads to
> stable NIC-independent addresses that don't vary even if you replace the
> NIC. Is *this* what I should note in the next rev of the document?
> 
> Thanks!
> 
> Best regards,
> -- 
> Fernando Gont
> e-mail: fernando@gont.com.ar || fgont@si6networks.com
> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------