client.js uses the following

rfcRef.href = `https://www.rfc-editor.org/refs/bibxml/reference.RFC.${rfcNum}.xml`

It should point to bib.ietf.org instead as it is now the source for BibXML for I-Ds and RFCs:

rfcRef.href = `https://bib.ietf.org/public/rfc/bibxml/reference.RFC.${rfcNum}.xml`

not sure whether that's out of scope: https://github.com/dret/webconcepts has the idea of "concepts" and "values", which at some level are close to IANA registries and the values in them. it focuses on web-API level things. but there is some data to play around with: http://webconcepts.info/specs/IETF/RFC/ lists 177 RFCs and there is structured data about them. http://webconcepts.info/JSON explains the JSON data available, but i could easily create other data (in XML or JSON) if that would work better.
if there is an opportunity to support this more structured view of RFCs, that would be nice, and i'd be willing to put some effort into making data available from http://webconcepts.info/.

Hi，is there an API or method to get all RFC numbers related to one specific protocol(eg:HTTP) ?
Because I found this web page has no network request when I search RFCs about one protocol, so I can't get it by writing a crawler.

It would be interesting to surface this information in some fashion.

eg

https://github.com/lucaong/minisearch

Steps to reproduce

1. Set the flag "Show obsolete and historic" (just in case)
2. Search for "pgp"

Expected behaviour

Search results should show RFCs with "PGP" in the title, e.g. RFC 4880.

Actual behaviour

Search results show only some RFCs with "OpenPGP" in the title. Many other (arguably important, like 4880) OpenPGP RFCs are missing.

I am not sure if this affects other keywords as well.

Screenshots

Searching for "pgp":

Searching for "openpgp":

Many collections under the tags.json file have sorted array of rfcs already, but a few are unsorted. Enforcing sorting in it can make the maintenance easier as the list grows, because it will reduce the chances of accidental duplicate entries within the same collection. I can create a PR if this is something desired by the maintainers.

To make sure that tags reflect the latest documents, if a cited RFC is obsoleted by another, it should be used instead.

Makes it easier to keep things up to date.

Right now, typing in a number only brings up a single best match for input so far. It'd be interesting if all prefix-matching RFCs were listed, maybe even from the first digit. 0 would likely need special casing.

Yup, my memory sucks too -- but I think that being able to search by the RFC number (e.g: RFC1034) would be helpful - people keep referring to documents by number, and it's often useful to be able to look them up by that as well. I think: "RFC1034", "RFC 1034" and possibly just "1034" -> "Domain Names - Concepts And Facilities"

Hi!

I just checked a few RFCs, most of them were found, but this one for example missing:
https://datatracker.ietf.org/doc/html/draft-cavage-http-signatures-12

Cheers.

Hi, is there a way to search for (active) drafts ?

I also saw the issue template, but I am a bit confused: don't you fetch the RFCs using an API from IETF ? Why a maintainer is needed ? For instance, I wanna track some RFCs regarding WebRTC, some of which are drafts like https://tools.ietf.org/html/draft-ietf-rtcweb-security-arch-20.

Maybe a crowdsourced measure of relevance or quality could be set up, so that we can tell the difference between (for example) HTTPS and SHTTP...

Could be part of a protocol design collection, and/or a liaison collection...

... on top-level page.

Focus on use cases.

I think it might be useful to have the same color codes for tags as on datatracker:

From site's source (reordered):

.bgwhite  { background-color: white; }
.bgred    { background-color: #F44; }
.bgorange { background-color: #FA0; }
.bgyellow { background-color: #EE0; }
.bgmagenta{ background-color: #F4F; }
.bgblue   { background-color: #66F; }
.bgcyan   { background-color: #4DD; }
.bggreen  { background-color: #4F4; }
.bggrey   { background-color: #666; }
.bgbrown  { background-color: #840; }