IS-IS has “forever” (at least since RFC 1195) supported multiple layer-3 protocol, but always with a nasty side-effect: if a link in your network did not support one of them, you could get hard-to-diagnose black holes. The problem is illustrated in the left-hand column of the following diagram. Due to a single IS-IS topology, the shortest path between A and B is the direct link and since IPv6 is not enabled on that link (click on the diagram to get an enlarged version where you'll be able to see the link colors), A and B cannot exchange IPv6 traffic even though there’s an alternate path between them.
I’m describing further implications of single/multi-topology IS-IS and deployment guidelines in the Building IPv6 Service Provider Core webinar.
When you enable multi-topology IS-IS (right-hand column in the diagram), the routers build two topologies, one for each L3 protocol (usually IPv4 and IPv6) and can find the optimum path for each L3 protocol even when some links in the network support only one of them.
You’ll find more details in the Multi-topology IS-IS white paper published by Cisco.