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

Hesham ElBakoury <helbakoury@gmail.com> Thu, 04 August 2022 20:39 UTC

Return-Path: <helbakoury@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 445BEC157901 for <ietf@ietfa.amsl.com>; Thu, 4 Aug 2022 13:39:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.104
X-Spam-Level:
X-Spam-Status: No, score=-1.104 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 utcRID-iGrQd for <ietf@ietfa.amsl.com>; Thu, 4 Aug 2022 13:39:33 -0700 (PDT)
Received: from mail-qv1-xf2a.google.com (mail-qv1-xf2a.google.com [IPv6:2607:f8b0:4864:20::f2a]) (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 57685C14CF0C for <ietf@ietf.org>; Thu, 4 Aug 2022 13:39:12 -0700 (PDT)
Received: by mail-qv1-xf2a.google.com with SMTP id u8so491835qvv.1 for <ietf@ietf.org>; Thu, 04 Aug 2022 13:39:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=wJQSzow8IA/s05/7ksHDvPWY8IECW/FhzDWloS0bQ5E=; b=hFFlztl0FYpt+/YfM1WWctG0vIEzTPyv5DlGPcLToUxJ0/EKg46JQ6hFkdhSKc8L2o XjmRiul7gYm0IknE+BaBKtTtch42zZoQT43ZVNZ9CgujHvTHHtnqm6wCCrXqxH9gPcte lwUx+HZ5jydvzXnH7htQQAjOiOuRxgWndY5PCwSsZKJy415uoRr0mUM+RA9BQIZEixuL 1Oou3dbxNCehrnLNptX7dn30bh6ycoV+vLBX1XpReu2iOOp6NVowpeDGUjP62C+UPVtX /DUrNVn8yOtZ+2fG4IAm+AyLpkX9wmbOgyX8zJ5T6UP1d7z/9r/2kG7np4QlDJKSyf7+ D8JQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wJQSzow8IA/s05/7ksHDvPWY8IECW/FhzDWloS0bQ5E=; b=tp+bfe/bziH/eS9vilRBZseyyyCH249QDpTJxbLTRYG9yFJCQjG+yqc2FVHowN0IHS O0rZUCjMSRPrR/9TXe7PB8huHZlIDPA9xEVZjR3hVcsIACarP8BWdM9eaqx+JwczbJMm rx11j/1zvLQs2zYigaw6wfSaIkJic7MJlUxKCWhx+Z4cqLopBvpy6wETcVsPDtpKnre5 dOMdKYU+0cUX3+VF1Ccc1KVZ5cifUHe3Ise6lj+jcc/yBFBnZ+IPaunQpVdhudnexcuX uMSGzSIvS/3g1RYxe2pI2FgPKuk92OhuiN0QZi7RlTm448t5S0GxfEYflpS5CQAXC3jp jqfA==
X-Gm-Message-State: ACgBeo3lukfb71A1xXCjR+TASGJxzTBlF0Nl7mTFiq0lkYI3M6rTobOT RDNnljy0vKit9CjZ37ffHE8NWAgnP2t0UyOqfMMc9Vxg
X-Google-Smtp-Source: AA6agR6gnsHn8OYrRMeXIDPqwisC1+HwAj4J9lkPoJxI/DUQ/l9c7kRpX7AqNJ704MZXSqbmkN5pmm0OcfwWRwwTnv4=
X-Received: by 2002:a05:6214:21cc:b0:476:10cc:f928 with SMTP id d12-20020a05621421cc00b0047610ccf928mr3136670qvh.14.1659645550998; Thu, 04 Aug 2022 13:39:10 -0700 (PDT)
MIME-Version: 1.0
References: <CAMm+LwgjBZYufVWUO47jVZjJ2Ae=F7OCarraLhmCszpBfjtK3A@mail.gmail.com> <6D2064F9-D596-4CFA-B48C-27CCCC98FABA@me.com> <CAMm+Lwj5J=k3Pi1M8Vq002RRJGQ56GC5rsA1GN1xORHOvQyCMQ@mail.gmail.com>
In-Reply-To: <CAMm+Lwj5J=k3Pi1M8Vq002RRJGQ56GC5rsA1GN1xORHOvQyCMQ@mail.gmail.com>
From: Hesham ElBakoury <helbakoury@gmail.com>
Date: Thu, 04 Aug 2022 13:38:58 -0700
Message-ID: <CAFvDQ9rDR-=RsSFUMf52YNjuKyyp6kvm2sBW4iFY74RO8MXrnQ@mail.gmail.com>
Subject: Re: The Sheraton was a good choice for IETF 114 but....
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: Ole Jacobsen <olejacobsen@me.com>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000085396205e57057a0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/z63pGgxsJ5SCGd1amvcsyhmaXz8>
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: Thu, 04 Aug 2022 20:39:38 -0000

The noisy air conditioner has a mind of its own. It  wakes up and goes to
sleep based on uncontrolled timer which does not take into account whether
I am sleeping or awake. Perhaps there is away I do not know to control this
timer to suit my needs.

Hesham



On Thu, Aug 4, 2022, 1:29 PM Phillip Hallam-Baker <phill@hallambaker.com>
wrote:

> I have never really had cause to think about this before as this is the
> first time I have been MeetEchoing into WGs from inside the conference
> hotel. This was largely because I did other things during lunch breaks and
> went to my room to eat so as to comply with the mask requirement.
>
> On Thu, Aug 4, 2022 at 4:08 PM Ole Jacobsen <olejacobsen@me.com> wrote:
>
>> Once upon a time in a conference hotel, far, far away (Stockholm).
>>
>> The IETF used camera feeds from a couple of the larger meeting rooms and
>> provided this
>> on the in-house hotel channels. Work really nicely, but has of course
>> been somewhat
>> supplanted by our own devices watching YouTube livestreams or Meetecho.
>>
>> I like the idea of a general "preferences profile" ...
>>
>> Ole
>>
>> On Aug 4, 2022, at 12:27, Phillip Hallam-Baker <phill@hallambaker.com>
>> wrote:
>>
>> I thought the Sheraton was a fine choice of hotel. There were some
>> limitations due to the pandemic and the Marriott and Hilton brands offer
>> slightly nicer decor but at this point I have spent so much time living in
>> hotels that I really don't care very much about the precise quality of the
>> granite surround of the sink.
>>
>> There was one thing that did strike me as having room for improvement.
>> And here, the answer lies in ourselves.
>>
>> If you used the in-room TV rather than ignoring it (as I usually do), you
>> will have noted that not only did it provide an easy means of plugging in a
>> HDMI cable (hooray!), it also provided an easy way to connect to my
>> NetFlix, Pandora etc. subscriptions. Another thing I very much appreciated
>> in the Sheraton is that they did not reset my room thermostat to freezing
>> each day which seems to be the norm in US hotels.
>>
>> Now don't get me wrong, that is really really good, much better than I
>> have seen at any other hotel. And yet...
>>
>> What if...
>>
>> What if when I book a hotel room or rent a car, it could be automatically
>> provisioned with all the subscriptions, etc. etc. that I hold?
>>
>> Also, rather more generally, I do not actually have different preferences
>> for room temperature according to the season (they vary by time of day but
>> not by much). Many hotels seem to think I want the room to be freezing cold
>> in the summer and boiling hot in winter. If I wanted to do that, I would
>> simply move to Australia and not bother with HVAC at all.
>>
>> So if that information could simply be downloaded into the thermostat,
>> that would do nicely.
>>
>> One more thing which is a bit more IETF specific (but not a lot) is that
>> the big limitation for using a TV for teleconferencing right now is that
>> (1) TV's don't have cameras and (2) I am absolutely not going to buy any TV
>> that does have a camera unless it is fully visible and comes with a
>> hardware lens cover.
>>
>> So I want to be able to use my mobile phone camera for video in a WebRTC
>> interaction taking place on a separate device. Not just in meetecho, as a
>> general WebRTC capability.
>>
>>
>> These all seem to me to be problems that require a mixture of open
>> specifications and some intelligent consideration of security concerns.
>>
>>
>> Ole J. Jacobsen
>> Editor and Publisher
>> The Internet Protocol Journal
>> Office: +1 415-550-9433
>> Cell:   +1 415-370-4628
>> Web: protocoljournal.org
>> E-mail: olejacobsen@me.com <olejacobsen@me.com>
>> E-mail: ole@protocoljournal.org
>> Skype: organdemo
>>
>>
>>
>>