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

More documents

Recommendations

Info

Application viewpointThere’s no separate lookup/resolving phase forapplications.Client application calls connect(P:L). Client stack:1. Issues a FIND(P:L) to locate an object P:L.2. Also initiates transport exchange <strong>with</strong> FIND(P:L).RH infrastructure routes only the FIND(P:L), while the IPlayer routes the following (data) packets.
ChallengesUsabilitySecurityConcernFlat names are hard toremember.Private keys will getcompromised.ApproachExternal mechanismsneeded.Key revocationmechanism needed.Scalability Huge flat namespace. More shortly...
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: Forwarding FIND(P:L)When FIND(P:L)
Page 19 and 20: Using name-based anycastName-based
Page 21 and 22: Feasibility
Page 23 and 24: Computational requirementsRegistrat
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?