Re: RFC 3484 Section 6 Rule 9
Mark Andrews <Mark_Andrews@isc.org> Mon, 02 June 2008 13:53 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 F27F93A6D06; Mon, 2 Jun 2008 06:53:23 -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 8EBFC3A6D06 for <ietf@core3.amsl.com>; Mon, 2 Jun 2008 06:53:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 tBJ6bv3ISV4k for <ietf@core3.amsl.com>; Mon, 2 Jun 2008 06:53:21 -0700 (PDT)
Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc]) by core3.amsl.com (Postfix) with ESMTP id 5AC5428C170 for <ietf@ietf.org>; Mon, 2 Jun 2008 06:50:12 -0700 (PDT)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.2/8.14.2) with ESMTP id m52Do7tj032327; Mon, 2 Jun 2008 23:50:08 +1000 (EST) (envelope-from marka@drugs.dv.isc.org)
Message-Id: <200806021350.m52Do7tj032327@drugs.dv.isc.org>
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
From: Mark Andrews <Mark_Andrews@isc.org>
Subject: Re: RFC 3484 Section 6 Rule 9
In-reply-to: Your message of "Mon, 02 Jun 2008 08:45:59 +0200." <48439727.7050108@it.uc3m.es>
Date: Mon, 02 Jun 2008 23:50:07 +1000
Cc: 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: multipart/mixed; boundary="===============1019529866=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
> Well, longest prefix match is kind of useful in some scenarios i think. > > Imagine a site that is multihomed to two ISPs and has two PA address blocks. > > Now, longest prefix match ensures that when a node of the multihomed > site wants to contact any other customer of its own isps, it does > perform the correct source address selection and that is likely to be > critical for the communication to work, especially if the isps are doing > ingress filtering (i am assuming that the intra site routing of the > multihomed site will preffer the route through the ISP that owns the > prefix contained in the destiantion address) > > Even though this is one case and the problem is more general, i tend to > think that this is an importnat case and things would break more if this > rule didn't exist > > Regards, marcelo Section 6 Rule 9 is DESTINATION address selection. It provides absolutely no help when attempting to distingish a multi-homed destination that is not with your current ISP. It also won't help once your current ISP has more than one prefix. It doesn't help with PI clients connected to your current ISP. It biases what should be a random selection. There is no science that says a /30 match is better than a /28 or a /8 match. If one really wants to have directly connected clients of your ISP match then get a appropriate feed of prefixes and use it to build appropriate tables. We have the technology to distribute sets of prefixes. Just don't attempt to have longest match do the just because it can't do it except for PA address and even then only when your ISP has a single prefix. For any other senario it is biased garbage. > Mark Andrews escribió: > > This rule should not exist for IPv4 or IPv6. Longest match > > does not make a good sorting critera for destination address > > selection. In fact it has the opposite effect by concentrating > > traffic on particular address rather than spreading load. > > > > I received a request today asking us to break up DNS RRsets > > as a workaround to the rule. Can we please get a errata > > entry for RFC 3484 stating that this rule needs to be ignored. > > > > Mark > > > > -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org
_______________________________________________ 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