Re: [Tools-implementation] Fwd: Emacs lock files in rfc rsync

Specifically this would be the next tools-implementation team meeting.

We don't have one of those scheduled (as we didn't have anything 
immediate to discuss). We can schedule one now.

1600 UTC had been working for us - is it still a reasonable time? If so, 
is Fri 12Feb open for folks.

RjS

On 2/5/21 1:19 PM, Roman Danyliw wrote:
> Hi Glen!
> (looping in Greg)
>
> Concur about adding this as an agenda item for the next meeting  A few related thoughts:
>
> (1) During the community consultation on FTP, parties noted that we should improve our rsync documentation.  All I can find is:
>
> https://www.ietf.org/standards/ids/internet-draft-mirror-sites/
>
> Minimally, I was thinking maybe proving a list of the sync points and what they contain.
>
> (2) https://www.ietf.org/standards/ids/internet-draft-mirror-sites/ currently says "All Internet-Drafts are available via ftp, http, and rsync. This page provided details about these services, including locations and instructions related to I-D mirrors."
>
> -- s/via ftp, http, and rsync/via ftp, https, and rsync/
>
> -- This page only talks about rsync and not the others.  Should we be pointing to https://www.ietf.org/id/ as the reference for HTTPS?
>
> (3) As you noted below that ::rfc is not authoritative, we might want to scrub the following descriptions to annotate which are mirrors of something else (i.e., ::rfc, ::iana, ::iana-timezone) -- say s/Repository of RFCs/Mirror of the repository of RFCs (see also rsync.rfc-editor.org)/
>
> roman@ubuntu:~/ietf$ rsync rsync.ietf.org::
> everything-ftp 	- The entire IETF FTP Archive
> internet-drafts	- The Internet Draft Repository (currently active drafts)
> id-archive     	- The Internet Draft Archive (both active and expired drafts)
> iesg-minutes   	- IESG Minutes
> proceedings    	- Repository of Proceedings
> xml2rfc.bibxml 	The xml2rfc citation libraries
> charter        	- Repository of WG Charters
> concluded-wg-ietf-mail-archive	- Older list text archives
> conflict-reviews	- Repository of Conflict Review documents
> iana           	- IANA assignments
> iana-timezone  	- IANA Time Zone Datatbase (see also http://www.iana.org/time-zones)
> legacy-files   	- Legacy material supporting long-lived URLs
> mailman-archive	- Repository of Mailing List Text Archives
> rfc            	- Repository of RFCs
> slides         	- Repository of Slide Documents
> status-changes 	- Repository of Status Change Documents
>
> (4) We likely also want to discuss the legacy status of ::rfc.
>
> Roman
>
>> -----Original Message-----
>> From: Tools-implementation <tools-implementation-bounces@ietf.org> On
>> Behalf Of Glen
>> Sent: Thursday, February 4, 2021 6:40 PM
>> To: tools-implementation@ietf.org
>> Subject: [Tools-implementation] Fwd: Emacs lock files in rfc rsync
>>
>> Something we should review in our next meeting.   I'll provide the
>> technical details at that time.  (Roman, sorry I forgot to cc you on the original
>> reply, I missed your presence in the header until after I hit send, but this is the
>> same email reply below.)
>>
>> Glen
>>
>> -------- Forwarded Message --------
>> Subject: Re: Fwd: Emacs lock files in rfc rsync
>> Date: Thu, 4 Feb 2021 15:38:02 -0800
>> From: Glen <glen@amsl.com>
>> Organization: AMS
>> To: Eric Rescorla <ekr@rtfm.com>
>> CC: Sandy Ginoza <sginoza@amsl.com>, Alice Russo <arusso@amsl.com>, John
>> R Levine <johnl@taugh.com>
>>
>> All -
>>
>> In the interest of time, I am just grouping everyone together and replying to
>> this thread directly.
>>
>>>> From: Eric Rescorla <ekr@rtfm.com>
>>>> Subject: Emacs lock files in rfc rsync
>>>> Date: February 4, 2021 at 1:06:27 PM PST
>>>> To: RFC Editor <rfc-editor@rfc-editor.org>, Roman Danyliw
>>>> <rdd@cert.org> Hi folks.
>>>> I just rsynced the rfc directory and I see that several of the files have Emacs
>> lock files [0] associated with them:
>>>> lrwxrwxrwx  1 ekr  staff  39 Mar 16  2016 .#bcp-ref.txt ->
>>>> ahagens@rfcpa.amsl.com.16317:1457089460
>>>> lrwxrwxrwx  1 ekr  staff  39 Mar 27  2019 .#rfc-index.xml ->
>>>> ahagens@rfcpa.amsl.com.12369:1551880913
>>>> Aside from just creating problems when someone else tries to edit the files
>> in Emacs, it suggests that you might have some kind of process problem,
>> because this material should be machine generated, and people shouldn't be
>> editing it in a way that the directories are just raw synced to the server.
>>
>> Eric -
>>
>> My apologies, but you are not using the authoritative source for your rsync.
>> You stated that you're using:
>>
>>> rsync.ietf.org::rfc
>> That is the IETF's legacy mirror of RFCs.  I do not refer or recommend it.  It
>> appears to be a legacy configuration, and to have some duplication in it.
>> Moreover, for reasons unknown to me, it is being rsynced without the --delete
>> option, which means it will retain every file it ever saw during any prior rsync.
>> That is why you are seeing those files.  They existed at some interval in the
>> past; they do not exist (on the RFC servers) now.
>>
>> I will raise this with the Tools Implementation Team to see if (a) this behavior
>> should change or (b) the IETF copy should be removed or referred.  Removing
>> files from it, or making changes to it, are not things I can "just do" on my own
>> in my role.  Note that they are working on other, larger projects right now, so
>> this will need some time before it can get attention.
>>
>> In the meantime, I recommend that you change your configuration to rsync
>> your RFCs from rfc-editor.org:: , which is the authoritative source for RFCs.
>> They have a catalog of options, one of which will I hope suit:
>>
>> # rsync rfc-editor.org::
>> everything-ftp  Everything FTP
>> refs            XML references for RFCs (for use with xml2rfc)
>> rfcs            Contents of in-notes including subdirectories std, bcp,
>> fyi, and ien
>> rfcs-text-only  Only the text files from the directories in [rfcs]
>> rfc-ed-all      Entire repository (excluding internet-drafts)
>> internet-drafts Internet Drafts
>> ids-text-only   Only text files from the Internet Drafts mirror
>> rfcs-pdf-only   PDF versions of ASCII RFCs to ensure correct page
>> breaks, etc
>> rfcs-exclude-json       Contents of [rfcs] excluding JSON files
>> rfcs-json-only  Only the JSON files from the directories in [rfcs]
>>
>> In the meantime, the files you referred to, which may exist on the legacy IETF
>> copy, will not be removed, nor will any other changes be made to the IETF
>> copy, until the Tools Implementation Team can carve out time to review this
>> and determine the correct solution.
>>
>> I will send the relevant information to them now, to get this on their radar.
>>
>> Thank you,
>> Glen
>>
>>
>>
>>
>> --
>> Tools-implementation mailing list
>> Tools-implementation@ietf.org
>> https://www.ietf.org/mailman/listinfo/tools-implementation