Teemu Koponen (ICSI/HIIT) joint work with Mohit Chawla, Byung ...

More documents

Recommendations

Info

Where is the challenge?RHs need only keep routing state for data that lie belowor equal to it in the AS hierarchy.Toughest requirements on the Tier-1 providers -- belowit’s easy.Only supporting the FIND/REGISTER load critical.All other RH functionality is optional.
Computational requirementsRegistration processing requirements for a single Tier-1 ISP:10 11 names, 42 bytes per name = routing table of 4TB.Registration lifetime 2 weeks = 83000 registrations/s(w/ crypto ops).Forwarding requirements:20000 FINDs/s per every Gbit/s worth of traffic.Name resolution speeds, not packet forwarding speeds!
Page 1 and 2: Data-Oriented (and Beyond)Network A
Page 3 and 4: In the beginning...First applicatio
Page 5 and 6: User-relevant issuesPersistence: a
Page 7 and 8: Basic Design
Page 9 and 10: DONA approachHandled byProvided byP
Page 11 and 12: Self-certifying namesA piece of dat
Page 13 and 14: Resolution infrastructureREGISTER s
Page 15 and 16: Forwarding FIND(P:L)When FIND(P:L)
Page 17 and 18: ChallengesUsabilitySecurityConcernF
Page 19 and 20: Using name-based anycastName-based
Page 21: Feasibility
Page 25 and 26: Broader ArchitecturalImplications
Page 27: Thank you! Questions?

Teemu Koponen (ICSI/HIIT) joint work with Mohit Chawla, Byung ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?