AW for infrastructure

Dear David & lir-wg,
My appologies for not posting this earlier, but I have been busy changing
jobs.

Here is the status on this action from my slides at RIPE 39:

36.5  Assignment window applied on infrastructure

An LIR may request a separate assignment window for assignments to its own
infrastructure (IIAW Incremental Infrastructure Assignment window).
Such an assignment window should apply to the incremental assignment.
Do we want the IIAW to be reviewed annualy ?
Or should we keep it as it is because LIRs realy can't be trusted in
assigning addresses to themselves and we should always have a second
opinion.
TO be further discussed on lir-wg:
.2-4 week discussion
.Call for consensus
.Forward to RIPE NCC for implementation

So far there have been no concrete proposals on how to do this.

Some background: RIPE 185 3.7 reads:
http://www.ripe.net/ripe/docs/ir-policies-procedures.html#toc39

(...)
To assure the conservation, aggregation, and registration goals are met, we
must be sure the assignment criteria and procedures are properly applied. In
general, this means that Local IRs with little or no experience should
receive maximal support in the assignment process, whereas Local IRs with
more experience should be allowed to make most assignments without
consulting the RIPE NCC. Large assignments always require prior approval
because of their impact on the available address space.
(...)
The assignment window is not only applied to individual assignments, but to
multiple assignments to the same end user in a 12 month period If a Local IR
makes more than one assignment to an organisation in any 12 month period,
the total amount of address space assigned may not exceed the Local IR's
assignment window. This also applies to address space used by the Registry
for their internal network. Additional address space can only be assigned to
that organisation after approval by the RIPE NCC.

Problem:
Since this applies to address space used by the registry for their internal
network, a registry that mainly assignes addresses to its own infrastructure
will never qualify for an assignment window.

Proposed solution:
Change the wording to:
This does not apply to address space used by the registry for their internal
netowork. On the registrys internal network the asssignment window applies
to the individual assignment.

In this way the registry can make assignments to its own infrastructure when
needed. When the registry has convinced the RIPE NCC that the "assignment
criteria and procedures are properly applied. "  The registry will get an
assignment window, and since the assignment window applies to individual
assignment the registry can grow its own network in a timely fashion.

If the RIPE NCC feels that a registry is misusing this mechanism the RIPE
NCC already have the mechanism of an audit in place, and should be able to
uncover improper interpretation of the policy.
Sincerely,

---
Hans Petter Holen, Technical Manager
Tiscali, Norway, +47 24 11 26 44 mobile: +47 99 21 76 70 fax:+47 24 11 24 11