Re: [rtcweb] rtcweb@ietf110: agenda posted

Harald Alvestrand <harald@alvestrand.no> Tue, 02 March 2021 09:38 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE9683A147F for <rtcweb@ietfa.amsl.com>; Tue, 2 Mar 2021 01:38:18 -0800 (PST)
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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 o438bFyev9D0 for <rtcweb@ietfa.amsl.com>; Tue, 2 Mar 2021 01:38:16 -0800 (PST)
Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F2DE3A147E for <rtcweb@ietf.org>; Tue, 2 Mar 2021 01:38:16 -0800 (PST)
Received: from [192.168.3.157] (unknown [78.156.11.215]) by mork.alvestrand.no (Postfix) with ESMTPSA id 198427C6872 for <rtcweb@ietf.org>; Tue, 2 Mar 2021 10:38:15 +0100 (CET)
To: rtcweb@ietf.org
References: <3A09060E-C513-4153-B04E-9E9F74BE9370@sn3rd.com>
From: Harald Alvestrand <harald@alvestrand.no>
Message-ID: <c021194d-7324-0648-66fc-7024c4a6a412@alvestrand.no>
Date: Tue, 02 Mar 2021 10:38:14 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <3A09060E-C513-4153-B04E-9E9F74BE9370@sn3rd.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/WXZBGqydKHZnIYSmuCLWR4uRIHY>
Subject: Re: [rtcweb] rtcweb@ietf110: agenda posted
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Mar 2021 09:38:19 -0000

If we want more things to fill up the agenda ("since we're here 
anyway"), I can do 2 slides on NAT Slipstream and why it is a security 
concern for WebRTC that is not addressed in our security considerations RFC.


On 2/24/21 9:32 PM, Sean Turner wrote:
> Hi!  Here’s an agenda for our 2-hour Friday time slot.
> https://datatracker.ietf.org/meeting/110/materials/agenda-110-rtcweb-00
>
> Spt
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb