Documentation Needed for PI Requests

Obtaining Provider Independent (PI) resources from RIPE NCC requires submitting comprehensive documentation that demonstrates your eligibility, verifies your legal identity, and justifies your technical requirements. This article provides a complete guide to the documentation you'll need for a successful PI resource request, whether you're applying for IPv4 PI (via transfer) or IPv6 PI (direct assignment).

Understanding and preparing proper documentation before starting your application significantly accelerates the approval process and reduces the likelihood of requests for additional information or rejections.

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

Overview: Document Categories

PI resource requests require three main categories of documentation:

1. Legal verification documents: Prove your organization's legal existence and authority
2. Technical justification: Demonstrate your need for PI resources and how you'll use them
3. RIPE Database objects: Establish your presence in the RIPE registry system

The specific documents needed vary based on:

• Whether you're requesting IPv4 PI (transfer) or IPv6 PI (new assignment)
• Your organization type (company, individual, non-profit, etc.)
• Assignment size (standard /48 or larger)
• Whether you're using a sponsoring LIR or applying directly

Legal Verification Documents

RIPE NCC requires proof of legal identity before assigning resources.

For Organizations

Required documents:

1. Business registration documents
   • Certificate of incorporation
   • Articles of association
   • Company registration extract
   • Trade registry excerpt
   • Any official document proving legal entity status

What RIPE verifies:

• Legal entity name matches application
• Organization legally exists
• Registration is current and valid
• Entity has capacity to enter contracts

Document requirements:

• Must be official documents from government registry
• Should be recent (typically within last 12 months)
• Must show organization name clearly
• Should include registration number or tax ID

Language considerations:

• Documents in English preferred
• Documents in local language acceptable if from EU/RIPE region
• Certified translation may be required for non-EU languages
• Translation costs typically €50-200 if needed

Example acceptable documents:

• UK: Certificate of Incorporation from Companies House
• Germany: Handelsregisterauszug (commercial register extract)
• France: Extrait Kbis
• Netherlands: KvK uittreksel (Chamber of Commerce extract)
• USA: Certificate of Formation or Articles of Incorporation

For Individuals

Individuals can request IPv6 PI resources in some circumstances.

Required documents:

1. Valid identification document:
   • Passport (preferred)
   • National ID card
   • Driver's license (in some cases)
   • Other government-issued photo ID

Verification process: RIPE NCC uses a third-party service called iDenfy to verify individual identities.

How iDenfy verification works:

• Upload digital copy of ID document
• iDenfy performs automated verification
• Checks document authenticity
• May require selfie for biometric matching
• Results provided to RIPE NCC typically within minutes to hours

Privacy considerations:

• ID verification handled by trusted third party
• Personal data protected under GDPR
• Information used only for verification purposes
• RIPE NCC receives confirmation, not full ID details

For Special Entity Types

Non-profit organizations:

• Registration documents from relevant authority
• Non-profit status certification
• Articles of association
• Proof of tax-exempt status (if applicable)

Government entities:

• Official government authorization
• Department or agency charter
• Authorization letter from government authority
• Proof of governmental status

Educational institutions:

• University or school registration
• Educational authority accreditation
• Official institutional documents
• Proof of educational status

Contractual Documents

PI resource holders must establish a contractual relationship with RIPE NCC.

Independent Assignment Agreement

Required document: "Independent Assignment Request and Maintenance Agreement"

This agreement establishes:

• Contractual relationship between end user and RIPE NCC
• Rights and obligations of both parties
• Fee payment terms
• Resource usage conditions
• Policy compliance requirements

Two versions available:

1. Standard agreement: For permanent PI assignments
2. Temporary agreement: For time-limited assignments (research projects, temporary networks)

Signing requirements:

• Authorized signatory from organization
• Legal authority to bind organization
• Matching signatory authorization documentation

Where to obtain:

• Provided by RIPE NCC during application process
• Available through sponsoring LIR
• Accessible via RIPE NCC member portal

Sponsoring LIR Agreement

If using a sponsoring LIR (most common approach):

Required document: Service agreement with sponsoring LIR

What this covers:

• LIR will submit requests on your behalf
• LIR acts as liaison with RIPE NCC
• Fee collection and remittance
• Ongoing administrative support
• Resource management services

Typical terms:

• Setup fee: €200-500
• Annual service fee: €100-300
• RIPE fees passed through: €75 per assignment
• Support and consultation services

Technical Justification Documents

Technical documentation demonstrates your legitimate need for PI resources and how you'll use them.

Network Topology Diagrams

Purpose: Visual representation of your network architecture

What to include:

• Physical and logical network layout
• Site locations (if multiple)
• Router and network equipment placement
• Connections to ISPs
• Internal network segmentation
• Critical infrastructure components

Level of detail:

• High-level overview for standard /48 requests
• Detailed architecture for larger assignments
• Show multi-homing configuration
• Indicate subnet allocation zones

Tools for creating:

• Network diagramming software (Visio, draw.io, Lucidchart)
• Simple diagrams acceptable
• Professional appearance not required
• Clarity and accuracy most important

Example elements:

[Internet]
    |
    +--- ISP 1 --- [Border Router 1]
    |                     |
    +--- ISP 2 --- [Border Router 2]
                          |
                  [Core Network]
                          |
        +-----------------+-----------------+
        |                 |                 |
    [HQ Site]        [Data Center]    [Regional Office]

Infrastructure Description

Purpose: Written explanation of your network and infrastructure

What to document:

Current infrastructure:

• Number of sites/locations
• Network equipment inventory
• Server and service infrastructure
• Employee count and network users
• Current IP addressing (if applicable)

Network architecture:

• Routing protocols in use
• Multi-homing configuration
• Redundancy and failover setup
• Network segmentation strategy
• Security zones and DMZs

Service offerings (if applicable):

• Hosting services
• SaaS platforms
• Public WiFi infrastructure
• Customer connectivity services

Example infrastructure description:

"Our organization operates a multi-site network spanning 3 locations: headquarters in Amsterdam (200 employees), data center in Frankfurt (hosting infrastructure for SaaS platform), and regional office in London (50 employees). We require multi-homing to two ISPs for redundancy and business continuity. The network uses BGP routing with our ASN [number] to announce our address space through both providers. Our data center hosts 150 physical servers and 500 virtual machines supporting our SaaS application serving 200 business customers."

Subnet Allocation Plan

Required for: Larger assignments (beyond standard /48) or multiple assignments

Purpose: Detailed breakdown of how you'll use the address space

Format:

Purpose	Subnet Size	Quantity	Total Addresses
HQ office network	/60	3	3 x 16 /64s
Regional offices	/60	25	25 x 16 /64s
Data center production	/56	2	2 x 256 /64s
Data center management	/64	10	10 /64s
Point-to-point links	/64	50	50 /64s
Reserve for growth	-	-	30% buffer

What to specify:

• Subnet purpose and function
• Size of each subnet or subnet group
• Number of subnets needed
• Justification for quantity
• Growth projections

Growth Projections

Purpose: Demonstrate long-term need and future requirements

Time horizon: Typically 2-5 years

What to document:

Infrastructure expansion:

• New locations planned
• Additional data centers
• Service expansion
• Technology migrations

Business growth:

• Customer growth projections
• New service offerings
• Market expansion
• Strategic initiatives

Technical evolution:

• IPv6 deployment roadmap
• Network architecture changes
• New technologies (IoT, containers, etc.)
• Infrastructure modernization

Presentation format:

• Narrative description acceptable
• Tables or timelines helpful
• Specific milestones and dates
• Realistic, justifiable projections

Multi-homing Documentation

For IPv4 PI (historical) and relevant for IPv6 PI where multi-homing is the use case:

Purpose: Prove intent or capability to connect to multiple ISPs

Required documents:

1. ISP commitment letters or contracts:

   • Letters of intent from 2+ ISPs
   • Existing service agreements
   • Quotes or proposals for connectivity
   • BGP peering arrangements

2. BGP configuration documentation:

   • Your Autonomous System Number (ASN)
   • BGP session plans
   • Route announcement policies
   • Traffic engineering strategy

3. Network topology:

   • Show connections to multiple ISPs
   • Border router configuration
   • Redundancy architecture
   • Failover capabilities

Example ISP letter of intent:

"This letter confirms that [ISP Name] agrees to provide BGP transit services to [Organization Name] for the purpose of announcing IPv6 PI prefix [prefix] via ASN [number]. We will establish BGP peering at [location] with connectivity effective [date]."

Usage Documentation

Purpose: Demonstrate legitimate use of PI resources

What to document:

Intended use:

• How addresses will be utilized
• Services hosted on the network
• Infrastructure supported
• User base served

Compliance with policy:

• Confirm "own infrastructure" use
• No sub-assignment to other organizations
• No unauthorized ISP operations
• Legitimate business purpose

For specific use cases:

SaaS platforms:

• Application architecture
• Customer count and growth
• Service endpoints
• Infrastructure scale

Hosting providers:

• Facility details
• Customer infrastructure (colocation model)
• Your infrastructure vs customer equipment
• Address allocation approach

Multi-site enterprises:

• Site inventory
• Network per site
• Central services
• Inter-site connectivity

RIPE Database Objects

Before or during your PI request, establish presence in the RIPE Database.

Organisation Object

Purpose: Represents your legal entity in the RIPE Database

Required fields:

• Organisation name (legal name)
• Organisation type (typically "OTHER" for end users)
• Address (legal address)
• Contact email
• Abuse contact information

Format example:

organisation: ORG-EA123-RIPE
org-name:     Example Corporation
org-type:     OTHER
address:      Example Street 123
address:      1234 AB Amsterdam
address:      Netherlands
e-mail:       admin@example.com
mnt-ref:      EXAMPLE-MNT
mnt-by:       EXAMPLE-MNT

Who creates: Typically your sponsoring LIR creates this during the application process

Maintainer Object (mntner)

Purpose: Controls access to and modification of your RIPE Database objects

Required fields:

• Maintainer name (unique identifier)
• Description
• Authentication credentials
• Email contacts

Authentication methods:

• MD5 password (most common)
• PGP key
• SSO integration

Security importance: Maintainer credentials control your resources - protect them carefully

Format example:

mntner:      EXAMPLE-MNT
descr:       Example Corporation Maintainer
admin-c:     EC123-RIPE
tech-c:      EC123-RIPE
auth:        MD5-PW $1$abcd1234$...
mnt-by:      EXAMPLE-MNT

Person/Role Objects (NIC Handles)

Purpose: Contact information for administrative and technical roles

Required roles:

• Administrative contact (admin-c)
• Technical contact (tech-c)
• Abuse contact (for organizations)

Required fields per person/role:

• Name
• Address
• Phone number
• Email address
• Associated maintainer

Format example:

person:      John Smith
address:     Example Corporation
address:     Example Street 123
address:     1234 AB Amsterdam
address:     Netherlands
phone:       +31 20 1234567
e-mail:      john.smith@example.com
nic-hdl:     JS12345-RIPE
mnt-by:      EXAMPLE-MNT

Best practices:

• Use role objects for organizational contacts (more flexible)
• Keep contact information current
• Ensure contacts are responsive
• Designate backups for critical roles

Creating Database Objects

Methods:

1. Through sponsoring LIR: LIR creates objects on your behalf (easiest)
2. RIPE NCC web interface: Create via web forms at ripe.net
3. Email submission: Send properly formatted objects to auto-dbm@ripe.net
4. API: Programmatic creation for automated processes

Timing: Create before submitting PI request, or your sponsoring LIR will create during application

Documentation for Different Request Types

Requirements vary based on what you're requesting.

Standard IPv6 PI /48 Request

Minimal documentation:

✓ Legal verification (company registration or ID) ✓ Independent Assignment Agreement (signed) ✓ Basic network description (1-2 paragraphs) ✓ Intended use statement ✓ RIPE Database objects (org, mntner, person/role)

Optional but helpful:

• Network diagram (simple high-level)
• Multi-homing documentation
• Infrastructure overview

Justification level: Minimal - /48 is standard and appropriate

Larger IPv6 PI Assignment Request

Comprehensive documentation required:

✓ Legal verification ✓ Independent Assignment Agreement ✓ Detailed network topology diagrams ✓ Comprehensive infrastructure description ✓ Subnet allocation plan (detailed) ✓ Growth projections (with timelines) ✓ Justification narrative explaining why /48 insufficient ✓ RIPE Database objects

Justification level: High - must clearly demonstrate need exceeding standard /48

Multiple IPv6 PI Assignment Request

Documentation emphasizing separation:

✓ Standard legal and contractual documents ✓ Network topology showing distinct infrastructures ✓ Routing documentation explaining different policies ✓ Organizational or geographic separation justification ✓ Infrastructure descriptions for each requested assignment

Key focus: Explain why multiple separate assignments needed vs. one larger assignment

IPv4 PI Transfer Documentation

Transfer-specific documents:

✓ All standard PI documentation ✓ Transfer agreement between buyer and seller ✓ Proof of transaction (if required by RIPE NCC) ✓ Receiving party justification for IPv4 need ✓ Compliance confirmation for "own infrastructure" use ✓ Multi-homing intent or capability

Additional considerations: Transfer seller must also provide documentation of valid assignment

Document Preparation Best Practices

Accuracy and Consistency

Critical requirements:

• Organization name identical across all documents
• Addresses consistent
• Contact information accurate
• No discrepancies between documents

Common mistakes to avoid:

• Legal name on registration different from application
• Outdated company information
• Inconsistent address formats
• Mismatched contact details

Completeness

Before submission checklist:

□ All required documents included □ Signatures on contractual documents □ Legal verification documents recent and valid □ Technical justification addresses all requirements □ Network diagrams clear and labeled □ RIPE Database objects created or arranged

Incomplete applications result in:

• Requests for additional information
• Processing delays
• Potential rejection
• Restart of evaluation process

Clarity and Professionalism

Document quality:

• Clear, readable scans of legal documents
• Professional network diagrams (but perfection not required)
• Well-organized written descriptions
• Proper grammar and formatting

Purpose: Help evaluators quickly understand your request and approve without questions

Language Considerations

Preferred language: English

Acceptable alternatives:

• Local languages within EU/RIPE region generally acceptable
• Translation required for documents from outside EU in non-European languages

Technical descriptions: Write in English when possible to expedite review

Working with Your Sponsoring LIR

Most organizations obtain PI resources through a sponsoring LIR who assists with documentation.

Documentation Support Services

What sponsoring LIRs typically provide:

Review and guidance:

• Review your draft documents
• Identify missing information
• Suggest improvements
• Ensure policy compliance

Document preparation:

• Help draft technical justifications
• Create network diagrams
• Prepare subnet allocation plans
• Write usage descriptions

RIPE Database setup:

• Create organisation, mntner, and person objects
• Configure proper object relationships
• Establish authentication credentials
• Test database access

Application assembly:

• Compile all documents
• Format for RIPE NCC submission
• Submit through proper channels
• Track application status

Choosing a Sponsoring LIR

Selection criteria:

Experience: Choose LIRs with proven track record of successful PI applications

Support quality: Evaluate responsiveness, expertise, and guidance quality

Documentation assistance: Assess level of help provided with complex documentation

Fee structure: Compare setup fees, annual costs, and included services

Ongoing relationship: Consider long-term support for resource management

Document Retention and Updates

Keep Records

Maintain copies of:

• All application documents
• Approval correspondence
• Signed agreements
• Technical justifications
• Network diagrams

Why retain documentation:

• Future audits may require original justification
• Transfer processes reference original applications
• Historical record for organization
• Evidence of policy compliance

Duration: Keep indefinitely while holding PI resources

Update When Changes Occur

Trigger updates when:

• Network architecture changes significantly
• Organization legal status changes
• Contact information changes
• Infrastructure expands beyond original justification
• Ownership or control changes

What to update:

• RIPE Database objects
• Notify sponsoring LIR
• Update internal documentation
• Revise network diagrams

Importance: Accurate current documentation simplifies audits and future resource requests

Common Documentation Issues and Solutions

Issue 1: Legal Documents Not in English

Problem: Company registered in non-English speaking country with local language documents

Solutions:

• Documents from EU/RIPE region countries usually acceptable in local language
• For non-EU countries, certified translation may be required
• Budget €50-200 for professional translation if needed
• Some LIRs offer translation services

Issue 2: Individual Requesting as Sole Proprietor

Problem: Not clear whether to apply as individual or company

Solution:

• If legally incorporated business: Use company documentation
• If sole proprietor without legal entity: Apply as individual with ID verification
• If trade name registered: Provide both ID and trade registration
• Consult sponsoring LIR for guidance on specific situation

Issue 3: Insufficient Technical Justification

Problem: RIPE NCC requests additional information on subnet needs

Solution:

• Provide more detailed breakdown of subnet allocation
• Add specific use cases for different subnet groups
• Include infrastructure inventory with address requirements
• Explain growth projections with concrete plans

Issue 4: Multi-homing Documentation Lacking

Problem: Cannot provide ISP commitment letters

Solution:

• Explain planned multi-homing with implementation timeline
• Provide quotes or proposals from ISPs instead of signed contracts
• Document technical capability even if not immediately implementing
• For IPv6 PI, multi-homing intent acceptable without immediate implementation

Issue 5: Network Diagram Too Simple or Too Complex

Problem: Diagram doesn't convey needed information clearly

Solution:

• Create multiple diagrams at different detail levels
• High-level overview showing main components
• Detailed diagrams for specific areas if needed
• Label all components clearly
• Use standard network diagram symbols

Summary: Documentation Checklist

Every PI Request Needs:

✓ Legal verification:

• Company registration (organizations)
• ID verification via iDenfy (individuals)

✓ Contractual documents:

• Independent Assignment Agreement (signed)
• Sponsoring LIR agreement (if applicable)

✓ Technical justification:

• Network description
• Intended use statement
• Infrastructure overview

✓ RIPE Database objects:

• Organisation object
• Maintainer (mntner)
• Person/role contacts

Additional for Larger Assignments:

✓ Detailed network topology diagrams ✓ Comprehensive subnet allocation plan ✓ Growth projections with timelines ✓ Extensive justification narrative

Additional for Transfers:

✓ Transfer agreement ✓ Receiving party justification ✓ Proof of transaction (may be required)

Best Practices:

✓ Start documentation early ✓ Work with experienced sponsoring LIR ✓ Ensure consistency across all documents ✓ Provide complete information upfront ✓ Keep copies of all submissions ✓ Update documentation when circumstances change

Frequently Asked Questions

How recent do legal documents need to be?

Generally within the last 12 months is preferred. Very recent (within 3 months) is ideal. Older documents may be questioned, requiring updated versions.

Can I start the application before having all documents ready?

Your sponsoring LIR can begin the process, but RIPE NCC won't evaluate until all required documents are submitted. It's better to prepare everything first.

What if my organization's legal name is very long or complex?

Use the exact legal name from registration documents. You can use abbreviated or trade names informally, but legal documents must match official registration.

Do I need to provide financial statements or business plans?

Not typically. Technical and infrastructure documentation is primary focus. Financial information rarely required unless specifically requested.

How detailed should network diagrams be?

Sufficient to understand your infrastructure and address space needs. For standard /48, high-level diagrams suffice. Larger requests need more detail showing subnet allocation rationale.

Can my sponsoring LIR prepare all documentation for me?

Many LIRs offer documentation preparation services as part of their fees. You'll need to provide information, but they can format and write technical justifications.

What if I make a mistake in submitted documents?

Contact your sponsoring LIR immediately. Minor errors can usually be corrected. Significant issues may require resubmission or clarification to RIPE NCC.

How long do documents remain valid after submission?

Application documents are valid for the specific request. If circumstances change significantly after approval, you may need to update information, especially for audits.

Next Steps

Ready to prepare your PI request documentation?

Start preparation:

• Gather legal entity documents
• Draft network description
• Create infrastructure inventory
• Develop network diagrams

Find a sponsoring LIR: Partner with Via-Registry for expert documentation assistance:

• Review and preparation services
• Template documents and guidance
• RIPE Database object creation
• Complete application support

Submit your request: With complete documentation, applications process quickly - typically 1-2 weeks for standard requests.

Via-Registry simplifies PI documentation:

• Experienced with hundreds of successful applications
• Comprehensive documentation review
• Technical justification writing assistance
• Fast processing and approval

Learn more about our services:

• IPv6 PI Resources Service
• IPv4 PI Resources Service

Contact Via-Registry to discuss your PI documentation needs.

Related resources:

• Understanding Provider Independent (PI) Resources
• IPv6 PI Allocation Sizes Explained
• RIPE PI Resource Application Process

---

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