<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hi Shane,</div><div><br></div>Maybe consider: <a href="http://tools.ietf.org/html/rfc2374">http://tools.ietf.org/html/rfc2374</a><div><br><div><div><div>"The SLA ID field is used by an individual organization to create its</div><div>own local addressing hierarchy and to identify subnets. This is</div><div>analogous to subnets in IPv4 except that each organization has a much</div><div>greater number of subnets. The 16 bit SLA ID field support 65,535</div><div>individual subnets."</div><div><br></div><div>You could reserve some bits from here to identify the region within the </div><div>Asia Pacific, location within the region, etc. You could put other flags</div><div>in here, too (customer vs infrastructure?).</div><div><br></div><div>- Tom</div></div><div><br><div><div>On 21/05/2010, at 3:59 AM, Shane Short wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Howdy Guys,<br>We've got our /32 from APNIC a while ago, I'm now finally looking to begin rolling this out across the network and to be honest, the sheer amount of space is doing my head in a little..<br>I did a bit of a google around and I couldn't really find any 'best practice' for splitting up a subnet of this size..<br><br>How're people here picking which subnets to allocate customers? are you splitting it up into chunks of /48s,/56's and /64s and handing them out sequentially?<br><br>Thanks,<br>Shane<br></div></blockquote></div><br><div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>-- <br>Kind Regards,<br><br>Tom Wright<br>Internode Network Operations<br>P: +61 8 8228 2999<br>W: <a href="http://www.internode.on.net/">http://www.internode.on.net</a></div></div>
</div>
<br></div></div></div></body></html>