RE: [BEHAVE] Re: RE: [MBONED] FW: WGLC:draft-ietf-behave-multicast-06.txt
"Dan Wing" <[email protected]> Wed, 6 Jun 2007 15:20:49 -0700
| Newsgroups | gmane.ietf.magma,gmane.ietf.nat.behave |
|---|---|
| Message-ID | <[email protected]> |
> The NAPT knows what is SSM. Couldn't it also do a Multicast Group > Translation for SSM groups ? Why > is this more difficult than, say, port translation ? It may be fairly easy -- except for rewriting the advertisements in SAP, HTTP, HTTPS (a big problem there), email, SIP, RTSP, .... And NAPTs don't do that kind of rewriting today; draft-ietf-behave-multicast is only a BCP and trying to describe what a NAT should best be doing as of its date of publication. If we want NAPTs to do this, we would want a different document that was standards-track and that document would define how we wanted NAPTs to perform this function. However, I don't see a successful path if such an operation would require the NAPT to have an ALG for SAP, HTTP, SIP, and RTSP and requires the NAT also rewrite those packets. We'd need something else. ALGs don't work well for a variety of reasons. -d