Edward Ned Harvey wrote: > > > 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.
Actually there is a third option that is already in use, a protocol and a service dedicated just for this. There are already two common ones in place today, SIP and XMPP. The idea is that the clients, which can be anywhere on the net, know to talk to their respective servers, which have known addresses on the net, (think MX record for a mail server, except that it is an SRV record), then the communication goes client to server to server to client, so our clients are talking to each other (though the servers). Now that they are talking, the client can exchange their ip addresses, as well as which protocol (typically RTP over UDP) and codecs they want to use, and then finally establish a peer to peer connection. If you use google talk to connect to gmail, and initiate a voice call to me using pidgin, connected to my xmpp server, this is exactly what's going on. Pidgin has an xmpp console feature, and it is neat to see it negotiate the the addresses, protocols and codecs. -- Yves. http://www.SollerS.ca/ gmail, jabber, LiveJournal, nimbuzz, ovi, dreamhost xim.ca: xmpp:y...@zioup.com _______________________________________________ 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/
