[174385] in North American Network Operators' Group
Re: The Next Big Thing: Named-Data Networking
daemon@ATHENA.MIT.EDU (Masataka Ohta)
Sun Sep 7 18:39:33 2014
X-Original-To: nanog@nanog.org
Date: Mon, 08 Sep 2014 07:37:27 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
To: Barry Shein <bzs@world.std.com>
In-Reply-To: <21516.34466.439880.900138@world.std.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Barry Shein wrote:
> Understand these were speaking notes and it was safe to assume the
> audience basically understood DNS so it wasn't my intention to give an
> exhaustive introduction to how DNS works.
Surprisingly many people who basically understand DNS have the
same misunderstanding as you, which is why some people believe
in NDN.
> There also seems to be some splitting of hairs over the meaning of
> "site" in your response. That is, some sort of physical boundary vs an
> authoritative boundary.
Then, "site" based FQDN can not be used for scalable routing.
> At any rate my proposal doesn't eliminate hierarchical addresses,
See above.
> One could use the FQDNs themselves as hierarchical
> addresses at least as an external representation.
You are trying to define something not usable for scalable
routing a hierarchical address, which is as bad as your
attempt to distort the definition of "site".
Masataka Ohta
