[Nfd-dev] Please review the update of NDN-TLV spec, introducing implicit digest name component

[Junxiao Shi]

Hi Dave

Please see the following pseudocode that explains the sentences below.

data.fullName = data.name + computeImplicitDigest(data);

function matches(interest, data) {
  if (! interest.name.isPrefixOf(data.fullName))
    return false;
  // test other selectors
  return true;
}



Yours, Junxiao

On Fri, Oct 10, 2014 at 8:31 AM, Dave Oran (oran) <oran at cisco.com> wrote:

>
> On Oct 10, 2014, at 11:15 AM, Junxiao Shi <shijunxiao at email.arizona.edu>
> wrote:
> >
> > The full Name of a Data packet is defined to be the Name field plus the
> implicit digest.
> >
> Therefore, by this logic the digest should not be semantically treated as
> a name component. Unless I’m misunderstanding the syntax proposal below, it
> makes the digest a name component.
>
> > An Interest, containing ImplictSha256DigestComponent or not, can be
> satisfied by a Data packet, if the Interest Name is a prefix of Data full
> Name.
> >
> I don’t understand this sentence.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20141010/ac6f0b17/attachment.html>