Issang Victor Singjalarjastang
2015-03-25 17:08:22 UTC
Is ipv6 capable of bouncing packets forward in some way maybe similar to
dynamic DNS. I think I read about renumbering and mobile user use-case
of ipv6 deployment scenario some when in the past. I am trying to think
if it would be possible to make client software point to a certain ipv6
address (or DNSname) but which would then on the ipv6 protocol layer
notify the connecting node of the new actual address that the supposed
service would be to be reached at?
Maybe similar to those http redirect result codes 302 or something
object address moved temporarily or permanently and such redirects.
Does ipv6 have such a feature or can this be achieved in some ways in
some intelligent way?
I am wondering if ipv6 designing folks ever thought of the near endless
ipv6 addresses and them maybe constantly changing and those privacy
protection stuff coming into the equation too.
So if my client software would like to connect to a
hostname:portcombination, but my ISP would give me constantly or
regularly new ipv6 addresses and delegate dynamic networks, then maybe I
could have one static ipv6 address, which then would inform the
connecting ipv6 node of the new actual ipv6 currently destined in use
for that original ipv6, so forwarding or bouncing forward the request,
and the client software then asking that new ipv6 address again instead
and find the desired service.
Was ipv6 ever designed with this or similar scenario in mind? Or what is
that mobile ipv6 use I somewhere some when heard about?
Thanks for bearing with me.
Issang.
dynamic DNS. I think I read about renumbering and mobile user use-case
of ipv6 deployment scenario some when in the past. I am trying to think
if it would be possible to make client software point to a certain ipv6
address (or DNSname) but which would then on the ipv6 protocol layer
notify the connecting node of the new actual address that the supposed
service would be to be reached at?
Maybe similar to those http redirect result codes 302 or something
object address moved temporarily or permanently and such redirects.
Does ipv6 have such a feature or can this be achieved in some ways in
some intelligent way?
I am wondering if ipv6 designing folks ever thought of the near endless
ipv6 addresses and them maybe constantly changing and those privacy
protection stuff coming into the equation too.
So if my client software would like to connect to a
hostname:portcombination, but my ISP would give me constantly or
regularly new ipv6 addresses and delegate dynamic networks, then maybe I
could have one static ipv6 address, which then would inform the
connecting ipv6 node of the new actual ipv6 currently destined in use
for that original ipv6, so forwarding or bouncing forward the request,
and the client software then asking that new ipv6 address again instead
and find the desired service.
Was ipv6 ever designed with this or similar scenario in mind? Or what is
that mobile ipv6 use I somewhere some when heard about?
Thanks for bearing with me.
Issang.