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

Tim Chown <tjc@ecs.soton.ac.uk> Fri, 13 April 2012 10:37 UTC

Return-Path: <tjc@ecs.soton.ac.uk>
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 6B59721F8627 for <ipv6@ietfa.amsl.com>; Fri, 13 Apr 2012 03:37:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 kMXFBnaJyikQ for <ipv6@ietfa.amsl.com>; Fri, 13 Apr 2012 03:37:49 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 7400C21F8624 for <ipv6@ietf.org>; Fri, 13 Apr 2012 03:37:49 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id q3DAbjws022172; Fri, 13 Apr 2012 11:37:45 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk q3DAbjws022172
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1334313465; bh=AEZZPIixvFyd5T/fMBOfnxl0Qw8=; h=Subject:Mime-Version:From:In-Reply-To:Date:Cc:References:To; b=uANqzG1FJkqvMA3VKUGZ+tRG6Zju3OH0cZXJm5amUAJfkXboYwgIBRTLQBCvLtQGy b+fzHKlTYn5DKgo2TSwyWvQG5+KDqdP9Il+DCqANz5/ajyMgZ+Dw2reFUeOIHRgIHj J8cKkMC5cXaecPeAKZf+Kh/cs34F+LL10ovGox0A=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id o3CBbj0543760396p0 ret-id none; Fri, 13 Apr 2012 11:37:45 +0100
Received: from ip-205-201.eduroam.soton.ac.uk (ip-205-201.eduroam.soton.ac.uk [152.78.205.201]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id q3DAbdrZ019129 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 13 Apr 2012 11:37:39 +0100
Subject: Re: Consensus call on adopting: <draft-gont-6man-stable-privacy-addresses-01>
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <4F87D245.4000102@gmail.com>
Date: Fri, 13 Apr 2012 11:37:39 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|09206087d5a8f81e80ca891498271ae5o3CBbj03tjc|ecs.soton.ac.uk|95F65935-A316-4CFB-9A79-9B0AB7E33A10@ecs.soton.ac.uk>
References: <E7607B61-9889-43A9-B86B-133BD4238BA2@gmail.com> <4F87D245.4000102@gmail.com> <95F65935-A316-4CFB-9A79-9B0AB7E33A10@ecs.soton.ac.uk>
To: IPv6 WG Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1257)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=o3CBbj054376039600; tid=o3CBbj0543760396p0; client=relay,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: q3DAbjws022172
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: 6man Chairs <6man-chairs@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: Fri, 13 Apr 2012 10:37:50 -0000

On 13 Apr 2012, at 08:14, Brian E Carpenter wrote:

> On 2012-04-12 22:28, Bob Hinden wrote:
>> All,
>> 
>> This is a consensus call on adopting:
>> 
>>    Title     : A method for Generating Stable Privacy-Enhanced Addresses with
>>                IPv6 Stateless Address Autoconfiguration (SLAAC)
>>    Author(s) : Fernando Gont
>>    Filename  : draft-gont-6man-stable-privacy-addresses-01
>>    Pages     : 15
>>    Date      : 2012-12-31
>> 
>>    http://tools.ietf.org/html/draft-gont-6man-stable-privacy-addresses-01
>> 
>> as a 6MAN working group document.  Please state your opinion, positive
>> or negative, on the mailing list or to the chairs.  This consensus call
>> will end on April 26, 2012.
> 
> Yes to adoption. Karl Auer's points all need discussion, and I think
> we also need to consider the impact on 3484bis.

Yes, let's adopt.

Personally I think a different name for these types of addresses would be more appropriate, to avoid confusion with RFC4941 Privacy Extensions.  If I understand it correctly, essentially what you are defining is randomised stable-per-prefix public interface identifiers, but that's not a catchy term :)

On 3484bis, if stable privacy addresses are alternative public (not temporary) identifiers for hosts then is there anything more to say?  What impact are you considering Brian, other than would exist if two other public addresses existed on an interface?

Note that RFC4941 temporary addresses can also be stable, in that they do not change if the host stays on the same network; the specification only says identifiers SHOULD be regenerated at some defined interval.  

Finally, it would be interesting to know what algorithm Windows uses to generate its identifiers; they are randomised, public and stable.  I had thought they were based on the prefix, but Fernando's tests suggest not. 

Tim