<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Keeping this on-list, even though specific to my situation, in case
it answers others questions:<br>
<br>
To chime in on this Skeeve, I currently have a /32 assigned from
APNIC (inside 2400::/12), so by what your saying I can only
advertise the /32 and never anything bigger (smaller, lol)?<br>
<br>
Should I be requesting a larger /30 from APNIC so I have the
opportunity to split /32's across sites?<br>
<br>
If I own a /32 how do I manage multi-homing in regards to trying to
manage inbound traffic? A decent, easy method of this now is path
prepending different /24's on your transit providers to try and
artificially generate more traffic on a peer, how would I go about
similar things in IPv6? Or is this where having multiple /32's comes
in to effect and doing the same, but at the /32 level?<br>
<br>
Is it possible to request blocks from APNIC that fall within a range
that is allowed to go down to /48? Or is this just problematic in
general?<br>
<br>
Thanks,<br>
Joe<br>
<br>
<div class="moz-cite-prefix">On 03/07/14 15:35, Skeeve Stevens
wrote:<br>
</div>
<blockquote
cite="mid:CAEUfUGM3NbBb_wN46_ZHr6VF9Ej6-0fC2nHOWWLTJBFKyF-VLA@mail.gmail.com"
type="cite">
<div dir="ltr">OK... so here goes.
<div><br>
</div>
<div>My opinion is that what SAGE is doing is well meaning, but
ultimately problematic.</div>
<div><br>
</div>
<div>They should not be breaking down their /32 for members to
announce /48's.</div>
<div><br>
</div>
<div>The reasoning for this was a significant part of my policy
proposal 083 a couple of years ago (<a moz-do-not-send="true"
href="https://www.apnic.net/policy/proposals/prop-083">https://www.apnic.net/policy/proposals/prop-083</a>)</div>
<div><br>
</div>
<div>The issue was that if I got a /32, I was not able to break
it down for announcement if I want to put part of it in a
different (non-connected/aggregated) location. So the policy
allows you to get another block to announce in that location.</div>
<div><br>
</div>
<div>The key issue here is that SAGE's /32 allocation is from a
block, where if strict BOGON listing is used, means their
member routes will be dropped.</div>
<div><br>
</div>
<div>For example, the current ipv6 BOGON list is: (<a
moz-do-not-send="true"
href="http://www.space.net/%7Egert/RIPE/ipv6-filters.html">http://www.space.net/~gert/RIPE/ipv6-filters.html</a>)</div>
<div><br>
</div>
<div>
<pre style="color:rgb(0,0,0)">ipv6 prefix-list ipv6-ebgp-strict deny 3ffe::/16 le 128
ipv6 prefix-list ipv6-ebgp-strict permit 2001:500::/30 ge 48 le 48
ipv6 prefix-list ipv6-ebgp-strict deny 2001:db8::/32 le 128
ipv6 prefix-list ipv6-ebgp-strict permit 2001::/32
ipv6 prefix-list ipv6-ebgp-strict permit 2001::/16 ge 35 le 35
ipv6 prefix-list ipv6-ebgp-strict permit 2001::/16 ge 19 le 32
ipv6 prefix-list ipv6-ebgp-strict permit 2001:0678::/29 le 48
ipv6 prefix-list ipv6-ebgp-strict permit 2001:0c00::/23 ge 48 le 48
ipv6 prefix-list ipv6-ebgp-strict permit 2001:13c7:6000::/36 le 48
ipv6 prefix-list ipv6-ebgp-strict permit 2001:13c7:7000::/36 le 48
ipv6 prefix-list ipv6-ebgp-strict permit 2001:43f8::/29 ge 40 le 48
ipv6 prefix-list ipv6-ebgp-strict permit 2002::/16
ipv6 prefix-list ipv6-ebgp-strict permit 2003::/16 ge 19 le 32
<b>ipv6 prefix-list ipv6-ebgp-strict permit 2400::/12 ge 19 le 32</b>
ipv6 prefix-list ipv6-ebgp-strict permit 2600::/12 ge 19 le 32
ipv6 prefix-list ipv6-ebgp-strict permit 2610::/23 ge 24 le 32
ipv6 prefix-list ipv6-ebgp-strict permit 2620::/23 ge 40 le 48
ipv6 prefix-list ipv6-ebgp-strict permit 2800::/12 ge 19 le 32
ipv6 prefix-list ipv6-ebgp-strict permit 2a00::/12 ge 19 le 32
ipv6 prefix-list ipv6-ebgp-strict permit 2801:0000::/24 le 48
ipv6 prefix-list ipv6-ebgp-strict permit 2c00::/12 ge 19 le 32
ipv6 prefix-list ipv6-ebgp-strict deny 0::/0 le 128</pre>
</div>
<div>
<div class="gmail_extra">If you look at the block SAGE is in,
their block, in strict form, means anything smaller than a
/32 will be dropped.</div>
<div class="gmail_extra">
<br>
</div>
<div class="gmail_extra">Members who get a /48 from APNIC are
from a different pool, 2001 somewhere, which has a /48
length.</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">So... sorry SAGE, but you pooched
this one.<br clear="all">
<div>
<div dir="ltr">
<div><br>
...Skeeve</div>
<div><br>
</div>
<div>
<div><b style="font-size:13px;font-family:Calibri">Skeeve
Stevens - </b><span
style="font-size:13px;font-family:Calibri">eintellego
Networks Pty Ltd</span></div>
<div>
<div><span
style="font-family:Calibri;font-size:13px"><a
moz-do-not-send="true"
href="mailto:skeeve@eintellegonetworks.com"
target="_blank">skeeve@eintellegonetworks.com</a> ; <a
moz-do-not-send="true"
href="http://www.eintellegonetworks.com/"
target="_blank">www.eintellegonetworks.com</a></span><font>
<p
style="font-family:Calibri;font-size:13px;margin:0px">
Phone: 1300 239 038; Cell +61 (0)414 753 383
; <a moz-do-not-send="true">skype://skeeve</a></p>
<p
style="font-family:Calibri;font-size:13px;margin:0px"><a
moz-do-not-send="true"
href="http://facebook.com/eintellegonetworks"
target="_blank">facebook.com/eintellegonetworks</a> ; <a
moz-do-not-send="true"
href="http://linkedin.com/in/skeeve"
target="_blank">linkedin.com/in/skeeve</a> </p>
<p
style="font-family:Calibri;font-size:13px;margin:0px"><a
moz-do-not-send="true"
href="http://twitter.com/theispguy"
target="_blank">twitter.com/theispguy</a><span
style="color:rgb(0,0,0)"> ; blog: </span><a
moz-do-not-send="true"
href="http://www.theispguy.com/"
target="_blank">www.theispguy.com</a><br>
</p>
<p
style="font-family:Calibri;font-size:13px;margin:0px"><img
moz-do-not-send="true"
src="http://eintellegonetworks.com/logos/ein09.png"><br>
</p>
<p style="margin:0px"><span
style="color:rgb(127,0,127);font-family:Calibri,sans-serif;font-size:13px">The
Experts Who The Experts Call</span></p>
</font></div>
<div
style="font-family:Calibri,sans-serif;font-size:14px;color:rgb(127,0,127)"><span
style="color:rgb(0,32,96);font-size:13px">Juniper
- Cisco </span><span
style="color:rgb(0,32,96);font-size:13px">-
Cloud</span><span
style="color:rgb(0,32,96);font-size:13px"> </span><span
style="color:rgb(0,32,96);font-size:13px">-
Consulting</span><span
style="color:rgb(0,32,96);font-size:13px"> </span><span
style="color:rgb(0,32,96);font-size:13px">- IPv4
Brokering</span></div>
</div>
</div>
</div>
</div>
<br>
<br>
<div class="gmail_quote">On Thu, Jul 3, 2014 at 2:30 PM,
Jeroen Massar <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:jeroen@massar.ch"
target="_blank">jeroen@massar.ch</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
On 2014-07-02 23:41, Robert Hudson wrote:<br>
> > So whats the min mask length. So it I
wanted to multihome would I be<br>
> > okay with 1 /48 or will up streams take
/49-64 ?<br>
><br>
> /48 is the accepted minimum.<br>
><br>
><br>
> Which is why SAGE-AU settled on offering an IPv6
/48 to every member<br>
> (and yes, this does mean that as a business, if all
you want is an IPv6<br>
> /48, you can get a completely portable /48
allocation from SAGE-AU for<br>
> $165 a year instead of paying the APNIC membership
fee if the member you<br>
> pay for agrees to utilise the allocation for your
business purposes).<br>
<br>
Quick check:<br>
<br>
inet6num: 2406:C500::/32<br>
netname: TSAGOA<br>
descr: The System Administrators Guild of
Australia<br>
country: AU<br>
<br>
That is a single /32, out of the PA block of APNIC.
Hence, unless you<br>
convince every single ISP in the world to accept it, the
only thing you<br>
can announce is that /32, nothing else.<br>
<br>
More specifics will properly be dropped.<br>
<br>
Please don't spam the BGP tables with more specifics. If
you need PI, go<br>
get a distinct PI block for that site from your
favourite LIR.<br>
<br>
Greets,<br>
Jeroen<br>
<br>
<br>
Oh and yes, it will be a lot of fun when some large
company is going to<br>
split and then have to split up their IPv6 address
space, somebody will<br>
be renumbering a lot of hosts... ;)<br>
<br>
_______________________________________________<br>
AusNOG mailing list<br>
<a moz-do-not-send="true"
href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
<a moz-do-not-send="true"
href="http://lists.ausnog.net/mailman/listinfo/ausnog"
target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
AusNOG mailing list
<a class="moz-txt-link-abbreviated" href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a>
<a class="moz-txt-link-freetext" href="http://lists.ausnog.net/mailman/listinfo/ausnog">http://lists.ausnog.net/mailman/listinfo/ausnog</a>
</pre>
</blockquote>
<br>
</body>
</html>