HOST.NET

Customer BGP Policy

Receivable Communities

Customers may influence the Broadband One routing policies by a number of community tags which may be set on routes which they announce. These tags can control the propagation of routes, adjust the localpref assigned to them, and even null route traffic.

Receivable Communities
Community	Action
19151:1	Prepend 19151 to route
19151:2	Prepend 19151 19151 to route
19151:3	Prepend 19151 19151 19151 to route
19151:10	Set local preference to 10 (backup route)
19151:295	Reduce localpref -5
19151:305	Reduce localpref -3
19151:666	Black hole

Local Preferences
Localpref	Description
10	Backup route
100	Default transit route
150	Depreferenced peering route
200	Default peering route
300	Default customer route
400	Default internal route

Announced Communities

All routes announced are tagged with the following information:

Regional and Location

Eastern US 19151:1000

Ashburn ASH 19151:61001

New Jersey NJ 19151:61002

New York NY 19151:61003

Pittsburgh PITT 19151:61005

Columbus COL 19151:61008

South East US 19151:1500

Atlanta ATL 19151:61006

Boca Raton BOC 19151:61010

Miami MIA 19151:61007

Central US 19151:2000

Nashville NSH 19151:62001

Dallas DAL 19151:62002

Madison MAD 19151:62003

Phoenix PHX 19151:62004

Chicago CHI 19151:62006

Indianapolis IND 19151:62008

Western US 19151:3000

Seattle SEA 19151:63001

San Jose SJC 19151:63002

Palo Alto PAO 19151:63003

San Francisco SFO 19151:63004

Los Angeles LAX 19151:63005

Las Vegas VEG 19151:63007

Europe 19151:4000

London LON 19151:64001

Amsterdam AMS 19151:64002

Local Network

Backbone 19151:65010

Customer Routes 19151:65020, 19151:65025

Peering Routes 19151:65040

Transit 19151:65050

IRR Filtering

All customers announcements are filtered against Internet Routing Registry (IRR) databases. BGP speaking customers will be expected to maintain current and correct IRR entries.