Re: [admin-discuss] IETF Administration LLC 2024 Draft Budget

Jay Daley <exec-director@ietf.org> Thu, 07 December 2023 12:40 UTC

Return-Path: <jay@staff.ietf.org>
X-Original-To: admin-discuss@ietfa.amsl.com
Delivered-To: admin-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACE79C14F60B for <admin-discuss@ietfa.amsl.com>; Thu, 7 Dec 2023 04:40:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.905
X-Spam-Level:
X-Spam-Status: No, score=-6.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=staff-ietf-org.20230601.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a7LrObKWylHi for <admin-discuss@ietfa.amsl.com>; Thu, 7 Dec 2023 04:40:37 -0800 (PST)
Received: from mail-wm1-x32f.google.com (mail-wm1-x32f.google.com [IPv6:2a00:1450:4864:20::32f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CAD3C14F60A for <admin-discuss@ietf.org>; Thu, 7 Dec 2023 04:40:37 -0800 (PST)
Received: by mail-wm1-x32f.google.com with SMTP id 5b1f17b1804b1-40b27726369so10003095e9.0 for <admin-discuss@ietf.org>; Thu, 07 Dec 2023 04:40:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20230601.gappssmtp.com; s=20230601; t=1701952836; x=1702557636; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=8HmhFHwor3y0mB6YqfGRxWX7VURopbReBl5RC8uRfXw=; b=oSIVhVYu9bNuXT6fKEVlxwoyu+/SCzrjbLXbPKVUhAQd+As9aFh4OvSkQpfz3DrQN3 crV0uOs2DveKPkST2gQZmYHvnaOwSCqbCmZdp3tazNJnBEf1P3krGazEZOAzRXaXeHJZ fC/GWQaa3Vr1447iIcSTwg7bLaL6aEN3pSTBRhuQW8q75LuE3TnJqZ+ysUOM74VRl0V7 JadJqiEyieSLTm/Z3AqIkbgcqhr3FT6O75arQqHwnkKrxpzLQqBM2nT/aTfyR+/cC1yr +F1hsunUk953K+gGoBOaLVc0461TBza63rc5LgnlNMr5ACr6NEncZwrD7wSKopYCI0hc cy0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701952836; x=1702557636; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=8HmhFHwor3y0mB6YqfGRxWX7VURopbReBl5RC8uRfXw=; b=wlaAs3FbtWBBHwM93urBCPOa/oGxSS0N6K3gEzS9F6PrK0HnPe5zWyqKpoR+cv3nDA 14aBiTGCxnSsscNRr4m9JD3socVq0mILKjQZUxZK/j8xcrVRlPAFwRJ+LznWPF3Uv3R4 LIwO3A6q0zEm/HGq0wi0ZO4y8bU+4Fnqh7ta9D5mGcKSPf3p1v0Eu7fak7JPmCqt5ONC Q4zczLJH5BBzxURDodWFT4yTF2M86PkR+5uIujFmjwkd4hjkA0B/K4uGiZINlE6tPNUf O81C8x4kPfaT3cRmbm5gdImEaM06GVYN9oOAkvQPDXqMzEI9QN9BNPk90rRRGjSHoXdT InGg==
X-Gm-Message-State: AOJu0Yz82RxxhYjN9HDn4g6U17A+naMkcflSpRKiuHwecOvpaLECTppJ 73ahV0rP6l2J1rw77KwtxeyEqjZT
X-Google-Smtp-Source: AGHT+IF+/XIRwZVSe+L13qM/j5ayN+gYL8MQrO+PuAjgf7Fto8bIQgDdUEuoVk92HU3JTz6moUcsLw==
X-Received: by 2002:a05:600c:378c:b0:40c:2b99:a4c3 with SMTP id o12-20020a05600c378c00b0040c2b99a4c3mr411986wmr.146.1701952835841; Thu, 07 Dec 2023 04:40:35 -0800 (PST)
Received: from smtpclient.apple (host-92-27-125-209.static.as13285.net. [92.27.125.209]) by smtp.gmail.com with ESMTPSA id r20-20020a05600c35d400b0040b538047b4sm1897874wmq.3.2023.12.07.04.40.35 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Dec 2023 04:40:35 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\))
From: Jay Daley <exec-director@ietf.org>
In-Reply-To: <CADnDZ88+_XK2JWNXBrN0yTSpnyq-fRTsmxcXFEJWN+J5RrJ3UA@mail.gmail.com>
Date: Thu, 07 Dec 2023 12:40:24 +0000
Cc: admin-discuss@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <13B71C16-E621-44BF-B70B-7BC1B64DAFD9@ietf.org>
References: <2B935668-2840-4E34-8DF5-6BA663EC020B@ietf.org> <CADnDZ88+_XK2JWNXBrN0yTSpnyq-fRTsmxcXFEJWN+J5RrJ3UA@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.3774.200.91.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/admin-discuss/pfT02csSZoGOfc14zjcIIZfQo3Y>
Subject: Re: [admin-discuss] IETF Administration LLC 2024 Draft Budget
X-BeenThere: admin-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussion list for IETF LLC administrative issues <admin-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/admin-discuss>, <mailto:admin-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/admin-discuss/>
List-Post: <mailto:admin-discuss@ietf.org>
List-Help: <mailto:admin-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/admin-discuss>, <mailto:admin-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Dec 2023 12:40:42 -0000

Hi Abdussalam

Thank you for your comments, some responses inline below:

> On 6 Dec 2023, at 21:37, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
> 
> Thanks for this draft and I don't say I am familiar with all of it, but I know that you done a big effort for all the best of LLC and I hope this feedback can help me and all of us for better understanding or better future IETF.
> 
> Two questions and one comment or suggestion and some reasoning below,
> 
> 1)  I am not sure why we have this capitalization adjustment of USD 1,015,942, why is it reducing our net income lower than the previous year? are we buying some tools that are an asset for the LLC IETF.

US accounting rules (as with most countries) specify what work should be capitalised and software development is broadly covered in that (there is a lot of detail I am skipping over).  We are following those rules.

> 2) Staff cost of tools, is getting increased very high within the budget but not understood why, or what is really meant by (migrating IT Infrastructure,,,,) ?

Yes we are investing very heavily in tools in order to bring them up to the standard needed.  The IT infrastructure migration is a new project for 2023/2024 that follows on from a new infrastructure strategy that was thoroughly discussed on the tools-discuss list.  The latest update on this project was the other day:

	https://mailarchive.ietf.org/arch/msg/tools-discuss/jrM7qJhvPQHUgX1LGbWgHBBI2qU/

> 
> 3)  Also I expect that the tools 2024_budget_draft to be around USD 1,377,000 but shows in table as USD 1,577,962 (why increase to be higher than 200,000)

I do not understand that comment, can you please explain more?

> and better close to the community leadership budget, so it will be more important to increase support for commun_leadership than to increase tools by USD 475,000. I suggest that the increase to be splitted between them both so becoming as follows:
> 
> community leadership: USD 1,102,829
> tools: USD 1,377,962
> 
> Reasons:
> 1) The increase in leadership within budget draft goes only to the secretary but the higher level is same, so it is needed to be increased as well, the increase only is about USD 100,000 and goes only to the secretary.

Our budget, like all good budgets, is built from a bottom-up analysis of our needs and historic spending.  For the last couple of years, the community leadership portion has been underspent and so no increase is needed in most of the line items.  The cost increase for the Secretariat is due to a cost increase in the contract. 

> 2) any big/small/medium increase in budget needs to have a supported goal/transformation for LLC IETF, so I was not able to see that while checking the budget. However, it is important that increases in all table fields need to reasonable for the purpose and for all bodies to work more efficient, but if no increase in support that can mean that there were no need for increase related to information that is not understood by the reader but understood by the writer of budget.

I agree.  When constructing a budget and a strategic plan, there is a trade-off between how much detail to put into linking it to strategy and how much flexibility is needed to respond to uncertain or changing circumstances.  

> 3) The non-meeting revenue was decreased so that we should not increase staff cost and should not increase operation cost.

We are not a commercial organisation with a very direct linkage between income and staffing.  We are a much longer-term focused public charity with a mission and that means we sometimes need to invest counter-cyclically.

> Furthermore, the meeting revenue value has increased so it is most better not to reduce meeting expenses average (2024 does have less average meeting expenses than 2023).

I don’t understand - overall meetings expenses have risen slightly.

> 4) The meeting expenses within Vancouver IETF120 shows USD 1,487,893, which it is high by looking into the city way of life or by looking into F&B which looks higher than the other F&B of meeting IETF119 and IETF121.

IETF 120 Vancouver was booked some year ago and rescheduled due to COVID and so benefits from a lower cost than can currently be achieved as venues aim to recoup income lost over the COVID period.  Each venue structures their costs differently, with some such the Vancouver venue, providing the meeting space for free if a certain  F&B spend and room occupancy is agreed to.

kind regards
Jay

> 
> Best Regards
> AB
> 
> 
> On Wed, Dec 6, 2023 at 6:14 PM IETF Executive Director <exec-director@ietf.org> wrote:
> The IETF Administration LLC has prepared its draft budget for 2024:
> 
>         https://www.ietf.org/blog/ietf-administration-llc-2024-draft-budget/
> 
> Community feedback on the budget is welcome and should be made either directly to the IETF Executive Director at exec-director@ietf.org, who can also answer any questions, or to the public list admin-discuss@ietf.org.  Please provide any feedback before December 30th 2023.
> 
> -- 
> Jay Daley
> IETF Executive Director
> exec-director@ietf.org
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
> -- 
> admin-discuss mailing list
> admin-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/admin-discuss

-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org