1. New Namespaces Jon Crowcroft, http://www.cl.cam.ac.uk/~jac22 http://www.cl.cam.ac.uk/teaching/1011/R02

2. Old Name Spaces 1 Hosts.txt Update → send new entry to FTP.ISI.ARPAFTP.ISI.ARPA Distribution → FTP to * (Broadcast) How is this different from *.com? The Main Name Service Note risks of root → Verisign accidental deletion of entire database Risk worse if TTL for Rrs set to 0 !

3. Old Name Spaces 2 X.500 Directory Tree Structure (like DNS) Distributed and Delegated Content = (Attrib, Value)* Can wildcard lookup attributes == SEARCH! Update has secure per record locks

4. Old Name Spaces 3 DNS Hackery... Rotaries – What is returned on each call varies – Load balancer – Hide mobility or failures – No interface for policy (backdoor hack) – Requires low(0?) to stop cacheing interfereing with LB

5. Old Name Spaces 4 DynDNS – Allow rapid update – Controlled more at leaves of system – Used by bad guys (e.g. botnets IRC controllers find bots via Dyn DNS) Secure DNS – Update (not just edit named boot file and kill -restart:) Better be secure – Needs key distribution architecture – Better not have cyclic dependency between key and dyndns/update :-(

6. INS + CCN Binding – Design, Code, Compile, Link, Load/Run, Call What, Where and When... – Semantics of thing returned – Dynamicity? Use? Esp. Update rate/churn in map INS looks like evolution CCN looks like revolution CCN does a lot of other things too...

7. INS limits Self org – why not use CAN, Chord etc? – Looks like directory too – Search efficiency? – Churn etc/ambiguity – See X.500/LDAP experiences... See also Appletalk :-)

8. CCN – What are people lookin for? Many URLs (dynamic web page) name content – So make this first class thing Most content is already replicated – “finding” replica is a DNS hack – e.g. LB or Akamaized URLs => So make this hack part of architecture – Fix limits (content not just@source orjust@source fully replicated (akamai/youtube limited model) See also Multicast and Pub/Sub But promote “cache” and “router” to be same thing

9. CCN problems? Integrity (pollution proof) HH – Need to have hash/MIC on set of blocks – And not break if “bad” block inserted Privacy of Subscription HC – Need to match interest to datum – Equiv. To tag matching in encrypted domain – Is x=y, when X and Y both crypted Computationally expensive... Some new results on homomorphic cryptography promising

10. Essays 1. IPNL, Ipv6, I^3 2. Multipath IP and TCP – See web page for – Resource pooling and multipath work – In essay/notes, discuss deployment possibilities – e.g. In wide area In enterprise In data center See also re-feedback work by Bob Briscoe for discussion of incentives/security

11. Essay 2 Multipath IP TCP other

12. Reading for 9/11/10 Internet Topology and its Evolution Social Networks