OpenPacketCore SDK RFC Index

This directory contains the foundational RFCs for the OpenPacketCore SDK and CNF architecture. These documents are intended to be implementation inputs for engineers.

Foundation Set

RFCTitlePrimary Scope
001Transactional Management SubstrateConfig commits, persistence, recovery, NACM boundary
002YANG-to-Rust ProjectionCodegen, RFC 7951, validation, memory layout
003Security SubstrateSPIFFE, gNSI, tenant identity, keys, audit
004High-Performance Session StoreSession state, leases, fencing, handover, geo-redundancy
005Zero-Copy Protocol FrameworkParsers, codecs, lifetimes, fuzzing, spec tags
006Conformance and Evidence PipelineSBOM, VEX, provenance, signing, known gaps
007SBI Service FrameworkTS 29.500/29.510, NRF, OAuth2, overload, retries
008CNF Runtime ChassisStartup, supervision, shutdown, health, resource budgets
009Operator Lifecycle and UpgradeCRDs, rollout, migration, drain, rollback
010Data Governance and PrivacyData classes, redaction, retention, LI, regulated records
011Node and Data-Plane Resource ContractSR-IOV, Multus, AF_XDP, CPU, NUMA, pod security
012Testbed and Simulator FrameworkScenario DSL, simulators, fixtures, virtual time
013Fault Management and Alarm SubstrateAlarms, severity, probable cause, FM sinks
014Interactive Operational Console and Command FrameworkCNF command catalogs, human login, typed operations, first-class TUI
015Live SA Keymat MirrorKeys-never-persist failover, standby custody, mTLS keymat transport, re-pin composition
016Opaque Durable GTP-U Selector NamespaceExperimental durable whole-group selector authority, affine admissions, tombstones, eBPF control binding
017Mixed Selector Provenance and Loss-Qualified RestoreExperimental mixed per-atom provenance and marker-retaining namespace restore under RFC 016's ledger
018Never-Admitted Selector Namespace RelocationExplicit relocation under positive permanent no-admission proof; excludes all prior session history
019NETCONF Required Audit for Exact Configuration EffectsExact-worker writable-running handoff; candidate, startup and confirmed lifecycle obligations remain open

Contracts with separate implementation qualification

RFCTitleStatus and scope
020Authority-owned online audit recipient verificationAcceptance is recorded by maintainer-approved merge of #979; implementation qualification remains separate. Online recipient custody, authenticated application boundary and checkpoint/report semantics for #959.
022Scope authority and atomic child batches, profile 4Experimental untimed execution fencing, stable-scope floors and activation continuity; transport, local effects and lost-worker retirement have separate qualification.
024Scope work priorities and backpressureImplemented class isolation, shared-lane arbitration and class-aware proposal admission; composed lane and authenticated transport qualification remain separate.
025Exact Local Kernel LifecycleAccepted design for untimed local discovery, transient containment, exact reset/readback and supervised undo; implementation qualification remains separate.
026Authenticated scope and voter management transportWorker scope admission and batch recovery with normative bootstrap, closure and wire vectors; voter management follows RFC 023 helpers. Runtime qualification remains separate.
026 addendumBounded authenticated worker child readsImplemented revision 2, one-cut reads of 1–32 keys, builder admission and native kernel-authority readback; runtime qualification remains separate.
030IKE recovery profile and lifecycle qualificationImplemented SDK contract and deterministic reference composition for CAS, replay, handshake/rekey and pending-KE custody; consumer infrastructure and deployment qualification remain separate.
031Bounded S-NAPTR peer discoveryImplemented bounded host prefixes, branch provenance, root classification and DNS freshness; code review and qualification pending.

  1. RFC 008: runtime chassis.

  2. RFC 003: security substrate.

  3. RFC 001: management substrate.

  4. RFC 002: YANG projection.

  5. RFC 007: SBI framework.

  6. RFC 004: session store.

  7. RFC 015: live SA keymat mirror.

  8. RFC 005: protocol framework.

  9. RFC 009: operator lifecycle.

  10. RFC 010: data governance.

  11. RFC 011: node/data-plane resources.

  12. RFC 013: fault management.

  13. RFC 014: interactive operational console.

  14. RFC 012: testbed framework.

  15. RFC 006: evidence pipeline.

  16. RFC 016: opaque durable GTP-U selector namespace (after RFC 004, RFC 006, RFC 011, ADR 0018, and ADR 0019).

  17. RFC 017: mixed selector provenance and loss-qualified restore (after RFC 016).

  18. RFC 018: never-admitted selector namespace relocation (after RFC 016 and RFC 017's scope boundaries).

  19. RFC 019: NETCONF exact-effect required audit (after RFC 001, RFC 003 and ADR 0025).

RFC 006 should be revisited after each implementation slice because it defines the evidence required to claim that the slice is complete.