Re: [Netrqmts] [Inform] Meeting Network Costs

"Livingood, Jason" <> Fri, 21 June 2019 12:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 16F711200B6 for <>; Fri, 21 Jun 2019 05:56:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id BIRYznjU4aDC for <>; Fri, 21 Jun 2019 05:55:58 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 03C1E12025C for <>; Fri, 21 Jun 2019 05:55:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256;; s=20190412; c=relaxed/simple; q=dns/txt;; t=1561121755; x=2425035355; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=xbWO/ro/t2QmCjEK41+H/kdUiZHBm3A3EFaY3N+Upu8=; b=BQxdQMFNOasVSHvzj6m4hk4yZtG2PAD1B42psAMqR4sGFsE21TITy3XryyPiFyh6 OmgPaPzHKloAO5PW1LCUuUilvWHVA1fPLNcvVyPONL4EGI1H93mN/i/30xznjqjv 06rzXltZ5kiYYDqTc8j1dxogegvkwT0oWiX1GjoWSqKh5jKvxymS7lxhwVVH9Kg5 By4LalNh17gt/LiryXSeFWiFzfItGiX2R838XolL0USwrS0Si0nDGTd1bKU0kfxz 1k546YpIGyKk8B45f6Pl7PbuQrB0EIt+SknAGaK0PeIBoTYie9+uAggr2t4cl8GB RnK1tXyZcbLKMkcPTjIfXA==;
X-AuditID: 60729ed4-f05ff7000000add3-a8-5d0cd3db0a0b
Received: from ( []) (using TLS with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by (SMTP Gateway) with SMTP id B7.3B.44499.BD3DC0D5; Fri, 21 Jun 2019 06:55:55 -0600 (MDT)
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Fri, 21 Jun 2019 08:55:54 -0400
Received: from ([fe80::3aea:a7ff:fe36:8a94]) by ([fe80::3aea:a7ff:fe36:8a94%15]) with mapi id 15.01.1713.006; Fri, 21 Jun 2019 08:55:54 -0400
From: "Livingood, Jason" <>
To: Bob Hinden <>
CC: "" <>, Alexa Morris <>, Portia Danley <>
Thread-Topic: [Netrqmts] Re: [Inform] Meeting Network Costs
Thread-Index: AQHVKDCpWEOqsnpFTEOqWQkUPf2ahQ==
Date: Fri, 21 Jun 2019 12:55:54 +0000
Message-ID: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprFKsWRmVeSWpSXmKPExsWSUDRnsu7tyzyxBt9bLC1+7njFbrH1/T42 i3N/trNa3J3xkNGBxePftO/sHjtn3WX3WLLkJ1MAc1QDo01JRlFqYolLalpqXnGqHZcCBrBJ Sk3LL0p1TSzKqQxKzUlNxK4MpDIlNSezLLVIH6sx+ljNSehiyjjev4W9YI9+xZb3Og2MC/S6 GDk4JARMJHa+S+ti5OIQEjjCJLF03WVmCKeFSWLq3p+sEM5pRonHb6ezdzFycrAJmEncXXiF GcQWEVCVWN7fzw4yiVmgUOLxr3qQsLCAtcSOw1NYIEpsJB5c/soIUiIioCdxoi0VJMwC1Pn0 9TewEl4BF4n1Ha/ApjMKiEl8P7WGCcRmFhCXuPVkPpgtISAgsWTPeWYIW1Ti5eN/rCC2qIC+ xI/tN9kg4nISy37eYYa4RlNi/S59CNNKYk9DCcRERYkp3Q/ZIbYKSpyc+YQFolNc4vCRHawT GMVnIVk8C2HQLIRBs5AMmoVk0AJG1lWMfJZmeoaGJnqGphZ6RoZGmxjBKWbelR2Ml6d7HGIU 4GBU4uFduYcnVog1say4MvcQowQHs5IIL08OUIg3JbGyKrUoP76oNCe1+BCjNAeLkjhvZBF3 rJBAemJJanZqakFqEUyWiYNTqoEx98qnRIvW7El7Vvmd3nDwKvOEv1re+pMsNBfHToyTenpS t8MuuOzbhjteF5/4VtyKWbxCxrNX9VyLj0lb2myuCgPHVx/O7X4jyiCyfjavM+Mx9pJpp+b0 y9vaWsZpeixsOd+hu3Iq/7zpi1o+anOqnl6SUK75yYaPI36V/PpJWz0PJ15q7O1SYinOSDTU Yi4qTgQAdBy6ei0DAAA=
Archived-At: <>
Subject: Re: [Netrqmts] [Inform] Meeting Network Costs
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Meeting Network Requirements <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 21 Jun 2019 12:56:00 -0000

I want to be mindful that we don't stray from the focus on the BoF, which is to explore meeting network requirements. The numbers Portia supplied were intended to give a sense for how much it costs to support a meeting technically, which includes the network itself, the NOC, and the various technical tools involved. 

If you’d like to discuss changes to remote participation, I'm not sure if the BoF is the right place - maybe ask the co-chairs. 


On 6/20/19, 6:14 PM, "Netrqmts on behalf of Bob Hinden" < on behalf of> wrote:

    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?  
    > On Jun 20, 2019, at 3:09 PM, Livingood, Jason <> 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 <> wrote:
    >> Portia,
    >> Thanks for the quick response.
    >> inline
    >>> On Jun 20, 2019, at 2:17 PM, Portia Wenze-Danley <> 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 <> 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 mailing list