[members-discuss] GM topic

I hope this email will be read from many of you and WGs members...

few defitions:
INR - Any Internet identifiers such as IP addresses (IPv4, IPv6) and
       Autonomous System Numbers.
LSR - Sumary numbers of all PA and PI LIR INR delegated from RIPE to the
       LIR.

Step 1. we have to agree on this:
RIPE NCC (or every other RIR) can hold operate and be authoritive for 
finite INR - Absolutely maximum values:
16581375   x /24 IPV4 blocks
4294967296 x /32 IPV6 blocks
4294967296 x ASN

>From wich maximum values RIPE is authoritive for are:
XXXXXXX x /24 IPV4 blocks
YYYYYYY x /32 IPV6 blocks
ZZZZZZZ x ASN

Fair share INR to each LIR from the abouve RIPE resources are (each 
resource category / members , recalculated each year):
LLLLLLL x /24 IPV4 blocks
IIIIIII x /32 IPV6 blocks
RRRRRRR x ASN


Step. 2 RIPE NCC should change a little its policies to state that will 
provide and support registry services to each LIR up to the LIR's fair 
share INR. For the INR above fair share INR, RIPE to addopt different 
policy where explicitly to be writen "penalty" actions. In the current 
moment it should be extra fee for each:
1 x /24 IPV4 
1 x /32 IPV6
1 x ASN
But not below than 10% of the current (change every year) free market 
price of each resource type.

For LIRs with LSR below the fair share INR limits, to be create 3 more 
waiting queues (1 for IPV4, 1 for IPV6, one for ASN), with lower priority 
than the new members queues. Via this new queues the LIRs can request 
resources up to their fair share INR limit.
LIRs with LSR on or over fair share INR can not request INR from the 
queues and can aks for resources only from other LIRs (free market).

No need to change RIPE charging scheme - can be flat (equal for each 
member). The calculation of the anual fee _MUST_ be done to cover only 
direct expenses to ensure the normal work of the register. Every 
additional expenses (projects, travels, training courses e.t.c.) to be 
covered from the collected "penalty" fees.

Standart redistribution scheme for over collected money also _MUST_ be 
applied (in case there are such).


----------
Idea about a little push to those who refuse to use IPV6

The portal (https://lirportal.ripe.net) to be accessible over IPV4 
network from 1st to 7th day of each calendar month only. In the other 
time IPV4 access to be restricted and redirected to page where to state - 
the portal access is 24/7 over IPV6, and from 1st to 7th day each month 
over IPV4.

This way I believe network administrators and people who work with the 
portal will start to use at least to one system on IPV6 in their networks. 
Highly likely after that the technicals will stop to be scare from using 
IPV6, and already done part of the work to deploy IPV6 in their networks, 
will start using it more aggressively.


Ivaylo Josifov
VarnaIX / Varteh LTD
+359 52 969393
Varna, Bulgaria