SKNK Field Notes · Point by point
Compare IPv4 use rights, ownership, routing authority, cost shape, and lifecycle work before choosing a lease or a transfer path.
Reviewed against public documentation: 2 August 2026
Compare point by point
Option one · IPv4 lease
The contract grants use rights for the active lease term; the recorded holder keeps the resource relationship.
Option two · IPv4 purchase or transfer
The completed transfer records the resource relationship with the buyer under the applicable registry process.
Option one · IPv4 lease
Recurring term pricing supports a lower initial commitment and a renewal decision at each term.
Option two · IPv4 purchase or transfer
A purchase or transfer usually concentrates more cost around the transaction, with separate recurring registry or service costs where applicable.
Option one · IPv4 lease
Route, ROA, and LOA scope follows the actual resource, Origin ASN, and written Order for the case.
Option two · IPv4 purchase or transfer
The buyer or resource holder coordinates registry and routing authority under the transfer record and upstream requirements.
Option one · IPv4 lease
Application review checks candidate availability, IP reputation, intended use, and the requested term.
Option two · IPv4 purchase or transfer
Timing follows seller availability, transfer eligibility, registry review, due diligence, and transaction completion.
Option one · IPv4 lease
The parties follow the Order for renewal, withdrawal, replacement space, and renumbering.
Option two · IPv4 purchase or transfer
The buyer plans ongoing registry, routing, abuse, and address-management work around the acquired resource.
Where this model fits
Leasing fits a time-bounded deployment, a migration project, or a network that values public term pricing and a defined operational scope.
A purchase or transfer fits a long-lived resource plan with the budget, eligibility, and operational capacity for the registry relationship.
Confirmation items before an application or change
How long will the resource be needed?
Who will hold routing and registry authority?
Which renewal, abuse, and exit actions belong in the written plan?
Policies, resource relationships, service boundaries, and upstream filters vary by situation. Formal pages and the responsible party confirm price, eligibility, ownership, and service-end arrangements.
SKNK · Sources and scope
Each source supports one kind of conclusion. Source pages, registry records, and routing observations update at different times, so read every result with its source and timestamp.
Registry and IRR records
Useful for checking
Whether a public object exists for this ASN or prefix, who it is registered to, and who maintains it.
Needs a separate check
Live BGP observations show the current announcement state.
Route-origin authorisation
Useful for checking
Whether the announcer holds an authorisation — prefix, origin ASN, and maximum length matching.
Needs a separate check
Propagation, service availability, and application approval each use separate evidence.
Current commercial scope
Useful for checking
SKNK's public /24 term prices and application-based scope.
Needs a separate check
A transfer or purchase depends on the actual seller, registry, policy, and transaction documents.
