Can we either have a problem statement draft or declare this out of scope? IMHO it's a legitimate topic but probably one for later.
Regards Brian On 2012-05-07 22:20, Dan Wing wrote: >> -----Original Message----- >> From: Michael Thomas [mailto:[email protected]] >> Sent: Monday, May 07, 2012 11:51 AM >> To: Dan Wing >> Cc: [email protected] >> Subject: Re: [homenet] I have a problem >> >> On 05/07/2012 11:39 AM, Dan Wing wrote: >>> ... >>>> Well, people already use vpn's on the road and in evil places now, >>>> it's just that they're doing it through a corpro vpn back at the >>>> mothership. >>>> I just want to be able to have the same choice when I'm doing this >> on >>>> my own dime. As it stands, I can't do that for all intents and >>>> purposes. >>> Apple's Back to My Mac, Microsoft's DirectAccess, and the SIP >>> VPN method all rely on one important thing: a rendezvous service. >>> Apple's solution is aimed at consumers and uses Apple's me.com >>> domain. Microsoft's solution is aimed at corporate users and >>> uses IT-operated servers. The SIP VPN method uses SIP proxies. >>> We could imagine someone specifying XMPP for such a thing, too. >>> >>> But the prototypical "Grandma" does not have access to a >>> rendezvous service, unless she participates in the Apple >>> ecosystem (and uses Apple's me.com as the rendezvous service). >>> >>> I don't know how to make one of these systems work without a >>> rendezvous service, and it seems nobody else does, either -- >>> all of them rely on some sort of rendezvous service that is >>> separate from the service provided by the typical residential >>> ISP. >>> >> Ah, but a lot of that thinking seems to be rooted in the v4 >> mindset where home ip addresses are ephemeral, right? In a v6 >> world, why can't I just put a AAAA record in some name server >> just like everything else on the net that wants to be reached >> by name, since the IP subnet I have at home doesn't have to >> change on a regular basis due to the need to recycle v4 >> addresses? >> >> No nat, no dhcp*, no other hacks simplifies this a lot it seems >> to me. >> >> Mike >> >> [*] in the rotating ip address sense, not in the discovery sense. > > If the subscriber's IP address really is static, the subscriber > can avoid DNS entirely, and just put their static IPv6 (or > IPv4) address into their portable computing device (tablet, > PC, whatever) and they're done. That way, the user doesn't > need to know how to edit a zone file or beg their ISP for > a FQDN. > > That leaves the user with the complication of configuring a VPN > on their consumer-grade router and on their portable computing > device (table, PC, whatever). Still pretty hard. > > There are small/medium business routers that support VPN, > and could do this already for IPv4. Many of them probably > lack IPv6 support yet, though. > > -d > > > _______________________________________________ > homenet mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/homenet > _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
