SKNK Field Notes · Look at responsibility first

Choose a Network Model by Who Owns What

The choice is broken into facts you can check: who manages the resource, who runs BGP, and what survives — or restarts — when a relationship ends. Three guides, three common decisions.

Start with the decision in front of you

Three responsibilities people mix up — separated for you.

Pick the guide closest to your situation, then compare responsibilities and the questions still worth asking.

Choose the registry relationship

Direct RIPE NCC Membership or a Sponsoring LIR?

The real difference is who owns the registry relationship: the account, the fees, the policy contact, and the day-to-day administration.

Read the decision guide

Choose an address-resource lifecycle

IPv6 PA or PI? Start with Lifecycle, Not Prefix Size

PA (Provider Aggregatable) and PI (Provider Independent) differ in who administers the prefix, who holds the authorisation, and what happens when you change providers. Lifecycle is the real topic; price comes later.

Read the decision guide

Choose who owns routing operations

Run Your Own ASN or Use Provider-Managed Routing?

This is a decision about operational ownership: who controls the routing identity, who configures BGP, who takes incidents, and who carries the dependencies when the network changes.

Read the decision guide

After reading, confirm

Price is one condition; responsibility and lifecycle decide whether a model works over time.

Policy, contract, and upstream conditions come from the relevant parties; this comparison exists to list the questions before you apply or deploy.

Suggested order

  1. 1.Write down the routing capability you actually need.
  2. 2.Then confirm what happens to the resource when the relationship ends.
  3. 3.Finally, confirm contract and filtering conditions with the relevant party.
Return to the learning center