Re: [Ext] [irsg] Minutes being messed with?

Paul Hoffman <paul.hoffman@icann.org> Thu, 08 August 2019 19:40 UTC

Return-Path: <paul.hoffman@icann.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42D6B120183 for <wgchairs@ietfa.amsl.com>; Thu, 8 Aug 2019 12:40:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 HzXfU74tzAMp for <wgchairs@ietfa.amsl.com>; Thu, 8 Aug 2019 12:40:28 -0700 (PDT)
Received: from out.west.pexch112.icann.org (out.west.pexch112.icann.org [64.78.40.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 452DF120147 for <wgchairs@ietf.org>; Thu, 8 Aug 2019 12:40:28 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 8 Aug 2019 12:40:25 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1473.005; Thu, 8 Aug 2019 12:40:25 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: "wgchairs@ietf.org" <wgchairs@ietf.org>
Subject: Re: [Ext] [irsg] Minutes being messed with?
Thread-Topic: [Ext] [irsg] Minutes being messed with?
Thread-Index: AQHVTiBOO1vRZTzxmUaFNoSL7kgNU6byG1eA
Date: Thu, 08 Aug 2019 19:40:25 +0000
Message-ID: <B0A1E5CF-8E79-42B0-BCE4-A3D5A6B71548@icann.org>
References: <2C180C92-9DE3-416B-8A6B-7765BCAEEDB1@eggert.org> <DB7PR07MB51483F20F4261CDE848E3EAFE0DD0@DB7PR07MB5148.eurprd07.prod.outlook.com> <1f00cab2-991f-7f0c-f061-a692f10cad16@gmail.com> <A6240C58-14C4-4900-A9CD-86779D7A44BC@eggert.org> <DB7PR07MB51487A4B4E8F38979893FFE4E0DD0@DB7PR07MB5148.eurprd07.prod.outlook.com> <92621f1a-7050-1558-86dc-1836e17c6f7c@bluepopcorn.net> <473915be-8fe1-ba82-fb30-8bd05751cb32@levkowetz.com> <CAOdDvNqDZN6kR_jv+Em3PoSR9sWx8U2JTLWFzJtCVY=QZrsS3A@mail.gmail.com> <7466_1564562703_5D41550F_7466_455_3_65b0b515-b273-177b-84ce-210ef716f0cd@orange.com> <DBFDF146-C2AD-49A8-AED0-B7112733D29E@gmail.com> <A09242D6-B4A5-49AE-9CFD-78E34FB638FE@tzi.org> <B8AE42B2-8A28-4041-AD2F-0136900BAE4F@gmail.com> <8B059BA9-B235-4A1E-9AC2-5339C1C9CE13@akamai.com> <7df564fa-5940-4c92-1d73-856bffc81ce1@bluepopcorn.net> <F7ECF7DB-9639-40EA-9774-82DB940FA342@tislabs.com> <42E6A418-879F-482B-BDAD-66D4DD46475C@gmail.com> <693C8CDA-76DE-4C6F-B19D-7500C962C66F@tzi.org> <1032b409-1905-ec3a-b271-f2a23ca4beac@nostrum.com> <241D5A95-D3DC-41C7-9AB8-D2260F0A0AAA@tzi.org> <2D09D61DDFA73D4C884805CC7865E6114E25BBE0@GAALPA1MSGUSRBF.ITServices.sbc.com>
In-Reply-To: <2D09D61DDFA73D4C884805CC7865E6114E25BBE0@GAALPA1MSGUSRBF.ITServices.sbc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <65119D89C548954386C6652CF1D2687B@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/3ZLqVlLyR93HJSDj9uMhURYjdd4>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2019 19:40:29 -0000

[ As the person who started this thread... ]

There is a good chance that the (temporary) damage happened after the meeting. Thus, knowing this in advance, I might export the results at the end of the meeting.

Even if I don't, as long as the history function works, I can alway reverse the damage.

Given that, I don't see any good reason for the proposed premature optimizations.

--Paul Hoffman