Re: [106attendees] Social event

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Tue, 19 November 2019 09:16 UTC

Return-Path: <prvs=1226fef138=jordi.palet@consulintel.es>
X-Original-To: 106attendees@ietfa.amsl.com
Delivered-To: 106attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B95CF12081F for <106attendees@ietfa.amsl.com>; Tue, 19 Nov 2019 01:16:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
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 JzIDBf72nC55 for <106attendees@ietfa.amsl.com>; Tue, 19 Nov 2019 01:16:38 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 858A71200C1 for <106attendees@ietf.org>; Tue, 19 Nov 2019 01:16:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1574154997; x=1574759797; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To: Mime-version:Content-type; bh=QvmWwsUxDM48/PU6JruchWm7tNK5a1I3V6 oqYV3SOT8=; b=PfCQEnxv4peUu/3rYX4Nr5ZJkYuYlLtdOqMo6zkuO1hDFtsHsC FLGxSqysXyFKBoFJYVnCVYkmg1MDB3PGiFARbfUHXLIVIBzVuPoeokvfcKBk6iLS cgg4JvEbDP3mA0yoCxZAq+piVg+TNGH3360+HA7sJ3wOEA/8yQ16rgl38=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Tue, 19 Nov 2019 10:16:37 +0100
X-Spam-Processed: mail.consulintel.es, Tue, 19 Nov 2019 10:16:36 +0100
Received: from [172.20.4.214] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50006472845.msg for <106attendees@ietf.org>; Tue, 19 Nov 2019 10:16:35 +0100
X-MDRemoteIP: 10.8.10.10
X-MDHelo: [172.20.4.214]
X-MDArrival-Date: Tue, 19 Nov 2019 10:16:35 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1226fef138=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: 106attendees@ietf.org
User-Agent: Microsoft-MacOutlook/10.1f.0.191110
Date: Tue, 19 Nov 2019 17:16:25 +0800
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <106attendees@ietf.org>
Message-ID: <12FD8C50-3105-4A1D-A7FF-07BFE0C4FF90@consulintel.es>
Thread-Topic: [106attendees] Social event
References: <CAMm+Lwgx9PTQrPo_sWcUxswEY97eBBGco9sgKSvn_HjQnD9JyQ@mail.gmail.com> <VI1PR0701MB267163382A39CFD0132C62DB924C0@VI1PR0701MB2671.eurprd07.prod.outlook.com>
In-Reply-To: <VI1PR0701MB267163382A39CFD0132C62DB924C0@VI1PR0701MB2671.eurprd07.prod.outlook.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3657028590_536240039"
Archived-At: <https://mailarchive.ietf.org/arch/msg/106attendees/icwbrv38VVW7ISFz5ce_I9hytjg>
Subject: Re: [106attendees] Social event
X-BeenThere: 106attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list of all 106 attendees for official communication <106attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/106attendees>, <mailto:106attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/106attendees/>
List-Post: <mailto:106attendees@ietf.org>
List-Help: <mailto:106attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/106attendees>, <mailto:106attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2019 09:16:44 -0000

Actually this is a generic comment, not only for the social, but for all the week in the venue …

 

Can we as IETF, have a stricter control of the usage of the AC in our venues, and make it a contractual requirement, showing that energy conservation is important for us, and we don’t want to have freeing rooms, especially in hot places where you try to avoid heavy clothes?

 

If a venue is not able to match it, we should reconsider that venue for future meetings. It is insane to waste energy and need to bring coats!

 

I rather prefer to have a “closer” temperature as the outdoor one (I’m not meaning be sweating), with I can partially solve with summer clothes, than being frozen and get a cold in every IETF meeting, unless the IETF or the venue want to pay for the medical and associated expenses to everyone.

 

Regards,

Jordi

@jordipalet

 

 

 

El 19/11/19 17:06, "106attendees en nombre de Maisonneuve, Julien (Nokia - FR/Paris-Saclay)" <106attendees-bounces@ietf.org en nombre de julien.maisonneuve@nokia.com> escribió:

 

I’m told it should be about 20°C.

Some might find it cold considering the outside weather.

Surely we could save a bit of AC.

Julien.

 

From: 106attendees <106attendees-bounces@ietf.org> On Behalf Of Phillip Hallam-Baker
Sent: Tuesday, November 19, 2019 9:44 AM
To: 106attendees@ietf.org
Subject: [106attendees] Social event

 

Does anyone know if tonights social event is going to be too hot or too cold?

-- 106attendees mailing list 106attendees@ietf.org https://www.ietf.org/mailman/listinfo/106attendees 



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.