summaryrefslogtreecommitdiffstats
path: root/usr.sbin/ldpd/labelmapping.c
diff options
context:
space:
mode:
authorrenato <renato@openbsd.org>2015-07-19 20:50:03 +0000
committerrenato <renato@openbsd.org>2015-07-19 20:50:03 +0000
commit7b9982ada470bd15c9003a8316437c81f50cbdfe (patch)
treed25757843c9eca30847270d324d4352e8a572bca /usr.sbin/ldpd/labelmapping.c
parentAdd infrastructure for specifying a "version script" for the shared library (diff)
downloadwireguard-openbsd-7b9982ada470bd15c9003a8316437c81f50cbdfe.tar.xz
wireguard-openbsd-7b9982ada470bd15c9003a8316437c81f50cbdfe.zip
Remove incomplete support for unnecessary modes of operation.
LDP has several modes of operation, it was designed in that way so it could run on legacy equipment like ATM/FR switches with very strict memory limitations. For modern hardware there's no point on using either the "Conservative Label Retention" or "Downstream On Demand" modes of operation since they save memory at cost of blackholing traffic when routing changes. Major vendors implement only the "Liberal Label Retention" and "Downstream Unsolicited" modes for non ATM/FR hardware. Let's do that too. As for using either "Independent Control" or "Ordered Control", let's stick with the first option mainly because it's easier to implement and because it doesn't really matter which control mode is used. For reference, Cisco implements only "Independent Control" and Juniper only "Ordered Control". Both modes are interoperable. The point of supporting only one combination of all modes of operation is that it will allow for the writing of a simpler code without removing useful functionality. ok claudio@
Diffstat (limited to 'usr.sbin/ldpd/labelmapping.c')
0 files changed, 0 insertions, 0 deletions