Design Elements » History » Version 6
Suravi Regmi, 11/21/2025 07:39 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 | Stream naming hierarchy (include diagram from paper) |
| 6 | Data naming: |
||
| 7 | /org/md2k/.../DATA/<timestamp> |
||
| 8 | |||
| 9 | Attribute names (/org/md2k/ATTRIBUTE/...) |
||
| 10 | |||
| 11 | Manifest naming (.../MANIFEST/<seq>) |
||
| 12 | |||
| 13 | CK naming conventions |
||
| 14 | |||
| 15 | DKEY naming conventions |
||
| 16 | |||
| 17 | PUBPARAMS naming |
||
| 18 | |||
| 19 | 5 | Suravi Regmi | ### **[[Trust Model|Trust Model]]** |
| 20 | 1 | Suravi Regmi | |
| 21 | Trust anchor |
||
| 22 | |||
| 23 | Component identities |
||
| 24 | |||
| 25 | Cert verification |
||
| 26 | |||
| 27 | Signing chain |
||
| 28 | |||
| 29 | What each module verifies |
||
| 30 | |||
| 31 | 6 | Suravi Regmi | ### **[[Access Control|Access Control + Policy Structure]]** |
| 32 | 1 | Suravi Regmi | |
| 33 | New policy structure (requester, allow/deny filters) |
||
| 34 | |||
| 35 | Example policy with evolution from old → new format |
||
| 36 | |||
| 37 | Filter semantics |
||
| 38 | |||
| 39 | Mapping to attributes |
||
| 40 | |||
| 41 | 2 | Suravi Regmi | ### NAC-ABE Design |
| 42 | 1 | Suravi Regmi | |
| 43 | Why KP-ABE |
||
| 44 | |||
| 45 | Data encryption → CK encryption → CK decryption |
||
| 46 | |||
| 47 | ABE encryption of CK (black box) |
||
| 48 | |||
| 49 | ABE key issuance (DKEY) |
||
| 50 | |||
| 51 | CK granularity (second/minute/hour) |
||
| 52 | |||
| 53 | Tradeoffs of CK reuse level |
||
| 54 | |||
| 55 | 2 | Suravi Regmi | ### Manifest Design |
| 56 | 1 | Suravi Regmi | |
| 57 | Why manifests exist |
||
| 58 | |||
| 59 | Manifest format (full data names + digest) |
||
| 60 | |||
| 61 | Creation triggers: count/time threshold |
||
| 62 | |||
| 63 | Sequential numbering scheme |
||
| 64 | |||
| 65 | How manifests replace per-data sync announcements |
||
| 66 | |||
| 67 | 2 | Suravi Regmi | ### PSync Design |
| 68 | 1 | Suravi Regmi | |
| 69 | Why PSync is used |
||
| 70 | |||
| 71 | How the sync list works conceptually |
||
| 72 | |||
| 73 | Manifest announcement via PSync |
||
| 74 | |||
| 75 | Differences from classical pub-sub |
||
| 76 | |||
| 77 | Limitations / assumptions |
||
| 78 | |||
| 79 | Boundaries (MGuard-specific usage, not raw PSync theory) |
||
| 80 | |||
| 81 | ### Pub-Sub API Design (MGuard Perspective) |
||
| 82 | |||
| 83 | Producer API: publish() |
||
| 84 | |||
| 85 | Consumer API: subscribe() |
||
| 86 | |||
| 87 | Callback delivery |
||
| 88 | |||
| 89 | Reliability guarantees |