Re: [Tools-discuss] [Manycouches] Proposal to discontinue live mp3 audio streams at IETF meetings

Watson Ladd <watsonbladd@gmail.com> Sun, 04 October 2020 03:11 UTC

Return-Path: <watsonbladd@gmail.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C0283A0ACB; Sat, 3 Oct 2020 20:11:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 5wAMoQz1RPgy; Sat, 3 Oct 2020 20:11:30 -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 9E1123A0AC8; Sat, 3 Oct 2020 20:11:29 -0700 (PDT)
Received: by mail-lf1-x135.google.com with SMTP id z19so6863582lfr.4; Sat, 03 Oct 2020 20:11:29 -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=HK3DjURIm2iHr0p2e021ShJIlScj56CWNwVJs0BfSiY=; b=TGckOMK0PkuENWJz0gn/2U4yKmutiqcbhNMn0CXtkZjnF0sjh6zgxzVr4fSDunxUyJ 0WWVqRTqXJIJFCzMJuGsZxIUggo8tfhOuPM/r7lYJFXEoiu1K7p07uYbZ1E7um18gSas 6up0K2jKyVjEN3rlQg4G1lpMbo/QXFegC6e+9p4ViFD911gyrqvio3tK7hm9lW0qKUdd WQOHZO1WVbwYa+fcSHfAwzIqgbHmscbwpSwNDFwRaMoIVelfa2nVIFbNaMow7bhpUkiQ QjbLMP1VwN1+4EOHVhVhK3hK/kKit6MaDLwNARGE1cE0ltkvVatQ7qnHYQaZF0qUVC7r l+Pw==
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=HK3DjURIm2iHr0p2e021ShJIlScj56CWNwVJs0BfSiY=; b=gHUETNGXXkrki7CrRLKfExRyh+CaoTpRTFFKJXkPBcq1OgZvB4e2+r1FHffMlHzbGB MdCW0XKkqUtrbB2LxdMuiHPCWycdFRggEqYp0wOTkQRM7UQ+3iUVAYex0m0gEZqJWLEc Os5tG4J/fi3UcmOSJ5j+znWu3TXkRmOpQxWDLeP3e8+xlZzVakyfTyJKk14iDjXpLe9i 1wqhtZ2ne3XF33MzAGvA+/2tnHXdiE3EpdPk+YlOfo2rHNfCU2U5TM2EmFwB8YA9S6NY Ea6lhNv4ZPDUoSzYyKfhMulZeQDSbcQ1nRP8e5muj1uJ0tLH0YIne6vaqy8ZnXmQdl8P Krgg==
X-Gm-Message-State: AOAM530bFHZFmGDBMzkq8bF8Fm9/NdSPZqzsR0UVTtKVWVG07eC5QmRZ vVHlV0EQyGf1Os7qmJLmRgX8LO8LH1gBmX6nInc=
X-Google-Smtp-Source: ABdhPJyMJ4UOFVn7h78QRyJa6hNEo4SdSAZb5gwZUYB65/DZYUDGJ/e1fQB54FO4Hl2/4O7DLRKDfTy8Pwy9H/L6WzQ=
X-Received: by 2002:a19:ed15:: with SMTP id y21mr3737616lfy.570.1601781087622; Sat, 03 Oct 2020 20:11:27 -0700 (PDT)
MIME-Version: 1.0
References: <5a8ed7f4-b0a0-a5ab-5c81-a7af404e9d10@nostrum.com> <e0d05c54-505c-7f94-0ea7-6905bd63d989@gmail.com> <14FC90BA1260E306F5DB4D31@PSB>
In-Reply-To: <14FC90BA1260E306F5DB4D31@PSB>
From: Watson Ladd <watsonbladd@gmail.com>
Date: Sat, 3 Oct 2020 20:11:16 -0700
Message-ID: <CACsn0cmdMfGwHZThAFrDyNu9cU97xQCUq8S4yjJ5iuQHnfA0Hw@mail.gmail.com>
To: John C Klensin <john-ietf@jck.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, tools-discuss@ietf.org, manycouches@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/4ICm1RAM8hhWk5UDROF_ARjbOok>
Subject: Re: [Tools-discuss] [Manycouches] Proposal to discontinue live mp3 audio streams at IETF meetings
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Oct 2020 03:11:32 -0000

On Thu, Oct 1, 2020 at 9:03 PM John C Klensin <john-ietf@jck.com> wrote:
>
> Out of a desire to stay out of this discussion, I sent a private
> note to Robert earlier today that I will not try to reprise
> here.  However...
>
> --On Friday, October 2, 2020 08:42 +1300 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>
> >> * This removes a mechanism that allowed people to listen to a
> >> session in real-time without paying a registration fee.
> >>
> >>     There will be ongoing discussion and tuning of the
> >>     meeting registration structure. In the meantime, the fee
> >>     waiver program is available and  being
> >>     improved.
> >
> > I don't think that's a tools-discuss decision alone. It's been
> > a significant point of principle discussed (e.g.) in SHMOO,
> > hence the extra CC.
>
> Right.  And I think there are some very broad principles about
> who we are willing to disenfranchise, whether we are willing to
> insist that people give up privacy to observe our meetings;
> whether real-time observation is actually needed or whether
> people who just want to observe can watch or listen later;
> whether policies that require either registration fees that are
> not tied to ability to pay or asking for fee waivers are
> inherently discriminatory against, e.g., people from developing
> areas; how many people have to be pushed out before it is an
> issue (note the tie to Robert's "not many people are using the
> mp3 feed); etc.
>
> To me, there is also a small elephant lurking around the corners
> of the room having to do with just how serious we are about key
> discussions and decisions occurring on the mailing lists.  My
> recollection about what I heard when the IETF got started --long
> before real-time remote participation was feasible for most
> people -- was that there was not a lot of concern about these
> issues, not because people were backward, but because it was
> very clear that meetings were about discussion and getting a
> shared understanding of the issues and how to explain them, not
> about "deciding" or even "agreeing".   I suspect that a really
> pure form of that approach may be somewhat mythological, but the
> difference between even a watered-down version and the "decide
> in meeting, ask on mailing list if there are any significant
> objections" pattern we've seen frequently in recent years is
> still significant.

I think it's extremely difficult to get any deep understanding of a
significant issue at a meeting session. The number of words that can
be exchanged on any topic in a minute or two at the mike is miniscule,
while emails have far more length and can be digested at leisure, and
clarifications requested after digestion.  Buttonholing attendees for
informal conversation is far more important use of the meeting.
Particularly for TLS 1.3 standardization a considerable amount of the
action in late stages was in academic conferences that weren't
officially part of the IETF because of the technicalities.

>
> However, I think my main point is similar to Brian's (if I
> correctly understand him): it is time we have discussions about
> principles and make decisions about them and then answer
> questions (probably easily) about what services we need to offer
> and how they should be arranged and/or delivered in terms of
> those principles.   Making a decision about something like an
> mp3 feed (and a variety of other things) in isolation is
> unlikely to lead us to good places.

+1

>
> > It seems to me that the principle of the fee waiver and when
> > it's ethical to use it is still not clear, and we don't know
> > whether it is financially viable in the medium to long term.
> > Until that's settled, I'm a bit uneasy about dropping the mp3
> > streams, precisely because they do not need pre-registration.
>
> > (If meetecho had a "read only" or observer mode without
> > pre-registration, this problem would go away instantly.)
>
> Which, of course, Meetecho, in its IETF form, had in the
> original distinction between joining as an observer and as a
> participant until "we" decided to shut it off in the run-up to
> IETF 108 (or IETF 107 if not using Meetecho at all for that
> meeting counts).  The problem is not what mode(s) are available
> but where we draw the dividing line about who gets a free ride.
> Personally I have a lot of difficulty justifying free mp3 live
> streaming but requiring that "read only" / observer Meetecho
> users pay, but YMMD.
>
> And I see parts of those things as both important but larger
> parts as just another symptom.  We need to look at whether to
> make a distinction between observers and participants and
> whether the latter (at least) are pay to play... always, or only
> when a meeting is all-remote.  We need to figure out if there is
> any real justification for requiring that observers be able to
> observe in real time and, if not, how much delay in getting
> video (and audio?) posted is tolerable.  And so on.  I think
> that, if we have answers to those sorts of questions of
> principle, most of the questions about live audio feeds and even
> fee waivers will largely fall out.
>
> best,
>    john
>
> _______________________________________________
> Manycouches mailing list
> Manycouches@ietf.org
> https://www.ietf.org/mailman/listinfo/manycouches

Sincerely,
Watson


--
Astra mortemque praestare gradatim