I would argue for a Bylaw change, not because we "need" it, but because it would significantly decrease possibility of disputes from those who believe enforcement of a voluntary registry commitment DOES constitute (incorrectly in my mind) ICANN content regulation.That being said, although I think that the number of NOs to a Fundanmental Bylaw change would not exceed that allowed (that is, one), I am not at all convinced we will get the required three YESes.AlanOn Sun, May 19, 2024 at 10:04 AM avri--- via CPWG <cpwg@icann.org> wrote:_______________________________________________Hi,
I think when we get down to it, the jury will be out whichever way ICANN goes with the RVC-Bylaws decision - at least until the the Accountability measures have been run; i.e. reconsideration to whatever extent there is reconsideration, and IRP.
But it does sound to me like the AL voices are mostly supporting enforceability but not Bylaws changes, contrary to DI's claim.
Do I understand correctly?
Does anyone have an argument for why ICANN needs a bylaws change for enforceability?
Especially pertinent would be an end user argument for the bylaws change.
thanks
avri
On 2024-05-19 08:35, Hadia Abdelsalam Mokhtar EL miniawi via CPWG wrote:
+1 Greg to all what you have said. And just to note URS includes looking and referencing content.
What’s in the contract needs to be enforced otherwise just drop it.
Hadia
On 19 May 2024, at 8:23 AM, gopal via CPWG <cpwg@icann.org> wrote:
This is as usual a bone of contention. I am reading some of the post on this subject, but I am opting to reply to the very first post on this thread.
"ICANN Is Not the Internet Content Police" is the position as on 12 June 2015. Technically, Content Delivery Networks that can be under the purview of ICANN come into focus when certain "web content" has a high potential to go viral or [like in UK] citizens need to be aware of some crimes in the near neighbourhood.
Policing is an intricate idea in itself.
For example:
Policing: An International Journal of Police Strategies & Management is a quarterly peer-reviewed academic journal covering the study of policing. It was established in 1978. It became "Police Studies: International Review of Police Development" in 1977 after merging with the American Journal of police.
The real concern is when in trouble who should one look up to without taking law and enforcement into one's hands ?
There are content filters supported by many web browsers and one can use content filters on the server side too. The server side filters operate as commands. For example : filter r/33/-97/200 t/n
It used to be a tedium to check the specific ports and configuration. Now there are many good tools.
Server-side content filters block harmful content before it reaches the user’s device. They are installed on a key network device [firewall, load balancer, VPN gateway, email server], where they filter traffic based on a configurable set of rules.
There are advantages and disadvantages.
Does ICANN see any conflict in making the DNS happen with all good properties such as stability and resilience due to the provisions of Server Side Filters?
Thanks in advance.
Sincerely,
Gopal T V
0 9840121302
https://vidwan.inflibnet.ac.in/profile/57545
https://www.facebook.com/gopal.tadepalli
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Dr. T V Gopal
Professor
Department of Computer Science and Engineering
College of Engineering
Anna University
Chennai - 600 025, INDIA
Ph : (Off) 22351723 Extn. 3340
(Res) 24454753
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
________________________________
From: CPWG <cpwg-bounces@icann.org> on behalf of Olivier MJ Crépin-Leblond via CPWG <cpwg@icann.org>
Sent: 17 May 2024 16:09
To: cpwg@icann.org <cpwg@icann.org>
Subject: [CPWG] Jury still out on ICANN’s content policing powers
Interesting article summarising where we are:
https://domainincite.com/29888-jury-still-out-on-icanns-content-policing-powers
_______________________________________________
CPWG mailing list
CPWG@icann.org
https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
_______________________________________________
CPWG mailing list
CPWG@icann.org
https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
CPWG mailing list
CPWG@icann.org
https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.