RFC Implementation Status
This page is Ze's public RFC proof ledger. It lists the RFCs Ze implements, in part or in full, and for each one how much of what the RFC requires is proven. It reports proof only: whether an operator can use a capability is a property of the feature that carries it (features/<id>.md, its Scope), not of the RFC.
Every row below is declared by the RFC's own summary, in the ## Meta table of rfc/short/<stem>.md. A row belongs here only when current docs, source code, tests, or learned closure notes tie the RFC to a Ze feature, and a summary that ties to none writes | Support | - | instead.
The per-requirement detail behind each row is published at /quality/rfc-compliance/<stem>/, one page for every summary under rfc/short/, naming each requirement, the tests bound to it, the audit verdict a reader recorded, and every gap and untested MUST under its own requirement id. The 24 of 242 summaries (9.9%) with no row on this page are published there too, and the index at /quality/rfc-compliance/ links all of them.
Area is the one cell an author writes, a classification. Every other cell is derived, and no author can change it:
- Proof is
N of M MUST proven: of the M MUST-level requirements the summary gates, the N whose tests a recorded break still verifies (rfc/discrimination/<stem>.json), counting a requirement a layer under Ze performs once its recorded break proves the state Ze installs for that layer (OS verified). A tag with no verifying record, and a record that escapes the break (no-break,kernel-producer), prove nothing here. An RFC whose requirement list has not been walked against the RFC's own text (no validrfc/extraction/<stem>.json) readsnot walkedand publishes no number, because its list bounds nothing. A walked RFC gating no MUST-level requirement readsno MUST rows. - Evidence counts the rows Ze's tests prove by the strongest kind of test behind each (
interop, thenfunctional,editor,unit), and the OS verified rows asos, so the counts sum to N. - Unmet lists the requirement ids the summary annotates
{gap},{partial}or{linux-limit}, and those an audit judged not met, at every level.
A brief table (Internet-Drafts and other standards) carries Area, Proof and Unmet and leaves Evidence out, so an unmet requirement of a draft is still named by its id.
How strong the proof behind a row is. Every requirement's evidence is listed in that RFC's own file under rfc/requirements/, with a kind/tier cell per test link. kind is the layer the test exercises (unit, functional, editor, interop); tier is whether anything executes it. verify means it runs in ./le verify current on every push. interop/nightly runs only in the scheduled, advisory evidence-nightly workflow -- so a requirement whose evidence is entirely nightly-tier is marked **nightly-only** on its row there, and counted in its own column of the coverage rollup in ai/RFC-REQUIREMENTS.md. A tag in a suite no pipeline runs is refused outright rather than published with a caveat.
./le rfc check refuses an enrolled RFC that carries an unmet requirement and renders no row here, and a row that disappears while its summary remains.
Bidirectional Forwarding Detection
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 5880 | BFD base | 72 of 111 MUST proven | unit 72 | RFC5880-6.6-2, RFC5880-6.6-3, RFC5880-6.8.1-11, RFC5880-6.8.1-13, RFC5880-6.8.15-1, RFC5880-6.8.17-1, RFC5880-6.8.6-14, RFC5880-6.8.7-6, RFC5880-6.8.7-7, RFC5880-6.8.7-8, RFC5880-7-1, RFC5880-7-2 |
| RFC 5881 | BFD single-hop | 13 of 23 MUST proven | unit 13 | RFC5881-2-1, RFC5881-2-3, RFC5881-2-4, RFC5881-4-2, RFC5881-4-6, RFC5881-4-7, RFC5881-6-3, RFC5881-6-4 |
| RFC 5882 | BFD generic application | 0 of 3 MUST proven | - | RFC5882-10.1.3-1, RFC5882-4.1-1, RFC5882-4.4-1 |
| RFC 5883 | BFD multi-hop | 3 of 6 MUST proven | unit 3 | - |
| RFC 9384 | BFD-triggered BGP Cease | ✕ | - | - |
BGP communities, route leak prevention, and policy signalling
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 5635 | RTBH filtering with uRPF | ✕ | - | - |
| RFC 1997 | Standard communities | 5 of 5 MUST proven | interop 1, functional 2, unit 2 | - |
| RFC 3765 | NOPEER community | ✕ | - | - |
| RFC 4360 | Extended communities | 2 of 5 MUST proven | unit 2 | RFC4360-6-1, RFC4360-7-1, RFC4360-7-2 |
| RFC 5701 | IPv6 extended communities | 0 of 4 MUST proven | - | RFC5701-4-1 |
| RFC 7611 | ACCEPT_OWN community | 2 of 5 MUST proven | unit 2 | RFC7611-2.3-1, RFC7611-3-1 |
| RFC 7999 | BLACKHOLE community | 4 of 4 MUST proven | interop 2, unit 2 | - |
| RFC 8092 | Large communities | 7 of 7 MUST proven | functional 1, unit 6 | - |
| RFC 9234 | BGP Role and OTC | 12 of 19 MUST proven | interop 1, functional 5, unit 6 | RFC9234-5-7, RFC9234-5-8, RFC9234-6-1 |
BGP base protocol, capabilities, attributes, and error handling
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 4271 | BGP-4 base protocol | 85 of 133 MUST proven | interop 4, functional 6, unit 75 | RFC4271-3.1-2, RFC4271-5.1.6-1, RFC4271-5.1.7-1, RFC4271-6.2-3, RFC4271-8.2.1-3, RFC4271-8.2.2-13, RFC4271-9.1.2-1, RFC4271-9.1.2-4, RFC4271-9.1.2.1-2, RFC4271-9.1.2.2-2, RFC4271-9.2-2, RFC4271-9.2-3, RFC4271-9.2.1.1-2, RFC4271-9.2.1.1-3, RFC4271-9.2.2.2-1, RFC4271-9.2.2.2-2, RFC4271-9.2.2.2-3, RFC4271-9.2.2.2-4, RFC4271-9.2.2.2-5 |
| RFC 2545 | IPv6 next-hop handling | 3 of 5 MUST proven | interop 1, functional 2 | RFC2545-3-3, RFC2545-3-6 |
| RFC 5492 | BGP capability advertisement | 8 of 9 MUST proven | unit 8 | RFC5492-4-3 |
| RFC 6608 | BGP FSM Error subcodes | 0 of 3 MUST proven | - | RFC6608-4-1, RFC6608-4-2, RFC6608-4-3 |
| RFC 8212 | EBGP default reject without policy | 2 of 2 MUST proven | interop 1, functional 1 | - |
| RFC 9072 | Extended Optional Parameters Length for BGP OPEN | 5 of 9 MUST proven | unit 5 | RFC9072-2-5, RFC9072-2-6, RFC9072-3-1, RFC9072-3-3 |
| RFC 9687 | Send Hold Timer | 4 of 13 MUST proven | unit 4 | - |
| RFC 4760 | Multiprotocol BGP | 6 of 6 MUST proven | unit 6 | - |
| RFC 2918 | Route Refresh | 3 of 6 MUST proven | functional 1, unit 2 | - |
| RFC 4486 | BGP Cease subcodes and prefix maximum | 0 of 1 MUST proven | - | - |
| RFC 6793 | 4-byte AS numbers | 21 of 30 MUST proven | functional 2, unit 19 | RFC6793-4.1-3 |
| RFC 7311 | AIGP attribute | 13 of 22 MUST proven | unit 13 | - |
| RFC 7911 | ADD-PATH | 9 of 9 MUST proven | interop 1, functional 1, unit 7 | - |
| RFC 6286 | AS-wide unique BGP Identifier | 0 of 4 MUST proven | - | RFC6286-2.1-1 |
| RFC 7606 | Revised UPDATE error handling | 28 of 53 MUST proven | interop 2, functional 4, unit 22 | RFC7606-8-1 |
| RFC 8950 | Extended Next Hop | 3 of 6 MUST proven | unit 3 | - |
| RFC 5549 | Legacy extended next-hop encoding | 3 of 6 MUST proven | unit 3 | - |
| RFC 7313 | Enhanced Route Refresh | 5 of 11 MUST proven | unit 5 | RFC7313-4-13, RFC7313-4-4, RFC7313-4-5, RFC7313-4-6, RFC7313-4-7 |
| RFC 7607 | Codification of AS 0 processing | 0 of 5 MUST proven | - | - |
| RFC 8654 | BGP Extended Message | 9 of 12 MUST proven | interop 2, unit 7 | RFC8654-5-3 |
| RFC 9774 | Deprecation of AS_SET and AS_CONFED_SET | 2 of 3 MUST proven | unit 2 | RFC9774-5.2-1 |
BGP Flow Specification
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 8955 | IPv4 FlowSpec | 13 of 29 MUST proven | unit 13 | RFC8955-12-2, RFC8955-4-3 |
| RFC 5575 | BGP Flowspec (obsoleted by RFC 8955) | 2 of 9 MUST proven | unit 2 | RFC5575-6-1 |
| RFC 8956 | IPv6 FlowSpec | 7 of 9 MUST proven | unit 7 | - |
| RFC 9117 | FlowSpec validation | 2 of 2 MUST proven | unit 2 | - |
BGP Link-State distribution
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 9552 | BGP-LS (obsoletes RFC 7752) | 44 of 59 MUST proven | functional 1, unit 43 | RFC9552-5.1-7, RFC9552-5.2-5, RFC9552-5.3-1, RFC9552-5.3-2, RFC9552-5.3.2.7-1, RFC9552-5.4-2, RFC9552-8.2.6-2 |
| RFC 7752 | BGP-LS | 8 of 26 MUST proven | unit 8 | RFC7752-3.2-2, RFC7752-3.2-3, RFC7752-3.2.1-1, RFC7752-3.2.1.1-1, RFC7752-3.2.1.1-2, RFC7752-3.2.1.4-1, RFC7752-3.2.1.4-2, RFC7752-3.2.1.5-1, RFC7752-3.3-1, RFC7752-3.3.2.1-1, RFC7752-3.3.2.2-1, RFC7752-3.3.2.7-1, RFC7752-3.3.3-1, RFC7752-6.2.2-1, RFC7752-6.2.6-1, RFC7752-8-1 |
| RFC 9085 | BGP-LS Segment Routing extensions | 9 of 9 MUST proven | unit 9 | - |
| RFC 9086 | BGP-LS Egress Peer Engineering SIDs | 7 of 11 MUST proven | unit 7 | RFC9086-5-2, RFC9086-5.2-1, RFC9086-7-1, RFC9086-7-2 |
| RFC 9514 | BGP-LS SRv6 extensions | 15 of 20 MUST proven | unit 15 | RFC9514-7.2-1, RFC9514-7.2-2, RFC9514-7.2-3, RFC9514-7.2-5, RFC9514-7.2-6 |
BGP Monitoring Protocol (BMP)
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 8522 | Looking Glass command set API | 0 of 18 MUST proven | - | RFC8522-2-1, RFC8522-2-2, RFC8522-2-3, RFC8522-2.2-1, RFC8522-2.3-1, RFC8522-2.3-2, RFC8522-2.3.1-1, RFC8522-2.3.1-2, RFC8522-2.3.1-3, RFC8522-2.3.1-4, RFC8522-2.3.1-5, RFC8522-2.3.2-1, RFC8522-2.3.3-1, RFC8522-3.1.1-1, RFC8522-3.2.1-1, RFC8522-3.3-1, RFC8522-3.3.2-1, RFC8522-6-1 |
| RFC 7854 | BMP v3 | 25 of 39 MUST proven | unit 25 | - |
| RFC 8671 | BMP Adj-RIB-Out | 2 of 11 MUST proven | unit 2 | RFC8671-5.2-1, RFC8671-5.2-2 |
| RFC 9069 | BMP Loc-RIB monitoring | 10 of 16 MUST proven | unit 10 | - |
BGP session operations: graceful restart, shutdown, route reflection, route servers, and AS migration
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 4456 | Route Reflection | 1 of 4 MUST proven | unit 1 | - |
| RFC 5065 | BGP confederations | not walked | - | - |
| RFC 7705 | AS migration: Local AS, No Prepend Inbound, Replace Old AS, Internal BGP AS Migration | 9 of 9 MUST proven | unit 9 | - |
| RFC 4724 | Graceful Restart | 14 of 26 MUST proven | interop 1, unit 13 | RFC4724-3-5, RFC4724-4.1-1, RFC4724-4.1-2, RFC4724-4.1-3, RFC4724-4.1-5, RFC4724-4.1-6, RFC4724-4.1-8, RFC4724-4.2-1, RFC4724-4.2-2 |
| RFC 7947 | BGP Route Server | 2 of 3 MUST proven | unit 2 | RFC7947-2.1-1 |
| RFC 8203 | Administrative Shutdown Communication | 3 of 5 MUST proven | unit 3 | - |
| RFC 9003 | Administrative Shutdown Communication update | 1 of 4 MUST proven | unit 1 | - |
| RFC 8538 | Notification GR | not walked | - | - |
| RFC 9494 | Long-Lived Graceful Restart | 8 of 25 MUST proven | functional 2, unit 6 | RFC9494-4.2-10, RFC9494-4.2-7, RFC9494-4.2-9, RFC9494-4.3-2, RFC9494-4.7.2-1, RFC9494-4.7.2-2, RFC9494-5-2 |
BGP segment routing, SRv6, and tunnel encapsulation
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 8669 | BGP Prefix-SID attribute | 13 of 24 MUST proven | functional 6, unit 7 | RFC8669-3.1-1, RFC8669-4.1-3, RFC8669-4.1-4, RFC8669-4.1-5, RFC8669-4.1-7, RFC8669-5.1-1, RFC8669-6-2 |
| RFC 9012 | Tunnel Encapsulation attribute | 25 of 76 MUST proven | unit 25 | RFC9012-11-1, RFC9012-11-11, RFC9012-11-2, RFC9012-11-5, RFC9012-11-6, RFC9012-11-8, RFC9012-13-16, RFC9012-13-17, RFC9012-13-21, RFC9012-13-4, RFC9012-13-6, RFC9012-15-1, RFC9012-3.1.1-3, RFC9012-3.2.1-1, RFC9012-3.2.1-3, RFC9012-3.2.1-4, RFC9012-3.2.1-5, RFC9012-3.2.1-6, RFC9012-3.2.4-1, RFC9012-3.2.5-1, RFC9012-3.3-1, RFC9012-3.3.2-1, RFC9012-3.4.1-2, RFC9012-3.4.1-3, RFC9012-3.4.1-4, RFC9012-3.4.2-2, RFC9012-3.5-1, RFC9012-3.5-2, RFC9012-3.5-4, RFC9012-3.6-1, RFC9012-3.6-13, RFC9012-3.6-2, RFC9012-3.6-3, RFC9012-3.6-4, RFC9012-3.6-5, RFC9012-3.6-6, RFC9012-3.6-7, RFC9012-3.6-8, RFC9012-3.7-2, RFC9012-3.7-3, RFC9012-3.7-4, RFC9012-4.1-1, RFC9012-4.1-2, RFC9012-4.1-3, RFC9012-4.2-1, RFC9012-4.3-1, RFC9012-6-2, RFC9012-7.1-1, RFC9012-8-1, RFC9012-8-2 |
| RFC 9252 | BGP SRv6 Service TLV (Prefix-SID) | 14 of 25 MUST proven | functional 4, unit 10 | RFC9252-3.2-6, RFC9252-3.3-2, RFC9252-4.1-1, RFC9252-5-2, RFC9252-6.1-1, RFC9252-6.2-1 |
| RFC 9256 | Segment Routing Policy Architecture | 0 of 22 MUST proven | - | RFC9256-2.1-1, RFC9256-2.1-3, RFC9256-2.11-1, RFC9256-2.2-1, RFC9256-2.2-2, RFC9256-2.2-3, RFC9256-2.4-1, RFC9256-2.4-2, RFC9256-2.6-1, RFC9256-2.9-1, RFC9256-4-6, RFC9256-4-7, RFC9256-5.1-2, RFC9256-5.1-5, RFC9256-5.2-1, RFC9256-6.1-3, RFC9256-6.2-4, RFC9256-6.2.3-3, RFC9256-6.2.3-4, RFC9256-7-1 |
| RFC 9830 | BGP SR Policy | 37 of 97 MUST proven | unit 37 | RFC9830-2.4.4.2.4-4, RFC9830-2.4.5-2, RFC9830-2.4.5-3, RFC9830-2.4.5-4, RFC9830-2.4.5-5, RFC9830-2.4.5-6, RFC9830-2.4.5-7, RFC9830-2.4.5-8, RFC9830-3-3, RFC9830-4.1-2, RFC9830-4.2.1-1, RFC9830-4.2.1-4, RFC9830-4.2.1-5, RFC9830-4.2.1-8, RFC9830-4.2.1-9, RFC9830-4.2.2-1, RFC9830-4.2.2-2, RFC9830-4.2.2-5, RFC9830-4.2.3-1, RFC9830-4.2.3-2, RFC9830-5-5, RFC9830-5-6, RFC9830-5-7, RFC9830-5-8 |
BGP session transport security
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 2385 | TCP MD5 | 8 of 8 MUST proven | unit 8 | - |
| RFC 5082 | GTSM and TTL security | 4 of 4 MUST proven | unit 4 | - |
| RFC 5925 | TCP-AO | not walked | - | - |
BGP/MPLS VPNs, labeled routes, VPLS, and EVPN
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 4364 | BGP/MPLS IP VPNs | 0 of 8 MUST proven | - | RFC4364-13.1-1, RFC4364-13.1-2, RFC4364-4.3.1-1, RFC4364-4.3.1-2, RFC4364-4.3.2-1, RFC4364-4.3.2-2, RFC4364-4.3.2-3, RFC4364-6-1 |
| RFC 4659 | VPNv6 | 4 of 18 MUST proven | interop 1, unit 3 | RFC4659-3.2.1.2-1, RFC4659-4-1, RFC4659-4-2, RFC4659-4-3, RFC4659-4-4, RFC4659-4-5, RFC4659-4-6, RFC4659-4-7, RFC4659-8-1, RFC4659-8-2, RFC4659-8-3, RFC4659-8-4, RFC4659-8-5 |
| RFC 8277 | BGP Labeled Unicast | 11 of 35 MUST proven | unit 11 | RFC8277-2-1, RFC8277-2-3, RFC8277-2.1-1, RFC8277-2.1-10, RFC8277-2.1-11, RFC8277-2.1-12, RFC8277-2.1-13, RFC8277-2.1-14, RFC8277-2.1-15, RFC8277-2.1-2, RFC8277-2.1-3, RFC8277-2.1-4, RFC8277-2.1-5, RFC8277-2.1-6, RFC8277-2.1-7, RFC8277-2.1-8, RFC8277-2.1-9, RFC8277-2.2-2, RFC8277-3.2.1-2, RFC8277-3.2.1-3, RFC8277-3.2.1-4, RFC8277-3.2.2-1, RFC8277-3.2.2-2, RFC8277-3.2.2-3 |
| RFC 4684 | Route Target Constraint | 2 of 6 MUST proven | unit 2 | RFC4684-3.2-1, RFC4684-3.2-2, RFC4684-3.2-3, RFC4684-6-1 |
| RFC 4761 | VPLS NLRI | 0 of 18 MUST proven | - | RFC4761-2.3-1, RFC4761-3.2.3-1, RFC4761-3.2.3-2, RFC4761-3.2.4-1, RFC4761-3.2.4-2, RFC4761-3.2.4-3, RFC4761-3.2.4-4, RFC4761-3.2.4-5, RFC4761-3.2.4-6, RFC4761-3.3-1, RFC4761-3.4.2-1, RFC4761-3.5-1, RFC4761-3.5-2, RFC4761-4.2.1-1, RFC4761-4.2.2-1, RFC4761-4.2.5-1, RFC4761-6-1, RFC4761-6-2 |
| RFC 6514 | MVPN and PMSI Tunnel | not walked | - | - |
| RFC 7432 | EVPN | 11 of 103 MUST proven | unit 11 | RFC7432-10-2, RFC7432-10-3, RFC7432-10-4, RFC7432-10.1-1, RFC7432-10.1-4, RFC7432-10.1-5, RFC7432-11-1, RFC7432-11.1-1, RFC7432-11.1-2, RFC7432-11.2-1, RFC7432-11.2-2, RFC7432-11.2-3, RFC7432-11.2-5, RFC7432-11.2-6, RFC7432-11.2-7, RFC7432-12-1, RFC7432-12.1-1, RFC7432-12.1-2, RFC7432-12.2-1, RFC7432-13.1-1, RFC7432-13.1-2, RFC7432-13.1-3, RFC7432-13.1-4, RFC7432-13.1-5, RFC7432-13.1-6, RFC7432-13.1-7, RFC7432-14.1-1, RFC7432-14.1.1-1, RFC7432-14.1.1-2, RFC7432-14.1.1-3, RFC7432-14.1.2-1, RFC7432-14.1.2-2, RFC7432-15-1, RFC7432-15-2, RFC7432-15.1-1, RFC7432-15.1-2, RFC7432-15.2-1, RFC7432-17.3-1, RFC7432-17.3-3, RFC7432-5-10, RFC7432-5-11, RFC7432-5-12, RFC7432-5-13, RFC7432-5-3, RFC7432-5-4, RFC7432-5-5, RFC7432-5-6, RFC7432-5-7, RFC7432-5-8, RFC7432-5-9, RFC7432-6.1-1, RFC7432-6.1-2, RFC7432-6.2-1, RFC7432-6.2-2, RFC7432-6.3-1, RFC7432-6.3-2, RFC7432-6.3-3, RFC7432-6.3-4, RFC7432-7.10.1-1, RFC7432-7.10.1-2, RFC7432-7.6-1, RFC7432-7.6-2, RFC7432-7.9-1, RFC7432-7.9-2, RFC7432-7.9-3, RFC7432-8.2.1-1, RFC7432-8.2.1-11, RFC7432-8.2.1-3, RFC7432-8.2.1-5, RFC7432-8.2.1-6, RFC7432-8.2.1-8, RFC7432-8.2.1.1-1, RFC7432-8.3-1, RFC7432-8.3.1-1, RFC7432-8.3.1.1-1, RFC7432-8.3.1.1-2, RFC7432-8.3.1.1-3, RFC7432-8.3.1.1-6, RFC7432-8.3.1.1-7, RFC7432-8.3.1.2-1, RFC7432-8.3.1.2-2, RFC7432-8.4-1, RFC7432-8.4.1-1, RFC7432-8.5-2, RFC7432-9.1-1, RFC7432-9.2.1-2, RFC7432-9.2.1-3, RFC7432-9.2.1-4, RFC7432-9.2.2-1, RFC7432-9.2.2-2 |
| RFC 9136 | EVPN IP Prefix (RT-5) | 3 of 14 MUST proven | unit 3 | RFC9136-3-1, RFC9136-3.1-7, RFC9136-3.1-8, RFC9136-3.1-9, RFC9136-3.2-1, RFC9136-3.2-2, RFC9136-3.2-3, RFC9136-3.2-4 |
| RFC 4762 | VPLS using LDP signaling | not walked | - | - |
DHCP, address autoconfiguration, and TFTP provisioning
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 1350 | TFTP | 8 of 11 MUST proven | unit 8 | RFC1350-4-2, RFC1350-5-1, RFC1350-5-5 |
| RFC 2131 | DHCPv4 | 21 of 71 MUST proven | unit 21 | RFC2131-2-1, RFC2131-3.1-3, RFC2131-3.1-4, RFC2131-3.1-6, RFC2131-3.1-7, RFC2131-3.2-1, RFC2131-3.2-3, RFC2131-3.4-1, RFC2131-4.1-15, RFC2131-4.1-4, RFC2131-4.1-5, RFC2131-4.1-7, RFC2131-4.1-8, RFC2131-4.2-1, RFC2131-4.3.1-1, RFC2131-4.3.1-10, RFC2131-4.3.1-3, RFC2131-4.3.1-5, RFC2131-4.3.1-7, RFC2131-4.3.2-2, RFC2131-4.3.3-1, RFC2131-4.3.5-1, RFC2131-4.4-1, RFC2131-4.4-2, RFC2131-4.4-3, RFC2131-4.4.2-1, RFC2131-4.4.2-2, RFC2131-4.4.3-1 |
| RFC 2132 | DHCP options | 1 of 34 MUST proven | unit 1 | RFC2132-3.10-1, RFC2132-3.11-1, RFC2132-3.12-1, RFC2132-3.13-1, RFC2132-3.6-1, RFC2132-3.7-1, RFC2132-3.9-1, RFC2132-4.3-1, RFC2132-4.7-1, RFC2132-5.8-1, RFC2132-8.10-1, RFC2132-8.12-1, RFC2132-8.13-1, RFC2132-8.14-1, RFC2132-8.15-1, RFC2132-8.16-1, RFC2132-8.17-1, RFC2132-8.18-1, RFC2132-8.19-1, RFC2132-8.2-1, RFC2132-8.20-1, RFC2132-8.21-1, RFC2132-8.3-1, RFC2132-8.9-1, RFC2132-9.14-1, RFC2132-9.8-1 |
| RFC 4861 | IPv6 Neighbor Discovery and Router Advertisement | 30 of 138 MUST proven | unit 30 | RFC4861-11.2-1, RFC4861-11.2-2, RFC4861-2.3-1, RFC4861-4.4-3, RFC4861-4.6-1, RFC4861-6.1.1-1, RFC4861-6.1.1-2, RFC4861-6.2.1-1, RFC4861-6.2.1-8, RFC4861-6.2.4-1, RFC4861-6.2.5-1, RFC4861-6.2.5-2, RFC4861-6.2.6-1, RFC4861-7.2.6-1, RFC4861-7.2.8-1, RFC4861-7.2.8-2, RFC4861-9-7 |
| RFC 2347 | TFTP option negotiation | 3 of 3 MUST proven | unit 3 | - |
| RFC 2349 | TFTP timeout and transfer size options | 3 of 4 MUST proven | unit 3 | RFC2349-x-4 |
| RFC 4578 | DHCP PXE options | 1 of 5 MUST proven | unit 1 | RFC4578-2.1-1, RFC4578-2.2-1, RFC4578-2.3-1 |
| RFC 4862 | IPv6 stateless address autoconfiguration | 0 of 16 MUST proven | - | RFC4862-5.1-1, RFC4862-5.4-1, RFC4862-5.4-2, RFC4862-5.4-5, RFC4862-5.4.1-1, RFC4862-5.4.2-1, RFC4862-5.4.2-4, RFC4862-5.4.3-1, RFC4862-5.4.5-1, RFC4862-5.5-2 |
| RFC 7440 | TFTP windowsize | 9 of 9 MUST proven | unit 9 | - |
| RFC 8106 | RA DNS options (RDNSS, DNSSL) | 5 of 11 MUST proven | unit 5 | RFC8106-5.2-1, RFC8106-5.2-2, RFC8106-5.2-3, RFC8106-5.2-4, RFC8106-5.3.1-2, RFC8106-5.3.1-3 |
| RFC 9915 | DHCPv6 | 85 of 126 MUST proven | unit 85 | RFC9915-10-1, RFC9915-11.2-1, RFC9915-11.2-2, RFC9915-11.2-3, RFC9915-11.2-4, RFC9915-11.2-5, RFC9915-11.3-1, RFC9915-15-2, RFC9915-16.10-3, RFC9915-18.2.1-7, RFC9915-18.2.10.1-1, RFC9915-18.2.10.5-1, RFC9915-18.2.11-2, RFC9915-18.2.12-3, RFC9915-18.2.4-2, RFC9915-18.2.6-1, RFC9915-18.2.6-2, RFC9915-18.2.6-3, RFC9915-18.2.6-4, RFC9915-18.2.7-5, RFC9915-18.2.7-8, RFC9915-18.2.9-4, RFC9915-20.2-1, RFC9915-20.3-3, RFC9915-20.3-4, RFC9915-21.15-1, RFC9915-21.15-2, RFC9915-21.16-1, RFC9915-21.17-1, RFC9915-21.17-2, RFC9915-21.17-3, RFC9915-21.23-1, RFC9915-21.23-5, RFC9915-21.23-6, RFC9915-21.23-7, RFC9915-21.25-2, RFC9915-21.25-3, RFC9915-21.25-4 |
| RFC 7084 | IPv6 customer edge router | 19 of 41 MUST proven | unit 19 | RFC7084-4.1-3, RFC7084-4.2-14, RFC7084-4.2-15, RFC7084-4.2-16, RFC7084-4.2-20, RFC7084-4.2-22, RFC7084-4.2-9, RFC7084-4.3-10, RFC7084-4.3-11, RFC7084-4.3-12, RFC7084-4.3-14, RFC7084-4.3-19, RFC7084-4.3-2, RFC7084-4.3-3, RFC7084-4.3-5, RFC7084-4.3-6 |
DNS, DNSSEC, encrypted DNS transports, and AS112
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 1035 | DNS message behavior | 12 of 27 MUST proven | functional 1, unit 11 | - |
| RFC 2181 | DNS clarifications | 12 of 23 MUST proven | unit 12 | RFC2181-10.1-4, RFC2181-10.1.1-1, RFC2181-10.2-1, RFC2181-5.4.1-8, RFC2181-5.5-4 |
| RFC 2782 | DNS SRV records | 0 of 7 MUST proven | - | RFC2782-Notes-2, RFC2782-Notes-3, RFC2782-Priority-1, RFC2782-Target-1, RFC2782-Target-2 |
| RFC 4035 | DNSSEC protocol modifications | 4 of 108 MUST proven | unit 4 | RFC4035-2.1-2, RFC4035-2.1-4, RFC4035-2.1-5, RFC4035-2.2-1, RFC4035-2.2-3, RFC4035-2.2-4, RFC4035-2.2-5, RFC4035-2.2-6, RFC4035-2.2-7, RFC4035-2.2-8, RFC4035-2.3-1, RFC4035-2.3-3, RFC4035-2.3-4, RFC4035-2.3-5, RFC4035-2.3-6, RFC4035-2.3-7, RFC4035-2.4-3, RFC4035-2.4-4, RFC4035-2.5-1, RFC4035-2.5-2, RFC4035-2.6-1, RFC4035-3-1, RFC4035-3-2, RFC4035-3-5, RFC4035-3.1-1, RFC4035-3.1-2, RFC4035-3.1-3, RFC4035-3.1.1-3, RFC4035-3.1.1-4, RFC4035-3.1.1-5, RFC4035-3.1.1-6, RFC4035-3.1.1-8, RFC4035-3.1.2-3, RFC4035-3.1.2-4, RFC4035-3.1.3-1, RFC4035-3.1.3.1-1, RFC4035-3.1.3.2-1, RFC4035-3.1.3.3-1, RFC4035-3.1.3.3-2, RFC4035-3.1.3.4-1, RFC4035-3.1.4-1, RFC4035-3.1.4-2, RFC4035-3.1.4-3, RFC4035-3.1.5-2, RFC4035-3.1.5-3, RFC4035-3.1.5-4, RFC4035-3.1.5-5, RFC4035-3.1.5-6, RFC4035-3.1.5-7, RFC4035-3.1.6-6, RFC4035-3.2.1-1, RFC4035-3.2.1-2, RFC4035-3.2.1-3, RFC4035-3.2.2-1, RFC4035-3.2.2-4, RFC4035-3.2.3-2, RFC4035-4.1-5, RFC4035-4.2-1, RFC4035-4.2-3, RFC4035-4.2-5, RFC4035-4.2-6, RFC4035-4.3-1, RFC4035-4.4-1, RFC4035-4.7-2, RFC4035-4.7-3, RFC4035-4.7-7, RFC4035-4.8-1, RFC4035-4.9.3-2, RFC4035-5-1, RFC4035-5-2, RFC4035-5-3, RFC4035-5.2-1, RFC4035-5.2-3, RFC4035-5.3.1-1, RFC4035-5.3.1-10, RFC4035-5.3.1-2, RFC4035-5.3.1-3, RFC4035-5.3.1-4, RFC4035-5.3.1-5, RFC4035-5.3.1-6, RFC4035-5.3.1-7, RFC4035-5.3.1-8, RFC4035-5.3.1-9, RFC4035-5.3.2-1, RFC4035-5.3.2-2, RFC4035-5.3.2-3, RFC4035-5.3.3-1, RFC4035-5.3.3-2, RFC4035-5.4-1, RFC4035-5.4-2, RFC4035-5.4-3, RFC4035-5.4-4, RFC4035-5.5-2, RFC4035-5.5-3 |
| RFC 8484 | DNS Queries over HTTPS (DoH) | 1 of 16 MUST proven | unit 1 | RFC8484-3-1, RFC8484-4.1-3, RFC8484-5.1-2, RFC8484-5.1-3, RFC8484-5.3-1, RFC8484-5.4-2 |
| RFC 7534 | AS112 operations | 2 of 3 MUST proven | unit 2 | - |
| RFC 7535 | EMPTY.AS112.ARPA | 0 of 1 MUST proven | - | RFC7535-6-1 |
| RFC 7871 | EDNS0 Client Subnet | 0 of 36 MUST proven | - | RFC7871-11.1-2, RFC7871-11.2-1, RFC7871-11.3-4, RFC7871-12.1-3, RFC7871-12.1-4, RFC7871-12.1-5, RFC7871-6-1, RFC7871-6-2, RFC7871-7.1.1-2, RFC7871-7.1.1-3, RFC7871-7.1.1-4, RFC7871-7.1.1-7, RFC7871-7.1.2-2, RFC7871-7.1.2-3, RFC7871-7.1.2-5, RFC7871-7.1.3-1, RFC7871-7.1.3-2, RFC7871-7.1.3-3, RFC7871-7.2.1-12, RFC7871-7.2.1-2, RFC7871-7.2.1-3, RFC7871-7.2.1-4, RFC7871-7.2.1-5, RFC7871-7.2.1-8, RFC7871-7.3-3, RFC7871-7.3-4, RFC7871-7.3-6, RFC7871-7.3.1-1, RFC7871-7.3.1-3, RFC7871-7.3.1-4, RFC7871-7.3.2-1, RFC7871-7.3.2-4, RFC7871-7.5-1, RFC7871-9-1 |
| RFC 5625 | DNS proxy guidelines | 12 of 12 MUST proven | unit 12 | - |
| RFC 7858 | DNS over TLS (DoT) | 3 of 19 MUST proven | unit 3 | RFC7858-3.1-2, RFC7858-3.1-3, RFC7858-3.1-7, RFC7858-3.3-4, RFC7858-3.3-5, RFC7858-3.4-7, RFC7858-3.4-8, RFC7858-3.4-9, RFC7858-4.2-4, RFC7858-4.2-5, RFC7858-4.2-6, RFC7858-4.2-7 |
Drafts and non-RFC standards tracked near RFC work
These are not RFCs, but they sit next to RFC implementation status and are useful when reading the other tables on this page.
| Standard | Area | Proof | Unmet |
|---|---|---|---|
| sflow-v5 | sFlow export | 21 of 31 MUST proven | SFLOW-V5-4.3-1, SFLOW-V5-x-13, SFLOW-V5-x-36, SFLOW-V5-x-37, SFLOW-V5-x-38, SFLOW-V5-x-39, SFLOW-V5-x-40, SFLOW-V5-x-41, SFLOW-V5-x-42 |
| draft-walton-bgp-hostname-capability | BGP FQDN capability code 73 | ✕ | - |
| draft-abraitis-bgp-version-capability | BGP Software Version capability code 75 | 11 of 11 MUST proven | - |
| draft-abraitis-idr-addpath-paths-limit | BGP PATHS-LIMIT | 1 of 4 MUST proven | - |
| draft-ietf-bess-mup-safi | BGP Mobile User Plane SAFI 85 | 17 of 47 MUST proven | DRAFT-IETF-BESS-MUP-SAFI-3.1.3.1-4, DRAFT-IETF-BESS-MUP-SAFI-3.1.4.1-2, DRAFT-IETF-BESS-MUP-SAFI-3.3.1-1, DRAFT-IETF-BESS-MUP-SAFI-3.3.1-2, DRAFT-IETF-BESS-MUP-SAFI-3.3.1-3, DRAFT-IETF-BESS-MUP-SAFI-3.3.1-4, DRAFT-IETF-BESS-MUP-SAFI-3.3.10-1, DRAFT-IETF-BESS-MUP-SAFI-3.3.10-2, DRAFT-IETF-BESS-MUP-SAFI-3.3.11-1, DRAFT-IETF-BESS-MUP-SAFI-3.3.12-4, DRAFT-IETF-BESS-MUP-SAFI-3.3.12-5, DRAFT-IETF-BESS-MUP-SAFI-3.3.12-6, DRAFT-IETF-BESS-MUP-SAFI-3.3.12-7, DRAFT-IETF-BESS-MUP-SAFI-3.3.2-1, DRAFT-IETF-BESS-MUP-SAFI-3.3.3-1, DRAFT-IETF-BESS-MUP-SAFI-3.3.3-2, DRAFT-IETF-BESS-MUP-SAFI-3.3.3-3, DRAFT-IETF-BESS-MUP-SAFI-3.3.3-4, DRAFT-IETF-BESS-MUP-SAFI-3.3.4-1, DRAFT-IETF-BESS-MUP-SAFI-3.3.4-2, DRAFT-IETF-BESS-MUP-SAFI-3.3.4-3, DRAFT-IETF-BESS-MUP-SAFI-3.3.4-4, DRAFT-IETF-BESS-MUP-SAFI-3.3.5-2, DRAFT-IETF-BESS-MUP-SAFI-3.3.6-1, DRAFT-IETF-BESS-MUP-SAFI-3.3.6-2, DRAFT-IETF-BESS-MUP-SAFI-3.3.6-4, DRAFT-IETF-BESS-MUP-SAFI-3.3.7-1, DRAFT-IETF-BESS-MUP-SAFI-3.3.8-1, DRAFT-IETF-BESS-MUP-SAFI-3.3.9-1, DRAFT-IETF-BESS-MUP-SAFI-3.3.9-2 |
| draft-ietf-idr-linklocal-capability | Link-local next-hop capability code 77 | 13 of 15 MUST proven | DRAFT-IETF-IDR-LINKLOCAL-CAPABILITY-1-2, DRAFT-IETF-IDR-LINKLOCAL-CAPABILITY-4-15 |
| draft-ietf-sidrops-aspa-verification | ASPA path verification | 8 of 10 MUST proven | DRAFT-IETF-SIDROPS-ASPA-VERIFICATION-5.1-2 |
| draft-ietf-idr-bgp-bfd-strict-mode | BFD strict mode for BGP, capability code 74 | 4 of 4 MUST proven | - |
EAP methods and their TLS and CHAP building blocks
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 3748 | EAP | 42 of 59 MUST proven | unit 42 | RFC3748-2.3-1, RFC3748-3.1-1, RFC3748-3.1-2, RFC3748-3.1-3, RFC3748-4.1-2, RFC3748-5.7-1 |
| RFC 2759 | MS-CHAPv2 (PPP and EAP inside IKEv2) | 4 of 7 MUST proven | unit 4 | - |
| RFC 5216 | EAP-TLS (EAP inside IKEv2) | 30 of 47 MUST proven | unit 30 | RFC5216-2.4-5, RFC5216-2.4-7, RFC5216-5.2-1, RFC5216-5.2-2, RFC5216-5.2-3, RFC5216-5.2-4, RFC5216-5.3-2, RFC5216-5.3-3, RFC5216-5.3-5 |
| RFC 5998 | IKEv2 EAP | 1 of 6 MUST proven | unit 1 | RFC5998-3-1, RFC5998-3-2, RFC5998-3-3, RFC5998-3-4, RFC5998-4-1 |
First-hop redundancy
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 9568 | VRRPv3 (IPv4 and IPv6) | 37 of 66 MUST proven | unit 37 | RFC9568-5.1.1.2-1, RFC9568-5.1.2.2-1, RFC9568-6.4.2-3, RFC9568-6.4.3-4, RFC9568-8.2.2-2, RFC9568-8.2.2-3, RFC9568-8.2.3-1, RFC9568-8.4.2-1, RFC9568-8.4.2-2, RFC9568-8.4.2-3 |
| RFC 3768 | VRRPv2 (IPv4 only) | 31 of 41 MUST proven | unit 31 | RFC3768-5.2.2-1, RFC3768-8.3-1, RFC3768-9.2-1 |
| RFC 5798 | VRRPv3 (obsoleted by RFC 9568) | 49 of 59 MUST proven | unit 49 | RFC5798-6.4.3-4, RFC5798-7.1-3, RFC5798-8.2.2-2, RFC5798-8.2.2-3, RFC5798-8.2.3-1, RFC5798-8.4.2-1, RFC5798-A.2-1, RFC5798-A.2-3 |
Flow export: NetFlow v9 and IPFIX
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 3954 | NetFlow v9 | 4 of 14 MUST proven | unit 4 | RFC3954-x-2, RFC3954-x-22, RFC3954-x-23, RFC3954-x-5, RFC3954-x-6, RFC3954-x-7 |
| RFC 7011 | IPFIX | 12 of 50 MUST proven | unit 12 | RFC7011-10-1, RFC7011-10-2, RFC7011-10-5, RFC7011-10.2.2-1, RFC7011-10.3.2-1, RFC7011-10.4.1-1, RFC7011-10.4.4-1, RFC7011-11-1, RFC7011-11.1-1, RFC7011-11.1-2, RFC7011-11.1-3, RFC7011-11.1-4, RFC7011-11.3-1, RFC7011-11.3-2, RFC7011-11.3-3, RFC7011-11.3-4, RFC7011-3.2-2, RFC7011-3.4.2-1, RFC7011-3.4.2.1-1, RFC7011-4.1-1, RFC7011-4.1-2, RFC7011-4.1-3, RFC7011-6.1.3-1, RFC7011-6.1.4-1, RFC7011-6.1.6-1, RFC7011-6.1.6-2, RFC7011-6.2-3, RFC7011-7-1, RFC7011-7-2, RFC7011-8.1-1, RFC7011-8.2-4, RFC7011-x-2 |
| RFC 7012 | IPFIX Information Model | 1 of 6 MUST proven | unit 1 | RFC7012-2.1-1, RFC7012-2.1-2, RFC7012-2.1-3, RFC7012-2.1-5, RFC7012-4-2 |
IPsec, IKEv2, and kernel security associations
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 4739 | Multiple authentication exchanges | 2 of 2 MUST proven | unit 2 | - |
| RFC 5685 | IKEv2 redirect | 0 of 26 MUST proven | - | RFC5685-11-1, RFC5685-3-1, RFC5685-3-2, RFC5685-3-3, RFC5685-3-4, RFC5685-3-5, RFC5685-3-6, RFC5685-3-7, RFC5685-4-1, RFC5685-5-1, RFC5685-5-2, RFC5685-6-1, RFC5685-6-2, RFC5685-6-3, RFC5685-6-4, RFC5685-6-5, RFC5685-6-6, RFC5685-9.1-1, RFC5685-9.1-2, RFC5685-9.2-1, RFC5685-9.2-2, RFC5685-9.2-3, RFC5685-9.2-4, RFC5685-9.2-5, RFC5685-9.3-1, RFC5685-9.3-2 |
| RFC 4754 | ECDSA authentication methods 9, 10 and 11 | 1 of 1 MUST proven | unit 1 | - |
| RFC 5280 | X.509 certificates and CRLs | 32 of 102 MUST proven | unit 32 | RFC5280-4.1.2.4-1, RFC5280-4.1.2.5-3, RFC5280-4.2-1, RFC5280-4.2-2, RFC5280-4.2-4, RFC5280-4.2.1.10-1, RFC5280-4.2.1.10-3, RFC5280-4.2.1.10-5, RFC5280-4.2.1.4-1, RFC5280-4.2.1.4-2, RFC5280-4.2.1.4-3, RFC5280-4.2.1.4-4, RFC5280-4.2.1.6-11, RFC5280-4.2.1.6-8, RFC5280-4.2.1.6-9, RFC5280-5-1, RFC5280-6.1-1, RFC5280-6.3-1, RFC5280-7.1-2, RFC5280-7.2-1 |
| RFC 3948 | UDP encapsulation of ESP | 6 of 11 MUST proven | unit 6 | RFC3948-2.1-4 |
| RFC 4106 | ESP | 4 of 8 MUST proven | unit 4 | - |
| RFC 4301 | IPsec architecture | 44 of 101 MUST proven | unit 44 | RFC4301-4.1-5, RFC4301-4.4.1-13, RFC4301-4.4.1-2, RFC4301-4.4.1-3, RFC4301-4.4.1.1-1, RFC4301-4.4.1.1-2, RFC4301-4.4.1.1-5, RFC4301-4.4.1.2-2, RFC4301-4.4.2.1-13, RFC4301-4.4.2.1-14, RFC4301-4.4.2.1-15, RFC4301-4.4.2.1-16, RFC4301-4.4.2.1-17, RFC4301-4.4.2.1-2, RFC4301-4.4.2.1-3, RFC4301-4.4.3.3-1, RFC4301-5.1-7, RFC4301-5.1.2.1-1, RFC4301-5.2-1, RFC4301-5.2-2, RFC4301-5.2-9, RFC4301-6-1, RFC4301-6.2-2, RFC4301-6.2-3, RFC4301-6.2-4, RFC4301-6.2-5, RFC4301-7-1, RFC4301-7.2-1, RFC4301-7.2-2, RFC4301-7.3-1, RFC4301-7.3-2, RFC4301-8.1-2 |
| RFC 4302 | Authentication Header | 9 of 32 MUST proven | unit 9 | RFC4302-2.5-5, RFC4302-2.5.1-1, RFC4302-4-1, RFC4302-A2-1 |
| RFC 4303 | ESP | 7 of 23 MUST proven | unit 7 | RFC4303-2.2-1, RFC4303-2.2-2, RFC4303-2.2-3, RFC4303-2.4-1, RFC4303-2.6-1, RFC4303-2.6-2, RFC4303-3.3.3-1, RFC4303-3.3.4-1, RFC4303-3.3.4-2, RFC4303-3.4.2-1, RFC4303-3.4.2-2, RFC4303-3.4.3-3, RFC4303-3.4.4.1-1, RFC4303-3.4.4.1-2, RFC4303-3.4.4.2-1 |
| RFC 5282 | IKEv2 AEAD algorithms | 19 of 19 MUST proven | unit 19 | - |
| RFC 7296 | IKEv2 | 89 of 234 MUST proven | interop 1, functional 1, unit 87 | - |
| RFC 8247 | IKEv2 algorithms | 17 of 20 MUST proven | unit 17 | RFC8247-2.2-2, RFC8247-2.3-2, RFC8247-3.2-2 |
| RFC 4555 | MOBIKE | 3 of 14 MUST proven | unit 3 | - |
| RFC 7383 | IKEv2 fragmentation | 0 of 25 MUST proven | - | - |
| RFC 7634 | ESP | 1 of 2 MUST proven | unit 1 | - |
| RFC 8031 | Curve25519 and Curve448 key exchange | 0 of 3 MUST proven | - | RFC8031-2-1, RFC8031-3.2-1, RFC8031-3.2-2 |
| RFC 8221 | ESP algorithms | 15 of 16 MUST proven | unit 15 | - |
| RFC 9329 | IKE and ESP over TCP | 0 of 30 MUST proven | - | RFC9329-1.2-1, RFC9329-2-1, RFC9329-3-1, RFC9329-3.1-1, RFC9329-3.1-2, RFC9329-3.2-1, RFC9329-3.2-2, RFC9329-3.2-3, RFC9329-4-1, RFC9329-5-1, RFC9329-5-2, RFC9329-5.1-1, RFC9329-6.1-1, RFC9329-6.1-2, RFC9329-6.1-3, RFC9329-6.1-4, RFC9329-6.1-5, RFC9329-6.1-6, RFC9329-6.1-7, RFC9329-6.1-8, RFC9329-6.1-9, RFC9329-6.2-1, RFC9329-6.3-1, RFC9329-6.6-1, RFC9329-6.7-1, RFC9329-7.1-1, RFC9329-7.1-2, RFC9329-7.2-1, RFC9329-7.5-1, RFC9329-9-1 |
| RFC 9370 | Multiple key exchanges (hybrid post-quantum) | 0 of 23 MUST proven | - | RFC9370-2.2.1-1, RFC9370-2.2.1-10, RFC9370-2.2.1-11, RFC9370-2.2.1-12, RFC9370-2.2.1-2, RFC9370-2.2.1-3, RFC9370-2.2.1-4, RFC9370-2.2.1-5, RFC9370-2.2.1-6, RFC9370-2.2.1-7, RFC9370-2.2.1-8, RFC9370-2.2.1-9, RFC9370-2.2.2-1, RFC9370-2.2.4-1, RFC9370-2.2.4-10, RFC9370-2.2.4-2, RFC9370-2.2.4-3, RFC9370-2.2.4-4, RFC9370-2.2.4-5, RFC9370-2.2.4-6, RFC9370-2.2.4-7, RFC9370-2.2.4-8, RFC9370-2.2.4-9 |
IS-IS
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 5301 | IS-IS dynamic hostname | 0 of 7 MUST proven | - | - |
| RFC 5304 | IS-IS HMAC-MD5 authentication | 0 of 9 MUST proven | - | RFC5304-2-5 |
| RFC 5305 | IS-IS wide metrics and TE TLVs | 8 of 14 MUST proven | unit 8 | RFC5305-3.2-2, RFC5305-3.3-2, RFC5305-3.7-1, RFC5305-4.1-3, RFC5305-4.3-1 |
| RFC 1195 | Integrated IS-IS for IPv4 | 25 of 41 MUST proven | unit 25 | RFC1195-1.2-1, RFC1195-1.4-1, RFC1195-1.4-3, RFC1195-3.10.2-1, RFC1195-3.2-3, RFC1195-8-1, RFC1195-8-2 |
| RFC 2966 | IS-IS up/down bit | 3 of 6 MUST proven | unit 3 | - |
| RFC 3787 | IS-IS interoperability guidelines | 5 of 5 MUST proven | interop 1, unit 4 | - |
| RFC 5303 | IS-IS point-to-point three-way | 8 of 17 MUST proven | unit 8 | RFC5303-3.1-2, RFC5303-3.1-3, RFC5303-3.2-12, RFC5303-3.2-4, RFC5303-3.2-8, RFC5303-3.2-9 |
| RFC 5308 | IS-IS IPv6 | 8 of 8 MUST proven | unit 8 | - |
| RFC 5310 | IS-IS generic crypto authentication | 6 of 9 MUST proven | unit 6 | RFC5310-3.2-6 |
| RFC 5120 | IS-IS multi-topology | not walked | - | - |
Configuration modeling and management protocols
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 7950 | YANG 1.1 data modeling | 37 of 91 MUST proven | functional 1, unit 36 | RFC7950-11-1, RFC7950-11-2, RFC7950-11-3, RFC7950-12-1, RFC7950-5.1-1, RFC7950-5.3-1, RFC7950-5.5-1, RFC7950-5.6.5-1, RFC7950-6.2.1-1, RFC7950-6.3.1-1, RFC7950-6.4-1, RFC7950-6.4-2, RFC7950-7.1.4-1, RFC7950-7.12-1, RFC7950-7.14.2-1, RFC7950-7.14.3-1, RFC7950-7.15-1, RFC7950-7.16-1, RFC7950-7.17-1, RFC7950-7.18.2-1, RFC7950-7.20.1-1, RFC7950-7.20.2-1, RFC7950-7.20.3-1, RFC7950-7.20.3.2-1, RFC7950-7.21.2-1, RFC7950-7.21.5-1, RFC7950-7.21.5-2, RFC7950-7.3-1, RFC7950-7.5.3-1, RFC7950-7.6.1-4, RFC7950-7.6.5-1, RFC7950-7.7-1, RFC7950-7.7.2-1, RFC7950-7.8.2-1, RFC7950-7.8.3-1, RFC7950-7.9.2-1, RFC7950-7.9.3-1, RFC7950-7.9.4-1, RFC7950-8.1-1, RFC7950-8.1-4, RFC7950-8.3.1-2, RFC7950-8.3.2-1, RFC7950-8.3.3-2, RFC7950-9.10.2-1, RFC7950-9.12-2, RFC7950-9.2.4-1, RFC7950-9.2.4-2, RFC7950-9.4.5-1, RFC7950-9.6.4-1, RFC7950-9.7-1, RFC7950-9.7.4-1, RFC7950-9.7.4.2-1, RFC7950-x-1, RFC7950-x-2 |
| RFC 5905 | NTP client (SNTP subset) | 0 of 8 MUST proven | - | RFC5905-11.2.3-1, RFC5905-2-1, RFC5905-2-2, RFC5905-7.4-1, RFC5905-7.4-2, RFC5905-7.4-3, RFC5905-7.4-4, RFC5905-7.4-5 |
MPLS, LDP, RSVP-TE, and fast reroute
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 2205 | RSVP base protocol | 31 of 75 MUST proven | unit 31 | RFC2205-1-1, RFC2205-1-2, RFC2205-1-3, RFC2205-1-4, RFC2205-2-10, RFC2205-2-11, RFC2205-2-12, RFC2205-2-5, RFC2205-2-6, RFC2205-2-9, RFC2205-2.5-1, RFC2205-3-10, RFC2205-3-11, RFC2205-3-16, RFC2205-3-21, RFC2205-3-22, RFC2205-3-23, RFC2205-3-24, RFC2205-3-25, RFC2205-3-26, RFC2205-3-27, RFC2205-3-28, RFC2205-3-29, RFC2205-3-3, RFC2205-3-30, RFC2205-3-31, RFC2205-3-32, RFC2205-3-33, RFC2205-3-34, RFC2205-3-35, RFC2205-3-36, RFC2205-3-38, RFC2205-3-4, RFC2205-3-43, RFC2205-3-5, RFC2205-3-6, RFC2205-3-7, RFC2205-3-8, RFC2205-3-9, RFC2205-3.9-1, RFC2205-4-1, RFC2205-4-2, RFC2205-4-3, RFC2205-4-5 |
| RFC 5036 | LDP | 29 of 91 MUST proven | unit 29 | RFC5036-2.5.1-3, RFC5036-2.5.1-4, RFC5036-2.5.3-2, RFC5036-2.5.3-7, RFC5036-2.6.1.2-1, RFC5036-2.6.1.3-1, RFC5036-2.7-1, RFC5036-2.8.1-1, RFC5036-2.8.1-2, RFC5036-2.8.1-3, RFC5036-2.8.1-4, RFC5036-2.8.1-5, RFC5036-2.8.1-6, RFC5036-2.8.1-7, RFC5036-2.8.2-1, RFC5036-2.8.2-10, RFC5036-2.8.2-11, RFC5036-2.8.2-12, RFC5036-2.8.2-13, RFC5036-2.8.2-2, RFC5036-2.8.2-3, RFC5036-2.8.2-4, RFC5036-2.8.2-5, RFC5036-2.8.2-6, RFC5036-2.8.2-7, RFC5036-2.8.2-8, RFC5036-2.8.2-9, RFC5036-2.9-1, RFC5036-3.4.2.2-1, RFC5036-3.4.2.2-2, RFC5036-3.4.2.2-3, RFC5036-3.4.2.3-1, RFC5036-3.4.4.1-3, RFC5036-3.4.5.1.1-1, RFC5036-3.4.5.1.1-2, RFC5036-3.4.5.1.1-3, RFC5036-3.4.5.1.2-1, RFC5036-3.4.5.1.2-2, RFC5036-3.4.5.1.2-3, RFC5036-3.5.1-1, RFC5036-3.5.11.1-1, RFC5036-3.5.3-10, RFC5036-3.5.3-11, RFC5036-3.5.3-12, RFC5036-3.5.3-13, RFC5036-3.5.3-14, RFC5036-3.5.3-2, RFC5036-3.5.7-1, RFC5036-3.5.8.1-1, RFC5036-3.5.8.1-2, RFC5036-3.5.8.1-3, RFC5036-3.5.8.1-4, RFC5036-3.5.9.1-1, RFC5036-3.5.9.1-2, RFC5036-3.5.9.1-3, RFC5036-3.6.1.1-1, RFC5036-3.6.1.2-1, RFC5036-A.1-1, RFC5036-A.1.2-1, RFC5036-A.1.7-1 |
| RFC 5561 | LDP | 1 of 17 MUST proven | unit 1 | RFC5561-10-1, RFC5561-3-1, RFC5561-3-2, RFC5561-3-5, RFC5561-4-1, RFC5561-4-2, RFC5561-6-1, RFC5561-6-2, RFC5561-6-3, RFC5561-8-1, RFC5561-8-2, RFC5561-8-3, RFC5561-8-4, RFC5561-9-1, RFC5561-9-2, RFC5561-9-3 |
| RFC 3031 | MPLS architecture | 2 of 10 MUST proven | unit 2 | RFC3031-3.10-1, RFC3031-3.10-2, RFC3031-3.16-2, RFC3031-3.16-3, RFC3031-3.23-1, RFC3031-3.8-1, RFC3031-4.1.2.2-1, RFC3031-x-1 |
| RFC 3032 | MPLS label stack encoding | 3 of 18 MUST proven | unit 3 | RFC3032-1-1, RFC3032-2.2-2, RFC3032-2.2-3, RFC3032-2.4.2-1, RFC3032-2.4.2-2, RFC3032-2.4.2-3, RFC3032-2.4.3-2, RFC3032-3.3-1, RFC3032-3.3-2, RFC3032-3.4-1, RFC3032-3.4-2, RFC3032-3.4-3, RFC3032-3.5-1, RFC3032-3.5-2, RFC3032-3.6-1, RFC3032-3.6-2 |
| RFC 3209 | RSVP-TE | 23 of 59 MUST proven | unit 23 | RFC3209-2.6-1, RFC3209-2.6-2, RFC3209-2.6-3, RFC3209-4.1.1.1-1, RFC3209-4.1.1.1-2, RFC3209-4.1.1.1-3, RFC3209-4.2.2-1, RFC3209-4.2.2-2, RFC3209-4.2.2-3, RFC3209-4.2.3-1, RFC3209-4.2.3-2, RFC3209-4.2.5-1, RFC3209-4.6.1-2, RFC3209-4.6.2-2, RFC3209-4.7.4-1, RFC3209-4.7.4-2, RFC3209-5.2.2-1, RFC3209-5.2.2-2, RFC3209-5.2.2-3, RFC3209-5.3-1, RFC3209-5.3-10, RFC3209-5.3-11, RFC3209-5.3-2, RFC3209-5.3-3, RFC3209-5.3-4, RFC3209-5.3-5, RFC3209-5.3-6, RFC3209-5.3-7, RFC3209-5.3-8, RFC3209-5.3-9, RFC3209-5.4-1, RFC3209-5.4-2 |
| RFC 4090 | RSVP-TE Fast Reroute | 29 of 33 MUST proven | unit 29 | RFC4090-4.4-5, RFC4090-6-8 |
| RFC 5443 | LDP IGP Synchronization (OSPF) | 5 of 8 MUST proven | unit 5 | RFC5443-2-3, RFC5443-2-4, RFC5443-2-6 |
| RFC 5286 | Loop-Free Alternate FRR | 2 of 6 MUST proven | unit 2 | RFC5286-x-4, RFC5286-x-5, RFC5286-x-6 |
OAuth 2.0 for management access
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 8707 | Resource Indicators for OAuth 2.0 (MCP resource server) | 0 of 2 MUST proven | - | RFC8707-2-1, RFC8707-2-2, RFC8707-2-6 |
| RFC 8414 | OAuth 2.0 Authorization Server Metadata (MCP resource server) | 9 of 31 MUST proven | unit 9 | RFC8414-2-13, RFC8414-2.1-1, RFC8414-2.1-2 |
| RFC 9728 | OAuth 2.0 Protected Resource Metadata (MCP resource server) | 9 of 26 MUST proven | unit 9 | RFC9728-2-6, RFC9728-2-7, RFC9728-2-8, RFC9728-2.2-1, RFC9728-2.2-2, RFC9728-3.3-4 |
OSPFv2 and OSPFv3
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 2328 | OSPFv2 | 58 of 67 MUST proven | unit 58 | - |
| RFC 3101 | OSPF NSSA | 15 of 28 MUST proven | unit 15 | RFC3101-3.2-3 |
| RFC 5250 | OSPFv2 opaque LSAs | 10 of 15 MUST proven | unit 10 | - |
| RFC 3623 | OSPFv2 Graceful Restart | 8 of 13 MUST proven | unit 8 | RFC3623-3-1, RFC3623-3.1-1, RFC3623-3.2-1, RFC3623-A-1 |
| RFC 3630 | OSPFv2 Traffic Engineering LSA | 0 of 5 MUST proven | - | RFC3630-6-1, RFC3630-6-2, RFC3630-6-3, RFC3630-6-4 |
| RFC 5709 | OSPFv2 HMAC-SHA authentication | 5 of 15 MUST proven | unit 5 | - |
| RFC 7474 | OSPFv2 manual-key security extension | 7 of 12 MUST proven | unit 7 | RFC7474-8-1 |
| RFC 7684 | OSPF Extended Prefix and Link LSAs | 4 of 9 MUST proven | unit 4 | RFC7684-4-1, RFC7684-6.5-1, RFC7684-6.5-2 |
| RFC 4576 | OSPF DN bit for BGP/MPLS IP VPNs | 0 of 4 MUST proven | - | RFC4576-4-1, RFC4576-4-2, RFC4576-4-3, RFC4576-4-4 |
| RFC 4577 | OSPF as the PE/CE protocol for BGP/MPLS IP VPNs | 0 of 46 MUST proven | - | RFC4577-4.1.1-1, RFC4577-4.1.1-2, RFC4577-4.1.1-3, RFC4577-4.1.3-1, RFC4577-4.1.4-1, RFC4577-4.2.1-1, RFC4577-4.2.1-2, RFC4577-4.2.4-1, RFC4577-4.2.4-2, RFC4577-4.2.4-3, RFC4577-4.2.4-4, RFC4577-4.2.4-5, RFC4577-4.2.4-6, RFC4577-4.2.4-7, RFC4577-4.2.4-8, RFC4577-4.2.5.1-1, RFC4577-4.2.5.1-2, RFC4577-4.2.5.1-3, RFC4577-4.2.5.1-4, RFC4577-4.2.5.2-1, RFC4577-4.2.5.2-10, RFC4577-4.2.5.2-2, RFC4577-4.2.5.2-3, RFC4577-4.2.5.2-4, RFC4577-4.2.5.2-5, RFC4577-4.2.5.2-6, RFC4577-4.2.5.2-7, RFC4577-4.2.5.2-8, RFC4577-4.2.5.2-9, RFC4577-4.2.6-1, RFC4577-4.2.6-10, RFC4577-4.2.6-11, RFC4577-4.2.6-12, RFC4577-4.2.6-13, RFC4577-4.2.6-14, RFC4577-4.2.6-15, RFC4577-4.2.6-16, RFC4577-4.2.6-2, RFC4577-4.2.6-3, RFC4577-4.2.6-4, RFC4577-4.2.6-6, RFC4577-4.2.6-7, RFC4577-4.2.6-8, RFC4577-4.2.6-9, RFC4577-4.2.7.1-1, RFC4577-4.2.7.1-2, RFC4577-4.2.7.1-3, RFC4577-4.2.7.1-4, RFC4577-4.2.7.1-5, RFC4577-4.2.7.2-1, RFC4577-4.2.7.3-1, RFC4577-4.2.7.3-2, RFC4577-4.2.7.3-3, RFC4577-4.2.7.3-4, RFC4577-4.2.7.4-1, RFC4577-4.2.7.4-2, RFC4577-4.2.7.4-3, RFC4577-4.2.7.4-4, RFC4577-4.2.8.1-1, RFC4577-4.2.8.1-2, RFC4577-4.2.8.1-3, RFC4577-4.2.8.1-4, RFC4577-4.2.8.1-5 |
| RFC 4552 | OSPFv3 IPsec authentication | 6 of 27 MUST proven | unit 6 | RFC4552-11-4, RFC4552-6-7, RFC4552-9-1, RFC4552-9-2, RFC4552-9-3, RFC4552-9-4 |
| RFC 5340 | OSPFv3 (partial, experimental) | 6 of 23 MUST proven | unit 6 | RFC5340-2.5-2, RFC5340-2.8-2, RFC5340-4.2.2-1, RFC5340-4.9-1, RFC5340-4.9-2 |
| RFC 5187 | OSPFv3 Graceful Restart | 4 of 4 MUST proven | unit 4 | - |
| RFC 5392 | OSPF inter-AS TE (OSPFv2) | 5 of 14 MUST proven | unit 5 | RFC5392-3.1.2-1, RFC5392-3.2.1-2, RFC5392-3.2.1-5, RFC5392-3.3.3-1, RFC5392-3.3.3-2 |
| RFC 5838 | OSPFv3 multiple address families | 4 of 16 MUST proven | unit 4 | RFC5838-2.2-1, RFC5838-2.7-1, RFC5838-2.7-11, RFC5838-2.7-2, RFC5838-2.7-3, RFC5838-2.7-4, RFC5838-2.7-8, RFC5838-4-1, RFC5838-5-3 |
| RFC 7166 | OSPFv3 authentication trailer | 0 of 17 MUST proven | - | RFC7166-2.1-1, RFC7166-3-3, RFC7166-3-6, RFC7166-4.1-2, RFC7166-4.1-3, RFC7166-4.1-4, RFC7166-4.1-5, RFC7166-4.1.1-1, RFC7166-4.2-3, RFC7166-4.2-4, RFC7166-4.3-1, RFC7166-4.3-4, RFC7166-4.4-1, RFC7166-4.6-1, RFC7166-4.6-3, RFC7166-4.6-4, RFC7166-4.6-5, RFC7166-4.6-6, RFC7166-4.6-7 |
| RFC 7770 | OSPF Router Information LSA | 1 of 11 MUST proven | unit 1 | RFC7770-2-1, RFC7770-2.3-1, RFC7770-2.7-1, RFC7770-5.2-1, RFC7770-5.2-2, RFC7770-5.3-1 |
| RFC 8362 | OSPFv3 Extended LSAs | not walked | - | - |
| RFC 8665 | OSPF Segment Routing extensions | 13 of 51 MUST proven | unit 13 | RFC8665-3.1-4, RFC8665-3.1-5, RFC8665-3.2-8, RFC8665-3.4-2, RFC8665-3.4-3, RFC8665-4-1, RFC8665-4-2, RFC8665-4-3, RFC8665-5-8, RFC8665-5-9, RFC8665-7.1-1, RFC8665-7.1-2, RFC8665-7.1-3, RFC8665-7.2-1 |
| RFC 8666 | OSPFv3 Segment Routing | 6 of 32 MUST proven | unit 6 | RFC8666-5-3, RFC8666-5-4, RFC8666-6-10, RFC8666-8.1-1, RFC8666-8.1-2, RFC8666-8.1-3 |
PPP, PPPoE, and L2TP subscriber access
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 1661 | PPP LCP | 35 of 76 MUST proven | interop 4, unit 31 | RFC1661-2-2, RFC1661-3.4-1, RFC1661-3.5-2, RFC1661-3.5-4, RFC1661-3.7-2, RFC1661-4.3-3, RFC1661-4.4-1, RFC1661-5-1, RFC1661-5.3-4, RFC1661-5.7-2, RFC1661-5.9-1, RFC1661-5.9-3, RFC1661-6.5-3 |
| RFC 1570 | PPP LCP extensions | 0 of 22 MUST proven | - | - |
| RFC 1994 | PPP CHAP (MD5) | 6 of 16 MUST proven | unit 6 | RFC1994-2.3-1, RFC1994-4.1-9 |
| RFC 2516 | PPPoE | 24 of 37 MUST proven | unit 24 | RFC2516-3-1, RFC2516-x-11, RFC2516-x-14, RFC2516-x-15 |
| RFC 1332 | IPCP | 6 of 8 MUST proven | unit 6 | - |
| RFC 1334 | PAP | 12 of 13 MUST proven | unit 12 | - |
| RFC 4638 | PPPoE MTU/MRU above 1492 | 0 of 6 MUST proven | - | RFC4638-3-1, RFC4638-4-1, RFC4638-4-2, RFC4638-5.1-2, RFC4638-5.1-3, RFC4638-5.2-2 |
| RFC 1877 | IPCP DNS options | ✕ | - | - |
| RFC 5072 | IPv6CP | 9 of 16 MUST proven | unit 9 | RFC5072-2-2, RFC5072-4.1-10, RFC5072-4.1-11, RFC5072-4.1-8 |
| RFC 2661 | L2TPv2 | 89 of 95 MUST proven | functional 5, unit 84 | RFC2661-4.2-2, RFC2661-9.5-2 |
| RFC 3145 | L2TP PPP disconnect cause | 0 of 8 MUST proven | - | - |
Network primitives other protocols build on
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 905 | Fletcher checksum (ISO Transport Annex B) | 8 of 11 MUST proven | unit 8 | RFC905-13.2.3.1-1, RFC905-6.17.3-1, RFC905-6.17.3-2 |
| RFC 1071 | Internet checksum (OSPF, VRRP, ICMP probe, RSVP-TE) | 6 of 6 MUST proven | unit 6 | - |
| RFC 4787 | NAT behavior for UDP | 0 of 13 MUST proven | - | RFC4787-10-1, RFC4787-10-2, RFC4787-11-1, RFC4787-11-2, RFC4787-4.1-1, RFC4787-4.2.1-1, RFC4787-4.3-1, RFC4787-4.3-2, RFC4787-4.4-1, RFC4787-6-1, RFC4787-6-2, RFC4787-8-1, RFC4787-9-1 |
| RFC 5382 | NAT behavior for TCP | 0 of 11 MUST proven | - | RFC5382-4.1-1, RFC5382-4.2-1, RFC5382-4.2-2, RFC5382-4.3-1, RFC5382-4.3-2, RFC5382-4.3-3, RFC5382-5-1, RFC5382-5-2, RFC5382-7.1-1, RFC5382-7.2-1, RFC5382-7.3-1 |
RADIUS and TACACS+ authentication, authorization, and accounting
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 2865 | RADIUS authentication | 27 of 31 MUST proven | unit 27 | - |
| RFC 2866 | RADIUS accounting | 8 of 15 MUST proven | functional 1, unit 7 | - |
| RFC 2548 | Microsoft vendor-specific RADIUS attributes | 0 of 31 MUST proven | - | - |
| RFC 6911 | RADIUS IPv6 access attributes | 0 of 3 MUST proven | - | - |
| RFC 4818 | RADIUS DHCPv6 prefix delegation | 0 of 3 MUST proven | - | - |
| RFC 2867 | RADIUS tunnel accounting | 0 of 1 MUST proven | - | - |
| RFC 2868 | RADIUS tunnel attributes | 0 of 18 MUST proven | - | - |
| RFC 2869 | RADIUS extensions | 4 of 8 MUST proven | unit 4 | - |
| RFC 3162 | RADIUS IPv6 attributes | 3 of 6 MUST proven | unit 3 | RFC3162-2.3-1, RFC3162-3.2-1, RFC3162-5-1 |
| RFC 3579 | RADIUS/EAP | 17 of 31 MUST proven | unit 17 | RFC3579-1-2, RFC3579-1.2-2, RFC3579-2.1-2, RFC3579-2.2-2, RFC3579-2.6.3-3, RFC3579-2.6.5-1, RFC3579-4.2-1, RFC3579-4.2-2, RFC3579-4.2-3, RFC3579-4.3.4-1, RFC3579-4.3.6-1, RFC3579-4.3.6-3, RFC3579-4.3.6-4, RFC3579-4.3.6-5 |
| RFC 5176 | RADIUS CoA and Disconnect Message | 26 of 30 MUST proven | unit 26 | - |
| RFC 8907 | TACACS+ | 38 of 56 MUST proven | unit 38 | RFC8907-5.4-1, RFC8907-5.4-2, RFC8907-5.4.2.3-1, RFC8907-5.4.2.4-1, RFC8907-5.4.2.5-1, RFC8907-5.4.2.6-1 |
MRT routing information export
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 6396 | MRT | 6 of 13 MUST proven | unit 6 | RFC6396-4.2-1, RFC6396-4.3.4-2, RFC6396-4.4.2-1, RFC6396-4.4.3-1, RFC6396-5.1-1, RFC6396-B.1-1 |
| RFC 6397 | MRT geo-location | 0 of 4 MUST proven | - | RFC6397-4.1-1, RFC6397-4.1-2, RFC6397-4.1-3, RFC6397-6-1 |
| RFC 8050 | MRT ADD-PATH | 5 of 6 MUST proven | unit 5 | RFC8050-4.1-1 |
RPKI, origin validation, and RPKI to router
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 9582 | A Profile for Route Origin Authorizations (ROAs) | 0 of 16 MUST proven | - | - |
| RFC 6811 | RPKI origin validation | 1 of 5 MUST proven | unit 1 | - |
| RFC 6810 | RPKI-to-Router Protocol v0 (RPKI-RTR), not spoken: ze speaks versions 1 and 2 only (RFC 8210) | 0 of 40 MUST proven | - | RFC6810-2-1, RFC6810-3-1, RFC6810-4-1, RFC6810-4-2, RFC6810-5-1, RFC6810-5.1-1, RFC6810-5.1-2, RFC6810-5.1-3, RFC6810-5.10-1, RFC6810-5.10-2, RFC6810-5.10-3, RFC6810-5.10-4, RFC6810-5.5-1, RFC6810-5.6-1, RFC6810-5.8-1, RFC6810-6.1-1, RFC6810-6.3-1, RFC6810-6.4-1, RFC6810-7-1, RFC6810-7-2, RFC6810-7-3, RFC6810-7.1-2, RFC6810-7.2-1, RFC6810-7.2-2, RFC6810-7.2-3, RFC6810-7.2-4, RFC6810-7.2-5, RFC6810-7.2-6, RFC6810-7.2-7, RFC6810-7.2-8, RFC6810-7.3-1, RFC6810-7.3-2, RFC6810-7.4-1, RFC6810-7.4-2, RFC6810-7.4-3, RFC6810-7.4-4, RFC6810-8-1, RFC6810-8-2 |
| RFC 8097 | RPKI origin validation state extended community | 0 of 5 MUST proven | - | RFC8097-2-1, RFC8097-2-2, RFC8097-2-3, RFC8097-2-4, RFC8097-2-5 |
| RFC 8893 | RPKI origin validation on export | 0 of 4 MUST proven | - | RFC8893-1-1, RFC8893-1-2, RFC8893-3-1, RFC8893-3-2 |
| RFC 8210 | RPKI RTR v1 | 12 of 59 MUST proven | unit 12 | RFC8210-2-1, RFC8210-4-2, RFC8210-4-3, RFC8210-5.1-3, RFC8210-5.1-4, RFC8210-5.1-5, RFC8210-5.10-1, RFC8210-5.10-2, RFC8210-5.11-2, RFC8210-5.11-3, RFC8210-5.3-1, RFC8210-5.3-2, RFC8210-5.5-1, RFC8210-5.6-1, RFC8210-5.8-1, RFC8210-7-2, RFC8210-7-4, RFC8210-9-2, RFC8210-9.1-2, RFC8210-9.1-5, RFC8210-9.2-12, RFC8210-9.2-3, RFC8210-9.2-6, RFC8210-9.2-9, RFC8210-9.3-1, RFC8210-9.3-2, RFC8210-9.4-1, RFC8210-9.4-2, RFC8210-9.4-3 |
IP-in-IP, GRE, and IPv6 transition tunnels
| RFC | Area | Proof | Evidence | Unmet |
|---|---|---|---|---|
| RFC 2003 | IP-in-IP tunnels (ipip, protocol 4) | 0 of 13 MUST proven | - | RFC2003-3.1-1, RFC2003-3.1-2, RFC2003-3.1-3, RFC2003-3.2-1, RFC2003-3.2-2, RFC2003-4.1-1, RFC2003-4.1-2, RFC2003-4.1-3, RFC2003-4.1-4, RFC2003-4.3-1, RFC2003-4.4-1, RFC2003-4.5-1, RFC2003-5.1-1 |
| RFC 2784 | GRE tunnels (gre, gretap) | 0 of 11 MUST proven | - | RFC2784-2.2-1, RFC2784-2.3-1, RFC2784-2.3-2, RFC2784-2.3-3, RFC2784-2.3.1-1, RFC2784-2.6-1, RFC2784-3-1, RFC2784-3.1-1, RFC2784-3.1-2, RFC2784-3.1-3, RFC2784-5.2-1 |
| RFC 4213 | IPv6 over IPv4 configured tunnels (6in4, sit) | 1 of 23 MUST proven | unit 1 | RFC4213-2.2-1, RFC4213-2.2-2, RFC4213-3.2.1-1, RFC4213-3.2.1-2, RFC4213-3.6-5 |
| RFC 2473 | IPv6 tunnels (ip6tnl, ipip6) | 1 of 11 MUST proven | unit 1 | RFC2473-7.1-1, RFC2473-7.1-2, RFC2473-7.1-4 |
| RFC 2890 | GRE key and sequence number extensions | 0 of 3 MUST proven | - | RFC2890-2.2-3, RFC2890-2.2-4, RFC2890-3-1 |