As promised, here is the second article on IP Multicast. This one specifically cover the addressing, which evolved in parallel to the high number of standards that define what multicast is today. I tried to compile a list that is as comprehensive as possible; if you find something that I omitted, please let me know, I will be glad to update this article accordingly. I hope this article will help you to quickly and efficiently review all or specific part of the multicast addressing.
This article is the first of a series about IP multicast. Multicast is a great technology which you may come across as an network engineer. Unfortunately, it's still a frequently overlooked technology due to its alleged complexity. In fact, multicast addressing is no more complex than unicast. Multicast routing is only about understanding a few basic principles, but once you get them, you can easily design and implement very large and sparse multicast networks. Troubleshooting is certainly more difficult because of the stateful nature of multicast routing, but with proper use of tools and procedures, you can quickly figure out where problems lies and how to solve them. As these aspects are very different from each other, I will cover them in separate articles. Here's the first article; an overview of IP multicast.
A few months ago, I had that crazy idea to write a book about IP Multicast. It's a technology I always found very attractive, but unfortunately quite overlooked by most network professionals. There is already lot of great literature on the subject, so I wanted to bring something new; treating the subject in both a vendor neutral and network-layer independent way. In addition to the consequent theoretical aspect of multicast, I wanted to share my practical experience by covering tools and troubleshooting procedures.
Fortunately, or unfortunately, I will let you judge, I've no more spare time to continue the writing of this book. Recent updates in my professional career plan have shorten my spare time considerably; enough to ask myself if it's not more profitable to release the content I already wrote for free, so anyone can benefit of it.