Barriers to entry
S Moonesamy <sm+ietf@elandsys.com> Wed, 01 February 2017 11:24 UTC
Return-Path: <sm@elandsys.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 47C63129D1A; Wed, 1 Feb 2017 03:24:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.198
X-Spam-Level:
X-Spam-Status: No, score=-5.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-3.199, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=opendkim.org header.b=yaCyDrRN; dkim=pass (1024-bit key) header.d=elandsys.com header.b=lMIftqIZ
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 xRGAqOQuIMYj; Wed, 1 Feb 2017 03:24:10 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 44372129D18; Wed, 1 Feb 2017 03:24:10 -0800 (PST)
Received: from sm-THINK.elandsys.com (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id v11BO8be005615 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Feb 2017 03:24:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1485948249; x=1486034649; bh=6Vr7EG28xO2tdmcAeFwjiy3dxtJ/asFjGFkfesVRBOE=; h=Date:To:From:Subject:Cc; b=yaCyDrRN6qPUR8CRVVAaPUmiPMQ9S4KYzC55QOnxO8nuTUrMTeEkiYL/JtcaNCk3X ifecnaJ0UbAyvtydy99oZtrdZMLrrLTMNpAFkfvv9DJxFJXxVBnnEXvKHTGHHe6gQ1 AtIS9rT4zNoFuUZOjlxDl/9f5J9I557ECsyvVEpA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1485948249; x=1486034649; i=@elandsys.com; bh=6Vr7EG28xO2tdmcAeFwjiy3dxtJ/asFjGFkfesVRBOE=; h=Date:To:From:Subject:Cc; b=lMIftqIZbxCSGeUa7k6UJ+rG+LGZC9+A/amrNdaq4T+O85QTnh6wMc9MTomByVVBL mRoS43WEujqTB4FXSzbUX36JqI/P68vpu36PT/ssFHZZs7VURzsggpkTw9WGmtrT2E DgIHdnwIpDmOU8BL41vobd3pcshdccOF6ubo5R0w=
Message-Id: <6.2.5.6.2.20170201031607.0c259c28@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 01 Feb 2017 03:22:45 -0800
To: iaoc@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Barriers to entry
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/G8EzHz6xFv2plBc3jO2EuSbWuys>
Cc: 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:24:11 -0000
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
- Barriers to entry S Moonesamy
- Re: Barriers to entry Yoav Nir
- Re: Barriers to entry S Moonesamy