Re: [Netrqmts] [EXTERNAL] Re: [Inform] Meeting Network Costs

Bob Hinden <bob.hinden@gmail.com> Thu, 20 June 2019 22:14 UTC

Return-Path: <bob.hinden@gmail.com>
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 14E8212014F; Thu, 20 Jun 2019 15:14:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 A-_naEfJHWKK; Thu, 20 Jun 2019 15:14:21 -0700 (PDT)
Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98B3F12022D; Thu, 20 Jun 2019 15:14:21 -0700 (PDT)
Received: by mail-wr1-x432.google.com with SMTP id n4so3369610wrs.3; Thu, 20 Jun 2019 15:14:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=gZLyURcaBAjws3BU5E4yhRuvqql1RT+SHMDkcif4q+w=; b=bCT7Kt9KHGQtBUUCFUk+/TAy+wQeoSmIxvvz1sLuTTZToB6gvdVyPSxZgJ5nUBPE3w tf9i7k0d3zdktysXOIMOx2OClZbieoaWxwoSRZpueZN9mOf1PLp3uPa0lJZWA7oiZCOV 6zbVD1aTrFqQHWs8eePMaDDOmZ5Jl6ejYuUGyBEY5D/P+ttBZVpGHTF+iOsGfEu8fO08 Sao+LbhhT9/KnMzvKUgn3y+J/Y45470ZGB5GKc+fKQxQNMOz5p89BUDXyUiG5bLrpMsV gcGPgGpg5FlgD1fmmXKK72WeCbpIkTZu0nTvehIeoR+3515PyOhRXBBL73gM8x9/x8VS ZVfA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=gZLyURcaBAjws3BU5E4yhRuvqql1RT+SHMDkcif4q+w=; b=GHmuejyxTSDos7DxzNNpp+ys7ZxsL6Eov6X6SK6xoxWLG6d1i/ue6eoh/BNVho0w/x pSI3Ya9B0lH1hgiyLenD4MuYpOE4wdIBkm7jRMgf+3dN6kASJFmKVajaiiywEdfuThch whKT1EQRWlRP9+5DGsqp9WIHsk3zM2se5Z01Sqkld+9STLmtkbpZOklfiHHmsgnzWYTs ZnSsPVs27dCye+b0sV9xaEm27y2bTAZbduTrzlAlDh7HYLbP/Hi5JhwXkVfPh5a6KMUz aWc9EilwCMBRMnojzPoboMAN1xDcWaCSY2zsnd/8pW+87KXw+U4F4ygxIrDx3nqmJVrt fYlg==
X-Gm-Message-State: APjAAAXD/N0BuCQlfyJqQcFBhxln4xintTSztE5dtdxaE5jV3CJtvFRi U9CHMRJylvwL4uGLY2cdpGU=
X-Google-Smtp-Source: APXvYqwxo3ijVfLfm2Am3mJIIwAzB7btR9O51MBTUawLtLF3BFXERZ+c5uZvGiv/tji6+Fp2ScRO5Q==
X-Received: by 2002:adf:dfc4:: with SMTP id q4mr19552021wrn.54.1561068860101; Thu, 20 Jun 2019 15:14:20 -0700 (PDT)
Received: from [10.0.0.199] (c-24-5-53-184.hsd1.ca.comcast.net. [24.5.53.184]) by smtp.gmail.com with ESMTPSA id u13sm530532wrq.62.2019.06.20.15.14.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Jun 2019 15:14:19 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <20797361-7DF1-42A6-A55A-CDA9D604D098@cable.comcast.com>
Date: Thu, 20 Jun 2019 15:14:14 -0700
Cc: Bob Hinden <bob.hinden@gmail.com>, Portia Danley <pwdanley@ietf.org>, "netrqmts@ietf.org" <netrqmts@ietf.org>, Alexa Morris <amorris@amsl.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <259B4AA9-8848-409A-9AC7-11607B637CF4@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> <20797361-7DF1-42A6-A55A-CDA9D604D098@cable.comcast.com>
To: Jason Livingood <Jason_Livingood@comcast.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netrqmts/wDSjG2OBRNhgrkI6aJccMiVCSMw>
Subject: Re: [Netrqmts] [EXTERNAL] Re: [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: Thu, 20 Jun 2019 22:14:24 -0000

Jason,

Seem to me that remote participation is a meeting service just like registration, blue sheets, food, and venues.   The fact that is is provided over the network or the people doing it sit in the NOC is a detail.  

Is this group also looking at evaluating how the IETF does remote participation?  

Bob



> On Jun 20, 2019, at 3:09 PM, Livingood, Jason <Jason_Livingood@comcast.com> wrote:
> 
> Despite the PDF title this is intended to give a sense of costs to bring network tech to support the meetings - as conveyed perhaps by the subject of the email. 
> 
> Regards,
> Jason 
> 
>> On Jun 20, 2019, at 18:03, 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
>>>> 
>>>