RIPE PI Resource Application Process

Obtaining Provider Independent (PI) resources from RIPE NCC involves a structured application process with multiple steps, specific requirements, and defined timelines. Understanding this process helps you navigate it efficiently, avoid common pitfalls, and obtain your PI resources as quickly as possible. This article provides a comprehensive, step-by-step guide to applying for PI resources through RIPE NCC.

While the process may seem complex at first, working with an experienced sponsoring LIR and preparing documentation thoroughly makes it straightforward. Most standard IPv6 PI applications complete within 1-2 weeks.

For comprehensive background on PI resources, see our guide to Understanding Provider Independent (PI) Resources.

Process Overview

The RIPE PI application process involves seven main steps:

1. Find a sponsoring LIR - Partner with a RIPE NCC member organization
2. Determine requirements - Identify exactly what resources you need
3. Prepare documentation - Gather legal, technical, and contractual documents
4. Create RIPE Database objects - Establish your registry presence
5. Submit application - Sponsoring LIR files request with RIPE NCC
6. RIPE NCC review - Evaluation of policy compliance and documentation
7. Assignment and activation - Receive resources and configure routing

Typical timeline:

• Standard IPv6 PI /48: 1-2 weeks
• Larger IPv6 PI assignments: 2-4 weeks
• IPv4 PI transfers: 3-6 weeks

Let's examine each step in detail.

Step 1: Find a Sponsoring LIR

Most organizations obtain PI resources through a sponsoring LIR rather than directly from RIPE NCC.

What is a Sponsoring LIR?

A sponsoring LIR is a RIPE NCC member organization (Local Internet Registry) that submits PI resource requests on behalf of end-user organizations. They act as intermediary between you and RIPE NCC.

Why use a sponsoring LIR?:

• No need to become full RIPE NCC member (saves significant costs)
• Expert guidance through application process
• Documentation review and assistance
• Ongoing administrative support
• Simpler fee structure
• Access to professional expertise

Sponsoring LIR Responsibilities

Your sponsoring LIR handles:

Application process:

• Documentation review and preparation
• Request submission through RIPE portal
• Communication with RIPE NCC
• Follow-up on questions or clarifications
• Status tracking and updates

RIPE Database management:

• Creating organization and maintainer objects
• Establishing person/role contacts
• Configuring object relationships
• Maintaining accurate registry data

Ongoing services:

• Annual fee collection and remittance to RIPE NCC
• Resource management support
• Database maintenance assistance
• Policy compliance guidance

Selecting a Sponsoring LIR

Key selection criteria:

Experience and track record:

• Number of PI applications processed
• Success rate and approval timeframes
• Years operating as RIPE member
• References from current customers

Service quality:

• Responsiveness and communication
• Technical expertise level
• Documentation assistance provided
• Support availability

Fee structure:

• Setup/application fees: Typically €200-500
• Annual service fees: Typically €100-300
• RIPE NCC fees pass-through: €75 per assignment
• Additional service costs
• Payment terms and methods

Geographic considerations:

• Language support
• Time zone compatibility
• Regional expertise
• Local presence (if important)

Additional services:

• BGP configuration assistance
• ASN application support
• IPv4 transfer facilitation
• Consulting and technical support

Via-Registry as Sponsoring LIR

Via-Registry provides comprehensive sponsoring LIR services:

Application support:

• Complete documentation review
• Technical justification assistance
• Fast application processing
• Direct RIPE NCC liaison

Transparent pricing:

• Clear fee structure
• No hidden costs
• Competitive rates
• Annual billing

Ongoing management:

• Database maintenance
• Fee management
• Compliance support
• Technical consultation

Learn more about our IPv6 PI Resources Service.

Alternative: Direct RIPE NCC Membership

Organizations can become direct RIPE NCC members instead of using a sponsoring LIR.

When to consider direct membership:

• You need LIR status to assign addresses to customers
• You want to manage multiple PI assignments
• You operate as an ISP or hosting provider
• You prefer direct relationship with RIPE NCC

Costs of LIR membership:

• Setup fee: €2,000
• Annual membership: €1,400
• Includes ability to request PA allocations
• Full LIR responsibilities

For most organizations: Sponsoring LIR model is more cost-effective and simpler.

Step 2: Determine Your Requirements

Before starting the application, clearly define what you need.

IPv6 PI Assignment Size

Standard size: /48 (65,536 /64 subnets)

• Appropriate for >95% of organizations
• No special justification required
• Fast approval process

Larger sizes: /44, /40, /36, etc.

• Requires detailed justification
• Document subnet requirements exceeding /48
• Longer approval process
• Additional documentation needed

Multiple assignments: Separate /48s for distinct infrastructure

• Justified by different routing requirements
• Geographic or organizational separation
• Independent routing policies

For detailed guidance, see our article on IPv6 PI Allocation Sizes Explained.

IPv4 PI Space (Transfer Market)

Since RIPE NCC no longer assigns new IPv4 PI space:

Identify needs:

• Exact size required
• Minimum block size (typically /24)
• Budget for purchase
• Timeline requirements

Locate available space:

• Direct contact with holders
• RIR transfer listings
• Via-Registry IPv4 sourcing services

Transfer process: Separate from new assignment process, involves both seller and buyer documentation.

Learn more: IPv4 PI Eligibility Requirements

ASN Requirements

PI resources often pair with an Autonomous System Number:

Why you might need an ASN:

• Multi-homing with BGP routing
• Announcing PI prefixes
• Traffic engineering
• Provider independence

ASN application: Can be submitted simultaneously with PI request or separately.

Additional Considerations

Timeline expectations:

• When do you need the resources operational?
• Lead time for network configuration?
• Coordination with ISP connections?

Budget planning:

• Application fees
• Annual maintenance costs
• Equipment requirements
• Consulting or support needs

Step 3: Prepare Documentation

Comprehensive documentation is critical for smooth application processing.

Required Documents Checklist

Legal verification:

• □ Company registration documents (organizations)
• □ ID verification via iDenfy (individuals)
• □ Recent and valid (within 12 months)
• □ Clear and legible copies

Contractual documents:

• □ Independent Assignment Agreement (signed)
• □ Sponsoring LIR service agreement
• □ Authorized signatures
• □ Proper authorization documentation

Technical justification:

• □ Network topology diagram
• □ Infrastructure description
• □ Subnet allocation plan (for larger assignments)
• □ Intended use statement
• □ Growth projections (if applicable)

Multi-homing documentation (if applicable):

• □ ISP commitment letters or contracts
• □ BGP configuration plans
• □ ASN documentation
• □ Routing architecture

For complete documentation guidance, see our article: Documentation Needed for PI Requests.

Documentation Quality Standards

Accuracy:

• Organization name consistent across all documents
• Addresses match exactly
• Contact information current
• No contradictions between documents

Completeness:

• All required documents included
• No missing signatures
• All fields completed
• Supporting documents attached

Clarity:

• Network diagrams labeled clearly
• Technical descriptions detailed
• Justifications well-articulated
• Professional presentation

Working with Your Sponsoring LIR

Documentation review process:

1. Submit draft documents to sponsoring LIR
2. LIR reviews for completeness and compliance
3. LIR provides feedback and suggests improvements
4. You revise based on feedback
5. LIR confirms readiness for submission

Benefits of LIR review:

• Catch issues before RIPE NCC evaluation
• Ensure policy compliance
• Improve approval likelihood
• Reduce processing delays

Step 4: Create RIPE Database Objects

Before or during application submission, establish your presence in the RIPE Database.

Required Database Objects

Organisation object:

• Represents your legal entity
• Contains organization name, address, contacts
• Type typically "OTHER" for end users

Maintainer (mntner):

• Controls access to your database objects
• Contains authentication credentials
• Critical for security

Person/role objects:

• Administrative contact (admin-c)
• Technical contact (tech-c)
• Abuse contact
• Contains contact details

Object Creation Methods

Through sponsoring LIR (recommended):

• LIR creates objects on your behalf
• Ensures proper configuration
• Establishes correct relationships
• Provides credentials securely

RIPE NCC web interface:

• Create via web forms
• Requires RIPE NCC access
• Guided process
• Immediate feedback

Email submission:

• Send formatted objects to auto-dbm@ripe.net
• Requires proper syntax
• For experienced users
• Automated processing

Object Relationships

Proper relationships between objects ensure smooth management:

[Organisation Object]
        |
        +--- maintained by ---> [Maintainer]
        |
        +--- admin-c ---------> [Person/Role]
        |
        +--- tech-c ----------> [Person/Role]

Critical: Maintainer credentials must be secure and accessible to authorized staff only.

Timing Considerations

Ideal timing: Create objects before application submission

During application: Sponsoring LIR typically creates objects as part of submission process

Post-approval: Objects must exist before assignment can be registered

Step 5: Submit Application

Your sponsoring LIR submits the formal application to RIPE NCC.

Submission Portal

Applications submit through my.ripe.net portal:

Access requirements:

• RIPE NCC account (LIR member)
• Proper authentication
• Correct permissions

Submission path:

1. Log into my.ripe.net
2. Navigate to "Request" section
3. Select "Provider Independent IPv6"
4. Complete application form
5. Upload supporting documents
6. Review and submit

Application Form Components

Organization information:

• Legal entity details
• Contact information
• Organization database object reference

Resource request:

• Assignment size requested
• Justification for size
• Intended use description
• Technical requirements

Supporting documentation:

• Uploaded files attached
• Document types specified
• All required materials included

Contractual acknowledgment:

• Policy compliance confirmation
• Fee acceptance
• Terms and conditions agreement

Submission Checklist

Before clicking submit, verify:

• □ All form fields completed accurately
• □ All required documents uploaded
• □ Organization information matches legal documents
• □ Technical justification clear and complete
• □ Contact information current
• □ Database objects created or arranged
• □ Authorized signatures present
• □ Sponsoring LIR has reviewed

Application Reference Number

Upon submission, RIPE NCC issues:

Ticket number: Unique reference for tracking

Acknowledgment email: Confirmation of receipt

Status portal access: Monitor application progress

Keep this information: For communication and tracking purposes

Step 6: RIPE NCC Review and Evaluation

RIPE NCC evaluates your application against policy requirements.

Evaluation Process

Initial review (1-3 business days):

• Completeness check
• Required documents present
• Basic information verification
• Database object validation

Policy compliance evaluation (2-7 business days):

• Eligibility assessment
• Technical justification review
• Size appropriateness evaluation
• Legal verification confirmation

Additional information requests (if needed):

• RIPE NCC may request clarifications
• Missing documents identification
• Technical questions
• Policy compliance concerns

Final decision:

• Approval and assignment
• Rejection with explanation
• Request for modifications

Evaluation Timeline

Standard IPv6 PI /48:

• Complete documentation: 1-2 weeks
• Minor questions: 2-3 weeks
• Significant issues: 3-4+ weeks

Larger assignments:

• More detailed review required
• 2-4 weeks typical
• Complex cases may take longer

IPv4 PI transfers:

• Both parties evaluated
• 3-6 weeks typical
• Coordination between parties adds time

Common Evaluation Questions

Technical justification:

• "Can you provide more detail on your subnet requirements?"
• "Why is a /48 insufficient for your infrastructure?"
• "Please clarify your multi-homing architecture"

Legal verification:

• "Can you provide more recent company registration?"
• "Please confirm the authorized signatory"
• "Additional proof of legal entity required"

Policy compliance:

• "Please confirm addresses will be used for own infrastructure only"
• "Clarify the relationship between your organization and [mentioned entity]"
• "Explain how this complies with [specific policy provision]"

Responding to RIPE NCC

Best practices:

Timeliness: Respond within 2-3 business days

• Quick responses speed approval
• Delays extend timeline
• Set reminders and calendar alerts

Completeness: Address all questions thoroughly

• Answer every question asked
• Provide requested documentation
• Anticipate follow-up questions

Clarity: Be clear and specific

• Direct answers to direct questions
• Provide specific details
• Avoid vague or ambiguous statements

Professional tone: Maintain professional communication

• Courteous and respectful
• Technical and precise
• Well-organized responses

Working with Your Sponsoring LIR

Your LIR manages RIPE NCC communication:

LIR receives questions: RIPE NCC contacts the LIR

LIR coordinates with you: Forwards questions and requests

LIR submits responses: Compiles and formats your answers

LIR provides guidance: Helps craft appropriate responses

Advantage: Professional intermediary ensures proper communication

Step 7: Assignment and Activation

Upon approval, you receive your PI resources and can begin using them.

Assignment Notification

Approval email from RIPE NCC containing:

• Assigned prefix (e.g., 2001:db8:1234::/48)
• Assignment date
• Ticket closure
• Next steps information

RIPE Database registration:

• inet6num object created
• Your organization object linked
• Maintainer assigned
• Status: ASSIGNED PI

Database Object Configuration

Verify database entries:

• Check inet6num object accuracy
• Confirm organization linkage
• Validate maintainer relationship
• Review contact information

Configure reverse DNS:

• Request domain delegation for IP6.ARPA
• Set up authoritative DNS servers
• Configure reverse zone
• Test resolution

Create route objects:

• Register route6 object for your prefix
• Specify origin AS (your ASN)
• Enable routing validation
• Support RPKI deployment

RPKI Configuration

Resource Public Key Infrastructure validates route origins:

Create ROA (Route Origin Authorization):

1. Access RIPE NCC RPKI interface
2. Create ROA for your prefix
3. Specify authorized origin AS
4. Set maximum prefix length
5. Publish ROA

Why RPKI matters:

• Prevents route hijacking
• Improves routing acceptance
• Industry best practice
• Increasingly required by networks

ISP Coordination

Prepare for routing:

Contact your ISPs:

• Notify of new PI prefix
• Provide prefix and ASN details
• Request BGP session configuration
• Coordinate announcement timing

BGP configuration:

• Configure border routers
• Establish BGP sessions
• Announce prefix to upstream providers
• Implement routing policies

Testing:

• Verify BGP session establishment
• Confirm prefix announcement
• Test routing from multiple locations
• Monitor global routing visibility

Network Configuration

Internal network setup:

Subnet allocation:

• Assign subnets to network segments
• Configure router interfaces
• Update DHCP/SLAAC as needed
• Document subnet assignments

Services configuration:

• Update DNS records
• Configure application endpoints
• Modify firewall rules
• Update monitoring systems

Transition planning (if migrating from PA):

• Dual-stack period
• Gradual service migration
• DNS TTL reduction
• Customer communication

Verification and Monitoring

Confirm proper operation:

Routing visibility:

• Check route propagation globally
• Use looking glasses: bgp.he.net, route-views.org
• Verify reachability from various locations
• Monitor BGP announcement consistency

DNS resolution:

• Test forward DNS
• Test reverse DNS (PTR records)
• Check from multiple resolvers
• Validate delegation

Connectivity testing:

• Test from different networks
• Verify services accessible
• Check latency and performance
• Monitor for issues

Tools for verification:

• RIPE Stat: stat.ripe.net
• Hurricane Electric BGP Toolkit: bgp.he.net
• Looking glasses: Various providers
• ping6 and traceroute6 utilities

Special Processes

Larger Assignment Applications

Process variations for assignments beyond /48:

Additional evaluation time: 2-4 weeks typical vs 1-2 for standard

More detailed review: Extensive scrutiny of justification

Likely follow-up questions: Expect requests for clarification

Documentation depth: Comprehensive technical details required

Approval authority: May require senior evaluation

Multiple Assignment Requests

Requesting separate assignments simultaneously:

Submit together: Bundle requests to show full picture

Explain relationship: Clarify why separate vs. one larger assignment

Independent justification: Each assignment needs own rationale

Routing documentation: Show distinct routing requirements

IPv4 PI Transfer Process

Different process for IPv4 PI acquisitions:

Identify seller: Locate holder willing to transfer

Negotiate terms: Agree on price and conditions

Transfer agreement: Execute legal agreement

Both parties submit: Coordinated application to RIPE NCC

Dual evaluation: RIPE NCC evaluates both parties

Approval and registration: Database updates upon approval

Payment and completion: Financial settlement per agreement

Timeline Expectations

Typical Processing Times

Standard IPv6 PI /48:

• Complete documentation: 1-2 weeks
• Minor clarifications: 2-3 weeks
• Moderate issues: 3-4 weeks

Larger IPv6 PI assignments:

• Straightforward justification: 2-3 weeks
• Complex infrastructure: 3-5 weeks
• Significant questions: 4-6 weeks

IPv4 PI transfers:

• Simple transfer: 3-4 weeks
• Standard process: 4-6 weeks
• Complex situations: 6-8+ weeks

Factors Affecting Timeline

Accelerating factors:

• Complete documentation upfront
• Clear, detailed justification
• Experienced sponsoring LIR
• Responsive to questions
• Straightforward use case

Delaying factors:

• Incomplete documentation
• Insufficient justification
• Slow responses to questions
• Legal document issues
• Policy compliance concerns
• Complex technical requirements

Managing Expectations

Plan ahead:

• Start process well before needed
• Allow buffer time
• Account for potential delays
• Coordinate with network changes

Stay engaged:

• Monitor application status
• Respond promptly to questions
• Maintain communication with LIR
• Be available for clarifications

Common Application Issues and Solutions

Issue 1: Incomplete Documentation

Problem: Application missing required documents

Prevention:

• Use comprehensive checklist
• Review with sponsoring LIR
• Prepare everything before submission

Solution:

• Provide missing documents quickly
• Use expedited delivery if time-sensitive
• Communicate timeline to RIPE NCC

Issue 2: Legal Name Mismatch

Problem: Application name doesn't match company registration

Prevention:

• Use exact legal name from registration
• Verify spelling and format
• Check across all documents

Solution:

• Provide clarification letter
• Submit corrected documentation
• Explain any legitimate variations

Issue 3: Insufficient Technical Justification

Problem: RIPE NCC questions need for larger assignment or multiple assignments

Prevention:

• Provide detailed, specific justification upfront
• Include concrete numbers and plans
• Document clear technical requirements

Solution:

• Expand technical documentation
• Provide infrastructure inventory
• Explain architecture in more detail
• Offer to discuss via call/email

Issue 4: Database Object Issues

Problem: Organisation or maintainer objects have problems

Prevention:

• Create objects carefully
• Use sponsoring LIR expertise
• Verify before application submission

Solution:

• Correct object issues quickly
• Update as directed by RIPE NCC
• Confirm fixes with LIR

Issue 5: Slow Response to Questions

Problem: Delays responding to RIPE NCC inquiries extend timeline

Prevention:

• Designate responsive contact person
• Monitor application status regularly
• Set alerts for communications

Solution:

• Prioritize responses
• Coordinate with LIR for urgent handling
• Provide complete answers to avoid follow-ups

Post-Assignment Responsibilities

After receiving your PI assignment, ongoing obligations begin.

Annual Maintenance

Fee payment:

• €75 per assignment annually (2025 rate)
• Due date reminder from RIPE NCC
• Payment through sponsoring LIR
• LIR typically adds service fee

Compliance maintenance:

• Continue meeting eligibility criteria
• Use resources as documented
• No unauthorized sub-assignment
• Maintain multi-homing capability if applicable

Database Maintenance

Keep current:

• Update contact information promptly
• Revise network details as infrastructure changes
• Maintain accurate organization data
• Respond to RIPE NCC inquiries

Best practices:

• Review database entries semi-annually
• Update when staff changes
• Maintain current email addresses
• Keep emergency contacts accessible

Audit Preparedness

RIPE NCC may audit:

• Resource usage verification
• Policy compliance check
• Documentation review
• Infrastructure assessment

Maintain:

• Original application documents
• Current network diagrams
• Infrastructure inventory
• Usage documentation

If audited:

• Respond promptly and thoroughly
• Provide requested documentation
• Demonstrate legitimate use
• Show policy compliance

Summary: The PI Application Process

7 key steps:

1. Find experienced sponsoring LIR
2. Determine exact requirements (size, type)
3. Prepare complete documentation
4. Create RIPE Database objects
5. Submit application through LIR
6. Respond to RIPE NCC evaluation
7. Activate assignment and configure routing

Success factors:

• Thorough documentation preparation
• Clear technical justification
• Experienced sponsoring LIR partnership
• Prompt response to questions
• Policy compliance understanding

Typical timeline: 1-2 weeks for standard IPv6 PI /48 with complete documentation

Ongoing obligations: Annual fees, database maintenance, policy compliance

Frequently Asked Questions

Can I apply for PI resources directly without a sponsoring LIR?

Technically yes, but you'd need to become a RIPE NCC member (LIR), which costs significantly more (€1,400/year plus €2,000 setup) than using a sponsoring LIR (typically €200-500 total annually). Most organizations use sponsoring LIRs.

How long does a standard IPv6 PI application take?

With complete documentation, typically 1-2 weeks. Incomplete documentation or complex requests take 3-4+ weeks. IPv4 transfers typically require 3-6 weeks.

What happens if RIPE NCC rejects my application?

RIPE NCC provides explanation of rejection reasons. You can address the issues and resubmit, modify your request to meet requirements, or appeal the decision. Your sponsoring LIR can help strategize next steps.

Can I start using the addresses before RIPE NCC approves?

No. Wait for official approval and assignment before configuring or announcing the addresses. Using unassigned addresses violates policy and can cause routing issues.

What if I don't respond to RIPE NCC questions in time?

Your application may be closed due to inactivity. You'd need to restart the process. Always respond promptly - within 2-3 business days is best.

Can I expedite the application process?

RIPE NCC doesn't offer formal expedited processing. However, submitting complete, accurate documentation upfront and responding immediately to questions effectively accelerates approval.

What if my requirements change during the application process?

Notify your sponsoring LIR immediately. Minor changes can often be accommodated. Significant changes may require modified or new application.

Do I need to configure routing immediately after approval?

No required timeline, but most organizations configure within days to weeks. Plan your routing implementation based on your needs, but don't delay unnecessarily.

Next Steps

Ready to begin your PI resource application?

Prepare now:

• Select a sponsoring LIR (consider Via-Registry)
• Gather legal documentation
• Draft technical descriptions
• Create network diagrams
• Determine exact size needed

Partner with Via-Registry:

• Experienced with hundreds of applications
• Fast processing and high approval rates
• Complete documentation support
• Competitive, transparent pricing
• Ongoing management services

Submit your application: With Via-Registry's support, most applications complete within 1-2 weeks.

Learn more about our services:

• IPv6 PI Resources Service
• IPv4 PI Resources Service

Contact Via-Registry to start your PI application today.

Related resources:

• Understanding Provider Independent (PI) Resources
• Documentation Needed for PI Requests
• IPv6 PI Allocation Sizes Explained

---

This article is part of our comprehensive resource library on IP addressing and Internet resources. For personalized guidance on the PI application process, contact our team or explore our service offerings.