Re: [hrpc] Censorship

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 21 March 2022 16:59 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: hrpc@ietfa.amsl.com
Delivered-To: hrpc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C7933A1A5F for <hrpc@ietfa.amsl.com>; Mon, 21 Mar 2022 09:59:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.66
X-Spam-Level:
X-Spam-Status: No, score=0.66 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 50oTXjn3lgRg for <hrpc@ietfa.amsl.com>; Mon, 21 Mar 2022 09:59:43 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2A553A0F35 for <hrpc@irtf.org>; Mon, 21 Mar 2022 09:59:42 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 22LGx0kj026009; Mon, 21 Mar 2022 17:59:00 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id E8224207E1E; Mon, 21 Mar 2022 17:58:59 +0100 (CET)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id DB55D207DF8; Mon, 21 Mar 2022 17:58:59 +0100 (CET)
Received: from [10.11.240.9] ([10.11.240.9]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 22LGwx0l012205; Mon, 21 Mar 2022 17:58:59 +0100
Message-ID: <f181992d-6e49-e571-0d3a-fe6c40ea9d0f@gmail.com>
Date: Mon, 21 Mar 2022 17:58:59 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0
Content-Language: fr
To: S Moonesamy <sm+ietf@elandsys.com>, hrpc@irtf.org
References: <6.2.5.6.2.20220321085202.07188f08@elandnews.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
In-Reply-To: <6.2.5.6.2.20220321085202.07188f08@elandnews.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/ZfssDqtQrzOluTc6YmEg2Nicao4>
Subject: Re: [hrpc] Censorship
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: hrpc discussion list <hrpc.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hrpc>, <mailto:hrpc-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hrpc/>
List-Post: <mailto:hrpc@irtf.org>
List-Help: <mailto:hrpc-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hrpc>, <mailto:hrpc-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Mar 2022 16:59:48 -0000

Le 21/03/2022 à 17:08, S Moonesamy a écrit :
> Hi Alexandre,
>
>> I think the organisations in charge should gracefully remove .su from
>> DNS and provide an alternative like .aspiring-country to all those who
>> try to become such.  Also consider the term 'Union State' used between
>> Bel-Rus.
>
> There is a news article about .io: http://r.elandsys.com/r/78117 
> Neither of the two DNS identifiers are the work of the I*TF.  Why 
> should this IRTF group be part of the discussion space?


I did not know the .io problem - thanks!

Can I suppose that the .io problem is not as accute because of the 
following reason: they are not at war.

Can I dare to think for a moment that it is not because there are many 
similar problems that they are not problems?


Is the potential solution to the problem of .io to remove .io and 
replace it by something else?  Or is the solution to give the .io to 
somebody else?


As for IRTF and .su:

Hmm, it might be that a research could be performed to understand the 
human rights implications of using a wrong (false) domain name .su - 
this '.su' represents nothing, a non existent object; but because 
nothing is really 'nothing', it can be said that it has been populated 
by some people who might want .su to actually mean something.  Maybe the 
space was free because of inattention and someoe occupied for cheap.  
And there lies a problem.  The domain is in use out of lack of 
knowledge.  A crispation already exists there in that use of .su.

Maybe it is too much away from what IRTF might be interested in doing.

In that case, I still wonder where else could this wrongness and 
possible evolution towards righteousness (migration, smooth for users, 
the humans) of .su could be discussed.  The idea would be to delete .su 
but migrate the websites to some other domain, such that the humans (end 
users) still access the content.

There are also aspects of the .fr (written in russian) domain that could 
be discussed as well about human rights and entitlements (.fr in russian 
text stands for Federation of Russia, but in latin characters it stands 
for France; this potential confusion, that nobody seems to do, might 
have some implications; it might be that new names should be proposed 
such as to balance a 'primacy' such as to not hurt anyone's feelings; 
were they to be called '.fra' for France and '.fedru' for Russia, or 
even '.rusfed' in their own language, then there would be no confusion 
problem; other solutions are possible; all these might have impacts on 
human rights.

Alex

>
> Regards,
> S. Moonesamy