Re: Registration details for IETF 108

S Moonesamy <sm+ietf@elandsys.com> Mon, 01 June 2020 04: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 A4A973A0C86 for <ietf@ietfa.amsl.com>; Sun, 31 May 2020 21:24:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 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, 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 wEZehMI9bA1I for <ietf@ietfa.amsl.com>; Sun, 31 May 2020 21:24:30 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 2CB5F3A0C84 for <ietf@ietf.org>; Sun, 31 May 2020 21:24:30 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.117.216]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 0514OF2E028233 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 31 May 2020 21:24:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1590985468; x=1591071868; i=@elandsys.com; bh=VLVmtr3Us8l6L8baO0Mr+0ou1rVcGRbEGdFErGDJbpw=; h=Date:To:From:Subject:In-Reply-To:References; b=nYCoUnWBlxz6HkBtMWfh+HspepO5QV6y6+JYhJ7QM5SZwtFYBvW7fwR2+w/8drY6W bMiB9pHV6UQZsGp6gaA3v3Z207Ri8Txmtmc9GQ2UA+nf10yf4Us+4QeyF5lbGbIyyC 3/l9V96dGxpaYxYrh5g1Olaza96TieviYAmEBD7E=
Message-Id: <6.2.5.6.2.20200531202152.0ba2cdb0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 31 May 2020 21:12:41 -0700
To: Maja Andjelkovic <mandjelkovic@worldbank.org>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Registration details for IETF 108
In-Reply-To: <1E2FD2FF-6997-4703-AF58-F5AC1163324E@cooperw.in>
References: <159062833754.6110.5826748635235943562@ietfa.amsl.com> <6.2.5.6.2.20200531121457.0b249858@elandnews.com> <1E2FD2FF-6997-4703-AF58-F5AC1163324E@cooperw.in>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/igaCfgVbXlkP842I5pUmwZS8xWA>
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, 01 Jun 2020 04:24:32 -0000

Dear Ms Andjelkovic,

I am contacting you as you are one of the IETF Administration LLC 
Directors.  A year ago, I submitted a short draft [1] to the 
IETF.  One of the issues raised during the discussion of the short 
draft was that there is a risk that remote participants might abuse 
the process.  I am a bit curious about what the IETF Administration 
LLC has done to mitigate that risk, if it exists.  However, that is 
not the reason why I am taking the liberty to contact you.

I came across an announcement about the registration details for IETF 
108.  I was  somewhat surprised to see that a fee will be charged for 
online participation given that:

   (a) it is a change from existing practice;

   (b) there hasn't been any formal discussion about the decision.

I would like to ask you who took the decision to charge a fee for 
online participation for IETF 108.

Regards,
S. Moonesamy

1. https://tools.ietf.org/html/draft-moonesamy-recall-rev-03