search

GrumpyOldTroll / draft-jholland-quic-multicast

Work in progress to propose a multicast extension to quic.
Other
6 stars 6 forks source link

What if MC_ANNOUNCE contains bogus IPs #101

Open LPardue opened 1 year ago

LPardue commented 1 year ago

The Source IP and Group IP have certain requirements. If I receive an MC_ANNOUNCE where e.g. the Group IP is not in the multicast IP range, what should I do?

One option is to say that senders MUST send valid values as per RFC 4607, and that receivers of bad values MUST ignore them, or that they MUST ignore them, or something along those lines. I didn't think much through the ramifications of this, maybe you have more opinion or experience?

GrumpyOldTroll commented 1 year ago

Yeah, good point. The reaction should be specified. My first idea is that declining a join to such a channel with a new reason like UNUSABLE_ADDRESS might be right. We don't really have a way to object to an announce, but refusing a join is easy. (BAD_ADDRESS also might be applicable for addresses that are multicast but reserved, or that are in a range that isn't for SSM.)