BYOIP means using a customer-owned or lawfully authorised prefix in the operator infrastructure. It can mean origination from the operator ASN, origination from the customer ASN over eBGP or simple routing without a separate customer session.
Choose the model and launch path before payment. Otherwise hardware may already be billing while filters, a LOA or a ROA remain between several organisations.
Choose the announcement model
In one model the operator originates the prefix from its ASN and routes it to the customer. In another, the customer establishes BGP and becomes the origin. Hybrid designs exist, but the origin visible globally must still be defined.
The model determines documents, RPKI, filters, equipment and responsibilities. Put the origin ASN and next hop in the technical schedule.
NextDivide responsibilities→Divide responsibilities
The address holder normally covers lawful use, the LOA and the ROA. The ASN holder covers the intended origin and filter data. The facility operator covers the port, session parameters, its filters and onward propagation to upstreams.
When a reseller is involved, one party still needs to coordinate the case. The customer should not spend weeks locating the queue where the request stopped.
- who creates and changes the ROA;
- who creates the route object and in which IRR;
- who validates the LOA and right to use;
- who configures the session and upstream filters;
- who owns communication when the route is unavailable.
Agree BGP parameters before delivery
Record peer addresses, both ASNs, session type, VLAN, authentication when used, max-prefix and the routes accepted and advertised. Confirm communities, blackhole, default route, BFD and permitted prefix lengths separately.
Not every feature belongs to a basic BGP service. Confirm availability and cost before payment, especially when remote blackhole or route-control communities are operational requirements.
NextVerify actual redundancy→Verify actual redundancy
Two sessions do not prove two independent paths. They may terminate on one switch, router or upstream. Ask whether ports, network devices, circuits and external carriers are diverse.
Define failure behaviour: who changes traffic, which timers apply, whether BFD is used and how the primary path returns. Redundancy is ready only after a controlled test.
NextClarify DDoS treatment for BYOIP→Clarify DDoS treatment for BYOIP
Protection for operator addresses may not automatically apply to a customer prefix. Confirm supported prefix size, detection method, attack capacity, scrubbing method and blackhole rules.
Ask whether origin changes during mitigation, whether the route changes, whether a GRE tunnel is required and which protocols or ports are restricted. “DDoS protection” is too vague without these details.
NextDefine readiness and delivery time→Define readiness and delivery time
BGP is ready when the session is established, agreed prefixes are accepted, the announcement is visible externally, RPKI has the expected state and traffic passes both ways. “Configuration applied” is not an acceptance test.
The quotation should state initial delivery time and the correction time for filters or routing. If BYOIP is essential, server billing can be linked to network readiness, but this must be expressly agreed.
- both sides report Established;
- the prefix passes max-prefix and route filters;
- independent looking glasses see the announcement;
- ROA produces the expected origin-validation result;
- inbound, outbound and backup routes are tested.