From nobody Sun Dec 4 13:37:16 2016 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 0D0271295E6 for ; Sun, 4 Dec 2016 13:37:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-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 RNkCms_GsIVi for ; Sun, 4 Dec 2016 13:37:11 -0800 (PST) Received: from smtp.smtpout.orange.fr (smtp12.smtpout.orange.fr [80.12.242.134]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DA93127A91 for ; Sun, 4 Dec 2016 13:37:10 -0800 (PST) Received: from macbook-pro-de-julien-elie.home ([92.170.5.52]) by mwinf5d47 with ME id Fxd71u00Y17Lgi403xd7qK; Sun, 04 Dec 2016 22:37:08 +0100 X-ME-Helo: macbook-pro-de-julien-elie.home X-ME-Auth: anVsaWVuLmVsaWU0ODdAd2FuYWRvby5mcg== X-ME-Date: Sun, 04 Dec 2016 22:37:08 +0100 X-ME-IP: 92.170.5.52 To: tools-discuss@ietf.org From: =?UTF-8?Q?Julien_=c3=89LIE?= Organization: TrigoFACILE -- http://www.trigofacile.com/ Message-ID: <5e8d32dc-6ea7-0470-c868-2dc6dd5e838e@trigofacile.com> Date: Sun, 4 Dec 2016 22:37:07 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Archived-At: Subject: [Tools-discuss] Encoding of ietf-announce list X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2016 21:37:14 -0000 Hi all, There is an encoding issue in the mails sent to ietf-announce (by datatracker?). You can see a recent example here: https://www.ietf.org/mail-archive/web/ietf-announce/current/msg16068.html where the Subject header field, as well as the title of the Internet-Draft in the body of the mail are incorrectly encoded: "Use of Transport Layer Security (TLS) in the Network News Transfer Protocol (NNTP)". " " should result in an unbreakable space. I hope this list is the right place to report that issue. Otherwise, who should I contact for the mails sent to ietf-announce? Thanks, -- Julien ÉLIE « – Tu n'as rien remarqué d'étrange chez cet Arverne ? – Oui, son accent. » (Astérix) From nobody Sun Dec 4 13:41:36 2016 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 01BC21295EB for ; Sun, 4 Dec 2016 13:41:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-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 K1JNm-ULJHUF for ; Sun, 4 Dec 2016 13:41:32 -0800 (PST) Received: from smtp.smtpout.orange.fr (smtp12.smtpout.orange.fr [80.12.242.134]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB20C1295DE for ; Sun, 4 Dec 2016 13:41:31 -0800 (PST) Received: from macbook-pro-de-julien-elie.home ([92.170.5.52]) by mwinf5d47 with ME id FxhV1u00L17Lgi403xhVAp; Sun, 04 Dec 2016 22:41:29 +0100 X-ME-Helo: macbook-pro-de-julien-elie.home X-ME-Auth: anVsaWVuLmVsaWU0ODdAd2FuYWRvby5mcg== X-ME-Date: Sun, 04 Dec 2016 22:41:29 +0100 X-ME-IP: 92.170.5.52 To: tools-discuss@ietf.org From: =?UTF-8?Q?Julien_=c3=89LIE?= Organization: TrigoFACILE -- http://www.trigofacile.com/ Message-ID: <2c0acd49-7e78-5f32-9017-7675ee98adef@trigofacile.com> Date: Sun, 4 Dec 2016 22:41:29 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Archived-At: Subject: [Tools-discuss] Unreadable LC reviews in datatracker X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2016 21:41:34 -0000 Hi all, Are the links to Last Call reviews (secdir, genart, etc.) correctly handled in datatracker? https://datatracker.ietf.org/doc/review-murchison-nntp-compress-05-secdir-lc-leiba-2016-09-22/ https://datatracker.ietf.org/doc/review-murchison-nntp-compress-05-genart-lc-dupont-2016-09-26/ https://datatracker.ietf.org/doc/review-murchison-nntp-compress-06-genart-telechat-dupont-2016-10-31/ All of them give an error like this one: Error; cannot read (review-murchison-nntp-compress-05-secdir-lc- leiba-2016-09-22.txt) -- Julien ÉLIE « – Tu n'as rien remarqué d'étrange chez cet Arverne ? – Oui, son accent. » (Astérix) From nobody Sun Dec 4 14:20:04 2016 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 75A5F12960A for ; Sun, 4 Dec 2016 14:20:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.9 X-Spam-Level: X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 NB_9AFNim_4E for ; Sun, 4 Dec 2016 14:20:01 -0800 (PST) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (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 E8860129609 for ; Sun, 4 Dec 2016 14:20:00 -0800 (PST) Received: from h-43-30.a357.priv.bahnhof.se ([79.136.43.30]:59959 helo=[192.168.1.120]) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1cDf8Y-0005rF-5B; Sun, 04 Dec 2016 14:19:58 -0800 Message-ID: <58449684.5090504@levkowetz.com> Date: Sun, 04 Dec 2016 23:19:48 +0100 From: Henrik Levkowetz User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:31.0) Gecko/20100101 Thunderbird/31.8.0 MIME-Version: 1.0 To: =?UTF-8?B?SnVsaWVuIMOJTElF?= , tools-discuss@ietf.org References: <5e8d32dc-6ea7-0470-c868-2dc6dd5e838e@trigofacile.com> In-Reply-To: <5e8d32dc-6ea7-0470-c868-2dc6dd5e838e@trigofacile.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="RFRqoG6x672NcMUE6bNjvaKiMk6mptweE" X-SA-Exim-Connect-IP: 79.136.43.30 X-SA-Exim-Rcpt-To: tools-discuss@ietf.org, julien@trigofacile.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 zinfandel.tools.ietf.org) Archived-At: Subject: Re: [Tools-discuss] Encoding of ietf-announce list X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2016 22:20:02 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --RFRqoG6x672NcMUE6bNjvaKiMk6mptweE Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Julien, On 2016-12-04 22:37, Julien =C3=89LIE wrote: > Hi all, >=20 > There is an encoding issue in the mails sent to ietf-announce (by=20 > datatracker?). > You can see a recent example here: > https://www.ietf.org/mail-archive/web/ietf-announce/current/msg16068= =2Ehtml >=20 > where the Subject header field, as well as the title of the=20 > Internet-Draft in the body of the mail are incorrectly encoded: > "Use of Transport Layer Security (TLS) in=C3=82 the=C3=82 Network=C3=82= News=C3=82 Transfer=C3=82=20 > Protocol (NNTP)". > " " should result in an unbreakable space. Yes. Issue found and a fix committed 4 days ago: https://trac.tools.ietf.org/tools/ietfdb/changeset/12429 This will be part of the next patch release, some time during the coming week. > I hope this list is the right place to report that issue. Otherwise,=20 > who should I contact for the mails sent to ietf-announce? For any issue related to the datatracker, please see the footer informati= on for this list. Best regards, Henrik --RFRqoG6x672NcMUE6bNjvaKiMk6mptweE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJYRJaFAAoJEE6bV0uPuxcaB1IP/jxk2V9zXW4O8HRG+Tctt5zl mb3gbq0pRASDVTiClyr3GTHS70lHSjJWEd8SsJtiX+utXMdTgyQmKG1s90MnzUal a9gjvBtmzjWf0cTpNlZK6fqzI3PnWdj/CvLBNrYzaDHFkJrj/8AwAeMbJFZTr0le XrxHn8fH6Y2ki698ceg3AcMDNHVHhsK2C90H+DjsX+X84uo/ciG3hVX41jP3h4W2 +YMhybE+rPq6g9QZ5itmekp1rRDkXm0vOhvKevkJ/mO4QjBgynTLyZF8FLVe+/je Z5Mk2T8QjODJWtrZP8PJ6RYwMJKz5AVQ7iGpELibiv7JAtGlxizDLmQ4nlDZEsOs BU/B/DZXoGQdOC9n8azmPfQfrVyBKGehXsZRYIjDTVCxto6jjJUDqPOLH7kWTnTl gUwp1tNWtR89md7aTYYd8GGoylaGteMgCuF976nnjjM75IgOrX6TvJZnTSS5EaqH UAUtDGNzA17EBXtgtbzfGILdmLyPbTzF0R2EAgItjblM4DGhWrntbF4Ft/uPuvbH RTU4u+qdEHtNoqGwyoKRi+XA4q9VaBVVQNneuzcJwl4AqtScQA0B/xN20HaKRTu7 huRUhPygzWHrPXFpYkzz1nId3bFaPLfDE+tYZRdiUCbULQ/S942A3dPZdFyTgrCn oTu6TsRpBZdOW33rpunc =Dnwo -----END PGP SIGNATURE----- --RFRqoG6x672NcMUE6bNjvaKiMk6mptweE-- From nobody Mon Dec 5 02:26:36 2016 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 540E712942F for ; Mon, 5 Dec 2016 02:26:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=iola-dk.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 sUtdO9esLAC7 for ; Mon, 5 Dec 2016 02:26:32 -0800 (PST) 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 5CE3A129429 for ; Mon, 5 Dec 2016 02:26:25 -0800 (PST) Received: by mail-qk0-x22e.google.com with SMTP id n204so341045659qke.2 for ; Mon, 05 Dec 2016 02:26:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iola-dk.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=x48V7lgERkSx+gwD0WHUp99GOxhaY1DF2dVgTynjmlA=; b=wG3fOuGeCbbv+epjCpKFuSpwrEPW6fHME83FYGqEsP9lOomukZt+vz/vhK3cBXLwEK K8sijAtIl7SuCELvj4RulFpXkabf2wNXLTyWUdl0IcrU/SS1lfTNKHksgr0w9e6jFPYM 5dSlW5REk5KBLiVGLzq/Gf74ao+XcHJ5eDf6nOaXOeLJWWcNeTZGeY9P1PsqkbO2VlIq /uLZWKyaUvMYqWEQa37wlHFcCaYymnFe7uftWrbnraO9BXPbeWIxU5m96EXL4jwVTdiq j9RCdjRI5c6ys30p2DtkzY2WtWXUFosoZT6f9mvu2LrJm1TlBJzVA/QQeBNcIekKYWBw gK2w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=x48V7lgERkSx+gwD0WHUp99GOxhaY1DF2dVgTynjmlA=; b=g7ZYOnPIxceWVtFEC5YGjU7LWZ7r5d+PGpFrqsZ9aOiVIulqrPyRnJ5jg0ttnxDmIV +ivKNDatl/HC/jqVE0EOM48Cx/ebQNa2LE19ro8DeSY1jaWAMkewCqHWlNfKFFiOPmN4 O9IQI1iRkfLQkE42vhFrfd2T58jnA6Zq9+lY36IUP1gexIOX2+AsuGwOVODfJIX/aBwz uCHTpkMZ9YS2hAJ7oBLDX4RWlGXMWVXd2dgrcBiec1OOH2VWjm8ikyY29PNq2BysVQns 9mTBdd8GxojR3dyZU54lFsHX2giyZAqfhuc8oweGCRjVGajcUeu2zPEgGdEVcXkeKq+M t4hA== X-Gm-Message-State: AKaTC02n9goOa8ntTYTzoXLs26+Ok3JB0kORV3Nu4h5ekATbskKxx5dEhBaw8+T540B72QqnAH791ArkYfzr3Q== X-Received: by 10.55.122.134 with SMTP id v128mr46019823qkc.111.1480933584287; Mon, 05 Dec 2016 02:26:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.200.57.117 with HTTP; Mon, 5 Dec 2016 02:26:03 -0800 (PST) In-Reply-To: <2c0acd49-7e78-5f32-9017-7675ee98adef@trigofacile.com> References: <2c0acd49-7e78-5f32-9017-7675ee98adef@trigofacile.com> From: Ole Laursen Date: Mon, 5 Dec 2016 11:26:03 +0100 Message-ID: To: =?UTF-8?B?SnVsaWVuIMOJTElF?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Archived-At: Cc: Tools Team Discussion Subject: Re: [Tools-discuss] Unreadable LC reviews in datatracker X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2016 10:26:34 -0000 2016-12-04 22:41 GMT+01:00 Julien =C3=89LIE : > Are the links to Last Call reviews (secdir, genart, etc.) correctly handl= ed > in datatracker? Hi! It's a problem with reviews imported from the old review tool - we didn't have time to get the content in. Last thing I heard, that's being worked on. Ole From nobody Mon Dec 5 07:21:01 2016 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 77E7D129AB9 for ; Mon, 5 Dec 2016 07:20:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.796 X-Spam-Level: X-Spam-Status: No, score=-4.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-2.896] 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 Cn90kG1x63Cp for ; Mon, 5 Dec 2016 07:20:56 -0800 (PST) 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 49CCF129AA6 for ; Mon, 5 Dec 2016 07:20:39 -0800 (PST) Received: from unnumerable.local ([47.186.56.40]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id uB5FKcYg009663 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=OK) for ; Mon, 5 Dec 2016 09:20:39 -0600 (CST) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host [47.186.56.40] claimed to be unnumerable.local To: tools-discuss@ietf.org References: <2c0acd49-7e78-5f32-9017-7675ee98adef@trigofacile.com> From: Robert Sparks Message-ID: <095fe2c6-6ad4-f8a3-01f8-e549def61199@nostrum.com> Date: Mon, 5 Dec 2016 09:20:37 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [Tools-discuss] Unreadable LC reviews in datatracker X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2016 15:20:59 -0000 It is being tracked at https://trac.tools.ietf.org/tools/ietfdb/ticket/2064. I'm working on it now. On 12/5/16 4:26 AM, Ole Laursen wrote: > 2016-12-04 22:41 GMT+01:00 Julien ÉLIE : >> Are the links to Last Call reviews (secdir, genart, etc.) correctly handled >> in datatracker? > Hi! > > It's a problem with reviews imported from the old review tool - we > didn't have time to get the content in. Last thing I heard, that's > being worked on. > > > Ole > From nobody Mon Dec 5 13:07:54 2016 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 CD3DB129E29 for ; Mon, 5 Dec 2016 13:07:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-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 VuXcoWZ0tUrU for ; Mon, 5 Dec 2016 13:07:49 -0800 (PST) Received: from smtp.smtpout.orange.fr (smtp05.smtpout.orange.fr [80.12.242.127]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A37C129D50 for ; Mon, 5 Dec 2016 13:05:20 -0800 (PST) Received: from macbook-pro-de-julien-elie.home ([92.170.5.52]) by mwinf5d28 with ME id GM5H1u00F17Lgi403M5Hgd; Mon, 05 Dec 2016 22:05:18 +0100 X-ME-Helo: macbook-pro-de-julien-elie.home X-ME-Auth: anVsaWVuLmVsaWU0ODdAd2FuYWRvby5mcg== X-ME-Date: Mon, 05 Dec 2016 22:05:18 +0100 X-ME-IP: 92.170.5.52 To: tools-discuss@ietf.org References: <5e8d32dc-6ea7-0470-c868-2dc6dd5e838e@trigofacile.com> <58449684.5090504@levkowetz.com> From: =?UTF-8?Q?Julien_=c3=89LIE?= Organization: TrigoFACILE -- http://www.trigofacile.com/ Message-ID: <7480abc6-3487-6c29-c5d2-afdfe832cee9@trigofacile.com> Date: Mon, 5 Dec 2016 22:05:17 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <58449684.5090504@levkowetz.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [Tools-discuss] Encoding of ietf-announce list X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2016 21:07:52 -0000 Hi Henrik, >> There is an encoding issue in the mails sent to ietf-announce (by >> datatracker?). >> You can see a recent example here: >> https://www.ietf.org/mail-archive/web/ietf-announce/current/msg16068.html >> >> where the Subject header field, as well as the title of the >> Internet-Draft in the body of the mail are incorrectly encoded: >> "Use of Transport Layer Security (TLS) in the Network News Transfer >> Protocol (NNTP)". >> " " should result in an unbreakable space. > > Yes. Issue found and a fix committed 4 days ago: > > https://trac.tools.ietf.org/tools/ietfdb/changeset/12429 > > This will be part of the next patch release, some time during the > coming week. Many thanks for having fixed the issue. Greatly appreciated. -- Julien ÉLIE « – Tu n'as rien remarqué d'étrange chez cet Arverne ? – Oui, son accent. » (Astérix) From nobody Mon Dec 5 13:18:37 2016 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 94245129D90 for ; Mon, 5 Dec 2016 13:18:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.88 X-Spam-Level: X-Spam-Status: No, score=-0.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-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 JhVNojb58u0D for ; Mon, 5 Dec 2016 13:18:34 -0800 (PST) Received: from smtp.smtpout.orange.fr (smtp05.smtpout.orange.fr [80.12.242.127]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24E7B129E2E for ; Mon, 5 Dec 2016 13:14:59 -0800 (PST) Received: from macbook-pro-de-julien-elie.home ([92.170.5.52]) by mwinf5d28 with ME id GMEy1u00617Lgi403MEySU; Mon, 05 Dec 2016 22:14:58 +0100 X-ME-Helo: macbook-pro-de-julien-elie.home X-ME-Auth: anVsaWVuLmVsaWU0ODdAd2FuYWRvby5mcg== X-ME-Date: Mon, 05 Dec 2016 22:14:58 +0100 X-ME-IP: 92.170.5.52 References: <2c0acd49-7e78-5f32-9017-7675ee98adef@trigofacile.com> Cc: Tools Team Discussion From: =?UTF-8?Q?Julien_=c3=89LIE?= Organization: TrigoFACILE -- http://www.trigofacile.com/ Message-ID: <5db8c7a5-b949-d143-994b-81069817027d@trigofacile.com> Date: Mon, 5 Dec 2016 22:14:58 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [Tools-discuss] Unreadable LC reviews in datatracker X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2016 21:18:35 -0000 Hi Ole, >> Are the links to Last Call reviews (secdir, genart, etc.) correctly handled >> in datatracker? >> All of them give an error like this one: >> Error; cannot read (review-murchison-nntp-compress-05-secdir-lc-leiba-2016-09-22.txt) > > It's a problem with reviews imported from the old review tool - we > didn't have time to get the content in. Last thing I heard, that's > being worked on. Thanks for your answer. It appears to have been fixed. Just a nit: https://datatracker.ietf.org/doc/review-murchison-nntp-compress-06-genart-telechat-dupont-2016-10-31/ https://datatracker.ietf.org/doc/review-murchison-nntp-compress-05-genart-lc-dupont-2016-09-26/ The link to wiki.tools.ietf.org at the 8th line of the above reviews was modified during the import (there should not be any line feeds after "<"). -- Julien ÉLIE « – Tu n'as rien remarqué d'étrange chez cet Arverne ? – Oui, son accent. » (Astérix) From nobody Wed Dec 7 10:59:06 2016 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 69B70129559 for ; Wed, 7 Dec 2016 10:59:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 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, 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 n-_86NQxU-dq for ; Wed, 7 Dec 2016 10:59:02 -0800 (PST) Received: from mail-pg0-x22e.google.com (mail-pg0-x22e.google.com [IPv6:2607:f8b0:400e:c05::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 BADD212954F for ; Wed, 7 Dec 2016 10:59:02 -0800 (PST) Received: by mail-pg0-x22e.google.com with SMTP id x23so164833592pgx.1 for ; Wed, 07 Dec 2016 10:59:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=yzidVl7gXMUKAyOfu4QAHffPW6y/qgKSKJFi5vBZx/Q=; b=VgZn+qUURXTgk2C1RM+iGD4dqlh+RiEfp5C5mAto21pZRTCaav/L1fs+CsFbw1Lo7b of951yHCAABlZyMZQ+r6/uLtUWvAE3zjzwC9RtjanRQAMGEL78eFCdS/IXjKvAauLR4P 80TqVIjnqIKwkSoh/3GCCqK2djxhd/VlG5nLSTvomfnLPTu5C7ZhRBkcbrY0J76OW7L2 T/ISD/zga6wo/NO9jKN4rLa3R278F074N3IJsSjdTy9U/GtFMfuP2qusLDSRKpsIyEqw Chmd1qb2/U5Ty+saAmeptur4s0a3/4Kg+H32PmWOX0/8Am/OzFGi6aSbPC4cxgf4qNFg /vqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=yzidVl7gXMUKAyOfu4QAHffPW6y/qgKSKJFi5vBZx/Q=; b=g4RAEbMkhI3/cVEyXuOUSeEjJtyJorXDo7FD+EntXV+isr1eGC5jkg7u+Rs5e+IEF6 eDPe2IPbgqNl0PGHFa8ZXTmhlDGelmlS+CtgArv3yWAN64rskl4a9QvoM6+xF56Dz7kd dwdJ1i4Pgy+rQNfMzv/z3vE4lNf0YunZIGVcgENtCjCy8dmqoy3tpx0jK9ioafvk/c6t Y7d6KBpcAnhFcOIxeqhz5e+t8dxmXStcq2qy12HQk4+jDb1OObJ2R0jnucL/ELJrw1p/ /5Z9L6y0X6hKduKXLgRoOwk3b41nQDAnzxN6Kiez+cML6TCDG4a/wuh83md4PWLEpdgL AFQg== X-Gm-Message-State: AKaTC03sNlVZ1vTyURbSKUUSpduz3Fk6lnI3X8SXrujivkvrnU+MxU4NEUdZ9yAqW2buwQ== X-Received: by 10.99.125.65 with SMTP id m1mr125305386pgn.159.1481137142152; Wed, 07 Dec 2016 10:59:02 -0800 (PST) Received: from [192.168.178.21] (80.217.69.111.dynamic.snap.net.nz. [111.69.217.80]) by smtp.gmail.com with ESMTPSA id o68sm44333360pfb.42.2016.12.07.10.58.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 07 Dec 2016 10:59:01 -0800 (PST) To: Henrik Levkowetz , =?UTF-8?Q?Julien_=c3=89LIE?= , tools-discuss@ietf.org References: <5e8d32dc-6ea7-0470-c868-2dc6dd5e838e@trigofacile.com> <58449684.5090504@levkowetz.com> From: Brian E Carpenter Organization: University of Auckland Message-ID: <9bd4da71-e783-8b1d-6ad6-8655509c6e38@gmail.com> Date: Thu, 8 Dec 2016 07:59:04 +1300 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <58449684.5090504@levkowetz.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Tools-discuss] Encoding of ietf-announce list X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2016 18:59:04 -0000 On 05/12/2016 11:19, Henrik Levkowetz wrote: ... > For any issue related to the datatracker, please see the footer information > for this list. > > For any issue related to the datatracker, please see the footer information > for this list. ... > 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 So, I'm now officially confused. I was taught to report all web site issues to ietf-action@ietf.org to put them into the Secretariat's tracker for follow-up. Brian From nobody Wed Dec 7 13:19:28 2016 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 AE105129BCA for ; Wed, 7 Dec 2016 13:19:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.796 X-Spam-Level: X-Spam-Status: No, score=-4.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-2.896] 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 nC46Ie3Iilra for ; Wed, 7 Dec 2016 13:19:21 -0800 (PST) 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 905ED129BC9 for ; Wed, 7 Dec 2016 13:19:21 -0800 (PST) Received: from unnumerable.local ([47.186.56.40]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id uB7LJJX3035479 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=OK); Wed, 7 Dec 2016 15:19:19 -0600 (CST) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host [47.186.56.40] claimed to be unnumerable.local To: Brian E Carpenter , Henrik Levkowetz , =?UTF-8?Q?Julien_=c3=89LIE?= , tools-discuss@ietf.org References: <5e8d32dc-6ea7-0470-c868-2dc6dd5e838e@trigofacile.com> <58449684.5090504@levkowetz.com> <9bd4da71-e783-8b1d-6ad6-8655509c6e38@gmail.com> From: Robert Sparks Message-ID: <9876a8ea-fe42-5d74-ac0c-556cd17548a2@nostrum.com> Date: Wed, 7 Dec 2016 15:19:19 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <9bd4da71-e783-8b1d-6ad6-8655509c6e38@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Tools-discuss] Encoding of ietf-announce list X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2016 21:19:27 -0000 On 12/7/16 12:59 PM, Brian E Carpenter wrote: > On 05/12/2016 11:19, Henrik Levkowetz wrote: > ... >> For any issue related to the datatracker, please see the footer information >> for this list. >> >> For any issue related to the datatracker, please see the footer information >> for this list. > ... >> 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 > So, I'm now officially confused. I was taught to report all web site issues to > ietf-action@ietf.org to put them into the Secretariat's tracker for follow-up. > > Brian > With understanding and sympathy for this not being as simple as it seems it should be, the instructions you quote have been on the various email lists and at the footers of the various tools for years. If you do report datatracker issues using ietf-action, the secretariat will only forward the ticket to the datatracker system and it will be closed. All followup will happen from the tools development team (currently, I'm making sure the datatracker issues are acted on as the project manager for the TMC). The net best result is a loss of time in getting the issue addressed. A similar thing will happen for tools.ietf.org issues - the secretariat can only send the tickets to Henrik and then close them. At best, time getting the right eyes on the issue is lost, and at worst something falls in the cracks during the handoff. I agree that having so many ways into reporting issues is confusing. I don't like it. But, the secretariat has tried (in the meeting context in particular) providing a single issue entry point, and has repeatedly seen the kinds of impedance problems I call out above. From nobody Wed Dec 7 13:51:58 2016 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 A9F3C1295AF for ; Wed, 7 Dec 2016 13:51:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 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, 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 jW0TivXIit71 for ; Wed, 7 Dec 2016 13:51:54 -0800 (PST) Received: from mail-pf0-x235.google.com (mail-pf0-x235.google.com [IPv6:2607:f8b0:400e:c00::235]) (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 7FCE11295A6 for ; Wed, 7 Dec 2016 13:51:53 -0800 (PST) Received: by mail-pf0-x235.google.com with SMTP id i88so78956540pfk.2 for ; Wed, 07 Dec 2016 13:51:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:organization:cc:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=EXJ+qKLoZ3aUg6vGJJ5JXvvtcDGyzWFX0I7Gda0Bibs=; b=cQZRcNPnv4J5qangKm51b2VTuSI6B2VPIXu9ZnktOkWtjwuO9HAd3Tm7CwrXYOUv7A 3Hkhqn02xybEE2/bcPLr/+kfzg+/qApwteOPO+s4p7it6MoSrizJOR5949TKmysxLSEM GZYqV9+6oqUDXrPCaVJm/xPotOe9PnZI3O5kExF0CtWHiR4tHYek0qHpdbg1kRBQjjeP iD+7ZUADy1uk5VzG1N156kgSEnYiyT/WvXGcfvnMfjdbP8hDoA/3LMLkP/TRyJwBi5Ax lHDlKZ7iYiN3h0gCasy4ot3zFf94MZ2liiLHSEvWJB7NMaagNIeTOk6jY9BzjDs/S8sm 7mAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:organization:cc :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=EXJ+qKLoZ3aUg6vGJJ5JXvvtcDGyzWFX0I7Gda0Bibs=; b=TxkOLoozp29eUC8t/VuW6bVb1HpSr88xIvqdNKq6P9eWiniOIGfvpO6ilpiyJe9zy/ DqtvAxDpunhkPACvlP+yJlCRYfcWsWFf0tPjMsVYmi/v8jPEk4kcK+dvi+uOkZ7zKpz8 kEwkyvDY3EA9WVUThVbAMOaP288z5FGOdz7lNGGvEd3gJoTUdL3h2TMhoxxIDS7sXvPn DJePmigvcSbUu7nPBHhtx+yLYQ9pnHSYigMTk5jS1LLoPUePWliWOGg6nkDbkBrVYVJ3 r0zLhyoCJ8jNuQX1rA+szSRwBBiSA/NNydp3R3EsS2Rv9I02uBd40MCUoYdbL3jV/xUK voNA== X-Gm-Message-State: AKaTC03uk74ciC8taXdOxBihSRmKHgLdxnQ7F87vkPnXtoSjg0F2YAreC6HJmktRkbb3Cg== X-Received: by 10.84.136.135 with SMTP id 7mr152099503pll.40.1481147512862; Wed, 07 Dec 2016 13:51:52 -0800 (PST) Received: from [192.168.178.21] (80.217.69.111.dynamic.snap.net.nz. [111.69.217.80]) by smtp.gmail.com with ESMTPSA id y15sm44950995pgc.43.2016.12.07.13.51.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 07 Dec 2016 13:51:52 -0800 (PST) To: Robert Sparks References: <5e8d32dc-6ea7-0470-c868-2dc6dd5e838e@trigofacile.com> <58449684.5090504@levkowetz.com> <9bd4da71-e783-8b1d-6ad6-8655509c6e38@gmail.com> <9876a8ea-fe42-5d74-ac0c-556cd17548a2@nostrum.com> From: Brian E Carpenter Organization: University of Auckland Message-ID: <5be5bb7e-3b73-cf16-6ba3-74489b5afd82@gmail.com> Date: Thu, 8 Dec 2016 10:51:55 +1300 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <9876a8ea-fe42-5d74-ac0c-556cd17548a2@nostrum.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Archived-At: Cc: =?UTF-8?Q?Julien_=c3=89LIE?= , Henrik Levkowetz , tools-discuss@ietf.org Subject: Re: [Tools-discuss] Encoding of ietf-announce list X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2016 21:51:57 -0000 below... On 08/12/2016 10:19, Robert Sparks wrote: > > > On 12/7/16 12:59 PM, Brian E Carpenter wrote: >> On 05/12/2016 11:19, Henrik Levkowetz wrote: >> ... >>> For any issue related to the datatracker, please see the footer information >>> for this list. >>> >>> For any issue related to the datatracker, please see the footer information >>> for this list. >> ... >>> 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 >> So, I'm now officially confused. I was taught to report all web site issues to >> ietf-action@ietf.org to put them into the Secretariat's tracker for follow-up. >> >> Brian >> > With understanding and sympathy for this not being as simple as it seems > it should be, the instructions you quote have been on the various email > lists and at the footers of the various tools for years. > > If you do report datatracker issues using ietf-action, the secretariat > will only forward the ticket to the datatracker system and it will be > closed. All followup will happen from the tools development team > (currently, I'm making sure the datatracker issues are acted on as the > project manager for the TMC). The net best result is a loss of time in > getting the issue addressed. > > A similar thing will happen for tools.ietf.org issues - the secretariat > can only send the tickets to Henrik and then close them. At best, time > getting the right eyes on the issue is lost, and at worst something > falls in the cracks during the handoff. > > I agree that having so many ways into reporting issues is confusing. I > don't like it. But, the secretariat has tried (in the meeting context in > particular) providing a single issue entry point, and has repeatedly > seen the kinds of impedance problems I call out above. It makes sense. However, the "Problem Reports" section of https://www.ietf.org/secretariat.html (which is the "Contact Us" page) says otherwise, so needs to be updated. Similarly https://www.ietf.org/contact-the-ietf.html (which is the "Contact" page). Why "Contact us" and "Contact" are different pages is another question. Also every page at www.ietf.org says this at the bottom: Please send problem reports to: ietf-action@ietf.org. Will you handle it? I could, but you're more likely to get it right. I suspect this needs a ticket to webmaster@ietf.org, maybe :-). Regards Brian From nobody Wed Dec 7 14:27:40 2016 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 34A5F12943E for ; Wed, 7 Dec 2016 14:27:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.796 X-Spam-Level: X-Spam-Status: No, score=-4.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-2.896] 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 pzyF2cZU4Y0D for ; Wed, 7 Dec 2016 14:27:37 -0800 (PST) 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 644A6129599 for ; Wed, 7 Dec 2016 14:27:37 -0800 (PST) Received: from unnumerable.local ([47.186.56.40]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id uB7MRZE6041991 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=OK); Wed, 7 Dec 2016 16:27:35 -0600 (CST) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host [47.186.56.40] claimed to be unnumerable.local To: Brian E Carpenter References: <5e8d32dc-6ea7-0470-c868-2dc6dd5e838e@trigofacile.com> <58449684.5090504@levkowetz.com> <9bd4da71-e783-8b1d-6ad6-8655509c6e38@gmail.com> <9876a8ea-fe42-5d74-ac0c-556cd17548a2@nostrum.com> <5be5bb7e-3b73-cf16-6ba3-74489b5afd82@gmail.com> From: Robert Sparks Message-ID: <6d17d5c9-9d4a-30f5-aa81-dd8f7fb70c3b@nostrum.com> Date: Wed, 7 Dec 2016 16:27:34 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <5be5bb7e-3b73-cf16-6ba3-74489b5afd82@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Cc: =?UTF-8?Q?Julien_=c3=89LIE?= , Henrik Levkowetz , tools-discuss@ietf.org Subject: Re: [Tools-discuss] Encoding of ietf-announce list X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2016 22:27:39 -0000 Yes, I'll take on driving those. On 12/7/16 3:51 PM, Brian E Carpenter wrote: > below... > > On 08/12/2016 10:19, Robert Sparks wrote: >> >> On 12/7/16 12:59 PM, Brian E Carpenter wrote: >>> On 05/12/2016 11:19, Henrik Levkowetz wrote: >>> ... >>>> For any issue related to the datatracker, please see the footer information >>>> for this list. >>>> >>>> For any issue related to the datatracker, please see the footer information >>>> for this list. >>> ... >>>> 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 >>> So, I'm now officially confused. I was taught to report all web site issues to >>> ietf-action@ietf.org to put them into the Secretariat's tracker for follow-up. >>> >>> Brian >>> >> With understanding and sympathy for this not being as simple as it seems >> it should be, the instructions you quote have been on the various email >> lists and at the footers of the various tools for years. >> >> If you do report datatracker issues using ietf-action, the secretariat >> will only forward the ticket to the datatracker system and it will be >> closed. All followup will happen from the tools development team >> (currently, I'm making sure the datatracker issues are acted on as the >> project manager for the TMC). The net best result is a loss of time in >> getting the issue addressed. >> >> A similar thing will happen for tools.ietf.org issues - the secretariat >> can only send the tickets to Henrik and then close them. At best, time >> getting the right eyes on the issue is lost, and at worst something >> falls in the cracks during the handoff. >> >> I agree that having so many ways into reporting issues is confusing. I >> don't like it. But, the secretariat has tried (in the meeting context in >> particular) providing a single issue entry point, and has repeatedly >> seen the kinds of impedance problems I call out above. > It makes sense. However, the "Problem Reports" section of https://www.ietf.org/secretariat.html > (which is the "Contact Us" page) says otherwise, so needs to be updated. Similarly > https://www.ietf.org/contact-the-ietf.html (which is the "Contact" page). > > Why "Contact us" and "Contact" are different pages is another question. > > Also every page at www.ietf.org says this at the bottom: > Please send problem reports to: ietf-action@ietf.org. > > Will you handle it? I could, but you're more likely to get it right. I suspect this needs > a ticket to webmaster@ietf.org, maybe :-). > > Regards > Brian From nobody Thu Dec 8 03:59:53 2016 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 7952B129D57 for ; Thu, 8 Dec 2016 03:59:52 -0800 (PST) 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 6GKEc45cBQlf for ; Thu, 8 Dec 2016 03:59:50 -0800 (PST) Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::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 7B130129D58 for ; Thu, 8 Dec 2016 03:59:33 -0800 (PST) Received: by mail-io0-x231.google.com with SMTP id l21so82916ioi.1 for ; Thu, 08 Dec 2016 03:59:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=dlBkhrJh6l4hGeTszGUJPOcQ5pjB28L6U/hyZsHmI/A=; b=uORLkiUdbejYmkwo2WNfkGriZVTg7d0/WDZ6Mdiu0MWlwaOtKMrnmU+92TK5V252d4 reV2NHlwHsWsoNuDwkIuGUZ551WkOvtvANRBzc1S1dNz8mu5RX3qfHCVkV+oqSbdkrgY 7N67p5WgxTF5Sc6rtk75vIz9uNaWbwrrgPAszsxYBjxQhhw0wmukbixf2H3X3uwFlGWk /qgV2Nn7ehM/453fx0K//Ff6igLeQ1DtnfYd5kfG1C9D8KlEBFwYHaiEnPrTkewvtioN f+mPN+4TM7+np8x91s64tV6Cj7uEfhkBSRITLyKRxLjegHhOSUt2RSPq48KexM0ZeR69 Fvqw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=dlBkhrJh6l4hGeTszGUJPOcQ5pjB28L6U/hyZsHmI/A=; b=Ss5I6c9ckbTaX2PRPdLRLp7pgcaV65/dVmZ+0tDbCCFmYQ/UShGF+9aKX+sqxMgbbI RSaN6en2Clnefm3Jjlk4IxOntAG7w+RhsDAvNICU91sFFIEh4kngnjrVZkdDG6ZbF7UG yaOa0BrQOmtrOsNIrbkj2IGx0A9U5pmsMlTbQGKnbYnd8ogsCUKKkPjXX5tadBODuNJ9 F9Uj6r4pVWCFaO1Ge3aThQBPVZgJPmNslF4xOSmZEzM2w0iFztKIGMiG6/MvOpBMfIBy mVNKd21M0KSnnjDM3Bip2z6QfHVNwdcrCai8ba8J+lvw/VNOE7hVxooVbCd7BWVz83Qs WAUA== X-Gm-Message-State: AKaTC01MjcFcrxFRU6GBbvkH8pFU69M72TIidhp6Tmks7QqbELIi4i59+R4awNg7IwjQtyT3kw/jHlM0mao2XA== X-Received: by 10.36.28.2 with SMTP id c2mr1279605itc.105.1481198372284; Thu, 08 Dec 2016 03:59:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.163.19 with HTTP; Thu, 8 Dec 2016 03:59:31 -0800 (PST) From: tjw ietf Date: Thu, 8 Dec 2016 06:59:31 -0500 Message-ID: To: Tools Team Discussion Content-Type: multipart/alternative; boundary=001a11444024d26fb40543245eb8 Archived-At: Subject: [Tools-discuss] IPR claims not following original document on tools.ietf.org X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2016 11:59:52 -0000 --001a11444024d26fb40543245eb8 Content-Type: text/plain; charset=UTF-8 When our draft https://datatracker.ietf.org/doc/draft-dickinson-dnsop-dns-capture-format/ Was adopted and replaced by this one: https://datatracker.ietf.org/doc/draft-ietf-dnsop-dns-capture-format/ the IPR claims followed along. However, this was not the case with the older tools.ietf.org versions: https://tools.ietf.org/html/draft-dickinson-dnsop-dns-capture-format-00 https://tools.ietf.org/html/draft-ietf-dnsop-dns-capture-format-00 tim --001a11444024d26fb40543245eb8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable