Loading ...
Sorry, an error occurred while loading the content.

1068RE: [tracker2] NSR support?

Expand Messages
  • scott@opentrac.org
    Sep 29, 2006
      That'll work with the existing preemption flag.
      As for using the destination address for routing, I'd rather see the routing specifier indicate the intent of the routing, and not the mechanics.  Don't say that you want to go two hops - say that you want to get to the nearest IGate, or to cover a 100-mile radius.
      A practical problem with the scheme is that you can't indicate what's been done to the packet without changing the destination and screwing up dupe checking.  Unless you put trace information in the digipeater path maybe...

      From: tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com] On Behalf Of Jason Winningham
      Sent: Friday, September 29, 2006 12:19 PM
      To: tracker2@yahoogroups.com
      Subject: Re: [tracker2] NSR support?

      If I understand things correctly, doesn't the "preemptive" flag on the
      T2 digi config indicate that I can do something like preemptive digi on
      a call of SAR and use

      WIDE1-1,WIDE2- 2,SAR7-7

      so that it'll use the normal infrastructure or any special SAR even
      digis that are up, if they're doing preemptive? The special event
      digis could ignore WIDE and focus the traffic on the SAR paths, but a
      tracker would still get in if it happened to hit a WIDE before it hit a

      Or is that the problem you're trying to solve?


    • Show all 10 messages in this topic