Fwd: RFC 3484 Section 6 Rule 9

"Arifumi Matsumoto" <a@arifumi.net> Sat, 07 June 2008 02:01 UTC

Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipngwg-archive@lists.ietf.org
Delivered-To: ietfarch-ipngwg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E5F983A6872; Fri, 6 Jun 2008 19:01:06 -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 7FCC13A6911 for <ipv6@core3.amsl.com>; Fri, 6 Jun 2008 19:01:04 -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 N5GrNo7e+Tc4 for <ipv6@core3.amsl.com>; Fri, 6 Jun 2008 19:01:03 -0700 (PDT)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by core3.amsl.com (Postfix) with ESMTP id B08183A6BD8 for <ipv6@ietf.org>; Fri, 6 Jun 2008 19:00:55 -0700 (PDT)
Received: by yw-out-2324.google.com with SMTP id 3so718072ywj.49 for <ipv6@ietf.org>; Fri, 06 Jun 2008 19:01:06 -0700 (PDT)
Received: by 10.150.12.3 with SMTP id 3mr1354069ybl.15.1212804066288; Fri, 06 Jun 2008 19:01:06 -0700 (PDT)
Received: by 10.150.11.21 with HTTP; Fri, 6 Jun 2008 19:01:06 -0700 (PDT)
Message-ID: <7b1e7a950806061901i6364c2a7u26c6172190b1801b@mail.gmail.com>
Date: Sat, 07 Jun 2008 11:01:06 +0900
From: Arifumi Matsumoto <a@arifumi.net>
To: ipv6@ietf.org
Subject: Fwd: RFC 3484 Section 6 Rule 9
In-Reply-To: <4849CE64.4080205@gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
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> <4849CE64.4080205@gmail.com>
X-Google-Sender-Auth: 456cb797beaea6fa
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

Let me switch to 6man ML.
# Brian, thank you for redirection ;)

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
--------------------------------------------------------------------
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------