SKNK · Decision notes
Membership, address resources, and day-to-day BGP operations each need their own ownership model. Price is one factor; resource treatment at service end and ongoing operations shape the result as well.
Four decision guides
The four decisions can move independently. Each guide maps the responsibility, resource changes, and service-end conditions for its area.
Account and administration
01
Decision focus
The account, invoices, policy notices, and registry administration need a long-term owner.
The agreement should name the End User or resource holder before commercial terms are compared.
Open the decision guideAddress lifecycle
02
Decision focus
A prefix belongs to a resource relationship. Provider changes reveal the work, authority, and portability attached to it.
Renumbering cost makes the written change and service-end process part of deployment planning.
Open the decision guideRouting operations
03
Decision focus
An ASN and BGP operations are separate commitments. Alerts, filters, and upstream coordination need ongoing ownership.
Self-operated routing needs a team that can carry its operational side over time.
Open the decision guideIPv4 lifecycle
04
Decision focus
Lease and transfer paths carry different cost timing, authority, and service-end work.
Put the prefix, Origin ASN, route/ROA/LOA scope, abuse path, and lifecycle actions into the written Order.
Open the decision guideFive checks before signing or deploying
01
The End User, resource holder, account holder, and agreement define responsibility when the relationship changes.
02
ASN, prefix, ROA and IRR access each have their own portability and renumbering work.
03
ROAs, route objects, and BGP configuration each need an identified change authority before an incident occurs.
04
Recurring fees, paperwork, renewals, and operator time sit alongside one-off setup work.
05
The support boundary defines incident ownership. A registry relationship and a managed routing service carry different commitments.
The next step for an existing object
For an ASN, prefix, or route result already in hand, the methodology page explains its source, time, and scope.
