<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><br class=""><blockquote type="cite" class="">On Apr 11, 2022, at 11:49 AM, Niels ten Oever <<a href="mailto:mail@nielstenoever.net" class="">mail@nielstenoever.net</a>> wrote:<br class=""><br class="">Excellent question.<br class=""><br class="">[question]<br class="">If a domain name (for instance "<a href="http://badperson.net" class="">badperson.net</a>") is sanctioned, should all subdomains of that domain (for instance "<a href="http://www.badperson.net" class="">www.badperson.net</a>") be automatically sanctioned as well? Or should each specific domain be sanctioned individually, recognizing that the operator of the sanctioned domain is then free to create additional as-yet-unsanctioned subdomains at will?<br class="">[/question]<br class=""><br class="">To what extend does this question differ from the question: what happens if different website are hosted on the same IP address ? This can be a case of the 'human shield' problem, but by no means has to be.<br class=""><br class="">To make this decision, I think there are several things to take into account:<br class=""><br class="">a. proportionality<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>- is there another way to reach the subdomain or website that is not the target of the sanction?<br class=""><br class="">b. impact<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>- is this service an important infrastructure for exercising human rights?<br class=""><br class="">c. alternatives<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>- is there another way to implement the sanction against the originally intended entity that would not hamper the non-sanctioned entity?</blockquote><div class=""><br class=""></div>Actually, BEREC’s statement today addressed exactly this issue:<div class=""><br class=""></div><div class=""><a href="https://berec.europa.eu/eng/news_and_publications/whats_new/9340-berec-supports-isps-in-implementing-the-eu-sanctions-to-block-rt-and-sputnik" class="">https://berec.europa.eu/eng/news_and_publications/whats_new/9340-berec-supports-isps-in-implementing-the-eu-sanctions-to-block-rt-and-sputnik</a><br class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div class="">It is BEREC’s understanding that the obligations to block RT and Sputnik are to be read in a broad manner and that all websites belonging to the entities mentioned in the Annex XV of the Regulation are covered… BEREC considers that all domains <i class="">incl. subdomains</i> (such as <a href="http://www.rt.com" class="">www.rt.com</a>, <a href="http://francais.rt.com" class="">francais.rt.com</a>, *.<a href="http://sputniknews.com" class="">sputniknews.com</a>, <a href="http://sputniknewslv.com" class="">sputniknewslv.com</a>, <a href="http://sputniknews.gr" class="">sputniknews.gr</a>, <a href="http://sputniknews.cn" class="">sputniknews.cn</a>, etc. ) related to the entities mentioned in the Annex XV fall under this exception. BEREC trusts that all parties will take action to implement the EU sanctions in a precise and timely manner.</div></div></blockquote><div class=""><div class=""><br class=""> -Bill<br class=""></div><br class=""></div></body></html>