Re: RFC 3484 Section 6 Rule 9

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 06 June 2008 23:55 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 31F3F3A6A29; Fri, 6 Jun 2008 16:55:16 -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 08B783A6AA4 for <ipv6@core3.amsl.com>; Fri, 6 Jun 2008 16:55:15 -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=[AWL=0.000, 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 G-o7SNe8U6mX for <ipv6@core3.amsl.com>; Fri, 6 Jun 2008 16:55:14 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.175]) by core3.amsl.com (Postfix) with ESMTP id 1C90F3A6A74 for <ipv6@ietf.org>; Fri, 6 Jun 2008 16:55:14 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 27so1249101wfd.31 for <ipv6@ietf.org>; Fri, 06 Jun 2008 16:55:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=wRJ7XSDpVAGaGdaqzQVveunuwwUphGRDsrVnKPk1cb4=; b=sdJIk/s4NhKchfn8vA10oX0Ib327C43RvHHMmH6ZyIAu9HERhbWridegVMbH5N7xgw OoYPt9sYCKsEGmKg6H0mv5FMXS9qEYvMN4GSuqEZIJap+DQma+bWPE2N9tJaTzTuG7JS Vv94235a8C/UJ/3zQ5FXkvrVeHFs4gKE6zU18=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=BBH3zOoGyQAgUjHkMzUGYohiE7HcY49W6J6lsRwZt6DC+rH7XgeiVNaTalBN4tNov9 m9vpG4Bqu6F1SOWBF/wwWFAbxlMVc0CubJnrPW14oW0dS9ngiASlmThedppnYItH6a5u wZcVcmlPSbYkH33snmOnjwwev+wsaOQz6jGxY=
Received: by 10.143.33.12 with SMTP id l12mr239553wfj.272.1212796524432; Fri, 06 Jun 2008 16:55:24 -0700 (PDT)
Received: from ?10.1.1.4? ( [118.93.185.187]) by mx.google.com with ESMTPS id 22sm10653496wfg.13.2008.06.06.16.55.21 (version=SSLv3 cipher=RC4-MD5); Fri, 06 Jun 2008 16:55:24 -0700 (PDT)
Message-ID: <4849CE64.4080205@gmail.com>
Date: Sat, 07 Jun 2008 11:55:16 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Arifumi Matsumoto <arifumi@nttv6.net>
Subject: Re: RFC 3484 Section 6 Rule 9
References: <C46AB084.3A7B8%leo.vegoda@icann.org> <4845B998.1010401@gmail.com> <884C2127-D98B-472E-B245-D18CE61D4018@ca.afilias.info> <48461822.8070608@gmail.com> <88E5E85A-3446-4490-B552-D8C624EC82F6@nttv6.net>
In-Reply-To: <88E5E85A-3446-4490-B552-D8C624EC82F6@nttv6.net>
Cc: marcelo bagnulo braun <marcelo@it.uc3m.es>, Mark Andrews <Mark_Andrews@isc.org>, 6man <ipv6@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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

Arifumi,

You got the wrong address for 6man...

   Brian

-------- Original Message --------
Subject: Re: RFC 3484 Section 6 Rule 9
Date: Fri, 6 Jun 2008 18:09:02 +0900
From: Arifumi Matsumoto <arifumi@nttv6.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, 6man@ietf.org
CC: Joe Abley <jabley@ca.afilias.info>,        marcelo bagnulo braun <marcelo@it.uc3m.es>,        Mark Andrews
<Mark_Andrews@isc.org>
References: <C46AB084.3A7B8%leo.vegoda@icann.org> <4845B998.1010401@gmail.com>
<884C2127-D98B-472E-B245-D18CE61D4018@ca.afilias.info> <48461822.8070608@gmail.com>

Let me switch to 6man ML.

Regarding this issue of RFC 3484 section 6 rule 9,
let me give you my two cents, which is conditional longest
matching rule application.

  When the length of matching bits of the destination
  address and the source address is longer than N,
  the rule 9 is applied. Otherwise, the order of the
  destination addresses do not change. (For DNS-RR)

The N should be configurable and I guess it should be 32
by default. This is simply because the two sites whose
matching bit length is longer than 32 are probably
adjacent.

Regards,
Arifumi Matsumoto

On 2008/06/04, at 13:20, Brian E Carpenter wrote:

> Joe,
>
>> It seems to me that direct assignment could quite possibly become the
>> default for small IPv6 sites in the ARIN region. IPv6 uptake to
>> date has
>> been so tiny that I don't think anybody can predict what behaviours
>> will
>> become prevalent if/when IPv6 takes off.
>
> We can't predict how economic actors will choose to act. What we can
> predict
> is catastrophe if ten or 100 million sites attempt to push /48
> advertisements
> out into BGP4. It would be highly irresponsible of any registry to
> pursue
> a policy that leads to such a result, until we have a technical
> solution
> to the resulting scaling problem. It's exactly because we don't have
> such
> a solution that the IPv6 design model is PA.
>
> I'm not shocked at the notion of a few hundred thousand early
> adopters of
> IPv6 getting PI prefixes. But that's a very different matter than
> millions.
>
> (This remains directly relevant to the subject of this thread. The
> infamous Rule 9 exists, right or wrong, because of PA addressing
> in IPv6.)
>
>    Brian
> _______________________________________________
> IETF mailing list
> IETF@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

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