IETF Logo Mail Archive

Re: Registration details for IETF 108

S Moonesamy <sm+ietf@elandsys.com> Tue, 02 June 2020 19:12 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 C00893A0EC8; Tue, 2 Jun 2020 12:12:35 -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 l0GHOyrJP5BY; Tue, 2 Jun 2020 12:12:32 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 6C8FA3A0887; Tue, 2 Jun 2020 12:12:27 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.82.240]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 052JCBit029597 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Jun 2020 12:12:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1591125143; x=1591211543; i=@elandsys.com; bh=2kQh65d2zSzUeOlQlmLQp0kaeQFbK2P9EB+tsXSfXEE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=oB1P74G/sBsUjzIH0J78fNtQN81kNzNVJXMIYwhesS7osN+YhlF5d8QP1WFsVTNvA KICek2p8H+jHCnkxlepaFkBcvO1MUcL5XEE33fGCHUIpxd9E2LYtyfAF9CMH4NlSpn sG+/Z8ylJD28hz5ayBE5a7SjRSQ9IwDS6M2oI6wM=
Message-Id: <6.2.5.6.2.20200602104420.08043b08@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 02 Jun 2020 12:11:31 -0700
To: Jay Daley <jay@ietf.org>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Registration details for IETF 108
In-Reply-To: <2205116C-CD28-419D-A2C6-4648BFFD68C9@ietf.org>
References: <6.2.5.6.2.20200601195354.098cdfc0@elandnews.com> <2205116C-CD28-419D-A2C6-4648BFFD68C9@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LcR5h5SJaFrER0v5iGst5xq-zeI>
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: Tue, 02 Jun 2020 19:12:36 -0000

Hi Jay,
At 10:55 PM 01-06-2020, Jay Daley wrote:
>We have not closed the March accounts due to the complexities of 
>accounting for the cancelled IETF 107 meeting. For example, we 
>reimbursed flights for a number of contractors who have been trying 
>to claim refunds and we need to show that properly in the 
>accounts.  I hope to have it published this week.

I forgot why I was looking for the monthly statements.  Thanks for 
explaining why the publication was delayed.

>Could you explain the reference to an accounting system? It sounds 
>as if you are suggesting we run the LLC without an accounting system 
>but that would be a disaster so I must have misunderstood.

There is usually some framework between to ensure that the LLC does 
not run into trouble.   It is, in simple terms, to ensure that the 
money is not being abused.  It could also help to lessen your 
workload (that is a guess as I don't have visibility of what you do).

Regards,
S. Moonesamy

v2.23.0 | Report a Bug | By Email