NFD Notification mechanism¶

NFD Notification mechanism notifies applications about events happening inside NFD.

Naming¶

• A stream of notifications is published under a certain Name prefix.
• A notification is one or more Data packets under this Name prefix with a version number and a segment number.
  • The version numbers of notifications in the same stream should be consecutive and increasing. They are not timestamps.
  • In most cases, a notification can fit in one Data packet, and would have segment number %00.

Example:

ndn:/localhost/nfd/face/status/2/%FD%00/%00 // first notification, first segment
ndn:/localhost/nfd/face/status/2/%FD%00/%01 // first notification, second segment
ndn:/localhost/nfd/face/status/2/%FD%01/%00 // second notification

Notification publisher¶

Notifications from NFD are Data packets generated and signed by NFD.

These Data packets enter forwarding system via the InternalFace, and are subject to regular forwarding pipelines.
They should be admitted into the ContentStore.

Notification subscriber¶

The subscriber should typically request the Name of notification stream (ndn:/localhost/nfd/face/status/2 in the example) with ChildSelector=1 and Exclude=<Any><Component>v</Component>, where v is the version number of the latest received notification.

• If no new notification has been generated after v, this Interest will stay in the PIT, and be satisfied when a new notification is generated.
• If one or more new notifications have been generated after v, the Interest will be satisfied from the ContentStore, and the latest notification is returned. The subscriber can retrieve missing notifications between v and the returned latest notification by expressing additional Interests.
• In the case that a notification has multiple segments, this Interest shall retrieve the first segment. The subscriber can retrieve subsequent segments by expressing additional Interests.