RE: [BEHAVE] RE: [MBONED] FW: WGLC: draft-ietf-behave-multicast-06.txt
"Manfredi, Albert E" <[email protected]>
| Newsgroups | gmane.ietf.magma,gmane.ietf.nat.behave |
|---|---|
| Message-ID | <CA7D9B4A761066448304A6AFC09ABDA9015AD23D@XCH-NE-1V2.ne.nos.boeing.com> |
> -----Original Message----- > From: Brian Haberman [mailto:[email protected]] > The main issue being that on the upstream interface of the NAPT, the > same source address will be used for the Report and Done message. So > depending on the order of those messages, traffic may stop temporarily > (until the router sends another Query). Except that, I thought, the multicast router has to send group-specific or group-and-source-specific queries before it stops forwarding multicast packets, in IGMPv2 (the former only) and v3. This is supposed to ensure that there are no members left in the group, before the multicast router stops forwarding the packets. So I'm not sure why there would be this gap in multicasts if everything is working as it should. Not that I have anything against aggregation. Just that it seems unnecessary. It would be nice if the NAT or NAPT device could be as transparent as possible, I think. Bert