If we only cared about the client/server model, IPv4 and NAT would be just
fine, now and for decades to come.  The real value-add of IPv6 is peer to
peer.  But in order for that to be logistically possible, a client needs to
know the IP address of another client, and one thing I know for *dang* sure
is that you don't want to read a 128-bit IPv6 address over the phone to
somebody typing it into their video conference TV at the other end using
their remote control.

 

Initially, without a vast and universal availability of IPv6 from ISP's, you
might be able to (forced to) keep the same IP address from day to day, as
you might be required to obtain your address from some . not sure what the
proper terminology would be . from some relay or service provider.  In which
case, you could have a relatively static DNS entry and that would be pretty
much fine.

 

But if you imagine that you get a different IPv6 address for every network
that you plug into, which is what you have to imagine to be commonplace some
years out from now.  then there are basically two options.  (a) whatever
service you're using (for example skype) has a known address that you
connect to, and then your screen name or username or whatever is able to be
mapped to your IP address.  Or  (b) dynamic dns is able to map your FQDN to
your IP address.

 

I can't assume option (a) because Intel's video conference system isn't
probably going to match Adobe's and Microsoft's and Apple's and Google's and
RedHat's and so on.  So there's got to be some really awesome DDNS solution.
I am familiar with dyndns.com and a few others, but dyndns.com seems to be
unable to support IPv6 right now . so . Anybody know how to solve the "I
need a DNS name wherever I am" problem of IPv6?

 

For that matter . anybody know how to get an IPv6 address, if your ISP
doesn't simply give them out?

_______________________________________________
Discuss mailing list
Discuss@lopsa.org
http://lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
 http://lopsa.org/

Reply via email to