-----BEGIN PGP SIGNED MESSAGE-----


>>>>> "der" == der Mouse <mouse@Rodents.Montreal.QC.CA> writes:
    >>> I've actually got a /56 (assigned out of a friendly site's /48), of
    >>> which I'm using a /96, with the other 40 bits presently all 0.
    >> it is up to you, but i highly recommend you to use /64 for subnets, as
    >> all specs recommend.

    der> What's the point of expanding the address space to 128 bits if
    der> you're just going to throw half of them away?

  Well, it is still possible that the upper 64 will be routing info only and
the lower 64 will be an end-point identifier. e.g. TCP/UDP will compare only
the lower 64. This comes up again and again and there are good reasons each
way. 

    >> stateless autoconfiguration is possible only with /64,

    der> What is that, and why would I want it?

  dhcp.

    >> and fixed /64 boundary for subnet eases many of management hurdles.

    der> Such as?  I have trouble thinking of anything that outweighs having
    der> a human-comprehensible correspondence between a machine's v6 address
    der> and its v4 address.

  Do that then for servers.
  I do precisely that, PREFIX::X where X is the same as the IPv4 last octet.

]       ON HUMILITY: to err is human. To moo, bovine.           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another NetBSD/notebook using, kernel hacking, security guy");  [


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1
Comment: Finger me for keys

iQCVAwUBPNVxpYqHRg3pndX9AQEP9wQAwP7mt8WyEg+GDSi9Pd9cTmGpo+OdKXlJ
PZsxQyTomu7mcZeIvQZLJbfQ34e+fMUZPNBIzfYmfKEJ5ZOn0TjExzjD4XVg0QMV
jROsFfQEhdsalqcmxZIVM1FNdqvuf1c/mSOX7DRPuVGUekWr640ZdqEF73BfCHWY
lvJ9MYpRImY=
=Chr0
-----END PGP SIGNATURE-----