Actions
Design Elements » History » Revision 13
« Previous |
Revision 13/19
(diff)
| Next »
Suravi Regmi, 11/25/2025 05:39 PM
Design Elements¶
This is the technical reference section.
Naming Scheme¶
- Stream naming hierarchy mGuard
- Manifest naming
- NAC-ABE naming scheme
Trust Model¶
- Signing chain
- Trust anchor
- Component identities
Access Control + Policy Structure¶
New policy structure (requester, allow/deny filters)
Example policy with evolution from old → new format
Filter semantics
Mapping to attributes
NAC-ABE Design¶
- NAC-ABE in mGuard
- KP-ABE
- ABE Encryption of CK
- CK
- End to End Flow
Manifest Design¶
- Manifest
- Manifest Format
- Processing Rules
PSync Design¶
Why PSync is used
How the sync list works conceptually
Manifest announcement via PSync
Differences from classical pub-sub
Limitations / assumptions
Boundaries (MGuard-specific usage, not raw PSync theory)
Pub-Sub API Design (MGuard Perspective)¶
Producer API: publish()
Consumer API: subscribe()
Callback delivery
Reliability guarantees
Repo¶
NDN-Python Repo and its ussage in MGuard
Updated by Suravi Regmi 20 days ago · 19 revisions