SLIDE 1
Outline
Multicast Address Allocation Overview ZC Multicast Address Allocation Issues
ZC Multicast Address Allocation Steve Hanna MALLOC WG co-chair Sun - - PowerPoint PPT Presentation
ZC Multicast Address Allocation Steve Hanna MALLOC WG co-chair Sun - - PowerPoint PPT Presentation
ZC Multicast Address Allocation Steve Hanna MALLOC WG co-chair Sun Microsystems, Inc. Outline Multicast Address Allocation Overview ZC Multicast Address Allocation Issues Dynamically Assigned IP Multicast Addresses Global Scope
SLIDE 2
SLIDE 3
Dynamically Assigned IP Multicast Addresses
Global Scope (225.0.0.0/8) "Big" Admin Scopes (various in 239.0.0.0/8) Allocation Scope (239.251.0.0/16) "Small" Admin Scopes (various in 239.0.0.0/8) Local Scope (239.255.0.0/16) Link-Local Scope (static-only in IPv4) Node-Local Scope (IPv6 only) Single Source (232.0.0.0/8)
SLIDE 4
MALLOC Architecture
Interdomain (MASC/Static) MAAS 1 Prefix Coordinator 1 MAAS 2 Prefix Coordinator 2 Intradomain (AAP) Client 1 Client 2 Client-Server (MADCAP)
SLIDE 5
AAP Overview
AAP = Address Allocation Protocol Intradomain protocol (allocation domain) Used by MAAS’s, Prefix Coordinators (like
MASC routers), and others
All messages are UDP packets multicast to a
scope-relative address (in the Allocation Scope for large scopes, in the scope being allocated from for small scopes)
SLIDE 6
AAP Messages
ASA
Address Set Announce
ASRP
Address Space Report
ACLM Address Claim AIU
Address In Use
AITU
Address Intent To Use
ANA
Address Not Available
SLIDE 7
MALLOC Architecture (Isolated)
Host 1 Host 2 AAP
SLIDE 8
MALLOC Architecture (with Edge Router)
Host 1 Host 2 Edge Router MADCAP Non-ZC MADCAP/AAP
SLIDE 9
ZC Host Behavior
If there's a MAAS (MADCAP server),
w USE IT!
If not, can allocate from ZC scopes
w Local Scope w Link-Local Scope (IPv6 only) w Node-Local Scope (IPv6 only) w Single Source Scope (IPv4 only)
SLIDE 10
ZC Host Address Allocation
For Node-Local and Single Source addresses,
allocate them yourself
For Local and Link-Local, use a subset of AAP:
w ACLM and w AIU
SLIDE 11
ZC Router Behavior
Are you an Edge router (between ZC & non-ZC)?
w If not, simply route multicast traffic transparently w If so, act as a mini-MAAS:
Establish a Local Scope boundary Act as a MADCAP server within the ZC env If there's a MADCAP server in the non-ZC env, forward
requests to it
Otherwise, participate in AAP in the non-ZC env and act as
a MAAS
SLIDE 12
Issues
How does a ZC router know if it's an edge router? Security Session Announcement Collisions likely, due to frequent topology
changes
Delay to establish AAP state