IETF Logo Mail Archive

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

Phillip Hallam-Baker <phill@hallambaker.com> Tue, 16 August 2022 15:50 UTC

Return-Path: <hallam@gmail.com>
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 B8DB3C1524DA for <ietf@ietfa.amsl.com>; Tue, 16 Aug 2022 08:50:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.409
X-Spam-Level:
X-Spam-Status: No, score=-1.409 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no autolearn_force=no
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 GgQ-HHVmFSSf for <ietf@ietfa.amsl.com>; Tue, 16 Aug 2022 08:50:12 -0700 (PDT)
Received: from mail-ot1-f45.google.com (mail-ot1-f45.google.com [209.85.210.45]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 BE660C157B5F for <ietf@ietf.org>; Tue, 16 Aug 2022 08:48:08 -0700 (PDT)
Received: by mail-ot1-f45.google.com with SMTP id h9-20020a9d5549000000b0063727299bb4so7678926oti.9 for <ietf@ietf.org>; Tue, 16 Aug 2022 08:48:08 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=W734a5NHpeJYYeJ7vJahLLmmhgpyTDVtta0kQuVpxQ4=; b=UvwA58dc/iOvVxqWB34ajksjqHaWInOYm4Rztg+vdTnHqBGtDDeN+PFLIwpj151Rhn 2LudDRaGOJ6cjCPzwS5fBaWDKRHNZV5e9OL2iXb8Kg95Sv7djMFcs3z26u9MWNUXcfk/ VYS//oZeYHV8eSICSbhypiDtzC+/2vH4XcZAiYEvAyboemGRRtGYE0s68vnVEfcLhhdh BWz03HjPntHu+pP7v7Un3XceCdoURcxTeuwyRiGnINVKDi9s8qtviAm/iQwnCU7+Jez4 wYOhAbjPaVYiiMfhcxa8Z0MQogkmE+4QFxAaenL8rnXsieASLGJ8n8Wom2x0gx5C8wva 09hQ==
X-Gm-Message-State: ACgBeo3Wq1aSRCXFR/s/PTavPAzj4K+gVgYzB8XjOyNAHnyJkblv7Vlw EqJgAjGyPee4QNm5eQzcOO944jKiB4VzXI2tZUI=
X-Google-Smtp-Source: AA6agR5R8hlNEQBiO8+h9Dt8gfrEQjrvv0jwXpoCXR8AnRu0B6QmqJe45CPzN9A3wDXatrtq6xBT0m1cUOao+ORWZMU=
X-Received: by 2002:a9d:63ce:0:b0:638:dadc:8ce0 with SMTP id e14-20020a9d63ce000000b00638dadc8ce0mr336481otl.93.1660664887765; Tue, 16 Aug 2022 08:48:07 -0700 (PDT)
MIME-Version: 1.0
References: <CAMm+LwgjBZYufVWUO47jVZjJ2Ae=F7OCarraLhmCszpBfjtK3A@mail.gmail.com> <8703.1659651478@localhost> <YvpmdkJxfKylqL1O@faui48e.informatik.uni-erlangen.de> <4878.1660581247@localhost>
In-Reply-To: <4878.1660581247@localhost>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Tue, 16 Aug 2022 11:47:58 -0400
Message-ID: <CAMm+Lwj2_kD8jWVQtXhgiyq9=Uw9pvPK_VbXjggQttbNjNVn3Q@mail.gmail.com>
Subject: Re: The Sheraton was a good choice for IETF 114 but....
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: Toerless Eckert <tte@cs.fau.de>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b9f0e905e65dac3a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FIuH-eoAEJULG0dRp1_RAaCzY6U>
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: Tue, 16 Aug 2022 15:50:12 -0000

On Mon, Aug 15, 2022 at 12:34 PM Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> 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.
>

That is thinking about functionality. I want the seamless experience from
booking through to checkin through to checkout.

Don't think about 'how'.

v2.23.0 | Report a Bug | By Email