Re: [addr-select-dt] New Version Notification for draft-ietf-6man-addr-select-considerations-02

Arifumi Matsumoto <arifumi@nttv6.net> Tue, 13 July 2010 00:17 UTC

Return-Path: <arifumi@nttv6.net>
X-Original-To: addr-select-dt@core3.amsl.com
Delivered-To: addr-select-dt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 031993A688C for <addr-select-dt@core3.amsl.com>; Mon, 12 Jul 2010 17:17:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level:
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[AWL=0.800, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kL99VZaaIRqF for <addr-select-dt@core3.amsl.com>; Mon, 12 Jul 2010 17:17:43 -0700 (PDT)
Received: from mail.nttv6.net (mail.nttv6.net [IPv6:2001:fa8::25]) by core3.amsl.com (Postfix) with ESMTP id 93B523A6822 for <addr-select-dt@ietf.org>; Mon, 12 Jul 2010 17:17:42 -0700 (PDT)
Received: from radiko.smartstream.ne.jp (localhost [IPv6:::1]) by mail.nttv6.net (8.14.4/8.14.3) with ESMTP id o6D0FDXA030497; Tue, 13 Jul 2010 09:15:14 +0900 (JST) (envelope-from arifumi@nttv6.net)
References: <20100712225745.806583A681D@core3.amsl.com> <A1FA46B4-A3E6-4733-99CB-110D559E4C70@ecs.soton.ac.uk> <EMEW3|e3d0d12dc076314b7b1b0aa2911f0a96m6BNx103tjc|ecs.soton.ac.uk|A1FA46B4-A3E6-4733-99CB-110D559E4C70@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|e3d0d12dc076314b7b1b0aa2911f0a96m6BNx103tjc|ecs.soton.ac.uk|A1FA46B4-A3E6-4733-99CB-110D559E4C70@ecs.soton.ac.uk>
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
Message-Id: <E489B67E-7FC8-4E39-9512-655475AEC6EA@nttv6.net>
Content-Transfer-Encoding: quoted-printable
From: Arifumi Matsumoto <arifumi@nttv6.net>
Date: Tue, 13 Jul 2010 09:15:13 +0900
To: Tim Chown <tjc@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.1081)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (mail.nttv6.net [IPv6:::1]); Tue, 13 Jul 2010 09:15:14 +0900 (JST)
Cc: addr-select-dt@ietf.org
Subject: Re: [addr-select-dt] New Version Notification for draft-ietf-6man-addr-select-considerations-02
X-BeenThere: addr-select-dt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IPv6 Address Selection Design Team <addr-select-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/addr-select-dt>, <mailto:addr-select-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/addr-select-dt>
List-Post: <mailto:addr-select-dt@ietf.org>
List-Help: <mailto:addr-select-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/addr-select-dt>, <mailto:addr-select-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Jul 2010 00:17:45 -0000

Tim

thank you very much !

All,
please review this quickly and go out to 6man ML after that.
If everyone is happy, I'll post an e-mail within 2 days.

On 2010/07/13, at 7:58, Tim Chown wrote:

> New version posted.
> 
> On 12 Jul 2010, at 23:57, IETF I-D Submission Tool wrote:
> 
>> 
>> A new version of I-D, draft-ietf-6man-addr-select-considerations-02.txt has been successfully submitted by Tim Chown and posted to the IETF repository.
>> 
>> Filename:	 draft-ietf-6man-addr-select-considerations
>> Revision:	 02
>> Title:		 Considerations for IPv6 Address Selection Policy Changes
>> Creation_date:	 2010-07-12
>> WG ID:		 6man
>> Number_of_pages: 19
>> 
>> Abstract:
>> Where the source and/or destination node of an IPv6 communication is
>> multi-addressed, a mechanism is required for the initiating node to
>> select the most appropriate address pair for the communication.  RFC
>> 3484 (IPv6 Default Address Selection) [RFC3484] defines such a
>> mechanism for nodes to perform source and destination address
>> selection.  While RFC3484 recognised the need for implementations to
>> be able to change the policy table, it did not define how this could
>> be achieved.  Requirements have now emerged for administrators to be
>> able to configure and potentially dynamically change RFC 3484 policy
>> from a central control point, and for (nomadic) hosts to be able to
>> obtain the policy for the network that they are currently attached to
>> without manual user intervention.  This text discusses considerations
>> for such policy changes, including examples of cases where a change
>> of policy is required, and the likely frequency of such policy
>> changes.  This text also includes some discussion on the need to also
>> update RFC 3484, where default policies are currently defined.
>> 
>> 
>> 
>> The IETF Secretariat.
>> 
>> 
> 
> _______________________________________________
> addr-select-dt mailing list
> addr-select-dt@ietf.org
> https://www.ietf.org/mailman/listinfo/addr-select-dt