9 | | To date, five end-user opt-in use cases have been identified: |
10 | | |
11 | | • Use Case 1: User opt-in to GENI experiment for service |
12 | | • Use Case 2: Wholesale opt-in to GENI of traffic |
13 | | • Use Case 3: A disruptive GENI experiment |
14 | | • Use Case 4: Opt-in of user resources to a GENI experiment |
15 | | • Use Case 5: Gathering data involving opt-in users in a GENI experiment |
16 | | |
17 | | These use cases then drive requirements on capabilities that are being included into GENI, including: |
18 | | |
19 | | • Capability 1: Gateway from GENI to another network, e.g., the Internet |
20 | | • Capability 2: Contribution (or association) of a user’s node to an experiment on GENI |
21 | | • Capability 3: Gathering logs and experiment data on GENI (some possibly user-identifiable) and managing their distribution |
22 | | |
23 | | Finally, we expect various common policy themes to arise from an examination of the policies and best practices required for each use case, such as: |
24 | | |
25 | | • Privacy policies for end-users |
26 | | • Disclosure policies |
27 | | |
28 | | |
29 | | |
30 | | For each use case, we want to better understand and write down: |
31 | | the players, their motivation and relationships; |
32 | | major issues (incentives, risks to consider, etc.) |
33 | | and a first cut at policies and best practices when operating in a GENI environment. |
34 | | |
35 | | |
36 | | We want to finish this meeting with a better understanding, and a few pages of text for each use case. Then, we hope to have a baseline view of GENI opt-in that can be expanded in the coming months. |
| 9 | We want to finish this meeting with a better understanding, and a baseline view of GENI opt-in that can be expanded in the coming months. |