From nobody Mon Mar 2 08:36:17 2020 Return-Path: X-Original-To: webtransport@ietf.org Delivered-To: webtransport@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CC6103A0AD8; Mon, 2 Mar 2020 08:36:10 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: =?utf-8?q?=C3=89ric_Vyncke_via_Datatracker?= To: "The IESG" Cc: webtrans-chairs@ietf.org, webtransport@ietf.org, webtransport@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.119.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: =?utf-8?q?=C3=89ric_Vyncke?= Message-ID: <158316697081.27324.13930579325368806740@ietfa.amsl.com> Date: Mon, 02 Mar 2020 08:36:10 -0800 Archived-At: Subject: [Webtransport] =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_ch?= =?utf-8?q?arter-ietf-webtrans-00-02=3A_=28with_COMMENT=29?= X-BeenThere: webtransport@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Mar 2020 16:36:11 -0000 Éric Vyncke has entered the following ballot position for charter-ietf-webtrans-00-02: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/charter-ietf-webtrans/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- This looks like an interesting work to be done. Just as non-blocking comments: 1) the milestones are really aggressive (and perhaps unrealistic) 2) when talking about "owners of the WebTransport API" this would be worth adding a reference to those owners. Good luck and fair winds to this potential new WG -éric From nobody Mon Mar 2 11:40:28 2020 Return-Path: X-Original-To: webtransport@ietfa.amsl.com Delivered-To: webtransport@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBC623A0FD9 for ; Mon, 2 Mar 2020 11:40:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 DuMX_utuADiM for ; Mon, 2 Mar 2020 11:40:25 -0800 (PST) Received: from mail-vs1-xe29.google.com (mail-vs1-xe29.google.com [IPv6:2607:f8b0:4864:20::e29]) (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 4FCBF3A0FDD for ; Mon, 2 Mar 2020 11:40:25 -0800 (PST) Received: by mail-vs1-xe29.google.com with SMTP id 7so730863vsr.10 for ; Mon, 02 Mar 2020 11:40:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=E2XlquAMxHFtGw26UmOOMn+nUekLXKaPycTZ/uCHook=; b=mbbWuyE/9MFkBTxj1ClWeirGF6VDi+Ov2jX9yruFW40wVAwrD4dBYalsnY45Dn9qIp vsqQ6OKv9ETqmiv+Bc2CawWFTO4RjSr34PIf2a65l8+WN9wOHIPgFXKvOj4xmpr8nZmP U7bJhZJcZu4z5k0GhqZlzzAhu5Be6uU5vt2QEju6VmDwFOv1M/Yr8fPOtwlluxYsTVte w6jPut/RlpX0O+yET1ZjhErEwwEZX65CkNFzjZzXdIR0IWmlDjUlKKwKp1b4GAP/0Rls 4/SOnq1nLJTn4KA9IcJN3L6U2XNuRNClJNzMmDLlBIwVsDTYlH23yoi54YGj7yfvAYm7 EEWw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=E2XlquAMxHFtGw26UmOOMn+nUekLXKaPycTZ/uCHook=; b=LAbTcN/4jjiddkI6mYSgDddhCRojTTRT4fVmyvYi91UYe2uXK9Ml+rJ95KsZ0pK1B8 9T26TXGNmYvd8p8JWalhC/OVv3fpJZGsEhPU2ORzVsXliot54VM0uZrVy3GKPev0reUk /C1iEOtu8FeMt2E6wxYqzJCHCDPbXKbC4xhXjBvbbm9pI/ZlETxXtSJvKl4z9s4yKb7b 4TDavizYUx4wfdYu+romK+JGWqA7SUQTesbKQmOIt8VDSb4yFY5Wq8KgQ7AOYLDzGZRN CE+WmqxiCVdH/OW0GGgYYzlfupTXuGkGe6uvIDTOF/g3CjoFVmmBv9wI+BTFcD2MQZ1R 2YnQ== X-Gm-Message-State: ANhLgQ05W2U29rKORDdt25ZCbRluiQ5rEfC7RRPGAEXrYxkMmdrLr1DM HK0IftCaVSFCZAM6K7kwP+FmLw9b2W6/dSmIzPN3wHjh X-Google-Smtp-Source: ADFU+vs2KDRXjuUvjkBf8tux3Xs6/kk6HngJBj0b7LQgrt+UIQuE9AUakiQlKafz78O+qy6zSg7aQnoepN1JmqyrQvY= X-Received: by 2002:a67:eb09:: with SMTP id a9mr341724vso.32.1583178023040; Mon, 02 Mar 2020 11:40:23 -0800 (PST) MIME-Version: 1.0 From: Bernard Aboba Date: Mon, 2 Mar 2020 11:40:11 -0800 Message-ID: To: webtransport@ietf.org Content-Type: multipart/alternative; boundary="000000000000adfc47059fe45b58" Archived-At: Subject: [Webtransport] IETF 107 WEBTRANS Meeting (and Agenda) X-BeenThere: webtransport@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Mar 2020 19:40:27 -0000 --000000000000adfc47059fe45b58 Content-Type: text/plain; charset="UTF-8" WEBTRANS will be meeting at IETF 107 on Monday, March 23, 2020 from 13:30 - 15:30 Pacific Time as noted here: https://datatracker.ietf.org/meeting/107/agenda If would like agenda time, please email webtrans-chairs@ietf.org. If you can't make it to the meeting in person but would like to attend remotely, please fill out the form here: https://www.ietf.org/registration/ietf107/remotereg.py --000000000000adfc47059fe45b58 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
WEBTRANS will be meeting at IETF 107 on Monday, March 23, = 2020 from 13:30 - 15:30 Pacific Time as noted here:=C2=A0
https://datatracker.ietf.org= /meeting/107/agenda

If would like agenda time, p= lease email webtrans-chairs@iet= f.org.=C2=A0

If you can't make it to the m= eeting in person but would like to attend remotely, please fill out the for= m here:=C2=A0




<= /div>
--000000000000adfc47059fe45b58-- From nobody Mon Mar 2 12:11:11 2020 Return-Path: X-Original-To: webtransport@ietfa.amsl.com Delivered-To: webtransport@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B06DF3A1088 for ; Mon, 2 Mar 2020 12:11:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 0PtLYyd-6Pwd for ; Mon, 2 Mar 2020 12:11:07 -0800 (PST) Received: from mail-ua1-x92c.google.com (mail-ua1-x92c.google.com [IPv6:2607:f8b0:4864:20::92c]) (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 A4FB93A1080 for ; Mon, 2 Mar 2020 12:11:07 -0800 (PST) Received: by mail-ua1-x92c.google.com with SMTP id t20so199499uao.7 for ; Mon, 02 Mar 2020 12:11:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=6j7l7mPDfSmyeaEJt6vPhmJsHvSlkx/fAqmkkALFHYE=; b=VRcQDHIYFtyNe3Jtd12sKjz8WSHo/DgC8qqNXyVzYBpJnMuyNoO4z2PGc7NiCRf3sm WVba74pgpMfCJszHSaJAMMwHAeaCnRAarhaaoATSb5TDITnSzqZQ1ySQCEakSHcqokOm Ixyq8eDnUJ7HWjJSvDams7nP7ozBhViqsYs5/qQCcRnMN+wfoQNlX9ZcJwtKEipLwHJD 3uLBEcITDH1qTb/QnaYRDPydkMHfE4+1hptPWscMd2hWazf3XfsM7adIixDUzsN1Qnxg mP27BSMdlMku6qbJuOCJADDmGkWsR5jyjv9PX9hHZ4IHa/h3UO8AAMsS2Gkzjeog53I2 NVuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=6j7l7mPDfSmyeaEJt6vPhmJsHvSlkx/fAqmkkALFHYE=; b=iXXyuduUsJ63l56aXDYB+HJhPlRymqppJMpBHKOYQgHjzAHm1bKQEmmf6lSYp1rRWL X/aQh/ovTo4Kgb9e9Qrzcm+6ZDmYqNZbabYotKwJzl4E495aZcY9pVM58IQ3AHvj+PF4 0L2D0NT6AQ6/3kBFUeSBedAI1NnoxkpL97f5XHMRPljrZIXNpB+hDvjF1rsY/KG0fHHC FPaTWdIiStQJpUDCPo/NLzLF74rWXSE3/NWE6//iq7VGm3g7SPA6eJMmJso20QBlMj2a YJr8dBTW5xTO6rMnX2rHKQILrSyOmLrWPBweUzw64/m1Wm8idaf9c9pLnNYLkNe19Ms8 z+dw== X-Gm-Message-State: ANhLgQ2v/UjwnbVan0yBrVeMKBiPpfGcjpZryLQvmkOL+mkfV7xJ2FP+ pVS9zVVJq1ZGLK7wDlTKp//sX/wrkT672URImf5rqdcj X-Google-Smtp-Source: ADFU+vteUqPpuefQcmiJQDHL+lXIRsv+DfsKoTRZllhcAoWlozsrKKJ+4vIZBSzqzfdrnmONW9lpfuEJsZZkcqToumI= X-Received: by 2002:ab0:2408:: with SMTP id f8mr831051uan.126.1583179866129; Mon, 02 Mar 2020 12:11:06 -0800 (PST) MIME-Version: 1.0 From: Bernard Aboba Date: Mon, 2 Mar 2020 12:10:54 -0800 Message-ID: To: webtransport@ietf.org Content-Type: multipart/alternative; boundary="000000000000894b20059fe4c975" Archived-At: Subject: [Webtransport] Reminder: IETF 107 Draft Submission Deadline: March 9, 2020 X-BeenThere: webtransport@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Mar 2020 20:11:10 -0000 --000000000000894b20059fe4c975 Content-Type: text/plain; charset="UTF-8" Just a reminder that the Draft Submission Deadline for IETF 107 is March 9, 2020 by UTC 23:59: https://datatracker.ietf.org/meeting/107/important-dates/ --000000000000894b20059fe4c975 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Just a reminder that the Draft Submission Deadline for IET= F 107 is March 9, 2020 by UTC 23:59:=C2=A0
--000000000000894b20059fe4c975-- From nobody Thu Mar 5 03:31:58 2020 Return-Path: X-Original-To: webtransport@ietf.org Delivered-To: webtransport@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AD0E3A0C76; Thu, 5 Mar 2020 03:31:56 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: =?utf-8?q?Mirja_K=C3=BChlewind_via_Datatracker?= To: "The IESG" Cc: webtrans-chairs@ietf.org, webtransport@ietf.org, webtransport@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.119.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: =?utf-8?q?Mirja_K=C3=BChlewind?= Message-ID: <158340791647.14611.13254437028498026001@ietfa.amsl.com> Date: Thu, 05 Mar 2020 03:31:56 -0800 Archived-At: Subject: [Webtransport] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_o?= =?utf-8?q?n_charter-ietf-webtrans-00-02=3A_=28with_COMMENT=29?= X-BeenThere: webtransport@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Mar 2020 11:31:57 -0000 Mirja Kühlewind has entered the following ballot position for charter-ietf-webtrans-00-02: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/charter-ietf-webtrans/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I agree with Ben that it would seem appropriate to mention HTTP somewhere in the charter. I'm also a bit worried that this work is so closely coupled to the work on the WebTransport API of another SoD that is further still in an unclear state. But I also don't have a good solution to that. Probably correct to start with requirement in this case... I would like to see the relationship of this new group to taps clarified in the charter! From nobody Thu Mar 5 05:56:42 2020 Return-Path: X-Original-To: webtransport@ietfa.amsl.com Delivered-To: webtransport@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FB883A1513; Thu, 5 Mar 2020 05:56:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.399 X-Spam-Level: X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 x8uPEBrqcYMM; Thu, 5 Mar 2020 05:56:35 -0800 (PST) Received: from mail-il1-f180.google.com (mail-il1-f180.google.com [209.85.166.180]) (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 72ECD3A1510; Thu, 5 Mar 2020 05:56:35 -0800 (PST) Received: by mail-il1-f180.google.com with SMTP id g126so5088915ilh.2; Thu, 05 Mar 2020 05:56:35 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GCotGDeXXovdTGZDFmzv+YHRgZ9F4Jr30DwrvYMYXjg=; b=BzSYcvi7O8+0oYcvOWMp/BRKQ0/5q27GnuAsTkALyMFNVi1rWXNrmEBoB8zpJaD361 WWAlr83OWCh5FSUKevvkhxKRv0XHkLhek1OZAxWREH2B8nr+dkLA4HXTfo3gsa9i6hww nk8r5qGzBBp7scjTp6IKruMtUpiUf8doqhx1mGyUgGcjBHRZtT7s9xeTQAIEGTtVzrKw yh7m7gzQlsW+0L+dePxPrEukdRxcuJr8OmvblWRR2i6iW7oZqymvmD2wYZuovbJ+KfpF jjUWdYznELo4egjy0S89w+j71o/AfUQm+0WVB5Rs6dnZxH07QUxtKvEBrBy5RksJw16Q Vnxw== X-Gm-Message-State: ANhLgQ3Cb+i/5ffSo5VgrpTvIPx9FQrU7OcYZpc9G5PntOZY7FMqZfsF esKniTFPBWk7Tu9yH5yEx/+aRxIOFY+v5QDwSQKWXQ== X-Google-Smtp-Source: ADFU+vuf+RiGRohUmQ8U/gQdK+8lxiAhnBbdj5kJk5VTooyX8rF7zKh98Yl89xpr8+A75ftPP3eY9paqqPzCAokx04U= X-Received: by 2002:a92:8f4b:: with SMTP id j72mr7841767ild.17.1583416594593; Thu, 05 Mar 2020 05:56:34 -0800 (PST) MIME-Version: 1.0 References: <158340791647.14611.13254437028498026001@ietfa.amsl.com> In-Reply-To: <158340791647.14611.13254437028498026001@ietfa.amsl.com> From: Barry Leiba Date: Thu, 5 Mar 2020 08:56:22 -0500 Message-ID: To: =?UTF-8?Q?Mirja_K=C3=BChlewind?= Cc: The IESG , webtrans-chairs@ietf.org, WebTransport Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Webtransport] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_o?= =?utf-8?q?n_charter-ietf-webtrans-00-02=3A_=28with_COMMENT=29?= X-BeenThere: webtransport@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Mar 2020 13:56:37 -0000 > I agree with Ben that it would seem appropriate to mention HTTP somewhere in > the charter. The charter talks about "web" and explicitly mentions connecting to HTTPbis. What more is important here? Please suggest text. > I would like to see the relationship of this new group to taps clarified in the > charter! Please suggest text. Barry From nobody Thu Mar 5 06:25:00 2020 Return-Path: X-Original-To: webtransport@ietfa.amsl.com Delivered-To: webtransport@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89FD33A1565; Thu, 5 Mar 2020 06:24:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.897 X-Spam-Level: X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 idaHVOm9A6rU; Thu, 5 Mar 2020 06:24:53 -0800 (PST) Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (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 519963A1564; Thu, 5 Mar 2020 06:24:53 -0800 (PST) Received: from p200300dee7239a00e984148d77e3bc6d.dip0.t-ipconnect.de ([2003:de:e723:9a00:e984:148d:77e3:bc6d]); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1j9rQh-0006nu-2v; Thu, 05 Mar 2020 15:24:51 +0100 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) From: Mirja Kuehlewind In-Reply-To: Date: Thu, 5 Mar 2020 15:24:50 +0100 Cc: webtrans-chairs@ietf.org, WebTransport , The IESG Content-Transfer-Encoding: quoted-printable Message-Id: <6B97C1D2-9402-4BF3-82D1-2DDCB6040D8D@kuehlewind.net> References: <158340791647.14611.13254437028498026001@ietfa.amsl.com> To: Barry Leiba X-Mailer: Apple Mail (2.3445.104.11) X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1583418293;881726a1; X-HE-SMSGID: 1j9rQh-0006nu-2v Archived-At: Subject: Re: [Webtransport] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_o?= =?utf-8?q?n_charter-ietf-webtrans-00-02=3A_=28with_COMMENT=29?= X-BeenThere: webtransport@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Mar 2020 14:24:55 -0000 Please see inline. > On 5. Mar 2020, at 14:56, Barry Leiba wrote: >=20 >> I agree with Ben that it would seem appropriate to mention HTTP = somewhere in >> the charter. >=20 > The charter talks about "web" and explicitly mentions connecting to > HTTPbis. What more is important here? Please suggest text. >=20 I would have expected more information in the second paragraph. However, = as I would like to see more information to actually understand what the = plan regarding to use or extending HTTP, I can proposed text. >> I would like to see the relationship of this new group to taps = clarified in the >> charter! >=20 > Please suggest text. Same here, I would like to know what the plan/intention/relationship is.=20= Mirja >=20 > Barry >=20 >=20 From nobody Fri Mar 6 09:53:59 2020 Return-Path: X-Original-To: webtransport@ietf.org Delivered-To: webtransport@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B10113A0C2D; Fri, 6 Mar 2020 09:53:48 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: The IESG To: "IETF-Announce" X-Test-IDTracker: no X-IETF-IDTracker: 6.119.0 Auto-Submitted: auto-generated Precedence: bulk Cc: webtrans-chairs@ietf.org, webtransport@ietf.org, The IESG MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-ID: <158351722869.2212.2520155156268920598@ietfa.amsl.com> Date: Fri, 06 Mar 2020 09:53:48 -0800 Archived-At: Subject: [Webtransport] WG Action: Formed WebTransport (webtrans) X-BeenThere: webtransport@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Mar 2020 17:53:49 -0000 A new IETF WG has been formed in the Applications and Real-Time Area. For additional information, please contact the Area Directors or the WG Chairs. WebTransport (webtrans) ----------------------------------------------------------------------- Current status: Proposed WG Chairs: Bernard Aboba David Schinazi Assigned Area Director: Barry Leiba Applications and Real-Time Area Directors: Adam Roach Alexey Melnikov Barry Leiba Mailing list: Address: webtransport@ietf.org To subscribe: https://www.ietf.org/mailman/listinfo/webtransport Archive: https://mailarchive.ietf.org/arch/browse/webtransport/ Group page: https://datatracker.ietf.org/group/webtrans/ Charter: https://datatracker.ietf.org/doc/charter-ietf-webtrans/ Description of Working Group The WebTransport working group will define new client-server protocols or protocol extensions in order to support the development of the WebTransport API https://wicg.github.io/web-transport. The WebTransport working group will define an application-layer protocol or suite of application-layer protocols that support a range of simple communication methods. These must include unreliable messages (that might be limited by the path MTU), reliable messages, and ordered streams of reliable messages. Attention will be paid to the performance of the protocol, with particular attention to the protocol’s overhead and the potential for head-of-line blocking; its ability to be deployed and used reliably under different network conditions; and its ability to integrate into the Web security model. The working group will not define new transport protocols but will instead use existing protocols such as QUIC and TLS/TCP. The group will pay attention to security issues arising from the above scenarios so as to protect against creation of new modes of attack. To assist in the coordination with owners of the WebTransport API, the group will initially develop an overview document containing use cases and requirements in order to clarify the goals of the effort. The requirements will include those arising from the WebTransport API. Feedback will also be solicited at various points along the way in order to ensure the best possible match between the protocol extensions and the needs of the WebTransport API. The group will also coordinate with related working groups within the IETF, such as QUIC and HTTPBIS, as appropriate. In particular, if the working group needs any changes to or extensions of the core protocols, those issues will be raised with the relevant working groups for decisions on how best to handle them. If those decisions result in work in WebTrans, the working group last calls for that work will again be sent to the relevant working groups. The group also needs to coordinate with TAPS, as they are working on related message-based APIs and it's important to make sure there aren't conflicts and/or duplications. Milestones: Mar 2020 - Adopt a WebTransport Overview draft as a WG work item Mar 2020 - Adopt a draft defining a WebTransport protocol as a WG work item Oct 2020 - Issue WG last call of the WebTransport Overview document. Jan 2021 - Issue WG last call on the first WebTransport protocol document From nobody Thu Mar 12 12:37:00 2020 Return-Path: X-Original-To: webtransport@ietfa.amsl.com Delivered-To: webtransport@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9EE73A046E for ; Thu, 12 Mar 2020 12:36:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 XD9R980l7yMf for ; Thu, 12 Mar 2020 12:36:56 -0700 (PDT) Received: from mail-vk1-xa33.google.com (mail-vk1-xa33.google.com [IPv6:2607:f8b0:4864:20::a33]) (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 3C0013A0477 for ; Thu, 12 Mar 2020 12:36:56 -0700 (PDT) Received: by mail-vk1-xa33.google.com with SMTP id b187so1929927vkh.12 for ; Thu, 12 Mar 2020 12:36:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=BLGv9p3hZUw9r23ohGzkl3v4y0iW6UvTk6Okm32Nu88=; b=vD5Pcb36OBoJ4AjBpMYMMo73Rk6NKDMlNxNX1qHS3hwcURU8OcW/sM/YSZNWqvYNPt vZmA+4aDlABkU8/rCOK5/Dt07+NMURjvMXEgOSTNyab3+2K2KfU5e4TYwOrRyJDlOnmC 0Z26GM92g5T0glCC7fu3Ya46H1MMvzL6PL6suFuuf7mEu1GV2yHyPPeKEx8NHJr99HEo fI26PCX5IHH4IWRs782OsInEJCatqgJwPBusetmB3TTkjwaE7zB6FLJrEQjeVFzTB4XK vJDqxf2dF5p+CWoO+3XK3rO7o14PwxrUj2rgeAGc2bSBqjszodbqPloVibQk384pbisN STwg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=BLGv9p3hZUw9r23ohGzkl3v4y0iW6UvTk6Okm32Nu88=; b=bHxCp0KaZPXJ85GaMhpAxZD1g0V1iLnlbEtUqb6LZ6JTrBaZeS1aRCmJQm+0aAoAEg oAtLhEeoZjb6WznZdIVFZn2RCQGN4CRvVV/Kkbnt+8WOjnMsD5eabNokqwTwRJn/oT2S As0T2nMOCSnH+twvaNc839tefyAYtXXM9vS589CpGmHLC5shwoeBnjlkjc2GO70ojGXq jfjk1Qnen1IgkMrzTgeqFN68K/wR/Jw52m13vsZmRMjS1zJlst/AqIwk+lRnENE3n2xM QTjxKuxopWmsob+jyEkuTiVRDw3qIn7ts3LlgkhjLRVRKB79gakJ+KsXRYbN+elxkmCg UDaA== X-Gm-Message-State: ANhLgQ2Y83iu01MskrUkKTvS3fMrMiCQ+t+maVPWEAMKSSlCfa96sM4x ljf8lymYMln0n69W7is0jdugOt41ZqF8PBR52e0xIRGoVns= X-Google-Smtp-Source: ADFU+vtW8PUDgAr92llzX04tpWwp5//OmTO92YXpQC9WyLRmqYhearRYmgCvhXtO7TM6z7UhDAIiRvVHUuKRnmEIrKY= X-Received: by 2002:a1f:2c58:: with SMTP id s85mr6488196vks.93.1584041814514; Thu, 12 Mar 2020 12:36:54 -0700 (PDT) MIME-Version: 1.0 From: Bernard Aboba Date: Thu, 12 Mar 2020 12:36:43 -0700 Message-ID: To: webtransport@ietf.org Content-Type: multipart/alternative; boundary="000000000000a9e17a05a0ad7903" Archived-At: Subject: [Webtransport] WEBTRANS Virtual Meeting on March 27, 2020 X-BeenThere: webtransport@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2020 19:36:59 -0000 --000000000000a9e17a05a0ad7903 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable As you probably know, WEBTRANS will not be meeting at IETF 107 on March 23. Instead, as noted by the IESG in the message below, WEBTRANS WG will have a virtual meeting on Friday, March 27 from 22:10 - 00:10 (UTC). This corresponds to 15:10 - 17:10 Pacific Time. More on meeting parameters will be forthcoming. In the meantime, please send any requests for agenda time to webtrans-chairs@ietf.org. Bernard For the Chairs ________________________________________ From: 107all <107all-bounces@ietf.org> on behalf of The IESG Sent: Thursday, March 12, 2020 11:34 AM To: IETF Announcement List Cc: ietf@ietf.org; 107all@ietf.org; irtf-announce@ietf.org Subject: [EXTERNAL] [107all] IETF 107 Virtual Meeting Agenda We have created a virtual IETF 107 agenda because the in-person meeting was cancelled. This is a detailed email that explains our choices. Please read it to the end. We prioritized the scheduling of BOFs, working groups meeting for the first time, and dispatch-style working groups. Existing working groups should know how to progress their work via email and (virtual) interims, and many of them have a solid basis to do that with participants who have been collaborating together for a long time. But BOFs and new WGs do not have that established working mode and usually benefit from dedicated meeting time for bootstrapping purposes, as well as from a participant base drawn from all IETF areas. Similarly, dispatch-style groups are aiming to dispatch new work that otherwise has not seen much previous discussion. The virtual agenda is as follows, with all times listed in UTC: Monday, March 23 20:00-22:00 TXAUTH 22:10-00:10 DISPATCH Tuesday, March 24 20:00-22:00 ADD, RAW 22:10-00:10 MASQUE Wednesday, March 25 20:00-21:30 WPACK, DRIP 21:40-22:40 GENDISPATCH 22:50-00:30 Plenary Thursday, March 26 20:00-22:00 PRIVACYPASS 22:10-00:10 RIPT Friday, March 27 20:00-22:00 SECDISPATCH 22:10-00:10 WEBTRANS The total meeting block for WG and BOF sessions amounts to: Pacific Time 13:00-17:10 (17:30 on Weds) Eastern Time 16:00-20:10 (20:30 on Weds) Coordinated Universal Time 20:00-00:10 (00:30 on Weds) Central European Time 21:00-01:10 (01:30 on Weds) India Standard Time 01:30-05:40 (06:00 on Weds) China Standard Time 04:00-08:10 (08:30 on Weds) Australian Eastern Standard Time 07:00-11:10 (11:30 on Weds) We will be using Webex for all of these sessions. We will be posting training materials and online resources in an FAQ on the IETF web site next week for those who are unfamiliar with Webex. This agenda, with links to the Webex sessions, will appear in the datatracker shortly. If you plan to attend any of these sessions and you are not already registered for IETF 107, we encourage you to register as a remote participant < https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.iet= f.org%2Fhow%2Fmeetings%2Fregister%2F&data=3D02%7C01%7CBernard.Aboba%40m= icrosoft.com%7C19e12a8347eb4f64579a08d7c6b66547%7C72f988bf86f141af91ab2d7cd= 011db47%7C1%7C0%7C637196359005883721&sdata=3DkQfAgWbmmCw4EekDfNZsflv834= VNP7co5U7L9RhVaEc%3D&reserved=3D0 >. There will not be any other working group meetings, area meetings, or research group meetings scheduled between March 23 and March 27. HotRFC is cancelled. We are not providing virtual replacements for side meetings. The organizers of the Hackathon and the Code Sprint are working on virtual support for those events and they will communicate separately about those. We are aiming to provide a =E2=80=9Challway=E2=80=9D Webex meeting where pa= rticipants can go to test audio and other Webex features and to find others who are attending IETF 107 virtually. The hallway@jabber.ietf.org jabber room will also continue to be available. More information about these will be available on the FAQ page next week. There are many trade-offs involved in scheduling an all-virtual meeting. We will be pleased if the BOFs on the agenda are able to form WGs after this. But if not, the virtual BOF will not count as one attempt against the usual allotment of two attempts to form a WG, given the unusual circumstances. RFC 8713, which specifies the NomCom process, relies heavily on there being three meetings per year known as the first, second, and third meetings, respectively. We consider the virtual IETF 107 to be the first IETF meeting of 2020. We will be seating the new members of the 2020-2021 IESG, IAB, and IETF LLC Board at the virtual plenary. We are considering the implications of the cancelled Vancouver meeting for NomCom volunteer qualification specified in RFC 8713 Section 4.14 and we will be inviting community discussion about that soon. We chose to focus this agenda on the 4.5 hours between 20:00 UTC and 00:30 UTC. Because we anticipate having relatively few participants for the scheduled sessions located in the part of the world between Europe and China, this schedule aims to give the most participants an opportunity to experience =E2=80=9Cnight time=E2=80=9D -- albeit abbreviated -- even if th= ey wish to participate in the meeting multiple days in a row. We consulted with the chairs of the listed sessions when we were crafting this agenda to check if they thought that many of their expected participants would be disadvantaged by the slots chosen. They thought these slots were workable. We are preparing for an increased volume of virtual interim meetings in April and beyond. We will share more information about strategies for avoiding conflicts and ensuring fairness in scheduling of virtual interims next week. Until then, we would like to ask chairs to refrain from scheduling virtual interims. We understand that the agenda above is far from ideal. We know that some people reserved a whole week for IETF work and that week will now appear empty, and we know that working late into the night, working overnight, or getting up very early will be unpleasant or infeasible for some. We understand that when people join meetings from home, other commitments may interfere. We know there are many in our community with novel ideas about how to run virtual meetings, and these should be explored further. With the agenda above, we did the best we could given the rapidly changing conditions. We do not expect any of the decisions we made for this meeting to set a precedent for future meetings. It was very evident to the IESG in the course of developing this agenda that we lack consensus-based community recommendations about how to deal with the inherent difficulties of scheduling virtual meetings given time zone differences. After IETF 107, we will figure out the best way to work with those interested in the community on this topic, perhaps via the manycouches mailing list, GENDISPATCH, a BOF, or other ways. Feel free to send questions and comments to iesg@ietf.org. We may not be able to respond immediately since we are busier than usual at the moment as we prepare for the virtual meeting and the seating of the new IESG members. Regards, The IESG --000000000000a9e17a05a0ad7903 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
As you probably know, WEBTRANS will not be meeting at= IETF 107 on March 23.=C2=A0 Instead, as noted by the IESG in the message b= elow, WEBTRANS WG will have a virtual meeting on Friday, March 27 from 22:1= 0 - 00:10 (UTC).=C2=A0 This corresponds to 15:10 - 17:10 Pacific Time.=C2= =A0

More on meeting parameters will be forthcoming= .=C2=A0 In the meantime, please send any requests for agenda time to webtrans-chairs@ietf.org.=C2=A0

Bernard
For the Chairs
___________________________= _____________
<= span style=3D"color:rgb(50,49,48);font-size:14.6667px">From: 107all <107all-bounces@ietf.org> on = behalf of The IESG <iesg@ietf.org&g= t;
Sent: Thursday, March 12, 2020= 11:34 AM
To: IETF Announcement Li= st
Cc: ietf@ietf.org; 107all@ietf.or= g; irtf-announce@ietf.org=
Subject: [EXTERNAL] [107all] IETF= 107 Virtual Meeting Agenda

We have created a virtual I= ETF 107 agenda because the in-person meeting was cancelled. This is a detai= led email that explains our choices. Please read it to the end.

We prioritized the scheduling of BOFs, working groups meeting for = the first time, and dispatch-style working groups. Existing working groups = should know how to progress their work via email and (virtual) interims, an= d many of them have a solid basis to do that with participants who have bee= n collaborating together for a long time. But BOFs and new WGs do not have = that established working mode and usually benefit from dedicated meeting ti= me for bootstrapping purposes, as well as from a participant base drawn fro= m all IETF areas. Similarly, dispatch-style groups are aiming to dispatch n= ew work that otherwise has not seen much previous discussion.

The virtual agenda is as follows, with all times listed in UTC:

Monday, March 23
2= 0:00-22:00 TXAUTH
22:10-00:10 DISP= ATCH

Tuesday, March 24
20:00-22:00 ADD, RAW
22:= 10-00:10 MASQUE

Wednesday, March 25
20:00-21:30 WPACK, DRIP
21:40-22:40 GENDISPATCH
22:50-00:30 Plenary

Thursday, March 26
20:00-22:00 PRIVACYPASS
22:10-00:10 RIPT

Friday, March 27
20:00-22:00 SECDISPATCH
22:10-00:10 WEBTRANS

The tot= al meeting block for WG and BOF sessions amounts to:

Pa= cific Time=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 13:00-17:10=C2=A0 (17:30 on W= eds)
Eastern Time=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 16:00= -20:10=C2=A0 (20:30 on Weds)
Coord= inated Universal Time=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 20:00-00:10= =C2=A0 (00:30 on Weds)
Central Eur= opean Time=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 21:00-01:1= 0=C2=A0 (01:30 on Weds)
India Stan= dard Time=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= 01:30-05:40=C2=A0 (06:00 on Weds)
China Standard Time=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 = 04:00-08:10=C2=A0 (08:30 on Weds)
= Australian Eastern Standard Time=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 07:00-= 11:10=C2=A0 (11:30 on Weds)

We will be using Webex for = all of these sessions. We will be posting training materials and online res= ources in an FAQ on the IETF web site next week for those who are unfamilia= r with Webex.
<= br style=3D"color:rgb(50,49,48);font-size:14.6667px">This agenda, with links to the Webex sess= ions, will appear in the datatracker shortly. If you plan to attend any of = these sessions and you are not already registered for IETF 107, we encourag= e you to register as a remote participant <https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fww= w.ietf.org%2Fhow%2Fmeetings%2Fregister%2F&amp;data=3D02%7C01%7CBernard.= Aboba%40microsoft.com%7C19e12a8347eb4f64579a08d7c6b66547%7C72f988bf86f141af= 91ab2d7cd011db47%7C1%7C0%7C637196359005883721&amp;sdata=3DkQfAgWbmmCw4E= ekDfNZsflv834VNP7co5U7L9RhVaEc%3D&amp;reserved=3D0>.

There will= not be any other working group meetings, area meetings, or research group = meetings scheduled between March 23 and March 27. HotRFC is cancelled. We a= re not providing virtual replacements for side meetings. The organizers of = the Hackathon and the Code Sprint are working on virtual support for those = events and they will communicate separately about those.

We are aiming to provide a =E2=80=9Challway=E2=80=9D Webex meeting where = participants can go to test audio and other Webex features and to find othe= rs who are attending IETF 107 virtually. The hallway@jabber.ietf.org jabber room will also continue to = be available. More information about these will be available on the FAQ pag= e next week.
There are many trade-offs involved in sche= duling an all-virtual meeting. We will be pleased if the BOFs on the agenda= are able to form WGs after this. But if not, the virtual BOF will not coun= t as one attempt against the usual allotment of two attempts to form a WG, = given the unusual circumstances.

RFC 8713, which specif= ies the NomCom process, relies heavily on there being three meetings per ye= ar known as the first, second, and third meetings, respectively. We conside= r the virtual IETF 107 to be the first IETF meeting of 2020. We will be sea= ting the new members of the 2020-2021 IESG, IAB, and IETF LLC Board at the = virtual plenary. We are considering the implications of the cancelled Vanco= uver meeting for NomCom volunteer qualification specified in RFC 8713 Secti= on 4.14 and we will be inviting community discussion about that soon.

We chose to focus this agenda on the 4.5 hours between 20:00= UTC and 00:30 UTC. Because we anticipate having relatively few participant= s for the scheduled sessions located in the part of the world between Europ= e and China, this schedule aims to give the most participants an opportunit= y to experience =E2=80=9Cnight time=E2=80=9D -- albeit abbreviated -- even = if they wish to participate in the meeting multiple days in a row. We consu= lted with the chairs of the listed sessions when we were crafting this agen= da to check if they thought that many of their expected participants would = be disadvantaged by the slots chosen. They thought these slots were workabl= e.

We are preparing for an increased volume of virtual = interim meetings in April and beyond. We will share more information about = strategies for avoiding conflicts and ensuring fairness in scheduling of vi= rtual interims next week. Until then, we would like to ask chairs to refrai= n from scheduling virtual interims.

= We understand that = the agenda above is far from ideal. We know that some people reserved a who= le week for IETF work and that week will now appear empty, and we know that= working late into the night, working overnight, or getting up very early w= ill be unpleasant or infeasible for some. We understand that when people jo= in meetings from home, other commitments may interfere. We know there are m= any in our community with novel ideas about how to run virtual meetings, an= d these should be explored further. With the agenda above, we did the best = we could given the rapidly changing conditions. We do not expect any of the= decisions we made for this meeting to set a precedent for future meetings.=

It was very evident to the IESG in the course of devel= oping this agenda that we lack consensus-based community recommendations ab= out how to deal with the inherent difficulties of scheduling virtual meetin= gs given time zone differences. After IETF 107, we will figure out the best= way to work with those interested in the community on this topic, perhaps = via the manycouches mailing list, GENDISPATCH, a BOF, or other ways.=

Feel free to send questions and comments to iesg@ietf.org. We may not be able to respond immediatel= y since we are busier than usual at the moment as we prepare for the virtua= l meeting and the seating of the new IESG members.

Rega= rds,
The IESG
--000000000000a9e17a05a0ad7903-- From nobody Fri Mar 13 13:59:48 2020 Return-Path: X-Original-To: webtransport@ietf.org Delivered-To: webtransport@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 602B73A0FE8; Fri, 13 Mar 2020 13:59:09 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Secretariat\"" To: , Cc: webtransport@ietf.org, barryleiba@computer.org X-Test-IDTracker: no X-IETF-IDTracker: 6.121.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <158413314937.3136.5386321002619172321@ietfa.amsl.com> Date: Fri, 13 Mar 2020 13:59:09 -0700 Archived-At: Subject: [Webtransport] webtrans - Requested session has been scheduled for IETF 107 X-BeenThere: webtransport@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2020 20:59:23 -0000 Dear Amy Vezza, The session(s) that you have requested have been scheduled. Below is the scheduled session information followed by the original request. webtrans Session 1 (2:00 requested) Friday, 27 March 2020, Session II 2210-0010 Room Name: Virtual Track 1 size: None --------------------------------------------- iCalendar: https://datatracker.ietf.org/meeting/107/sessions/webtrans.ics Request Information: --------------------------------------------------------- Working Group Name: WebTransport Area Name: Applications and Real-Time Area Session Requester: Amy Vezza Number of Sessions: 1 Length of Session(s): 2 Hours Number of Attendees: 100 Conflicts to Avoid: Technology Overlap: core dnssd httpbis quic taps tls tsvarea avtcore mmusic emu People who must be present: Dr. Bernard D. Aboba Ph.D. Barry Leiba David Schinazi Resources Requested: Special Requests: --------------------------------------------------------- From nobody Fri Mar 20 10:31:51 2020 Return-Path: X-Original-To: webtransport@ietf.org Delivered-To: webtransport@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E1A913A09E5; Fri, 20 Mar 2020 10:31:48 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Agenda To: X-Test-IDTracker: no X-IETF-IDTracker: 6.121.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <158472550888.13582.7609771145307466144@ietfa.amsl.com> Date: Fri, 20 Mar 2020 10:31:48 -0700 Archived-At: Subject: [Webtransport] Virtual IETF 107 Meeting WebEx Invitation: WEBTRANS X-BeenThere: webtransport@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Mar 2020 17:31:49 -0000 WEBTRANS Session at IETF 107 Friday, March 27 22:10-00:10 UTC Join meeting: Meeting number (access code): 642 394 286 Meeting password: 3idGtEPsQ27 IETF 107 Agenda: From nobody Fri Mar 20 13:05:00 2020 Return-Path: X-Original-To: webtransport@ietfa.amsl.com Delivered-To: webtransport@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14B6E3A0DEF for ; Fri, 20 Mar 2020 13:04:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 4TLXiVkM25cU for ; Fri, 20 Mar 2020 13:04:56 -0700 (PDT) Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (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 3CF3B3A0DBB for ; Fri, 20 Mar 2020 13:04:56 -0700 (PDT) Received: by mail-lf1-x135.google.com with SMTP id m15so5561059lfp.2 for ; Fri, 20 Mar 2020 13:04:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=6j0+6M1nvXOs3CEu/5cRjn+3LXaSTqz8TkILhHPxNgE=; b=BJMrIsgtPeAOuNJj592XxIhvo1oyIw1ykk6iqaKnfoF//5Ajry6yHl0ojFTBqIMauN cGwCAk15CfxyKSP6XPP5MyImB1Jlgy2mHyL1J3dgzDSOWqbzDpniR4bn3WarpGWNID+C HvAOvb3SwP6C+Gt/hYBODhCVSmwTEFXpx9BqSGKpZF8BGC+XIWL/fpLtg7zUqfuvKdPe w23dwgl/UjGrV+hz494xTYIanQsEv8lqG1bvBC8H3Ec+vGLyv408XMf+SOZIX2AR6qTc Zob4WIOIssok6snZX/7nuX22F/zkjEv2WY4f/G4K2P9gcwH5MaAfWsWZ2CTa/aZCGNHQ Bwhg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=6j0+6M1nvXOs3CEu/5cRjn+3LXaSTqz8TkILhHPxNgE=; b=Qldbjqf+DVSrqMvfatJPXOVLbUb70zyGHLJsu/L73ULRXTmJprTudOHtGOT7sss6Su SAGe3s0IgzK+lp0KPaEUkYgvhirc1O2T1+4+L5q1nsTH6Ps7APfxjcJNyJHP3uYIhdsN sJQkJ1l+T1RDb14fV8LbG6fLKHMMWllzMSoBV56UFEHxyxapDI2/HC3DKdvZNWcpnStS EjaAg7Rx+LWFw94ifVXo2Sr1ti16/K6RTk05I6JuU1o0Hhf/CcShM5IAKfjcDoRmgsuR YlYo5oPghXuDy6wvsoodFcp1XLE6Ic4FJ95/Vlu7ygVz35T/8uV3cdv5xCQigaFTicws WjIg== X-Gm-Message-State: ANhLgQ3pLnMyZDCii2xPHbbNmp1mTK+K9PD4D8VsI1fBiCB8dekMTy3e noYOuX6JqmcvD3Q2y6XVv+02AuA7jMhdcgj/u0X0AeEm X-Google-Smtp-Source: ADFU+vv6gfmUFgdEx9ggHZFjl2Top/GX/vIRZR346acJYRTL3hSOZ0y7ZCeEVo+YBEjeUiFBnRlWbfQdQyFu2LOcE24= X-Received: by 2002:a19:23d0:: with SMTP id j199mr961198lfj.75.1584734693994; Fri, 20 Mar 2020 13:04:53 -0700 (PDT) MIME-Version: 1.0 From: Bernard Aboba Date: Fri, 20 Mar 2020 13:04:40 -0700 Message-ID: To: webtransport@ietf.org Content-Type: multipart/alternative; boundary="0000000000007fb6a305a14ecc1d" Archived-At: Subject: [Webtransport] Volunteers needed X-BeenThere: webtransport@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Mar 2020 20:04:59 -0000 --0000000000007fb6a305a14ecc1d Content-Type: text/plain; charset="UTF-8" The WEBTRANS WG will have a virtual meeting on Friday, March 27, 2020 from 15:10 - 17:10 PM Pacific Time. Since this virtual meeting will be something of an experiment, we'd like to get volunteers in advance for the following: 1. Jabber Scribe to take questions from the queue for anyone who is unable to use WebEx for voice. 2. Note takers to capture decisions and action items. Please email webtrans-chairs@ietf.org to volunteer. --0000000000007fb6a305a14ecc1d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
The WEBTRANS WG will have a virtual meeting on Friday, Mar= ch 27, 2020 from 15:10 - 17:10 PM Pacific Time.

Since th= is virtual meeting will be something of an experiment, we'd like to get= volunteers in advance for the following:

1. Jabbe= r Scribe to take questions from the queue for anyone who is unable to use W= ebEx for voice.

2. Note takers to capture decision= s and action items.=C2=A0

Please email webtrans-chairs@ietf.org to volunteer.=
--0000000000007fb6a305a14ecc1d-- From nobody Fri Mar 20 13:16:45 2020 Return-Path: X-Original-To: webtransport@ietfa.amsl.com Delivered-To: webtransport@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E8943A0DEB for ; Fri, 20 Mar 2020 13:16:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.087 X-Spam-Level: X-Spam-Status: No, score=-2.087 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=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 VuyhDQ0cKUQi for ; Fri, 20 Mar 2020 13:16:38 -0700 (PDT) Received: from mail-lj1-x234.google.com (mail-lj1-x234.google.com [IPv6:2a00:1450:4864:20::234]) (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 C6F8A3A0DE8 for ; Fri, 20 Mar 2020 13:16:37 -0700 (PDT) Received: by mail-lj1-x234.google.com with SMTP id r24so7868697ljd.4 for ; Fri, 20 Mar 2020 13:16:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=j1hD+gFDyOdLViZay+FvlgqJBnwc+fRkav4BPJT6Fi8=; b=mKkxu/WdI47773ghLWj4EqZqHXAtPJBD+dkv1PeW9TC8+G5upnhHXdJPBkw927HUyr mEz2UXGbZMTSZVb//sGsEOQf51QiXqwPnzIlhzL9OX3daR1aYhwJWqeuSFTCKwuHDZ8+ vZqtUG/8dTsl+PXDE5elKWrln83WZ1TVzvz0aIXE5s35mR/l/jecdZyzpaR3VwnrXucg kzPikZkBbjYbBkWnseUHtOrE0DSXiyt9Pfs+rERFqGY/3nW2rnVKleW+EPzcA9JdEIlu 6QIdGCph9VpnfuIgFbUpJaPj6GkxsKwgQtyoG51AJAB6fhFpOftyo9LE3eSlPRd1+I9g N8NQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=j1hD+gFDyOdLViZay+FvlgqJBnwc+fRkav4BPJT6Fi8=; b=Y9Sn9ESYFCEdvNTRLtJJ7hfZJpXSPCjj1HKrZIlBB+vv7bUfj1r+jO3jPUGJ6eq8/m /CltL902c+ZP/JYIGEf1pZciG3+TmrGc5+JR66jaAuk96V2OR4VXAT3nFomv/uj2cLfw UmnhmZtYBU28ofT9UMjDbQiVOuQBAJIGMKlLTwExzXL8crSJL6rG+qKOifNKt5TtTPhI CMl2qAPTMWmjXO1AqZ9Z9dFmYNNy4+4P3F1ieI2xP22TPQnCXcMOjfXXYAvGjtc8w3VA AkUfCn0/UmWmmjRQEPrB7dZQUoRrnMxz7Fb3sQRTSiz6oahZQu0m3oqQTklFjkzFgHIP OafA== X-Gm-Message-State: ANhLgQ2wnK0Xzq2FYAzm5+VhgCOPlYt/PFGcYlIEIPfly5UO7kfpjQAn Bkr2F/EsFj+3vDTzgkqL7PIWhPX19dx4/WLNtjF7pg+fRLQ= X-Google-Smtp-Source: ADFU+vsDqtOfMZwmze3jeAHqLPJrCswlQOtZTLSqn60eSG7IBM3OzfaPeu+OCsTpib8ad97BWbtSZkYnbSvt74FCBy4= X-Received: by 2002:a2e:a0ce:: with SMTP id f14mr6232839ljm.159.1584735395429; Fri, 20 Mar 2020 13:16:35 -0700 (PDT) MIME-Version: 1.0 From: Bernard Aboba Date: Fri, 20 Mar 2020 13:16:21 -0700 Message-ID: To: webtransport@ietf.org Content-Type: multipart/alternative; boundary="0000000000004ed16505a14ef6b9" Archived-At: Subject: [Webtransport] Draft Agenda for IETF 107 WEBTRANS WG Meeting X-BeenThere: webtransport@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Mar 2020 20:16:43 -0000 --0000000000004ed16505a14ef6b9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Here is a preliminary agenda for the IETF 107 WEBTRANS WG Meeting. If you'd like to propose additional agenda items or modify the time allocations, please send email to webtrans-chairs@ietf.org. If you are listed below as presenting, now would be a good time to work on your slides. The deck is available here: https://docs.google.com/presentation/d/1APFmYij7nyqlmu91R7G61F66pxvWQD5H6UY= 1W-taRjU IETF 107 WEBTRANS WG Agenda Friday, March 27, 2020 15:10 - 17:10 Pacific Time - 15:10 =E2=80=93 15:30 Preliminaries, Chairs (20 minutes) - Note Well - Jabber Scribe - Note Takers - Agenda Bash - 15:30 - 15:50 WebTransport Overview and Requirements, Victor Vasiliev (20 minutes) - https://tools.ietf.org/html/draft-vvv-webtransport-overview - 15:50 - 16:05 WebTransport using HTTP/2, Eric Kinnear (15 minutes) - https://tools.ietf.org/html/draft-kinnear-webtransport-http2 - 16:05 - 16:20 WebTransport over QUIC, Victor Vasiliev (15 minutes) - https://tools.ietf.org/html/draft-vvv-webtransport-quic - 16:20 - 16:35 WebTransport over HTTP/3, Victor Vasiliev (15 minutes) - https://tools.ietf.org/html/draft-vvv-webtransport-http3 - 17:00 - 17:10 Wrap up and Summary, Chairs & ADs (10 minutes) --0000000000004ed16505a14ef6b9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Here is a preliminary agenda for the IETF 107 WEBTRANS WG = Meeting.=C2=A0 If you'd like to propose additional agenda items or modi= fy the time allocations, please send email to webtrans-chairs@ietf.org.=C2=A0

If yo= u are listed below as presenting, now would be a good time to work on your = slides. The deck is available here:=C2=A0
ht= tps://docs.google.com/presentation/d/1APFmYij7nyqlmu91R7G61F66pxvWQD5H6UY1W= -taRjU=C2=A0=C2=A0

IETF 107 WEBTRANS WG Agenda
Friday, March 27, 2020
15:10 - 17:10 Pacific Time
<= div>

--0000000000004ed16505a14ef6b9-- From nobody Thu Mar 26 00:26:28 2020 Return-Path: X-Original-To: webtransport@ietfa.amsl.com Delivered-To: webtransport@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 906823A094B for ; Thu, 26 Mar 2020 00:26:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 IkvSArZ5I1Qz for ; Thu, 26 Mar 2020 00:26:24 -0700 (PDT) Received: from mail-lf1-x12d.google.com (mail-lf1-x12d.google.com [IPv6:2a00:1450:4864:20::12d]) (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 A7C543A0917 for ; Thu, 26 Mar 2020 00:26:24 -0700 (PDT) Received: by mail-lf1-x12d.google.com with SMTP id t21so3917482lfe.9 for ; Thu, 26 Mar 2020 00:26:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=q4lrRtUOGqLBT6/V0VD3IGU6+xQ9rgXp3IeQAJAYImc=; b=nx5OL9/2BO06nlEzFP51m/7VlJ9XHTHwV/CGkrXXp7bGAtDIHwEK0p0mhRj3wpJ7WL vRRnjQqBQvt3ktaKDtJ7NAn0aeYo5FEq909nAktrDFqWTrm03Xmi6IormOGdkcwVSZVl XaDIVF76F8HQFd8tP/U/VGJj7V7cjMEF6WlKqzsxVNwnw2zgqiH4VbV08Hh6jYpMNBqH 6nKJXOCBGhA276xWiRtcw0e47ldzcpY7G+Lr5ysNNH0yRDj6z33E7cPmjBIrtxI9gTX+ /J3miG55XCWv3nBV44iUQPD74109RRqff/GYYGbRdNjBrMdsVFxfswbkKSfE8493+U/Z 9Ivw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=q4lrRtUOGqLBT6/V0VD3IGU6+xQ9rgXp3IeQAJAYImc=; b=g5iExc/CcabwMfcjWW2YCswq90TnADQoZP5cADrioCy0LVRqNB1txv14JheIt8tFKv tKPUOaUqPI1OB7vXkq7KmoqiJXakmQ5MMDK0tl9tPsnEkJtfg2dHua1thF9dI3Ubw539 81BFMn/xPAcyCxNn8zy0nM7dWpjnT8q/0FE5PA1CkWEBt1FVWz4YsBhG0nXih9uUmYCq SvzPDna29cxsByUujV0bE2EsmQiZHnkH31+7Mvn0yDECKSxXJL1u/zQRS02n3W8ITM63 3iIqkbo5BE3R2YgHwvFKegJucSYZjk1Y4X5elifs4BTkCsmI+kvYnjZ/aP1ICGwGNCCa TwWg== X-Gm-Message-State: ANhLgQ2KcgltC65Sx9P1jI5eO36WWEvCVSx7+Q5Ge0Pvj4c1ZWlXM5el 6Mq9CE3QUP9ibBeg9p7lazYW1x2X8YvBy2tm6iFfsgxdO+A= X-Google-Smtp-Source: ADFU+vsZjBpVSPuk2m4abz2NyHQhnvsqyEwPxYZtyA1wLTisanqQE809nJC0qpbx5+Lzqv/w/J0cZEQdB3f5m+tKj5c= X-Received: by 2002:a19:f618:: with SMTP id x24mr4813133lfe.106.1585207582316; Thu, 26 Mar 2020 00:26:22 -0700 (PDT) MIME-Version: 1.0 From: Bernard Aboba Date: Thu, 26 Mar 2020 00:26:11 -0700 Message-ID: To: webtransport@ietf.org Content-Type: multipart/alternative; boundary="000000000000d6dc5905a1bce6f8" Archived-At: Subject: [Webtransport] Request for slides X-BeenThere: webtransport@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Mar 2020 07:26:27 -0000 --000000000000d6dc5905a1bce6f8 Content-Type: text/plain; charset="UTF-8" The IETF 107 meeting of the WEBTRANS WG is tomorrow, March 27, 2020. The agenda is posted here: https://datatracker.ietf.org/meeting/107/materials/agenda-107-webtrans-00 In order to have the slides available and posted to the materials management site, we need to have the presenters provide these ASAP. --000000000000d6dc5905a1bce6f8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
The IETF 107 meeting of the WEBTRANS WG i= s tomorrow, March 27, 2020.=C2=A0

The agenda is posted h= ere:=C2=A0

In order to= have the slides available and posted to the materials management site, we = need to have the presenters provide these ASAP.=C2=A0
--000000000000d6dc5905a1bce6f8-- From nobody Fri Mar 27 13:34:40 2020 Return-Path: X-Original-To: webtransport@ietfa.amsl.com Delivered-To: webtransport@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22F893A0772 for ; Fri, 27 Mar 2020 13:34:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 h6XLRaYEsTIE for ; Fri, 27 Mar 2020 13:34:37 -0700 (PDT) Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (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 676B83A093B for ; Fri, 27 Mar 2020 13:34:37 -0700 (PDT) Received: by mail-lj1-x231.google.com with SMTP id r24so11632523ljd.4 for ; Fri, 27 Mar 2020 13:34:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=2prKYKlEULbipNK2ZE7wH6LM1kjWDxaGg6345ybTFYE=; b=YcOZQ+g1F5iMQ/jZT87qUE7pdT8UR+XikZSocNDnlPozoA3Kj4KKCM0GhCczOaxGrq aYQCvo2Uze273ageFIFxEnWdOcGRKbijskBHSHSkHUkRU6On8KeHxXEeZIpCLWSpFo+V Q2T+W+6icWmEZjQ/8GZ4qszAa2gWRNbxdZX/jff9bR/Ww4U9k0tMeoHxqa/AvZ9dzR6n pWWwdIqBTKlezAj58d1QX/0Z5nnqxsSSHDmiz12ohfDTZVE5M3GrFfo2M2CU6KKhfdB7 ZVcz5T3iNyJ48xkr2Gq1M9Vao7nvLZwYdTZWqAX4lKIo66k7WAy46i+Ui1LvldMKoDXK BOSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=2prKYKlEULbipNK2ZE7wH6LM1kjWDxaGg6345ybTFYE=; b=pY35PkVdYYhW3KqAIxKJNeBiexNMBfK4ZPYELiKpdbZplnh6JdPM6NzLzV7pirNorD P8uzJQQnQv8J9X1SSR7jZWiPMOVsbZwOx/7VQUN3+4psaZRUBRmVRIDdl5XuVc7nLSLQ yxqvWf8bT7a5enRAL1Eb0EWwW60Hq1Qm8iPJEMa7Pxw7ko5hwcZbNC55xa7lpdwpO3Ms KJ58+IVODI6b+Kcogi3HyvJTxrK6XSpeErbPoSv2OFjf9urs1XrqTpkbbwPtjxviXCRS q9abNKWQwJ/TOgqF4cBzp7iFB20PhIt2uRDhnFUFMy/wBhNtDJcacde/Nb8+plI7CuZl gCfA== X-Gm-Message-State: AGi0PuaaL+UuSIf2aAmIVLuaJiOUbc5vmM6gBLpVFMnI30o8krrjtyfi RoCPIcqQPgqvtqnVVCLsIGXipVc4ZgE+y6OThZo9TZYxpzQ= X-Google-Smtp-Source: APiQypKXENV10HTC3ZIRjL5QDnyZIe/uX93vJIy+m4jUYa2GmKfBGJ9bS9EPpgRaUgt435vAxcP9yH2CoSGjRGv6dE8= X-Received: by 2002:a2e:b804:: with SMTP id u4mr420042ljo.159.1585341275011; Fri, 27 Mar 2020 13:34:35 -0700 (PDT) MIME-Version: 1.0 From: Bernard Aboba Date: Fri, 27 Mar 2020 13:34:23 -0700 Message-ID: To: webtransport@ietf.org Content-Type: multipart/alternative; boundary="0000000000008b7d8b05a1dc07b7" Archived-At: Subject: [Webtransport] Agenda and slides for today's meeting X-BeenThere: webtransport@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Mar 2020 20:34:39 -0000 --0000000000008b7d8b05a1dc07b7 Content-Type: text/plain; charset="UTF-8" The agenda for today's meeting is available by clicking on "Meeting Materials" for the WEBTRANS WG entry on the agenda page: https://datatracker.ietf.org/meeting/107/agenda For reasons I'm not clear about, the uploaded slides are not yet visible there, although they do show up here: https://datatracker.ietf.org/meeting/107/session/webtrans In case we don't figure this out in time, you can access the slides here: https://docs.google.com/presentation/d/1APFmYij7nyqlmu91R7G61F66pxvWQD5H6UY1W-taRjU/ Bernard, for the Chairs --0000000000008b7d8b05a1dc07b7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
The agenda for today's meeting is available by clickin= g on "Meeting Materials" for the WEBTRANS WG entry on the agenda = page:=C2=A0

For reasons I'm not clear about, the uploaded slides are not y= et visible there, although they do show up here:=C2=A0

In = case we don't figure this out in time, you can access the slides here:= =C2=A0
<= div>
Bernard, for the Chairs
--0000000000008b7d8b05a1dc07b7-- From nobody Fri Mar 27 18:16:52 2020 Return-Path: X-Original-To: webtransport@ietfa.amsl.com Delivered-To: webtransport@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BC7B3A0C52 for ; Fri, 27 Mar 2020 18:16:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 6U6YG2nZLrjJ for ; Fri, 27 Mar 2020 18:16:49 -0700 (PDT) Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (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 DD63A3A0BF5 for ; Fri, 27 Mar 2020 18:16:48 -0700 (PDT) Received: by mail-lj1-x22d.google.com with SMTP id f20so12174349ljm.0 for ; Fri, 27 Mar 2020 18:16:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=iiG86HnOF+V1+1wJvWhXE9nvoYNEaBdm/pQAc06gDug=; b=ezCjSeDI0VBjcMSnumhpfq+jucw48r0Iu1P0Vppdizn4EL21i2eQmjd7USFro8+6C4 v/BMyAZjIDQZIeDN130gR+B5gDaL2tcJbSZxuR7bCGlbagCiz0nYpLXXdpxw7p26COfx Ae3jKuuwbrVNXtcBOnQL51jvwAo1PipPfmRmr7K/XR8Rquz4M3aNIiv+PWCLa0vUomdo 49GoPTHnDIBbbUlXeSBFoS5sHdj3j2xFowPAexbhpSQofw6ogJSvQcuGGkZZnbC/caDQ 8NmM05vbC7TY1tpIHWFfbcGy8j9cDM81PmfMfJ0qtX9vLGyA86EQAon1U6Av9gIDg3D3 fiMg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=iiG86HnOF+V1+1wJvWhXE9nvoYNEaBdm/pQAc06gDug=; b=oWvDU/3jlgEqCE7jHarM02drTahrGZeKmBBE9DkD9pPY7SUCwdex+TBDpISsK/mZSU 5zQ56vMsESmC91XXgVCqKY7nauIx2id1fSQf93bVK8YO4Z8LZYuCKVnDCkqSsoRrHik+ Ut4wVIxK06bTyrrV6unu4E19DIWEU2bGnuyRonlhghA4BJs14FHdHI0GN1Q7c9B6c8nc jNrzIpiB/NQI9iMjxcWQOUCfadHu96QGSQOE1C10PhbUMcbW6Rx5yhHAJj96l3hNs7/g MqufN2DqSbeStd0OBJb410z7/7BR6DRlH+eg2ag1p6rpyQQL5Nj2yHOw1FIp567ppZxy pOZA== X-Gm-Message-State: AGi0PuYt5VrrTMO5gsAklyTxort44qGzvXZNasWGQQS5Dxs5+HzdFNUh KAQ1BQa04hOeuKgsMMfOUzgiJLj2JN/bzzfj+fjRV78P X-Google-Smtp-Source: APiQypJ/NvLMSDZNeJvnsoGBMDEN6/A6QrrRDyqRMbJFFVGuC1yQlUOH3DzafTjKugwiYQytf7goUeQm0CJPyZsdJ8s= X-Received: by 2002:a2e:82d0:: with SMTP id n16mr955080ljh.174.1585358206735; Fri, 27 Mar 2020 18:16:46 -0700 (PDT) MIME-Version: 1.0 From: David Schinazi Date: Fri, 27 Mar 2020 18:16:35 -0700 Message-ID: To: WebTransport Content-Type: multipart/alternative; boundary="000000000000c1186f05a1dff8ac" Archived-At: Subject: [Webtransport] WEBTRANS Minutes from IETF 107 X-BeenThere: webtransport@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Mar 2020 01:16:51 -0000 --000000000000c1186f05a1dff8ac Content-Type: text/plain; charset="UTF-8" Hi folks, We have posted the minutes of WEBTRANS @ IETF 107 to the datatracker: https://datatracker.ietf.org/doc/minutes-107-webtrans/ Please verify that your statements were correctly recorded, and reply to this message if you see any error. Thanks again to Bron Gondwana and Peter Wu for taking minutes and to Lucas Pardue for Jabber scribing. Cheers, David Schinazi --000000000000c1186f05a1dff8ac Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi folks,

We have posted the minutes of= WEBTRANS @ IETF 107 to the datatracker:

Please verify that = your statements were correctly recorded,
and reply to this messag= e if you see any error.

Thanks again to=C2=A0Bron = Gondwana and Peter Wu for taking minutes
and to Lucas Pardue for = Jabber scribing.

Cheers,
David Schinazi<= /div>
--000000000000c1186f05a1dff8ac-- From nobody Tue Mar 31 17:00:27 2020 Return-Path: X-Original-To: webtransport@ietfa.amsl.com Delivered-To: webtransport@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EB1F3A0DBA for ; Tue, 31 Mar 2020 17:00:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.197 X-Spam-Level: X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 W-39XzZtWp4B for ; Tue, 31 Mar 2020 17:00:23 -0700 (PDT) Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) (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 9FD5B3A0E07 for ; Tue, 31 Mar 2020 17:00:20 -0700 (PDT) Received: by mail-lj1-x229.google.com with SMTP id b1so3333984ljp.3 for ; Tue, 31 Mar 2020 17:00:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=2rPs8DeJj+pw+Jm5yonYiGA8uEEG9p60wq3gha1AQPM=; b=oxvFtC2sFdmEpk1+W/zJpB4R9Vd6hU+X18GGGWvAY1epTMH8sNn/nXnoltXOl27Lsw 126OnXAQn0gcN/2+SdjjGsD8zaavQeK64Tga6kWnqLfeVwM9Ix1Z/h9j9slq//1qvswZ mTWkFosemNtWSL70IRQ4uvR6oRPDa8c+2t1vdrfoGFQ/+UzNj+Z7YHGtP6G7Udsldp4E 3Q6Ja8XEgZ49D3MZNijlmXsbiTtR3I1W7g7PHbsdUw7La6MZMudI4LSSrwKOdNHCdBq2 T9UBcug67nBw8ReNK4WPvi86ji1H3qiKqGypqxpfuOg5XspRA8B3mEB+zs/H0S5elDKH gibQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=2rPs8DeJj+pw+Jm5yonYiGA8uEEG9p60wq3gha1AQPM=; b=EoPeiTDP0pDmAfgXHL1h0E24toLRA6v51+u2Tvrp3KResI8pUBN4HjPdpWcBOAbYXK 1dhnzKuu4kSER/X9ep9WbO9zlVzOy/cp1KCAzw21cbDYIjBmOLDjTQMsGAVMrAGpwaV2 +rOeyuosLbBgV+S+xSpSRk7Ltvep8T4hRlXMk6xEwaIbqPiqm7NK6SE8eHnolWmXWdgZ dVjaUrBGEqoz0NoD26OZZOoQI2jY32mZrIfAgtfSu4Aya3czWhBAuucf312AnIUCCOSD bPV9CR6xxbUFJLtubrMvmSc/PCtxzVVGKD46MUVrHKqghbtrsEMXWSp82sSezgw6mka6 tpnQ== X-Gm-Message-State: AGi0PuZzC6HlxbgFQ6Z4gGdzqpJ5O8gvYSghXGjWUKXRYJ9RpJiNyqva iIjdXXsfC4WoxsYRvfXLj92wdyBU8dXvu7VvS2b+6uJW X-Google-Smtp-Source: APiQypJlxWyqY41CMVqaKtEkiF6hZ8bpt/D1il2lLCryMvd0WY6m1yZ5BE7HGhusZmHYUqwFkNLak6lMCwhE73pnVPc= X-Received: by 2002:a2e:94c8:: with SMTP id r8mr11529892ljh.28.1585699218480; Tue, 31 Mar 2020 17:00:18 -0700 (PDT) MIME-Version: 1.0 From: David Schinazi Date: Tue, 31 Mar 2020 17:00:07 -0700 Message-ID: To: WebTransport Content-Type: multipart/alternative; boundary="000000000000a364d105a22f5e53" Archived-At: Subject: [Webtransport] Call for adoption: draft-vvv-webtransport-overview X-BeenThere: webtransport@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2020 00:00:26 -0000 --000000000000a364d105a22f5e53 Content-Type: text/plain; charset="UTF-8" Hi WebTransport enthusiasts, As discussed in our meeting at IETF 107 last week, this email starts a two-week WEBTRANS Working Group adoption call for draft-vvv-webtransport-overview. https://datatracker.ietf.org/doc/draft-vvv-webtransport-overview/ The adoption call will run until 2020-04-14. Please send comments, statements of support, and/or objections to . I'll note that WG adoption does not mean that the document has WG consensus yet, it just means that we think that Victor's individual draft is a good basis for us to start a new WG draft. As a reminder, an overview document is discussed in our charter: https://datatracker.ietf.org/wg/webtrans/about/ To assist in the coordination with owners of the WebTransport API, the group will initially develop an overview document containing use cases and requirements in order to clarify the goals of the effort. Thanks, David and Bernard --000000000000a364d105a22f5e53 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi WebTransport enthusiasts,

As discuss= ed in our meeting at IETF 107 last week,
this email starts a two-= week WEBTRANS Working Group
adoption call for=C2=A0draft-vvv-webt= ransport-overview.

The adoption call w= ill run until 2020-04-14. Please send comments,
statements of sup= port, and/or objections to=C2=A0<webtransport@ietf.org>.

I'll note tha= t WG adoption does not mean that the document has WG
consensus ye= t, it just means that we think that Victor's individual draft
is a good basis for us to start a new WG draft.

A= s a reminder, an overview document is discussed in our charter:
<= a href=3D"https://datatracker.ietf.org/wg/webtrans/about/">https://datatrac= ker.ietf.org/wg/webtrans/about/
=C2=A0 =C2=A0 To assist i= n the coordination with owners of the WebTransport API, the
=C2=A0 =C2= =A0 group will initially develop an overview document containing use cases<= br>=C2=A0 =C2=A0 and requirements in order to clarify the goals of the effo= rt.

Thanks,
David and Bernard
<= /div> --000000000000a364d105a22f5e53-- From nobody Tue Mar 31 17:25:47 2020 Return-Path: X-Original-To: webtransport@ietfa.amsl.com Delivered-To: webtransport@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F47A3A0E56 for ; Tue, 31 Mar 2020 17:25:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.053 X-Spam-Level: X-Spam-Status: No, score=0.053 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 FDfMxRqDtwNm for ; Tue, 31 Mar 2020 17:25:36 -0700 (PDT) Received: from mail-wm1-x331.google.com (mail-wm1-x331.google.com [IPv6:2a00:1450:4864:20::331]) (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 18ED13A0E31 for ; Tue, 31 Mar 2020 17:25:36 -0700 (PDT) Received: by mail-wm1-x331.google.com with SMTP id b12so4692306wmj.3 for ; Tue, 31 Mar 2020 17:25:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0iI2e8psbV7ABc5wBINTYlHsl4CxnP5SlsASduIQfIQ=; b=B+Du6M5+Nj2uj4p8g42pdBDVBx2TfkuMYXsSgF3UQYa/nk4QAEF/kNmM2vNM5pxQsi weUum7zmdxWKxsUWmF+JcosaFC5RbxxWT2TYaj4xLsy9CSMf/1tRVvhqoBeH9Ox6ox1c P+f/IOpb1NLRscFxw3e7bb3oVIALAvUWWdFWzD25EGoBow3CSRAeICb58zFNQO2IZw1r UHIXNy9MAg6vbxCgWCxIkbLeTPkXEeekFsp8+zcWxgueeSvvjOWp5Jmc3raKZYwWaOJm q3Mui+YejHmbedwrNtY30kV1Xl1eYk78M31oGJ7QKH9xmEL8c4Xhjiyp6YfLvyRlgHzx R5yQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0iI2e8psbV7ABc5wBINTYlHsl4CxnP5SlsASduIQfIQ=; b=UKRLdJbG5AKrilpTectrdw3ltZmMS3Ki2QscqSetd9uXeQU77PwG47mZQsN49k8LtU zOoJWJgwhe5NIGeX9Rkgfce6T4YAsCxH30tPkSMxX7TLjs9Ew8TZg3zniIQIL5kk9xue WBDXHPO7CnxrOdMeMrg5UNbVrPOmp5nggLqpcx+mR0LHYjqf5PhtHrdwHSSffbGXkurd EuiCkNWFnUY5KWbaEj6/OJVVN6e0pKeHBlJWEzIjNFlJoyzviebvLcmxMgSxvP/CtQau iQnLf23SBMWo0+TEqQKJ67tt5oBFpdykkjaadh5KQ68Ni32xTpuwvZAVmshbBmcNF+aJ XqDg== X-Gm-Message-State: AGi0PuabqeA4YWPBbdwavc09uXH1yqiqDKJycKEggbl8bmrmzy+QWoJY Df0RjbXjMCI0JtcenCqZHxEmhCrlY5GPqyNWiRw= X-Google-Smtp-Source: APiQypI8Iies36aeIKDlJyRINmb6W13WTzHvDPl/qtuc81wfQcnLBoHB9Lnya/tvX2s2afFM2SmMDGXbFoTbGIBIQ2c= X-Received: by 2002:a1c:ba04:: with SMTP id k4mr1412713wmf.165.1585700734485; Tue, 31 Mar 2020 17:25:34 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Lucas Pardue Date: Wed, 1 Apr 2020 01:25:25 +0100 Message-ID: To: David Schinazi Cc: WebTransport Content-Type: multipart/alternative; boundary="000000000000ffc98d05a22fb828" Archived-At: Subject: Re: [Webtransport] Call for adoption: draft-vvv-webtransport-overview X-BeenThere: webtransport@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2020 00:25:45 -0000 --000000000000ffc98d05a22fb828 Content-Type: text/plain; charset="UTF-8" I support the adoption of this draft. IMO, of all the documents on the table, this is the tightest scoped and broadly applicable. Cheers Lucad On Wed, 1 Apr 2020, 01:00 David Schinazi, wrote: > Hi WebTransport enthusiasts, > > As discussed in our meeting at IETF 107 last week, > this email starts a two-week WEBTRANS Working Group > adoption call for draft-vvv-webtransport-overview. > https://datatracker.ietf.org/doc/draft-vvv-webtransport-overview/ > > The adoption call will run until 2020-04-14. Please send comments, > statements of support, and/or objections to . > > I'll note that WG adoption does not mean that the document has WG > consensus yet, it just means that we think that Victor's individual draft > is a good basis for us to start a new WG draft. > > As a reminder, an overview document is discussed in our charter: > https://datatracker.ietf.org/wg/webtrans/about/ > To assist in the coordination with owners of the WebTransport API, the > group will initially develop an overview document containing use cases > and requirements in order to clarify the goals of the effort. > > Thanks, > David and Bernard > -- > Webtransport mailing list > Webtransport@ietf.org > https://www.ietf.org/mailman/listinfo/webtransport > --000000000000ffc98d05a22fb828 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I support the adoption of this draft.=C2=A0

IMO, of all the documents on the tabl= e, this is the tightest scoped and broadly applicable.=C2=A0

Cheers
Lucad

On Wed, 1 Apr 2020, 01:00 David Schinazi, <dschinazi.ietf@gmail.com> wrote:
Hi WebTransport enthusiasts,
As discussed in our meeting at IETF 107 last week,
th= is email starts a two-week WEBTRANS Working Group
adoption call f= or=C2=A0draft-vvv-webtransport-overview.

The adoption call will run until 20= 20-04-14. Please send comments,
statements of support, and/or obj= ections to=C2=A0<webtransport@ietf.org>.

<= div>I'll note that WG adoption does not mean that the document has WG
consensus yet, it just means that we think that Victor's indiv= idual draft
is a good basis for us to start a new WG draft.
=

As a reminder, an overview document is discussed in our= charter:
=C2=A0 =C2=A0 To assist in the coordinatio= n with owners of the WebTransport API, the
=C2=A0 =C2=A0 group will init= ially develop an overview document containing use cases
=C2=A0 =C2=A0 an= d requirements in order to clarify the goals of the effort.
<= br>
Thanks,
David and Bernard
--
Webtransport mailing list
Webtransport@ietf.org
https://www.ietf.org/mailman/listinfo/w= ebtransport
--000000000000ffc98d05a22fb828-- From nobody Tue Mar 31 17:39:16 2020 Return-Path: X-Original-To: webtransport@ietfa.amsl.com Delivered-To: webtransport@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DAAC3A0E63 for ; Tue, 31 Mar 2020 17:39:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.197 X-Spam-Level: X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 SfxRdwL6DnB0 for ; Tue, 31 Mar 2020 17:39:13 -0700 (PDT) Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (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 1AAFD3A0E58 for ; Tue, 31 Mar 2020 17:39:13 -0700 (PDT) Received: by mail-lf1-x12f.google.com with SMTP id t16so18088509lfl.2 for ; Tue, 31 Mar 2020 17:39:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BE4IH/kmamw0KXQopAJeS10zXGXcQz5SrQ7SyD10YLQ=; b=LIU7Ts0rQb+UFQ/LKJS9v4APFwanF+eR6iX9vtfPSRZabT5+jTno95JLVYZ0l0NLnF 2LjHBboEv5ojQlKsVtE3IM5Jj/zgARKCrg+7uzf/nPAyxzxHXVPlEhSmbN4BXMaNZRl4 0IijZvMjl87EgYnOqFu/YAuAqb7btJe/J4orc8gZAWKOcmOK363VYq81UWcxXFaQcubS wGX+dN1MLb1wDNwiO8XYJMvDytmqFzkqKC7gOIHBUhgXLO83vUyqY+KDVWzzCz5kFxRk gZFrH9K4rI/yNlGYhBaE0ty6p/Z1UOxwcYlbjZmBdbFHvFT1D7RMYumouHrGyepOMCNr l+NQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BE4IH/kmamw0KXQopAJeS10zXGXcQz5SrQ7SyD10YLQ=; b=aNK3nBJqW3egbJRvOsKzXuCU7npUHE7ZuKMyJ1QUFgWHrJNdmwSWcl3w3jtT3R89yd I7hIfZHYC7B6FwF5sh+lxVgUWEGPItdVN/KlaI6AX5lMDxN443gBFHGhhNE3OuKHuJ5l qSgZPYIv0WwT6oSIsh7FG4syQoXyNBSqp0Em7LyXqiHCxsCKpqyEXspQmdCWz1wZDO0T 14JuRp3T7V8TXer+O1a86l7+puY4eANxLsrzDGV60dMGwYSg6SPXulR3XDqpyEgUgCXk 4DQKLafb1CxUCI8YzjOVnOHFUhdjIuvqzBKbTi7bf7huI8uVfPTDfS2N0Dr6s4VpOcSy 8emQ== X-Gm-Message-State: AGi0PuZFC2Gj/7vHyClO8QjZsFOpkY3ig/hmYUIfkFug3ExvjqKtJVzE g7Zk76WIefhP2ayJqoJIMp+9oslzV1Gl+8Y3IFQ= X-Google-Smtp-Source: APiQypLLsG2dKFubjV9kOLS6VAnFT/YxXMe+J+tU31x6GCojLFRwDSySxiw2Qz54amzO5vCgXMRm8vWLA76k/Jt1/Go= X-Received: by 2002:ac2:5146:: with SMTP id q6mr13394794lfd.81.1585701551327; Tue, 31 Mar 2020 17:39:11 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Spencer Dawkins at IETF Date: Tue, 31 Mar 2020 19:38:45 -0500 Message-ID: To: David Schinazi Cc: WebTransport Content-Type: multipart/alternative; boundary="000000000000afce1d05a22fe923" Archived-At: Subject: Re: [Webtransport] Call for adoption: draft-vvv-webtransport-overview X-BeenThere: webtransport@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2020 00:39:15 -0000 --000000000000afce1d05a22fe923 Content-Type: text/plain; charset="UTF-8" Hi, David, On Tue, Mar 31, 2020 at 7:00 PM David Schinazi wrote: > Hi WebTransport enthusiasts, > > As discussed in our meeting at IETF 107 last week, > this email starts a two-week WEBTRANS Working Group > adoption call for draft-vvv-webtransport-overview. > https://datatracker.ietf.org/doc/draft-vvv-webtransport-overview/ > > The adoption call will run until 2020-04-14. Please send comments, > statements of support, and/or objections to . > > I'll note that WG adoption does not mean that the document has WG > consensus yet, it just means that we think that Victor's individual draft > is a good basis for us to start a new WG draft. > I think this document is in good enough shape for the working group to adopt. > As a reminder, an overview document is discussed in our charter: > https://datatracker.ietf.org/wg/webtrans/about/ > To assist in the coordination with owners of the WebTransport API, the > group will initially develop an overview document containing use cases > and requirements in order to clarify the goals of the effort. > I do hope the working group focuses a bit on use cases in its work on this document. Best, Spencer > > Thanks, > David and Bernard > -- > Webtransport mailing list > Webtransport@ietf.org > https://www.ietf.org/mailman/listinfo/webtransport > --000000000000afce1d05a22fe923 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi, David,=C2=A0

On Tue, Mar 31, 2020 at 7= :00 PM David Schinazi <dschi= nazi.ietf@gmail.com> wrote:
Hi WebTransport enthusiasts,

As discussed in our meeting at IETF 107 last week,
this = email starts a two-week WEBTRANS Working Group
adoption call for= =C2=A0draft-vvv-webtransport-overview.
<= div>
The adoption call will run until 2020-04-14. Please send= comments,
statements of support, and/or objections to=C2=A0<<= a href=3D"mailto:webtransport@ietf.org" target=3D"_blank">webtransport@ietf= .org>.

I'll note that WG adoption does = not mean that the document has WG
consensus yet, it just means th= at we think that Victor's individual draft
is a good basis fo= r us to start a new WG draft.

I= think this document is in good enough shape for the working group to adopt= .=C2=A0
=C2=A0
As a reminder, an overview document is discussed= in our charter:
=C2=A0 =C2=A0 To assist in the coordination with o= wners of the WebTransport API, the
=C2=A0 =C2=A0 group will initially de= velop an overview document containing use cases
=C2=A0 =C2=A0 and requir= ements in order to clarify the goals of the effort.

I do hope the working group focuses a bit on use c= ases in its work on this document.=C2=A0

Best,

Spencer
=C2=A0

= Thanks,
David and Bernard
--
Webtransport mailing list
Webtransport@iet= f.org
https://www.ietf.org/mailman/listinfo/webtransport=
--000000000000afce1d05a22fe923-- From nobody Tue Mar 31 18:36:06 2020 Return-Path: X-Original-To: webtransport@ietfa.amsl.com Delivered-To: webtransport@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C94C3A0F8C for ; Tue, 31 Mar 2020 18:36:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.199 X-Spam-Level: X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.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 NP3H79_HzIfZ for ; Tue, 31 Mar 2020 18:35:59 -0700 (PDT) Received: from ma1-aaemail-dr-lapp03.apple.com (ma1-aaemail-dr-lapp03.apple.com [17.171.2.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06B3B3A0F89 for ; Tue, 31 Mar 2020 18:35:58 -0700 (PDT) Received: from pps.filterd (ma1-aaemail-dr-lapp03.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp03.apple.com (8.16.0.27/8.16.0.27) with SMTP id 0311VpF6038680; Tue, 31 Mar 2020 18:35:57 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=sender : content-type : content-transfer-encoding : from : mime-version : subject : date : message-id : references : cc : in-reply-to : to; s=20180706; bh=QkbBxFSE7aI1uG/qZf3GUYFVCWM9McoOOG/9wPX3VFw=; b=DYy6/eOZ007CxvzNHRbYTDZzaxoKAnaFVSpLiJN3BGNsFxSpX7Iqxs/VpxkaW/BNqW8k XzWBWjZw0RZh8hLn5KbhW5rLICrtc/gWdzylHjfKQrdir7cNeZeybZdmGUuNlDOPIF69 dQ1rnS6Ovp6p90pSm8lTw6uKLVadqhCbr7gV+lXsahCOcY1v85hyD4C/chSfcLcryYSE uG1+j0KZ+J/eMyDaJYpMpK3RDOUFT0HNCWatYPvBwrdgAC5sp4OC0W1oUK+QoL+Om3e1 qj2xrEXAYwkeT1TUJ2MEukflE3jYSK1K2pvgSHGglyHJXUhMixhBpuCukbYs4fm+w521 zw== Received: from rn-mailsvcp-mta-lapp01.rno.apple.com (rn-mailsvcp-mta-lapp01.rno.apple.com [10.225.203.149]) by ma1-aaemail-dr-lapp03.apple.com with ESMTP id 3025jvke3h-11 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 31 Mar 2020 18:35:57 -0700 Received: from rn-mailsvcp-mmp-lapp03.rno.apple.com (rn-mailsvcp-mmp-lapp03.rno.apple.com [17.179.253.16]) by rn-mailsvcp-mta-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.5.20200312 64bit (built Mar 12 2020)) with ESMTPS id <0Q8300K925RWII30@rn-mailsvcp-mta-lapp01.rno.apple.com>; Tue, 31 Mar 2020 18:35:56 -0700 (PDT) Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp03.rno.apple.com by rn-mailsvcp-mmp-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.5.20200312 64bit (built Mar 12 2020)) id <0Q8300O005KH4N00@rn-mailsvcp-mmp-lapp03.rno.apple.com>; Tue, 31 Mar 2020 18:35:56 -0700 (PDT) X-Va-A: X-Va-T-CD: 10a534a1686abdccb129dd18c18ba03f X-Va-E-CD: d61a922a5b3bc055080e14c0938dc345 X-Va-R-CD: 147b21ef2042ada0c64cb5917427ea01 X-Va-CD: 0 X-Va-ID: e50c7c6f-6813-4e40-a617-200931d587d2 X-V-A: X-V-T-CD: 10a534a1686abdccb129dd18c18ba03f X-V-E-CD: d61a922a5b3bc055080e14c0938dc345 X-V-R-CD: 147b21ef2042ada0c64cb5917427ea01 X-V-CD: 0 X-V-ID: 34ab9d51-84dd-4346-ae24-b4d5d21b8d0d X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.676 definitions=2020-03-31_07:2020-03-31, 2020-03-31 signatures=0 Received: from [10.104.105.84] (unknown [10.104.105.84]) by rn-mailsvcp-mmp-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.5.20200312 64bit (built Mar 12 2020)) with ESMTPSA id <0Q83007015RWKA40@rn-mailsvcp-mmp-lapp03.rno.apple.com>; Tue, 31 Mar 2020 18:35:56 -0700 (PDT) Sender: ekinnear@apple.com Content-type: multipart/alternative; boundary=Apple-Mail-08C65F20-B160-4306-AC2E-093CDCD498EE Content-transfer-encoding: 7bit From: Eric Kinnear MIME-version: 1.0 (1.0) Date: Tue, 31 Mar 2020 18:35:55 -0700 Message-id: <8F15A5C3-9425-452E-AB2C-8B8CE3F646F0@apple.com> References: Cc: WebTransport In-reply-to: To: David Schinazi X-Mailer: iPad Mail (17E255) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.676 definitions=2020-03-31_07:2020-03-31, 2020-03-31 signatures=0 Archived-At: Subject: Re: [Webtransport] Call for adoption: draft-vvv-webtransport-overview X-BeenThere: webtransport@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2020 01:36:03 -0000 --Apple-Mail-08C65F20-B160-4306-AC2E-093CDCD498EE Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I support adoption.=20 It=E2=80=99s a good starting point and can be enhanced as necessary. Thanks, Eric > On Mar 31, 2020, at 5:00 PM, David Schinazi wro= te: >=20 > =EF=BB=BF > Hi WebTransport enthusiasts, >=20 > As discussed in our meeting at IETF 107 last week, > this email starts a two-week WEBTRANS Working Group > adoption call for draft-vvv-webtransport-overview. > https://datatracker.ietf.org/doc/draft-vvv-webtransport-overview/ >=20 > The adoption call will run until 2020-04-14. Please send comments, > statements of support, and/or objections to . >=20 > I'll note that WG adoption does not mean that the document has WG > consensus yet, it just means that we think that Victor's individual draft > is a good basis for us to start a new WG draft. >=20 > As a reminder, an overview document is discussed in our charter: > https://datatracker.ietf.org/wg/webtrans/about/ > To assist in the coordination with owners of the WebTransport API, the= > group will initially develop an overview document containing use cases= > and requirements in order to clarify the goals of the effort. >=20 > Thanks, > David and Bernard > --=20 > Webtransport mailing list > Webtransport@ietf.org > https://www.ietf.org/mailman/listinfo/webtransport --Apple-Mail-08C65F20-B160-4306-AC2E-093CDCD498EE Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
I support adoption. <= /div>
It=E2=80=99s a good starting point and can be enhanced= as necessary.

Thanks,
Eric


=
On Mar 31, 2020, at 5:00 PM, David Schinazi <ds= chinazi.ietf@gmail.com> wrote:

=EF=BB=BF
Hi WebTransport enthusi= asts,

As discussed in our meeting at IETF 107 last week,<= /div>
this email starts a two-week WEBTRANS Working Group
adop= tion call for draft-vvv-webtransport-overview.

=
The adoption call will run until 2020-04-14. Please send comments= ,
statements of support, and/or objections to <webtransport@ietf.org>.

<= /div>
I'll note that WG adoption does not mean that the document has WG<= /div>
consensus yet, it just means that we think that Victor's individua= l draft
is a good basis for us to start a new WG draft.
=
As a reminder, an overview document is discussed in our chart= er:
   = ; To assist in the coordination with owners of the WebTransport API, the
=     group will initially develop an overview document containing u= se cases
    and requirements in order to clarify the goals of t= he effort.

Thanks,
David and Bernard<= /div>
--
Webtransport mailing list
Webtrans= port@ietf.org
https://www.ietf.org/mailman/listinfo/webtrans= port
= --Apple-Mail-08C65F20-B160-4306-AC2E-093CDCD498EE-- From nobody Tue Mar 31 19:02:58 2020 Return-Path: X-Original-To: webtransport@ietfa.amsl.com Delivered-To: webtransport@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DB3E3A0FDE for ; Tue, 31 Mar 2020 19:02:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.196 X-Spam-Level: X-Spam-Status: No, score=-0.196 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 9dyCyH7Ku1xX for ; Tue, 31 Mar 2020 19:02:55 -0700 (PDT) Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) (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 CEB973A07EF for ; Tue, 31 Mar 2020 19:02:55 -0700 (PDT) Received: by mail-pg1-x529.google.com with SMTP id k191so11297641pgc.13 for ; Tue, 31 Mar 2020 19:02:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:in-reply-to:to; bh=Kl9XH9DniepQR5qtYCWSnw4nqQCQloPG6Gc7sETedqw=; b=drZwh4EWz5jBkrIZ/e/ABtxTKE5dovx/JGgtGsXcjuj9aUhwjQ2xmXbMIBdoe/r8T1 Jjh3NLAkby/sUyX8hJy5yJD2TmOABIuTMOPn0x8S2qcNE0DEJuR2hw+byTI4UEbVDOoj +QsSFVnx+4ekFCQzigEIGk5VZPoCCX26gsY540gZO1GWsQdKPqb6SbCMdF4Z2pAUAkRE K3nBIIGcFWoyAPs/02bAj2YeqfVE76hxaGyu8TzZYK14CbMZCRblukgMnfsFftCHVMWa GP0YLyZN4ThuR0ddMZM5XjJtZKo+lOk7WJYJl0tByNKyvsW/UJmL10xCe3Y6qRDfw9uV oKpw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:in-reply-to:to; bh=Kl9XH9DniepQR5qtYCWSnw4nqQCQloPG6Gc7sETedqw=; b=ihG2M+dLnCCIf5xiebQYLBei44YqDaCjL7w0wKqDmsYErOHIF/kTS9LDlS4g/mPc5e wa/2fRRcO+KefoubkiBdd6RM5iIG/YRwATvyqxmHN/u3qkc66zr3jJII7nio+uQ5p1ij e+utWZB9PeYbb2mtJlDttfSqNDMvlIw1o/4MeHLPus4fVZZ8hLH1AsSPBXnTEGhwObSH 3oxvLMYe0tDqfGXT2cHcdyDolVcNlHPl00EI6iN15BJKvLwouvFDg6WzX0lzTj2EG67a k7TQV8WLOMsnqWu2xlC7h6LwGn0kfvlJGLpm3ukoI33fc4o+MYOe0EQa8X5o5xEQOBYt mJmQ== X-Gm-Message-State: ANhLgQ1y17eERVnte3gfmq9LHfs8UgJA+nsCs71CZqWBt5SpM6FxawEw v1UnlpGEAItF/IbRg6xrepSbIMCat5w= X-Google-Smtp-Source: ADFU+vuV3N3ou22V0cSaU6Le3vaz21KHJM1qTXXfzZZetuj15TiQkSNFADO5qbOg7ISuLLzYNXnU0A== X-Received: by 2002:a65:5189:: with SMTP id h9mr19900448pgq.296.1585706574772; Tue, 31 Mar 2020 19:02:54 -0700 (PDT) Received: from [192.168.1.197] (c-71-227-236-207.hsd1.wa.comcast.net. [71.227.236.207]) by smtp.gmail.com with ESMTPSA id p4sm337154pfg.163.2020.03.31.19.02.53 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 31 Mar 2020 19:02:54 -0700 (PDT) Content-Type: multipart/alternative; boundary=Apple-Mail-81EC6653-9544-4444-A62E-C8BAF007F251 Content-Transfer-Encoding: 7bit From: Bernard Aboba Mime-Version: 1.0 (1.0) Date: Tue, 31 Mar 2020 19:02:52 -0700 Message-Id: References: <8F15A5C3-9425-452E-AB2C-8B8CE3F646F0@apple.com> In-Reply-To: <8F15A5C3-9425-452E-AB2C-8B8CE3F646F0@apple.com> To: webtransport@ietf.org X-Mailer: iPad Mail (17E255) Archived-At: Subject: Re: [Webtransport] Call for adoption: draft-vvv-webtransport-overview X-BeenThere: webtransport@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2020 02:02:57 -0000 --Apple-Mail-81EC6653-9544-4444-A62E-C8BAF007F251 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I also support adoption. >> Hi WebTransport enthusiasts, >> >> As discussed in our meeting at IETF 107 last week, >> this email starts a two-week WEBTRANS Working Group >> adoption call for draft-vvv-webtransport-overview. >> https://datatracker.ietf.org/doc/draft-vvv-webtransport-overview/ >> >> The adoption call will run until 2020-04-14. Please send comments, >> statements of support, and/or objections to . >> >> I'll note that WG adoption does not mean that the document has WG >> consensus yet, it just means that we think that Victor's individual draft >> is a good basis for us to start a new WG draft. >> >> As a reminder, an overview document is discussed in our charter: >> https://datatracker.ietf.org/wg/webtrans/about/ >> To assist in the coordination with owners of the WebTransport API, the >> group will initially develop an overview document containing use cases >> and requirements in order to clarify the goals of the effort. >> >> Thanks, >> David and Bernard >> -- >> Webtransport mailing list >> Webtransport@ietf.org >> https://www.ietf.org/mailman/listinfo/webtransport > -- > Webtransport mailing list > Webtransport@ietf.org > https://www.ietf.org/mailman/listinfo/webtransport --Apple-Mail-81EC6653-9544-4444-A62E-C8BAF007F251 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
I also support adoption.&n= bsp;

Hi WebTransp= ort enthusiasts,

As discussed in our meeting at IETF 107 l= ast week,
this email starts a two-week WEBTRANS Working Group
adoption call for draft-vvv-webtransport-overview.
ht= tps://datatracker.ietf.org/doc/draft-vvv-webtransport-overview/

The adoption call will run until 2020-04-14. Please sen= d comments,
statements of support, and/or objections to <<= a href=3D"mailto:webtransport@ietf.org">webtransport@ietf.org>.
=

I'll note that WG adoption does not mean that the docume= nt has WG
consensus yet, it just means that we think that Victor's= individual draft
is a good basis for us to start a new WG draft.<= /div>

As a reminder, an overview document is discussed in= our charter:
&n= bsp;   To assist in the coordination with owners of the WebTransport AP= I, the
    group will initially develop an overview document co= ntaining use cases
    and requirements in order to clarify the= goals of the effort.

Thanks,
David a= nd Bernard
--
Webtransport mailing list
Webtrans= port@ietf.org
https://www.ietf.org/mailman/listinfo/webtrans= port
--
Webtransport mai= ling list
Webtransport@ietf.org
https://www.= ietf.org/mailman/listinfo/webtransport
<= /html>= --Apple-Mail-81EC6653-9544-4444-A62E-C8BAF007F251--