Re: [hrpc] Censorship
S Moonesamy <sm+ietf@elandsys.com> Tue, 22 March 2022 11:37 UTC
Return-Path: <sm@elandsys.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 4047C3A112A for <hrpc@ietfa.amsl.com>; Tue, 22 Mar 2022 04:37:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.707
X-Spam-Level:
X-Spam-Status: No, score=-1.707 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com
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 p3QKvZ030U51 for <hrpc@ietfa.amsl.com>; Tue, 22 Mar 2022 04:37:52 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EACC3A1129 for <hrpc@irtf.org>; Tue, 22 Mar 2022 04:37:52 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.107.36]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id 22MBbYvt021408 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Mar 2022 04:37:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1647949066; x=1648035466; i=@elandsys.com; bh=21jQdsFusAsZQKqRE85XhbS9n+viRsVxbECH/2JL/Lk=; h=Date:To:From:Subject:In-Reply-To:References; b=nY/bhkJAG4t31+bQbN9Pf0kyZ8iEMmFhDISZjo1flTvwOpMDHFXG4AhpUGdVnra1/ i1fteE4wGNaHNTnXM3QhLLEG06CcLBoCxxvZpgOJz384qgo52fg3373gyi0KV1GkTc uk7W5IYoQWGa0XKRGeCJXSh0vCztpAxGg2kttSrc=
Message-Id: <6.2.5.6.2.20220322034608.0c41e928@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 22 Mar 2022 04:37:09 -0700
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, hrpc@irtf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <f181992d-6e49-e571-0d3a-fe6c40ea9d0f@gmail.com>
References: <6.2.5.6.2.20220321085202.07188f08@elandnews.com> <f181992d-6e49-e571-0d3a-fe6c40ea9d0f@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/TN3VStJ9dhZoPNYtRchxYKjen8c>
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:37:57 -0000
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