Re: Required Google Account to review an IETF meeting. Really?
George Michaelson <ggm@algebras.org> Tue, 03 June 2025 08:44 UTC
Return-Path: <ggm@algebras.org>
X-Original-To: ietf@mail2.ietf.org
Delivered-To: ietf@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 4A3883016104 for <ietf@mail2.ietf.org>; Tue, 3 Jun 2025 01:44:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=algebras-org.20230601.gappssmtp.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f9sgr2RJZRg6 for <ietf@mail2.ietf.org>; Tue, 3 Jun 2025 01:44:30 -0700 (PDT)
Received: from mail-oo1-xc35.google.com (mail-oo1-xc35.google.com [IPv6:2607:f8b0:4864:20::c35]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 2185430160FD for <ietf@ietf.org>; Tue, 3 Jun 2025 01:44:29 -0700 (PDT)
Received: by mail-oo1-xc35.google.com with SMTP id 006d021491bc7-607dceb1afdso3521931eaf.3 for <ietf@ietf.org>; Tue, 03 Jun 2025 01:44:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=algebras-org.20230601.gappssmtp.com; s=20230601; t=1748940269; x=1749545069; darn=ietf.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=NwV52I+ZDFoswRBJpTFUuXV7mNweCfVv8aNB45I6I0I=; b=bZVE1M6Tb2b0Rvhe8Xrg6q0lLuSE+I0o7K673j0LOIhkmbJoDkCLic4qmItd/RMYy8 zczHNo87fwtdFUMw326V2dgasezz3AQjEDWFIWHVHaIRl1TUEM3rzxfjoYTUWDakC5gN DMaclP4YdJVQX/2qhzY9SwOu/ZHhkYQzMik4cYPbg/AgImbw89AtnpLtBl+ACYLhss7q F1FA031nrwD3nfUHtyhb3nrUImMGhOubskGxZ1pN6w+ai79R6KxAhdsv2CZpyatcYE62 Q6pRn4hZ3Yna7Zs630l4ZZk3sJ3qdk7qgseQCvdQIR6vdxx3dmgsPU7oPnFBV2BhUXTc +jOQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1748940269; x=1749545069; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=NwV52I+ZDFoswRBJpTFUuXV7mNweCfVv8aNB45I6I0I=; b=ZdGnE6DTgEUU5stAuYaCv3+flWgsC8CcppY7GdCjKr1RQb47kYn/FJ/CHurB+Lnv2m 5Yzp/RFIagAC3EqjFJ4YI0UI5qOtYIDDskRlkNu4M5dw+jHhPCieINkb9AKsp70v5qkp incGcMsIQ5TFHpvJjIZLP7NmYiQvRhuAoklzOjklgZ3k9ZrFwJnT8VLAlhZRuPWSZQw9 cNzdk0bP5HUkURMRvwOjABwgJZsAVTWUkNaYSRKUGDcZkR8MEYGHyl+h+qZTj+4cSbWF 3UWgRaKM/BDpuF5aOnYwLopQTYvOXt/MriLvQiPBD4i52QTUlv6qi592yFkHeLs9oCn4 BT5w==
X-Gm-Message-State: AOJu0YwVxvB+91VZLm3CPkv86IdBoJOg/M9wlhKESfqLVaZtSxuYq37R zkK8xri1km/6LF7evKFPdNo5gF2qn021vp78wu/LW/WMRL8yLuHrM1vXKPAew7zYG4dusUtQ84T NSu0n8jabWmtQyy6IeTfOtuNTPKxn4j6OEwLm1jy2m1XygThuq7NX
X-Gm-Gg: ASbGncv5C9NqVf41YrycNj1nwakzdWbruwEuiomBCzAtqzsWuhiYNOh7JoZnZaBgrq+ nLS2kwahFkbNRl3DDMsQ6xdgPZLC48ZGo1Nq6jrU+F5tiFx/amPmgSCpw8PdgoQ6S+8NPeONApa 0dZ54q7reL4as2ew073CNsI6R2qoirpjdtf2q3Is8sqcKpIQVt8O7qzYehQn80eW0=
X-Google-Smtp-Source: AGHT+IFVfQ/avsZlxfJhm6fpCGtUfKHIge7vRsvDYe4cURAJO7HRoVKM2qxpsh8MLc3knD5UeHWdNqrBcUhI4LOw/B4=
X-Received: by 2002:a05:6820:270a:b0:60b:a7d2:f993 with SMTP id 006d021491bc7-60dc37b2e56mr7675978eaf.7.1748940269090; Tue, 03 Jun 2025 01:44:29 -0700 (PDT)
MIME-Version: 1.0
References: <31fe9f16-b070-443e-8971-9e16753b2cf6@huawei.com> <6.2.5.6.2.20250603002416.0abeb338@elandnews.com>
In-Reply-To: <6.2.5.6.2.20250603002416.0abeb338@elandnews.com>
From: George Michaelson <ggm@algebras.org>
Date: Tue, 03 Jun 2025 18:44:18 +1000
X-Gm-Features: AX0GCFscHpkptBTG5pNq8a6CbNENdViI1McFzYFOFrvbzn75V_O3o8cZj9Jwo4Y
Message-ID: <CAKr6gn2S1F-DYrnS4UjtiROpsetd_2Tv60vsamOU5K0ZZeG6Sg@mail.gmail.com>
Subject: Re: Required Google Account to review an IETF meeting. Really?
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000790a1e0636a6e3b3"
Message-ID-Hash: H53E4VPSRVILVFX3ENM3NK72NBKWPVE7
X-Message-ID-Hash: H53E4VPSRVILVFX3ENM3NK72NBKWPVE7
X-MailFrom: ggm@algebras.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CojZjKEAnmBeG-jnQwkqHqqXn6o>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>
I think without being overly legalistic we're blurring distinctions between publicly freely available and available without registration and/or identity. I don't like the change in behaviour by YouTube either. (In a purely personal capacity, this hasn't been discussed by the LLC Board) George On Tue, 3 June 2025, 6:18 pm S Moonesamy, <sm+ietf@elandsys.com> wrote: > Hi Benoit, > At 08:09 AM 28-05-2025, Benoit Claise wrote: > >I want to listen to an IETF interim meeting recording. > >Note: in this case, an NMOP interim meeting to create the meeting minutes. > > > >So I am logged in the datatracker, I follow the link from > >https://datatracker.ietf.org/wg/nmop/meetings/ and click on the > >Meetecho session recording, which leads to the ietf.org site, > >specifically > >https://meetecho-player.ietf.org/playout/?session=IETF-NMOP-20250521-1400 > >And now, I received the message that I must have a Google account to > >view this video: "Sign in to confirm you're not a bot" > > > >I don't believe this is right to force me to sign me into YouTube in > >order to see IETF-related content. > >Am I the only thinking along those lines? > > I tried accessing the URL yesterday. It did not require a YouTube > login. I did a quick search and found this: > https://discussions.apple.com/thread/255851527 > > There was a policy change in or around 2017 to provide better data to > the IETF community and leadership. There weren't a lot of objections > to that change. Anyway, the above is somewhat of a different > issue. The IETF Administration LLC's video hosting service might be > having some difficulty distinguishing between people and automated > harvesters. I don't see why I should log into a service to view > something which is described as "publicly available". > > Regards, > S. Moonesamy > >
- Re: Required Google Account to review an IETF mee… Stephen Farrell
- Re: Required Google Account to review an IETF mee… John C Klensin
- Required Google Account to review an IETF meeting… Benoit Claise
- Re: Required Google Account to review an IETF mee… Robert Sparks
- Re: Required Google Account to review an IETF mee… Robert Sparks
- Re: Required Google Account to review an IETF mee… Andy Ringsmuth
- Re: Required Google Account to review an IETF mee… Benoit Claise
- Re: Required Google Account to review an IETF mee… Ross Finlayson
- Re: Required Google Account to review an IETF mee… Job Snijders
- Re: Required Google Account to review an IETF mee… Christian Huitema
- Re: Required Google Account to review an IETF mee… John Levine
- Re: Required Google Account to review an IETF mee… Livingood, Jason
- Re: Required Google Account to review an IETF mee… Stephen Farrell
- Re: Required Google Account to review an IETF mee… Rob Sayre
- Re: Required Google Account to review an IETF mee… John C Klensin
- Re: Required Google Account to review an IETF mee… Rob Sayre
- Re: Required Google Account to review an IETF mee… Andy Ringsmuth
- Re: Required Google Account to review an IETF mee… John Levine
- Re: Required Google Account to review an IETF mee… Russ Housley
- Re: Required Google Account to review an IETF mee… John C Klensin
- Re: Required Google Account to review an IETF mee… Andy Ringsmuth
- Re: Required Google Account to review an IETF mee… Joel Halpern
- Re: Required Google Account to review an IETF mee… Michael Richardson
- Re: Required Google Account to review an IETF mee… Ross Finlayson
- Re: Required Google Account to review an IETF mee… John Levine
- Re: Required Google Account to review an IETF mee… Nick Hilliard
- Re: Required Google Account to review an IETF mee… Stephen Farrell
- Re: how painful is it to use our web sites, was R… John R Levine
- Re: Required Google Account to review an IETF mee… Rob Sayre
- Re: Required Google Account to review an IETF mee… Joel Halpern
- Re: Required Google Account to review an IETF mee… Rob Sayre
- Re: Required Google Account to review an IETF mee… Jeffrey Walton
- Re: Required Google Account to review an IETF mee… Rob Sayre
- RE: Required Google Account to review an IETF mee… Antoine FRESSANCOURT
- Re: Required Google Account to review an IETF mee… Michael Richardson
- Re: Required Google Account to review an IETF mee… Benoit Claise
- Re: Required Google Account to review an IETF mee… John R Levine
- Re: how painful is it to use our web sites, was R… Livingood, Jason
- Re: Required Google Account to review an IETF mee… S Moonesamy
- Re: Required Google Account to review an IETF mee… George Michaelson
- Re: Required Google Account to review an IETF mee… Rob Sayre