In message <[email protected]>, [email protected] wrote:
>Many hosting and access providers like to give each paying customer their >own IPv4 address, since it simplifies DMCA compliance. No, it doesn't. If I have a web server that's configured to serve up pages for 1,000 different web sites, and I get a DMCA complaint about one in particular, I can disable that one alone. Is this not self-evident? >Otherwise the >hosting provider needs to get into the middle of keeping logs for every >customer. No, you don't. I frankly don't know what you are going on about. How do logs even enter into this? If a DMCA complaint comes in, you go and look at the (alleged) offending content. If it appears that it may be a DMCA action, then you action either that page or the whole web site, as may suit you. How do logs even enter into this? They are demonstratably irrelevant. >As for NAT and even web hosting, the 64k port limitation is also an issue >as pointed out by others. No, it isn't. A web server needs one port (80). A mail server needs one port (25). A name server needs one port (53). A /24 block provides nearly seventeen *million* IPv4 ports for outbound _client_ use, most or all of which should actually be migrated over to IPv6 anyway. Regards, rfg _______________________________________________ ARIN-PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ([email protected]). Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected] if you experience any issues.
