Fwd: New Version Notification for draft-arifumi-6man-rfc3484-revise-00

Arifumi Matsumoto <arifumi@nttv6.net> Mon, 23 June 2008 09:50 UTC

Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 189BB3A693C; Mon, 23 Jun 2008 02:50:40 -0700 (PDT)
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 70BC53A693C; Mon, 23 Jun 2008 02:50:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=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 5fBlzZLmSAef; Mon, 23 Jun 2008 02:50:37 -0700 (PDT)
Received: from mail.nttv6.net (mail.nttv6.net [IPv6:2001:fa8::25]) by core3.amsl.com (Postfix) with ESMTP id 3D4BD3A690F; Mon, 23 Jun 2008 02:50:36 -0700 (PDT)
Received: from arifumi1.nttv6.com (arifumi1.nttv6.com [192.47.163.61]) by mail.nttv6.net (8.14.3/8.14.1) with ESMTP id m5N9obJP001316; Mon, 23 Jun 2008 18:50:39 +0900 (JST) (envelope-from arifumi@nttv6.net)
Message-Id: <93D9EA01-9679-41A7-B62A-B1CEA622698F@nttv6.net>
From: Arifumi Matsumoto <arifumi@nttv6.net>
To: ipv6@ietf.org
Mime-Version: 1.0 (Apple Message framework v924)
Subject: Fwd: New Version Notification for draft-arifumi-6man-rfc3484-revise-00
Date: Mon, 23 Jun 2008 18:50:21 +0900
References: <20080619094027.CD98F3A6B90@core3.amsl.com>
X-Mailer: Apple Mail (2.924)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (mail.nttv6.net [192.16.178.5]); Mon, 23 Jun 2008 18:50:39 +0900 (JST)
Cc: v6ops@ietf.org, ietf@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="iso-2022-jp"; Format="flowed"; DelSp="yes"
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

Folks,

I submitted the following draft regarding RFC 3484 revision.
This draft covers these issues:

- to remove the description regarding site-local unicast address.
- ULA related changes, such as the default policy table.
- to disable the rule 9 of the destination address selection rules.
   i.e. the longest matching rule.

Though we had discussion regarding the longest matching rule at
several places like ietf@ietf.org and v6ops@ietf.org, why not
discuss at 6man to start ?

Any comments are welcome.

Begin forwarded message:

> 差出人: IETF I-D Submission Tool <idsubmission@ietf.org>;
> 日時: 2008年6月19日 18:40:27:JST
> 宛先: arifumi@nttv6.net
> Cc: fujisaki@syce.net, hiromi@inetcore.com, kanayama_kenichi@intec-si.co.jp
> 件名: New Version Notification for  draft-arifumi-6man-rfc3484- 
> revise-00
>
>
> A new version of I-D, draft-arifumi-6man-rfc3484-revise-00.txt has  
> been successfuly submitted by Arifumi Matsumoto and posted to the  
> IETF repository.
>
> Filename:	 draft-arifumi-6man-rfc3484-revise
> Revision:	 00
> Title:		 Things To Be Considered for RFC 3484 Revision
> Creation_date:	 2008-06-19
> WG ID:		 Independent Submission
> Number_of_pages: 10
>
> Abstract:
> RFC 3484 has several known issues to be fixed mainly because of the
> deprecation of IPv6 site-local unicast address and the coming of ULA.
> Additionally, the rule 9 of the destination address selection rules,
> namely the longest matching rule, is known for its adverse effect on
> the round robin DNS technique.  This document covers these essential
> points to be modified and proposes possible useful changes to be
> included in the revision of RFC 3484.
>
>
>
> The IETF Secretariat.
>
>

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------