Feature #1813
open
Include route flags in advertised names
Added by A K M Mahmudul Hoque over 10 years ago.
Updated almost 7 years ago.
Description
Inheritance flags affect the computation of next hops for a prefix. The default flag for registered RIB routes is capture, but this is not advertised to other routers.
It is possible for someone to register a route in NFD that gets readvertised into NLSR with child_inherit flags, but for that flag not to be honored in advertisements.
- NLSR would be able to inform other routers about the route flags associated with a given prefix.
- NLSR would consider these flags when computing next hops for a prefix.
Suggestion on this issue please
- Tracker changed from Task to Feature
- Subject changed from Advertised name should be configured with flag to Include route flags in advertised names
- Description updated (diff)
- Priority changed from High to Normal
- Target version set to v0.5.0
The original description by Hoque:
name is advertised by following way
advertising
{
; to advertise name prefixes owned by or directly reachable by the router,
; configure one block of prefix configuration command for every name
prefix /ndn/edu/memphis/cs/netlab ; name in ndn URI format
prefix /ndn/edu/memphis/sports/basketball
}
If flag is configurable then we should also change the configuration format. What about below format? Default value for flag is
catch.
advertising
{
; to advertise name prefixes owned by or directly reachable by the router,
; configure one block of prefix configuration command for every name
prefix
{
name /ndn/edu/memphis/cs/netlab ; name in ndn URI format
flags catch ; default value catch. Allowed value inherit and catch
}
prefix
{
name /ndn/edu/memphis/sports/basketball
}
}
Any suggestion?
- Assignee deleted (
A K M Mahmudul Hoque)
- Target version deleted (
v0.5.0)
This has been discussed a few times, but no one seems to know what this issue is about. It will be a floating task until we figure out what it was for.
Also available in: Atom
PDF
Updated by 
Updated by