Implement new version/dynamic fetching for Internet-Drafts

[ronaldtse]

The Internet-Drafts dataset is the special dataset that combines serving from both bulk loaded data with the latest data coming straight from datatracker.ietf.org.

datatracker.ietf.org is the authoritative source of the data. The bulk data the BibXML services loads is from a periodic export from datatracker.

There are two types of references that are served by the service:

1. Unversioned Reference pattern: draft-{example-name}. This is in fact a redirect reference to the draft of the highest draft-number number.
2. Versioned Reference pattern: draft-{example-name}-{draft-number}. The {draft-number} is a two-digit sequential integer, starting from 00 or 01 incrementally.

For the Versioned Reference pattern (given draft-{example-name}-{draft-number}), the operating mode is:

• If the bulk Internet-Drafts dataset contains draft-{example-name}-{draft-number}, return it and done.
• If the bulk Internet-Drafts dataset does not contain draft-{example-name}-{draft-number}, then it means that datatracker.ietf.org may have a new draft number or the draft did not exist in the bulk dataset. The BibXML Service should then contact datatracker.ietf.org to load draft-{example-name}-{draft-number}.
  • If datatracker returns with data, then we cache the entry by entering it into our database, and return this.
  • If datatracker does not have this draft, it means that the draft does not exist. We return an error.

For the Unversioned Reference pattern (given draft-{example-name}), the operating mode is:

• We cannot know whether the draft-{example-name}-{draft-number} items we have are actually the newest.
• We will have to proxy the request to datatracker.ietf.org every single time.
• There may not be any point in caching this because again, we can never know. It would be better to err on the side of accuracy.