Project

General

Profile

Feature #4831

Redefine ParametersSha256DigestComponent covered area

Added by Junxiao Shi 15 days ago. Updated 8 days ago.

Status:
Feedback
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 to use ParametersIn Progress

History

#1 Updated by Junxiao Shi 15 days ago

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

#2 Updated by Junxiao Shi 15 days ago

  • Blocks Feature #4599: Redesign Signed Interest and Command Interest to use Parameters added

#3 Updated by Junxiao Shi 15 days 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 15 days ago

  • Status changed from Resolved to Code review

#5 Updated by Junxiao Shi 8 days 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 8 days 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.

Also available in: Atom PDF