Re: [hrpc] Censorship
Alexandre Petrescu <alexandre.petrescu@gmail.com> Tue, 22 March 2022 11:41 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 161C93A113A
for <hrpc@ietfa.amsl.com>; Tue, 22 Mar 2022 04:41:51 -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, HTML_MESSAGE=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] 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 Mjl1KuFghEGP for <hrpc@ietfa.amsl.com>;
Tue, 22 Mar 2022 04:41:48 -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 1D2C33A1139
for <hrpc@irtf.org>; Tue, 22 Mar 2022 04:41:47 -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 22MBfNJD016333; Tue, 22 Mar 2022 12:41:23 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1])
by localhost (Postfix) with SMTP id 0966E204567;
Tue, 22 Mar 2022 12:41:23 +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 EE78320444A;
Tue, 22 Mar 2022 12:41:22 +0100 (CET)
Received: from [10.8.32.130] (is245935.intra.cea.fr [10.8.32.130])
by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP
id 22MBfMl2025014; Tue, 22 Mar 2022 12:41:22 +0100
Content-Type: multipart/alternative;
boundary="------------9IGm5JnM3DvwZCmnKO0nFPwA"
Message-ID: <fd3fbd64-1348-d43f-1a69-af40e0b8cb33@gmail.com>
Date: Tue, 22 Mar 2022 12:41:23 +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>
<f181992d-6e49-e571-0d3a-fe6c40ea9d0f@gmail.com>
<6.2.5.6.2.20220322034608.0c41e928@elandnews.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
In-Reply-To: <6.2.5.6.2.20220322034608.0c41e928@elandnews.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/0nyLupKkUTz4QOHnXo7TQ1noP2Y>
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: Tue, 22 Mar 2022 11:41:51 -0000
I will not be able to answer, not because I dont want to. I will not discuss this privately, as I think it is more important. Thank you for the message. Alex Le 22/03/2022 à 12:37, S Moonesamy a écrit : > Hi Alexandre, > At 09:58 AM 21-03-2022, Alexandre Petrescu wrote: >> 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. > > A change request should not be dependent on whether the entities > involved in the matter are 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? > > Yes. > >> 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? > > I have not given any thought to a solution as it would most likely be > ill-informed. > >> 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. > > The ccTLD must have some value to the persons/organizations who > registered domain names under it or else they would not have > registered those domain names. > >> 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 was some discussion within ICANN about what to do about that > ccTLD. I haven't had time to keep track of the discussion. > >> 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. > > The above could be about universal acceptance or digital sovereignty. > > At 02:42 AM 22-03-2022, Alexandre Petrescu wrote: > >> Today I received an incident report in some conenctivity. It comes >> from an .io email address. But the report has nothing to do with >> the Indian Ocean area. >> >> Not only there is disconnection at IP layer but there is >> disconnection in our semantic understanding of what .io should mean, >> in the first place. > > It's an identifier which people use. The meaning depends on branding. > > Regards, > S. Moonesamy
- [hrpc] Censorship Vittorio Bertola
- Re: [hrpc] Censorship Bill Woodcock
- Re: [hrpc] Censorship Vittorio Bertola
- Re: [hrpc] Censorship Bill Woodcock
- Re: [hrpc] Censorship Eliot Lear
- Re: [hrpc] Censorship Bill Woodcock
- Re: [hrpc] Censorship Eliot Lear
- Re: [hrpc] Censorship S Moonesamy
- Re: [hrpc] Censorship avri
- Re: [hrpc] Censorship Stephen Farrell
- Re: [hrpc] Censorship Bill Woodcock
- Re: [hrpc] Censorship Stephen Farrell
- Re: [hrpc] Censorship Bill Woodcock
- Re: [hrpc] Censorship Stephen Farrell
- Re: [hrpc] Censorship Bill Jouris
- Re: [hrpc] Censorship Jens Finkhaeuser
- Re: [hrpc] Censorship Vittorio Bertola
- Re: [hrpc] Censorship Paul Wouters
- Re: [hrpc] Censorship Eliot Lear
- Re: [hrpc] Censorship Mallory Knodel
- Re: [hrpc] Censorship Niels ten Oever
- Re: [hrpc] Censorship Niels ten Oever
- Re: [hrpc] Censorship bzs
- Re: [hrpc] Censorship Bill Woodcock
- Re: [hrpc] Censorship Bill Woodcock
- Re: [hrpc] Censorship Bill Woodcock
- Re: [hrpc] Censorship Bill Jouris
- Re: [hrpc] Censorship Bill Woodcock
- Re: [hrpc] Censorship farzaneh badii
- Re: [hrpc] Censorship Paul Wouters
- Re: [hrpc] Censorship Paul Wouters
- Re: [hrpc] Censorship Bill Woodcock
- Re: [hrpc] Censorship Andrew Sullivan
- Re: [hrpc] Censorship bzs
- Re: [hrpc] Censorship bzs
- Re: [hrpc] Censorship Jens Finkhaeuser
- Re: [hrpc] Censorship Bill Woodcock
- Re: [hrpc] Censorship S Moonesamy
- Re: [hrpc] Censorship Niels ten Oever
- Re: [hrpc] Censorship Alexandre Petrescu
- Re: [hrpc] Censorship Andrew Sullivan
- [hrpc] draft-irtf-hrpc-association (was Re: Censo… Andrew Sullivan
- Re: [hrpc] draft-irtf-hrpc-association (was Re: C… Niels ten Oever
- Re: [hrpc] Censorship Niels ten Oever
- Re: [hrpc] Censorship Andrew Sullivan
- Re: [hrpc] Censorship Jens Finkhaeuser
- Re: [hrpc] ***SPAM**** Re: Censorship Stephen Farrell
- Re: [hrpc] Censorship bzs
- Re: [hrpc] Censorship Alexandre Petrescu
- Re: [hrpc] ***SPAM**** Re: Censorship Mallory Knodel
- Re: [hrpc] Censorship Niels ten Oever
- Re: [hrpc] ***SPAM**** Re: Censorship Bill Woodcock
- Re: [hrpc] Censorship Mallory Knodel
- Re: [hrpc] ***SPAM**** Re: Censorship Mallory Knodel
- Re: [hrpc] ***SPAM**** Re: Censorship Niels ten Oever
- Re: [hrpc] Censorship farzaneh badii
- Re: [hrpc] ***SPAM**** Re: Censorship Eliot Lear
- Re: [hrpc] Censorship Andrew Sullivan
- Re: [hrpc] ***SPAM**** Re: Censorship Mallory Knodel
- Re: [hrpc] ***SPAM**** Re: Censorship Melinda Shore
- Re: [hrpc] Censorship Stephen Farrell
- Re: [hrpc] ***SPAM**** Re: Censorship Eliot Lear
- Re: [hrpc] Censorship Niels ten Oever
- Re: [hrpc] Censorship Niels ten Oever
- Re: [hrpc] Censorship farzaneh badii
- Re: [hrpc] Censorship Desiree Miloshevic
- Re: [hrpc] Censorship Alexandre Petrescu
- Re: [hrpc] Censorship Alexandre Petrescu
- Re: [hrpc] Censorship S Moonesamy
- Re: [hrpc] Censorship Desiree Miloshevic
- Re: [hrpc] Censorship Alexandre Petrescu
- Re: [hrpc] Censorship Alexandre Petrescu
- Re: [hrpc] Censorship Alexandre Petrescu
- Re: [hrpc] Censorship S Moonesamy
- Re: [hrpc] Censorship Alexandre Petrescu
- Re: [hrpc] Censorship Alexandre Petrescu
- Re: [hrpc] Censorship S Moonesamy
- Re: [hrpc] RIPE Cooperation Working Group Remote … Alexandre Petrescu