[194440] in North American Network Operators' Group
Re: ipv6 accepted & announcement size upto /48 or longer than /48 ?
daemon@ATHENA.MIT.EDU (Job Snijders)
Thu Apr 27 13:06:19 2017
X-Original-To: nanog@nanog.org
Date: Thu, 27 Apr 2017 19:05:12 +0200
From: Job Snijders <job@ntt.net>
To: Seth Mattinen <sethm@rollernet.us>
In-Reply-To: <2540460d-c325-7c7c-0663-bd20940699ec@rollernet.us>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Thu, Apr 27, 2017 at 09:30:48AM -0700, Seth Mattinen wrote:
> On 4/27/17 06:47, root <junosiosxr@gmail.com> wrote:
> >
> > Am i right ?
> >
> > Policy for ipv4 accept and send upto /24
> > Policy for ipv6 accept and send upto /48
> >
> > -------------------------------------------------------------
> >
> > I confused when i checked the ipv6 prefix at route-view and ntt looking
> > glass.
> >
> > Example : seem like AS2914 accepted the /64 prefix from AS20940
>
> Internally, sure.
NTT accepts "longer-than-/48" (and similarly "longer-than-/24") prefixes
only from customers, if an exact matching route6: or route: object
exists in the IRR. NTT will announce such more-specifics to customers,
but not to peers.
This is useful for customers who want to use NTT's backbone to connect
their satellite sites to each other, as an alternative to building out
their own backbone.
Personally I wouldn't expect global reachability for prefixes longer
than /48 or /24, so you'll see that most people make sure a covering
announcement also exists. In a controlled environments these
more-specifics can be very useful.
Kind regards,
Job
