2 Oct
2016
2 Oct
'16
11:35 a.m.
El 01/10/16 a las 17:04, Rob Janssen escribió:
(Please trim inclusions from previous messages)
_______________________________________________
I think it's better to leave the use of the first 64 bits of the IPv6
free to the network admin, so he can distribute the bits between the /48
he gets from his ISP (for example) and the /64 subnets as he sees fit.
Given that we would always have a callsign encoded in the last 64 bits,
I don't see why anyone would want to encode information about the
country in the first 64 bits, especially since you can use compound
callsigns such as PA/EA4GPZ if you're operating abroad.
Perhaps it would be interesting to have the information about the
Maidenhead locator or GPS coordinates of a subnet (where this makes
sense). Someone could use this info to make a geographical map of the
network. However, I think that this info should belong to an external
database (whois maybe) and not be encoded in the IPv6's.
73,
Dani.
Hmm.. Do you have any examples of such ISPs? I’ve
only seen them give
out a /64 to the PPPoE / WAN interface and then also have a routable
/56 or /48 which is almost always available using DHCPv6-PD. The /64
is only used for communication with the ISP (can also be a /126) while
everything else if up to the router to manage.
Although I do get a /48 from my ISP there is nothing I can manage about
the subnetting. The 16 bits between my prefix and my networks are
assigned by my router using DHCPv6-PD and there is nothing I can do to
set these bits. They are assigned to my networks sequentially.
I don't think it is feasible to use those bits with a special meaning.