1. 1. AMPATH's AS number is 20080 and supports both IPv4 and IPv6;
   2. AMPATH recommends that all customers use MD5 authentication on their BGP sessions:
       a. If the customer wants to use MD5 authentication, it should supply a password string;
   3. AMPATH reserves the right to disable a BGP peer that is adversely affecting other AMPATH customers or AMPATH's network stability and/or performance until the problem is remedied. A reasonable effort will be made to contact the customer prior to turning down the peer; however, the integrity of the AMPATH network remains the top priority;
   4. AMPATH makes no guarantees, explicit or implicit, about the routing policies of other providers and the routes that they accept into their routing tables;
   5. AMPATH filters BGP announcements from the customer based on network address space;
   6. Every new IPv4/IPv6 prefix to advertise from customers must be inserted in AMPATH's prefix-lists. To request this insertion, customers can:
       a. Request by ticket/email providing the information of new IPv4/IPv6 prefix.
       b. Provide a route-set from any public IRR.
   7. AMPATH uses RADB IRR for manage its and users IPv4/IPv6 prefixes. The following objects are used:
       a. Mnt-by: MAINT-AS20080
       b. Route-set: RS-AS20080-Transit
       c. Route-set per customer: RS-AS20080-AS<ASN#>
   8. Announcements are allowed on the following basis:
       a. AMPATH assigns the IP prefix to the customer;
       b. ARIN or other RIR assigns the IP prefix to the customer;
       c. When another provider assigns the IP prefix, AMPATH will verify the announcements by one of the following:
            i. The information is in RWHOIS or other RIR database.
            ii. The IP prefix already being announced globally from the customer
   9. Every new IP prefix usually takes up to 48 hours to be completely functional on the Internet;
   10. At any moment, customers may decide receive one of the following set of routes:
       a. Full Routing: all prefixes received from all BGP sessions;
       b. Partial Routing: only prefixes from AMPATH's customers and peers;
       c. Default Route: only default route;
       d. Full Routing + Default Route: all prefixes plus the default route;
       e. BGP Communities on Appendix B could be used by customers for more specific selection of routes;
   11. AMPATH does not accept announcements that are more specific than /24 for IPv4 or /48 for IPv6;
   12. AMPATH removes all community strings that are not on the list on Appendix B – AMPATH BGP Communities;
   13. AS Prepending: Customers with public AS numbers may prepend their AS path to control the desirability of their connections. Customers with an assigned private AS number from AMPATH may not pad their AS path. AMPATH will ignore any padding of private AS numbers from customers;
   14. BGP Multi-Exit Discriminator: customers with more than one BGP session could control their incoming traffic based on MED or BGP Communities to change the BGP Local Preference;
   15. AMPATH does not accept any RFC1918 prefix or private address;
   16. AMPATH uses 160 as default BGP Local Preference;
   17. AMPATH makes use of Unicast Reverse Path Forward (uRPF) in Loose mode to validate incoming traffic from users' IP interfaces, using IP prefixes provided by users on item #6;
   18. AMPATH provides a set of community strings to help customers to manage their traffic. These communities are listed on Appendix B – AMPATH BGP Communities;
   19. AMPATH reserves the right to perform inbound and outbound traffic engineering with its upstreams providers, using AS-Path prepending or BGP Communities;
   20. Any question about IP transit, BGP or this document can be sent to bgp@ampath.net.
   

RPKI Validation: