Project

General

Profile

Actions
Copy link

Feature #4441

closed

Replace MinSuffixComponents and MaxSuffixComponents with CanBePrefix flag

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

Status:
Closed
Priority:
Normal
Assignee:
Alex Afanasyev
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 1 (0 open — 1 closed)

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

Actions
Actions
Copy link

Also available in: Atom PDF