ipv6 accepted & announcement size upto /48 or longer than /48 ?
Hi, 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 NTT looking output Query Results: Router: Ashburn, VA - US Command: show bgp ipv6 unicast 2001:418:1401:9:: BGP routing table entry for 2001:418:1401:9::/64 Versions: Process bRIB/RIB SendTblVer Speaker 64282538 64282538 Last Modified: Oct 12 13:27:02.644 for 28w1d Paths: (1 available, best #1) Advertised to update-groups (with more than one peer): 0.10 0.28 0.38 0.39 0.40 0.49 Advertised to peers (in unique update groups): 2001:418:0:5000::9bd 2001:418:0:5000::1b7 2001:418:0:5000::fc3 2001:418:0:5000::5b1 Path #1: Received by speaker 0 Advertised to update-groups (with more than one peer): 0.10 0.28 0.38 0.39 0.40 0.49 Advertised to peers (in unique update groups): 2001:418:0:5000::9bd 2001:418:0:5000::1b7 2001:418:0:5000::fc3 2001:418:0:5000::5b1 20940 20940 2001:418:0:5000::419 (metric 5010) from (129.250.0.117) Origin IGP, metric 0, localpref 120, valid, confed-internal, best, group-best Received Path ID 0, Local Path ID 1, version 64282538 Community: 2914:370 2914:1009 2914:2000 2914:3000 20940:411 route-view : 2001:418:0:1000::F016 4 2914 304889 22799 30638084 0 0 1w0d 36959 route-views>show bgp ipv6 un nei 2001:418:0:1000::F016 routes | i /56 *> 2001:218:200E:100::/56 *> 2001:218:200E:200::/56 *> 2001:218:200E:300::/56 *> 2001:218:200E:400::/56 *> 2001:218:3003:100::/56 *> 2001:218:3003:200::/56 *> 2001:418:141B:200::/56 *> 2001:418:141F:100::/56 *> 2001:418:141F:200::/56 *> 2001:418:1420:200::/56 *> 2001:418:1427:100::/56 *> 2001:418:1427:300::/56 *> 2001:418:142A:100::/56 *> 2001:418:142A:300::/56 *> 2001:418:143A:100::/56 *> 2001:418:143B:100::/56 *> 2001:418:1446:100::/56 *> 2001:418:1446:300::/56 *> 2001:418:1456:200::/56 *> 2001:418:1456:A00::/56 *> 2001:418:3801:100::/56 *> 2001:728:2003:100::/56 *> 2600:C0B:2:100::/56 *> 2600:C0B:3010::/56 *> 2600:C0B:3010:200::/56 *> 2607:F360:100:100::/56 route-views>show bgp ipv6 un nei 2001:418:0:1000::F016 routes | i /64 *> 2001:418:1401:1::/64 *> 2001:418:1401:4::/64 *> 2001:418:1401:7::/64 *> 2001:418:1401:9::/64 *> 2001:418:1401:E::/64 *> 2001:418:1401:F::/64 *> 2001:418:1401:98::/64 *> 2001:418:1C01:1::/64 *> 2001:418:3801:3::/64 *> 2001:728:1808:3::/64 *> 2001:728:1808:4::/64 *> 2001:7F8:F::/64 2001:418:0:1000::F016 *> 2001:DF0:1E:4000::/64 *> 2001:DF5:B400::/64 *> 2400:8B00:1000:2::/64 * 2400:8B00:1100:1::/64 *> 2400:ED00::/64 2001:418:0:1000::F016 *> 2401:2700:1::/64 2001:418:0:1000::F016 *> 2407:0:0:1::/64 2001:418:0:1000::F016 *> 2407:0:0:2::/64 2001:418:0:1000::F016 * 2407:0:0:4::/64 2001:418:0:1000::F016 *> 2407:0:0:A::/64 2001:418:0:1000::F016 *> 2407:0:0:12::/64 2001:418:0:1000::F016 *> 2407:0:1000:4::/64 *> 2407:0:1000:8::/64 *> 2607:3E80::/64 2001:418:0:1000::F016 *> 2607:3E80:0:1::/64 *> 2607:3E80:0:2::/64 *> 2607:3E80:0:3::/64 *> 2607:3E80:0:4::/64 *> 2607:3E80:0:5::/64 *> 2607:3E80:0:6::/64 *> 2620:116:B097::/64 *> 2801:80:E0:1800::/64 *> 2801:80:E0:1801::/64 *> 2804:14C:5FF9:3::/64 *> 2804:14C:5FF9:8::/64 *> 2804:14C:87F9:D::/64 *> 2804:14C:87F9:E::/64 *> 2804:14C:9D10:672::/64 *> 2804:14C:DEFF:1::/64 *> 2804:14C:DEFF:4::/64 *> 2804:14D:10F9:1::/64 *> 2804:14D:16F9:5::/64 *> 2804:14D:2AF9:2::/64 *> 2804:14D:3CF9:4::/64 *> 2804:14D:5CF9::/64 *> 2804:14D:5CF9:1::/64 *> 2804:14D:5CF9:4::/64 *> 2804:14D:5CF9:5::/64 *> 2804:14D:5CF9:6::/64 *> 2804:14D:5CF9:A::/64 *> 2804:14D:5CF9:B::/64 *> 2804:14D:5CF9:C::/64 *> 2804:14D:90F9:5::/64 *> 2804:14D:A210:672::/64 *> 2804:14D:A211:672::/64 *> 2804:138B:B040:A2::/64 *> 2804:138B:C040:A2::/64 *> 2A00:5400:3000::/64 *> 2A02:B60::/64 2001:418:0:1000::F016 *> 2A02:B60:0:F::/64 *> 2A02:B60:2000:3::/64 *> 2001:418:1401:9::/64 2001:418:0:1000::F016 10631 0 2914 20940 20940 i route-views>show ipv6 route 2001:418:1401:9::/64 longer-prefixes IPv6 Routing Table - default - 41191 entries Codes: C - Connected, L - Local, S - Static, U - Per-user Static route B - BGP, R - RIP, H - NHRP, I1 - ISIS L1 I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary, D - EIGRP EX - EIGRP external, ND - ND Default, NDp - ND Prefix, DCE - Destination NDr - Redirect, O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1 OE2 - OSPF ext 2, ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2 la - LISP alt, lr - LISP site-registrations, ld - LISP dyn-eid a - Application B 2001:418:1401:9::/64 [20/10631] via 2001:418:0:1000::F016 best regards
On 4/27/17 06:47, root <junosiosxr@gmail.com> wrote:
Hi,
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. ~Seth
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
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-p... and https://labs.ripe.net/Members/emileaben/has-the-routability-of-longer-than-2... Theodore Baschak - AS395089 - Hextet Systems https://bgp.guru/ - https://hextet.net/ http://mbix.ca/ - http://mbnog.ca/
As an example, the RIPE community has documented that, at the time of writing of this document, IPv4 prefixes longer than /24 and IPv6 prefixes longer than /48 are generally neither announced nor accepted in the Internet [20] [21].
https://tools.ietf.org/html/bcp194 On 4/28/17 3:17 AM, Max Tulyev wrote:
Yes, but that's not a policy, that's a BCP.
On 27.04.17 16: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
participants (6)
-
Job Snijders -
Max Tulyev -
root <junosiosxr＠gmail.com> -
Seth Mattinen -
Theodore Baschak -
Yuya KAWAKAMI