IETF Logo Mail Archive

Re: IETF LLC & IETF Participation from USA-sanctioned countries

Keith Moore <moore@network-heretics.com> Mon, 08 March 2021 17:20 UTC

Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66E903A133D for <ietf@ietfa.amsl.com>; Mon, 8 Mar 2021 09:20:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.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 s0_4MH3SA-wH for <ietf@ietfa.amsl.com>; Mon, 8 Mar 2021 09:20:57 -0800 (PST)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69B973A134D for <ietf@ietf.org>; Mon, 8 Mar 2021 09:20:46 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id F2C9D28E7 for <ietf@ietf.org>; Mon, 8 Mar 2021 12:20:45 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Mon, 08 Mar 2021 12:20:46 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=W3RLNL q6jvf11nuB/3srhl+Vtw03GFxiAopLtc+z9bU=; b=nj1b02jRSetjYNTx/I4Y4g 3b1aG5/ymHQSS82l3Y91FtNBudG7gd7qcfSFQ2FnY07qxX+8iljug6xXNVPaxXJ2 wvMyD/9/WUn8JKJ7DYdwpYqI/j2MisokpXKz//5uSUrle/TYZQXvbL12ucrf/vyU ZRCJiw0X+qhRkkhIkJIZASq/dVCiemcg8TBE35LCu4rU+wd0plUjORtiJxk5+x2Q 4WueLhmj6Rb2yXxIIvjk2Gr53cTyDF5EgXJ3JRJ6sWUzRr9HTTbkRUlFdFkSTD7Q PVeTS2/7acJ5lFVOFc4K/R3mchSdx5Q20jvW5By/FLVhN2coV7epPYfUPjVeDJuA ==
X-ME-Sender: <xms:7VxGYJwvGdPYl9wBNx49Vrf2shuFf2i6OhJRCkf-c_VIUjuqXljPaA> <xme:7VxGYJSJRfbbOHScDpycSa4HSS62WDXQkq5izYvH6K3PQkpW2rb_JDZ57EvN_AACw qKsl7VQYbvDqQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledruddugedgfeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgesrgdtre ertdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvghtfiho rhhkqdhhvghrvghtihgtshdrtghomheqnecuggftrfgrthhtvghrnhepveefteduieegtd elvddvtddufeejjeffvdefteejieeulefgtdfggedtffektedunecukfhppedutdekrddv vddurddukedtrdduheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehmohhorhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtghomh
X-ME-Proxy: <xmx:7VxGYDXkBnmPXrtjZeikou7gToVMPWLvrFq3nTfAkXsyLWaYExVN5Q> <xmx:7VxGYLg0tlSULMd0kVzZa46pB7LyaMYoIANV8rbmC8nOOkJV3NHA_g> <xmx:7VxGYLCG1So6L53PHYuFE7zYuTUXVRtYE18p-_-rOzbvQWoyO_udMg> <xmx:7VxGYPxyduClZBlwXem2mafhyIoktz1x6GtdxquQCOaFdjSzHZ9O8g>
Received: from [192.168.1.90] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id 1A3B71080054 for <ietf@ietf.org>; Mon, 8 Mar 2021 12:20:45 -0500 (EST)
Subject: Re: IETF LLC & IETF Participation from USA-sanctioned countries
To: ietf@ietf.org
References: <4619acc8-1ed4-52e8-849b-bfda9de61bb0@gont.com.ar> <20210303221433.ufsitioimata4dtg@crankycanuck.ca> <4739AA0B-95BA-48C8-A17D-730EAF547F55@gmail.com> <20210304155203.n5cfd3kmu2fpgdrt@crankycanuck.ca> <4FCD1F07-6DE9-402F-AFD3-A3C42F3D0ACF@cisco.com> <5a221b8f-73d8-037d-9b4f-f51a9c54e3bd@network-heretics.com> <20210304195744.jbgzpjlegbogmxu4@crankycanuck.ca> <dc91126f-59e8-e2f0-213c-e622b8ea0aa5@network-heretics.com> <25E6DFA6-C70D-4094-AC8C-19E0DBD46AEE@cisco.com> <54fd914c-a95c-2cef-658a-1bcd5e9e47a6@network-heretics.com> <eaf1cf64-83bb-88f4-5673-de73d5038ded@si6networks.com> <31743.1615133499@localhost> <7f457f48-197e-1c01-674e-1701a029e115@network-heretics.com> <110df203-044b-aba9-00a3-e34a06162754@huitema.net> <2c31ee39-e0b4-f397-5e80-bd63a1667a03@si6networks.com> <8248F239-A4E6-4165-95EF-AA77BEF10EC6@gmail.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <34adceee-674b-b504-297b-1dd9a87de81d@network-heretics.com>
Date: Mon, 08 Mar 2021 12:20:44 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <8248F239-A4E6-4165-95EF-AA77BEF10EC6@gmail.com>
Content-Type: multipart/alternative; boundary="------------ABE76E26AB6A36ABE6388590"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DmV6xVUHbHA3k-GZhn6gqoItUcA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2021 17:21:05 -0000

On 3/8/21 10:05 AM, Bob Hinden wrote:

>> FWIW, at the very least, I was wondering what would be the effect of things for folks that openly and truthfully employ email addresses from e.g. ccTLDs from said countries, or that indicate a postal address from one of said countries when registering to an IETF meeting.
> I note that filtering by ccTLD wouldn’t work very well, as a ccTLD only says where the domain was registered, not where the user is.  For example, I checked and I could register hinden.ir.

For that matter, I'm pretty sure that anyone in the DPRK (just to pick 
one example) who is authorized by that government to access and/or 
participate in IETF discussions, will have the resources needed to evade 
whatever mechanisms IETF might impose to discourage that.

Heck, IETF even lets Americans participate.   Might as well let all the 
riff raff in.

Keith

v2.23.0 | Report a Bug | By Email