Project

General

Profile

Feature #4831

Redefine ParametersSha256DigestComponent covered area

Added by Junxiao Shi 3 months ago. Updated about 1 month ago.

Status:
Closed
Priority:
Normal
Assignee:
Start date:
Due date:
% Done:

100%

Estimated time:

Description

ParametersSha256DigestComponent is previously defined as a digest over Parameters element. This definition makes it impossible to introduce new elements covered by ParametersSha256DigestComponent in a compatible way.

To improve evolvability, the definition should be updated so that ParametersSha256DigestComponent covers a portion of Interest starting from any TLV element whose TLV-TYPE number falls under a certain range.


Related issues

Related to NDN Specifications - Task #4780: Make Interest Parameters TLV non-criticalClosed

Blocks NDN Specifications - Feature #4599: Redesign Signed Interest and Command Interest for packet format v0.3Closed

Blocks ndn-cxx - Feature #4658: Encode and decode Interest ApplicationParametersIn Progress

History

#1 Updated by Junxiao Shi 3 months ago

  • Related to Task #4780: Make Interest Parameters TLV non-critical added

#2 Updated by Junxiao Shi 3 months ago

  • Blocks Feature #4599: Redesign Signed Interest and Command Interest for packet format v0.3 added

#3 Updated by Junxiao Shi 3 months ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Discussion record: https://www.lists.cs.ucla.edu/pipermail/ndn-interest/2019-January/002346.html
Spec update: https://gerrit.named-data.net/5222

Implementation will go together with #4804 and is not part of this issue.

#4 Updated by Davide Pesavento 3 months ago

  • Status changed from Resolved to Code review

#5 Updated by Junxiao Shi 2 months ago

  • Status changed from Code review to Feedback

Spec merged, but JeffT has concerns on the naming of the name component with TLV-TYPE 0x02. He will post an update.

#6 Updated by Jeff Thompson 2 months ago

We have an Interest TLV element called Parameters. And we have a Name component called ParametersSha256DigestComponent, however it isn't just a digest of the Parameters element but includes other elements. So one or the other should be renamed. Some possibilities:

  1. Rename ParametersSha256DigestComponent to ParametersEtcSha256DigestComponent, since it is a digest of Parameters plus some other stuff. (Jeff T's proposal, but I don't have a strong feeling.)
  2. Rename the Parameters TLV element to ApplicationParameters.
  3. Since the other fields are also be considered parameters (processed by ParametersSha256DigestComponent), rename Parameters to ApplicationParameters and also rename SignatureInfo to SignatureInfoParameters, etc.

#7 Updated by Davide Pesavento 2 months ago

2019-02-20 call decides to go with option 2 in note-6.

#8 Updated by Junxiao Shi 2 months ago

  • Status changed from Feedback to Closed

#9 Updated by Junxiao Shi 2 months ago

  • Status changed from Closed to Feedback

Oh, this still needs a rename. I'll do it soon.

#10 Updated by Davide Pesavento about 2 months ago

  • Status changed from Feedback to In Progress
  • % Done changed from 100 to 80

#11 Updated by Junxiao Shi about 1 month ago

  • Status changed from In Progress to Code review
  • % Done changed from 80 to 100

#12 Updated by Junxiao Shi about 1 month ago

  • Status changed from Code review to Closed

#13 Updated by Davide Pesavento 20 days ago

  • Blocks Feature #4658: Encode and decode Interest ApplicationParameters added

Also available in: Atom PDF