[address-policy-wg] IPv6 micro allocation or something else?

Dear All,
   	I have a question regarding the IPv6 address assignment to
cc level DNS server.

If you don't have answer to this question please forward it to an 
appropriate working group - sorry for cross-posting this mail to two wg.

We have here in Hungary a dilemma:

- Traditionally, the IPv4 address of the primary cc level DNS server in of 
belonged to NIIF/HUNGARNET.

- The DNS registration service a while ago was delegated to Council of 
Hungarian Internet Providers (ISZT) who is also operating the biggest 
Internet Exchange of Hungary (BIX). All big ISPs in Hungary (including 
NIIF/HUNGARNET) has right to do the registration via a special interface.

- The IPv4 address of the primary cc level DNS server announced by 
NIIF/HUNGARNET. But ISZT is reorganizing its infrastructure to allocate 
address from a new PI type IPv4 address space to DNS servers.

- The primary hu DNS server is connected to BIX - to be well connected.


What IPv6 address space should we allocate to hu primary DNS server?

1. Assign IPv6 address from /32 address space of NIIF/HUNGARNET?
- not very optimal since the only transit to hu primary will be NIIF/HUNGARNET
- not ISP neutral 
- easy, no problem from point of view of NIIF/HUNGARNET


2. Assign IPv6 address space from /48 allocated to BIX (based on ripe-256 
and ripe-310)?
- According to the RIPE documents: "Networks assigned under this policy 
may not be globally routable" - which problematical since primary DNS 
servers should be globally reachable.

3. Allocate multiple /48 from IPv6 providers in HUNGARY to primary 
hu DNS server?
- This can be problematical since the answers to DNS queries might be quite
big.

4. Allocate /48 to primary hu DNS server that is globally routable?
Are there similar to /48 from 2001:0500::/30 in RIPE region?

- I think this is the cleanest solution.

Can we discuss this issue on the working group or mailing lists?

I saw a proposal: http://www.ripe.net/ripe/policies/proposals/2005-2.html

In my opinion this can solve the problem....

Best Regards,


Janos Mohacsi
Network Engineer, Research Associate
NIIF/HUNGARNET, HUNGARY
Key 00F9AF98: 8645 1312 D249 471B DBAE  21A2 9F52 0D1F 00F9 AF98