<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Dec 18, 2016 at 12:10 PM, Eric S. Raymond <span dir="ltr"><<a href="mailto:esr@thyrsus.com" target="_blank">esr@thyrsus.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">> Can I clarify:<br>
> This 'multicast' is not necessarily the same as the IANA addresses,<br>
> 224.0.1.1 and FF0X::101.<br>
<br>
</span>Correct. As you note, the documentation used ti caution agains using<br>
the IANA multicat address. I don't know why.<div class="gmail-yj6qo gmail-ajU"><div id="gmail-:12c" class="gmail-ajR" tabindex="0"></div></div></blockquote></div><br></div><div class="gmail_extra">I assume because you might (as a client) try to use 224.0.1.1 as a server, send out a query, and die under the millions of servers that respond. Thankfully, this was avoided by no one using multicast on the public internet (whew!).<br></div><div class="gmail_extra"><br>I would like a Time Lord to answer the below (preferably without reading the documentation):<br><br></div><div class="gmail_extra">As a broadcast client, I listen to broadcast messages. I know what happens when I get one, I mobilise an (ephermal) association. What if I get two?<br><br></div><div class="gmail_extra">As a broadcast client, I listen to broadcast messages. Do I ever grab-n-prune?<br><br></div><div class="gmail_extra">When a manycast server replies for the first time, what IP address does it use as the sender?<br><br><br clear="all"></div><div class="gmail_extra"><div><div class="gmail_signature">-- <br>Sanjeev Gupta<br>+65 98551208 <a href="http://www.linkedin.com/in/ghane" target="_blank">http://www.linkedin.com/in/ghane</a></div></div>
</div></div>