Re: [EAI] [IETF] Content Issues [
Yuriy Kargapolov <yvk@uanic.net> Sun, 16 October 2016 10:26 UTC
Return-Path: <yvk@uanic.net>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84D6C12969C for <ima@ietfa.amsl.com>; Sun, 16 Oct 2016 03:26:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.099
X-Spam-Level:
X-Spam-Status: No, score=0.099 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham 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 PDcjylsVy5BF for <ima@ietfa.amsl.com>; Sun, 16 Oct 2016 03:26:56 -0700 (PDT)
Received: from postoffice.net.ua (postoffice.net.ua [62.149.8.98]) by ietfa.amsl.com (Postfix) with ESMTP id 20AE2129411 for <ima@ietf.org>; Sun, 16 Oct 2016 03:26:55 -0700 (PDT)
Received: from [46.164.143.170] (account yvk@ua-nic.net HELO [192.168.1.121]) by postoffice.net.ua (DigitalGate Pro SMTP 5.2c3) with ESMTPSA id 427709505; Sun, 16 Oct 2016 13:26:51 +0300
Date: Sun, 16 Oct 2016 13:26:53 +0300
From: Yuriy Kargapolov <yvk@uanic.net>
Organization: uanic
X-Priority: 3 (Normal)
Message-ID: <776420919.20161016132653@uanic.net>
To: Shawn Steele <Shawn.Steele@microsoft.com>, "ima@ietf.org" <ima@ietf.org>
In-Reply-To: <MWHPR03MB281341141A1CE0C0895F58A482D10@MWHPR03MB2813.namprd03.prod.outlook.com>
References: <MWHPR03MB281341141A1CE0C0895F58A482D10@MWHPR03MB2813.namprd03.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ima/p0e89ZRp2M3Q2Q8F_rd421QjY0E>
Subject: Re: [EAI] [IETF] Content Issues [
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ima/>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Oct 2016 10:26:58 -0000
>> Seriously, at least in the near term, I'd oppose letting anyone post to an IETF list from a non-ASCII address. This has been discussed before in other contexts, but it is important that we, as a standards body, be able to identify who is posting to our lists and trying to influence outcomes. Anyone? Let's start from Administrators of IDN ccTLD/gTLD (admin-c or/and tech-c by IANA DB). They are "anyone"? > I'm confused because I don't see how EAI addresses would be less > accountable than ASCII addresses. Sure, they might be less > readable, but surely people could have > JohnDoe@SpecialServer.whatever and we'd have no clue who they "really" were. > I'd vote for "eat our own dogfood" > -Shawn Excuse me, from point of view man with English as mother-language you are right on 100% But some other picture will be from man with, for example, Swahili or Russian or Kyrgyz or Bulgarian ... - so much other mother-languages are exist on Earth Maybe I mistake or I didn't correctly understood you > _______________________________________________ > IMA mailing list > IMA@ietf.org > https://www.ietf.org/mailman/listinfo/ima -- Best Regards, Yuri mailto:yvk@uanic.net
- Re: [EAI] [IETF] Content Issues [ Shawn Steele
- Re: [EAI] [IETF] Content Issues [ Yuriy Kargapolov
- Re: [EAI] [IETF] Content Issues [ ned+ima
- Re: [EAI] [IETF] Content Issues [ Shawn Steele
- Re: [EAI] [IETF] Content Issues [ Shawn Steele
- Re: [EAI] [IETF] Content Issues [ John C Klensin
- Re: [EAI] [IETF] Content Issues [ John C Klensin
- Re: [EAI] [IETF] Content Issues [ Shawn Steele
- Re: [EAI] [IETF] Content Issues [ John C Klensin
- Re: [EAI] [IETF] Content Issues [ ned+ima
- Re: [EAI] [IETF] Content Issues [ ned+ima
- [EAI] [IETF] Barriers to Deployment [ was: Conten… nalini.elkins
- Re: [EAI] [IETF] Barriers to Deployment [ was: Co… John C Klensin
- Re: [EAI] [IETF] Content Issues [ Martin J. Dürst
- Re: [EAI] [IETF] Content Issues [ Martin J. Dürst
- Re: [EAI] [IETF] Content Issues [ Martin J. Dürst
- Re: [EAI] [IETF] Barriers to Deployment [ was: Co… ned+ima
- Re: [EAI] [IETF] Content Issues [ ned+ima
- Re: [EAI] [IETF] Content Issues [ Martin J. Dürst
- Re: [EAI] [IETF] Barriers to Deployment [ was: Co… John C Klensin
- Re: [EAI] [IETF] Content Issues [ ned+ima
- Re: [EAI] [IETF] Content Issues [ Martin J. Dürst