IPv6 Routing table will be bloated?

Sven Olaf Kamphuis sven at cb3rob.net
Tue Oct 26 18:19:39 UTC 2010


On Tue, 26 Oct 2010, Randy Carpenter wrote:

> ----- Original Message -----
>> On 10/26/2010 12:04 PM, Nick Hilliard wrote:
>>> In practice, the RIRs are implementing sparse allocation which makes
>>> it
>>> possible to aggregate subsequent allocations. I.e. not as bad as it
>>> may
>>> seem.
>>>
>>
>> Except, if you are given bare minimums, and you are assigning out to
>> subtending ISPs bare minimums, those subtending ISPs will end up with
>> multiple networks. Some of them are BGP speakers. I can't use sparse
>> allocation because I was given minimum space and not the HD-Ratio
>> threshold space.
>
> Wait... If you are issuing space to ISPs that are multihomed, they should be getting their own addresses. Even if they aren't multihomed, they should probably be getting their own addresses. Why would you be supplying them with address space if they are an ISP?
>
> -Randy

to my knowledge, RIPE still does not issue ipv6 PI space.
so giving them their own space, is "problematic" to say the least.

-- 
Greetings,

Sven Olaf Kamphuis,
CB3ROB Ltd. & Co. KG
=========================================================================
Address: Koloniestrasse 34         VAT Tax ID:      DE267268209
          D-13359                   Registration:    HRA 42834 B
          BERLIN                    Phone:           +31/(0)87-8747479
          Germany                   GSM:             +49/(0)152-26410799
RIPE:    CBSK1-RIPE                e-Mail:          sven at cb3rob.net
=========================================================================
<penpen> C3P0, der elektrische Westerwelle

=========================================================================

Confidential: Please be advised that the information contained in this
email message, including all attached documents or files, is privileged
and confidential and is intended only for the use of the individual or
individuals addressed. Any other use, dissemination, distribution or
copying of this communication is strictly prohibited.






More information about the NANOG mailing list