Task #1620
closed
NullFace and reserved FaceId
Added by Junxiao Shi over 10 years ago.
Updated over 10 years ago.
Description
Develop a NullFace which has no underlying transport and drops every outgoing packet.
Modify FaceTable FaceId assignment algorithm:
- FaceId 1~255 are reserved for special faces such as InternalFace and NullFace
- Ordinary faces are assigned FaceIds of 256 or above
Purpose: a blackhole FIB entry can be created by adding the well-known FaceId of the NullFace as its sole nexthop.
- Related to Task #1622: Special FaceId for ContentStore added
- Status changed from New to In Progress
- Assignee set to Junxiao Shi
- Target version set to v0.3
- Status changed from In Progress to Code review
- % Done changed from 0 to 100
Junxiao Shi wrote:
- FaceId 1~255 are reserved for special faces such as InternalFace and NullFace
Why are we not using FaceId == 0 for anything?
Why are we not using FaceId == 0 for anything?
The assignment is arbitrary.
It's better to leave 0 unassigned, just like IANA reserves the first and last block of class C IP addresses (until CIDR is introduced).
- Status changed from Code review to Closed
Also available in: Atom
PDF
Updated by 
Updated by