IETF Logo Mail Archive

Re: a brief pondering

Carsten Bormann <cabo@tzi.org> Sun, 22 March 2020 13:51 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68E823A0805 for <ietf@ietfa.amsl.com>; Sun, 22 Mar 2020 06:51:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 JOWPUqe1d3G7 for <ietf@ietfa.amsl.com>; Sun, 22 Mar 2020 06:51:12 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3FF83A0800 for <IETF@ietf.org>; Sun, 22 Mar 2020 06:51:11 -0700 (PDT)
Received: from [192.168.217.147] (p548DCD70.dip0.t-ipconnect.de [84.141.205.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 48lf6x6tdyzyyH; Sun, 22 Mar 2020 14:51:05 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
Subject: Re: a brief pondering
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <26B25A87-5820-462D-8279-8C82EC44EB16@lurchi.franken.de>
Date: Sun, 22 Mar 2020 14:51:05 +0100
Cc: "Livingood, Jason" <Jason_Livingood@comcast.com>, ietf <IETF@ietf.org>, Eliot Lear <lear@lear.ch>
X-Mao-Original-Outgoing-Id: 606577865.362761-6c58a6abeaf37f6855580fb064c430e3
Content-Transfer-Encoding: quoted-printable
Message-Id: <2DE1D3E9-EE59-479B-8624-29749E7F02D3@tzi.org>
References: <fd6b7ee2-cdbe-14a1-0087-ce61282b22f6@lear.ch> <29D0DCA7-1D72-428F-A6DD-05511D90C039@cable.comcast.com> <31A798F0-9DE0-4231-A768-76BA9A1A2180@tzi.org> <26B25A87-5820-462D-8279-8C82EC44EB16@lurchi.franken.de>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
X-Mailer: Apple Mail (2.3608.60.0.2.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UJgC1vNq7qigvmW75grrM8CmoWI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Mar 2020 13:51:15 -0000

On 2020-03-22, at 11:21, Michael Tuexen <Michael.Tuexen@lurchi.franken.de> wrote:
> 
>> The one thing that would be most useful for me right now would be a document with operational considerations for keeping WebRTC running (e.g., How not to mess it up with your firewall).
> Would that be another candidate for C238?

Not sure that it needs to get stuck there, but yes, it might be a useful part of that suite of documents.  A lot of people here have been in the trenches long enough that they know deeply what breaks WebRTC in a firewall, and it would be a useful operational-area exercise to extract that knowledge and make it presentable (and RFP-referenceable!) to firewall builders and maintainers.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email