<p dir="ltr">Hi Jeroen,</p>
<p dir="ltr">Sorry for top-posting, I am on a mobile device.</p>
<p dir="ltr">I spoke before of SAGE-AU, but this post now comes from my other "persona" - that of an employee of a multinational organisation.</p>
<p dir="ltr">We have recently put together an IPv6 strategy, and there are two options we are investigating - either a single /32 PI allocation globally, or a /32 PI per region (aligned with the RIRs). The point is to have an internally contiguous IP addressing scheme (or as close as possible, but then use the same address space publicly as well (NAT is evil). The preference is for the single global allocation, but I don't see regional /32 allocations as a significant overhead.</p>
<p dir="ltr">Either way, the plan is to take /32 PI space and split it into a /48 per site. Some of those sites are aggregated with a single point of Internet connectivity, but even so, just in Asia Pacific, we are talking about 5 different countries in which we'd be advertising our various /48 allocations - and there is a different carrier per Internet connection.</p>
<p dir="ltr">If I am reading what you are saying correctly, we can't use either a single global /32 of PI space or even a /32 of PI space per region and split it up into multiple sites. Globally we're looking at several hundred sites (which incidently is probably more routes than SAGE-AU members are likely to produce in the near future) - are you are suggesting that carriers will drop/filter our advertisements and cause us issues with IPv6 Internet connectivity?</p>
<div class="gmail_quote">On 05/07/2014 12:18 AM, "Jeroen Massar" <<a href="mailto:jeroen@massar.ch">jeroen@massar.ch</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 2014-07-04 08:47, James Andrewartha wrote:<br>
> Hi Jeroen,<br>
><br>
> On Fri, 4 Jul 2014, Jeroen Massar wrote:<br>
><br>
>> Do note that anybody who is going to announce that prefix in a useful<br>
>> manner also needs to have proper routing equipment to handle a full BGP<br>
>> feed. The cost of that kind of equipment, the transit payments and the<br>
>> engineers that do that will add up to a LOT more than $1200 PA :)<br>
><br>
> Obviously you haven't seen what people do with cheap Mikrotiks :P<br>
<br>
I (un)fortunately have seen them and other such setups.<br>
<br>
They are great for starting out, but people also think they can have<br>
more than 2 full-transits on them and have a stable connection and/or<br>
that they can compare to the more 'professional' grade routers that are<br>
out there ;)<br>
<br>
I do think that it is great that such systems, or just a simple<br>
Supermicro with a Xeon E5 and Bird or Quagga on it, exists as it does<br>
enable a lot more people to connect to this amazing thing called the<br>
Internet and start new businesses.<br>
<br>
For more networks to stay on connecting though, that table size should<br>
not be too huge as otherwise starting out on the edge will not be<br>
possible at one point or another.<br>
<br>
Hence this whole thread that networks do filter and that one should be<br>
aware of not using portions of PA space as PI, as that will not work.<br>
<br>
> More seriously, is wanting a different routing policy an acceptable reason<br>
> for a second allocation? I can imagine ISPs might want to advertise<br>
> seperate ranges in different states, do they then need multiple /32s?<br>
<br>
A real, full-on ISP, likely no, as they can backhaul that traffic; if<br>
they are unable to then they are not a full-on ISP IMHO.<br>
<br>
If you are located in two disparate locations though and do not want to<br>
backhaul one will have a teeny problem.<br>
<br>
It can be partially solved by having your transits announce the /32, but<br>
announcing more specifics to your PEERS. Note the word PEERS there,<br>
hence not transits. Having one transit leak the more specific will cause<br>
all traffic to go there. Hence do avoid that.<br>
<br>
More importantly: The other side of the world does not need to know<br>
where that traffic needs to be delivered locally.<br>
<br>
> Even I split my IPv4 /22 into two /23s so I can advertise them out<br>
> different links (broadly - school owned device to AARNet, non-school owned<br>
> to commodity transit).<br>
<br>
(You are part of the 44% of de-aggregated prefixes on the net)<br>
<br>
> Can I ask APNIC for another PI /48 to achieve this?<br>
> Their policies are unclear.<br>
<br>
You would have to justify why those locations are distinct and why they<br>
need separate routable blocks.<br>
<br>
IMHO, using the above trick of announcing more specifics to peers and<br>
the aggregate to transits is likely the better trick.<br>
<br>
The other variant would be to determine if you really need your own<br>
space (eg because of independence for whatever reason) or if you can<br>
live with a chunk of PA of somebody else.<br>
<br>
Note that quite a few universities/school networks in IPv6 simply use a<br>
/48 out of the /32 they get from their NREN. Though there is a school in<br>
Switzerland (Cantonsschule Zug) who have their own /32 that they use for<br>
connectivity for the multiple locations that they have and for<br>
connectivity of their students (yep, they do cable and dsl as a school).<br>
<br>
> <a href="https://www.apnic.net/publications/media-library/documents/resource-guidelines/ipv6-guidelines" target="_blank">https://www.apnic.net/publications/media-library/documents/resource-guidelines/ipv6-guidelines</a><br>
> seems to be the main one, and is somewhat contradictory. 6.2 says for<br>
> operational, geographic or regulatory reasons your network can be<br>
> considered as multiple discrete networks. So that covers the ISP case. My<br>
> site is multihomed, so I qualify under 9.1.1. However the end of section 2<br>
> says "Only one IPv6 address block is to be assigned to an organization<br>
> upon an initial request; subnets of this block may be assigned by the<br>
> organization to its different sites if needed."<br>
> But you claim (in contrast to Mark) that a /56 advertisement is verboten,<br>
> which conflicts with that.<br>
<br>
I have not claimed that a /56 advertisement is verboten, I did not even<br>
mention a /56 yet in this thread. But a /56 definitely will not go far<br>
in BGP, as that is not an allocation size that the RIRs give out.<br>
<br>
But yes, a end-site should get at minimum either a /56 or /48. Typically<br>
a /56 is "good enough" for home networks, while a /48 should be for any<br>
business type of situation.<br>
<br>
IMHO for ease of assignment one should just give everybody a /48.<br>
<br>
RIR policies allow fully for it and there are enough /48 in the global<br>
IPv6 space to do so for a long long time. (Note that German & France<br>
telecom both got /19s based on their /48 for every customer<br>
justification, for /56 they would have had enough with a lot less)<br>
<br>
<br>
Note also the differences between:<br>
<br>
- allocation<br>
RIR/NIR -> LIR<br>
~/16 - /32 PA or ~/40 - /48 PI<br>
<br>
- assignment<br>
LIR -> end-site<br>
typically a /48, but up-to a /40 happens too<br>
<br>
- advertisement/announcement<br>
What you throw into BGP<br>
depends on the allocation size as from the RIR, no more-specifics<br>
See also <a href="http://www.space.net/~gert/RIPE/ipv6-filters.html" target="_blank">http://www.space.net/~gert/RIPE/ipv6-filters.html</a><br>
<br>
> 9.2 then does say discrete netwoks qualify, so if I can demonstrate the<br>
> need APNIC should give me another /48 even though I could just as easily<br>
> split my original /48.<br>
<br>
Yes, you can "split" your network internally, but you should not be<br>
announcing it that way, possibly to peers, but definitely not to transits.<br>
<br>
> In the end there's no real difference to me, so is<br>
> the only gain that network operators have to fill out a bit more paperwork<br>
> to justify their operational reasons for extra prefixes to advertise for<br>
> traffic engineering?<br>
<br>
Indeed.<br>
<br>
> Seems a bit like overkill IMHO, and anyone who's<br>
> going to the effort of traffic engineering isn't going to be put off by a<br>
> little paperwork.<br>
<br>
Bingo.<br>
<br>
It is a bit overkill in a way, but in the long term it might be<br>
beneficial to the size of the routing tables, see above.<br>
<br>
Note that you can get a /32 PA with 65k /48s, but the RIRs will never<br>
give you 65k PI blocks for your distinct locations, you should be<br>
aggregating those. Unless you are an insanely popular and big LIR with a<br>
huge 200k businesses as distinct customers, but if you are then you<br>
would not be discussing these rules here asking questions and would have<br>
done so already ;)<br>
<br>
Greets,<br>
Jeroen<br>
<br>
_______________________________________________<br>
AusNOG mailing list<br>
<a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
<a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
</blockquote></div>