NLSR

Feature #1813

Updated by Nicholas Gordon over 7 years ago

Inheritance flags affect name is advertised by following way  



     advertising 
     { 
     ; to advertise name prefixes owned by or directly reachable by the computation router, 
     ; configure one block of next hops prefix configuration command for a prefix. The default 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 registered RIB routes flag is capture, but this is not advertised 
 catch. 


     advertising 
     { 
     ; to other routers.  

 It is possible advertise name prefixes owned by or directly reachable by the router, 
     ; configure one block of prefix configuration command for someone to register a route every name 

        prefix 
        { 
           name /ndn/edu/memphis/cs/netlab             ; name 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 ndn URI format 
           flags associated with a given prefix. 
 * NLSR would consider these flags when computing next hops for a prefix. catch                                 ; default value catch. Allowed value inherit and catch 
        } 
       
        prefix 
        { 
           name /ndn/edu/memphis/sports/basketball 
        } 
     } 


 Any suggestion?

Back