[174352] in North American Network Operators' Group
Re: The Next Big Thing: Named-Data Networking
daemon@ATHENA.MIT.EDU (Murat Yuksel)
Fri Sep 5 15:28:22 2014
X-Original-To: nanog@nanog.org
From: Murat Yuksel <yuksem@cse.unr.edu>
In-Reply-To: <D02F5BF1.25B5C3%brian_field@cable.comcast.com>
Date: Fri, 5 Sep 2014 12:27:35 -0700
To: "Field, Brian" <Brian_Field@cable.comcast.com>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
As far as I understand, NDN's basic premise is to install "names" into =
the network layer. I don't think they (the NDN inventors) consider it as =
a new "app" at this point, even tough eventually it may merely stay as a =
new app.
I think the final thing that will determine the success of NDN is =
whether or not pushing names into the network layer rather than handling =
it at the app layer is going to return significant enough benefits. On =
the positive side, we will get rid of name -> address -> name mapping we =
are doing with DNS, we will enjoy content caching in routers themselves =
without relying on content servers to do it for us, and the story of =
upgrading to IPv6 will be over. :) On the negative side, we will have =
to deal with a whole new set of security and privacy issues (I can see a =
new wave of funding for cyber-security folks), we will need to revamp =
our routers (arguably which seems to attract Cisco so far) to handle =
names rather than IP addresses, and most importantly re-educate our =
practitioners to configure these "revamped" routers!
The key question is that do we really need to push the names into the =
network layer? I personally don't see this will happen, particularly as =
a replacement to TCP/IP as was laid down in the slashdot article. The =
best bet, IMHO, for NDN is to establish software-based NDN routers that =
maintain content tagged with names. One way to imagine I guess is to =
consider each router as a NAT box for this. I just can't see it =
replacing IP-based forwarding. We all wish things were so easy to =
change, but simply they are not.
Best,
-Murat
On Sep 5, 2014, at 11:51 AM, Field, Brian =
<Brian_Field@cable.comcast.com> wrote:
>=20
> Here=B9s my $0.02. I=B9m only going to touch on a small part of what =
I
> understand NDN to be=8B namely making caching a first class citizen of =
the
> network. When you think about the types of traffic currently carried =
over
> our collective networks, there might be value if the network eco =
system
> more natively supported caching.
>=20
> Van=B9s first paper proposing this NDN concept (afaik) was in 2009.
>=20
> If we were to get into the =B3way-back=B2 machine to say 2003, when
> peer-2-peer was a big app, one might have then decided that we really =
need
> to make =B3peer-2-peer=B2 a first class citizen of the network. In =
fact the
> IETF tried [at some level] to do this with the DECADE WG. The app =
space
> evolved, p2p is no longer as prevalent, and DECADE saw/got little
> traction. =20
>=20
> In 1998, we might have been thinking about making NNTP a first class
> citizen of the network.
>=20
> Maybe we need to think about making *software* [instead of a specific
> service] a first class citizen of the network. What do I mean by =
this?
>=20
> If software were a first class citizen of our networks in 2003, we =
might
> have hopped onto our routers and done a =B3yum install decade=B2=8B =
which would
> install software that would make the network eco system more efficient =
at
> supporting p2p traffic.
>=20
> Today, on our network eco system we might do a =B3yum uninstall =
decade=B2 and
> then do a =B3yum install caching=B2=8B which might embed caching =
functionality
> into our routing eco system=8B hopefully making the delivery of =
cacheable
> content more efficient.
>=20
> In N years, when there is yet another new app pushing the network eco
> system, we might then be doing a =B3yum uninstall caching=B2 and =
instead doing
> a =B3yum install new-app=B2 which would make the network eco system =
more
> efficient at supporting this new-app.
>=20
> Brian
>=20
>=20
>=20
>=20
>=20
> On 9/5/14, 8:16 AM, "Jay Ashworth" <jra@baylink.com> wrote:
>=20
>> How many Youtube subject tags will fit in *your* routers' TCAM?
>>=20
>>=20
>> =
http://tech.slashdot.org/story/14/09/04/2156232/ucla-cisco-more-launch-con=
>> sortium-to-replace-tcpip
>>=20
>> [ Can someone convince me this isn't the biggest troll in the history
>> of the internet? Cause it sounds like shoehorning DNS /and Google/ =
into
>> IP in place of, y'know, IP addresses. ]
>>=20
>> Cheers,
>> -- jra
>> --=20
>> Jay R. Ashworth Baylink
>> jra@baylink.com
>> Designer The Things I Think =
RFC
>> 2100
>> Ashworth & Associates http://www.bcp38.info 2000 Land
>> Rover DII
>> St Petersburg FL USA BCP38: Ask For It By Name! +1 727 =
647
>> 1274
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20
Murat Yuksel
Associate Professor
Graduate Director
Department of Computer Science and Engineering=20
University of Nevada - Reno=20
1664 N. Virginia Street, MS 171, Reno, NV 89557.
Phone: +1 (775) 327 2246, Fax: +1 (775) 784 1877
E-mail: yuksem@cse.unr.edu
Web: http://www.cse.unr.edu/~yuksem=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
