nanog mailing list archives
Re: ipv6 accepted & announcement size upto /48 or longer than /48 ?
From: Job Snijders <job () ntt net>
Date: Thu, 27 Apr 2017 19:05:12 +0200
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 AS20940Internally, 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
Current thread:
- ipv6 accepted & announcement size upto /48 or longer than /48 ? root <junosiosxr () gmail com> (Apr 27)
- Re: ipv6 accepted & announcement size upto /48 or longer than /48 ? Seth Mattinen (Apr 27)
- Re: ipv6 accepted & announcement size upto /48 or longer than /48 ? Job Snijders (Apr 27)
- Re: ipv6 accepted & announcement size upto /48 or longer than /48 ? Theodore Baschak (Apr 27)
- Re: ipv6 accepted & announcement size upto /48 or longer than /48 ? Max Tulyev (Apr 27)
- Re: ipv6 accepted & announcement size upto /48 or longer than /48 ? Yuya KAWAKAMI (Apr 28)
- Re: ipv6 accepted & announcement size upto /48 or longer than /48 ? Seth Mattinen (Apr 27)