the malloc architecture
play

The malloc Architecture Steve Hanna steve.hanna@sun.com IP - PowerPoint PPT Presentation

The malloc Architecture Steve Hanna steve.hanna@sun.com IP Multicast Model Group is identified with class D IP address Any host can send to a multicast address To receive, join the group via IGMP Packets can be constrained


  1. The malloc Architecture Steve Hanna steve.hanna@sun.com

  2. IP Multicast Model • Group is identified with class D IP address • Any host can send to a multicast address • To receive, join the group via IGMP • Packets can be constrained using TTL or admin-scoped multicast addresses

  3. Hard Parts • Multicast addresses are relatively scarce • Multicast routing requires state – Finding core for a group – Maintaining a distribution tree • Multicast address allocation can help with both of these

  4. Ideal malloc Requirements • Collision-Free • High Address Space Utilization • Aggregatable Address Allocation • Robust • Scalable • Secure • Fast and Efficient

  5. The Bad News • We can’t do all that at the same time – See Mark Handley’s thesis • So we split up the problem space – Interdomain, Intradomain, and Host-Server • And relax a few overall requirements – Mostly Collision-Free – Decent Address Space Utilization

  6. Three Protocols • Interdomain: MASC • Intradomain: AAP • Host-server: MDHCP

  7. MASC

  8. MASC • Interdomain • Hierarchy of MASC domains • Time scale: days (to span outages) • Parent injects block • Siblings send out claims and complain if they collide • Parent can enforce policy

  9. AAP MASC Server MASC Domain MAAS MAAS MAAS

  10. AAP • Intradomain • Peer to peer via multicast • MASC server announces address sets • AAP servers claim addresses from the sets and announce those claims periodically • Uses periodic multicast announcements (like SAP)

  11. MDHCP Server Discovery MAAS MAAS Host

  12. MDHCP Request-Response MAAS MAAS Host

  13. MDHCP • Host-server • Similar to DHCP • Multicast Server Discovery • Unicast Request-Response • Fast and low-bandwidth • Assumes coordinated servers

  14. When to use malloc • Use full mechanism for some set of global addresses; others may be allocated statically by IANA or in some other way • For admin-scoped addresses, can use anything you like. We suggest using something like this. Do not need MASC for small scopes, though.

  15. Document Status • Architecture – Still needs minor revisions to reflect previous consensus • MASC, AAP, MDHCP, and Abstract API – All recently updated – Resolved some open issues, some remain – MDHCP to WG Last Call 1/99 – Other drafts to WG Last Call by 4/99?

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend