Naming in content_oriented_architectures [repaired]
Published on: Mar 3, 2016
Transcripts - Naming in content_oriented_architectures [repaired]
Naming in Content-Oriented
Paper by: Ali Ghodsi et al.
Pressented by: Haroon Rashid
–Self certifying, flat naming (Cryptographic based).
–User friendly, hierarchical naming.
•Issues identified with Self-certifying names.
–Not scalable as these are not hierarchical
–Need a third party for translation purpose (like
–Better scalability than hierarchical by using flexible
–Have better security than human readable names.
–Both naming architectures can be combined.
Network security components
Entities for establishing security
•Real world Identity (RWI) – principal for data.
–Used for fetching the data
–Provided by principal
–Each principal associated with private/public key
–Used for authentication purposes
•RWI – Name: Helps in identifying the principal.
•RWI – Public key: Only intended principal could
claim to be the principal of data.
•Public key – Name: Associating key helps in
verifying the provenance of data.
•Bindings are transitive – proving any two of
them implies third one.
•Bindings in Human readable, Hierarchical
–Intrinsic binding:- RWI – Name
–Extrinsic binding:- Name - key by using certificate
authority (third party - PKI)
•Bindings in self-certifying names (P:L)
–Intrinsic binding (Name – key):- Take hash of key at
any node and check whether it hashes to P.
–Extrinsic binding:- RWI- key (external authority)
Human readable, Hierarchical
•Remain unchanged as
cryptographic algos evolve.
•Name - RWI binding not tight,
e.g., acronym ICSI.
•Tiny URLs obliterate Name –
Self-certifying, Flat (DONA)
• Usability - Difficult to
remember such names
•Require careful engineering to
retain names as algos. evolve.
•Hierarchical names help scalability
–Reduce size of routing table
–Reduce update rate of routing table
–Common Assumption – Aggregation impossible
–No hierarchy found but still supports greater
flexibility* in aggregation.
* Explicit aggregation is more flexible than inherent aggregation
•Deepest match working ??
• Fetch Terms:
-Principal creates various fetch terms
corresponding to different third party
- Like outsourcing of content dissemination.
- Seems much like of CDN.
Naming and Flexibility
•Human friendly naming require PKI for binding
keys to names.
–Require universal agreement on the root trust
• self certifying naming require external
authority for binding of keys to RWI.