Re: Barriers to entry

Yoav Nir <ynir.ietf@gmail.com> Wed, 01 February 2017 11:57 UTC

Return-Path: <ynir.ietf@gmail.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 451A4129D1D; Wed, 1 Feb 2017 03:57:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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=gmail.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 UK6PCpZfSmFr; Wed, 1 Feb 2017 03:57:39 -0800 (PST)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B275B129400; Wed, 1 Feb 2017 03:57:38 -0800 (PST)
Received: by mail-wm0-x22e.google.com with SMTP id r141so35062765wmg.1; Wed, 01 Feb 2017 03:57:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=UeP0CmDUme0Q2JTUHkLbr4SpuM59uWwvMcU0LhwDT2s=; b=j21kZeLKD3D58Zj7WXAc31HS6bH7upmnKvX93FDaRUNdeQRE/7oznXBKy+foHfAVbR UEa3DzhFKoFCGLT1nuEK7RI/JPYjxSt1lWp6+CoGrFYe9VoWMmSSCh78t/uy5odxJqqV v9JZ+/mRHLY8Frz3s1+ggazEf7eqjIusN54hBYfkqtSwzRlDlka14cz/kHpQutmzAoB1 enB/G1cUEgtE1W6I3j6PKB+gaTTeoRcI+cGErnvjb5EkjHO0IWgUhdjnTYjBcK3Oq+MR Kv8FYV9whVthwfiW6OhP3TkfOLIFrD4c6OhjofRfcAdlfSr784QxLv8ubMCe86OCMEKD H3gg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=UeP0CmDUme0Q2JTUHkLbr4SpuM59uWwvMcU0LhwDT2s=; b=AjCbEHpaSrk7d/CKt3m3JCPGPI4DpWVde8WGjD7TyetyS28AKDesMxkgZu4lWURu4y NPrvVPml2Izm0qW+d51kWu29IGPbT/ysf40ZLSt3OJFeZN1n7QAdMvO+uyrYeeyPuaQQ hj3VsbOMHRENt7K/6rdfNzzT1fzWravxyMovk06kZuBXA8t08tuisKNAKCYFeqvmO1xa 07YAM9aWW58BZvfh/Jz3673mKVtkaJhuOIC0c7DhCbuNehAbwFvvwagjh50qAEexBDyk Abg060IXb7x5UtxYCQcx4eGRLizmSqGjVTWdtYoaSGVJ+NHpgww6usu+9jYUv/o/kZJV xzTw==
X-Gm-Message-State: AIkVDXIIjkry9PH+vqGCXQGTv4D6zqvyATG44gOqL+9JV/A1eDUGw9pQ31/KtKixofOdDg==
X-Received: by 10.28.51.205 with SMTP id z196mr21842038wmz.22.1485950257115; Wed, 01 Feb 2017 03:57:37 -0800 (PST)
Received: from [172.24.250.167] (dyn32-131.checkpoint.com. [194.29.32.131]) by smtp.gmail.com with ESMTPSA id s17sm33694481wrc.6.2017.02.01.03.57.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Feb 2017 03:57:36 -0800 (PST)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <34E7C9A1-83EF-480A-ACC1-B84D2D97D373@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_E559A281-F30E-4E2C-80E0-F5F12255F8BB"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Barriers to entry
Date: Wed, 01 Feb 2017 13:57:19 +0200
In-Reply-To: <6.2.5.6.2.20170201031607.0c259c28@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
References: <6.2.5.6.2.20170201031607.0c259c28@elandnews.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IUAGdrY_T57JCR8ipuHX9EExHLE>
Cc: iaoc@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 01 Feb 2017 11:57:41 -0000

Hi, SM

I’m not sure if this is even up to the IAOC. However, the registration confirmation includes the following:

2. Refunds are subject to a 10% (ten percent) cancellation fee.

3. Cancellations and requests for refunds must be received by 2359 UTC Monday, March 20, 2017. Refund requests will not be honored beyond this point.

So it appears that refunds are available anyway, and what you are requesting is for someone (the IAOC?) to waive the 10% cancellation fee. Correct?

Yoav

> On 1 Feb 2017, at 13:22, S Moonesamy <sm+ietf@elandsys.com> wrote:
> 
> Hello,
> 
> There is a blog article at https://www.ietf.org/blog/2017/01/barriers-to-entry/ about "barriers to entry".  Dave Burstein [1] suggested that the IETF considers refunding the IETF attendance fee for an attendee who is blocked from attending the next IETF meeting due to the barriers to entry.
> 
> Does the IAOC agree to refunding the attendance fee for such cases?
> 
> Regards,
> S. Moonesamy
> 
> 1. https://www.ietf.org/mail-archive/web/ietf/current/msg100934.html