On Tue, 2004-07-20 at 16:54, [EMAIL PROTECTED] wrote:
> Hello all, I have been "playing" with ipv6 for a while now (mostly on 
> Linux and osX) and I have started to turn my thoughts to networking and 
> servers.
> The easy one I guess is servers. Presumably a static ipaddress is best to 
> use because of DNS etc. If a static address is allocated, radvd will not 
> be required because there is no ipv4 DHCP type requirement. Is this a 
> correct assumption?

Correct, but then you can't renumber easily. The 'best' would be the
number your _services_ eg:

2001:db8:2000::80  = webserver (port 80 tcp ;)
2001:db8:2000::110 = pop3server (port 110 tcp)
etc...

but still having the host main IP be assigned by radvd.
The service IP then never changes (1,2,3) but you can swap around the
real host.

Also see: http://www.ams-ix.net/more/aiad/xs4all.pdf

> Second, networks. On an ipv4 based ip network, it is usual on wan links 
> (unless they are unnumbered serial lines) to use a .252 or /30 mask with 4 
> addresses in the subnet (net, ip1, ip2, broadcast). Is this wise to 
> implement in ipv6? eg use a /126 mask to allow four valid ipv6 addresses.
> In that case, if I get a /48, I would need to use the first allowed block 
> (/49 mask?) carved up into much smaller chunks, ultimately down to the 
> /126's for wan lines.

Use /64's per tunnel then you can use that same /64 when there are more
hosts (read: more routers) on the same link in the future. There are
also proposals for using IP's as crypto identifiers.

> Given a working ipv4 network where each remote site has a /24 ipv4 
> allocation (and is more than enough given the number of pc's there), would 
> it be sensible to use a /120 for each site or perhaps be profligate(!) and 
> use /118 to allow for all the ipv6 toasters we are likely to be able to 
> buy next year?

Every site gets a /48, if one needs something bigger then let them draw
up an allocation plan.

Or the words (not exactly but almost) from Timothy Lowe from RIPE NCC:
-------
- when you are very very very sure that only 1 'link' will ever be
  connected, then give a /64.
- in every other case delegate a /48.
-------

Why a /48? well so you can move around to other ISP's and always be sure
that you get a /48 so that you don't have to reorganize your network
every time. Next to that there are 'only' 65k /64's in a /48 and every
link gets a /64. At the moment there might not be such a demand, but
think about 10/20 years or even more..

Greets,
 Jeroen

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to