[194439] in North American Network Operators' Group
Re: ipv6 accepted & announcement size upto /48 or longer than /48 ?
daemon@ATHENA.MIT.EDU (Theodore Baschak)
Thu Apr 27 12:56:14 2017
X-Original-To: nanog@nanog.org
In-Reply-To: <CALPKgOw8b8JaLj6X7XkJ6qzTccwSzY8bp2ESgSnr_HpBLjhnBw@mail.gmail.com>
From: Theodore Baschak <theodore@ciscodude.net>
Date: Thu, 27 Apr 2017 11:56:09 -0500
To: "NANOG Operators' Group" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Thu, Apr 27, 2017 at 8:47 AM, root <junosiosxr@gmail.com> <
junosiosxr@gmail.com> wrote:
> Hi,
>
>
> Am i right ?
>
> Policy for ipv4 accept and send upto /24
> Policy for ipv6 accept and send upto /48
>
Sending up to a /24 is an oversimplification in today's post-IPv4
exhaustion world. ARIN now has a "Dedicated IPv4 block to facilitate IPv6
Deployment" (23.128.0.0/10) from which they are may allocate in /24 thru
/28 sized blocks.
RIPE has tested visibility of longer than /24's and reported on that in
2014 and 2015, both with and without IRR entries.
https://labs.ripe.net/Members/emileaben/propagation-of-longer-than-24-ipv4-prefixes
and
https://labs.ripe.net/Members/emileaben/has-the-routability-of-longer-than-24-prefixes-changed
Theodore Baschak - AS395089 - Hextet Systems
https://bgp.guru/ - https://hextet.net/
http://mbix.ca/ - http://mbnog.ca/
