[174358] in North American Network Operators' Group
Re: The Next Big Thing: Named-Data Networking
daemon@ATHENA.MIT.EDU (William Herrin)
Fri Sep 5 17:18:09 2014
X-Original-To: nanog@nanog.org
X-Really-To: <nanog@nanog.org>
In-Reply-To: <EEB60D32-C501-41F0-89DE-E6E176E62D34@cse.unr.edu>
From: William Herrin <bill@herrin.us>
Date: Fri, 5 Sep 2014 17:17:34 -0400
To: Murat Yuksel <yuksem@cse.unr.edu>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Fri, Sep 5, 2014 at 3:27 PM, Murat Yuksel <yuksem@cse.unr.edu> wrote:
> As far as I understand, NDN's basic premise is to
> install "names" into the network layer.
Hi Murat,
If they think names belong at layer 4 instead of layer 7 I can offer a
couple insights on how this might be used to make layer 3 cheaper and
more effective.
If they think names belong at layer 3 everyone in this forum can
rattle off a dozen reasons why that's totally wacko.
On Fri, Sep 5, 2014 at 2:51 PM, Field, Brian
<Brian_Field@cable.comcast.com> wrote:
> I'm only going to touch on a small part of what I
> understand NDN to be=E2=80=B9 namely making caching a first class citizen=
of the
> network.
Anycast can allow a supporting client to find the nearest device of
type X. And it can allow the local device of type X to find the
nearest regional device of type X. Making caching a first class
network element is positively needless.
Regards,
Bill Herrin
--=20
William Herrin ................ herrin@dirtside.com bill@herrin.us
Owner, Dirtside Systems ......... Web: <http://www.dirtside.com/>
Can I solve your unusual networking challenges?
