Re: [MBONED] An alternative to draft-ietf-mboned-64-multicast-address-format?

[<[e-mail]>]

Hi Stig, all,

The main purpose of draft-ietf-mboned-64-multicast-address-format is to specify the following: 

* an address format to embed an IPv4 address into an IPv6 address
* how to extract an IPv4 address from an IPv4-embedded IPv6 multicast address
 
draft-ietf-mboned-64-multicast-address-format concludes that it is useful to identify an IPv4-embedded IPv6 multicast address compared to a native IPv6 multicast address for the reasons listed in http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-format-02#page-11.

Cheers,
Med

>-----Message d'origine-----
>De : [e-mail] [mailto:[e-mail]] 
>De la part de Stig Venaas
>Envoyé : jeudi 28 juin 2012 23:57
>À : [e-mail]
>Objet : [MBONED] An alternative to 
>draft-ietf-mboned-64-multicast-address-format?
>
>The draft draft-ietf-mboned-64-multicast-address-format 
>specifies as you
>know, a new flag to indicate that an IPv4 multicast address is 
>embedded.
>This is useful for translators (and maybe other devices) that can then
>extract the IPv4 address and doing operations as needed on 
>that address.
>
>I would like to present a possible alternative, and hear your thoughts.
>What if instead, when the group address is specified in a PIM join, or
>an MLD report, there was a flag as part of the PIM/MLD message that
>indicated that an IPv4 address is embedded?
>
>A new draft describing this is available at
>http://tools.ietf.org/html/draft-kumar-mboned-64mcast-embedded-
>address-00
>
>What do you think? Might this be an alternative? Are there other
>cases (apart from receiving a PIM join or an MLD report), where we
>need to know that an IPv4 address is embedded in the group address?
>
>Stig
>_______________________________________________
>MBONED mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/mboned
>