I'm looking at Web App Proxy in Server 2012 R2 as a successor to TMG. I am posting here because it is in the same group of features as Direct Access, RRAS and so on.
I can't find much documentation perhaps someone can help. I am especially interested in how this might handle IPv6. I have found these documents:
http://technet.microsoft.com/en-us/library/dn280944.aspx
http://www.ntsystems.it/post/Web-Application-Proxy-in-Windows-2012-R2-preview.aspx
http://blog.kloud.com.au/2013/07/15/publish-lync-2013-with-2012-r2-preview-web-application-proxy/
http://msdn.microsoft.com/en-us/library/windows/desktop/dn323740(v=vs.85).aspx
But none mention the NIC configuration and IPv6.
If I give the server 2 NICs (as I would have done a UAG or TMG or ISA server) they both get local link addresses
fe80::215:5dff:fe62:3734%12
fe80::215:5dff:fe62:3735%22
So as far as I can see the two NICs will communicate with each other on the local link, so why even have two NICs. I know the fe80 addresses should not be routed by the firewalls, but I am also curious as to how to do the IPv6 addressing: one subnet for the LAN, one for the DMZ, one for the WAN?
I suppose (thinking aloud) that the "firewall" features of TMG and ISA are no longer included, and that the Web App Proxy really does depend on being in a DMZ created by another device.
Help and documentation appreciated.
CarolChi