network manager
Click on the red underlined text to get to the source
... datagram simply because it believes that the delay of the available
paths is "too high" (actually, the network manager can override this
behavior through creative use of routing metrics, but this is
...
... datagram. Inside such a routing domain, the network manager may
choose to limit the size of the routing database ...
... TOS value (0000). Static routes have
their TOS values assigned by the network manager.
When a router ...
... routing
is a choice made by the network manager, a user requiring a free
path might not get one if the packet has to pass through a routing
...
... Very Weak TOS will make little practical difference, since (except
where the network manager has intentionally set things up
otherwise) there will be a route with the default TOS ...
... regard.
Under the first option, if the network manager neglects some
pieces of the configuration the likely consequence is that some
packets which would benefit from TOS ...
... routed as if they had requested the default TOS. Under the second
option, however, a network manager can easily (accidently)
configure things in such a way that packets which request a
certain TOS ...
... the first option would seem to have a slight edge with regard to
robustness in the face of errors by the network manager.
It has been also been suggested that the first option provides the
...
... routing loops) would result. The mechanisms
specified in this memo reflect the first option because that will
probably be more intuitive to most network managers. Internet
routing ...
... topology changes, routes with infinite
metrics occur only as the result of deliberate action (or serious
error) on the part of the network manager. Thus, packets are
unlikely to be discarded unless the network manager has taken
...
... error) on the part of the network manager. Thus, packets are
unlikely to be discarded unless the network manager has taken
deliberate action to cause them to be. Some people believe that
this is an important feature of the specification, allowing the
...
... cost be minimized off of a link that is so expensive that the
network manager feels confident that the users would want their
packets to be dropped. Others (including the author of this memo)
believe that this "feature" will prove not to be useful, and that
...
... routing choices
particularly more intuitive. It is also worth noting that this is
another case that a network manager has to try rather hard to
create: since OSPF ...
... non-zero TOS, a
network manager would have to await the development of a new
routing protocol or create ...
... semantics.
(2) This specification assumes that network managers will do "the
right thing". If a routing domain ...
... routing domain uses TOS, the network
manager must configure the routers in such a way that a
reasonable path is chosen for each TOS ...
... reasonable path is chosen for each TOS. While this ought not
to be terribly difficult, a network manager could accidently
or intentionally violate our rule that using the TOS facility
...