> Sure. I can imagine a Linux implementation of "4via6 translation > support". If enabled, the TCP/IP stack would only bind to specific ports > (from the range). If you check the section III./C of the following paper: > > http://zhuyc.info/globecom08mivi.pdf > > the authors propose a modification "to the system call related to bind() > in the socket library of the operating system".
That is not practicable. You can't do such modification on innumerable hosts. > Then I could just connect my home gateway-server directly to the ISPs > network, providing support for "4via6 translation" and that's it. > > Also, I see is as a use case in non-ISP environments, where you could > have IPv6-only, but 4via6 enabled server networks, with servers supporting > "4via6 translation". Like SA46T-AS, for example. > > The main advantage of all this is of course that the IPv4 address is then > natively configured on the (virtual) interface. Sorry. I still can't see much benefits from that. Gang _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
