Skip to content

chore: non-normative edits for embedded PDP reference architecture#15

Open
beonde wants to merge 2 commits intomainfrom
chore/embedded-pdp-non-normative
Open

chore: non-normative edits for embedded PDP reference architecture#15
beonde wants to merge 2 commits intomainfrom
chore/embedded-pdp-non-normative

Conversation

@beonde
Copy link
Member

@beonde beonde commented Mar 21, 2026

Summary

Non-normative RFC edits supporting the embedded PDP reference architecture. All changes are informational — no normative requirements modified.

RFC-005 v1.1 Changes

§4.2 Implementation Note

Clarifies that bundle-based PDP internals (e.g., OPA policy bundles loaded from a co-located bundle server) are a valid implementation detail, invisible to the PEP at the wire contract level.

§6.3 Bundle vs Decision Caching

Distinguishes decision-level caching (storing a specific evaluation result) from bundle-level caching (evaluating fresh decisions against cached policy data). Both are valid. Bundle-level caching does not violate the temporal bounds in §6.3 because each evaluation produces a new decision.

Appendix B: Reference PDP Architecture (Non-Normative)

Documents the reference PDP shipped with capiscio-server:

  • B.1: Architecture (embedded OPA evaluator via PDPClient interface)
  • B.2: PIP-to-OPA input mapping (1:1 from §5 attributes to OPA input document)
  • B.3: Bundle structure (policy rules + live registry data payload)
  • B.4: Bundle staleness behavior per enforcement mode
  • B.5: Starter policies (trust level, DID lists, route-scoped access, rate limits)

Changelog

Added v1.1 entry.

RFC-001 Change

§6 Co-Located PDP Note

Non-normative note that embedding the PDP within the PEP process is a valid deployment variant, with a cross-reference to RFC-005 Appendix B.

Related

  • Architecture decision: 2026-03-21
  • Implementation guide: internal-docs/engineering/embedded-pdp-implementation-guide.md

beonde added 2 commits March 21, 2026 00:26
RFC-005 v1.1:
- §4.2: Implementation note clarifying bundle-based PDP internals are valid
- §6.3: Note distinguishing bundle-level caching from decision-level caching
- Appendix B: Reference PDP architecture (OPA embed, PIP-to-OPA mapping,
  bundle structure, staleness behavior, starter policies) — non-normative

RFC-001:
- §6: Co-located PDP deployment note — non-normative

All changes are informational. No normative requirements modified.
Resolve the deployment-specific placeholder in Appendix B §B.4.
EM-GUARD allows on stale bundle with BUNDLE_STALE telemetry warning,
consistent with its deny-on-DENY contract. EM-STRICT remains the
fail-closed option. Added rationale paragraph.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant