RIPE resources: IPv4, IPv6, ASN and sponsorship
Terms and responsibilities
| Component | Purpose | Not automatically included |
|---|---|---|
| IPv4 / IPv6 | IP address space | Operation and reachability |
| ASN | Autonomous system identifier | Router configuration and transit |
| Sponsorship | Contractual resource relationship | Ongoing administration |
| Management | Separately agreed support | Uncommissioned operating tasks |
Separate resources from operations
IPv4 and IPv6 are Internet number resources. An ASN identifies an autonomous system implementing an independent routing policy. Supplying a resource does not operate a network. Router configuration, reachability, routing security, RIPE database maintenance and abuse handling remain separate tasks unless explicitly commissioned.
PA, PI and sponsorship
Address space can be assigned differently depending on product and policy. Provider-aggregatable space is tied to its providing structure. For independent resources, clarify the appropriate contractual relationship with a sponsoring LIR or the RIPE NCC. Eligibility follows current RIPE policy. In NUXOA's offer, the parent company acts as LIR and resource holder.
When an ASN makes sense
An ASN is relevant for organisations operating an independent routing policy and suitable network connections. Clarify upstreams, prefixes, routing expertise, filters, RPKI and reachable contacts. An organisation addressing one service does not automatically need its own ASN.
Maintain registry data
RIPE objects support technical and administrative contacts. Keep responsibilities current and use role addresses with managed handling. Plan who authorises and records changes. Public contact data should avoid unnecessary personal details while operational reports must reliably reach somebody.
Abuse and security
Resource holding, administration and abuse handling are different responsibilities. Before ordering decide who receives, investigates and answers reports promptly. Routing filters and RPKI can reduce erroneous announcements but replace neither host hardening nor incident response. Do not request unplanned routing changes without a tested rollback.
Choose a resource around the actual use case
A business wants to connect its own infrastructure through multiple network partners. It first needs to establish its routing policy, technical ownership and the prefixes those partners will accept. An ASN may form part of that plan, but it does not configure routers or provide suitable address space by itself. An organisation that simply needs a website online would usually start with the hosting and address options offered by its provider.
Resource assignment follows the applicable policies and contractual conditions. Before making an enquiry, record where the infrastructure resides, which network partners are involved and who operates it. Resources, registration, connectivity and ongoing management can then be discussed as separate elements.
Compare charges over the same period
RIPE-related services can combine monthly and annual fees, with setup charges in addition. Compare a consistent period. For the first year, add twelve monthly charges, any annual fees and one-off setup. For later years, consider recurring charges separately. Compare minimum terms and notice periods separately.
Alongside price, record whether an offer covers address space, sponsorship or administrative support. Establish the contracting party, resource holder and operational contact. NUXOA's portal separates resource provision from ongoing administration. The quote needs to list any additional operating tasks and responsibilities that remain with your organisation.
Prepare routing changes with a rollback path
Before a change, give participating network partners consistent information: intended prefixes, origin ASN, timing and contacts. Check existing filters and registry entries for consistency. Where RPKI is used, intended announcements must match the published authorisations. An incorrect relationship can affect reachability; conversely, an authorisation alone does not guarantee that the entire routing path is correct.
Plan verification from several perspectives and define when rollback will occur. The person commissioning the change must remain reachable, and rollback must not depend on a connection that has already been disabled. Document the previous and intended states. If your organisation lacks routing experience, include assisted planning in the enquiry before using a resource in production. That is more useful than discovering an ownership gap during a connectivity problem.
Organise operation after provisioning
A technical contact address is useful only if reports are actually handled. Assign registry maintenance, abuse reports and network-partner coordination to named roles. Clarify cover and access before staff changes occur. For a later contract change or provider move, review notice periods, the resource relationship and any required renumbering early. Keep operating records current so the team can explain the setup without relying on one person's memory.
- Distinguish resources, sponsorship, connectivity and administration in the offer.
- Compare one-off and recurring fees over the same period.
- Agree routing, registry information and contacts before activation.
- Check current policies and product conditions immediately before ordering.
RIPE services from NUXOA
NUXOA offers eight RIPE services for customers with their own external infrastructure. Billing is monthly or annual depending on the service, with setup fees where applicable. Current prices and terms are available in the customer portal. You can request administration and management separately.