Project

General

Profile

Actions
Copy link

Feature #4831

closed

Redefine ParametersSha256DigestComponent covered area

Added by Junxiao Shi almost 6 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Junxiao Shi
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 3 (0 open — 3 closed)

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

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

Actions
Blocks ndn-cxx - Feature #4658: Encode and decode Interest ApplicationParametersClosedDavide Pesavento

Actions
Actions
Copy link
 #1

Updated by Junxiao Shi almost 6 years ago

  • Related to Task #4780: Make Interest Parameters TLV non-critical added
Actions
Copy link
 #2

Updated by Junxiao Shi almost 6 years ago

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

Updated by Junxiao Shi almost 6 years 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.

Actions
Copy link
 #4

Updated by Davide Pesavento almost 6 years ago

  • Status changed from Resolved to Code review
Actions
Copy link
 #5

Updated by Junxiao Shi almost 6 years 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.

Actions
Copy link
 #6

Updated by Anonymous almost 6 years 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.
Actions
Copy link
 #7

Updated by Davide Pesavento almost 6 years ago

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

Actions
Copy link
 #8

Updated by Junxiao Shi almost 6 years ago

  • Status changed from Feedback to Closed
Actions
Copy link
 #9

Updated by Junxiao Shi almost 6 years ago

  • Status changed from Closed to Feedback

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

Actions
Copy link
 #10

Updated by Davide Pesavento almost 6 years ago

  • Status changed from Feedback to In Progress
  • % Done changed from 100 to 80
Actions
Copy link
 #11

Updated by Junxiao Shi almost 6 years ago

  • Status changed from In Progress to Code review
  • % Done changed from 80 to 100
Actions
Copy link
 #12

Updated by Junxiao Shi almost 6 years ago

  • Status changed from Code review to Closed
Actions
Copy link
 #13

Updated by Davide Pesavento over 5 years ago

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

Also available in: Atom PDF