From nobody Tue Oct 6 10:09:07 2020 Return-Path: X-Original-To: tools-implementation@ietfa.amsl.com Delivered-To: tools-implementation@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 162593A0D9B for ; Tue, 6 Oct 2020 10:09:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.91 X-Spam-Level: X-Spam-Status: No, score=-101.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_WELCOMELIST=-0.01, 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 IYKjjqryXVlx for ; Tue, 6 Oct 2020 10:09:02 -0700 (PDT) Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC7183A0C3D for ; Tue, 6 Oct 2020 10:09:01 -0700 (PDT) Received: from mail.amsl.com (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTPS id 9725D3C24C1 for ; Tue, 6 Oct 2020 10:08:51 -0700 (PDT) Received: from [192.168.86.10] (173-8-133-94-SFBA.hfc.comcastbusiness.net [173.8.133.94]) by c8a.amsl.com (Postfix) with ESMTPSA id 8397F3C24C0 for ; Tue, 6 Oct 2020 10:08:51 -0700 (PDT) To: tools-implementation@ietf.org From: Glen Organization: AMS Message-ID: <6b0b23ba-3ba6-97ab-b9e4-a944b2d8df6f@amsl.com> Date: Tue, 6 Oct 2020 10:09:00 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.3.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Archived-At: Subject: [Tools-implementation] FTP updates applied X-BeenThere: tools-implementation@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Implementation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Oct 2020 17:09:06 -0000 All - The new ftp service is now online, rooted on /a/ftp, as previously described. Henrik has updated Ghostlink to perform the immediate syncs of internet-drafts and some other items, and intra- and inter-server backups have been created and checked. Proftpd has been repointed, and we are now done. Glen From nobody Tue Oct 6 10:10:52 2020 Return-Path: X-Original-To: tools-implementation@ietfa.amsl.com Delivered-To: tools-implementation@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8D893A0D9B for ; Tue, 6 Oct 2020 10:10:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.292 X-Spam-Level: X-Spam-Status: No, score=-2.292 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.213, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.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 YO3F8Bh2cB3U for ; Tue, 6 Oct 2020 10:10:50 -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 097203A0D9D for ; Tue, 6 Oct 2020 10:10:47 -0700 (PDT) Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 096HAk1E050299 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Tue, 6 Oct 2020 12:10:47 -0500 (CDT) (envelope-from rjsparks@nostrum.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1602004247; bh=f+TgYKMe+AkELPGGPz61/Yd+6OGyT+CtSEwq/JUBulk=; h=Subject:To:References:From:Date:In-Reply-To; b=XGOIVWrWZ3uym8FAAqpwZ1muSyFPZMIQZqI8MwaHKSXN0oz7Hnkz0oqeat/H20KfV Zcr0fUOCVwcS6gm1v1lYaaL105hGIvQU7ywImK2HX8IUSX+Xg52jvFYd/OdDKnNnjU DuFsmhHDyAVJRrL1cn5qSNGSz+8DKTHoZElOSolQ= X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local To: tools-implementation@ietf.org References: <6b0b23ba-3ba6-97ab-b9e4-a944b2d8df6f@amsl.com> From: Robert Sparks Message-ID: <60444f15-115a-82f0-5a98-539dec6ae6e5@nostrum.com> Date: Tue, 6 Oct 2020 12:10:44 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:78.0) Gecko/20100101 Thunderbird/78.3.1 MIME-Version: 1.0 In-Reply-To: <6b0b23ba-3ba6-97ab-b9e4-a944b2d8df6f@amsl.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: Re: [Tools-implementation] FTP updates applied X-BeenThere: tools-implementation@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Implementation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Oct 2020 17:10:51 -0000 Thank you both! RjS On 10/6/20 12:09 PM, Glen wrote: > All - > > The new ftp service is now online, rooted on /a/ftp, as previously > described. > > Henrik has updated Ghostlink to perform the immediate syncs of > internet-drafts and some other items, and intra- and inter-server > backups have been created and checked. > > Proftpd has been repointed, and we are now done. > > Glen > From nobody Thu Oct 22 11:27:59 2020 Return-Path: X-Original-To: tools-implementation@ietfa.amsl.com Delivered-To: tools-implementation@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF12D3A0A6E for ; Thu, 22 Oct 2020 11:27:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.078 X-Spam-Level: X-Spam-Status: No, score=-2.078 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.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 4Yb9NKqKjWdt for ; Thu, 22 Oct 2020 11:27:55 -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 474253A0A96 for ; Thu, 22 Oct 2020 11:27:55 -0700 (PDT) Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 09MIRrQM037674 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Thu, 22 Oct 2020 13:27:53 -0500 (CDT) (envelope-from rjsparks@nostrum.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1603391273; bh=mKDK8B57xhaMeYYlPS/nKOYf6/5DX0i60z0fL09mJDE=; h=To:From:Subject:Date; b=Y/L2a5bp9l9emr6vdq2JqfVioU2C9N1eRS2CXt/Bs9LarftSGFgySREuxerL/kUx/ ODFizNXjyeB9wjcWLAOZQWJPpb/ygEJil14LrMsDcugDdHJkMVVPogOsnZ+Jn2CtFn JltfTotdaL0jXh4qTiQjvq4unUW1wF9InLDNQM78= X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local To: "tools-implementation@ietf.org" From: Robert Sparks Message-ID: <311060fe-463e-33ae-1dfd-3ebc951f8edf@nostrum.com> Date: Thu, 22 Oct 2020 13:27:53 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:78.0) Gecko/20100101 Thunderbird/78.3.3 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Language: en-US Archived-At: Subject: [Tools-implementation] Requiring Javascript for anything that needs login on the datatracker. X-BeenThere: tools-implementation@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Implementation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Oct 2020 18:27:57 -0000 I believe we are at a point that we need to lift (or at least=20 significantly change) the requirement that most of our pages work=20 without javascript. We already have many pages that have crossed that line - people who are=20 doing anything really significant with the datatracker now need to allow = javascript for things to function. As we start to try to further improve the speed of the datatracker one=20 of the things we will want to look at is taking advantage of front-end=20 frameworks like React (or at least following some of the same patterns=20 for how they work). So I think we should start setting the=C2=A0 expectation that for anythin= g=20 that requires you to login to the datatracker, you should expect to be=20 running javascript. That moves the line for keeping pages functional=20 without it to those things that you can do without logging in. A concrete example of where this will make a difference: Right now, it isn't immediately straightforward to cache results from=20 the datatracker because we have a section on the page that is highly=20 personalized to the logged in person (look at the menu under the logged=20 in name). To blindly cache a page would cache things based on whoever=20 was logged in as the cache was written. Someone else getting such a=20 cached response would see a page with the wrong login (and other details = in that menu). We can work around that, with some effort, by caching=20 _parts_ of the page, mostly using template caching, but we have to be=20 careful in that case to ensure that the parts that are cached are=20 logged-in-user invariant, and be very careful with where the database=20 reads happen. See=20 https://trac.tools.ietf.org/tools/ietfdb/changeset/18625/trunk for a=20 short example of the kind of care that has to be exercised. One path we could take that would let us more easily cache pages in a=20 general fashion would be to move the rendering of the logged-in-user=20 specific information into javascript, so that what pages return are=20 login-invariant. The browser could then fetch and render the=20 logged-in-user specific things. But that would require javascript, and=20 would push the boundary of where javascript is required to "all pages=20 where a user is logged in". RjS From nobody Thu Oct 22 11:32:27 2020 Return-Path: X-Original-To: tools-implementation@ietfa.amsl.com Delivered-To: tools-implementation@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 670C33A0A96 for ; Thu, 22 Oct 2020 11:32:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.897 X-Spam-Level: X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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 pMjXk42pyfml for ; Thu, 22 Oct 2020 11:32:24 -0700 (PDT) Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C8F03A0A62 for ; Thu, 22 Oct 2020 11:32:24 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id D6623300B31 for ; Thu, 22 Oct 2020 14:32:21 -0400 (EDT) X-Virus-Scanned: amavisd-new at mail.smeinc.net Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id YAVTXa8oPi2i for ; Thu, 22 Oct 2020 14:32:20 -0400 (EDT) Received: from [192.168.1.161] (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 2DEA83005DB; Thu, 22 Oct 2020 14:32:20 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\)) From: Russ Housley In-Reply-To: <311060fe-463e-33ae-1dfd-3ebc951f8edf@nostrum.com> Date: Thu, 22 Oct 2020 14:32:21 -0400 Cc: "tools-implementation@ietf.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <311060fe-463e-33ae-1dfd-3ebc951f8edf@nostrum.com> To: Robert Sparks X-Mailer: Apple Mail (2.3445.104.17) Archived-At: Subject: Re: [Tools-implementation] Requiring Javascript for anything that needs login on the datatracker. X-BeenThere: tools-implementation@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Implementation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Oct 2020 18:32:26 -0000 This has been a comunity discussion point in the past. I think the IESG = needs to make the call, perhaps after further discussion. Russ > On Oct 22, 2020, at 2:27 PM, Robert Sparks = wrote: >=20 > I believe we are at a point that we need to lift (or at least = significantly change) the requirement that most of our pages work = without javascript. >=20 > We already have many pages that have crossed that line - people who = are doing anything really significant with the datatracker now need to = allow javascript for things to function. >=20 > As we start to try to further improve the speed of the datatracker one = of the things we will want to look at is taking advantage of front-end = frameworks like React (or at least following some of the same patterns = for how they work). >=20 > So I think we should start setting the expectation that for anything = that requires you to login to the datatracker, you should expect to be = running javascript. That moves the line for keeping pages functional = without it to those things that you can do without logging in. >=20 > A concrete example of where this will make a difference: >=20 > Right now, it isn't immediately straightforward to cache results from = the datatracker because we have a section on the page that is highly = personalized to the logged in person (look at the menu under the logged = in name). To blindly cache a page would cache things based on whoever = was logged in as the cache was written. Someone else getting such a = cached response would see a page with the wrong login (and other details = in that menu). We can work around that, with some effort, by caching = _parts_ of the page, mostly using template caching, but we have to be = careful in that case to ensure that the parts that are cached are = logged-in-user invariant, and be very careful with where the database = reads happen. See = https://trac.tools.ietf.org/tools/ietfdb/changeset/18625/trunk for a = short example of the kind of care that has to be exercised. >=20 > One path we could take that would let us more easily cache pages in a = general fashion would be to move the rendering of the logged-in-user = specific information into javascript, so that what pages return are = login-invariant. The browser could then fetch and render the = logged-in-user specific things. But that would require javascript, and = would push the boundary of where javascript is required to "all pages = where a user is logged in". >=20 > RjS From nobody Fri Oct 23 12:09:18 2020 Return-Path: X-Original-To: tools-implementation@ietfa.amsl.com Delivered-To: tools-implementation@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADD193A12A0 for ; Fri, 23 Oct 2020 12:09:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.078 X-Spam-Level: X-Spam-Status: No, score=-2.078 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.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 X01-pPLtKOX4 for ; Fri, 23 Oct 2020 12:09:15 -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 72ABC3A0A96 for ; Fri, 23 Oct 2020 12:09:15 -0700 (PDT) Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 09NJ9Eh3009039 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Fri, 23 Oct 2020 14:09:14 -0500 (CDT) (envelope-from rjsparks@nostrum.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1603480154; bh=2BEyaeV3sTFQW75KBwo2EFMgIUO+bsRcpb1P1zWz+fk=; h=To:From:Subject:Date; b=qxbolwtDk7sztV6q18fya1K1MCjJ5T3W3k6rek0k4+qsa1xUfwrzKVuaGUNoyvEvg n9bLWXkMZbSQ7hsIxeHPsBjTzXKtHxbv7Drp0MrzWbJEyU9W/TRniWDcwOang0CZS2 tEJHG1n2SXTVDqsIu2GNuBLBycsX4jTFeLUAi6KA= X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local To: "tools-implementation@ietf.org" From: Robert Sparks Message-ID: <07d3ab8d-360f-8765-30c5-c28a58773b2f@nostrum.com> Date: Fri, 23 Oct 2020 14:09:13 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:78.0) Gecko/20100101 Thunderbird/78.4.0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------D81E54A285F339671AF0ECAB" Content-Language: en-US Archived-At: Subject: [Tools-implementation] Changing the id-announce template to remove ftp X-BeenThere: tools-implementation@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Implementation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Oct 2020 19:09:17 -0000 This is a multi-part message in MIME format. --------------D81E54A285F339671AF0ECAB Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable All (but especially Roman: I propose that we change the following text, that appears in the=20 messages sent to i-d-announce: > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ To: "Internet-Drafts are also via rsync at rsync.ietf.org::id-archive" Note that earlier parts of the message already point to how to get=20 drafts over https. (See=20 https://mailarchive.ietf.org/arch/browse/i-d-announce/ if you haven't=20 looked at i-d-announce recently). Questions: 1) I think we can just make this change. Do we need to give the IESG a=20 heads up? 2) The message points to the archive, and not the repository. There has=20 been confusion about the distinction and having things point to the=20 archive has helped resolve that. But, fwiw, there is also an rsync point = for the repository. I don't think we should point there, but does anyone = disagree? --------------D81E54A285F339671AF0ECAB Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

All (but especially Roman:

I propose that we change the following text, that appears in the messages sent to i-d-announce:

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
To:

"Internet-Drafts are also via rsync at rsync.ietf.org::id-archive"

Note that earlier parts of the message already point to how to get drafts over https. (See https://mailarchive.ietf.org/arch/browse/i-d-announce/ if you haven't looked at i-d-announce recently).

Questions:

1) I think we can just make this change. Do we need to give the IESG a heads up?

2) The message points to the archive, and not the repository. There has been confusion about the distinction and having things point to the archive has helped resolve that. But, fwiw, there is also an rsync point for the repository. I don't think we should point there, but does anyone disagree?

--------------D81E54A285F339671AF0ECAB-- From nobody Fri Oct 23 12:17:48 2020 Return-Path: X-Original-To: tools-implementation@ietfa.amsl.com Delivered-To: tools-implementation@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B83C3A13B3 for ; Fri, 23 Oct 2020 12:17:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.896 X-Spam-Level: X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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 PKb4TTkPXujE for ; Fri, 23 Oct 2020 12:17:45 -0700 (PDT) Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB2723A13B2 for ; Fri, 23 Oct 2020 12:17:44 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 49506300BA6 for ; Fri, 23 Oct 2020 15:17:41 -0400 (EDT) X-Virus-Scanned: amavisd-new at mail.smeinc.net Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id VlIWV9O1D67H for ; Fri, 23 Oct 2020 15:17:40 -0400 (EDT) Received: from [192.168.1.161] (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 76EC6300B31; Fri, 23 Oct 2020 15:17:40 -0400 (EDT) From: Russ Housley Message-Id: <42D68178-814E-45FB-BE46-63591AAF2FD7@vigilsec.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_0F4F8628-DF5F-421B-B1A0-E46588939E81" Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\)) Date: Fri, 23 Oct 2020 15:17:41 -0400 In-Reply-To: <07d3ab8d-360f-8765-30c5-c28a58773b2f@nostrum.com> Cc: "tools-implementation@ietf.org" To: Robert Sparks References: <07d3ab8d-360f-8765-30c5-c28a58773b2f@nostrum.com> X-Mailer: Apple Mail (2.3445.104.17) Archived-At: Subject: Re: [Tools-implementation] Changing the id-announce template to remove ftp X-BeenThere: tools-implementation@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Implementation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Oct 2020 19:17:47 -0000 --Apple-Mail=_0F4F8628-DF5F-421B-B1A0-E46588939E81 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Robert: >=20 > All (but especially Roman: >=20 > I propose that we change the following text, that appears in the = messages sent to i-d-announce: >=20 >=20 >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ = To: >=20 > "Internet-Drafts are also via rsync at rsync.ietf.org::id-archive" >=20 > Note that earlier parts of the message already point to how to get = drafts over https. (See = https://mailarchive.ietf.org/arch/browse/i-d-announce/ = if you haven't = looked at i-d-announce recently). >=20 > Questions: >=20 > 1) I think we can just make this change. Do we need to give the IESG a = heads up? >=20 Any change should go through the IESG. > 2) The message points to the archive, and not the repository. There = has been confusion about the distinction and having things point to the = archive has helped resolve that. But, fwiw, there is also an rsync point = for the repository. I don't think we should point there, but does anyone = disagree? >=20 I agree with you. Russ --Apple-Mail=_0F4F8628-DF5F-421B-B1A0-E46588939E81 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii Robert:


All (but especially Roman:

I propose that we change the following text, that appears in the messages sent to i-d-announce:


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
To:

"Internet-Drafts are also via rsync at rsync.ietf.org::id-archive"

Note that earlier parts of the message already point to how to get drafts over https. (See https://mailarchive.ietf.org/arch/browse/i-d-announce/ if you haven't looked at i-d-announce recently).

Questions:

1) I think we can just make this change. Do we need to give the IESG a heads up?

Any change should go through the IESG.

2) The message points to the archive, and not the repository. There has been confusion about the distinction and having things point to the archive has helped resolve that. But, fwiw, there is also an rsync point for the repository. I don't think we should point there, but does anyone disagree?

I agree with you.

Russ

--Apple-Mail=_0F4F8628-DF5F-421B-B1A0-E46588939E81-- From nobody Mon Oct 26 06:33:44 2020 Return-Path: X-Original-To: tools-implementation@ietfa.amsl.com Delivered-To: tools-implementation@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10CA23A0AF5 for ; Mon, 26 Oct 2020 06:33:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.146 X-Spam-Level: X-Spam-Status: No, score=-2.146 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.247, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 BdMTo8NDgNZu for ; Mon, 26 Oct 2020 06:33:40 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E35F3A0B2D for ; Mon, 26 Oct 2020 06:33:33 -0700 (PDT) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:52444 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1kX2cp-00006B-Dh; Mon, 26 Oct 2020 06:33:30 -0700 To: Robert Sparks , "tools-implementation@ietf.org" References: <07d3ab8d-360f-8765-30c5-c28a58773b2f@nostrum.com> From: Henrik Levkowetz Message-ID: <4ae7e4e9-6391-78f9-f8e5-d27df1941e36@levkowetz.com> Date: Mon, 26 Oct 2020 14:33:13 +0100 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: <07d3ab8d-360f-8765-30c5-c28a58773b2f@nostrum.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="2RcTfx8fQuRv57KPd5q7T4hEVMiX0Ef6L" X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: tools-implementation@ietf.org, rjsparks@nostrum.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) X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [Tools-implementation] Changing the id-announce template to remove ftp X-BeenThere: tools-implementation@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Implementation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Oct 2020 13:33:42 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --2RcTfx8fQuRv57KPd5q7T4hEVMiX0Ef6L Content-Type: multipart/mixed; boundary="RXV5hDlHcWg2LtOLdu2NFcVp3e20uPUVC"; protected-headers="v1" From: Henrik Levkowetz To: Robert Sparks , "tools-implementation@ietf.org" Message-ID: <4ae7e4e9-6391-78f9-f8e5-d27df1941e36@levkowetz.com> Subject: Re: [Tools-implementation] Changing the id-announce template to remove ftp References: <07d3ab8d-360f-8765-30c5-c28a58773b2f@nostrum.com> In-Reply-To: <07d3ab8d-360f-8765-30c5-c28a58773b2f@nostrum.com> --RXV5hDlHcWg2LtOLdu2NFcVp3e20uPUVC Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2020-10-23 21:09, Robert Sparks wrote: > All (but especially Roman: >=20 > I propose that we change the following text, that appears in the=20 > messages sent to i-d-announce: >=20 >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ > To: >=20 > "Internet-Drafts are also via rsync at rsync.ietf.org::id-archive" >=20 > Note that earlier parts of the message already point to how to get=20 > drafts over https. (See=20 > https://mailarchive.ietf.org/arch/browse/i-d-announce/ if you haven't=20 > looked at i-d-announce recently). >=20 > Questions: >=20 > 1) I think we can just make this change. Do we need to give the IESG a = > heads up? >=20 > 2) The message points to the archive, and not the repository. There has= =20 > been confusion about the distinction and having things point to the=20 > archive has helped resolve that. But, fwiw, there is also an rsync poin= t=20 > for the repository. I don't think we should point there, but does anyon= e=20 > disagree? Nope, WFM. Henrik --RXV5hDlHcWg2LtOLdu2NFcVp3e20uPUVC-- --2RcTfx8fQuRv57KPd5q7T4hEVMiX0Ef6L Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl+W0BkACgkQTptXS4+7 FxqEkRAAjDT1ifZ3bOBQP/d5iTxE+elzO8v77otUAyCHYWRSzVafflqelG1eVYiu YFhKxKshubuhtkHNjddrFoxnMnsnwzJJVsgllclAyY2xCwpM3iKh6OwPrDSoK2Ak hKacy8fg+0Y7/4z9Wcm0odVcJQY/N/pBWrMtJZRjn/+WUvGv+QqTwCMOfE/mZ+Ft a1OlDEgZt8TCI7KYJuyrm/ZgYEjuD6n1rc0QEMpIbJu6FZS2VQ/J3dcRgd0v57hY zApN41MDZECPLCGuaK4zrhdy6ZCMWrq/fucAuXXCPq9SP7BE08OW7U5PhRJnK03Z xO69etG1cxS3qBJHUd/nJqHGjLQIK9BtYc5fGOQPozdRCMHhsqbw1rHv9rN1Rb0h aqgGqoiuOMwTiHMFnEVXJjDknSyrwProS7u5OS/jbcMWorce7TufaF00hl/+OhCi IMs9g8OBIS6hgAtt82fggLyKsJJx8Gz6GN9sI7rQ2VLlqnpoyxu1LshzZkoYTWa6 QG0GWFZr6UNN7yYW5fkL8tnD3fo85mv2wa7SSZ6phHQApoiOOMEBOYtjlidMkSY+ nfGTsmC5XTuDO+M7u5mxFUdXP+gULuhes8Br2L89n6yShJw+lKdnXlm/pbJZfXTz tttSJ8+yR+RxJgl4dXWOa7+Yc2/+5L7jEiZsLJUZNbPkgrl9gYw= =bvkJ -----END PGP SIGNATURE----- --2RcTfx8fQuRv57KPd5q7T4hEVMiX0Ef6L--