Re: RE: 3484bis and privacy addresses

Ray Hunter <v6ops@globis.net> Sat, 05 May 2012 06:41 UTC

Return-Path: <v6ops@globis.net>
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 D35AF21F8454 for <ipv6@ietfa.amsl.com>; Fri, 4 May 2012 23:41:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.436
X-Spam-Level:
X-Spam-Status: No, score=-2.436 tagged_above=-999 required=5 tests=[AWL=0.163, 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 o1n7TdYtDHwh for <ipv6@ietfa.amsl.com>; Fri, 4 May 2012 23:41:09 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 10E0821F8453 for <ipv6@ietf.org>; Fri, 4 May 2012 23:41:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id C157A870080; Sat, 5 May 2012 08:41:07 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at globis01.globis.net
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RDFXfMXy64rc; Sat, 5 May 2012 08:41:00 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 321A787007B; Sat, 5 May 2012 08:41:00 +0200 (CEST)
Message-ID: <4FA4CB7A.4060103@globis.net>
Date: Sat, 05 May 2012 08:40:58 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.3 (Macintosh/20120304)
MIME-Version: 1.0
To: Dave Thaler <dthaler@microsoft.com>
Subject: Re: RE: 3484bis and privacy addresses
References: <4F716D5C.40402@innovationslab.net> <4F726C9E.50107@gmail.com> <9B57C850BB53634CACEC56EF4853FF653B5054C1@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <4F83D8D0.5030402@gmail.com> <9B57C850BB53634CACEC56EF4853FF653B508719@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <4F858C32.6060709@globis.net> <9B57C850BB53634CACEC56EF4853FF653B50CBC2@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <4F87D4EA.4040801@globis.net> <9B57C850BB53634CACEC56EF4853FF653B513879@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <4F8935C7.6020602@globis.net> <9B57C850BB53634CACEC56EF4853FF653B5159E0@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <9B57C850BB53634CACEC56EF4853FF653B5AF1C5@TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <9B57C850BB53634CACEC56EF4853FF653B5AF1C5@TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "ipv6@ietf.org" <ipv6@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: Sat, 05 May 2012 06:41:09 -0000

ACK. Thanks.

Dave Thaler wrote:
> I wrote in response to Ray Hunter:
>> I take your comment as asking for a summary table in rfc 3484bis of
>> system-wide config options.   That could be done as a purely editorial
>> change, although if there's only 1 thing in the table it's less interesting.
>> But if others in the WG think this would be helpful, then yes we can do that.
>
> Turns out there were already 2 things so I've done this in -03.
>
> OLD:
> 	This specification optionally allows for the possibility of
> 	administrative configuration of policy (e.g., via manual
> 	configuration or a DHCP option such as that proposed in
> 	[I-D.ietf-6man-addr-select-opt]) that can override the default
> 	behavior of the algorithms.  The policy override takes the form of a
> 	configurable table that specifies precedence values and preferred
> 	source prefixes for destination prefixes.  If an implementation is
> 	not configurable, or if an implementation has not been configured,
> 	then the default policy table specified in this document SHOULD be
> 	used.
>
> NEW:
> 	This specification optionally allows for the possibility of
> 	administrative configuration of policy (e.g., via manual
> 	configuration or a DHCP option such as that proposed in
> 	[I-D.ietf-6man-addr-select-opt]) that can override the default
> 	behavior of the algorithms.  The policy override consists of the
> 	following set of state, which SHOULD be configurable:
>
> 	o  Policy Table (Section 2.1): a table that specifies precedence
> 	   values and preferred source prefixes for destination prefixes.
> 	o  Automatic Row Additions flag (Section 2.1): a flag that specifies
> 	   whether the implementation may automatically add site-specific
> 	   rows for certain types of addresses.
> 	o  Privacy Preference flag (Section 5): a flag that specifies whether
> 	   temporary source addresses or stable source addresses are
> 	   preferred by default, when both types exist.
>
> This is purely an editorial change.   The rest of Ray's comments apply
> to I-D.ietf-6man-addr-select-opt, which is already informatively
> referenced in the above text.
>
> -Dave
>
>