Feature #2990
closed
FaceMgmt: specify face persistency
Added by Junxiao Shi over 9 years ago.
Updated over 9 years ago.
Description
In FaceMgmt protocol faces/create command, allow requester to specify whether a face would be a permanent face or not.
The protocol shall also define the behavior when a face with the same FaceUri exists but has a different FacePersistency.
- Blocks Feature #2991: FaceManager: specify face persistency added
- Description updated (diff)
The obvious solution is adding FacePersistency field into ControlParameters.
An issue with this solution is: FacePersistency has been assigned a TLV-TYPE code in application range, but ControlParameters elements are required to have TLV-TYPE codes in forwarding daemon range.
This means we would have to renumber FacePersistency.
Before renumbering, I want to revisit the requirement of ControlParameters elements' TLV-TYPE codes to be assigned from forwarding daemon range.
NFD Management doesn't have a fundamental difference from a regular application protocol, so I don't understand why we need a "forwarding daemon range".
At 20150805 conference call Alex agrees to dropping the requirement of ControlParameters elements having TLV-TYPE codes in forwarding daemon range.
Therefore, FacePersistency can be added into ControlParameters without renumbering.
Code assignments for existing elements should remain unchanged.
- Status changed from New to In Progress
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Done. Updated to ControlCommand rev24 and FaceMgmt rev46.
I also added NInNacks and NOutNacks to the Face dataset.
- Status changed from Resolved to Closed
20150821 conference call approves note-7 design.
Also available in: Atom
PDF
Updated by