Document both ends of the session
Record the facility and cross-connect reference, interface speed, VLAN if used, link addresses, both ASNs and the operational contacts. Confirm who owns each side of the physical handoff and who can troubleshoot outside business hours.
For a InformatiQ handoff, send your ASN, prefixes, selected Amsterdam facility, required port speed and expected commit. We will confirm the available interface and addressing in the service order.
Agree what may be announced and accepted
List the IPv4 and IPv6 prefixes you intend to originate. Check the relevant IRR objects and Route Origin Authorisations before activation; a ROA identifies the origin AS and can set the maximum allowed prefix length. A more-specific route outside that limit becomes RPKI Invalid.
Agree prefix limits, filters, full-table or default-route delivery and any communities you will use. The IETF operational guidance covers session protection and route filtering; the exact policy belongs in the handoff record.
Define a pass or fail test
At turn-up, check physical link state, IPv4 and IPv6 BGP establishment, expected received-route counts, accepted announcements and reachability from independent vantage points. Confirm that an unapproved prefix is not propagated.
If this is a migration, document the rollback contact and the point at which traffic will move. Keep acceptance criteria separate from a promise of a particular latency or route: those depend on destination and current network conditions.