Re: IPv6 concern
Jeroen Massar <jeroen@unfix.org> Tue, 22 May 2012 11:57 UTC
Return-Path: <jeroen@unfix.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D66921F847B for <ipv6@ietfa.amsl.com>; Tue, 22 May 2012 04:57:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nJU3HWm3mICv for <ipv6@ietfa.amsl.com>; Tue, 22 May 2012 04:57:08 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [IPv6:2a01:4f8:130:74c1:5054:ff:fec4:f7d4]) by ietfa.amsl.com (Postfix) with ESMTP id 4399821F847A for <ipv6@ietf.org>; Tue, 22 May 2012 04:57:08 -0700 (PDT)
Received: from yomi.ch.unfix.org (117-1.5-85.cust.bluewin.ch [85.5.1.117]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id 9D1D5801C813; Tue, 22 May 2012 13:56:54 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unfix.org; s=DKIM2009; t=1337687824; bh=xj+MZekD7iN8WnVQQ0Bo0S/Z5BbZa4A7hTHg07JErlU=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=cnWIULvhNEfwdUNlNVvm30JXFlUm81vCSOoHJCa09ciEln44QLzo+KoUtaGmare8V +qKk6h75PugQmvQl4S1IX90j2YyoaHtejcTHUDoba+r1JeCijNNCGfawGG5n3Y3KrT ICsbh/E8MG4meIjWPGR8Wg8iTeu74yG8vjaltHgLhgREpvMI1zSIXB2R83Kgch4oK0 qpd6pY6j/8kfD54D9H2dNbNIgSIWzAvbt20Kn38nXJOD19DAF36/MmHdJ7JoW0yCEj 7Tw2rV7xWfL6tn8LgsG5+HJNdrXX98tp4avk3QczClhcvteSiGLVx0Wegd1JxqiDwq kPhKfnF7P/Ubw==
Message-ID: <4FBB7F06.9040609@unfix.org>
Date: Tue, 22 May 2012 13:56:54 +0200
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: justin franks <justintfranks@gmail.com>
Subject: Re: IPv6 concern
References: <CAMsS2gCFTOZCpZHyUyjMS_+rqznUGxJjkjH8X=fyoLdV44hFfg@mail.gmail.com>
In-Reply-To: <CAMsS2gCFTOZCpZHyUyjMS_+rqznUGxJjkjH8X=fyoLdV44hFfg@mail.gmail.com>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Tue, 22 May 2012 11:57:09 -0000
On 2012-05-22 03:12 , justin franks wrote: > Hello, > I am an Internet Engineer. Specifically large scale ISP and Data Center > networks. I understand we need IPv6 and am working towards that as well. > However, I have major concerns about 2 areas in IPv6 > 1. The BGP prefix filtering > 2. The assignment of multiple /32 or /48's to the same Organization by > various RIR's. > I have typed up a brief one page document here that explains some very > valid points. > http://www.inetassociation.com/ipv6subnetdesign.htm I do not grasp what you are trying to state with your message as it is very unstructured. But a couple of comments to statements in that text: > Really big organizations and ISP's are given a /32 block. Actually, per default an ISP will get a /32, really big ones will get larger blocks, up to /13 have been seen already. http://www.sixxs.net/tools/grh/dfp/ shows 1 /13 (spread into 14x /22), 2x /19 and several /20's as an example. > Smaller organizations are given a /48 block You mean: Organizations who request a PI block and cannot justify more than a /48. > Based on those numbers you now know which size prefix you request > from your RIR. A /48 or a /32. Or much much much larger, like those /19s mentioned above. You are obviously forgetting about HD ratio and the amount of customers that actually are served with these blocks. "Child Prefixes" are just called subprefixes > This model is super modular, super simple and super scalable. It is not, as if you made the wrong choice when chunking up the prefix you will need to move a little other chunk somewhere else and you will just end up in routing mess anyway. > If it was me I would only advertise Child Prefixes from the > appropriate BGP routers per region. [...] > There needs to be an industry standard on what is the smallest prefix > allowed to be advertised in BGP for IPv6. There is no standard now. > Once a standard is made then we can begin to plan and design global > networks accordingly. Please actually check http://www.space.net/~gert/RIPE/ipv6-filters.html for current operational practice that has been in use for nearly a decade already. You should only expect the assigned-from-RIR block to be accepted, nothing else, especially not larger announcements. As such your first concern is because you do not know about current operational practice. I suggest you follow: http://lists.cluenet.de/mailman/listinfo/ipv6-ops and visit RIPE, APNIC, NANOG etc meetings that cover these subjects. For your second concern, indeed, there are various organizations that have received a disjunct prefix per RIR and in some cases almost a disjunct prefix per country. These organizations are typically very very large though and tend to have disjunct routing policies too. And you do not want to ship your traffic yourself to the otherside of the world, it is just too messy, with multiple prefixes all that is solved. Greets, Jeroen
- IPv6 concern justin franks
- Re: IPv6 concern Jeroen Massar