[180483] in North American Network Operators' Group
Re: AWS Elastic IP architecture
daemon@ATHENA.MIT.EDU (Philip Dorr)
Thu Jun 4 14:31:01 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <CAL9jLaYEBZfBJaY59n8=so6SyVRQYUtj5sGgK9TmCYtDMR0u0A@mail.gmail.com>
From: Philip Dorr <tagno25@gmail.com>
Date: Thu, 4 Jun 2015 13:28:39 -0500
To: Christopher Morrow <morrowc.lists@gmail.com>
Reply-To: tagno25@gmail.com
Cc: nanog list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Thu, Jun 4, 2015 at 12:16 PM, Christopher Morrow
<morrowc.lists@gmail.com> wrote:
> On Thu, Jun 4, 2015 at 5:11 AM, Owen DeLong <owen@delong.com> wrote:
>> I=E2=80=99d argue that SSH is several thousand, not a few hundred. In an=
y case, I suppose you can make the argument that only a few people are tryi=
ng to access their home network resources remotely other than via some sort=
of proxy/rendezvous service. However, I would argue that such services exi=
st solely to provide a workaround for the deficiencies in the network intro=
duced by NAT. Get rid of the stupid NAT and you no longer need such service=
s.
>
> This is an interesting argument/point, but if you remove the rendevous
> service then how do you find the thing in your house? now the user has
> to manage DNS, or the service in question has to manage a dns entry
> for the customer, right?
You do not remove the locating service, what you remove is the remote
proxy service.
For example with a webcam on IPv4, you would connect to website to
download the video. The camera would also connect to the website to
upload the video.
On IPv6 the webcam would connect to the website to say that it is
alive and what its IP is. You would connect to the website and your
computer would get the IP and directly connect to the webcam. If
there were multiple people connecting, you may even be able to use
multicast.
