352-001 · Question #106
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 be
The correct answer is D. 239.193.0.60. RFC 2365 defines the administratively scoped multicast range 239.0.0.0/8 for private use, and 239.193.0.60 falls within the organization-local scope subrange 239.192.0.0/14.
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?
Options
- A224.0.0.60
- B232.192.0.60
- C239.128.0.60
- D239.193.0.60
How the community answered
(38 responses)- A5% (2)
- B3% (1)
- D92% (35)
Why each option
RFC 2365 defines the administratively scoped multicast range 239.0.0.0/8 for private use, and 239.193.0.60 falls within the organization-local scope subrange 239.192.0.0/14.
224.0.0.60 falls within the 224.0.0.0/24 well-known link-local range reserved by IANA for routing protocols and network infrastructure, and must not be used for enterprise application traffic.
232.192.0.60 falls within the 232.0.0.0/8 Source-Specific Multicast range defined by RFC 4607, which is a separate protocol range and is not the administratively scoped range specified in RFC 2365.
239.128.0.60 is within the 239.0.0.0/8 administratively scoped space but does not fall within the organization-local scope subrange 239.192.0.0/14 that RFC 2365 recommends for enterprise applications.
RFC 2365 designates 239.0.0.0/8 as the administratively scoped IPv4 multicast address space for private enterprise use. Within this range, 239.192.0.0/14 is specifically reserved for organization-local scope, meaning it is appropriate for a single enterprise or organization. The address 239.193.0.60 falls squarely within this organization-local subrange, making it the correct best-practice choice per RFC 2365.
Concept tested: RFC 2365 administratively scoped multicast address selection
Source: https://www.rfc-editor.org/rfc/rfc2365
Topics
Community Discussion
No community discussion yet for this question.