Actions
Feature #3027
open
ForwarderStatus: RouterName
Status:
New
Priority:
Normal
Assignee:
-
Category:
Protocol
Target version:
-
Start date:
Due date:
% Done:
20%
Estimated time:
1.50 h
Updated by Junxiao Shi almost 9 years ago
- Blocked by Feature #3026: RouterName configuration option added
Updated by Junxiao Shi almost 9 years ago
- Start date deleted (
07/09/2015) - Estimated time set to 1.50 h
Updated by Teng Liang almost 9 years ago
- Blocks Feature #3028: ForwarderStatus: RouterName added
Updated by Junxiao Shi over 8 years ago
ForwarderStatus "single Data packet" is getting larger and larger.
With a configurable RouterName which can theoretically have any length, there's a risk of exceeding packet size limit.
I'm thinking about:
- make it a StatusDataset rather than "single Data packet"
- rename as
ndn:/localhost/nfd/status/generalto have same Name structure as other Management modules
Updated by Junxiao Shi over 8 years ago
20150803 conference call approves note-4.
We also decide that the old Interest Name ndn:/localhost/nfd/status should be accepted for one release.
Updated by Junxiao Shi over 8 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
ForwarderStatus is updated to revision 5.
Updated by Junxiao Shi over 8 years ago
- Related to Task #3081: Transition ForwarderStatus single packet to GeneralStatus dataset added
Updated by Junxiao Shi over 8 years ago
- Status changed from Resolved to New
- Assignee deleted (
Junxiao Shi) - Target version deleted (
v0.4) - % Done changed from 100 to 20
RouterName field is reverted because #3026 is abandoned.
The transition to a StatusDataset should still be done, and the addition of NInNacks and NOutNacks are retained.
Actions