Design Elements » History » Version 12
Suravi Regmi, 11/25/2025 05:32 PM
| 1 | 1 | Suravi Regmi | # Design Elements |
|---|---|---|---|
| 2 | This is the technical reference section. |
||
| 3 | 4 | Suravi Regmi | |
| 4 | ### **[[Naming_Scheme|Naming Scheme]]** |
||
| 5 | 1 | Suravi Regmi | |
| 6 | 11 | Suravi Regmi | * Stream naming hierarchy mGuard |
| 7 | * Manifest naming |
||
| 8 | * NAC-ABE naming scheme |
||
| 9 | 1 | Suravi Regmi | |
| 10 | |||
| 11 | ### **[[Trust Model|Trust Model]]** |
||
| 12 | |||
| 13 | 11 | Suravi Regmi | * Signing chain |
| 14 | * Trust anchor |
||
| 15 | * Component identities |
||
| 16 | 1 | Suravi Regmi | |
| 17 | 6 | Suravi Regmi | ### **[[Access Control|Access Control + Policy Structure]]** |
| 18 | 1 | Suravi Regmi | |
| 19 | New policy structure (requester, allow/deny filters) |
||
| 20 | |||
| 21 | Example policy with evolution from old → new format |
||
| 22 | |||
| 23 | Filter semantics |
||
| 24 | |||
| 25 | Mapping to attributes |
||
| 26 | |||
| 27 | 7 | Suravi Regmi | ### **[[NAC-ABE Design|NAC-ABE Design]]** |
| 28 | 1 | Suravi Regmi | |
| 29 | 12 | Suravi Regmi | * NAC-ABE in mGuard |
| 30 | * KP-ABE |
||
| 31 | * ABE Encryption of CK |
||
| 32 | * CK |
||
| 33 | * End to End Flow |
||
| 34 | 1 | Suravi Regmi | |
| 35 | 7 | Suravi Regmi | ### **[[Manifest Design|Manifest Design]]** |
| 36 | 1 | Suravi Regmi | |
| 37 | Why manifests exist |
||
| 38 | |||
| 39 | Manifest format (full data names + digest) |
||
| 40 | |||
| 41 | Creation triggers: count/time threshold |
||
| 42 | |||
| 43 | Sequential numbering scheme |
||
| 44 | |||
| 45 | How manifests replace per-data sync announcements |
||
| 46 | 7 | Suravi Regmi | ### **[[PSync Design|PSync Design]]** |
| 47 | 2 | Suravi Regmi | |
| 48 | 1 | Suravi Regmi | |
| 49 | Why PSync is used |
||
| 50 | |||
| 51 | How the sync list works conceptually |
||
| 52 | |||
| 53 | Manifest announcement via PSync |
||
| 54 | |||
| 55 | Differences from classical pub-sub |
||
| 56 | |||
| 57 | Limitations / assumptions |
||
| 58 | |||
| 59 | Boundaries (MGuard-specific usage, not raw PSync theory) |
||
| 60 | 7 | Suravi Regmi | ### **[[Pub-Sub API|Pub-Sub API Design (MGuard Perspective)]]** |
| 61 | 1 | Suravi Regmi | |
| 62 | |||
| 63 | Producer API: publish() |
||
| 64 | |||
| 65 | Consumer API: subscribe() |
||
| 66 | |||
| 67 | Callback delivery |
||
| 68 | |||
| 69 | Reliability guarantees |
||
| 70 | 8 | Suravi Regmi | |
| 71 | ### **[[Repo|Repo]]** |
||
| 72 | NDN-Python Repo and its ussage in MGuard |