Re: Blocks in 193.in-addr.arpa domain document

> 
> 
> Folks,
> 
> Here's the updated document. I was planning on sending this out over the
> weekend, but forgot the modem cable ;-( Anyway, let's see if we can get
> agreement on this. Please note that the database specific things I do not
> want to spend too much on, this should be done at the RIPE meeting.
> 
> A few more days to comment. Want to start delegating blocks end of the week,
> and during next week (although I will be at the IETF).

Sorry, but I think the document is still missing some detail.
Altough implicit I think it should clearly say that delegation can be
done either for each single class-C net or for a 256-block. Unfortunately
no delegation is possible for smaller blocks.

> 8. The registration of the reverse zones for individual class C networks
> will usually be done by the registry administering the class C block
> this network has been assigned from. The registry will make the
> necessary changes to the zone, and update the network objects in the
> RIPE database for these networks, to reflect the correct "rev-srv"
> fields. In case the RIPE NCC receives a request for the reverse zone of
> an individual class C network out of a block that has been delegated,
> the request will be forwarded to the zone contact for this reverse
> block.
OK, but it is not said how the RIPE-NCC should receive (in a network template?)
a request for a network belonging to a block which has not been delegated to
any local registry and what happens then.
Suppose you get:
inetnum: 193.204.64.0 - 193.204.67.0
<administrativia>
rev-srv: <server1>
rev-srv: <server2>
But server1 and server2 only have data for 64.204.193.in-addr.arpa. because
the remaining three nets in the block are not yet active.
What will you do?

> Above procedures are defined to ensure the necessary high availability for
> the 193 reverse domains, and to minimize confusion. The NCC will ensure fast
> repsonse times for addition requests, and will in principle update the
> 193.in-addr.arpa domain at least once per working day.
> 
> The NCC also suggests that similar procedures are set up for the delegation
> of reverse zones from the registries to individual organisations.
I think this sentence should be expanded/clarified: no block delegation is
possible from a local registry to individual organization, only single
networks are under a 256-block.

> 
> Example domain object to request a block delegation
> 
> domain:  202.193.in-addr.arpa
> descr:   Pan European Organisations class C block
> admin-c: Daniel Karrenberg
> tech-c:  Marten Terpstra
> zone-c:  Marten Terpstra
> nserver: ns.eu.net
> nserver: sunic.sunet.se
> nserver: ns.ripe.net
> changed: marten@localhost 930319
> source:  RIPE
> 


----------                                                     ----------
Antonio_Blasco Bonito                          E-Mail: bonito@localhost
GARR - Network Information Service      c=it;a=garr;p=garr;o=nis;s=bonito
c/o CNUCE - Istituto del CNR                         Tel: +39 (50) 593246
Via S. Maria, 36                                    Telex: 500371 CNUCE I
56126 PISA   Italy                                   Fax: +39 (50) 904052
----------                                                     ----------