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

[Junxiao Shi]

Hi Dave

The full Name of a Data packet is defined to be the Name field plus the
implicit digest.

An Interest, containing ImplictSha256DigestComponent or not, can be
satisfied by a Data packet, if the Interest Name is a prefix of Data full
Name.

Yours, Junxiao

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

>
> On Oct 10, 2014, at 10:30 AM, Junxiao Shi <shijunxiao at email.arizona.edu>
> wrote:
>
> > Hi Dave
> >
> > "implicit digest component" is implicit in Data packet. It cannot appear
> in Data packet, but must be computed when needed.
> > ImplicitSha256DigestComponent can appear in Interest Name as the last
> component, and in Exclude.
> >
> then I’m even more confused than I thought.
>
> If the digest is a name component, and the data packet is supposed to echo
> back the exact name that was present in the interest, why isn’t the hash
> the last name component of the data packet as well as the interest packet.
>
> The CCN 1.0 approach does this differently by not making the hash a name
> component, but as a separate TLV in the Interest with the semantic of “hash
> restriction” as opposed to “implicit has as part of the name”.
>
> > Yours, Junxiao
> >
> > On Fri, Oct 10, 2014 at 5:35 AM, Dave Oran (oran) <oran at cisco.com>
> wrote:
> > Here’s a silly question.
> > If the hash is now explicitly in the packet as a name component, isn’t
> is no long implicit but explicit?
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20141010/aeefdafc/attachment.html>