1 / 8

Multicast Listener Discovery Version 2 (MLDv2) for IPv6

Multicast Listener Discovery Version 2 (MLDv2) for IPv6. Rolland Vida, Luis Costa, Remi Zara, Serge Fdida, Steve Deering, Bill Fenner, Isidor Kouvelas, and Brian Haberman. <draft-vida-mld-v2-00.txt>. Multicast Listener Discovery (MLD). translation of IGMP for IPv6 semantics

favian
Download Presentation

Multicast Listener Discovery Version 2 (MLDv2) for IPv6

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Multicast Listener Discovery Version 2 (MLDv2) for IPv6 Rolland Vida, Luis Costa, Remi Zara, Serge Fdida, Steve Deering, Bill Fenner, Isidor Kouvelas, and Brian Haberman <draft-vida-mld-v2-00.txt>

  2. Multicast Listener Discovery (MLD) • translation of IGMP for IPv6 semantics • MLD – translation of IGMPv2 for IPv6 • Deering, S., Fenner, W., Haberman, B., "Multicast Listener Discovery (MLD) for IPv6", RFC 2710, November 1999. • MLDv2 – translation of IGMPv3 for IPv6 • Vida, R., Costa, L., Zara, R., Fdida, S., Deering, S. , Fenner, B. , Kouvelas, I., Haberman, B., "Multicast Listener Discovery Version 2 (MLDv2) for IPv6", Internet Draft - <draft-vida-mld-v2-00.txt>

  3. MLD vs. IGMP • Changed terminology for IPv6 semantics Group > Multicast Address Member > Listener Join > Start Listening Leave > Stop Listening … • Different message formats • 16-byte v6 addresses instead of 4-byte v4 addresses • Differences regarding backward compatibility • The protocol mechanisms are essentially the same

  4. MLDv2 vs. MLDv1 • Introduces source-filtering • The IP API must be modified to support it • Additional fields in the Report and Query messages • No host suppression in MLDv2 • Destination address for reports • In MLDv1 – the « group’s » multicast address • In MLDv2 – « all MLDv2-capable multicast routers » • All the modifications described in IGMPv3 related to source filtering

  5. MLDv2 vs. IGMPv3 • Compatibility with older versions • IGMPv3 keeps compatibility with IGMPv1 and IGMPv2 • MLDv2 only has to be compatible with MLD(v1)

  6. MLDv2 vs. IGMPv3 • Formula to derive the Max Resp Time from the Max Resp Code • Max Resp Code (in a query message) • In IGMPv3 on 8 bits, units of 1/10 seconds, max. value of ~52 minutes • In MLDv2 on 16 bits, units of miliseconds, max. value of ~140 minutes 0 1 2 3 4 5 6 7 +-+-+-+-+-+-+-+-+ |1| exp | mant | +-+-+-+-+-+-+-+-+ Maximum Response Delay = (mant | 0x10) << (exp+3) If Max Resp Code >= 128 0 1 2 3 4 5 6 7 8 9 A B C D E F +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |1| exp | mant | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Maximum Response Delay = (mant | 0x1000) << (exp+3) If Max Resp Code >= 32768

  7. MLDv2 vs. IGMPv3 • Destination addresses for reports • In IGMPv3 – "all IGMPv3-capable routers" = 224.0.0.22 (allocated by IANA) • In MLDv2 - "all MLDv2-capable routers" – a specific address is to be allocated by IANA

  8. Document Status • Individual submission • Should it go to IPNG or MAGMA? • Should it include « Anycast using MLD »?

More Related