[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
using IPv6 address block across multiple locations
- Subject: using IPv6 address block across multiple locations
- From: joelja at bogus.com (Joel jaeggli)
- Date: Mon, 31 Oct 2011 09:01:01 -0700
- In-reply-to: <[email protected]>
- References: <CAP5kh1B9SbeA0T7EYtC2=PakUucyLk2WkxjwYaE470=jHGeMVA@mail.gmail.com> <[email protected]>
On 10/31/11 05:59 , Owen DeLong wrote:
> Ideally, you should put a /48 at each location.
>
> Owen
>
> On Oct 31, 2011, at 12:56 AM, Dmitry Cherkasov wrote:
>
>> Hello,
>>
>> Please advice what is the best practice to use IPv6 address block
>> across distributed locations.
>>
>> Recently we obtained our PI /48 from RIPE. The idea was to assign
>> partial slices from this block to different locations (we have
>> currently 3 offices in Europe and 2 in USA). All locations are
>> interconnected with static VPNs. Each location is supposed to
>> establish BGP session with local ISP. Partial prefix /56 + aggregate
>> /48 (with long AS PATH) are to be announced by each office.
>>
>> The problem we ran across is that ISP in US does not wish to accept
>> prefixes longer then /48 from us.
>> Need your advice: is this normal to distribute /48 by /56 parts across
>> locations or should we obtain separate /48 for each of them? Or maybe
>> we need /32 that can be split into multiple /48? Anyway we are not ISP
>> so /48 looks quite reasonable and sufficient for all our needs.
It's not because it can't be de-aggregated further in general. if you
have 5 discreet site you really need at /45. if you can tthe
announcements of the regions to something less specific than a /48 e.g.
a /46 then by all means do so.
>> Thank you.
>>
>> Dmitry Cherkasov
>
>