From looking it up it looks like it's mostly required when IP's change (e.g. when you change ISP), which for me is more of an argument to use DNS if you want fixed addresses.
And even if you run your internal services with only an AAAA record pointing to the ULA, the client's source address will likely be the global address of the client device unless you tweak the tables on each client, which then means you'll need to have your global address in all your firewall rules to access the internal services on ULAs, which then means you're not saved from having your ISP-provided global address in your configuration, which is what you were trying to avoid by using ULAs.
The existence of fridges with twitter integration proves that there is a need to a Lettice to tweet.
There are all kinds of things that exist, steam-powered motorbike among them. Not all of them exist for the right reasons.
Would you rather have a bunch of routers sending out advertisements which every client needs to sort out, or have one consistent multi wan load balancing/failover policy that is transparent to clients?
That's so much simpler than simple src-natting your clients at the edge of your control and routing your outgoing traffic based on a policy at your natting device /s
Using a firewall is obviously an option, but why give an IP to something you don’t want accessible by the outside world?
Thus proving that ipv6 failed in it's mission to get rid of nat
The uses that I found while searching weren't very convincing, I was hoping you could give an example.
