diff options
author | Renato Westphal <renato@opensourcerouting.org> | 2017-04-22 03:10:42 +0200 |
---|---|---|
committer | Renato Westphal <renato@opensourcerouting.org> | 2017-06-05 17:24:11 +0200 |
commit | abb160061189c9e4a1a8ab28aea4acbd64c32066 (patch) | |
tree | 39a37a92c221dc02cb7b16e7444b5abcc1c3ebbe /COMMUNITY.md | |
parent | ldpd: improve ldp_zebra_read_route() (diff) | |
download | frr-abb160061189c9e4a1a8ab28aea4acbd64c32066.tar.xz frr-abb160061189c9e4a1a8ab28aea4acbd64c32066.zip |
ldpd: schedule the sending of label messages when necessary
Once we send a Label Withdraw, we can't send a Label Mapping for the
same FEC until we receive a Label Release from the peer. This is due to
some limitations in the LDP algorithms described in Appendix A. ("LDP
Label Distribution Procedures") of RFC 5036.
To workaround this issue, make it possible to schedule the sending of
a Label Mapping as soon as a Label Release is received for the same FEC.
The easiest way to test this patch is by typing the "label local advertise
explicit-null" command. ldpd will withdraw all null labels using a
Wildcard FEC and then send new Label Mappings as soon the corresponding
Label Releases are received.
Signed-off-by: Renato Westphal <renato@opensourcerouting.org>
Diffstat (limited to 'COMMUNITY.md')
0 files changed, 0 insertions, 0 deletions