Project

General

Profile

Feature #4441

Replace MinSuffixComponents and MaxSuffixComponents with CanBePrefix flag

Added by Junxiao Shi over 2 years ago. Updated over 2 years ago.

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

100%

Estimated time:

Description

In order to simplify selectors processing in forwarder and libraries, deprecate MinSuffixComponents and MaxSuffixComponents selectors, and introduce CanBePrefix selector.
CanBePrefix is a binary selector similar to MustBeFresh. Its absence has the same semantics as "MinSuffixComponents=1 MaxSuffixComponents=1" if the Interest name does not end with ImplicitSha256DigestComponent, or "MinSuffixComponents=0 MaxSuffixComponents=0" if the Interest name ends with ImplicitSha256DigestComponent. Its presence has the same semantics as "MinSuffixComponents=0 MaxSuffixComponents omitted".

This issue involves protocol updates only. Implementation in forwarder and libraries shall be separate issues.


Related issues

Blocks ndn-cxx - Feature #4527: Decode v0.3 Interest format and interpret as v0.2ClosedJunxiao Shi

Actions
#1

Updated by Davide Pesavento over 2 years ago

  • Subject changed from Replace MinSuffixComponents and MaxSuffixComponents with CanBePrefix selector to Replace MinSuffixComponents and MaxSuffixComponents with CanBePrefix flag
  • Status changed from New to Code review
  • Assignee set to Alex Afanasyev
#2

Updated by Davide Pesavento over 2 years ago

  • Status changed from Code review to Closed
  • % Done changed from 0 to 100
#3

Updated by Junxiao Shi over 2 years ago

  • Blocks Feature #4527: Decode v0.3 Interest format and interpret as v0.2 added

Also available in: Atom PDF