DMCA complaints belong to my customers hosting a website and not to me.
I do not monitor what websites my customers choose to host on their
individual instance of Apache Web Server on their assigned IP address, nor
do I disable individual websites. Ideally I will SWIP each IP to that
customer so I am not in the DMCA reporting path AT ALL. If I cannot, I
will still send the report to the customer for resolution and not deal
with it myself.
If my customer does not properly deal with the DMCA complaint properly,
my answer is to disable that customer and they can find someone else to
provide their hosting. Its right there in their contract.
While you are right that I can have these many sites all on the same IP,
the amount of time I would have to spend on central management to do so is
grossly greater than the cost of the required customer IP addresses, which
of course is already passed onto the customer anyway. Just the time for
determining who is responsible for a single DMCA complaint is enough to
pay for the one per customer IP address. With proper SWIP management DMCA
bypasses my desk completely. I am not responsible to cram as many sites
and customers onto a single IP in order to make room for others who want
to stay with IPv4. Each Customer also gets an IPv6 address, and an "AAAA"
record if they choose to use our DNS. IPv4 addresses are offered because
the market currently requires it. Maybe some day I can operate IPv6 only.
Albert Erdmann
Network Administrator
Paradise On Line Inc.
On Sat, 2 Mar 2019, Ronald F. Guilmette wrote:
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.
_______________________________________________
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.
