Re: 3484bis and privacy addresses

Arifumi Matsumoto <arifumi@nttv6.net> Tue, 08 May 2012 12:01 UTC

Return-Path: <arifumi@nttv6.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 5546121F84FF for <ipv6@ietfa.amsl.com>; Tue, 8 May 2012 05:01:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 591RG+Q1Pbqh for <ipv6@ietfa.amsl.com>; Tue, 8 May 2012 05:01:26 -0700 (PDT)
Received: from leo.nttv6.net (leo.nttv6.net [192.47.162.93]) by ietfa.amsl.com (Postfix) with ESMTP id 64AC321F84D1 for <ipv6@ietf.org>; Tue, 8 May 2012 05:01:26 -0700 (PDT)
Received: from [127.0.0.1] (localhost.nttv6.net [127.0.0.1]) by leo.nttv6.net (8.14.5/8.14.4) with ESMTP id q48C0Wn4038370; Tue, 8 May 2012 21:00:32 +0900 (JST) (envelope-from arifumi@nttv6.net)
Subject: Re: 3484bis and privacy addresses
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset="us-ascii"
From: Arifumi Matsumoto <arifumi@nttv6.net>
In-Reply-To: <4FA4CB7A.4060103@globis.net>
Date: Tue, 08 May 2012 20:59:14 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <B424E962-EF78-43B0-8ECC-90C85BEC9247@nttv6.net>
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> <4FA4CB7A.4060103@globis.net>
To: Ray Hunter <v6ops@globis.net>
X-Mailer: Apple Mail (2.1257)
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, Dave Thaler <dthaler@microsoft.com>
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: Tue, 08 May 2012 12:01:27 -0000

Dave and Ray,

thanks for putting together regarding these points.
I'll compile these into the revision of DHCP option draft soon.

Thanks !

On 2012/05/05, at 15:40, Ray Hunter wrote:

> 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
>> 
>> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--
Arifumi Matsumoto
  NGN System Architecture Project
  NTT Service Integration Laboratories
  E-mail: arifumi@nttv6.net
  TEL +81-422-59-3334 FAX +81-422-59-6364