Best Multicast Address for Many-to-Many Enterprise Messaging Application
Question
A many-to-many enterprise messaging application is using multicast as a transport mechanism.
As part of the network design for this application, which multicast address should be used, according to best practices outlined in RFC 2365?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.D.
RFC 2365 provides guidelines for the use of multicast addressing in enterprise networks. In this scenario, a many-to-many enterprise messaging application is using multicast as a transport mechanism. Therefore, it is important to select the appropriate multicast address to ensure efficient and reliable operation of the application.
RFC 2365 specifies that multicast addresses in the range of 224.0.0.0/4 are reserved for use by the Internet Assigned Numbers Authority (IANA). Within this range, certain multicast addresses are reserved for specific purposes. For example, the address 224.0.0.1 is reserved for all systems on a network segment, while 224.0.0.2 is reserved for all routers on a network segment.
The multicast addresses in the range of 232.0.0.0/8 to 232.255.255.255/8 are designated as globally scoped addresses, which can be used by any organization for any purpose. However, these addresses are not recommended for use in enterprise networks, as they may be routed across the public Internet and can cause security and operational issues.
The multicast addresses in the range of 239.0.0.0/8 to 239.255.255.255/8 are designated as administratively scoped addresses, which are intended for use within a single organization or administrative domain. These addresses are recommended for use in enterprise networks.
Therefore, the correct answer to this question is option C, 239.128.0.60. This is an administratively scoped multicast address that can be used within the enterprise network for the many-to-many messaging application. Option A (224.0.0.60) is not recommended as it is in the IANA reserved address range, while options B (232.192.0.60) and D (239.193.0.60) are not administratively scoped addresses and may cause operational and security issues in the enterprise network.
