Re: The Sheraton was a good choice for IETF 114 but....

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 15 August 2022 16:34 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B763C1524C9 for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2022 09:34:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.707
X-Spam-Level:
X-Spam-Status: No, score=-1.707 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=sandelman.ca
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fp-mZ64RIC0T for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2022 09:34:15 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31151C1524D9 for <ietf@ietf.org>; Mon, 15 Aug 2022 09:34:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 616E838A7C; Mon, 15 Aug 2022 12:53:42 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id YUobT5rNL-wE; Mon, 15 Aug 2022 12:53:37 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 6C22E38A87; Mon, 15 Aug 2022 12:53:37 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1660582417; bh=DV1741vO7yEZPjq+UAyAEJSiTiBFXW29bP9TPTT9fMw=; h=From:To:Subject:In-Reply-To:References:Date:From; b=R8bter3Wz2hh9v0bLr36EHBLbuqLbQVr6ejJFuCC3RP3bX0sMB2+NcfUvVLjzOZe3 zqSpJ+kAItBvV+kNMDNMAqN4rq/foxnOS5v51H55qt/nFgDQL8vM8vk3RseuNee6f7 ErnlLXj4apkVnv+Q1Ko7Hu2YB6zWCZ2UOd2lNOEnw5qTgLHMW0IZ4c3AXzjzY9vlSh pR5DhA9YoYNUIE49Wko0u52OFRN1OTLz1dod1oiNQAYfpYuhE85NQezPtPbYjTQELB gTuDuWYg6X2qB/h76DQXEasvUd/Vx/p0/89/3zXWSE6GdRyqDB6BJYkkOte42YxznQ vYHUGsUN/jfHg==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id EE6A397; Mon, 15 Aug 2022 12:34:07 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Toerless Eckert <tte@cs.fau.de>, Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: The Sheraton was a good choice for IETF 114 but....
In-Reply-To: <YvpmdkJxfKylqL1O@faui48e.informatik.uni-erlangen.de>
References: <CAMm+LwgjBZYufVWUO47jVZjJ2Ae=F7OCarraLhmCszpBfjtK3A@mail.gmail.com> <8703.1659651478@localhost> <YvpmdkJxfKylqL1O@faui48e.informatik.uni-erlangen.de>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Mon, 15 Aug 2022 12:34:07 -0400
Message-ID: <4878.1660581247@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NLhy2LgP-X07RB3ZP6ghs1q747w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2022 16:34:19 -0000

Toerless Eckert <tte@cs.fau.de> wrote:
    > I was thinking more of a one-time-password generator for streaming
    > accounts, like there are with good banks virtual credit card numbers,
    > where you upfront can configure a period of validity, such as a week,
    > and maximum charge against it, and number of transactions.

Yes.
Any password with enough entropy to be useful is pretty much impossible to
type on some screen keyboard using the arrow pad on a remote.
Plus what PHB said about turning ones password over to unknown device.

This is a place where TIGRESS might be able to do some work, where the TV
creates a mailbox, displays the mailbox location as a QR code, and you scan
from the phone with a *wallet* app.
This is done today with some youtube players on TVs already.

    > Then again: i can live perfectly fine without password phishing on
    > hotel TV, but no cappuchino after 10AM in the Hotel bar, that was
    > performance impacting.

Being able to remote attend a session from my hotel room with the audio on
the TV set was pretty nice.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide