Re: RFC: new network config
jgg@ualberta.ca (Jason Gunthorpe) wrote on 05.02.99 in <[🔎] Pine.LNX.3.96.990205141641.11740B-100000@wakko>:
> Erm, but : is a standard for ports! Like
>
> http://foo.bar:80/
In URIs, yes. (Or would the right TLA be URN here?)
> If someone decides to use :'s for IPv6 address seperation then all sorts
> of nasty stuff breaks.
There was something about using IPv6 addresses in URIs, but I don't
remember the result.
Anyway, IPv6 addresses can have the following forms:
1234:5678:90ab:cdef:0123:4567:89ab:cdef
1111:2222:3333:0000:0000:4444:5555:6666
1111:2222:3333::4444:5555:6666 (same as before)
0000:0000:0000:0000:0000:0000:0000:0001 (IPv6 version of 127.0.0.1)
0:0:0:0:0:0:0:1 (same as before)
::1 (same as before)
0:0:0:0:0:0:0:0 (IPv6 version of 0.0.0.0)
::0 (same as before)
:: (same as before)
1234:5678:abcd:ef00:0000:0000:0000:0000/56 (a network)
1234:5678:abcd:ef00::/56 (same as before) (note last zeroes in word stay)
0000:0000:0000:0000:0000:0000:1.2.3.4 (IPv4-compatible IPv6 addresses)
::1.2.3.4 (same as before)
0000:0000:0000:0000:0000:FFFF:1.2.3.4 (IPv4-mapped IPv6 addresses)
::FFFF:1.2.3.4 (same as before)
Oh, and the lower 64 bits will *usually* be derived from your ethernet
card's MAC address, so it won't be a nice address anyway. IPv6 is
*heavily* into autoconfiguration, automatic renumbering, and so on.
All "normal" worldwide IPv6 addresses are supposed to be between 4000::
(inclusive) and 6000:: (exclusive).
Broadcast, multicast, and stuff, is ffff:<something>.
See RFC 1884 for more details.
MfG Kai
Reply to: