Actions
Task #1932
closed
Permit zero-length NameComponent
Start date:
Due date:
% Done:
100%
Estimated time:
2.00 h
Description
Permit zero-length NameComponent.
A zero-length NameComponent doesn't have special meaning in terms of packet processing and forwarding.
The processing rule is exactly same as any other NameComponent.
Files
Updated by Junxiao Shi about 10 years ago
- Related to Bug #1763: Canonical Order section permits empty NameComponent added
Updated by Junxiao Shi about 10 years ago
- Blocks Task #1933: Permit zero-length NameComponent added
Updated by Junxiao Shi about 10 years ago
- Status changed from New to In Progress
Updated by Junxiao Shi about 10 years ago
- Status changed from In Progress to Code review
- % Done changed from 0 to 100
Updated by Junxiao Shi about 10 years ago
- Status changed from Code review to Closed
Updated by Junxiao Shi over 9 years ago
Updated by Yingdi Yu over 9 years ago
Why not use "NULL" as a special name component to indicate a particular name component is not available?
Updated by Junxiao Shi over 9 years ago
Reply to note-7:
The string "NULL", or more precisely, the binary octets 4E554C4C, is a regular NameComponent, and it differs from null.
Similarly, in C++, the char[] literal "NULL" does not equal nullptr.
Defining 4E554C4C to have a special meaning of null has two drawbacks:
- It limits what value a regular NameComponent can take. For example, nonNegativeInterger 1314212940 and string "NULL" are not representable.
- Its place in canonical ordering is unusual. It's surprising to see "A" < null but "hello" > null.
Updated by Alex Afanasyev over 9 years ago
I'm a litle bit lost now. Didn't we already allowed empty component to exist? What else needs to be done?
Actions