Re: [Netrqmts] [Inform] Meeting Network Costs

Portia Wenze-Danley <pwdanley@ietf.org> Fri, 21 June 2019 04:16 UTC

Return-Path: <pwdanley@ietf.org>
X-Original-To: netrqmts@ietfa.amsl.com
Delivered-To: netrqmts@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EEA8120026; Thu, 20 Jun 2019 21:16:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 pEJHYHF_Vs1S; Thu, 20 Jun 2019 21:16:44 -0700 (PDT)
Received: from [IPv6:2601:14d:8101:1c3c:2da5:b29e:c8b:e470] (unknown [IPv6:2601:14d:8101:1c3c:2da5:b29e:c8b:e470]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 5E224120018; Thu, 20 Jun 2019 21:16:43 -0700 (PDT)
From: Portia Wenze-Danley <pwdanley@ietf.org>
Message-Id: <C7D9D927-9338-4343-9FCA-DAF12DE897A2@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B80292E5-5321-43B2-8E53-DB30BB33C332"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Fri, 21 Jun 2019 00:16:41 -0400
In-Reply-To: <22F85EB8-B932-480B-8ED4-C828B776FBB5@gmail.com>
Cc: "netrqmts@ietf.org" <netrqmts@ietf.org>, Jason Livingood <Jason_Livingood@comcast.com>, Alexa Morris <amorris@amsl.com>
To: Bob Hinden <bob.hinden@gmail.com>
References: <C7DA2508-6CEB-4FAE-B272-E153EB68D80A@contoso.com> <CC3DBBB0-5577-420B-975D-46A4E2104210@gmail.com> <BC06B950-06A1-4575-BD98-FC4D4C44C6F2@ietf.org> <22F85EB8-B932-480B-8ED4-C828B776FBB5@gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netrqmts/SSJs_Vq9Z4u4AeFqDoyaVoB6NjY>
Subject: Re: [Netrqmts] [Inform] Meeting Network Costs
X-BeenThere: netrqmts@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Meeting Network Requirements <netrqmts.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netrqmts>, <mailto:netrqmts-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netrqmts/>
List-Post: <mailto:netrqmts@ietf.org>
List-Help: <mailto:netrqmts-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netrqmts>, <mailto:netrqmts-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jun 2019 04:16:46 -0000

Thanks Bob.  My goal was to provide a wholistic view of the meeting network costs rather than just the support component; however, I understand and appreciate your understanding as well.

Thanks again.

________________________________
Portia Wenze-Danley
IETF Administration LLC Executive Director (Interim)
(Formerly IETF Administrative Director (IAD)	
Internet Engineering Task Force (IETF)
pwdanley@ietf.org







> On Jun 20, 2019, at 6:03 PM, Bob Hinden <bob.hinden@gmail.com> wrote:
> 
> Portia,
> 
> Thanks for the quick response.
> 
> inline
> 
>> On Jun 20, 2019, at 2:17 PM, Portia Wenze-Danley <pwdanley@ietf.org> wrote:
>> 
>> Hi Bob,
>> 
>> Comments below.
>> ________________________________
>>> 
>>> 
>>> If I understand it correctly, “in kind” means services donated to the IETF.   Is that correct?  If so, it’s not an actual cost.  
>> 
>> 	[pwd] We track “in kind” costs on our budget because although we did not come out of pocket for the expense, we are aware of the costs if a cash outlay is needed.  
> 
> Understood, but relevant to looking at the costs of the network at IETF meetings it is not an actual cost.   It’s accounting.   If we loose these donations of time and circuits, it will turn into real costs.
> 
>>> 
>>> Remote Participation Services are not a direct NOC expense.   It is to provide service to remote IETF participants.  Why is it included here?
>> 
>> 	[pwd] The benefit of Remote Participation Services extends beyond that to remote participants.  Meetecho is an integral part of the NOC as they also record all of the working groups, plenary and related official IETF sessions.  There is a lot that goes into remote participation support including managing the remote queue to raise hands and inject video and audio into the room.  They also monitor the integrated Jabber room.  They work with the NOC as a team.
>>> 
> 
> Let me try again, it’s not part of NOC Support, it’s part of IETF meeting support.   The title of this sheet is “NOC Expenses”.   Even if we were to find a different way provide a network at IETF meetings (for example, use the hotel network), we would still need to provide these meeting services.  It’s not a NOC expense.
> 
> Thanks,
> Bob
> 
> 
> 
> 
> 
>>> 
>>> 
>>>> On Jun 20, 2019, at 1:14 PM, Livingood, Jason <Jason_Livingood@comcast.com> wrote:
>>>> 
>>>> Hi – In preparation for the BoF at IETF-105, I wanted to share what the LLC’s costs look like (from Portia). This isn’t necessarily to suggest a need to make cuts – so please do **NOT** interpret it in that way! Rather, it is to give a sense of what the costs really are for accommodating our requirements; our direct costs. The indirect costs may be thought of as venues that cannot accommodate our requirements (so Alexa may have some sense of that in advance of the BoF).
>>>> 
>>>> Portia is the expert on these costs, and so if you have any questions then she’s the right person to respond.
>>>> 
>>>> Thanks!
>>>> Jason
>>>> <NOC_Expenses_102-104.pdf>-- 
>>>> Netrqmts mailing list
>>>> Netrqmts@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/netrqmts
>>> 
>> 
> 
> -- 
> Netrqmts mailing list
> Netrqmts@ietf.org
> https://www.ietf.org/mailman/listinfo/netrqmts