Re: [Mops] FW: Multicast for the Web (and WebTransport in particular)

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Fri, 30 July 2021 14:10 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: mops@ietfa.amsl.com
Delivered-To: mops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D4D53A2B72 for <mops@ietfa.amsl.com>; Fri, 30 Jul 2021 07:10:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, RCVD_IN_DNSWL_BLOCKED=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 abYmXo_H3Idt for <mops@ietfa.amsl.com>; Fri, 30 Jul 2021 07:10:28 -0700 (PDT)
Received: from mail-ua1-x935.google.com (mail-ua1-x935.google.com [IPv6:2607:f8b0:4864:20::935]) (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 998873A2B71 for <mops@ietf.org>; Fri, 30 Jul 2021 07:10:28 -0700 (PDT)
Received: by mail-ua1-x935.google.com with SMTP id d6so4042677uav.2 for <mops@ietf.org>; Fri, 30 Jul 2021 07:10:28 -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=2YtkaW6WVdoRYszHe0Vu1VFTzMKmkJ9beWAAtH9I7nI=; b=gWLYMkgBilCPzBkEL7FfXbqsELwDbBa3KKhLayx02N9sDTeL336yBqts9RObKCq8iy O51PpAIeLuf3kjgBPa86LpQxYIWp9UyVPLb19gFlNaqOnbcxPOBjDWXJULD2CVI6VkoX g9rqUCPz9uBJ+AqFb28zGVGuIIwkI9rsEAvXiG5ByxWgCB7P0E8XCOKIlkNQ4SnMRvqj F+z/eqXi2Gz4ibDd5pYN2m0IcmsuOKAQk227R5mSGt67G0luSUreC0thJ8NrxcezIr9u z6FZXw7P52onrDgJkpYASqt9zLfal1RMGoYJBLfq4uM8XGSoudNGjBL/zCfxSAHU2c8K SpFg==
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=2YtkaW6WVdoRYszHe0Vu1VFTzMKmkJ9beWAAtH9I7nI=; b=OMn9qPJJJR7YI8BsHYP2b3DW4yj4/V88NiSz/81MSkij/DMAmlLQq12uKVX/WJJifb ZVU/rR+96kwdzc538RnEYHCf7fKCStNvJ8S2XLFA4u1dyJH3VAC+vyq2rTea/E7qbS9S anOqJtV8QFBap/70AQ3PKbSDJ2bWlw4AoeF0uzba2b/pIJiCUW2BusfYUSHdJmXQ0pYB HinhtS8/YxIaJPUQnNp8UJu0g4WPwO2gJv8NEMj0Mouv3BurAK9Hv6V6mbVULZk1kYt4 qw6O2pEPX3XbhQOEOkNuqfYC/Mujouv1F/r6pc7nGLEvlt5bG2v4aXwff0F83QSn8IBc kClw==
X-Gm-Message-State: AOAM530uhfBXdd7fkQbeY1EGfcz19t78BGQpmiBSZ91qMmFGztpS6Sgg iVfKsZaLm9D1IbEoauUA9WwNDPxWVfiRUWfzQ5M=
X-Google-Smtp-Source: ABdhPJwWUwA30fUOu+Gqo6vbeBjtbH8X3BcOYeVIzogH4xsW+7g+qOQpeBxWcdQ97CHRe+ys/DdncWfKSS2Z/Mncljs=
X-Received: by 2002:a9f:2f14:: with SMTP id x20mr2002920uaj.104.1627654227081; Fri, 30 Jul 2021 07:10:27 -0700 (PDT)
MIME-Version: 1.0
References: <4B5C8DD7-8F64-4459-94E5-089CBDB04461@akamai.com> <111093F7-270D-4D12-95AB-60BACB9B6ABA@akamai.com> <CAKKJt-dVz3p0cT3O0fcEcfQSqueOLYkaVW0WWXpgZWqVFrefyw@mail.gmail.com> <99A8A55B-3C43-432F-8E51-47B4FEF59E47@akamai.com> <CAKKJt-e2uYfFtof8NXgj56-j-F=eTjFnzVjh+2MbxmHSxJQK5g@mail.gmail.com> <CAJU8_nUJM=shHf-me-Dk314-AYk=CpBO-RRG+CWmvo9aS2_tXQ@mail.gmail.com>
In-Reply-To: <CAJU8_nUJM=shHf-me-Dk314-AYk=CpBO-RRG+CWmvo9aS2_tXQ@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Fri, 30 Jul 2021 09:10:00 -0500
Message-ID: <CAKKJt-eTBS8Zps1TJ6ECeNyGe2vNAbs5UWESG=hgjyiZiX7qmw@mail.gmail.com>
To: Kyle Rose <krose@krose.org>
Cc: "Holland, Jake" <jholland@akamai.com>, "mops@ietf.org" <mops@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000005bcad05c857c8e7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/mO9ljV82-N8aKvIzLhuyI_cmcr4>
Subject: Re: [Mops] FW: Multicast for the Web (and WebTransport in particular)
X-BeenThere: mops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Media OPerationS <mops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mops>, <mailto:mops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mops/>
List-Post: <mailto:mops@ietf.org>
List-Help: <mailto:mops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mops>, <mailto:mops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jul 2021 14:10:34 -0000

Hi, Kyle,

On Fri, Jul 30, 2021 at 8:58 AM Kyle Rose <krose@krose.org> wrote:

> Given the existence of the new W3C multicast community group, one
> important consideration at this early stage of work is to make sure we
> develop a consistent, coherent vision. I would be in favor of a single
> mailing list until/unless we get to a point where responsibility can be
> assigned to groups working independently.
>

Makes sense to me, even if it's only used for coordination, and all of
the technical work goes somewhere else.

Do you and/or Jake have thoughts about whether that needs to be a new
mailing list, or whether something that already exists is fit for purpose?

Best,

Spencer


> Kyle
>
> On Fri, Jul 30, 2021 at 9:41 AM Spencer Dawkins at IETF <
> spencerdawkins.ietf@gmail.com> wrote:
>
>> Hi, Jake,
>>
>> On Thu, Jul 29, 2021 at 4:59 PM Holland, Jake <jholland@akamai.com>
>> wrote:
>>
>>> Hi Spencer,
>>>
>>> From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
>>> > Date: Thu,2021-07-29 at 12:36 PM
>>> >
>>> > This was a very interesting side meeting.
>>>
>>> Thanks!
>>>
>>> > Could I ask where you expect discussion to happen, and
>>> > where the notes would be posted?
>>>
>>> I was thinking I'd send a follow-up message to mops and
>>> webtransport with a summary and links to notes and the video
>>> once it's posted (there may be a slight delay).
>>>
>>> If we establish an IETF mailing list or venue, I guess I’ll
>>> probably also send one more follow-up message to mops,
>>> webtransport, mboned, and possibly ietf to invite interested
>>> parties to join, unless I get different guidance.
>>>
>>> If you want to comment on the IETF drafts or stay in an IETF
>>> context for this, there are several relevant drafts that have
>>> been adopted in mboned, where comment would be very welcome:
>>> https://www.ietf.org/mailman/listinfo/mboned
>>> https://datatracker.ietf.org/doc/draft-ietf-mboned-dorms/
>>> https://datatracker.ietf.org/doc/draft-ietf-mboned-cbacc/
>>> https://datatracker.ietf.org/doc/draft-ietf-mboned-ambi/
>>> https://datatracker.ietf.org/doc/draft-ietf-mboned-mnat/
>>>
>>> (NB: I'll also be presenting on these in the mboned meeting
>>> tomorrow.)
>>>
>>> If you want to get involved in the overall project including
>>> the web-specific aspect of it or to discuss other topics that
>>> might be tangential to mboned, I'd also encourage joining the
>>> W3C list:
>>> https://lists.w3.org/Archives/Public/public-multicast/
>>>
>>> If you're able to participate in W3C, that group is meeting monthly
>>> on first Wednesdays, with the next scheduled meeting on August
>>> 4th at 7:30am Pacific time (2:30pm UTC).  The details are here:
>>> https://lists.w3.org/Archives/Public/public-multicast/2021Jul/0004.html
>>>
>>> Best regards,
>>> Jake
>>>
>>
>> This is all very helpful! Thanks for the quick response.
>>
>> Do you think a mailing list would be useful for coordinating things among
>> various venues? If so, please let me know - I know how to request that.
>>
>> It sounds like you may not need a dedicated venue before IETF 112, but if
>> you decide that you do, please let me know - I'd love to help with that too.
>>
>> Best,
>>
>> Spencer
>> --
>> Mops mailing list
>> Mops@ietf.org
>> https://www.ietf.org/mailman/listinfo/mops
>>
>