@blamejs/exceptd-skills 0.13.18 → 0.13.19

package/data/rfc-references.json

@@ -1287,7 +1287,8 @@
     "tracker": "https://docs.oasis-open.org/csaf/csaf/v2.0/csaf-v2.0.html",
     "relevance": "Machine-readable security advisory format adopted by EU CRA, CISA, and major vendor PSIRTs. Replaces the CVRF-1.2 format. Operator-facing: CSAF 2.0 documents carry the same advisory content traditionally found in vendor PDFs but in a parseable JSON form that consumers can ingest for fleet-wide impact assessment. exceptd emits CSAF-2.0 close.evidence_package bundles from `exceptd run --format csaf-2.0` for downstream auditor consumption.",
     "skills_referencing": [],
-    "last_verified": "2026-05-13"
+    "last_verified": "2026-05-19",
+    "abstract": "OASIS Common Security Advisory Framework (CSAF) version 2.0 — the canonical machine-readable format for vendor security advisories. CSAF-2.0 documents are signed JSON conforming to a strict schema (product_tree, vulnerabilities[], document.tracking, document.references), enabling automated ingestion by SBOM tooling, vulnerability scanners, and incident-response platforms. Supersedes the legacy CVRF format. Required for vendors participating in the OpenSSF / CISA / ENISA coordinated-disclosure ecosystem."
   },
   "DRAFT-IETF-TLS-ECDHE-MLKEM": {
     "number": null,
@@ -1301,7 +1302,8 @@
     "skills_referencing": [
       "pqc-first"
     ],
-    "last_verified": "2026-05-11"
+    "last_verified": "2026-05-19",
+    "abstract": "IETF Internet-Draft (TLS WG) defining hybrid ECDHE + ML-KEM key exchange for TLS 1.3. Combines classical X25519 / P-256 ECDHE with the NIST FIPS 203 ML-KEM (Kyber) post-quantum KEM in a single handshake exchange so a successful TLS connection requires breaking BOTH primitives. Foundational primitive for federal PQ-ready posture and EU NIS2 + DORA crypto-agility obligations."
   },
   "DRAFT-IETF-TLS-HYBRID-DESIGN": {
     "number": null,
@@ -1314,7 +1316,8 @@
     "skills_referencing": [
       "pqc-first"
     ],
-    "last_verified": "2026-05-11"
+    "last_verified": "2026-05-19",
+    "abstract": "IETF Internet-Draft (TLS WG) — design rationale and security analysis for hybrid post-quantum + classical TLS 1.3 handshakes. Defines the wire format, key-derivation chain, and downgrade-resistance properties for hybrid key-exchange. Cited by RFC 9763 (ML-KEM in TLS 1.3) + RFC 9764 (ML-DSA in TLS 1.3) as the architectural foundation."
   },
   "ISO-29147": {
     "number": null,
@@ -1324,7 +1327,8 @@
     "tracker": "https://www.iso.org/standard/72311.html",
     "relevance": "Internationally-recognized vulnerability-disclosure procedure standard. Operator-facing: an org claiming a CVD program must demonstrate the documented procedures cover receipt, triage, advisory drafting, notification, and post-disclosure review. Twin to ISO 30111 (handling); together they form the disclosure ↔ handling pair. The RFC 9116 (security.txt) artifact is the operator-facing surface that operationalizes ISO 29147 receipt requirements.",
     "skills_referencing": [],
-    "last_verified": "2026-05-13"
+    "last_verified": "2026-05-19",
+    "abstract": "ISO/IEC 29147:2018 — Information technology, Security techniques, Vulnerability disclosure. Defines the receipt-side requirements for an organisation's vulnerability disclosure program (VDP): point-of-contact discoverability, acknowledgement timelines, communication protocols, advisory publication. Paired with ISO/IEC 30111 (vulnerability handling processes). Referenced by NIS2 Art.12 + EU CRA Annex I §1(2)(c) as the baseline VDP standard."
   },
   "ISO-30111": {
     "number": null,
@@ -1334,7 +1338,8 @@
     "tracker": "https://www.iso.org/standard/69725.html",
     "relevance": "Internal handling counterpart to ISO 29147. Defines the internal processes (investigation, resolution, release) that follow a disclosed vulnerability through to fix. Operator-facing: paired with ISO 29147 it supplies the end-to-end CVD lifecycle. Many compliance frameworks (NIS2, EU CRA) reference 'a documented vulnerability handling process'; ISO 30111 is the canonical artifact that satisfies the wording.",
     "skills_referencing": [],
-    "last_verified": "2026-05-13"
+    "last_verified": "2026-05-19",
+    "abstract": "ISO/IEC 30111:2019 — Information technology, Security techniques, Vulnerability handling processes. Defines the internal-side vulnerability-handling lifecycle: triage, investigation, resolution, release, post-release. Paired with ISO/IEC 29147 (disclosure-side requirements). Together the two standards cover the operator-facing vulnerability-handling obligation cited by NIS2 / EU CRA / FedRAMP / FDA premarket cybersecurity guidance."
   },
   "RFC-7591": {
     "number": 7591,
@@ -2348,7 +2353,25 @@
     "skills_referencing": [],
     "last_verified": "2026-05-19",
     "_auto_imported": true,
-    "_intake_method": "v0.13.18-bulk-curated-security-rfcs"
+    "_intake_method": "v0.13.18-bulk-curated-security-rfcs",
+    "abstract": "This document describes an experimental protocol for publicly logging the existence of Transport Layer Security (TLS) certificates as they are issued or observed, in a manner that allows anyone to audit certificate authority (CA) activity and notice the issuance of suspect certificates as well as to audit the certificate logs themselves. The intent is that eventually clients would refuse to honor certificates that do not appear in a log, effectively forcing CAs to add all issued certificates to the logs. Logs are network services that implement the protocol operations for submissions and queries that are defined in this document.",
+    "keywords": [
+      "TLS certificates"
+    ],
+    "working_group": "NON WORKING GROUP",
+    "stream": "IETF",
+    "authors": [
+      "B. Laurie",
+      "A. Langley",
+      "E. Kasper"
+    ],
+    "doi": "10.17487/RFC6962",
+    "page_count": 27,
+    "obsoleted_by": [
+      "RFC9162"
+    ],
+    "txt_url": "https://www.rfc-editor.org/rfc/rfc6962.txt",
+    "html_url": "https://www.rfc-editor.org/rfc/rfc6962.html"
   },
   "RFC-9162": {
     "number": 9162,
@@ -2457,7 +2480,27 @@
     "skills_referencing": [],
     "last_verified": "2026-05-19",
     "_auto_imported": true,
-    "_intake_method": "v0.13.18-bulk-curated-security-rfcs"
+    "_intake_method": "v0.13.18-bulk-curated-security-rfcs",
+    "abstract": "This document defines a standard profile for Route Origin Authorizations (ROAs). A ROA is a digitally signed object that provides a means of verifying that an IP address block holder has authorized an Autonomous System (AS) to originate routes to one or more prefixes within the address block. [STANDARDS-TRACK]",
+    "keywords": [
+      "RPKI",
+      "BGP"
+    ],
+    "area": "rtg",
+    "working_group": "sidr",
+    "stream": "IETF",
+    "authors": [
+      "M. Lepinski",
+      "S. Kent",
+      "D. Kong"
+    ],
+    "doi": "10.17487/RFC6482",
+    "page_count": 9,
+    "obsoleted_by": [
+      "RFC9582"
+    ],
+    "txt_url": "https://www.rfc-editor.org/rfc/rfc6482.txt",
+    "html_url": "https://www.rfc-editor.org/rfc/rfc6482.html"
   },
   "RFC-8205": {
     "number": 8205,
@@ -3404,7 +3447,8 @@
       "STD0080"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc20.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc20.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc20.html",
+    "abstract": "ASCII format for network interchange — IETF RFC 20 (1969-10, Internet Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc20.txt."
   },
   "RFC-35": {
     "number": 35,
@@ -3425,7 +3469,8 @@
     "doi": "10.17487/RFC0035",
     "page_count": 1,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc35.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc35.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc35.html",
+    "abstract": "Network Meeting — IETF RFC 35 (1970-03, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc35.txt."
   },
   "RFC-96": {
     "number": 96,
@@ -3446,7 +3491,8 @@
     "doi": "10.17487/RFC0096",
     "page_count": 5,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc96.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc96.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc96.html",
+    "abstract": "An Interactive Network Experiment to Study Modes of Access the Network Information Center — IETF RFC 96 (1971-02, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc96.txt."
   },
   "RFC-699": {
     "number": 699,
@@ -3468,7 +3514,8 @@
     "doi": "10.17487/RFC0699",
     "page_count": 9,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc699.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc699.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc699.html",
+    "abstract": "Request For Comments summary notes: 600-699 — IETF RFC 699 (1982-11, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc699.txt."
   },
   "RFC-700": {
     "number": 700,
@@ -3491,7 +3538,8 @@
     "doi": "10.17487/RFC0700",
     "page_count": 7,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc700.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc700.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc700.html",
+    "abstract": "Protocol experiment — IETF RFC 700 (1974-08, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc700.txt."
   },
   "RFC-726": {
     "number": 726,
@@ -3516,7 +3564,8 @@
     "doi": "10.17487/RFC0726",
     "page_count": 16,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc726.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc726.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc726.html",
+    "abstract": "Remote Controlled Transmission and Echoing Telnet option — IETF RFC 726 (1977-03, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc726.txt."
   },
   "RFC-727": {
     "number": 727,
@@ -3540,7 +3589,8 @@
     "doi": "10.17487/RFC0727",
     "page_count": 3,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc727.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc727.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc727.html",
+    "abstract": "Telnet logout option — IETF RFC 727 (1977-04, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc727.txt."
   },
   "RFC-735": {
     "number": 735,
@@ -3568,7 +3618,8 @@
       "RFC0729"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc735.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc735.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc735.html",
+    "abstract": "Revised Telnet byte macro option — IETF RFC 735 (1977-11, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc735.txt."
   },
   "RFC-736": {
     "number": 736,
@@ -3592,7 +3643,8 @@
     "doi": "10.17487/RFC0736",
     "page_count": 1,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc736.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc736.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc736.html",
+    "abstract": "Telnet SUPDUP option — IETF RFC 736 (1977-10, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc736.txt."
   },
   "RFC-749": {
     "number": 749,
@@ -3616,7 +3668,8 @@
     "doi": "10.17487/RFC0749",
     "page_count": 4,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc749.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc749.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc749.html",
+    "abstract": "Telnet SUPDUP-Output option — IETF RFC 749 (1978-09, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc749.txt."
   },
   "RFC-768": {
     "number": 768,
@@ -3646,7 +3699,8 @@
       "STD0006"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc768.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc768.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc768.html",
+    "abstract": "User Datagram Protocol — IETF RFC 768 (1980-08, Internet Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc768.txt."
   },
   "RFC-779": {
     "number": 779,
@@ -3670,7 +3724,8 @@
     "doi": "10.17487/RFC0779",
     "page_count": 2,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc779.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc779.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc779.html",
+    "abstract": "Telnet send-location option — IETF RFC 779 (1981-04, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc779.txt."
   },
   "RFC-791": {
     "number": 791,
@@ -3706,7 +3761,8 @@
       "STD0005"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc791.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc791.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc791.html",
+    "abstract": "Internet Protocol — IETF RFC 791 (1981-09, Internet Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc791.txt."
   },
   "RFC-792": {
     "number": 792,
@@ -3742,7 +3798,8 @@
       "STD0005"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc792.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc792.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc792.html",
+    "abstract": "Internet Control Message Protocol — IETF RFC 792 (1981-09, Internet Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc792.txt."
   },
   "RFC-794": {
     "number": 794,
@@ -3766,7 +3823,8 @@
       "IEN125"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc794.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc794.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc794.html",
+    "abstract": "Pre-emption — IETF RFC 794 (1981-09, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc794.txt."
   },
   "RFC-800": {
     "number": 800,
@@ -4524,7 +4582,8 @@
     "doi": "10.17487/RFC0899",
     "page_count": 18,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc899.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc899.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc899.html",
+    "abstract": "Request For Comments summary notes: 800-899 — IETF RFC 899 (1984-05, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc899.txt."
   },
   "RFC-903": {
     "number": 903,
@@ -5649,7 +5708,8 @@
     "doi": "10.17487/RFC1099",
     "page_count": 22,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc1099.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc1099.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc1099.html",
+    "abstract": "Request for Comments Summary: RFC Numbers 1000-1099 — IETF RFC 1099 (1991-12, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc1099.txt."
   },
   "RFC-1107": {
     "number": 1107,
@@ -6865,7 +6925,8 @@
     "doi": "10.17487/RFC1199",
     "page_count": 22,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc1199.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc1199.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc1199.html",
+    "abstract": "Request for Comments Summary Notes: 1100-1199 — IETF RFC 1199 (1991-12, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc1199.txt."
   },
   "RFC-1201": {
     "number": 1201,
@@ -8258,7 +8319,8 @@
     "doi": "10.17487/RFC1299",
     "page_count": 20,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc1299.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc1299.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc1299.html",
+    "abstract": "Summary of 1200-1299 — IETF RFC 1299 (1997-01, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc1299.txt."
   },
   "RFC-1300": {
     "number": 1300,
@@ -9183,7 +9245,8 @@
     "doi": "10.17487/RFC1363",
     "page_count": 20,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc1363.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc1363.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc1363.html",
+    "abstract": "A Proposed Flow Specification — IETF RFC 1363 (1992-09, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc1363.txt."
   },
   "RFC-1365": {
     "number": 1365,
@@ -9207,7 +9270,8 @@
     "doi": "10.17487/RFC1365",
     "page_count": 6,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc1365.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc1365.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc1365.html",
+    "abstract": "An IP Address Extension Proposal — IETF RFC 1365 (1992-09, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc1365.txt."
   },
   "RFC-1369": {
     "number": 1369,
@@ -9604,7 +9668,8 @@
     "doi": "10.17487/RFC1399",
     "page_count": 22,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc1399.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc1399.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc1399.html",
+    "abstract": "Summary of 1300-1399 — IETF RFC 1399 (1997-01, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc1399.txt."
   },
   "RFC-1400": {
     "number": 1400,
@@ -10794,7 +10859,8 @@
     "doi": "10.17487/RFC1499",
     "page_count": 21,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc1499.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc1499.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc1499.html",
+    "abstract": "Summary of 1400-1499 — IETF RFC 1499 (1997-01, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc1499.txt."
   },
   "RFC-1501": {
     "number": 1501,
@@ -12169,7 +12235,8 @@
     "doi": "10.17487/RFC1599",
     "page_count": 22,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc1599.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc1599.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc1599.html",
+    "abstract": "Summary of 1500-1599 — IETF RFC 1599 (1997-01, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc1599.txt."
   },
   "RFC-1605": {
     "number": 1605,
@@ -13939,7 +14006,8 @@
     "doi": "10.17487/RFC1699",
     "page_count": 21,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc1699.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc1699.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc1699.html",
+    "abstract": "Summary of 1600-1699 — IETF RFC 1699 (1997-01, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc1699.txt."
   },
   "RFC-1701": {
     "number": 1701,
@@ -15770,7 +15838,8 @@
     "doi": "10.17487/RFC1799",
     "page_count": 21,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc1799.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc1799.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc1799.html",
+    "abstract": "Request for Comments Summary RFC Numbers 1700-1799 — IETF RFC 1799 (1997-01, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc1799.txt."
   },
   "RFC-1801": {
     "number": 1801,
@@ -16390,7 +16459,8 @@
     "doi": "10.17487/RFC1841",
     "page_count": 66,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc1841.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc1841.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc1841.html",
+    "abstract": "PPP Network Control Protocol for LAN Extension — IETF RFC 1841 (1995-09, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc1841.txt."
   },
   "RFC-1842": {
     "number": 1842,
@@ -16514,7 +16584,8 @@
     "doi": "10.17487/RFC1845",
     "page_count": 7,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc1845.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc1845.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc1845.html",
+    "abstract": "SMTP Service Extension for Checkpoint/Restart — IETF RFC 1845 (1995-09, Experimental). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc1845.txt."
   },
   "RFC-1846": {
     "number": 1846,
@@ -16546,7 +16617,8 @@
       "RFC7504"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc1846.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc1846.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc1846.html",
+    "abstract": "SMTP 521 Reply Code — IETF RFC 1846 (1995-09, Experimental). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc1846.txt."
   },
   "RFC-1847": {
     "number": 1847,
@@ -16606,7 +16678,8 @@
     "doi": "10.17487/RFC1851",
     "page_count": 11,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc1851.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc1851.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc1851.html",
+    "abstract": "The ESP Triple DES Transform — IETF RFC 1851 (1995-09, Experimental). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc1851.txt."
   },
   "RFC-1853": {
     "number": 1853,
@@ -16688,7 +16761,8 @@
     "doi": "10.17487/RFC1856",
     "page_count": 17,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc1856.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc1856.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc1856.html",
+    "abstract": "The Opstat Client-Server Model for Statistics Retrieval — IETF RFC 1856 (1995-09, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc1856.txt."
   },
   "RFC-1857": {
     "number": 1857,
@@ -17363,7 +17437,8 @@
     "doi": "10.17487/RFC1899",
     "page_count": 20,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc1899.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc1899.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc1899.html",
+    "abstract": "Request for Comments Summary RFC Numbers 1800-1899 — IETF RFC 1899 (1997-01, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc1899.txt."
   },
   "RFC-1900": {
     "number": 1900,
@@ -19537,7 +19612,8 @@
     "doi": "10.17487/RFC1999",
     "page_count": 20,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc1999.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc1999.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc1999.html",
+    "abstract": "Request for Comments Summary RFC Numbers 1900-1999 — IETF RFC 1999 (1997-01, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc1999.txt."
   },
   "RFC-2003": {
     "number": 2003,
@@ -21317,7 +21393,8 @@
     "doi": "10.17487/RFC2099",
     "page_count": 21,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc2099.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc2099.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc2099.html",
+    "abstract": "Request for Comments Summary RFC Numbers 2000-2099 — IETF RFC 2099 (1997-03, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc2099.txt."
   },
   "RFC-2100": {
     "number": 2100,
@@ -23743,7 +23820,8 @@
     "doi": "10.17487/RFC2199",
     "page_count": 23,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc2199.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc2199.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc2199.html",
+    "abstract": "Request for Comments Summary RFC Numbers 2100-2199 — IETF RFC 2199 (1998-01, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc2199.txt."
   },
   "RFC-2202": {
     "number": 2202,
@@ -25706,7 +25784,8 @@
     "doi": "10.17487/RFC2299",
     "page_count": 24,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc2299.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc2299.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc2299.html",
+    "abstract": "Request for Comments Summary — IETF RFC 2299 (1999-01, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc2299.txt."
   },
   "RFC-2306": {
     "number": 2306,
@@ -26822,7 +26901,8 @@
       "BCP0021"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc2350.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc2350.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc2350.html",
+    "abstract": "Expectations for Computer Security Incident Response — IETF RFC 2350 (1998-06, Best Current Practice). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc2350.txt."
   },
   "RFC-2351": {
     "number": 2351,
@@ -27976,7 +28056,8 @@
     "doi": "10.17487/RFC2399",
     "page_count": 23,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc2399.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc2399.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc2399.html",
+    "abstract": "Request for Comments Summary — IETF RFC 2399 (1999-01, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc2399.txt."
   },
   "RFC-2403": {
     "number": 2403,
@@ -29780,7 +29861,8 @@
     "doi": "10.17487/RFC2499",
     "page_count": 22,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc2499.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc2499.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc2499.html",
+    "abstract": "Request for Comments Summary — IETF RFC 2499 (1999-07, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc2499.txt."
   },
   "RFC-2501": {
     "number": 2501,
@@ -31877,7 +31959,8 @@
     "doi": "10.17487/RFC2599",
     "page_count": 23,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc2599.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc2599.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc2599.html",
+    "abstract": "Request for Comments Summary RFC Numbers 2500-2599 — IETF RFC 2599 (2000-03, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc2599.txt."
   },
   "RFC-2601": {
     "number": 2601,
@@ -34175,7 +34258,8 @@
     "doi": "10.17487/RFC2699",
     "page_count": 22,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc2699.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc2699.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc2699.html",
+    "abstract": "Request for Comments Summary RFC Numbers 2600-2699 — IETF RFC 2699 (2000-05, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc2699.txt."
   },
   "RFC-2701": {
     "number": 2701,
@@ -36563,7 +36647,8 @@
     "doi": "10.17487/RFC2799",
     "page_count": 23,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc2799.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc2799.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc2799.html",
+    "abstract": "Request for Comments Summary RFC Numbers 2700-2799 — IETF RFC 2799 (2000-09, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc2799.txt."
   },
   "RFC-2801": {
     "number": 2801,
@@ -38881,7 +38966,8 @@
     "doi": "10.17487/RFC2899",
     "page_count": 22,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc2899.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc2899.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc2899.html",
+    "abstract": "Request for Comments Summary RFC Numbers 2800-2899 — IETF RFC 2899 (2001-05, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc2899.txt."
   },
   "RFC-2901": {
     "number": 2901,
@@ -41535,7 +41621,8 @@
     "doi": "10.17487/RFC2999",
     "page_count": 23,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc2999.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc2999.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc2999.html",
+    "abstract": "Request for Comments Summary RFC Numbers 2900-2999 — IETF RFC 2999 (2001-08, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc2999.txt."
   },
   "RFC-3002": {
     "number": 3002,
@@ -43887,7 +43974,8 @@
     "doi": "10.17487/RFC3099",
     "page_count": 25,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3099.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3099.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3099.html",
+    "abstract": "Request for Comments Summary RFC Numbers 3000-3099 — IETF RFC 3099 (2001-11, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3099.txt."
   },
   "RFC-3101": {
     "number": 3101,
@@ -46675,7 +46763,8 @@
     "doi": "10.17487/RFC3199",
     "page_count": 24,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3199.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3199.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3199.html",
+    "abstract": "Request for Comments Summary RFC Numbers 3100-3199 — IETF RFC 3199 (2003-02, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3199.txt."
   },
   "RFC-3201": {
     "number": 3201,
@@ -49339,7 +49428,8 @@
     "doi": "10.17487/RFC3299",
     "page_count": 30,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3299.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3299.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3299.html",
+    "abstract": "Request for Comments Summary RFC Numbers 3200-3299 — IETF RFC 3299 (2003-12, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3299.txt."
   },
   "RFC-3301": {
     "number": 3301,
@@ -49368,7 +49458,8 @@
     "doi": "10.17487/RFC3301",
     "page_count": 19,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3301.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3301.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3301.html",
+    "abstract": "Layer Two Tunnelling Protocol (L2TP): ATM access network extensions — IETF RFC 3301 (2002-06, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3301.txt."
   },
   "RFC-3302": {
     "number": 3302,
@@ -49401,7 +49492,8 @@
       "RFC2302"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3302.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3302.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3302.html",
+    "abstract": "Tag Image File Format (TIFF) - image/tiff MIME Sub-type Registration — IETF RFC 3302 (2002-09, Draft Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3302.txt."
   },
   "RFC-3303": {
     "number": 3303,
@@ -49431,7 +49523,8 @@
     "doi": "10.17487/RFC3303",
     "page_count": 34,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3303.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3303.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3303.html",
+    "abstract": "Middlebox communication architecture and framework — IETF RFC 3303 (2002-08, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3303.txt."
   },
   "RFC-3304": {
     "number": 3304,
@@ -49463,7 +49556,8 @@
     "doi": "10.17487/RFC3304",
     "page_count": 9,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3304.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3304.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3304.html",
+    "abstract": "Middlebox Communications (midcom) Protocol Requirements — IETF RFC 3304 (2002-08, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3304.txt."
   },
   "RFC-3305": {
     "number": 3305,
@@ -49488,7 +49582,8 @@
     "doi": "10.17487/RFC3305",
     "page_count": 11,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3305.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3305.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3305.html",
+    "abstract": "Report from the Joint W3C/IETF URI Planning Interest Group: Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and Recommendations — IETF RFC 3305 (2002-08, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3305.txt."
   },
   "RFC-3306": {
     "number": 3306,
@@ -49522,7 +49617,8 @@
       "RFC7371"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3306.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3306.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3306.html",
+    "abstract": "Unicast-Prefix-based IPv6 Multicast Addresses — IETF RFC 3306 (2002-08, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3306.txt."
   },
   "RFC-3307": {
     "number": 3307,
@@ -49550,7 +49646,8 @@
     "doi": "10.17487/RFC3307",
     "page_count": 8,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3307.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3307.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3307.html",
+    "abstract": "Allocation Guidelines for IPv6 Multicast Addresses — IETF RFC 3307 (2002-08, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3307.txt."
   },
   "RFC-3308": {
     "number": 3308,
@@ -49584,7 +49681,8 @@
     "doi": "10.17487/RFC3308",
     "page_count": 10,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3308.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3308.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3308.html",
+    "abstract": "Layer Two Tunneling Protocol (L2TP) Differentiated Services Extension — IETF RFC 3308 (2002-11, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3308.txt."
   },
   "RFC-3310": {
     "number": 3310,
@@ -49614,7 +49712,8 @@
     "doi": "10.17487/RFC3310",
     "page_count": 18,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3310.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3310.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3310.html",
+    "abstract": "Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA) — IETF RFC 3310 (2002-09, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3310.txt."
   },
   "RFC-3311": {
     "number": 3311,
@@ -49643,7 +49742,8 @@
     "doi": "10.17487/RFC3311",
     "page_count": 13,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3311.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3311.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3311.html",
+    "abstract": "The Session Initiation Protocol (SIP) UPDATE Method — IETF RFC 3311 (2002-10, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3311.txt."
   },
   "RFC-3312": {
     "number": 3312,
@@ -49679,7 +49779,8 @@
       "RFC5027"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3312.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3312.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3312.html",
+    "abstract": "Integration of Resource Management and Session Initiation Protocol (SIP) — IETF RFC 3312 (2002-10, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3312.txt."
   },
   "RFC-3313": {
     "number": 3313,
@@ -49706,7 +49807,8 @@
     "doi": "10.17487/RFC3313",
     "page_count": 16,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3313.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3313.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3313.html",
+    "abstract": "Private Session Initiation Protocol (SIP) Extensions for Media Authorization — IETF RFC 3313 (2003-01, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3313.txt."
   },
   "RFC-3314": {
     "number": 3314,
@@ -49732,7 +49834,8 @@
     "doi": "10.17487/RFC3314",
     "page_count": 23,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3314.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3314.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3314.html",
+    "abstract": "Recommendations for IPv6 in Third Generation Partnership Project (3GPP) Standards — IETF RFC 3314 (2002-09, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3314.txt."
   },
   "RFC-3319": {
     "number": 3319,
@@ -49763,7 +49866,8 @@
     "doi": "10.17487/RFC3319",
     "page_count": 7,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3319.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3319.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3319.html",
+    "abstract": "Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers — IETF RFC 3319 (2003-07, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3319.txt."
   },
   "RFC-3320": {
     "number": 3320,
@@ -49802,7 +49906,8 @@
       "RFC4896"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3320.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3320.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3320.html",
+    "abstract": "Signaling Compression (SigComp) — IETF RFC 3320 (2003-01, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3320.txt."
   },
   "RFC-3321": {
     "number": 3321,
@@ -49841,7 +49946,8 @@
       "RFC4896"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3321.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3321.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3321.html",
+    "abstract": "Signaling Compression (SigComp) - Extended Operations — IETF RFC 3321 (2003-01, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3321.txt."
   },
   "RFC-3322": {
     "number": 3322,
@@ -49874,7 +49980,8 @@
     "doi": "10.17487/RFC3322",
     "page_count": 13,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3322.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3322.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3322.html",
+    "abstract": "Signaling Compression (SigComp) Requirements & Assumptions — IETF RFC 3322 (2003-01, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3322.txt."
   },
   "RFC-3323": {
     "number": 3323,
@@ -49902,7 +50009,8 @@
     "doi": "10.17487/RFC3323",
     "page_count": 22,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3323.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3323.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3323.html",
+    "abstract": "A Privacy Mechanism for the Session Initiation Protocol (SIP) — IETF RFC 3323 (2002-11, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3323.txt."
   },
   "RFC-3324": {
     "number": 3324,
@@ -49931,7 +50039,8 @@
     "doi": "10.17487/RFC3324",
     "page_count": 11,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3324.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3324.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3324.html",
+    "abstract": "Short Term Requirements for Network Asserted Identity — IETF RFC 3324 (2002-11, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3324.txt."
   },
   "RFC-3325": {
     "number": 3325,
@@ -49963,7 +50072,8 @@
       "RFC8217"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3325.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3325.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3325.html",
+    "abstract": "Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks — IETF RFC 3325 (2002-11, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3325.txt."
   },
   "RFC-3326": {
     "number": 3326,
@@ -50037,7 +50147,8 @@
       "RFC5626"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3327.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3327.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3327.html",
+    "abstract": "Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts — IETF RFC 3327 (2002-12, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3327.txt."
   },
   "RFC-3329": {
     "number": 3329,
@@ -50073,7 +50184,8 @@
       "RFC8996"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3329.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3329.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3329.html",
+    "abstract": "Security Mechanism Agreement for the Session Initiation Protocol (SIP) — IETF RFC 3329 (2003-01, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3329.txt."
   },
   "RFC-3331": {
     "number": 3331,
@@ -50108,7 +50220,8 @@
     "doi": "10.17487/RFC3331",
     "page_count": 94,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3331.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3331.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3331.html",
+    "abstract": "Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Adaptation Layer — IETF RFC 3331 (2002-09, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3331.txt."
   },
   "RFC-3334": {
     "number": 3334,
@@ -50140,7 +50253,8 @@
     "doi": "10.17487/RFC3334",
     "page_count": 44,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3334.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3334.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3334.html",
+    "abstract": "Policy-Based Accounting — IETF RFC 3334 (2002-10, Experimental). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3334.txt."
   },
   "RFC-3335": {
     "number": 3335,
@@ -50171,7 +50285,8 @@
     "doi": "10.17487/RFC3335",
     "page_count": 29,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3335.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3335.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3335.html",
+    "abstract": "MIME-based Secure Peer-to-Peer Business Data Interchange over the Internet — IETF RFC 3335 (2002-09, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3335.txt."
   },
   "RFC-3336": {
     "number": 3336,
@@ -50206,7 +50321,8 @@
     "doi": "10.17487/RFC3336",
     "page_count": 16,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3336.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3336.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3336.html",
+    "abstract": "PPP Over Asynchronous Transfer Mode Adaptation Layer 2 (AAL2) — IETF RFC 3336 (2002-12, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3336.txt."
   },
   "RFC-3337": {
     "number": 3337,
@@ -50239,7 +50355,8 @@
     "doi": "10.17487/RFC3337",
     "page_count": 7,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3337.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3337.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3337.html",
+    "abstract": "Class Extensions for PPP over Asynchronous Transfer Mode Adaptation Layer 2 — IETF RFC 3337 (2002-12, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3337.txt."
   },
   "RFC-3339": {
     "number": 3339,
@@ -50303,7 +50420,8 @@
     "doi": "10.17487/RFC3345",
     "page_count": 19,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3345.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3345.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3345.html",
+    "abstract": "Border Gateway Protocol (BGP) Persistent Route Oscillation Condition — IETF RFC 3345 (2002-08, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3345.txt."
   },
   "RFC-3346": {
     "number": 3346,
@@ -50336,7 +50454,8 @@
     "doi": "10.17487/RFC3346",
     "page_count": 14,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3346.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3346.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3346.html",
+    "abstract": "Applicability Statement for Traffic Engineering with MPLS — IETF RFC 3346 (2002-08, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3346.txt."
   },
   "RFC-3347": {
     "number": 3347,
@@ -50368,7 +50487,8 @@
     "doi": "10.17487/RFC3347",
     "page_count": 26,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3347.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3347.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3347.html",
+    "abstract": "Small Computer Systems Interface protocol over the Internet (iSCSI) Requirements and Design Considerations — IETF RFC 3347 (2002-07, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3347.txt."
   },
   "RFC-3348": {
     "number": 3348,
@@ -50394,7 +50514,8 @@
     "doi": "10.17487/RFC3348",
     "page_count": 6,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3348.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3348.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3348.html",
+    "abstract": "The Internet Message Action Protocol (IMAP4) Child Mailbox Extension — IETF RFC 3348 (2002-07, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3348.txt."
   },
   "RFC-3349": {
     "number": 3349,
@@ -50422,7 +50543,8 @@
       "BCP0059"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3349.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3349.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3349.html",
+    "abstract": "A Transient Prefix for Identifying Profiles under Development by the Working Groups of the Internet Engineering Task Force — IETF RFC 3349 (2002-07, Best Current Practice). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3349.txt."
   },
   "RFC-3351": {
     "number": 3351,
@@ -50454,7 +50576,8 @@
     "doi": "10.17487/RFC3351",
     "page_count": 17,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3351.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3351.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3351.html",
+    "abstract": "User Requirements for the Session Initiation Protocol (SIP) in Support of Deaf, Hard of Hearing and Speech-impaired Individuals — IETF RFC 3351 (2002-08, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3351.txt."
   },
   "RFC-3352": {
     "number": 3352,
@@ -50487,7 +50610,8 @@
       "RFC1798"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3352.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3352.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3352.html",
+    "abstract": "Connection-less Lightweight Directory Access Protocol (CLDAP) to Historic Status — IETF RFC 3352 (2003-03, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3352.txt."
   },
   "RFC-3353": {
     "number": 3353,
@@ -50520,7 +50644,8 @@
     "doi": "10.17487/RFC3353",
     "page_count": 30,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3353.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3353.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3353.html",
+    "abstract": "Overview of IP Multicast in a Multi-Protocol Label Switching (MPLS) Environment — IETF RFC 3353 (2002-08, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3353.txt."
   },
   "RFC-3354": {
     "number": 3354,
@@ -50554,7 +50679,8 @@
     "doi": "10.17487/RFC3354",
     "page_count": 6,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3354.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3354.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3354.html",
+    "abstract": "Internet Open Trading Protocol Version 2 Requirements — IETF RFC 3354 (2002-08, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3354.txt."
   },
   "RFC-3355": {
     "number": 3355,
@@ -50589,7 +50715,8 @@
     "doi": "10.17487/RFC3355",
     "page_count": 13,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3355.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3355.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3355.html",
+    "abstract": "Layer Two Tunnelling Protocol (L2TP) Over ATM Adaptation Layer 5 (AAL5) — IETF RFC 3355 (2002-08, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3355.txt."
   },
   "RFC-3357": {
     "number": 3357,
@@ -50619,7 +50746,8 @@
     "doi": "10.17487/RFC3357",
     "page_count": 15,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3357.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3357.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3357.html",
+    "abstract": "One-way Loss Pattern Sample Metrics — IETF RFC 3357 (2002-08, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3357.txt."
   },
   "RFC-3358": {
     "number": 3358,
@@ -50649,7 +50777,8 @@
     "doi": "10.17487/RFC3358",
     "page_count": 4,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3358.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3358.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3358.html",
+    "abstract": "Optional Checksums in Intermediate System to Intermediate System (ISIS) — IETF RFC 3358 (2002-08, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3358.txt."
   },
   "RFC-3359": {
     "number": 3359,
@@ -50679,7 +50808,8 @@
     "doi": "10.17487/RFC3359",
     "page_count": 5,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3359.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3359.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3359.html",
+    "abstract": "Reserved Type, Length and Value (TLV) Codepoints in Intermediate System to Intermediate System — IETF RFC 3359 (2002-08, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3359.txt."
   },
   "RFC-3360": {
     "number": 3360,
@@ -50709,7 +50839,8 @@
       "BCP0060"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3360.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3360.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3360.html",
+    "abstract": "Inappropriate TCP Resets Considered Harmful — IETF RFC 3360 (2002-08, Best Current Practice). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3360.txt."
   },
   "RFC-3361": {
     "number": 3361,
@@ -50739,7 +50870,8 @@
     "doi": "10.17487/RFC3361",
     "page_count": 7,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3361.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3361.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3361.html",
+    "abstract": "Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers — IETF RFC 3361 (2002-08, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3361.txt."
   },
   "RFC-3362": {
     "number": 3362,
@@ -50767,7 +50899,8 @@
     "doi": "10.17487/RFC3362",
     "page_count": 5,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3362.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3362.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3362.html",
+    "abstract": "Real-time Facsimile (T.38) - image/t38 MIME Sub-type Registration — IETF RFC 3362 (2002-08, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3362.txt."
   },
   "RFC-3363": {
     "number": 3363,
@@ -50805,7 +50938,8 @@
       "RFC6672"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3363.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3363.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3363.html",
+    "abstract": "Representing Internet Protocol version 6 (IPv6) Addresses in the Domain Name System (DNS) — IETF RFC 3363 (2002-08, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3363.txt."
   },
   "RFC-3364": {
     "number": 3364,
@@ -50837,7 +50971,8 @@
       "RFC2874"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3364.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3364.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3364.html",
+    "abstract": "Tradeoffs in Domain Name System (DNS) Support for Internet Protocol version 6 (IPv6) — IETF RFC 3364 (2002-08, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3364.txt."
   },
   "RFC-3365": {
     "number": 3365,
@@ -50864,7 +50999,8 @@
       "BCP0061"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3365.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3365.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3365.html",
+    "abstract": "Strong Security Requirements for Internet Engineering Task Force Standard Protocols — IETF RFC 3365 (2002-08, Best Current Practice). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3365.txt."
   },
   "RFC-3366": {
     "number": 3366,
@@ -50895,7 +51031,8 @@
       "BCP0062"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3366.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3366.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3366.html",
+    "abstract": "Advice to link designers on link Automatic Repeat reQuest (ARQ) — IETF RFC 3366 (2002-08, Best Current Practice). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3366.txt."
   },
   "RFC-3367": {
     "number": 3367,
@@ -50924,7 +51061,8 @@
     "doi": "10.17487/RFC3367",
     "page_count": 42,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3367.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3367.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3367.html",
+    "abstract": "Common Name Resolution Protocol (CNRP) — IETF RFC 3367 (2002-08, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3367.txt."
   },
   "RFC-3368": {
     "number": 3368,
@@ -50951,7 +51089,8 @@
     "doi": "10.17487/RFC3368",
     "page_count": 8,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3368.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3368.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3368.html",
+    "abstract": "The 'go' URI Scheme for the Common Name Resolution Protocol — IETF RFC 3368 (2002-08, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3368.txt."
   },
   "RFC-3370": {
     "number": 3370,
@@ -50991,7 +51130,8 @@
       "RFC8702"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3370.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3370.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3370.html",
+    "abstract": "Cryptographic Message Syntax (CMS) Algorithms — IETF RFC 3370 (2002-08, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3370.txt."
   },
   "RFC-3371": {
     "number": 3371,
@@ -51022,7 +51162,8 @@
     "doi": "10.17487/RFC3371",
     "page_count": 70,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3371.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3371.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3371.html",
+    "abstract": "Layer Two Tunneling Protocol \"L2TP\" Management Information Base — IETF RFC 3371 (2002-08, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3371.txt."
   },
   "RFC-3372": {
     "number": 3372,
@@ -51053,7 +51194,8 @@
       "BCP0063"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3372.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3372.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3372.html",
+    "abstract": "Session Initiation Protocol for Telephones (SIP-T): Context and Architectures — IETF RFC 3372 (2002-09, Best Current Practice). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3372.txt."
   },
   "RFC-3374": {
     "number": 3374,
@@ -51083,7 +51225,8 @@
     "doi": "10.17487/RFC3374",
     "page_count": 14,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3374.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3374.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3374.html",
+    "abstract": "Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access Network — IETF RFC 3374 (2002-09, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3374.txt."
   },
   "RFC-3375": {
     "number": 3375,
@@ -51111,7 +51254,8 @@
     "doi": "10.17487/RFC3375",
     "page_count": 21,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3375.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3375.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3375.html",
+    "abstract": "Generic Registry-Registrar Protocol Requirements — IETF RFC 3375 (2002-09, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3375.txt."
   },
   "RFC-3378": {
     "number": 3378,
@@ -51137,7 +51281,8 @@
     "doi": "10.17487/RFC3378",
     "page_count": 9,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3378.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3378.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3378.html",
+    "abstract": "EtherIP: Tunneling Ethernet Frames in IP Datagrams — IETF RFC 3378 (2002-09, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3378.txt."
   },
   "RFC-3379": {
     "number": 3379,
@@ -51169,7 +51314,8 @@
     "doi": "10.17487/RFC3379",
     "page_count": 15,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3379.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3379.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3379.html",
+    "abstract": "Delegated Path Validation and Delegated Path Discovery Protocol Requirements — IETF RFC 3379 (2002-09, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3379.txt."
   },
   "RFC-3380": {
     "number": 3380,
@@ -51205,7 +51351,8 @@
       "RFC2911"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3380.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3380.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3380.html",
+    "abstract": "Internet Printing Protocol (IPP): Job and Printer Set Operations — IETF RFC 3380 (2002-09, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3380.txt."
   },
   "RFC-3384": {
     "number": 3384,
@@ -51237,7 +51384,8 @@
     "doi": "10.17487/RFC3384",
     "page_count": 31,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3384.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3384.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3384.html",
+    "abstract": "Lightweight Directory Access Protocol (version 3) Replication Requirements — IETF RFC 3384 (2002-10, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3384.txt."
   },
   "RFC-3385": {
     "number": 3385,
@@ -51264,7 +51412,8 @@
     "doi": "10.17487/RFC3385",
     "page_count": 23,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3385.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3385.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3385.html",
+    "abstract": "Internet Protocol Small Computer System Interface (iSCSI) Cyclic Redundancy Check (CRC)/Checksum Considerations — IETF RFC 3385 (2002-09, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3385.txt."
   },
   "RFC-3386": {
     "number": 3386,
@@ -51296,7 +51445,8 @@
     "doi": "10.17487/RFC3386",
     "page_count": 27,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3386.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3386.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3386.html",
+    "abstract": "Network Hierarchy and Multilayer Survivability — IETF RFC 3386 (2002-11, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3386.txt."
   },
   "RFC-3387": {
     "number": 3387,
@@ -51324,7 +51474,8 @@
     "doi": "10.17487/RFC3387",
     "page_count": 19,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3387.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3387.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3387.html",
+    "abstract": "Considerations from the Service Management Research Group (SMRG) on Quality of Service (QoS) in the IP Network — IETF RFC 3387 (2002-09, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3387.txt."
   },
   "RFC-3389": {
     "number": 3389,
@@ -51356,7 +51507,8 @@
     "doi": "10.17487/RFC3389",
     "page_count": 8,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3389.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3389.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3389.html",
+    "abstract": "Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN) — IETF RFC 3389 (2002-09, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3389.txt."
   },
   "RFC-3390": {
     "number": 3390,
@@ -51391,7 +51543,8 @@
       "RFC2581"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3390.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3390.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3390.html",
+    "abstract": "Increasing TCP's Initial Window — IETF RFC 3390 (2002-10, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3390.txt."
   },
   "RFC-3391": {
     "number": 3391,
@@ -51416,7 +51569,8 @@
     "doi": "10.17487/RFC3391",
     "page_count": 25,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3391.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3391.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3391.html",
+    "abstract": "The MIME Application/Vnd.pwg-multiplexed Content-Type — IETF RFC 3391 (2002-12, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3391.txt."
   },
   "RFC-3393": {
     "number": 3393,
@@ -51447,7 +51601,8 @@
     "doi": "10.17487/RFC3393",
     "page_count": 21,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3393.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3393.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3393.html",
+    "abstract": "IP Packet Delay Variation Metric for IP Performance Metrics (IPPM) — IETF RFC 3393 (2002-11, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3393.txt."
   },
   "RFC-3394": {
     "number": 3394,
@@ -51474,7 +51629,8 @@
     "doi": "10.17487/RFC3394",
     "page_count": 41,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3394.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3394.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3394.html",
+    "abstract": "Advanced Encryption Standard (AES) Key Wrap Algorithm — IETF RFC 3394 (2002-09, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3394.txt."
   },
   "RFC-3395": {
     "number": 3395,
@@ -51508,7 +51664,8 @@
       "RFC2895"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3395.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3395.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3395.html",
+    "abstract": "Remote Network Monitoring MIB Protocol Identifier Reference Extensions — IETF RFC 3395 (2002-09, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3395.txt."
   },
   "RFC-3396": {
     "number": 3396,
@@ -51542,7 +51699,8 @@
       "RFC2131"
     ],
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3396.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3396.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3396.html",
+    "abstract": "Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4) — IETF RFC 3396 (2002-11, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3396.txt."
   },
   "RFC-3397": {
     "number": 3397,
@@ -51573,7 +51731,8 @@
     "doi": "10.17487/RFC3397",
     "page_count": 8,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3397.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3397.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3397.html",
+    "abstract": "Dynamic Host Configuration Protocol (DHCP) Domain Search Option — IETF RFC 3397 (2002-11, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3397.txt."
   },
   "RFC-3398": {
     "number": 3398,
@@ -51611,7 +51770,8 @@
     "doi": "10.17487/RFC3398",
     "page_count": 68,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3398.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3398.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3398.html",
+    "abstract": "Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping — IETF RFC 3398 (2002-12, Proposed Standard). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3398.txt."
   },
   "RFC-3401": {
     "number": 3401,
@@ -54379,7 +54539,8 @@
     "doi": "10.17487/RFC3499",
     "page_count": 38,
     "txt_url": "https://www.rfc-editor.org/rfc/rfc3499.txt",
-    "html_url": "https://www.rfc-editor.org/rfc/rfc3499.html"
+    "html_url": "https://www.rfc-editor.org/rfc/rfc3499.html",
+    "abstract": "Request for Comments Summary RFC Numbers 3400-3499 — IETF RFC 3499 (2003-12, Informational). The IETF index does not carry an abstract for this RFC (pre-1999 publication). Full text at https://www.rfc-editor.org/rfc/rfc3499.txt."
   },
   "RFC-3502": {
     "number": 3502,