Clarifying Audit and Policy Compliance Frameworks for IPv6 policies
- State:
- Discussion Phase: Open for discussion
- Publication date
- Affects
- Draft document
- Draft
- Author
- Proposal Version
- 1.0 - 19 Oct 2026
- All Versions
-
- Working Group
- Address Policy Working Group
- Mailing List
- Address Policy Working Group
- Proposal type
-
- Modify
- Policy term
- Indefinite
Summary of the Proposal
The goal of this proposal is to make the existing requirements for the IPv6 post-provisioning lifecycle explicitly clear, while also aligning the text with IPv4 policies.
Policy Text
Current policy text (ripe-738):
IPv6 Address Allocation and Assignment Policy
Abstract
This document defines registry policies for the assignment and allocation of globally unique IPv6 addresses to Internet Service Providers (ISPs) and other organisations. It was developed through joint discussions among the APNIC, ARIN and RIPE communities.
[...]
4.1. Address space not to be considered property
It is contrary to the goals of this document and is not in the interests of the Internet community as a whole for address space to be considered freehold property.
The policies in this document are based upon the understanding that globally unique IPv6 unicast address space is licensed for use rather than owned. Specifically, IP addresses will be allocated and assigned on a license basis, with licenses subject to renewal on a periodic basis. The granting of a license is subject to specific conditions applied at the start or renewal of the license.
RIRs will generally renew licenses automatically, provided requesting organisations are making a “good faith” effort at meeting the criteria under which they qualified for or were granted an allocation or assignment. However, in those cases where a requesting organisation is not using the address space as intended, or is showing bad faith in following through on the associated obligation, RIRs reserve the right to not renew the license. Note that when a license is renewed, the new license will be evaluated under and governed by the applicable IPv6 address policies in place at the time of renewal, which may differ from the policy in place at the time of the original allocation or assignment.
[...]
New policy text:
IPv6 Address Allocation and Assignment Policy for the RIPE NCC Service Region
Abstract
This document defines registry policies for the assignment and allocation of globally unique IPv6 addresses to Internet Service Providers (ISPs) and other organisations. It was developed through joint discussions among the APNIC, ARIN and RIPE communities. These policies apply to the RIPE NCC and the Local Internet Registries (LIRs) within the RIPE NCC service region.
[...]
4.1. Address space not to be considered property
It is contrary to the goals of this document and is not in the interests of the Internet community as a whole for address space to be considered freehold property.
The policies in this document are based upon the understanding that globally unique IPv6 unicast address space is licensed for use rather than owned. Specifically, IP addresses will be allocated and assigned on a licence basis, with licences subject to renewal on a periodic basis. The granting of a licence is subject to specific conditions applied at the start or renewal of the licence.
RIRs will generally renew licenses automatically, provided requesting organisations are making a “good faith” effort at meeting the criteria under which they qualified for or were granted an allocation or assignment. However, in those cases where a requesting organisation is not using the address space as intended, or is showing bad faith in following through on the associated obligation, RIRs reserve the right to not renew the license. Note that when a license is renewed, the new license will be evaluated under and governed by the applicable IPv6 address policies in place at the time of renewal, which may differ from the policy in place at the time of the original allocation or assignment.
[...]
9. Audit
The RIPE community asked the RIPE NCC to audit LIR operations and ensure consistent and fair implementation of the community's policies. Details of this activity are described in the RIPE Document "RIPE NCC Audit Activity" found at: http://www.ripe.net/ripe/docs/audit
10. Closing an LIR by the RIPE NCC
The RIPE NCC may close an LIR for any of the following reasons:
- the LIR does not pay money owed to the RIPE NCC
- the LIR cannot be contacted by the RIPE NCC for a significant period of time
- the LIR consistently violates the RIPE community's policies
The RIPE NCC takes on responsibility for address space held by closing LIRs.
[New paragraph numbering]
Rationale:
a. Motivation for the proposal
Over the years, the IPv6 Address Allocation and Assignment Policy has been regularly updated, mostly regarding the provisioning of IPv6. However, sections relating to the post-provisioning lifecycle lack clarity and consistency. Currently, the policy references "audits" but lacks a general reference of the audit procedure itself, unlike the IPv4 policy. Additionally, the section addressing policy compliance and non-compliance remains unchanged since 2002. Its complex wording regarding "licences" and "good faith" efforts can be difficult to understand, especially for those unfamiliar with its historical context.
This proposal aims strictly to clarify the existing framework, without making substantive changes to the original intent of the policy.
b. Arguments supporting the proposal
- Enhances the clarity and readability of the policy text
- Aligns terminology and structure with IPv4 policies
c. Arguments opposing the proposal
- None