GTSM is not widely known, so be more concrete as to its effect

(viz. hop-limit-sensitive discards). Older implementations are
known to violate it, as it was made mandatory only recently by
RFC7552 (2015), eight years after the original LDP specification.
ok claudio@

1 files changed, 5 insertions, 5 deletions

diff --git a/usr.sbin/ldpd/ldpd.conf.5 b/usr.sbin/ldpd/ldpd.conf.5
index 2c797649be6..f06ada1d69f 100644
--- a/usr.sbin/ldpd/ldpd.conf.5
+++ b/usr.sbin/ldpd/ldpd.conf.5
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: ldpd.conf.5,v 1.37 2019/01/23 02:02:04 dlg Exp $
+.\"	$OpenBSD: ldpd.conf.5,v 1.38 2019/03/31 19:08:30 procter Exp $
 .\"
 .\" Copyright (c) 2013, 2016 Renato Westphal <renato@openbsd.org>
 .\" Copyright (c) 2009 Michele Marchetto <michele@openbsd.org>
@@ -19,7 +19,7 @@
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .\"
-.Dd $Mdocdate: January 23 2019 $
+.Dd $Mdocdate: March 31 2019 $
 .Dt LDPD.CONF 5
 .Os
 .Sh NAME
@@ -177,9 +177,9 @@ and RFC 7552 (for the IPv6 address-family).
 Since GTSM is mandatory for LDPv6, the only effect of disabling GTSM for the
 IPv6 address-family is that
 .Xr ldpd 8
-will not check the incoming packets' hop limit.
-Outgoing packets will still be sent using a hop limit of 255 to guarantee
-interoperability.
+will not discard packets with a hop limit below 255. This may be necessary
+to interoperate with older implementations. Outgoing packets will still be sent
+using a hop limit of 255 for maximum compatibility.
 .Pp
 If GTSM is enabled, multi-hop neighbors should have either GTSM disabled
 individually or configured with an appropriate gtsm-hops distance.