Multicast IP addresses fall within the range 184.108.40.206 - 220.127.116.11. In the pre-CIDR world, they would have been called Class D addresses (although nowadays it is not considered polite to use such vulgar terminology !). For the honours students, they are distinguished by the most significant four bits being "1110".
In the Ethernet world, a multicast MAC address is distinguished by a binary '1' in the least significant bit of the first byte. For IP multicast specifically, the Ethernet prefix "01-00-5e" is reserved.
Since it is obviously infeasible to have an equivalent of ARP when transmitting multicast traffic, we would ideally like a one-to-one mapping between multicast IP addresses and multicast MAC addresses. If we ignore the four most significant bits of the multicast IP address (which, as noted earlier, will always be "1110"), that leaves 28 bits of IP address information which needs to be mapped to a MAC address.
The astute reader may have noticed a problem by now: There are only 24 bits (the least significant three bytes of the MAC address) available into which to encode the IP address. Actually, it is even worse than this...only the lower 23 bits are available for use (for non-technical reasons which need not detain us here). To get around this, the most significant 9 bits of the multicast IP address are quite simply ignored and the remaining 23 bits are copied into the lowest 23 bits of the MAC address.
As a consequence of this, 5 bits of "useful" IP address information being scrapped, there is not a one-to-one mapping between multicast IP address and multicast MAC addresses. Rather, each multicast MAC address will be shared by 32 IP addresses.
This has implications for multicast application design. Typically, modern LAN switches have the intelligence to "filter" multicasts. Users will only "see" multicast traffic they have actually asked for, so that (for example) a high-bandwidth software download (using Ghost or something similar) will not affect network performance for all users. However, LAN switches are not IP-aware and will do their multicast filtering based on MAC addresses. This means that if the high-bandwidth software download is being transmitted on multicast IP address 18.104.22.168 and you are subscribed to a streaming video feed on multicast IP address 22.214.171.124 (which maps to the same MAC address), you are going to be swamped with the download traffic as well as your video feed.