400-007 · Question #107
The network designer needs to use GLOP IP address in order make them unique within their ASN, which multicast address range will be considered?
The correct answer is C. 233.0.0.0 to 233.255.255.255. GLOP addressing, defined in RFC 3180, maps a 16-bit Autonomous System Number into the second and third octets of the 233.0.0.0/8 multicast range to create globally unique, ASN-scoped multicast addresses.
Question
The network designer needs to use GLOP IP address in order make them unique within their ASN, which multicast address range will be considered?
Options
- A239.0.0.0 to 239.255.255.255
- B224.0.0.0 to 224.0.0.255
- C233.0.0.0 to 233.255.255.255
- D232.0.0.0 to 232.255.255.255
How the community answered
(39 responses)- A5% (2)
- B3% (1)
- C87% (34)
- D5% (2)
Why each option
GLOP addressing, defined in RFC 3180, maps a 16-bit Autonomous System Number into the second and third octets of the 233.0.0.0/8 multicast range to create globally unique, ASN-scoped multicast addresses.
The 239.0.0.0/8 range is the Administratively Scoped multicast address space defined in RFC 2365, intended for private organizational use within a defined scope boundary, not for globally unique ASN-based addressing.
The 224.0.0.0/24 range contains Well-Known link-local multicast addresses reserved by IANA for routing protocols such as OSPF (224.0.0.5) and EIGRP (224.0.0.10), and is not available for GLOP allocation.
The 233.0.0.0/8 range is specifically designated for GLOP addressing per RFC 3180, where the two middle octets (233.X.Y.0/24) are derived from the organization's registered 16-bit ASN, guaranteeing global uniqueness without requiring central allocation. For example, ASN 1000 (0x03E8) maps to the block 233.3.232.0/24, allowing any organization with an ASN to derive its own unique multicast space.
The 232.0.0.0/8 range is reserved for Source-Specific Multicast (SSM) as defined in RFC 4607, where receivers subscribe to traffic from a specific source address, which is an entirely different multicast model.
Concept tested: GLOP multicast address allocation using ASN (RFC 3180)
Source: https://www.rfc-editor.org/rfc/rfc3180
Topics
Community Discussion
No community discussion yet for this question.