Routing Policies
BGP customer communities

Customers wanting to alter local preference on their routes.

NTT Communications BGP customers may choose to affect our local preference on their routes by marking their routes with the following communities:

Community Local-pref Description
(default) 120 customer
2914:450 96 customer fallback
2914:460 98 peer backup
2914:470 100 peer
2914:480 110 customer backup
2914:490 120 customer default
2914:666   blackhole

Customers wanting to alter their route announcements to other customers.

NTT Communications BGP customers may choose to prepend to all other NTT Communications BGP customers with the following communities:

Community Description
2914:411 prepends o/b to customer 1x
2914:412 prepends o/b to customer 2x
2914:413 prepends o/b to customer 3x

Customers wanting to alter their route announcements to peers.

NTT Communications BGP customers may choose to prepend to all NTT Communications peers with the following communities:

Community Description
2914:421 prepends o/b to peer 1x
2914:422 prepends o/b to peer 2x
2914:423 prepends o/b to peer 3x
2914:429 do not advertise to any peer
2914:439 do not advertise to any peer outside region

Note: 2914 is the ASN prepend in all cases. If used, 654xx:nnn overrides 655xx:nnn and 2914:429, 655xx:nnn overrides the 2914:42x communities.


Customers wanting to alter their route announcements to selected peers.

NTT Communications BGP customers may choose to prepend to selected peers with the following communities, where nnn is the peer's ASN:

Community Description
65400:nnndo not advertise to peer nnn in North America
65401:nnnprepends o/b to peer nnn 1x in North America
65402:nnnprepends o/b to peer nnn 2x in North America
65403:nnnprepends o/b to peer nnn 3x in North America
65410:nnnannounce to peer nnn in North America, disregards 2914:429 and 65500:nnn
65420:nnndo not advertise to peer nnn in Europe
65421:nnnprepends o/b to peer nnn 1x in Europe
65422:nnnprepends o/b to peer nnn 2x in Europe
65423:nnnprepends o/b to peer nnn 3x in Europe
65430:nnnannounce to peer nnn in Europe, disregards 2914:429 and 65500:nnn
65440:nnndo not advertise to peer nnn in Asia
65441:nnnprepends o/b to peer nnn 1x in Asia
65442:nnnprepends o/b to peer nnn 2x in Asia
65443:nnnprepends o/b to peer nnn 3x in Asia
65450:nnnannounce to peer nnn in Asia, disregards 2914:429 and 65500:nnn
65460:nnndo not advertise to peer nnn in South America
65461:nnnprepends o/b to peer nnn 1x in South America
65462:nnnprepends o/b to peer nnn 2x in South America
65463:nnnprepends o/b to peer nnn 3x in South America
65470:nnnannounce to peer nnn in South America, disregards 2914:429 and 65500:nnn
65500:nnndo not announce to peer nnn
65501:nnnprepend o/b to peer nnn 1x
65502:nnnprepend o/b to peer nnn 2x
65503:nnnprepend o/b to peer nnn 3x
65510:nnnannounce to peer nnn, disregards 2914:429

Note: 2914 is the ASN prepend in all cases. If used, 654xx:nnn overrides 655xx:nnn and 2914:429, 655xx:nnn overrides the 2914:42x communities.


For further granularity, here are additional bgp communities customers can use to alter their route announcements to other NTT Communications BGP customers or peers, as indicated in the descriptions:

Community Description
2914:4011prepend o/b to all customers 1x in North America
2914:4012prepend o/b to all customers 2x in North America
2914:4013prepend o/b to all customers 3x in North America
2914:4019do not advertise to any customer in North America
2914:4021prepend o/b to all peers 1x in North America
2914:4022prepend o/b to all peers 2x in North America
2914:4023prepend o/b to all peers 3x in North America
2914:4029do not advertise to any peer in North America
2914:4211prepend o/b to all customers 1x in Europe
2914:4212prepend o/b to all customers 2x in Europe
2914:4213prepend o/b to all customers 3x in Europe
2914:4219do not advertise to any customer in Europe
2914:4221prepend o/b to all peers 1x in Europe
2914:4222prepend o/b to all peers 2x in Europe
2914:4223prepend o/b to all peers 3x in Europe
2914:4229do not advertise to any peer in Europe
2914:4411prepend o/b to all customers 1x in Asia
2914:4412prepend o/b to all customers 2x in Asia
2914:4413prepend o/b to all customers 3x in Asia
2914:4419do not advertise to any customer in Asia
2914:4421prepend o/b to all peers 1x in Asia
2914:4422prepend o/b to all peers 2x in Asia
2914:4423prepend o/b to all peers 3x in Asia
2914:4429do not advertise to any peer in Asia
2914:4611prepend o/b to all customers 1x in South America
2914:4612prepend o/b to all customers 2x in South America
2914:4613prepend o/b to all customers 3x in South America
2914:4619do not advertise to any customer in South America
2914:4621prepend o/b to all peers 1x in South America
2914:4622prepend o/b to all peers 2x in South America
2914:4623prepend o/b to all peers 3x in South America
2914:4629do not advertise to any peer in South America

Communities marked on routes sent to customers

Community Description
2914:410 NTT Communications and customer routes
2914:420 Peer routes
 
US MSA origins (2914:10--)
2914:1001 Ashburn, VA
2914:1001 Sterling, VA
2914:1002 Atlanta, GA
2914:1003 Chicago, IL
2914:1004 Dallas, TX
2914:1004 Houston, TX
2914:1005 Los Angeles, CA
2914:1006 Miami, FL
2914:1007 Seattle, WA
2914:1008 Milpitas, CA
2914:1008 Mountain View, CA
2914:1008 Palo Alto, CA
2914:1008 San Jose, CA
2914:1008 Santa Clara, CA
2914:1009 New York, NY
 
EU MSA origins (2914:12--)
2914:1201 Dusseldorf, Germany
2914:1201 Frankfurt, Germany
2914:1203 London, England
2914:1204 Madrid, Spain
2914:1205 Paris, France
2914:1206 Amsterdam, Netherlands
2914:1207 Warsaw, Poland
2914:1208 Sophia, Bulgaria
2914:1209 Budapest, Hungary
2914:1210 Bucharest, Romania
2914:1212 Milan, Italy
2914:1213 Munich, Germany
2914:1214 Stockholm, Sweden
2914:1215 Vienna, Austria
2914:1216 Barcelona, Spain
 
ASIA MSA origins (2914:14--)
2914:1401 Kuala Lumpur, Malaysia
2914:1402 New Territories, Hong Kong
2914:1403 Osaka, Japan
2914:1404 Seoul, South Korea
2914:1405 Singapore
2914:1406 Sydney, Australia
2914:1407 Taipei, Taiwan
2914:1408 Tokyo, Japan
2914:1409 Tseung Kwan O, Hong Kong
2914:1410 Jakarta, Indonesia
2914:1411 Bandar Seri Begawan, Brunei
 
South American MSA origins (2914:16--)
2914:1601 Sao Paulo, Brazil
 
North American country origins (2914:20--)
2914:2000 us (United States)
 
European country origins (2914:22--)
2914:2201 uk (United Kingdom)
2914:2202 de (Germany)
2914:2203 nl (Netherlands)
2914:2204 fr (France)
2914:2205 es (Spain)
2914:2207 pl (Poland)
2914:2208 bg (Bulgaria)
2914:2209 hu (Hungary)
2914:2210 ro (Romania)
2914:2211 be (Belgium)
2914:2212 it (Italy)
2914:2213 se (Sweden)
2914:2214 at (Austria)
 
Asian country origins (2914:24--)
2914:2401 jp (Japan)
2914:2402 au (Austria)
2914:2403 hk (Hong Kong)
2914:2404 tw (Taiwan)
2914:2405 kr (Korea)
2914:2406 sg (Singapore)
2914:2407 my (Malaysia)
2914:2408 id (Indonesia)
2914:2409 bn (Brunei)
 
South America country origins (2914:26--)
2914:2601 br (Brazil)
 
world region origins (2914:3---)
2914:3000 US
2914:3075 US region customer
2914:3200 Europe
2914:3275 Europe region customer
2914:3400 Asia
2914:3475 Asia region customer
2914:3600 South America
2914:3675 South America region customer
BGP IPv4 peer filter policy
The following is the NTT Communications filtering policy with its peers:

Inbound

  • NTT Communications accepts only those prefixes of length /24 and shorter from traditional class A, B, and C space.
  • NTT Communications uses max-prefix filters at most public exchanges. The max-prefix filter is set to 110% of the greater of the following values:
    • number of prefixes announced in the last 24 hours
    • number of prefixes registered in the routing registries under the peer's as-set if this number is less than 5000.

Outbound

  • NTT Communications will accept any properly registered prefix from our customers but will announce only /24 and shorter prefixes to our peers.
  • All NTT Communications announcements are registered in one of the routing registries and included under as-set AS2914:AS-GLOBAL.
NTT Communications reserves the right to modify this policy without prior notice.
BGP IPv6 peer filter policy
The Internet community filters IPV6 announcements based on the IPV6 allocations from ARIN. The allocations (and filtering) are necessary in order to minimize routing table expansion. Any customer requiring BGP multi-homing, now or in the future, should apply for Provider Independent (PI) IPv6 space directly from ARIN. ARIN can also allocate /48 critical infrastructure space if justified (eg. root domain operators). Customers with multiple connections to the NTT network may announce longer prefixes along with their ARIN allocation to effectively manage their inbound traffic, but longer prefixes than /48 will not be propagated beyond the AS2914 backbone.

More information regarding ARIN's IPv6 assignment and allocation policies can be found here: http://www.arin.net/policy/nrpm.html#six

The following is the NTT Communications filtering policy with its peers:

Inbound

  • NTT Communications will accept /48 and shorter prefixes from our peers.

Outbound

  • NTT Communications will announce /48 and shorter prefixes to our peers.
NTT Communications reserves the right to modify this policy without prior notice.
NTT Communications Global IP Network Routing Registry

The NTT Communications Global IP Network requires all customers using BGP to register each route that will be advertised in either:

  1. the NTT Communications Global IP Network routing registry, or
  2. one of the Internet routing registries mirrored by in the NTT Communications Global IP Network routing registry
All announced routes must be registered as an exact prefix. This is a safeguard to help protect the NTT Communications Global IP Network (and the rest of the Internet) from accidental announcement of prefixes which do not belong to the ASN, accidental announcement of every /32 within an IPv4 prefix, and similar errors which have caused other ISPs to have (multi-day) outages/instability. The current list of mirrored registries is:

  • altdb
  • apnic
  • arin
  • BBOI
  • bell
  • gt
  • jpirr
  • level3
  • radb
  • rgnet
  • ripe
  • savvis
  • TC
NTT Communications Global IP Network customers are welcome to register their routes in the NTT Communications Global IP Network routing registry. Look here for more information on this registry.

Note: Please make sure all of your Route Objects (ROs) are registered under your ASN or AS-SET. In addition, we do not recommend relying on proxy ROs. Just as they are automatically created, they can be automatically deleted.
Route Dampening

The NTT Global IP Network does not use route dampening.

Blackhole Service

Customers may announce hosts tagged with 2914:666 for v4 and v6 peering. Any /32 or /128 host tagged with this community will be discarded as soon as it reaches our network. The /32 or /128 prefix must be one included in the customer's existing ingress BGP filter. By default, peers are not configured for the blackhole functionality. Please contact the NTT NOC @ noc@us.ntt.net for this feature.