Feature #4830
closed
Treat "no Parameters" and "zero-length Parameters" as equivalent
0%
Description
Zero-length Parameters convey no meaningful information so it should be disallowed.
Updated by Junxiao Shi about 5 years ago
One concern of treating "no Parameters" and "zero-length Parameters" as equivalent is: under current protocol, ParametersSha256DigestComponent is required if Parameters are present, and is forbidden if Parameters are omitted.
This leads to a conflict: if an Interest arrives at a node with "zero-length Parameters" and ParametersSha256DigestComponent, and the node decides to re-encode the Interest (e.g. during ForwardingHint modification) with "no Parameters", the node would have to strip away ParametersSha256DigestComponent. Consequently, the new Interest is semantically different from the old Interest because its Name has changed.
Suggested solution: forbid zero-length Parameters outright, so that ParametersSha256DigestComponent can appear only if the Interest has a non-empty Parameters.
Updated by Davide Pesavento about 5 years ago
- Status changed from New to In Progress
Updated by Davide Pesavento about 5 years ago
- Status changed from In Progress to Rejected
- Start date deleted (
02/04/2019)
Today's call (Feb 04) decides that "no Parameters" and "zero-length Parameters" are NOT equivalent.