On Sun, Mar 24, 2019 at 10:03:15PM +1300, Richard Procter wrote:
> The ldpd issue might merit a hint in the man page as I found it difficult to 
> diagnose 
> as a newbie (see attached patch), and the man page, while not wrong, threw me 
> by 
> stating that GTSM is mandatory for LDPv6; it is now but wasn’t in the past. 
> 
> ok for the patch?
> 

Thank you very much for testing and the report.

I like the idea of being more specific in the manual.
OK denis@, I would however remove the parenthesis.

> Are there any other tests you’d be interested in while I have the machine 
> configured? 
> 
> best, 
> Richard. 
> 
> Here’s the version info of JUNOS I was using (note the git -dirty commit 
> (!!!)) 
> 
> uname -a: FreeBSD mx480-lab-re0 JNPR-10.3-20171207.04b87e3_buil FreeBSD 
> JNPR-10.3-20171207.04b87e3_builder_stable_10 #0 r356532+04b87e3(HEAD)-dirty: 
> Thu Dec  7 09:13:19 PST 2017     
> buil...@basith.juniper.net:/volume/build/junos/occam/freebsd/stable_10/20171116.200501_builder_stable_10.04b87e3/obj/amd64/juniper/kernels/JNPR-AMD64-PRD/kernel
>   amd64
> 
> Model: mx480
> Family: junos
> Junos: 17.2R2-S2.1
> 
> RFC5036 (2007) "LDP Specification"
> 
> RFC6720 (2012) "The Generalized TTL Security Mechanism (GTSM) for LDP” - 1 
> >> GTSM specifies that "it SHOULD NOT be enabled by default in order to
> >> remain backward compatible with the unmodified protocol" (see
> >> Section 3 of [RFC5082]).
> >> 
> >> This document specifies a "built-in dynamic GTSM capability negotiation" 
> >> for
> >> LDP to suggest the use of GTSM.  GTSM will be used as specified in this
> >> document provided both peers on an LDP session can detect each others' 
> >> support
> >> for GTSM procedures and agree to use it.  That is, the desire to use GTSM
> >> (i.e., its negotiation mechanics) is enabled by default without any 
> >> configuration.
> 
> RFC7552 (2015) "Updates to LDP for IPv6” - 5.1
> >> Also, the LDP Link Hello packets MUST have their IPv6 Hop Limit set
> >> to 255, be checked for the same upon receipt (before any LDP-specific
> >> processing), and be handled as specified in Section 3 of [RFC5082].
> 
> 
> cvs server: Diffing .
> Index: ldpd.conf.5
> ===================================================================
> RCS file: /cvs/src/usr.sbin/ldpd/ldpd.conf.5,v
> retrieving revision 1.37
> diff -u -p -u -r1.37 ldpd.conf.5
> --- ldpd.conf.5 23 Jan 2019 02:02:04 -0000      1.37
> +++ ldpd.conf.5 24 Mar 2019 08:36:14 -0000
> @@ -177,7 +177,8 @@ and RFC 7552 (for the IPv6 address-famil
>  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.
> +will not check the incoming packets' hop limit. (This may be necessary to 
> +interoperate with implementations lacking RFC 7552 (2015) compliance.)   
>  Outgoing packets will still be sent using a hop limit of 255 to guarantee
>  interoperability.
>  .Pp
> 
> 

Reply via email to