Re: RFC 3484 Section 6 Rule 9
"Arifumi Matsumoto" <a@arifumi.net> Tue, 03 June 2008 14:43 UTC
Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9B4943A68F4; Tue, 3 Jun 2008 07:43:30 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 836A33A6900 for <ietf@core3.amsl.com>; Tue, 3 Jun 2008 07:43:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 9dwVng36+Bwz for <ietf@core3.amsl.com>; Tue, 3 Jun 2008 07:43:26 -0700 (PDT)
Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28]) by core3.amsl.com (Postfix) with ESMTP id B14CF3A68E3 for <ietf@ietf.org>; Tue, 3 Jun 2008 07:43:26 -0700 (PDT)
Received: by yx-out-2324.google.com with SMTP id 8so132321yxg.49 for <ietf@ietf.org>; Tue, 03 Jun 2008 07:43:26 -0700 (PDT)
Received: by 10.151.141.16 with SMTP id t16mr2593183ybn.50.1212504206398; Tue, 03 Jun 2008 07:43:26 -0700 (PDT)
Received: by 10.150.148.21 with HTTP; Tue, 3 Jun 2008 07:43:26 -0700 (PDT)
Message-ID: <7b1e7a950806030743l7afffe7ch899dc91347b23a08@mail.gmail.com>
Date: Tue, 03 Jun 2008 23:43:26 +0900
From: Arifumi Matsumoto <a@arifumi.net>
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
Subject: Re: RFC 3484 Section 6 Rule 9
In-Reply-To: <4843FE7D.2060503@it.uc3m.es>
MIME-Version: 1.0
Content-Disposition: inline
References: <200806021350.m52Do7tj032327@drugs.dv.isc.org> <4843FE7D.2060503@it.uc3m.es>
X-Google-Sender-Auth: 23055a785f19f138
Cc: Mark Andrews <Mark_Andrews@isc.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
Hi all, 2008/6/2 marcelo bagnulo braun <marcelo@it.uc3m.es>: ... > so, are you suggesting to keep rule 8 of source address selection > (longest prefix match) and remove rule 9 of destiantion address > selection (longest prefix match)? > > btw, an analysis of some multihomed scenarios and the impact of longest > prefix match can be found at > http://www.ietf.org/internet-drafts/draft-ietf-v6ops-addr-select-ps-06.txt. > > From the draft, it is possible to see that it helps, but not that much > and it is probably worth having better support. But i am not sure we > should simply remvoe it with an errata. IMHO, we should actually solve > this problem and provide a solution for multiprefixed sites I'm one of the authors of the above mentioned draft. This draft shows the problematic cases with the default address selection rules defined in RFC 3484. Some of them are resulted from the longest matching rule. So, I don't feel comfortable to see the above sentence telling that this draft supports the longest matching rule. IMHO, the longest matching rule should be deleted from IPv4 and IPv6 in order to preserve the DNS Round-Robin mechanism. Or, at least, this rule should be configurable and should be off by default. Now that the DNS RR is widely used and IPv6 hierarchical address allocation is spoiled, we don't have a reasonable excuse for keeping the rule 9. DNS RR cannot be implemented without the universal address selection behavior. However, local optimization of traffic engineering owing to dst and src address selection can be implemented locally, for example, by manipulating the address selection policy table. The automization of this manipulation process is the motivation for our proposal: http://www.watersprings.org/pub/id/draft-fujisaki-dhc-addr-select-opt-05.txt which is currently expired, though. I have another expired draft: http://www.watersprings.org/pub/id/draft-arifumi-ipv6-rfc3484-revise-00.txt I'll include this issue of rule 9 in this draft and post it to 6man sooner. Kindest regards, Arifumi Matsumoto _______________________________________________ IETF mailing list IETF@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- Re: RFC 3484 Section 6 Rule 9 Mark Andrews
- Re: RFC 3484 Section 6 Rule 9 marcelo bagnulo braun
- Re: RFC 3484 Section 6 Rule 9 Mark Andrews
- RFC 3484 Section 6 Rule 9 Mark Andrews
- Re: RFC 3484 Section 6 Rule 9 Pekka Savola
- Re: RFC 3484 Section 6 Rule 9 Mark Andrews
- Re: RFC 3484 Section 6 Rule 9 marcelo bagnulo braun
- Re: RFC 3484 Section 6 Rule 9 SM
- Re: RFC 3484 Section 6 Rule 9 Brian E Carpenter
- Re: RFC 3484 Section 6 Rule 9 Tony Finch
- Re: RFC 3484 Section 6 Rule 9 Mark Andrews
- Re: RFC 3484 Section 6 Rule 9 Leo Vegoda
- Re: RFC 3484 Section 6 Rule 9 Thomas Narten
- Re: RFC 3484 Section 6 Rule 9 Simon Josefsson
- Re: RFC 3484 Section 6 Rule 9 Ralph Droms
- Re: RFC 3484 Section 6 Rule 9 Simon Josefsson
- Re: RFC 3484 Section 6 Rule 9 Tony Finch
- Re: RFC 3484 Section 6 Rule 9 Simon Josefsson
- Re: RFC 3484 Section 6 Rule 9 Arifumi Matsumoto
- Re: RFC 3484 Section 6 Rule 9 Michael StJohns
- Re: RFC 3484 Section 6 Rule 9 Tony Finch
- Re: RFC 3484 Section 6 Rule 9 Michael StJohns
- Re: RFC 3484 Section 6 Rule 9 Tony Finch
- Re: RFC 3484 Section 6 Rule 9 Brian E Carpenter
- Re: RFC 3484 Section 6 Rule 9 Joe Abley
- Re: RFC 3484 Section 6 Rule 9 Brian E Carpenter