SKNK Field Notes · Point by point
The account, fees, policy contact, and day-to-day administration define the ownership model of a registry relationship.
Reviewed against public documentation: 2 August 2026
Compare point by point
Option one · Direct RIPE NCC membership / LIR relationship
Your organisation manages the direct account and its obligations.
Option two · Sponsoring LIR relationship
The sponsoring LIR manages the relationship under the agreement.
Option one · Direct RIPE NCC membership / LIR relationship
Your organisation prepares and submits the request and account process.
Option two · Sponsoring LIR relationship
The End User provides the information while the sponsor runs the process under the agreement.
Option one · Direct RIPE NCC membership / LIR relationship
BGP, upstream choices, filtering, and day-to-day operations sit with your organisation.
Option two · Sponsoring LIR relationship
The sponsor's service boundary covers the registry relationship; routing operations have their own operational owner.
Option one · Direct RIPE NCC membership / LIR relationship
RIPE NCC's current fee schedule and direct-relationship obligations set the commercial framework.
Option two · Sponsoring LIR relationship
The sponsor's current price, service scope, and agreement set the commercial framework.
Option one · Direct RIPE NCC membership / LIR relationship
The direct account and resource procedures govern changes in the relationship.
Option two · Sponsoring LIR relationship
Each resource has its own lifecycle, portability, and possible renumbering work.
Where this model fits
Direct membership suits organisations that can run the complete registry relationship and its ongoing administration.
Sponsorship suits organisations that need an LIR to administer the relationship within a clearly stated boundary.
Confirmation items before an application or change
The named End User or resource holder
The governing policy and signed agreement
The lifecycle of each resource at service end
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.
Current service terms
Useful for checking
What SKNK publicly states about its service and resource lifecycle.
Needs a separate check
The signed agreement and RIPE NCC policy remain the governing documents.
