Direct Access IPv6 or not

Hello, Iam reading the text below on technet and do not really understand some aspects:

https://technet.microsoft.com/en-us/library/jj134148.aspx

1.1.2 Plan IPv6 intranet connectivity

To manage remote DirectAccess clients, IPv6 is required. IPv6 allows DirectAccess management servers to connect to DirectAccess clients that are located on the Internet for the purpose of remote management.

Note

Using IPv6 on your network is not required to support connections that are initiated by DirectAccess client computers to IPv4 resources on your organization network. NAT64/DNS64 is used for this purpose. If you are not managing remote DirectAccess clients, you do not need to deploy IPv6. Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) is not supported in DirectAccess deployments. When you use IPv6, you can enable IPv6 host (AAAA) resource record queries for DNS64 by using the following Windows PowerShell command: Set-NetDnsTransitionConfiguration -OnlySendAQuery $false

What does "To manage" mean? Manage them with SCCM, connect with RDP? I really do not understand. That takes me to my next question, IPv6 is required to manage clients, but the article also states that Teredo can be used and IPv6 does not have to be deployed.

However, DirectAccess does not necessarily require connectivity to the IPv6 Internet or native IPv6 support on internal networks. Instead, it automatically configures and uses IPv6 transition technologies to tunnel IPv6 traffic across the IPv4 Internet (by using 6to4, Teredo, or IP-HTTPS) and across your IPv4-only intranet (by using NAT64 or ISATAP). 

So can we manage those clients and "deploy" ipv6 by using Teredo or do we need an internet facing IPv6 address, internal native Ipv6 infrastructure or both?