Re: [Netrqmts] [Inform] Meeting Network Costs

Russ Housley <housley@vigilsec.com> Fri, 21 June 2019 13:22 UTC

Return-Path: <housley@vigilsec.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 B85F712026D for <netrqmts@ietfa.amsl.com>; Fri, 21 Jun 2019 06:22:26 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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 OybpVUzCqxeX for <netrqmts@ietfa.amsl.com>; Fri, 21 Jun 2019 06:22:24 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC335120269 for <netrqmts@ietf.org>; Fri, 21 Jun 2019 06:22:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 81B7230065E for <netrqmts@ietf.org>; Fri, 21 Jun 2019 09:03:06 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ytSzkqaeLEIs for <netrqmts@ietf.org>; Fri, 21 Jun 2019 09:03:05 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (unknown [138.88.156.37]) by mail.smeinc.net (Postfix) with ESMTPSA id 1016A3000D7; Fri, 21 Jun 2019 09:03:05 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <B279AF4A-30E8-4955-BFC3-FAF5DBA11160@cable.comcast.com>
Date: Fri, 21 Jun 2019 09:22:21 -0400
Cc: "netrqmts@ietf.org" <netrqmts@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <6D44B2A3-7355-4830-9109-7DEB571B9417@vigilsec.com>
References: <B279AF4A-30E8-4955-BFC3-FAF5DBA11160@cable.comcast.com>
To: Bob Hinden <bob.hinden@gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netrqmts/Tfg0z2rA-cJrHMpGBZZ--aoMPW0>
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 13:22:27 -0000

Bob:

>>    Is this group also looking at evaluating how the IETF does remote participation?  
> 
> 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. 

The on-site network needs to support the video and audio streaming for remote participation.  That means both directions, video and audio out from the meeting rooms to remote participants, and video and audio into the meeting room from remote participants.  What other *network* requirements do you have in mind?

Russ