lowering maximum assignment window

Hello Andrei,

I'm not talking about lowering the allocation size. An allocation would 
still be at least a /19. I'm talking about the assignment window- the 
maximum a registry can assign without comming to the RIPE NCC for 
approval.

Please see http://www.ripe.net/docs/ripe-185.html#toc39 for more 
information.

Kind regards,
Paula Caslav
RIPE NCC

 "Andrei V Masalov" <amasalov at na.ptt.ru> writes:
 * -----Original Message-----
 * From: Paula Caslav <paula at ripe.net>
 * To: lir-wg at ripe.net <lir-wg at ripe.net>
 * Date: Wednesday, February 10, 1999 4:50 PM
 * Subject: lowering maximum assignment window
 * 
 * 
 * >
 * >Hi all,
 * >
 * >As we discussed in our audit report at the Local IR working group at
 * >the RIPE 32 meeting, we would like to propose a change in the 
maximum
 * >assignment window that a Registry can have. Currently an assignment
 * >window for a Registry can be anything between a 0 and a /19. The /19
 * >assignment window, is a historical legacy.
 * > ....
 * 
 * >Actually for most Registries, a /24 or /23 assignment window is
 * >enough, since they rarely make larger assignments than that. 
However,
 * >for the Registries that make more large customer assignments, having
 * >up to a /21 assignment window would allow them room to make most of
 * >these larger assignment without coming to us for approval.
 * >
 * >Please think about this proposal and give us any comments by the 
end of
 * >next week.
 * 
 * 
 * What about BGP announces which are less then /19? Many (if not all) 
of
 * the major providers (like C&W, SprintLink) are filtering them out, 
at least
 * for
 * the 195/8 block.
 * 
 * ???
 * 
 * Kind regards,
 * Andrei Masalov
 * PTTNET.
 * 
 *