AinaCom BGP Peering policy

AinaCom has open policy for peering. There are some basic rules which has to be applied.
If you are interested about peering with AinaCom please contact peering@ainaip.net

Peering related issues

  • Peering can be done by public peering (in public peering points/IXP) or by private peering
  • We demand that every route announced by peer must be in some public RIS database
  • Peering partner must have working abuse, technical and administrative contact email address
  • Partner must respect the rules applied by RIR's (RIPE,ARIN,APNIC,etc.)
  • Peering partner must have Autonomous System (AS) number assigned by some RIR
  • In any cases the peering partner must have to make sure that they aggregate as much as possible

 

Routing and filtering related issues

  • AinaCom don't export IGP routes into EGP or EGP routes into IGP. Same rule applies on peering partner
  • The routing protocol for exchanging the routes is BGPv4
  • The exchange of traffic done by best effort basis if not otherwise agreed.
  • AinaCom use loose uRPF filters for general peers and transit providers. So AinaCom will filter out any traffic if there is no reverse bgp path
  • AinaCom use loose uRPF filters for customer peers
  • AinaCom filters out bogon address space.
  • AinaCom have as-macro object in Ripe database. Name of such object is AS-AINAIP
  • AinaCom does not currently use route flap dampening



BGP communities 

 
        Customers can use these communities to control how their prefices are
        announced to the peers:
 

        1. Communities controlling AS20569 internal use:

 

          Default Local Preference for customer prefix = 130

 

          20569:125 - Set LP to 125

          20569:135 - Set LP to 135

 

        2. Communities controlling egress distribution:

 

          20569:3001 - Prepend 20569 1 time

          20569:3002 - Prepend 20569 2 time

          20569:3003 - Prepend 20569 3 time

          20569:3009 - Don't announce

 

        3. AinaCom send out following communities based on where the prefix is learned:

 

          20569:1000 - Prefix learned from Ficix-peers

          20569:2000 - Prefix learned from other peers

          20569:4000 - Prefix learned from AinaCom customer peer or it's AinaCom internal