Process and Requirements for Downstream ISP
Last updated on 14/06/2024
The following items are required for a downstream ISP to get connected and announce their resources:
- Internet Resources List: A detailed list of the internet resources that will be announced, such as Autonomous System Numbers (ASN), IPv4, and IPv6 subnets.
- Letter of Authorization (LOA): A formal document that authorizes the downstream ISP to announce the specified internet resources.
- Route Object on WHOIS: A route object registered on the WHOIS database to validate the announcement of the specified resources.
- ROA Object for RPKI Validation: A Route Origin Authorization (ROA) object for Resource Public Key Infrastructure (RPKI) validation of ASN to IP.
- BGP Setup of Customer: The BGP setup details of the customer's router or server IP.
- Routing Table Requirements: Specification of whether a default route is required or a full routing table.
If a provider wants to become an upstream for another ISP, we allow that. However, the requirements still apply and the provider must submit these documents in their name along with the documents like LOA received from their end client.
Here is the process outline for downstream ISP connection:
- Once the service is confirmed, the customer has to mail noc@bharatdatacenter.com the required details. The mail should come from an authorized email address listed on the WHOIS of the internet resource such as ASN or IP.
- If any additional details are required, NOC will contact the customer. Otherwise, if everything is in order, NOC will notify the customer and then begin the process of allowing the announcement and forwarding the same to their upstream provider. This process takes about 24 hours for full announcement.
- Meanwhile, NOC will provide relevant BGP details to establish BGP interconnection with the customer's router or server.