From nobody Wed Jul 5 16:29:48 2017 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 505F212ECCB for ; Wed, 5 Jul 2017 16:29:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.15 X-Spam-Level: X-Spam-Status: No, score=-1.15 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_SPAM=0.5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, TVD_SPACE_RATIO=0.001] autolearn=no 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 loyOQ5cmr7jE for ; Wed, 5 Jul 2017 16:29:45 -0700 (PDT) Received: from NAM04-CO1-obe.outbound.protection.outlook.com (mail-oln040092010051.outbound.protection.outlook.com [40.92.10.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1303130A93 for ; Wed, 5 Jul 2017 16:29:41 -0700 (PDT) Received: from SN1NAM04FT031.eop-NAM04.prod.protection.outlook.com (10.152.88.53) by SN1NAM04HT134.eop-NAM04.prod.protection.outlook.com (10.152.89.74) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1199.9; Wed, 5 Jul 2017 23:29:40 +0000 Received: from CY4PR13MB1255.namprd13.prod.outlook.com (10.152.88.59) by SN1NAM04FT031.mail.protection.outlook.com (10.152.88.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1220.9 via Frontend Transport; Wed, 5 Jul 2017 23:29:41 +0000 Received: from CY4PR13MB1255.namprd13.prod.outlook.com ([10.173.179.17]) by CY4PR13MB1255.namprd13.prod.outlook.com ([10.173.179.17]) with mapi id 15.01.1240.013; Wed, 5 Jul 2017 23:29:40 +0000 From: Gabriel morin To: "tools-discuss@ietf.org" Thread-Topic: Update-0.34 feedback Thread-Index: AQHS9eaSehIG+6/2K0qCQikYyHua+A== Date: Wed, 5 Jul 2017 23:29:40 +0000 Message-ID: Accept-Language: fr-CA, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=live.ca; x-incomingtopheadermarker: OriginalChecksum:5D4B6FF0F2A2AE638DF972CE93984721F2046B66790F08A3129FC300EE5DDDC9; UpperCasedChecksum:C0CB1AAA0231F26B564485F64D6F7E8AB051789A50CE99E04E8B52075B5BACEE; SizeAsReceived:7030; Count:43 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [TzeKPzGc8uA8FIysEAKy7wKffydQ0Dgt] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; SN1NAM04HT134; 7:Kq4MhgdLdjHl+Pg8Qkjnl6BwGw9Sv94nSTD02Z17Bt72fOMvoznLu711fxULOJrRkGOFW5VMFm54Wm6mppjdqg6wdq5W6ue/0Gd+zDXzNeuLo6F6s7DOKN7Ye8EJUIGgLzmP5cJG/soAL++EcurZ9uAPp4mAthSrmWI2GdX5aLfI/WXCGDPKCxe+sH+iLtOM6uhfcz/3Gl1z3560k0Ad4kwkcydhRF1/C8f8RlcHUZQjSQ2skSdLVyw0FWAWjqcgS3nI+hSzzYVq1pVTV45h9WzPf9QjCMMr6ZJLFV8hSV4GVapWzvpdXJ5DM9ZupJUNMiuN85k07yngTookoXvzFjjJ/3oklRj8Ef1Clw6e/QQdTdfK+b7W5dila5RSQ68Htj03VmDlHcoraOu/dwUfo8u0bsc17FSeMNLbVtLlujjeMPBhTRTwJIdL65IY7Phq7vnwyVP8WgG5nODc/2gtC5wB85Hu8/Ape3hzdsijlqIg9UQlHs0oujPL21PPiTFz9xYgFR28HcdyiVHVTQphUQai6EKRSetv5GNwBIJV/0l4qx0LUP/aROzYG2H/hXaLhIMvsZaDBuGRtH3nUR3Jlcifnl1egNo3GWtt2+vCCDmpBxwBzVqMouXJQjoov8EmNMwbEAHsgbfqap6ilTPB9krswp8pupmx2hbZSS8srSDe5WaoPx2KMANMuAY26Yq2S9LDtU9BtIIShT43OUofjJOIvpGVyHgqYGC0XJpOuk8NaletIBcjB2JnK8S+W8sY+mH+0O+mszj2EcGpOgX8Cw== x-incomingheadercount: 43 x-eopattributedmessage: 0 x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:SN1NAM04HT134; H:CY4PR13MB1255.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; x-ms-office365-filtering-correlation-id: 2870fe85-0f33-4172-6355-08d4c3fdb538 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(300000503095)(300135400095)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1603101448)(1601125374)(1701031045)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:SN1NAM04HT134; x-ms-traffictypediagnostic: SN1NAM04HT134: x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(444000031); SRVR:SN1NAM04HT134; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:SN1NAM04HT134; x-forefront-prvs: 0359162B6D spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-ID: <7BAD27DAECF9E043A6A68D1A7B17BA16@namprd13.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Jul 2017 23:29:40.4359 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1NAM04HT134 Archived-At: Subject: [Tools-discuss] Update-0.34 feedback X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2017 23:29:46 -0000 pada Gab From nobody Thu Jul 6 10:28:13 2017 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FC1C13184F for ; Thu, 6 Jul 2017 10:28:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 1iXb5iSF3dpO for ; Thu, 6 Jul 2017 10:28:02 -0700 (PDT) Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E00B131848 for ; Thu, 6 Jul 2017 10:28:01 -0700 (PDT) Received: by mail-qk0-x230.google.com with SMTP id d78so8190219qkb.1 for ; Thu, 06 Jul 2017 10:28:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=zFrPSsgnuQPR1OWGNn0fKKlNFm1GOL+ozE3kHeYeyE8=; b=OJQno8LDoRJxQs+ENJgYlcScg6FruGJnJwxoVNKO5P9gkzTVEzVaZnmgFXKFPZN6X9 eWYgVePQKUhkJvlldUwOkpxBLVcLlp7NfupqBj71jeT4f3zg8lAWddd49Wv3mMIECFSm 5KKoDeEBw2UF0r7tPxQeyHuczcVD/SNJNcEO+Kqnoo/rPhLc1RBP0wGoKObzNr1GwoWd EcIC2DOx1/E0venkjS6wQrjKqhmK5ZLgG01T1AM5C52C5yUhSytEJQHjmGamXtrjkZOM 2bmXyhV9s7DuOXyQfbF6NC2GctWg1O7BcOaFnvrs79sdy3YzxZU4xzRfhYu4tx6rBQcy 3UMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=zFrPSsgnuQPR1OWGNn0fKKlNFm1GOL+ozE3kHeYeyE8=; b=Q0bjyO62hFdkOsFgFnk13jpd+n9lz3iB1BekK6IiSuxq7PaxvuV2yEp8XNSNwb8M0A vd6OtW0twcAM4grBH5aPsjWnkjxzJIEFFlhkJ4KQVaaqsoqvqKhsaHXhDwO8+rljo/ax k5RNI6EwBR5cZMtxQccahU59bKyMSn1LKYVICzddCjYL2Gf9TtZB7xUxAotKJEplB3h/ EEo1xms0s2WwrY4SEzZBL2J3TwkLcngi/RHKq5cW3LnSv900+sxdwnhWRjUIM2SUyKeo qqAxIAeVRIpzNDTVaubvG8G37NR/Z2h4SaYezmzir3SXitRz0ykNtKwbIzvOBFbqPX0H UNtA== X-Gm-Message-State: AIVw11026pANMkvl4kE+u2+imcaQmEetoPm3ot+fRnXqADwCX1effg+e n32rutUKpAbivf9XpbY= X-Received: by 10.55.115.69 with SMTP id o66mr34046639qkc.110.1499362080352; Thu, 06 Jul 2017 10:28:00 -0700 (PDT) Received: from [169.254.54.85] ([72.246.0.14]) by smtp.gmail.com with ESMTPSA id m187sm580438qke.17.2017.07.06.10.27.59 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Jul 2017 10:27:59 -0700 (PDT) From: "Aaron Falk" To: Tools-discuss Date: Thu, 06 Jul 2017 13:27:54 -0400 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_MailMate_31D7BE99-021D-44F4-A913-B95981DC3DA0_=" Content-Transfer-Encoding: 8bit X-Mailer: MailMate (1.9.6r5356) Archived-At: Subject: [Tools-discuss] Chrome odd wraps html-ized drafts X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2017 17:28:04 -0000 --=_MailMate_31D7BE99-021D-44F4-A913-B95981DC3DA0_= Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown Content-Transfer-Encoding: 8bit Has anyone else noticed [this](https://www.dropbox.com/s/fb4ky7yoxcl6ml5/draft-in-html.jpg?dl=0)? Very annoying, IMO. Looks fine in Safari, consistently bad wraps on Chrome. Reducing font size makes no difference. —aaron --=_MailMate_31D7BE99-021D-44F4-A913-B95981DC3DA0_= Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

Has anyone else noticed thi= s? Very annoying, IMO. Looks fine in Safari, consistently bad wraps= on Chrome. Reducing font size makes no difference.

=E2=80=94aaron

--=_MailMate_31D7BE99-021D-44F4-A913-B95981DC3DA0_=-- From nobody Thu Jul 6 10:37:37 2017 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6813131862 for ; Thu, 6 Jul 2017 10:37:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com 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 BBIamiRVkzsL for ; Thu, 6 Jul 2017 10:37:25 -0700 (PDT) Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 777FE131864 for ; Thu, 6 Jul 2017 10:37:23 -0700 (PDT) Received: by mail-qk0-x22e.google.com with SMTP id 16so8407477qkg.2 for ; Thu, 06 Jul 2017 10:37:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=bWx6ivoritYgvNBSiiLdGoYtlRrG9TzrJZAWj52jGqE=; b=NAQModnj+9LWyNUpOO0m5hpCONUinygiADvFuPHquPcxHdzkyhOsU9Ju1L8oCb1yl/ SfMhDmF1QU1EFpzIUf1ZRlo3LoYNjD0VUB6d7MIMbqZhN5I9y2lwysEHL0pZS9l2mo0V TMk7BmaBMCh0WUnhOYXOu5LCnWI1wRsgIVgpYiDNqRlP9kan/q01aJBWMCZ9qyE87J2+ nfFEIlsWaUjAHueOFLCULAUs4Wa9AMzNKUlfX+rDc86BseNuvZIVZwpEMtvuJjYqoWeZ 2wgxojuesIwIrqKHIyMM+VMtcR54VHCTJjinIC0YOh+tc8b/VxIkelqvvqeUP3WOW/xw cD1g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=bWx6ivoritYgvNBSiiLdGoYtlRrG9TzrJZAWj52jGqE=; b=HaXT1iSLq8VO/vzTti3XcEktFYMS5752JMrMFUv9880Y7TUI1N10s1bKbWPvVTkxns Z9jEvQZkJ8wVV+kMZ3TCyPmOqTr+O15yXFB1wYymIs86+R6DqbjZBLE6Atnv3JwK85xc QEIfznWYp+OiknizV113illkhqfCHhTlYNjAlg8wtcqLGiAPv/GKRs+lZmFZScJ4x1NZ M9oMcK0hBcB7sSHdeLUm5e7XXCO5voJnEJaYUIguInctPFiSHi5YhcyyxAA7y84/2u5X 6Zpa1acdxvRyLGn5I2PbIfvlwofQCKic8N/seeOj1rGdF4gz2J+fdyxbse3UoUJ9eRFc pIhA== X-Gm-Message-State: AKS2vOwOvXO4Tx5kokThb43btn9qe/9NbZYEriymfjnW1noBrS0ZwPK+ Op7ate0l4Ck3FoTW X-Received: by 10.55.155.141 with SMTP id d135mr57507474qke.11.1499362642595; Thu, 06 Jul 2017 10:37:22 -0700 (PDT) Received: from macbook-pro-6.ether.lede.home (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id l207sm563080qke.36.2017.07.06.10.37.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Jul 2017 10:37:21 -0700 (PDT) From: Ted Lemon Message-Id: <30BEA741-2174-459F-981E-95107EA19D3D@fugue.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_23AB07B2-8B48-41BC-86A9-2F10554E4587" Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Date: Thu, 6 Jul 2017 13:37:19 -0400 In-Reply-To: Cc: Tools-discuss To: Aaron Falk References: X-Mailer: Apple Mail (2.3273) Archived-At: Subject: Re: [Tools-discuss] Chrome odd wraps html-ized drafts X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2017 17:37:36 -0000 --Apple-Mail=_23AB07B2-8B48-41BC-86A9-2F10554E4587 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Jul 6, 2017, at 1:27 PM, Aaron Falk wrote: > Has anyone else noticed this = ? = Very annoying, IMO. Looks fine in Safari, consistently bad wraps on = Chrome. Reducing font size makes no difference. >=20 How about making your window wider? Is this on iPad? I just looked = at the same draft, and nothing I did was able to make it break, so it = sounds like maybe you're running an extension that's modifying the css = or something? --Apple-Mail=_23AB07B2-8B48-41BC-86A9-2F10554E4587 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii On Jul 6, 2017, at 1:27 PM, Aaron Falk <aaron.falk@gmail.com> wrote:

Has= anyone else noticed this? Very = annoying, IMO. Looks fine in Safari, consistently bad wraps on Chrome. = Reducing font size makes no difference.

How about = making your window wider?   Is this on iPad?   I just looked = at the same draft, and nothing I did was able to make it break, so it = sounds like maybe you're running an extension that's modifying the css = or something?

= --Apple-Mail=_23AB07B2-8B48-41BC-86A9-2F10554E4587-- From nobody Thu Jul 6 12:04:34 2017 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44D301317D4 for ; Thu, 6 Jul 2017 12:04:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 ZqsLIP8YLkbn for ; Thu, 6 Jul 2017 12:04:31 -0700 (PDT) Received: from mail-qt0-x231.google.com (mail-qt0-x231.google.com [IPv6:2607:f8b0:400d:c0d::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1768131558 for ; Thu, 6 Jul 2017 12:04:30 -0700 (PDT) Received: by mail-qt0-x231.google.com with SMTP id b40so10321464qtb.2 for ; Thu, 06 Jul 2017 12:04:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:embedded-html; bh=A8zfFg6/ZMarhzernVCM/vELDUzXyx7e+dWUD8lK9Rc=; b=uCmZ0/TN+wI4Ar1O4y4s/iSV+W7lAzfnn4yZlY1cq/8mc4iRZXMAumH/QyuqEf5xkP /b8XMB4svjGYR/5JN8RgObS3S/YhaG7W23d3f6d5M9U+foIakybwQkJwt6IDH66GuW5y /Kar0Xi9sNusAUYhCa8GXmzgul7wqoVMJVz4hDhfvmDc3jFQ2s3HzKOfqQDM3Xn6V/M3 RVDTH8Fi49Y2hjXDz1s67CcLSlOPJC4Z3BbSNbrpYMUW1YmKsSGhiZfUW4esYSSZ8Xcp njdNpGD54AL7M78rYuT12Nx+QxnguhMZ3OHwQ8G5GOfULvtpjUSaRlVxEf3m02lypXHi rkuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:embedded-html; bh=A8zfFg6/ZMarhzernVCM/vELDUzXyx7e+dWUD8lK9Rc=; b=ortUgvuxpDPiTok/SOKTqoR0ebusaa0aSlR+WvRWWtDufDQW2yVw8NXiw8WoIgIpiH RW2bR6PcKNlAL2rxf9RL8vQpUz9h4fe8/Ru4dpPh2ZsBAzK7QWyXD8DNmTyfYNdwIXbP JOnT2yuVZypHy/Hmm2v6bMBnrNS/2egiWI9ZeIoMk08yeKB6X0x8gRr37KAZAS7IgjSA Qlr3M0i6nFKHSaXXX0+PTqEdHm64kLUqaYVZc0BImW5oRucAvci4p+NMDTbiJAuj/9VU 3JRBxfd9AlN+znMdw7VLgXrYNJY2G8HukwXgjua04vh5QrCP4UPerOENToAH4efTm1BI lyFw== X-Gm-Message-State: AIVw111NxFNI8wRasYUQSR0lOQS6DI09aPuOx50pEvTWWYDzQptHHG8G U+P7fk8Ls4eXtPqxiGk= X-Received: by 10.237.32.196 with SMTP id 62mr21302471qtb.99.1499367870065; Thu, 06 Jul 2017 12:04:30 -0700 (PDT) Received: from [169.254.216.245] ([72.246.0.14]) by smtp.gmail.com with ESMTPSA id p36sm810615qtf.21.2017.07.06.12.04.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Jul 2017 12:04:29 -0700 (PDT) From: "Aaron Falk" To: "Ted Lemon" Cc: Tools-discuss Date: Thu, 06 Jul 2017 15:04:28 -0400 Message-ID: <22892E8C-EECF-46F7-A775-7D061E7FDAB5@gmail.com> In-Reply-To: <30BEA741-2174-459F-981E-95107EA19D3D@fugue.com> References: <30BEA741-2174-459F-981E-95107EA19D3D@fugue.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_MailMate_8C401FF1-9894-452F-BD3C-046AC3B89842_=" Embedded-HTML: [{"HTML":[390, 1245], "plain":[45, 516], "uuid":"06B1693F-0C6E-4616-9229-E721B5EB1C78"}] X-Mailer: MailMate (1.9.6r5356) Archived-At: Subject: Re: [Tools-discuss] Chrome odd wraps html-ized drafts X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2017 19:04:33 -0000 --=_MailMate_8C401FF1-9894-452F-BD3C-046AC3B89842_= Content-Type: text/plain; format=flowed On 6 Jul 2017, at 13:37, Ted Lemon wrote: > On Jul 6, 2017, at 1:27 PM, Aaron Falk wrote: >> Has anyone else noticed this >> ? >> Very annoying, IMO. Looks fine in Safari, consistently bad wraps on >> Chrome. Reducing font size makes no difference. >> > How about making your window wider? Is this on iPad? I just looked > at the same draft, and nothing I did was able to make it break, so it > sounds like maybe you're running an extension that's modifying the css > or something? Chrome Version 59.0.3071.115 (Official Build) (64-bit) MacOS Sierra 10.12.5 Wider window makes no difference, just adds white space. Smaller font makes no difference, just makes font smaller. Sigh. Turns out I had an extension on: > 
 Line Wrapper 1.0
> Enables line wrapping in 
 tags. Uncheck "Enabled" whenever you 
> want to revert to the default behavior.

--=_MailMate_8C401FF1-9894-452F-BD3C-046AC3B89842_=
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable








<=
p dir=3D"auto">On 6 Jul 2017, at 13:37, Ted Lemon wrote:




On Jul 6, 2017, at 1:27 PM, Aaron =
Falk <aaron.falk@gm=
ail.com> wrote:
Has anyone else noticed th=
is? Very annoying, IMO. Looks fine in Safari, consistently bad wraps =
on Chrome. Reducing font size makes no difference.
=
How about making your window wider?   Is this on iPad?   I just=
 looked at the same draft, and nothing I did was able to make it break, s=
o it sounds like maybe you're running an extension that's modifying the c=
ss or something?

=




Chrome Version 59.0.3071.115 (Official Build=
) (64-bit)

MacOS Sierra 10.12.5


Wider window makes no difference, just adds white space.<=
br>
Smaller font makes no difference, just makes font smaller.


Sigh.  Turns out I had an extension on:


<pre> Line Wrapper 1.0

Enables line wrapping in <pre> tags. Uncheck "Enabled" whenever you=
 want to revert to the default behavior.







--=_MailMate_8C401FF1-9894-452F-BD3C-046AC3B89842_=--


From nobody Thu Jul  6 14:36:17 2017
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BEA012EB9B for ; Thu,  6 Jul 2017 14:36:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.com
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 J9vejCVtFaEW for ; Thu,  6 Jul 2017 14:36:14 -0700 (PDT)
Received: from mail-vk0-x236.google.com (mail-vk0-x236.google.com [IPv6:2607:f8b0:400c:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43C75129B43 for ; Thu,  6 Jul 2017 14:36:14 -0700 (PDT)
Received: by mail-vk0-x236.google.com with SMTP id 191so7882322vko.2 for ; Thu, 06 Jul 2017 14:36:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=DQDV04MkNsA/u9xuCBTehdYReIXTvnJCQV1I1n1dETE=; b=tsf4kTgj9BhJjlMcUJMEuqv42CXEmBWAbjcL1Bv3uKTPhqw8uMor2Dvw/5BLMIt6Y8 hOz1ywHxhWBHTnKPTh2JjOhpXyMiWXIOQF7EiM/qZEfbFOy4RTyVzfC6ER2oSpfi89Gp kk+Lem0J58O4I0w6DodWR+t5WjbbK6imtfowwsc4Hreu8pngbGfB+as9WARoPNRo5eb6 ILVcWNErOp7yC+TByzCglthLVbYxZoXSsAwku7ahrAy6MwmWPh3Sldx70CxuNQf6vKFm zIy318jOoNxQBnoWJEAsdG442j3NPeLcm182uEEExf1HMje/k6CoFI5N3J3EYIfzppD4 Jncw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=DQDV04MkNsA/u9xuCBTehdYReIXTvnJCQV1I1n1dETE=; b=RGGRa1+KnGlqTTHY8C4V4Ijx0VyS0GpDOMam4j6TeAjjJJoo3+9zfAchPlfqOYbk6K cM8BL/7Cy2WjJFsM57X4vHAX1BEhAKPtiaW7klXP3d2BKqTZCzU5ZhcPHlyT89U46E2m JR9soGAo+JdTxoAMULwqhO/xiI8GF1whfcatnkOukcP34RsfyauI+QcTY2VGE2Y7/t/S c8kjJlbUApaK9ikK/KAzH6zfNpP4jzHW5JnA7egMQru0ghGCVceiQv9hGmesYf7Lr5yk 15UlU7EzGf933VLCqHYZeq2huIX6BCVYH7Oqz0kxZLvV6PB/X9if+2qVoEIOsLHcbw01 eGig==
X-Gm-Message-State: AKS2vOz0Bl5w3ex2bBairKWJHOQXuVAXphnUOsbE0Tuz9UWgYn8ImlVe UYv9u2AGjSCUlycD1LJ13TOdoYmz0kQn
X-Received: by 10.31.209.134 with SMTP id i128mr28515091vkg.125.1499376973373;  Thu, 06 Jul 2017 14:36:13 -0700 (PDT)
MIME-Version: 1.0
References:  <30BEA741-2174-459F-981E-95107EA19D3D@fugue.com> <22892E8C-EECF-46F7-A775-7D061E7FDAB5@gmail.com>
In-Reply-To: <22892E8C-EECF-46F7-A775-7D061E7FDAB5@gmail.com>
From: Warren Kumari 
Date: Thu, 06 Jul 2017 21:36:02 +0000
Message-ID: 
To: Aaron Falk , Ted Lemon 
Cc: Tools-discuss 
Content-Type: multipart/alternative; boundary="001a114e3a90e1f7190553ace718"
Archived-At: 
Subject: Re: [Tools-discuss] Chrome odd wraps html-ized drafts
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Thu, 06 Jul 2017 21:36:16 -0000

--001a114e3a90e1f7190553ace718
Content-Type: text/plain; charset="UTF-8"

On Thu, Jul 6, 2017 at 3:04 PM Aaron Falk  wrote:

> On 6 Jul 2017, at 13:37, Ted Lemon wrote:
>
> On Jul 6, 2017, at 1:27 PM, Aaron Falk  wrote:
>
> Has anyone else noticed this
> ? Very
> annoying, IMO. Looks fine in Safari, consistently bad wraps on Chrome.
> Reducing font size makes no difference.
>
> How about making your window wider?   Is this on iPad?   I just looked at
> the same draft, and nothing I did was able to make it break, so it sounds
> like maybe you're running an extension that's modifying the css or
> something?
>
> Chrome Version 59.0.3071.115 (Official Build) (64-bit)
> MacOS Sierra 10.12.5
>
> Wider window makes no difference, just adds white space.
> Smaller font makes no difference, just makes font smaller.
>
> Sigh. Turns out I had an extension on:
>
> 
 Line Wrapper 1.0
> Enables line wrapping in 
 tags. Uncheck "Enabled" whenever you want
> to revert to the default behavior.
>
>
Does what it says on then tin...

:-p

W

--
> Tools-discuss mailing list
> Tools-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-discuss
>
> Please report datatracker.ietf.org bugs at
> http://tools.ietf.org/tools/ietfdb
> or send email to datatracker-project@ietf.org
>
> Please report tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
> send email to webmaster@tools.ietf.org
>
-- 
I don't think the execution is relevant when it was obviously a bad idea in
the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair of
pants.
   ---maf

--001a114e3a90e1f7190553ace718
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable



On Thu, Jul 6, 2017 a=
t 3:04 PM Aaron Falk <aaron.falk=
@gmail.com> wrote:
On 6 Jul 2017, at 13:37, Ted Lemon wrote:




On Jul 6, 2017, at 1:27 PM,=
 Aaron Falk <a=
aron.falk@gmail.com> wrote:
Has anyone else noticed=C2=A0this? Very annoying, IMO. Looks fine in Safari, consistently bad =
wraps on Chrome. Reducing font size makes no difference.
How about making your window wider? =C2=A0 Is this on iPad? =C2=A0 I ju=
st looked at the same draft, and nothing I did was able to make it break, s=
o it sounds like maybe you're running an extension that's modifying=
 the css or something?





Chrome Version 59.0.3071.115 (Official Build) =
(64-bit)

MacOS Sierra 10.12.5


Wider window makes no difference, just adds white space.
Smaller font makes no difference, just makes font smaller.


Sigh.  Turns out I had an extension on:


<pre> Line Wrapper 1.0

Enables line wrapping in <pre> tags. Uncheck "Enabled" when=
ever you want to revert to the default behavior.

Does wha=
t it says on then tin...

:-p

W









--

Tools-discuss mailing list

Tools-discuss@i=
etf.org

https://www.ietf.org/mailman/listinfo/tools-discu=
ss



Please report datatracker.ietf.org bugs at http://tools.ietf=
.org/tools/ietfdb

or send email to datatracker-project@ietf.org



Please report tools.ietf.org bugs at http://tools.ietf.org/tools=
/issues or

send email to webmaster@tools.ietf.org


-- 
I don't think the execution is relevant when it wa=
s obviously a bad idea in the first place.
This is like putting rabid we=
asels in your pants, and later expressing regret at having chosen those par=
ticular rabid weasels and that pair of pants.
=C2=A0 =C2=A0---maf


--001a114e3a90e1f7190553ace718--


From nobody Tue Jul 11 01:06:52 2017
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3482F1319CC for ; Tue, 11 Jul 2017 01:06:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 jLM64AjuqBuH for ; Tue, 11 Jul 2017 01:06:49 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D27D4129AC4 for ; Tue, 11 Jul 2017 01:06:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v6B86j2x009063 for ; Tue, 11 Jul 2017 10:06:45 +0200 (CEST)
Received: from [192.168.217.113] (p5DC7E215.dip0.t-ipconnect.de [93.199.226.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3x6F6F39jnzDJbg; Tue, 11 Jul 2017 10:06:45 +0200 (CEST)
From: Carsten Bormann 
Content-Type: text/plain; charset=utf-8
X-Mao-Original-Outgoing-Id: 521453204.355447-773a471e2d222d24d2da42703a6a58c4
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 11 Jul 2017 10:06:44 +0200
Message-Id: 
To: "tools-discuss@ietf.org Discussion" 
X-Mailer: Apple Mail (2.3273)
Archived-At: 
Subject: [Tools-discuss] Datatracker authentication for Mailman?
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 11 Jul 2017 08:06:51 -0000

After doing the secret handshake again of giving someone the mailman =
password for a mailing list, I wonder how hard it would be to make =
datatracker authentication available in mailman.

Disclaimer: I know nothing about mailman, so this request may be =
ridiculously hard to implement.

But if it is doable with a reasonable amount of work, I think it would =
improve both the security of the mailing lists (by allowing us to get =
rid of shared, hard to change passwords) and make life a little bit =
simpler for chairs and other mailing list maintainers.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Tue Jul 11 04:26:59 2017
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39DDE131687 for ; Tue, 11 Jul 2017 04:26:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 BOpIgsldfgjA for ; Tue, 11 Jul 2017 04:26:56 -0700 (PDT)
Received: from mail-qk0-x22d.google.com (mail-qk0-x22d.google.com [IPv6:2607:f8b0:400d:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67FAA1316D3 for ; Tue, 11 Jul 2017 04:26:55 -0700 (PDT)
Received: by mail-qk0-x22d.google.com with SMTP id d78so99031543qkb.1 for ; Tue, 11 Jul 2017 04:26:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=PudQeCNruSkVqK7qOka0l3UyggaeV/c3X2M1TaN7O0c=; b=g2ihnakUDHIVEigjOIBwlwDXc5lRCPjVvtZCoPv7l4RAM5NY4SOTtI2eshPqReUze5 OUdJ7vtzO8PesDgy8ezOgW8BK1N54ogThztR1fXdIrK5VJHO0jVVGAj6bijy+byIrXWl TCGrgjh8UERtRabS/rs07R5Cg/pFpNI9UEDTMm2/g4zF58dXpITcRR44X+/VbstTCmWf FVfYCV3Vdo+gPYiDjL2PDhwCGJA3/fN/kZXDJuPUQG69/K3gD4jY+MmI3WEjxeKv8Q1P iHHzwfrCF87kwwrl75UczKb4aQUUBT3ueiZ4XQ3tqFJvbUWu7S2hbdWaxr9zb3n3Wj84 Nf/w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=PudQeCNruSkVqK7qOka0l3UyggaeV/c3X2M1TaN7O0c=; b=eOT8ii7mQ3zHnJDbFR6YMXL9sdHG8F+X8xo+dj6aUmYNSHoktpMdAKjyrcD5m4x8d/ zfuBaqs0PXJZiQg/GGGusSXS+NZyMHPgwMtO8cOLAvVzoIjk/xCN/VHrQUr8sgBq6/5K xjMX3AcHYNhlwnkUZfwIpWArB9YWquVsueIfPu7m6WEBe4a5EFeSYzA17U0vCBUgKm7J cOHlXmqF+JxuBJVjUVmk3/m2L6pWS6OaAPSCSSyEoeAburZ6+MXPuoILGdEf6fJNi86i hnTRdiEaVp3bIhlkTLSkdbW0UtZsOad8oSwFAbR53nqvWoryJX5ELSNpm10jUT1cfdUN OjCQ==
X-Gm-Message-State: AIVw110uVXSC5lDUe4j0mCdxWO/uURNyzsAr0bqCx8HKOtizMFBeHIfm Wqzxjy352EfDnEit
X-Received: by 10.55.46.2 with SMTP id u2mr10534918qkh.23.1499772414597; Tue, 11 Jul 2017 04:26:54 -0700 (PDT)
Received: from [10.0.30.153] (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id t43sm11698441qth.30.2017.07.11.04.26.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Jul 2017 04:26:53 -0700 (PDT)
From: Ted Lemon 
Message-Id: <0B58D40F-0E93-4210-ADD0-1E40BDF23472@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A0C5737C-567B-4614-82AD-69255DEA6C1C"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 11 Jul 2017 07:26:32 -0400
In-Reply-To: 
Cc: "tools-discuss@ietf.org Discussion" 
To: Carsten Bormann 
References: 
X-Mailer: Apple Mail (2.3273)
Archived-At: 
Subject: Re: [Tools-discuss] Datatracker authentication for Mailman?
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 11 Jul 2017 11:26:57 -0000

--Apple-Mail=_A0C5737C-567B-4614-82AD-69255DEA6C1C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jul 11, 2017, at 4:06 AM, Carsten Bormann  wrote:
> But if it is doable with a reasonable amount of work, I think it would =
improve both the security of the mailing lists (by allowing us to get =
rid of shared, hard to change passwords) and make life a little bit =
simpler for chairs and other mailing list maintainers.

+1

I suspect that it's hard, though.   But mailman's security for ietf =
mailing lists is horrible: the only reason we haven't been burned by it =
yet is that nobody's interested in attacking it.


--Apple-Mail=_A0C5737C-567B-4614-82AD-69255DEA6C1C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

On Jul 11, 2017, at 4:06 AM, Carsten Bormann <cabo@tzi.org> =
wrote:
But if it is doable =
with a reasonable amount of work, I think it would improve both the =
security of the mailing lists (by allowing us to get rid of shared, hard =
to change passwords) and make life a little bit simpler for chairs and =
other mailing list maintainers.

+1

I suspect that it's hard, though. =
  But mailman's security for ietf mailing lists is horrible: the =
only reason we haven't been burned by it yet is that nobody's interested =
in attacking it.

=

--Apple-Mail=_A0C5737C-567B-4614-82AD-69255DEA6C1C--


From nobody Tue Jul 11 06:35:11 2017
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2422127058 for ; Tue, 11 Jul 2017 06:35:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 foE1X4iQywcB for ; Tue, 11 Jul 2017 06:35:08 -0700 (PDT)
Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F9CE120724 for ; Tue, 11 Jul 2017 06:35:08 -0700 (PDT)
Received: from h-43-30.a357.priv.bahnhof.se ([79.136.43.30]:52166 helo=[192.168.1.120]) by durif.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1dUvJi-0006yW-9H; Tue, 11 Jul 2017 06:35:06 -0700
To: Carsten Bormann , "tools-discuss@ietf.org Discussion" 
References: 
From: Henrik Levkowetz 
Message-ID: <35f70009-7cf5-58ad-7609-1e750698d8f6@levkowetz.com>
Date: Tue, 11 Jul 2017 15:34:58 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: 
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="tve2bwrECpb53iJBkwNBAn19LI3vnBgVr"
X-SA-Exim-Connect-IP: 79.136.43.30
X-SA-Exim-Rcpt-To: tools-discuss@ietf.org, cabo@tzi.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on durif.tools.ietf.org)
Archived-At: 
Subject: Re: [Tools-discuss] Datatracker authentication for Mailman?
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 11 Jul 2017 13:35:11 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--tve2bwrECpb53iJBkwNBAn19LI3vnBgVr
Content-Type: multipart/mixed; boundary="EmeCuH0L7STaWuKWWQSP0lxEXxGFqOlWP";
 protected-headers="v1"
From: Henrik Levkowetz 
To: Carsten Bormann ,
 "tools-discuss@ietf.org Discussion" 
Message-ID: <35f70009-7cf5-58ad-7609-1e750698d8f6@levkowetz.com>
Subject: Re: [Tools-discuss] Datatracker authentication for Mailman?
References: 
In-Reply-To: 

--EmeCuH0L7STaWuKWWQSP0lxEXxGFqOlWP
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


On 2017-07-11 10:06, Carsten Bormann wrote:
> After doing the secret handshake again of giving someone the mailman
> password for a mailing list, I wonder how hard it would be to make
> datatracker authentication available in mailman.
>=20
> Disclaimer: I know nothing about mailman, so this request may be
> ridiculously hard to implement.
>=20
> But if it is doable with a reasonable amount of work, I think it
> would improve both the security of the mailing lists (by allowing us
> to get rid of shared, hard to change passwords) and make life a
> little bit simpler for chairs and other mailing list maintainers.

I think this makes sense, and would be valuable; but it probably should
be done based on Mailman 3, which is heavily refactored compared to
Mailman 2.  We already want to move to Mailman 3 in order to be able
to add EAI (RFC 6531) support.


Best regards,

	Henrik



--EmeCuH0L7STaWuKWWQSP0lxEXxGFqOlWP--

--tve2bwrECpb53iJBkwNBAn19LI3vnBgVr
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJZZNQCAAoJEE6bV0uPuxca8uwQAL6VcYdFrxqvXepXzPkCQNjK
BT01xwNBsiApV/meSSjxVd7jfJ/s6Cz4uukWHD8a0IyW2YsHWtmrZuRTX8mKv30n
ZTSWlo/6zZaVlsJkxUfzCBn3k+Lt/Th0LRVp0+BjPE9xmdOdBX+s9Jim6rSQFe38
T4csLqMCpMeVmbpWM6vyHkTVMUpDTCPtb1a7kUj12jIRWxRyMwMoixGGXDJEKiSw
sixPKq1MtxYVjGRm+tU7NF3lq4ZZZTfPRvhSIJTsj0HthDQGUsNLBDN15r01mtnH
o/I1xJ8MHnAWKjuIaAX99mNlwlJKhaFlWaUI53CSJaXynJikBFq41NiS+YgLMM5S
lAx1yhnD8XxG62SoOJ5HaPr8mQYI/idsaVxR/0IZ2kj5hA7bFPxtbaKeBi3V2pBN
yNHxsNWpDV9u4e4wTunRHg082qJxsulxM/2ny0fGO6pvvNOaow/ZKLzc9/QSCiKX
6HIdSOmxXGel5lySwMENdpUBW7BlJm4CwuL5h0WXFt2jswHJKnwl9ZESHA+uwz+y
W6DZa/cjDqJcJ4J1swX5F1KcSXpkQJiW3kwBZNYxjRyFWf/z90kyE5D1iuxouCgw
0qMSlroFmOT17QTFq5xA4Y6og0GvI1OSEpFLsRwzunRdpizPQ4CMyl/4F/L7DKdp
EoDDBUBHeFtSTZaT2RPM
=ghVv
-----END PGP SIGNATURE-----

--tve2bwrECpb53iJBkwNBAn19LI3vnBgVr--


From nobody Tue Jul 11 10:37:20 2017
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0615813176F for ; Tue, 11 Jul 2017 10:37:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=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 Qwj7pwDavWeZ for ; Tue, 11 Jul 2017 10:37:17 -0700 (PDT)
Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A830C1315FC for ; Tue, 11 Jul 2017 10:37:17 -0700 (PDT)
Received: from h-43-30.a357.priv.bahnhof.se ([79.136.43.30]:57749 helo=[192.168.1.120]) by durif.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1dUz65-0008TE-1c for tools-discuss@ietf.org; Tue, 11 Jul 2017 10:37:17 -0700
To: Tools Team Discussion 
From: Henrik Levkowetz 
Message-ID: <50a94180-347b-4861-4386-a59fa3438836@levkowetz.com>
Date: Tue, 11 Jul 2017 19:37:08 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="3Tvuq1kwXJJie7uw2uv9JbQi4f9gekX52"
X-SA-Exim-Connect-IP: 79.136.43.30
X-SA-Exim-Rcpt-To: tools-discuss@ietf.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on durif.tools.ietf.org)
Archived-At: 
Subject: [Tools-discuss] Python htmlization library
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 11 Jul 2017 17:37:19 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--3Tvuq1kwXJJie7uw2uv9JbQi4f9gekX52
Content-Type: multipart/mixed; boundary="xG2aTqiU1x1LNGHqse9N19Wds3AHpJBVC";
 protected-headers="v1"
From: Henrik Levkowetz 
To: Tools Team Discussion 
Message-ID: <50a94180-347b-4861-4386-a59fa3438836@levkowetz.com>
Subject: Python htmlization library

--xG2aTqiU1x1LNGHqse9N19Wds3AHpJBVC
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi,

The code which does htmlization of internet-drafts and rfcs on
tools.ietf.org/html/ is now available as a standalone python
module, at https://pypi.python.org/pypi/rfc2html.  Install it
with '$ pip install rfc2html'.

Please note that this provides the htmlization of the documents,
but not the page top which contains document meta-information;
that meta-information needs access to document-specific data
outside of what is present in the document itself, and needs to
be built to match the local database tables etc. if you want to
provide a full match of what tools.ietf.org/html/ gives.

The rfc2html module is in use in the datatracker.


Best regards,

	Henrik


--xG2aTqiU1x1LNGHqse9N19Wds3AHpJBVC--

--3Tvuq1kwXJJie7uw2uv9JbQi4f9gekX52
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJZZQzEAAoJEE6bV0uPuxcayeYP/3aboq+Me0QhWwv2fXwVrWzN
V2f7Xj8kqIiRmby0+N1mNIjb/T74KowrdyTKm36tQrlk2SGMWf9Bpi8LqpBMNbf6
FSZwNklratZTy0vwfrS9dbz62n9YLBHViv5+EfabH5SfYTVrGy3ZlocRhwPXXEZF
guuzbl7xfggTsfGAXuTAq7cbfOK7iUZiHqXyH1Hg76eVWALkzb9lW7DZUGWbJSK6
xwbeR5XEswHXBGdkRDug1Z5THiCDlsRaM3gCY32pp6KSLrj8v6x0ctCdGEZW/Ed6
1Z1w13CG4H4NX54Nhin5vDZ3vvIAaNfqquIoWn2ijfZVDZZEUBQKSs77VDPgHvaR
F4Y7BK2B5Dp157rDP9ehjWKc5WVIipOPCJGptMZPmHl+OCC99sFoWbYnCxwX3ZCK
rJqy1SQ21+b0Xk9+hXNonK6Lnc1/EbL88ASmR1MyC1dAYmcTsTwIdAVg7qU6UXpT
DD2qXZiXXCkR/n6wWlzUDcYGaky40GmJxRwjb0VprNMz+6PrMXIyu8LR033XPJXs
JvoTZPSTcJi6OK/6nQoESe+9IcngkqHBVjihzNHOkrduQaenJD8nH5LUieEX9yvR
xhZQpx9Owxn6ZTk2buapP1vujdHadRzanbvcz0aM3w8CPxs1XmiiwXDujEuaJR3L
39nuLAKs/t1Flw9+Z094
=h3GC
-----END PGP SIGNATURE-----

--3Tvuq1kwXJJie7uw2uv9JbQi4f9gekX52--


From nobody Tue Jul 11 20:14:58 2017
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFB7B12762F for ; Tue, 11 Jul 2017 20:14:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level: 
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no 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 IHQzELhkbzLz for ; Tue, 11 Jul 2017 20:14:55 -0700 (PDT)
Received: from resqmta-ch2-03v.sys.comcast.net (resqmta-ch2-03v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90503126CC7 for ; Tue, 11 Jul 2017 20:14:55 -0700 (PDT)
Received: from resomta-ch2-12v.sys.comcast.net ([69.252.207.108]) by resqmta-ch2-03v.sys.comcast.net with ESMTP id V86vd4qRO3ZQNV874dQHcI; Wed, 12 Jul 2017 03:14:54 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-12v.sys.comcast.net with SMTP id V873dRpk37ZFxV874d2uTW; Wed, 12 Jul 2017 03:14:54 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v6C3Ertf014641 for ; Tue, 11 Jul 2017 23:14:53 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v6C3ErCH014635; Tue, 11 Jul 2017 23:14:53 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: tools-discuss@ietf.org
Sender: worley@ariadne.com (Dale R. Worley)
Date: Tue, 11 Jul 2017 23:14:52 -0400
Message-ID: <87k23e4a8j.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfK0QJN7OaLEn/VOhdBgo1bZXEvrDoPu2t2S1J1lJgqf0U/7TOoG18OzGnacycpcUs+RD4BcH2HOQYgKeMxJtFnUf0yDspZcuAOwT1hcaDwWPADw67a0y fXJHO+00qiJeipsrOapG7+834mqc0Zj56tGjm7vpoHVimZc4bhyLcAcu
Archived-At: 
Subject: [Tools-discuss] Document history -- last call end date
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 12 Jul 2017 03:14:57 -0000

This is a very minor issue.  But every time I fill out a Gen-Art review,
I need to look up the IETF Last Call end date for a document and the
process is annoying because it seems to be unnecessarily awkward.  If I
look at the document's history (e.g.,
https://datatracker.ietf.org/doc/draft-ietf-pce-pceps/history/), there's
always an entry for the IESG telechat date (e.g., "2017-06-28 // 14 //
Deborah Brungard // Placed on agenda for telechat - 2017-08-03").  But
there is no corresponding item for the LC end date; I have to find the
entry for "The following Last Call announcement was sent out:" and look
through the body of the message to find the end date.

It seems like there should be a first-class history item, "IETF Last
Call ending xxxx-xx-xx", possibly combined with the header of the "The
following Last Call announcement was sent out:" item.

This does assume that the LC end date is actually recorded in the
datatracker as such, rather than being a consequence of being in the
body of the LC announcement.

Hoping this makes the cut at some point,

Dale


From nobody Wed Jul 12 07:00:27 2017
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C9A313168D for ; Wed, 12 Jul 2017 07:00:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 N4sBY2HcG0yM for ; Wed, 12 Jul 2017 07:00:25 -0700 (PDT)
Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0C45128961 for ; Wed, 12 Jul 2017 07:00:24 -0700 (PDT)
Received: from h-43-30.a357.priv.bahnhof.se ([79.136.43.30]:65502 helo=[192.168.1.120]) by durif.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1dVIBk-0003oM-6Q; Wed, 12 Jul 2017 07:00:24 -0700
To: "Dale R. Worley" , tools-discuss@ietf.org
References: <87k23e4a8j.fsf@hobgoblin.ariadne.com>
From: Henrik Levkowetz 
Message-ID: <348d5fde-78b6-bdec-93f7-e92a89c9d02d@levkowetz.com>
Date: Wed, 12 Jul 2017 16:00:16 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <87k23e4a8j.fsf@hobgoblin.ariadne.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="TVmDSC4kso8WpEa5pTL8HLuOHiPSK7I7O"
X-SA-Exim-Connect-IP: 79.136.43.30
X-SA-Exim-Rcpt-To: tools-discuss@ietf.org, worley@ariadne.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on durif.tools.ietf.org)
Archived-At: 
Subject: Re: [Tools-discuss] Document history -- last call end date
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 12 Jul 2017 14:00:26 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--TVmDSC4kso8WpEa5pTL8HLuOHiPSK7I7O
Content-Type: multipart/mixed; boundary="kH1gX19uv5wNr8GgbR9IpRUIL0ih49DNV";
 protected-headers="v1"
From: Henrik Levkowetz 
To: "Dale R. Worley" , tools-discuss@ietf.org
Message-ID: <348d5fde-78b6-bdec-93f7-e92a89c9d02d@levkowetz.com>
Subject: Re: [Tools-discuss] Document history -- last call end date
References: <87k23e4a8j.fsf@hobgoblin.ariadne.com>
In-Reply-To: <87k23e4a8j.fsf@hobgoblin.ariadne.com>

--kH1gX19uv5wNr8GgbR9IpRUIL0ih49DNV
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Dale,

On 2017-07-12 05:14, Dale R. Worley wrote:
> This is a very minor issue.  But every time I fill out a Gen-Art review=
,
> I need to look up the IETF Last Call end date for a document and the
> process is annoying because it seems to be unnecessarily awkward.  If I=

> look at the document's history (e.g.,
> https://datatracker.ietf.org/doc/draft-ietf-pce-pceps/history/), there'=
s
> always an entry for the IESG telechat date (e.g., "2017-06-28 // 14 //
> Deborah Brungard // Placed on agenda for telechat - 2017-08-03").  But
> there is no corresponding item for the LC end date; I have to find the
> entry for "The following Last Call announcement was sent out:" and look=

> through the body of the message to find the end date.
>=20
> It seems like there should be a first-class history item, "IETF Last
> Call ending xxxx-xx-xx", possibly combined with the header of the "The
> following Last Call announcement was sent out:" item.
>=20
> This does assume that the LC end date is actually recorded in the
> datatracker as such, rather than being a consequence of being in the
> body of the LC announcement.

The LC end date is recorded in the event which also holds the last
call text.  The actual end date is known for certain only when the
request to send out the last call email is posted.  Would it work
for you if I add the end date to the event text for that event,
giving:

  "The following Last Call announcement was sent out (ends 2017-07-28):

  ... "

?


Best regards,

	Henrik


--kH1gX19uv5wNr8GgbR9IpRUIL0ih49DNV--

--TVmDSC4kso8WpEa5pTL8HLuOHiPSK7I7O
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJZZitwAAoJEE6bV0uPuxcaaQEP/2iLJJfrYvFkv5XOrPMH9KJt
AMWDmL1490lUGnJVeC/LaPWmyxmS3mA7g4aB/Ps5BBv4cCpZUZQxYUklEVE9xmfB
W3uGkkrXJDhVajYsTGkwP9mfyNEHk9zWnt6C5fDWjSeLpNwhhto850lIkybCam6w
GTtgVDd/mI6iJ5l7f8AiVzgYdER8nd+pKw+5bqPDRLVCTiP1F3qqPF2oegNKd+h/
1s6gxakBosHbAjKoR8WQ7MszahJwRzjR5JkQaGHdPT0EMG7CJ4Vl203XfEh3hyXV
dWtD97dItTj4CeYMyjUCBh0RQ/zsGaSUEjP5L5P3KqouJDGy5QxT2Iirb+eKY8Kv
/6HeXN/qTnF0xa6SyhQjZMtyi41nFDwpQ8HKzMGlVro8K/In4FlVY4FZh7j+p7bG
hDcRtzD4ocdG13Sa6agalyZEjg4Ph3NofKCvmd+08qO6BD8l87k7LhRo6Lo2PM0+
C7Rr9yfIPDsAvkBHb9uBXe0JvtQCMNV2ZHOp6L8sfxAYBr1nHfS0SJoWfHlwY6hg
jIhhCiQqH+XLKSFi94VKp387LF86CWHQ51gBTzOtgq5TZfWHjNIsBjNTJoQnQycr
rgtXCSRDxhN02mv/HtSFL4eu/xD3LShdOSO6zPqzIfq24EuOm2jPfl69jxTEs7el
5sq1MiZMc8Hy0aMD6I/v
=YZb+
-----END PGP SIGNATURE-----

--TVmDSC4kso8WpEa5pTL8HLuOHiPSK7I7O--


From nobody Wed Jul 12 17:43:32 2017
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48C7012EC48 for ; Wed, 12 Jul 2017 17:43:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level: 
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 2ogAeY4nSSQZ for ; Wed, 12 Jul 2017 17:43:30 -0700 (PDT)
Received: from resqmta-ch2-05v.sys.comcast.net (resqmta-ch2-05v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CA7112EC01 for ; Wed, 12 Jul 2017 17:43:30 -0700 (PDT)
Received: from resomta-ch2-09v.sys.comcast.net ([69.252.207.105]) by resqmta-ch2-05v.sys.comcast.net with ESMTP id VSDEd5dcE2bOjVSE5dbC1K; Thu, 13 Jul 2017 00:43:29 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-09v.sys.comcast.net with SMTP id VSE4dd1ISh8eeVSE4dDyGx; Thu, 13 Jul 2017 00:43:29 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v6D0hRam000586; Wed, 12 Jul 2017 20:43:27 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v6D0hRco000581; Wed, 12 Jul 2017 20:43:27 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Henrik Levkowetz 
Cc: tools-discuss@ietf.org
In-Reply-To: <348d5fde-78b6-bdec-93f7-e92a89c9d02d@levkowetz.com> (henrik@levkowetz.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Wed, 12 Jul 2017 20:43:26 -0400
Message-ID: <87bmop415d.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfERZ7HvH3qDdaq28rnOYXTQmy90YDF4L/roCZd6uyFpTq7OZoK4CDxAsN/KQmWwrwkp00SjnmlUvozd3QGgpq9Nl4OSve33mKZeFCxqOqsJqtwXQbZJX WfKMp3FJGole2L5YzmNN2LxFUp6os3KebHvN4BVyh+jyVTr5u3+5mMrLJvge7aiUFhtfAUA5cS8/md0H4s5GuzjnaUHA++tFpyc=
Archived-At: 
Subject: Re: [Tools-discuss] Document history -- last call end date
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Thu, 13 Jul 2017 00:43:31 -0000

Henrik Levkowetz  writes:
> Would it work
> for you if I add the end date to the event text for that event,
> giving:
>
>   "The following Last Call announcement was sent out (ends 2017-07-28):
>   ... "

Yes, that would work fine.  It's essentially the same way the telechat
date is displayed in the history pane.

Dale


From nobody Thu Jul 13 05:45:10 2017
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DAAB129AC4 for ; Thu, 13 Jul 2017 05:45:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=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 AZ6-JMCXw4PG for ; Thu, 13 Jul 2017 05:45:06 -0700 (PDT)
Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEEF71318A9 for ; Thu, 13 Jul 2017 05:45:05 -0700 (PDT)
Received: from h-43-30.a357.priv.bahnhof.se ([79.136.43.30]:59255 helo=[192.168.1.120]) by durif.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1dVdUP-0008Si-3s; Thu, 13 Jul 2017 05:45:05 -0700
To: "Dale R. Worley" 
References: <87bmop415d.fsf@hobgoblin.ariadne.com>
Cc: tools-discuss@ietf.org
From: Henrik Levkowetz 
Message-ID: <7fa84d72-96da-f569-67a9-0438738f5dd7@levkowetz.com>
Date: Thu, 13 Jul 2017 14:44:50 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <87bmop415d.fsf@hobgoblin.ariadne.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="cmKNxI1wpx6aQ86NutW6rkPiS1UXrPC0S"
X-SA-Exim-Connect-IP: 79.136.43.30
X-SA-Exim-Rcpt-To: tools-discuss@ietf.org, worley@ariadne.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on durif.tools.ietf.org)
Archived-At: 
Subject: Re: [Tools-discuss] Document history -- last call end date
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Thu, 13 Jul 2017 12:45:08 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--cmKNxI1wpx6aQ86NutW6rkPiS1UXrPC0S
Content-Type: multipart/mixed; boundary="QCfo9pejAK21VrOA77Kt5qx2W2emmrC92";
 protected-headers="v1"
From: Henrik Levkowetz 
To: "Dale R. Worley" 
Cc: tools-discuss@ietf.org
Message-ID: <7fa84d72-96da-f569-67a9-0438738f5dd7@levkowetz.com>
Subject: Re: [Tools-discuss] Document history -- last call end date
References: <87bmop415d.fsf@hobgoblin.ariadne.com>
In-Reply-To: <87bmop415d.fsf@hobgoblin.ariadne.com>

--QCfo9pejAK21VrOA77Kt5qx2W2emmrC92
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Dale,

On 2017-07-13 02:43, Dale R. Worley wrote:
> Henrik Levkowetz  writes:
>> Would it work
>> for you if I add the end date to the event text for that event,
>> giving:
>>
>>   "The following Last Call announcement was sent out (ends 2017-07-28)=
:
>>   ... "
>=20
> Yes, that would work fine.  It's essentially the same way the telechat
> date is displayed in the history pane.

Ok, then.  It will be available when 6.56.0 (just released) is deployed.


Best regards,

	Henrik



--QCfo9pejAK21VrOA77Kt5qx2W2emmrC92--

--cmKNxI1wpx6aQ86NutW6rkPiS1UXrPC0S
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJZZ2tJAAoJEE6bV0uPuxcaG0AQANg6sVLA0p+PJmxefl8MNyAF
puuak8n4HnRZVx6CQG17EJMTcfwU0vi2So9MVjCOQ97krINGQS1x3gWpcL54cVTe
gZlEhFUwFOXSaNPFSkHwRyOAvgFcDODwZf1J/0ZdbjBs51Ba5lwE+OimrZyViAty
NDZ0vwaPcSZHLnEyDWYwyvN+Spd7LeRfjFz3mmOmnH9iOIrynG8E3LndF3zUuKQu
cNIRfbCLQczn5qQI8RsEs//leut5k+4xYaBtCA/p2vb0YycnxON2I21HTj2eDfPg
JaMw8unMfKH0grYPpVJj4qGWYdlvpizn02ow/UR5H2dz0goveTM1uzAk4+JGm5Mn
/KbqE5xBJianmSNGLfslNjOy4WT1yRcBzsIy1nnZdU44gP84PSCNqCZ09ioSOIlt
6V/+iQJsG8/MNaDII/BriWhQA+CqYQY90DX5p0Oi0omUhs0PrWxkTRFtK6CMrhWr
QN5uk30khPW4CvPl0FzBwl+9z0oi67G52toDlm99+1RHMHwLz1Pdn14J4nps+bWZ
V+/8hNgI4tLpwoIlMJnDA4I+3RdXBCK21jpjsGro2M/Ma5ge0flpCm64fd7Nasc7
+XVS7NQ5fWsp9yuW9E/PC003thgMx1hekr9bYz8PdttWb/HFWJbU+5nkVqHGjHV7
kgDmejnYoziV9MC/xUHd
=l8gs
-----END PGP SIGNATURE-----

--cmKNxI1wpx6aQ86NutW6rkPiS1UXrPC0S--


From nobody Wed Jul 19 00:52:56 2017
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA26B131C05 for ; Wed, 19 Jul 2017 00:52:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level: 
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=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 kTHO77sBOgQO for ; Wed, 19 Jul 2017 00:52:53 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68BE4131BFE for ; Wed, 19 Jul 2017 00:52:53 -0700 (PDT)
Received: from dhcp-8097.meeting.ietf.org (dhcp-8097.meeting.ietf.org [31.133.128.151]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v6J7qni2099868 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Wed, 19 Jul 2017 02:52:51 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
References: 
To: tools-discuss 
From: Robert Sparks 
X-Forwarded-Message-Id: 
Message-ID: 
Date: Wed, 19 Jul 2017 09:52:45 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: 
Content-Type: multipart/alternative; boundary="------------74C402CB81EFFC99A84ECB55"
Content-Language: en-US
Archived-At: 
Subject: [Tools-discuss] Fwd: Next steps in IETF list email archiving
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 19 Jul 2017 07:52:54 -0000

This is a multi-part message in MIME format.
--------------74C402CB81EFFC99A84ECB55
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

FYI -

Please keep the discussion on ietf@

RjS

-------- Forwarded Message --------
Subject: 	Next steps in IETF list email archiving
Date: 	Wed, 19 Jul 2017 09:43:24 +0200
From: 	Robert Sparks 
To: 	ietf@ietf.org 



Several years ago, we identified a set of issues with the way
we were archiving email messages and new functionality that a
searching and browsing solution should contain. The initial
requirements for improvements were captured in RFC 6778, and a
subsequent round of requirements were captured in RFC 7842.

One of the key issues was (and is) related to management of
the archives.  Currently if a message has to be removed
(rare, but not as rare as we would like due to spam hitting
some lists), the secretariat has to touch many places. One
of those is Mhonarc. Touching one message there involves
changing many files (any other message that contains a
navigation link to this one, and the index files that speak
about the message).

As we built the new systems, we've targeted having one source
of truth for the archives. For instance, as we added IMAP
access to the archives (RFC 7017), we ensured that it was
served from the same bits used by mailarchive.ietf.org.  It
has been our expectation from the beginning that
mailarchive.org would replace the Mhonarc archives (see
section 2.7 of RFC 6778).

We believe we are getting close to the point where we can
make that replacement. The rate of bug reports and feature
requests for mailarchive.ietf.org is slow. (As we do for
the datatracker, we plan to continuously improve the
mailarchive interface. We know already of some things that
need to be improved when viewing on phone-sized displays.)

If you use the mhonarc archives heavily, and have not yet
explored mailarchive.ietf.org, we encourage you to do so now,
and report any difficulties you find. We recognize that the
experience is different, but many of the RFC 7842 driven
improvements focused on minimizing the transition pain.

We have successfully tested the code that will redirect all
existing Mhonarc URLs into the mailarchive using the
testlist.

We are not going to make this transition immediately, but
we do plan to make it more in the near future than the far
future. Please help us identify any additional things we can
do to minimize the disruption to your current workflow.

RjS



--------------74C402CB81EFFC99A84ECB55
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit


  

    
  
  
    
FYI -

    
Please keep the discussion on ietf@

    

    
RjS

      

      -------- Forwarded Message --------
      

        
          

            Subject:
            
            Next steps in IETF list email archiving
          

          

            Date: 
            Wed, 19 Jul 2017 09:43:24 +0200
          

          

            From: 
            Robert Sparks <rjsparks@nostrum.com>
          

          

            To: 
            ietf@ietf.org <ietf@ietf.org>
          

        
      

      

      

      
Several years ago, we identified a set of issues with the way
we were archiving email messages and new functionality that a
searching and browsing solution should contain. The initial
requirements for improvements were captured in RFC 6778, and a
subsequent round of requirements were captured in RFC 7842.

One of the key issues was (and is) related to management of
the archives.  Currently if a message has to be removed
(rare, but not as rare as we would like due to spam hitting
some lists), the secretariat has to touch many places. One
of those is Mhonarc. Touching one message there involves
changing many files (any other message that contains a
navigation link to this one, and the index files that speak
about the message).

As we built the new systems, we've targeted having one source
of truth for the archives. For instance, as we added IMAP
access to the archives (RFC 7017), we ensured that it was
served from the same bits used by mailarchive.ietf.org.  It
has been our expectation from the beginning that
mailarchive.org would replace the Mhonarc archives (see
section 2.7 of RFC 6778).

We believe we are getting close to the point where we can
make that replacement. The rate of bug reports and feature
requests for mailarchive.ietf.org is slow. (As we do for
the datatracker, we plan to continuously improve the
mailarchive interface. We know already of some things that
need to be improved when viewing on phone-sized displays.)

If you use the mhonarc archives heavily, and have not yet
explored mailarchive.ietf.org, we encourage you to do so now,
and report any difficulties you find. We recognize that the
experience is different, but many of the RFC 7842 driven
improvements focused on minimizing the transition pain.

We have successfully tested the code that will redirect all
existing Mhonarc URLs into the mailarchive using the
testlist.

We are not going to make this transition immediately, but
we do plan to make it more in the near future than the far
future. Please help us identify any additional things we can
do to minimize the disruption to your current workflow.

RjS




    

  


--------------74C402CB81EFFC99A84ECB55--