RIPE Maintainer Services for RIPE Database Management
RIPE Maintainer services for RIPE Database management, including mntner configuration, authorized object updates and support for IPv4, ASN, route and domain objects. Where applicable, Hyper ICT can configure customer-managed Maintainer access for relevant RIPE Database objects.
Keep Your RIPE Database Objects Under the Right Control
We can help review your RIPE Database setup, configure the appropriate Maintainer structure and assist with permitted object changes. Where applicable, a customer-managed Maintainer can be configured so you can manage relevant RIPE Database objects directly.
- mntner configuration
- inetnum and route objects
- aut-num related support
- domain object support
- Authorized database updates
What Is a RIPE Maintainer?
A RIPE Maintainer is represented by a mntner object in the RIPE Database. It contains authentication information used to authorize operations on database objects protected by that Maintainer.
Control RIPE Database Changes
RIPE Database objects reference Maintainers through authorization attributes. These references determine which authorized credentials can be used for operations involving protected objects.
- Protect RIPE Database objects
- Authorize permitted changes
- Control object management access
- Maintain accurate network records
Common Maintainer Attributes
RIPE Database objects can reference Maintainers through several attributes depending on the type of object and the authorization being controlled.
-
mnt-by- protects the object itself -
mnt-routes- routing object authorization -
mnt-lower- hierarchical object authorization -
mnt-domains- domain object authorization
RIPE Objects a Maintainer Can Protect
Maintainer authorization is used across different RIPE Database object types. Which objects you can manage depends on the resources, authorization structure and Maintainer references involved.
inetnum
IPv4 address-space records containing registration and operational information about IPv4 resources.
aut-num
Autonomous System objects containing information associated with an ASN and its routing policy.
route
IPv4 routing registry objects that associate an IPv4 prefix with an origin ASN.
domain
Domain objects used for reverse DNS delegation, including authoritative nameserver information for applicable reverse zones.
role & person
Contact objects referenced by other RIPE Database records for administrative and technical responsibilities.
Other RIPE Objects
Maintainers can also protect other supported RIPE Database objects depending on the object's structure and applicable authorization rules.
RIPE Maintainer & Database Support
Whether you are working with leased IPv4 resources or an existing RIPE Database setup, we can help identify the relevant objects, Maintainer references and authorized changes required.
Maintainer Setup
Assistance with reviewing or configuring the Maintainer structure required for relevant RIPE Database objects, including customer-managed Maintainer access where applicable.
RIPE Object Updates
Technical support for authorized updates to RIPE Database objects when operational, resource or contact information needs to change.
Route Object Assistance
Help reviewing IPv4 route object requirements, Maintainer references and the hierarchical authorization required for route object creation or updates.
IPv4 Resource Records
Assistance with RIPE Database records associated with eligible IPv4 resources and the Maintainers protecting those records.
ASN-Related Objects
Support with relevant aut-num records, Maintainer references and RIPE Database requirements associated with Autonomous Systems.
Domain Object & rDNS
Assistance with RIPE domain objects and reverse DNS delegation for eligible IPv4 resources, including authoritative nameserver configuration where applicable.
Customer-Managed RIPE Maintainer Access
Where applicable, eligible Hyper ICT customers can have a customer-managed RIPE Maintainer configured for relevant RIPE Database objects associated with their deployment.
Manage Relevant Objects
Customer-managed Maintainer access can allow your network team to make authorized changes to the RIPE Database objects that reference your Maintainer.
- Direct authorized object management
- Customer-controlled Maintainer credentials
- Faster operational updates
- Clear responsibility for relevant records
Subject to Resource Authorization
Having a Maintainer does not automatically provide control over every RIPE Database object. The object must reference the appropriate Maintainer, and all applicable RIPE Database authorization requirements must still be satisfied.
- Access depends on the specific resource
- Only relevant objects are included
- Hierarchical authorization may still apply
- RIPE Database rules remain applicable
When Do You Need RIPE Maintainer Support?
Maintainer assistance becomes especially useful when IPv4 resources, routing information, reverse DNS or existing RIPE Database objects need to be reviewed or changed.
You Use IPv4 Resources
RIPE-managed IPv4 resources can have database objects that need to remain accurate and protected by the appropriate Maintainer structure.
- inetnum information
- Maintainer references
- Authorized object updates
You Operate Your Own ASN
Autonomous System operators may need assistance with aut-num records, Maintainer references and related routing database information.
- aut-num record review
- Maintainer references
- Routing information
You Need Route or Domain Object Changes
Route object creation and reverse DNS delegation can involve specific Maintainer and hierarchical authorization requirements. We can review the applicable objects and required next steps.
- route object review
- domain object review
- Authorization requirements
How RIPE Maintainer Support Works
Send us the resource or RIPE Database object you are working with and we will help determine the relevant object, Maintainer and authorization requirements.
Send Your Details
Send us the ASN, IPv4 prefix, RIPE Database object or a short description of the change you need.
Review the Objects
We review the relevant RIPE Database objects, Maintainer references and authorization structure.
Confirm Requirements
We identify the required object changes, applicable authorization and any additional information needed.
Complete the Authorized Update
The authorized change is completed or the required technical steps are coordinated with the appropriate parties.
Services Related to RIPE Database Management
RIPE Database management is often connected with IPv4, ASN, routing, RPKI and reverse DNS operations.
BGP Assistance
Technical assistance for IPv4 prefix announcements and routing requirements.
Reverse DNS
PTR records, reverse delegation and RIPE domain object support for eligible IPv4 resources.
Letter of Authorization
Authorization documentation for eligible IPv4 and BGP deployments.
RIPE Maintainer Frequently Asked Questions
Common questions about RIPE Maintainers, mntner objects, authorization and RIPE Database management.
What is a RIPE Maintainer?
A RIPE Maintainer is represented by a mntner object in the RIPE Database. The mntner contains authentication information used to authorize operations on database objects protected by that Maintainer.
What does mnt-by mean in the RIPE Database?
The mnt-by attribute references one or more Maintainer objects protecting a RIPE Database object. Modification or deletion of the protected object requires authorization from an applicable referenced Maintainer.
What are mnt-routes and mnt-lower?
These attributes are used for hierarchical authorization. For route object creation, RIPE Database authorization can use mnt-routes first, followed by mnt-lower and then mnt-by according to the applicable parent object configuration.
Can I manage RIPE Database objects with my own Maintainer?
Where applicable, eligible Hyper ICT customers can have a customer-managed RIPE Maintainer configured so they can manage relevant RIPE Database objects using their own authorized Maintainer access. The exact objects and permitted changes depend on the resource and applicable RIPE Database authorization requirements.
Does having a Maintainer give me access to every RIPE object?
No. A Maintainer only provides authorization where the relevant RIPE Database object or authorization hierarchy references that Maintainer. Other authorization rules may also apply depending on the operation and object type.
Can you help create or update route objects?
Yes. We can review route object requirements for eligible IPv4 resources and help coordinate the required Maintainer and hierarchical authorization. The exact requirements depend on the relevant prefix and existing RIPE Database objects.
Can RIPE Maintainer access be used for reverse DNS?
Maintainer authorization can be relevant to RIPE domain objects used for reverse DNS delegation. Depending on the resource and authorization structure, the appropriate Maintainer can be used when creating or updating the relevant domain object.
Can RIPE Maintainer support be used with an ASN?
Yes. If you operate an ASN in the RIPE Database, we can help review relevant aut-num information, Maintainer references and related database requirements.
What information should I send you?
Start with the relevant ASN, IPv4 prefix or RIPE Database object and a short explanation of what you need to create, change or review. We can then identify any additional information or authorization that may be required.
Need Help With a RIPE Maintainer or Database Object?
Send us your IPv4 prefix, ASN or RIPE Database requirement. Our network team can review the relevant object, Maintainer and authorization requirements.