Design Elements » History » Version 19
Suravi Regmi, 11/25/2025 09:09 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 | 14 | Suravi Regmi | * Access Control Flow |
| 19 | * Policy Structure |
||
| 20 | 1 | Suravi Regmi | |
| 21 | |||
| 22 | 7 | Suravi Regmi | ### **[[NAC-ABE Design|NAC-ABE Design]]** |
| 23 | 1 | Suravi Regmi | |
| 24 | 12 | Suravi Regmi | * NAC-ABE in mGuard |
| 25 | * KP-ABE |
||
| 26 | * ABE Encryption of CK |
||
| 27 | * CK |
||
| 28 | * End to End Flow |
||
| 29 | 1 | Suravi Regmi | |
| 30 | 7 | Suravi Regmi | ### **[[Manifest Design|Manifest Design]]** |
| 31 | 1 | Suravi Regmi | |
| 32 | 13 | Suravi Regmi | * Manifest |
| 33 | * Manifest Format |
||
| 34 | * Processing Rules |
||
| 35 | 1 | Suravi Regmi | |
| 36 | 7 | Suravi Regmi | ### **[[PSync Design|PSync Design]]** |
| 37 | 2 | Suravi Regmi | |
| 38 | 19 | Suravi Regmi | * Old Psync Implemetation |
| 39 | * New PSync Implementation |
||
| 40 | * Why PSync is used |
||
| 41 | 1 | Suravi Regmi | |
| 42 | 7 | Suravi Regmi | ### **[[Pub-Sub API|Pub-Sub API Design (MGuard Perspective)]]** |
| 43 | 15 | Suravi Regmi | * pubsub |
| 44 | 8 | Suravi Regmi | |
| 45 | ### **[[Repo|Repo]]** |
||
| 46 | 17 | Suravi Regmi | * NDN-Python Repo and its usage in MGuard |