The paper's definitely worth reading, although it's worth noting that:
a) This is implementation heavy
b) The implementation is tied to a specific company migrating to this approach incrementally
I would say it's a great case study for moving to a ZTN, but if I were to explain ZTN I'd probably just propose a definition. I'm technically a vendor but the definition serves me in no way.
1. Requests are mutually authenticated and always encrypted (ex: mtls)
2. Requests are authorized; policy oriented, granular, and contextual authorization
3. Requests are monitored and audited
The paper lists a bunch of ways to accomplish those goals. SSO, device inventories, an authorizing proxy, a monitor, etc.
Of course, you're right. Vendors are horribly self serving and have already significantly degraded the term and confused people.