Project

General

Profile

Actions
Copy link

Task #1807

closed

nfd-status should include some identification of NFD

Added by Alex Afanasyev over 10 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Chengyu Fan
Category:
Tools
Target version:
v0.2
Start date:
Due date:
% Done:

100%

Estimated time:

Description

Both plain text and XML output should include some kind of identification of NFD instance. This could be KeyLocator information (e.g., key name) or something else from Data packets.

Actions
Copy link
 #1

Updated by Alex Afanasyev over 10 years ago

  • Category set to Tools
Actions
Copy link
 #2

Updated by Chengyu Fan over 10 years ago

  • Status changed from New to In Progress
  • Assignee set to Chengyu Fan
Actions
Copy link
 #3

Updated by Junxiao Shi over 10 years ago

  • Target version set to v0.2
  • Start date deleted (07/28/2014)

I suggest displaying the KeyLocator field, together with version information; this means, such information is not displayed in plain text if version is not requested.

The KeyLocator field is likely to contain a Name, but the code should be prepared to handle a KeyDigest.

This Task requires no change in ForwarderStatus protocol.

Actions
Copy link
 #4

Updated by Chengyu Fan over 10 years ago

The general status contains the version information as well. Why not put the nfd id in the general status? Especially if we need to show it on the status page.

For the KeyLocator field handling, that's a good suggestion.

Actions
Copy link
 #5

Updated by Junxiao Shi over 10 years ago 

General NFD status:
         routerKey=/example/router/ucla/spurs
           version=2000
         startTime=20140725T232341.374000
       currentTime=20140725T233240
            uptime=538 seconds
Actions
Copy link
 #6

Updated by Chengyu Fan over 10 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 0 to 100
Actions
Copy link

Also available in: Atom PDF