[Ndn-interest] Freshness & Latest Content

Urs Schnurrenberger urs.schnurrenberger at unibas.ch
Thu May 3 12:11:07 PDT 2018


I have some conceptual questions about freshness and how to ask for latest content.

Imagine 2 properly versioned versions of /nytimes/frontpage (properly in the sense of "larger" version = "newer" version, according to [1]):
format : contentName | freshnessPeriod
/nytimes/frontpage/v100 | 100ms [stored at cache X somewhere between requester and producer]
/nytimes/frontpage/v105 | 300ms [stored at producer]

I assume that if a user does only know about the contentName (prefix), but not about the latest versionNumber, he/she asks for
Interest: /nytimes/frontpage | CanBePrefix=true | MustBeFresh=true

Question 1:
Is it correct that this Interest is satisfied by cache X because there is a prefix match on the contentName and a freshnessPeriod > 0?

Question 2:
Assuming the answer to Q1 is 'yes' and that the reuqester does NOT know the latest versionNumber, is there really no possibility for the requester to get the globally latest version v105 directly from the producer?

Question 3:
Assuming that the requester KNOWS the latest versionNumber (from some miraculous oracle), I guess she/he can simply ask for (/nytimes/frontpage/v105 | CanBePrefix=false | MustBeFresh=true). Correct?

Best regards,

[1] http://named-data.net/wp-content/uploads/2014/08/ndn-tr-22-ndn-memo-naming-conventions.pdf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20180503/c4d7d99c/attachment.html>

More information about the Ndn-interest mailing list