Feature #3783
closed
Honor NextHopFaceId universally
100%
Description
Currently NDNLPv2 NextHopFaceId field is honored only under namespaces where client-control strategy is used.
Apps wanting to use this feature must change strategy choice, which incurs unnecessary latency.
NextHopFaceId field should be recognized in forwarding pipelines, so that it is honored regardless of strategy choice.
Apps wanting to use this feature still needs to enable local fields with faces/update command, so that GenericLinkService would decode the field.
Forwarding rules are:
- ContentStore lookup is always performed.
- If NextHopFaceId is present in an Interest, goto step6.
- Find effective forwarding strategy from StrategyChoice table.
- Trigger after receive Interest on the strategy.
- Abort these steps.
- If the face identified in NextHopFaceId does not exist, drop the Interest and abort these steps.
- Forward the Interest to the face identified in NextHopFaceId.
client-control strategy will be deprecated, but kept as an alias of best-route v1.
Files
Updated by Junxiao Shi about 8 years ago
- Description updated (diff)
- Assignee set to Junxiao Shi
- Estimated time set to 6.00 h
Updated by Junxiao Shi about 8 years ago
- Blocks Task #1942: NextHopFaceId test scenario added
Updated by Junxiao Shi about 8 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 10
NDNLPv2 is updated in https://gist.github.com/yoursunny/92d8c3514476be6a7b93/611d60f8276914066d9c60b49c8cfc6f2a32374d to reflect the rule about ContentStore lookup.
Updated by Junxiao Shi about 8 years ago
- Blocks Feature #3626: Use IncomingFaceId tag to direct LSA Interests added
Updated by Junxiao Shi about 8 years ago
- File forwarding-pipelines_20160918.pptx forwarding-pipelines_20160918.pptx added
- % Done changed from 10 to 20
Pipelines design is updated as forwarding-pipelines_20160918.pptx.
It will be added into devguide after implementation.
Updated by Junxiao Shi about 8 years ago
- % Done changed from 20 to 70
https://gerrit.named-data.net/3229 honors NextHopFaceId in ContentStore miss pipeline.
https://gerrit.named-data.net/3230 deprecates client-control strategy.
Updated by Junxiao Shi about 8 years ago
do we require permissions to use NextHopFaceId?
This is controlled by management authenticator.
should we add restriction that the flag can be specified only on local faces?
NDNLPv2 recommends NextHopFaceId feature to be enabled on local faces.
#3226-5 decides that FaceMgmt, at protocol level, should not restrict local fields (including NextHopFaceId) to be enabled on local faces only; however, this restriction can be controlled by management authenticator.
Or the above is already handled by the face system?
Before enabling local fields through FaceMgmt faces/update command, GenericLinkService will not set NextHopFaceIdTag.
Updated by Junxiao Shi about 8 years ago
- Status changed from In Progress to Resolved
- % Done changed from 70 to 100
nfd-docs:commit:376e90b4dd65d74ff8ddbf59c34a369829107a2f adds NextHopFaceId steps into ContentStore Miss pipeline section, and deletes client-control strategy section.
Updated by Junxiao Shi about 8 years ago
- Status changed from Resolved to Closed
Closing since there's no objection.