In IPv4-land I have the possibility to
reconnect and get a new unrelated ip-address every time.They're issued by the same ISP, to they're related.
Ups. Unrelated in the sense of random ip from their pool, of course.
except of course that in practice if your lease hasn't expired and the
ip reassigned, or even if you manually release it you're very likely to
receive the same one.
manual configuration of ip address name mappings seems like a
rather low priority for the average home user...I don't expect that will be a big activity in the future either,
more devices means less manual intervention not more.Ok, ok, so that argument sucked. I guess I'm still stuck in the IPv4
mindset and have not yet grasped the full blessing of IPv6, zeroconf
etc. etc.
I'm not sure I'd characterize zeroconf, or rendezvous or anything other
technology for device mapping and discovery to be a blessing, that said
the use case for "take shiny new toy out of the box an plug it in is not
that different from the use case of device needs to discard it's old
mapping and use a new one.
Anyway, constantly changing prefixes for home users still seem like
begging for trouble. (Could be a service though, as mentioned, but on
the other hand I expect a fair number of anonymity services to arise
so charging for it might be tough.)
a device might get plugged in and be in the same location for the
entirety of it service life or it might move ever couple hours as a
number of increasing portable devices tend to do, the later set of
devices already cope with a lack of address stability fairly well and
pulling the run out from under them every once in a while supports
renumbering behavior...
I can remember early network printers using bootp and the assuming that
they could use that one ip address forever. today the printer will dhcp
and advertise it's availability in the same broadcast domain and may
well reregister it's name in dynamic dns if possible.
Potentially it's a value add that small ISPs can use to distinguish
their basic packet transport services from their larger competitors.
I can remember early network printers using bootp and the assuming that
they could use that one ip address forever. today the printer will dhcp
and advertise it's availability in the same broadcast domain and may
well reregister it's name in dynamic dns if possible.
Funny... I remember printers only thinking that if they were going to get
moved, they'd also likely get unplugged and get a new address after
the move.
Owen
I can remember early network printers using bootp and the assuming that
they could use that one ip address forever. today the printer will dhcp
and advertise it's availability in the same broadcast domain and may
well reregister it's name in dynamic dns if possible.Funny... I remember printers only thinking that if they were going to get
moved, they'd also likely get unplugged and get a new address after
the move.
rfc 951 made no provision in the protocol for the recovery of an
address. you may well get a new one but the old one is assigned forever
until someone prunes the cruft
This is surprising to me, can you comment on why DHCPv6 TA is being
used in this scenario?