About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Policy Proposals
search  
     
RIPE Navigation Ends
green dot Current Policy Proposals
green dot Archived Policy Proposals
green dot Subscribe to the Policy-Announce List
green dot Policy Proposal Template
green dot Policy Development Process Info (PDF)
RIPE NCC Navigation Ends
Next Section

RIPE Policy Proposal 2006-03

Number:
2006-03
Policy Proposal Name:
LIR-PARTITIONED status for IPv6
Author:
spacer
Joao Cabral

Vodafone
Proposal Version:
1.0
Submission Date:
1 June 2006
Current Status :
Withdrawn by proposer who decided that the proposal was no longer necessary.
Suggested WG for Discussion and Publication:
Database
Proposal Type:
New
Policy Term:
Permanent
Policy Document to be Affected:
n/a
Draft RIPE Document :
n/a

Summary of Proposal:

The proposal is to have a new status for IPv6 address space - "LIR-PARTITIONED".


Draft Policy Text:

A Local Internet Registry (LIR) can use LIR-PARTITIONED status field in inet6num objects to represent those blocks managed by different groups/parts/departments within the LIR.

This allows an LIR to document the distribution and delegate the management of allocated space within their own organisation. Address space with a status of LIR-PARTITIONED is not considered used. When the addresses are used, a more specific inet6num object should be registered in accordance with the policies for making assignments.


Rationale:

a. Arguments Supporting the Proposal

The LIR-PARTITIONED mechanism described in ripe-239 (New Values of the "status:" Attribute for INETNUM Objects (LIR-PARTITIONED)) is available as a status field in the RIPE Whois Database for inetnum objects. It allows large LIRs to partition their IPv4 allocated address space and to delegate
authority for managing these blocks to departments within the LIR's organisation. The mechanism is however not currently available in IPv6 for inet6num objects.

Some LIRs feel the need to partition their IPv6 allocation before making assignments for different purposes. These may include various services, customers and/or locations etc. Often, different groups within the same LIR are responsible for managing such segments.

Centralising the entire assignment process in such large organisations is not always practical or effective. There is a need for a means to delegate authority over database assignments in IPv6.

b. Arguments Opposing the Proposal

None identified so far.

 



 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | Copyright Statement
RIPE.NET Homepage LIR Portal RIPE Community