Nabble - GENI End-user Opt-in WG

Re: GEC#2 hotel & registration

2009-09-03T01:53:15Z

Aaron Falk wrote:

GENI Engineering Conference #2
------------------------------

This is a reminder that the GPO is holding a block of rooms the nights
of March 2nd and 3rd at $201/night at the Westin Arlington Gateway for
GEC attendees. (For comparison: The best Westin advertised rate for
those nights is $379.) The block is reserved under the label "GENI
Conference". Reservations must be made before ***February 15th*** to
get this rate.

wonderful! thanks for the info..

[url=http://simulationcreditauto.org][color=#FFFFFF][u] simulation credit auto comparatif voiture taux pret automobile [/u][/color][/url][color=#FFFFFF]financiers ont mis à la disposition des particuliers la simulation crédit auto[/color][url=http://simulationcreditauto.org][color=#FFFFFF][u] simulation credit auto comparatif voiture taux pret automobile [/u][/color][/url]

Westin Arlington Gateway:
http://www.starwoodhotels.com/westin/property/overview/index.html?propertyID=1513

Also, don't forget to pre-register for the GEC conference itself.
***There will be no onsite registration.***

GEC#2 registration:
https://www.regonline.com/gec2

GEC#2 logistics and agenda:
http://www.geni.net/GEC2/GEC2.html

--aaron

_______________________________________________
opt-in-wg mailing list
opt-in-wg@geni.net
http://lists.geni.net/mailman/listinfo/opt-in-wg

DRAFT agenda for End-User Opt-In WG meering at GEC5

2009-07-13T12:48:54Z

GENI Opt-In WG Members, and interested GENI participants,

GEC5 will be held in Seattle:
From Monday 7/20 1pm, through Wednesday 7/22 12:30pm.

The Opt-In Working Group will meet:
Tuesday 7/21 3:30pm - 5:30pm

The DRAFT agenda includes:

Review and discussion of GENI opt-in scenarios, with emphasis on
Spiral 1.
(organized by Justin Cappos and Harry Mussman)

Discussion and review of GENI structure of agreements and policies,
including DRAFT document
Harry Mussman

Review of WG meeting in NYC, including various key issues and DRAFT
overview document.
Henning Schulzrinne, Opt-In WG Co-Chair

Introduction of new co-chair(s), effective GEC6
Henning Schulzrinne

Wrapup and review of action items
Harry Mussman

Are there other topics you would like to see discussed?

We hope to see you all in Seattle!
(I would appreciate your email indicating that you will attend this
Opt-In WG meeting - we would like to get a count.)

Sincerely,

Harry E. Mussman
End-User Opt-In Systems Engineer

GENI Project Office
BBN Technologies
10 Moulton Street
Cambridge, MA 02138
(617) 873-4282 - Office
(781) 266-8479 - Mobile
(617) 873-4888 - Fax
hmussman@...
www.bbn.com

_______________________________________________
opt-in-wg mailing list
opt-in-wg@...
http://lists.geni.net/mailman/listinfo/opt-in-wg

Opt-In WG agenda (preliminary) for GEC4

2009-03-13T15:18:30Z

GENI Opt-In WG Members, and interested GENI participants,

GEC4 will be held in Miami:

From Tuesday 3/31 1pm, through Thursday 4/2 12:30pm.

The Opt-In Working Group will meet:

Thursday 4/2 9am - 11am

The preliminary agenda includes:

Requirements for Wholesale Opt-In Matt Mathis
A reference for this work and the document can be found at
http://groups.geni.net/geni/wiki/OptInReqs

Starting up Million-Node GENI Justin Cappos

Review and discussion of key GENI opt-in scenarios and capabilities,
with emphasis on Spirals 1 and 2 Organized by Harry Mussman,
Opt-In WG SE

Wrapup and review of action items Harry Mussman, CF WG SE

Are there other topics you would like to see discussed?

We hope to see you all in Miami!
(I would appreciate your email indicating that you will attend this
Opt-In WG meeting - we would like to get a count.)

Sincerely,

Harry E. Mussman
User Opt-In Systems Engineer

GENI Project Office
BBN Technologies
10 Moulton Street
Cambridge, MA 02138
(617) 873-4282 - Office
(781) 266-8479 - Mobile
(617) 873-4888 - Fax
hmussman@...
www.bbn.com

_______________________________________________
opt-in-wg mailing list
opt-in-wg@...
http://lists.geni.net/mailman/listinfo/opt-in-wg

Re: Opt-In document posted

2009-02-24T12:34:58Z

Oops, I had to move the document to it's own page:
http://groups.geni.net/geni/wiki/OptInReqs

On Tue, 24 Feb 2009, Matt Mathis wrote:

> I just posted "Requirements for Wholesale Opt-In" at
> http://groups.geni.net/geni/attachment/wiki/RegionalOptIn/OptInReqs.pdf
>
> Abstract:
>
> This document outlines requirements for a strong wholesale opt-in mechanism
> for GENI. When fully deployed it would permit GENI experimenters to request
> that ISPs redirect traffic from a huge population of innocent users through
> GENI infrastructure. These users are innocent in the sense that they do not
> have to do anything at all to participate, and might not even be aware that
> they are doing so. Key to wholesale opt-in is that it fully engages the
> Institutional Review Board (IRB) process and that all participants are
> motivated by their own self interests to do the right thing. It does not
> require ``selling'' GENI to application developers or anybody other than
> network researchers.
>
> Since the ISPs bear a disproportionate share of the risk with this technique,
> the ISPs are granted additional controls, implemented in an ``ISP Daemon''
> that serve to isolate the ISPs' critical core routers from GENI.
>
> When this approach is fully mature we expect it to be sufficiently robust
> where NSF might include GENI opt-in language in research solicitations across
> the entire foundation. This could bring as much traffic to GENI as is
> currently carried in aggregate by all of today's production research and
> education backbones.
>
> --
> I consider this document to still open for additions and improvements.
> Comments welcome. Ideally it would include input from the entire OptIn WG.
>
> This is one of my deliverables: can somebody clue me into all the
> places that this should be posted?
>
> Thanks,
> --MM--
> -------------------------------------------
> Matt Mathis http://staff.psc.edu/mathis
> Work:412.268.3319 Home/Cell:412.654.7529
> -------------------------------------------
> Evil is defined by mortals who think they know
> "The Truth" and use force to apply it to others.
>
> _______________________________________________
> opt-in-wg mailing list
> opt-in-wg@...
> http://lists.geni.net/mailman/listinfo/opt-in-wg
>

_______________________________________________
opt-in-wg mailing list
opt-in-wg@...
http://lists.geni.net/mailman/listinfo/opt-in-wg

Re: Opt-In document posted

2009-02-24T12:33:15Z

On Feb 24, 2009, at 2:56 PM, Matt Mathis wrote:

> I just posted "Requirements for Wholesale Opt-In" at
> http://groups.geni.net/geni/attachment/wiki/RegionalOptIn/
> OptInReqs.pdf
>
> Abstract:
>
> This document outlines requirements for a strong wholesale opt-in
> mechanism
> for GENI. When fully deployed it would permit GENI experimenters to
> request
> that ISPs redirect traffic from a huge population of innocent users
> through
> GENI infrastructure. These users are innocent in the sense that
> they do not
> have to do anything at all to participate, and might not even be
> aware that
> they are doing so. Key to wholesale opt-in is that it fully engages
> the
> Institutional Review Board (IRB) process and that all participants are
> motivated by their own self interests to do the right thing. It
> does not
> require ``selling'' GENI to application developers or anybody other
> than
> network researchers.
>
> Since the ISPs bear a disproportionate share of the risk with this
> technique,
> the ISPs are granted additional controls, implemented in an ``ISP
> Daemon''
> that serve to isolate the ISPs' critical core routers from GENI.
>
> When this approach is fully mature we expect it to be sufficiently
> robust
> where NSF might include GENI opt-in language in research
> solicitations across
> the entire foundation. This could bring as much traffic to GENI as is
> currently carried in aggregate by all of today's production research
> and
> education backbones.
>
> --
> I consider this document to still open for additions and improvements.
> Comments welcome. Ideally it would include input from the entire
> OptIn WG.
>
> This is one of my deliverables: can somebody clue me into all the
> places that this should be posted?

I think cross-posting to omis-wg would be a good idea, especially
since there are folks with ISP experience there.

>
>
> Thanks,
> --MM--
> -------------------------------------------
> Matt Mathis http://staff.psc.edu/mathis
> Work:412.268.3319 Home/Cell:412.654.7529
> -------------------------------------------
> Evil is defined by mortals who think they know
> "The Truth" and use force to apply it to others.
>
> _______________________________________________
> opt-in-wg mailing list
> opt-in-wg@...
> http://lists.geni.net/mailman/listinfo/opt-in-wg

_______________________________________________
opt-in-wg mailing list
opt-in-wg@...
http://lists.geni.net/mailman/listinfo/opt-in-wg

Opt-In document posted

2009-02-24T11:56:48Z

I just posted "Requirements for Wholesale Opt-In" at
http://groups.geni.net/geni/attachment/wiki/RegionalOptIn/OptInReqs.pdf

Abstract:

This document outlines requirements for a strong wholesale opt-in mechanism
for GENI. When fully deployed it would permit GENI experimenters to request
that ISPs redirect traffic from a huge population of innocent users through
GENI infrastructure. These users are innocent in the sense that they do not
have to do anything at all to participate, and might not even be aware that
they are doing so. Key to wholesale opt-in is that it fully engages the
Institutional Review Board (IRB) process and that all participants are
motivated by their own self interests to do the right thing. It does not
require ``selling'' GENI to application developers or anybody other than
network researchers.

Since the ISPs bear a disproportionate share of the risk with this technique,
the ISPs are granted additional controls, implemented in an ``ISP Daemon''
that serve to isolate the ISPs' critical core routers from GENI.

When this approach is fully mature we expect it to be sufficiently robust
where NSF might include GENI opt-in language in research solicitations across
the entire foundation. This could bring as much traffic to GENI as is
currently carried in aggregate by all of today's production research and
education backbones.

--
I consider this document to still open for additions and improvements.
Comments welcome. Ideally it would include input from the entire OptIn WG.

This is one of my deliverables: can somebody clue me into all the
places that this should be posted?

Thanks,
--MM--
-------------------------------------------
Matt Mathis http://staff.psc.edu/mathis
Work:412.268.3319 Home/Cell:412.654.7529
-------------------------------------------
Evil is defined by mortals who think they know
"The Truth" and use force to apply it to others.

_______________________________________________
opt-in-wg mailing list
opt-in-wg@...
http://lists.geni.net/mailman/listinfo/opt-in-wg

Minutes from GENI Opt-in WG Meeting at GEC-3 on 10/29/08

2008-11-21T10:37:45Z

All members of the Opt-in WG,

The Opt-in WG met at GEC-3 on 10/29/08.

The overall agenda of GEC3 can be found at:
http://www.geni.net/GEC3/GEC3-Agenda.pdf

All talks presented at GEC3 can be found at:
http://groups.geni.net/geni/wiki/presentations

All Opt-in WG meeting presentations can be found at:
http://groups.geni.net/geni/wiki/OptInWGGEC3

DRAFT minutes of the Opt-in WG meeting are at
http://groups.geni.net/geni/attachment/wiki/OptInWGGEC3/110408c%20%20GEC3_Op
tInWG_Minutes.pdf
and are attached below. Please forward any changes or additions to me.

One action item was identified at the meeting:
Agreed: WG should consider producing: "Best practices for involving an
Institutional Review Board when starting a GENI networking experiment". How
can we get this started?

Please use this mailing list to continue discussions from the meeting, or to
start new threads. And, please encourage your colleagues to join the
mailing list!

Best wishes,

Harry

Harry E. Mussman
Sr. Systems Engineer - GENI Project Office
BBN Technologies
10 Moulton Street
Cambridge, MA 02138
(617) 873-4282 - Office
(781) 266-8479 - Mobile
(617) 873-4888 - Fax
hmussman@...
www.bbn.com

________________________________________________________________________
3rd GENI Engineering Conference
Opt-In Working Group Meeting Minutes

Prepared by Opt-In Systems Engineer:
Harry Mussman at GENI Project Office hmussman@...,
November 4, 2008
________________________________________________
Content:
The agenda for the conference can be found at:
http://www.geni.net/GEC3/GEC3-Agenda.pdf

All slides from the conference can be found at:
http://groups.geni.net/geni/wiki/presentations

On the first day of the conference, there were two talks in plenary session
that summarized NSF-sponsored workshops, including one on the "User Opt-In
Workshop". Notes on this workshop are presented first in this report.

Then, on the second day of the conference, the Opt-In WG met. It heard one
short "lightning" talk, three related Spiral 1 project talks, the system
engineering report, and had a period of open discussion. Notes from this
meeting conclude this report.

One action item was identified:
Agree: WG should consider producing: "Best practices for involving an
Institutional Review Board when starting a GENI networking experiment". How
can we get this started?

_______________________________________________________________________
Plenary Session: Workshop Reports
Tuesday, October 28, 4:15pm - 5pm.
Building 20 Auditorium, Hewlett Packard, Palo Alto, CA
For an audio recording of this session, go to: TBD

________________________________________________
"Report from the GENI User Opt-IN Workshop"
Speaker and workshop chair: GENI Outreach Director Craig Partridge at GENI
Project Office craig@...
Slides:
http://groups.geni.net/geni/attachment/wiki/presentations/Partridge-Opt-In-W
orkshop-v1.0.ppt
Related workshop report at: TBD

This talk reviewed a one-day workshop (held on July 22, 2008 in Cambridge,
MA) that was structured to solicit ideas from experts interested in
technology, and its impact on society. Conclusions include: the way to
users is (mostly) through getting great applications into GENI slices.
Thus, we need to think about how to ensure GENI is application-friendly.

________________________________________________________________________
Opt-In Working Group Breakout Session
Wednesday, October 29, 2pm - 5pm.
Bldg 5M Spyglass Auditorium, Hewlett Packard, Palo Alto, CA
For an audio recording of this session, go to: TBD

________________________________________________
1) WG Co-Chair: Henning Schulzrinne at Columbia hgs@...
Review of agenda
Introductions
(Note: WG Co-Chair Helen Nissenbaum was unable to attend.)

________________________________________________
2) "Lightning talk" relevant to WG. (Invited by WG Chairs)

a) "PlanetLab Policies: Learning on the Job"
Speaker: Larry Peterson at Princeton llp@...
Slides:
http://groups.geni.net/geni/attachment/wiki/presentations/OptIn%20WG%20%202a
%20%20llp_policy.ppt

This talk summarized PlanetLab experience, starting with the actors and how
experiments lead to complaints. It ended with a review of suggested
policies and advice.

Here is a summary of the slides:

. PlanetLab Policies:
Learning on the Job
. Acronym Soup
. CALEA
. CFAA
. CMA
. DMCA
. ECPA
. SCA
. Acronym Soup
. CALEA
. Communication Assistance for Law Enforcement Act
. CFAA
. Computer Fraud & Abuse Act
. CMA
. Computer Misuse Act (UK)
. DMCA
. Digital Millennium Copyright Act
. ECPA
. Electronic Communications Protection Act
. SCA
. Stored Communications Act
. Actors
. PlanetLab Central
. testbed operator / trusted intermediary
. Hosting Sites
. Researchers
. Third Parties
. end-users
. content providers
. attackers
. ISPs
. Experiments Complaints
. Measurement Studies
. network probes
. application probes
. edge probes
. Deployment Studies
. opt-in strategy
. privacy
. abusing services
. bandwidth shifting
. financial gain
. Policies/Advice
. Do not police content
. DMCA is relevant
. Prefer opt-out to opt-in
. IRB oversight (of human studies) not required
. Protect privacy of log files
. ECPA & SCA are relevant
. Research is distinctive
. CALEA is not relevant
. Adhere to best practices
. avoid random probes (CMA - UK)
. prevent service abuse (CFAA)

Questions from the audience:
Q: What should you do if asked to capture more per CALEA?
A: Argue that it is not appropriate, or shut down the experiment.

Q: (Craig Partridge) we need to protect privacy of log files; is there a
way to make them publically accessible?
A: Keep them private, or modify data to be anonymous.

Q: What does opt-out mean?
A: Make sure that you are not included or touched by the experiment.

Comment: Matt at Internet2: We are looking at a process for releasing
data.

Q: (Heidi Dempsey) what are EU requirements? The need to be able to delete
their own records? Do you do it?
A: Not yet.

________________________________________________
3) Talks by related Spiral 1 projects:

________________________________________________
a) "Seattle: Building a Million-Node Testbed".
PIs: Thomas Anderson and Arvind Krishnamurthy at the University of
Washington - Seattle
Speaker: Thomas Anderson at the University of Washington - Seattle
Slides:
http://groups.geni.net/geni/attachment/wiki/presentations/OptIn%20WG%20%203a
%20%20seattle.pptx

This talk presented the case that existing testbeds don't model the
Internet. Instead, we should use resource donation and end user
applications to build a million node testbed to realize: platform
diversity; network diversity; and scale. See
https://seattle.cs.washington.edu

Questions from the audience:
Q: (Henning Schulzrinne) what do you suggest for incentives?
A: Diversity of opinion: 1) Give away app, but take 10% of resources. 2)
Make it easy to write an app.

Q: (Larry Peterson) How does GENI workflow fit this model?
A: Not well. User has to do it; it is not driven from the network.

Q: (Rob Ricci) this is good if research app provides a benefit to end
users. But, does this exclude research apps that do not benefit end users,
e.g., a measurement app?
A: Measurement works only when it is integrated into another application.

Q: (Henning Schulzrinne) But, DIMES is a client downloaded to your PC to
make measurements, and it is used.
A: Yes, but there are only a few 1000s of users, via volunteerism.

Comment by John Wroclawski: Consider not just volunteers, but also viral
marketing.

Q: (Henning Schulzrinne) Can user benefit include access to I/O devices?
A: Yes, but not important.

Q: (Max Ott) how do you know if users are representative?
A: We don't know.

________________________________________________
b) "Bringing External Connectivity and Experimenters to GENI".
PI and speaker: Nick Feamster at Georgia Tech.
Slides:
http://groups.geni.net/geni/attachment/wiki/presentations/OptIn%20WG%20%203b
%20bgp-mux-gec3.ppt

This project will provide for connectivity to and from the Internet, via a
BGP mux platform that provides BGP interconnects and tunnels. It is based
on the Quagga routing suite.

Questions from the audience:
Q: With a big AS, you can have multiple BGP sessions, at multiple
locations. How will mux do this?
A: Like any AS does it.

Comment by Heidi Dempsey: We will not have any upstream connectivity until
Internet2 agrees to provide it.

Q: Will mux be used only for BGP routing, or in a more general case?
A: Whenever you want upstream connectivity, reachable form this network,
you need upstream via this mux.

________________________________________________
c) "Regional Opt-In".
PIs: Matt Mathis and Ken Goodwin at Pittsburg Supercomputing Center and
Three rivers Optical Exchange
PI and speaker: Matt Mathis at Pittsburg Supercomputing Center and Three
rivers Optical Exchange
Slides:
http://groups.geni.net/geni/attachment/wiki/presentations/OptIn%20WG%20%203c
%20%20Mathis-regOPT.pdf

This talk presented a technique to allow regional Internet traffic flows to
be directed into a GENI experiment, and reviewed how such a process could be
managed on a day-to-day basis, including failure or success scenarios.

Questions from the audience:
Q: (Heidi Dempsey) Open flow switching is another way to do large-scale
opt-in. Can you compare?
A: Yes, but opt-in via open flow switch is local; is L2; and is
specifically selected. This is L3, and can be used at anywhere from campus
exit router (relatively easy) to backbone router (very difficult). They are
complementary in functions

________________________________________________
4) "Opt-In System Engineering Report"
Speaker: Harry Mussman at GENI Project Office hmussman@...
Slides:
http://groups.geni.net/geni/attachment/wiki/presentations/Opt_in%20WG%20%204
%20%20102908%20%20SE_Report_OptInWG_GEC3.ppt

This talk first provided an introduction to the role of the Opt-In WG system
engineer:

. Harry Mussman
- Current: Senior Systems Engineer in the GPO at BBN
- Last: Voice-over-IP architect at BridgePort Networks (a startup)
and GTE Internetworking/Genuity
- BSEE Univ Michigan, MSEE Northwestern Univ, PhD Stanford Univ
- hmussman@...
. Role of Opt-in WG SE
. Frame technical issues from top-down
- Collect issues from WG, organize and revise
- Use to identify and structure WG documents
. Synthesize input from bottom-up
- Collect input from WG, compile and distribute
- Look for and summarize consensus (or lack of it)
. Draft WG documents.
- Manage process to completion
. Assist WG communications
- Take and distribute notes
- Maintain wiki

Then, a possible way to summarize opt-in scenarios and capabilities was
presented:

. Overview of GENI
Opt-in Scenarios and Capabilities
. "GENI end-user opt-in is defined by scenarios where end users (not
researchers) become involved with GENI experiments, and by the capabilities
necessary to support them."
. Each opt-in scenario involves:
- One or more use cases.
- A set of players, with differing motivations.
- Unique issues.
. Each opt-in scenario requires:
- A set of policies and best practices.
- One or more underlying GENI capabilities to make it work.
. Opt-in Scenarios
. Have currently identified four distinct scenarios (which can
overlap).
. Scenario 1: An experiment on GENI that provides a service to users
and/or others
. Scenario 2: An experiment on GENI that can affect and disrupt users
and/or others
. Scenario 3: When users (or others) contribute (or associate)
resources to (with) experiments on GENI
. Scenario 4: When experiment data involving users is gathered on
GENI, and made available to researchers, and possibly others
. Other scenarios?
. Opt-in Capabilities
. Have currently identified three basic capabilities that will be
required.
. Capability 1: Gateway from GENI to another network, e.g., the
Internet
. Capability 2: Contribution (or association) of a user's node to an
experiment on GENI
. Capability 3: Gathering logs and experiment data on GENI, and
managing their distribution
. Other capabilities?
. Current Spiral 1 projects are focused primarily on providing a
capability.
. Capability 1: Gateway from GENI to another network, e.g., the
Internet
- 1601 Virtual Tunnels
- 1650 Regional Opt-In
. Capability 2: Contribution (or association) of a user's node to an
experiment on GENI
- 1645 Million Node GENI

Next, it presented an overview of related Spiral 1 projects.
(See slides)
Then, current opt-in issues were reviewed:

. Current Opt-in Issues and Tasks
. Scenario list:
- Review, and affirm or change.
. For each scenario:
- Formulate in more detail, and sub-divide as needed.
- Understand the players, their relationships and their motivations.
- Formulate proposed policies and best practices.
- Clearly identify and define key issues.
- Determine required capabilities.
- Reference current implementations, research and projects.
. Who in WG wants to contribute?
. continued (2)
. Capability list:
- Review, and affirm or change.
. For each capability:
- Formulate in more detail, and sub-divide as needed.
- Formulate requirements.
- Suggest design approaches.
- Reference current implementations, research and projects.
. Who in WG wants to contribute?

. Work towards defining and understanding scenarios is underway.
. Scenario 1: An experiment on GENI that provides a service to users
- See Opt-in Workshop report by Craig Partridge.
. Scenario 2: An experiment on GENI that can affect and disrupt users
and/or others
- Consider experience from PlanetLab, by Larry Peterson.
. Scenario 3: When users contribute (or associate) resources to
(with) experiments on GENI
- Studied as part of Spiral 1 project, 1645 Million Node GENI.

Finally, the documents planned for the next year were reviewed.
. Planned Opt-in Documents
. Architecture:
- Opt-in Architecture, v1 DRAFT due 3/1/09
. Scenarios?
. Capabilities?
. References?
. Who in WG wants to be an author? Editor?
. Who in WG wants to be an editor?
. Who in WG wants to be a reviewer?

. How WG Creates Document
. SE drafts document, with input from WG
. GPO does internal review
. SE posts first draft
- On wiki (to start); repository up RSN
. WG discusses document on WG list
- Possible one-on-one follow-ups
. SE assembles changes, and revises
. SE posts revision
. (Repeat, until document completed)

. Next.
. Notes, slides, action items, etc will be sent to the working group
mail list and posted on the wiki page:

http://groups.geni.net/geni/wiki/GeniOptIn

Question:
Q: (Harry Mussman) we heard about the PlanetLab issues; what about Emulab
and DETER?
A: (Ted Faber) Emulab has many fewer issues, because more self contained.
DETER has no issues, since completely isolated.

________________________________________________
5) Discussion, including comments and questions from the audience:

Q: (Henning Schulzrinne) who is audience for documents?
A: Future builders and experimenters. Those who provide required software
and hardware.

Comment from Josh Bers at BBN: As a member of the operations community,
would like you to consider use of GENI to try out novel techniques to
monitor network.

Topic for discussion: The need to involve an Institutional Review Board
when starting a GENI networking experiment.

Q: (Matt Mathis) How much of the personality of an IRB is institution
specific?
A: Quite a bit.

Comment by?: Had to go through an IRB to survey students; went very badly,
but eventually it was judged to not be needed.

Comment by Matt Mathis: Had submitted a short proposal that has not been
funded: Produce a white paper titled "Networking for IRB Members", Work has
not yet started.

Comment by Heidi Dempsey: IRB interface should be responsibility of
experimenters.

Agree: WG should consider producing: "Best practices for involving an
Institutional Review Board when starting a GENI networking experiment". How
can we get this started?

Q: (Henning Schulzrinne) How much disclosure is due users in the
million-node scenario?
A: Based on Sony activity that left active software on platform without
user's consent, you must at least inform them.

Comment by Heidi Dempsey: OMIS WG is working of security policies needed
for Spiral 1 operation; this overlaps with User Opt-In.

Q: (Henning Schulzrinne) Do we need architecture? Data format work?
Standard disclosure?
A: Yes. Yes. Yes.

Q: (Harry Mussman) How many are on Opt-In WG mailing list?
A: Small minority of audience.

________________________________________________________________________

_______________________________________________
opt-in-wg mailing list
opt-in-wg@...
http://lists.geni.net/mailman/listinfo/opt-in-wg

GENI Opt-in WG meeting at GEC3, 10/29/08, 2pm - 5pm

2008-10-24T13:05:04Z

All members of the Opt-in WG,

The WG will meet at GEC3, next week, on 10/29/08.

The overall agenda of GEC3 can be found at:

http://www.geni.net/GEC3/GEC3-Agenda.pdf

All talks to be presented at GEC3 can be found at:

http://groups.geni.net/geni/wiki/presentations

The agenda of the Opt-in WG meeting can be found below and on-line (latest version) at:

http://groups.geni.net/geni/attachment/wiki/presentations/102208%20%20GEC3_OptInWG_Agenda_Topics.doc

Talks at the Opt-in WG meeting include:

SE Report, at: http://groups.geni.net/geni/attachment/wiki/presentations/102208%20%20SE_Report_OptInWG_GEC3.ppt

(and more will be posted as they become available)

We look forward to meeting will all of you who are able to attend GEC3.

Best wishes,

Harry

Harry E. Mussman

Sr. Systems Engineer - GENI Project Office

BBN Technologies

10 Moulton Street

Cambridge, MA 02138

(617) 873-4282 - Office

(781) 266-8479 - Mobile

(617) 873-4888 - Fax

hmussman@...

www.bbn.com

Note: Check on-line for latest version:

3^rd GENI Engineering Conference

Opt-in Working Group Breakout Session

Wednesday, October 29, 2pm – 5pm.

Building 20 Auditorium

Agenda

1) Welcome by WG Chairs: Helen Nissenbaum and Henning Schulzrinne

Introductions

Scope of the Opt-in WG

Review of agenda

Additional topics?

2) Talks by relevant Spiral 1 projects:

a) “A Prototype of a Million-Node GENI”. PIs are Thomas Anderson and Arvind Krishnamurthy at the University of Washington – Seattle. This prototype addresses deploying a large number of end-user GENI nodes, and working through the resulting technical, motivational, security and scalability issues.

b) “Bringing Experimenters and External Connectivity to GENI”. PI is Nick Feamster at Georgia Tech. This project will provide for connectivity to and from the Internet, via a BGP mux platform that provides BGP interconnects and tunnels.

c) “Prototyping Techniques to Implement Opt-In”. PI is Matt Mathis at Pittsburg Supercomputing Center. Such a technique would allow current Internet traffic flows to be directed into a GENI experiment.

3) Opt-in Systems Engineering report by GPO Systems Engineer: Harry Mussman

Goals for this meeting.

Role of the GPO SE

Opt-in scenarios and capabilities

Relevant Spiral 1 projects

Current opt-in issues and tasks

Planned opt-in documents

4) “Lightning talks” relevant to WG.

(Invited by WG Chairs)

Review of PlanetLab experience in “Understanding and Resolving Conflicts Between Network Research and the Commodity Internet”, by Larry Peterson

Relevant talk from another Spiral 1 project?

5) Work plan for coming year.

Goals for the coming year. (WG Chairs)

Discussion of work plan and suggestions from the floor. (All WG members)

Recommendations for collaborators and authors. (All WG members)

6) Meeting wrap-up.

Review of opt-in action items. (GPO Systems Engineer)

Conclusions. (WG Chairs)

_______________________________________________
opt-in-wg mailing list
opt-in-wg@...
http://lists.geni.net/mailman/listinfo/opt-in-wg

it's time to register for GEC3

2008-09-03T13:26:21Z

Folks-

If you are planning to attend, please register for the GEC3 meeting
ASAP.

Registration site: http://www.edjassociates.com/geni3

Agenda: http://www.geni.net/GEC3/agenda.html

Thanks,

--aaron

_______________________________________________
opt-in-wg mailing list
opt-in-wg@...
http://lists.geni.net/mailman/listinfo/opt-in-wg

Use case slides

2008-03-02T19:43:28Z

See http://groups.geni.net/geni/wiki/Gec2 for better slides.

Henning

_______________________________________________
opt-in-wg mailing list
opt-in-wg@...
http://lists.geni.net/mailman/listinfo/opt-in-wg

Discussion on Monday

2008-03-02T19:06:27Z

Apologies for the very late message, but let me know if there are
items you'd like to discuss during the WG meeting on Monday.

We will be working from the scenario document (GENI use case). You can
see the slide at

http://www1.cs.columbia.edu:8080/display/optin/Home

(Note: it may well be a bit out of date.)

Minutes from the first meeting are also there.

Henning

_______________________________________________
opt-in-wg mailing list
opt-in-wg@...
http://lists.geni.net/mailman/listinfo/opt-in-wg

Re: [services-wg] GEC#2 hotel & registration

2008-02-13T08:36:35Z

Sorry for forgetting to add this (again):

You need to call the hotel directly at (703) 717-6200 to get the
conference rate.

--aaron

On Feb 13, 2008, at 11:26 AM, Aaron Falk wrote:

> GENI Engineering Conference #2
> ------------------------------
>
> This is a reminder that the GPO is holding a block of rooms the nights
> of March 2nd and 3rd at $201/night at the Westin Arlington Gateway for
> GEC attendees. (For comparison: The best Westin advertised rate for
> those nights is $379.) The block is reserved under the label "GENI
> Conference". Reservations must be made before ***February 15th*** to
> get this rate.
>
> Westin Arlington Gateway:
> http://www.starwoodhotels.com/westin/property/overview/index.html?propertyID=1513
>
> Also, don't forget to pre-register for the GEC conference itself.
> ***There will be no onsite registration.***
>
> GEC#2 registration:
> https://www.regonline.com/gec2
>
> GEC#2 logistics and agenda:
> http://www.geni.net/GEC2/GEC2.html
>
> --aaron
>
>
> _______________________________________________
> services-wg mailing list
> services-wg@...
> http://lists.geni.net/mailman/listinfo/services-wg

_______________________________________________
opt-in-wg mailing list
opt-in-wg@...
http://lists.geni.net/mailman/listinfo/opt-in-wg

GEC#2 hotel & registration

2008-02-13T08:26:03Z

GENI Engineering Conference #2
------------------------------

This is a reminder that the GPO is holding a block of rooms the nights
of March 2nd and 3rd at $201/night at the Westin Arlington Gateway for
GEC attendees. (For comparison: The best Westin advertised rate for
those nights is $379.) The block is reserved under the label "GENI
Conference". Reservations must be made before ***February 15th*** to
get this rate.

Westin Arlington Gateway:
http://www.starwoodhotels.com/westin/property/overview/index.html?propertyID=1513

Also, don't forget to pre-register for the GEC conference itself.
***There will be no onsite registration.***

GEC#2 registration:
https://www.regonline.com/gec2

GEC#2 logistics and agenda:
http://www.geni.net/GEC2/GEC2.html

--aaron

_______________________________________________
opt-in-wg mailing list
opt-in-wg@...
http://lists.geni.net/mailman/listinfo/opt-in-wg

geni-announce list

2007-10-22T11:26:50Z

In the interest of avoiding filling inboxes with multiple copies of
the same email, I'm sending this reminder that project related
announcements will be on the the GENI-announce mailing list. Here is
the subscription link:

http://lists.geni.net/mailman/listinfo/geni-announce

--aaron

---
Aaron Falk
Interim Engineering Architect
GENI Project Office
http://www.geni.net

_______________________________________________
opt-in-wg mailing list
opt-in-wg@...
http://lists.geni.net/mailman/listinfo/opt-in-wg

making list membership public

2007-10-12T18:13:24Z

As of October 17th, access to the lists of subscribers for GENI.net
mailing lists will be unrestricted permitting anyone to see who is on
which lists. We are making this change to be more consistent with
our general policy that all participation can be seen publicly.

FYI, our mail list tool does a mild obfuscation of email addresses
making it more difficult for spiders to collect the addresses.

Regards,

--aaron

---
Aaron Falk
Interim Engineering Architect
GENI Project Office
http://www.geni.net

_______________________________________________
opt-in-wg mailing list
opt-in-wg@...
http://lists.geni.net/mailman/listinfo/opt-in-wg

Opt-In Working Group breakout notes from GENI Engineering Conference - 10/10/07 3-6pm

2007-10-11T07:44:03Z

These are my un-edited notes, to be merged with the audio, slides, attendance, and flip-chart content later...

charter @ http://wiki.cs.columbia.edu

Opt-In views:

GENI as an ISP: can be transparent - might be too transparent to not reveal to the user that they are part of an experiment

Generalized end-user services: issues and potential seti -vs- botnet

In-Network services:

different implications on the interface required

Retail -vs- Wholesale:

User Motivation:

faster than I2:

individual/institution bandwidth provide local limitations, protocol limitations

as easy to fix the performance problems for I2 as it is to opt-in to GENI

Do you need to install software in order to opt-in?

Value offered to user -vs- what pain and suffering is inflicted on the user:

installing software - many dimensions to this (uses underlying stack, installs new stack, proxy, vm, etc)

traffic perturbation

For wholesale, need a method to opt-out

Is there a history of using IRB process for networking

IMC2008 - Internet usage and privacy issues paper, will be posted

have generally had limited access

as a community we have not done this broadly

There are local constraints and capabilities which will also apply

Could provide a template, where slices are available based on acceptable thresholds defining experiment attributes

Need to bring in experts from other areas who can inform the strategy

Another class of incentives -

Opt-In requirement on other NSF research - NSF could add incentives to other funded projects

Scale - Implies big changes in research incentives, practices, personnel, and budgets

User characteristics are not real - especially wrt. attacks

Real users require real software

Mobile users scale story the worst: 2B -> 4

need to partner with existing service providers

Issue of understanding an economic model and motivation of the donors - homework that needs to be done

Costly to write "real" (robust) services - this doesn't just happen, costs real money, and needs to be supported after the creator graduates Have to Get real value if they are going to use the service

Potential solution:

Involve the central IT departments

Graduate to GPO

adopt firefox model - large distributed and professional development staff (variants - bsd, apache, etc)

Most infrastructure which claims to support research has failed... wired is easier, for wireless need vendors for support

Missing technologies

residential broadband...

Realism: possible course of action

Remove or calibrated as a pillar

spend real money on clever packet generators

confront requirement for robust SW

Extend GENI to (all) desktops via sandbox technology

Sometimes, the incentive is based on user perception, not necessarily reality

Have we justified why we need real data?

Can we specify/characterize what real data is?

Don't want the observation/operation of the experimental parts to prevent transport as baseline service.

Can spectrum lending be used as an incentive?

Organization:

incentives

technology (software/vm, etc)

legal/ethical/etc...

What is a user?

Wholesale option - AT&T subscribes

Service Opt-In - CNN provides CNN' via GENI (wikipedia is being distributed via CODEEN)

Research community does not have a history of developing the killer app, but we have provided the means for killer apps to be created.

Access to resources they can't get otherwise

collection of graphics processors

distributed data storage

(expensive and large)

(imposes GENI as a veneer in front of something else - what is the motive for this service to allow GENI to impose itself in front of the service? The Places where GENI can impose itself are places above layer7)

Layered motivation

Users want the innovative services that are built upon unique resources made available via the unique network (or services that rely only on the unique network)

This way we don't compete with our industry partners

Should GENI (this WG) be involved in the formalization of IRB parameters and limits

NSF is interested in establishing a baseline

need to consider, exceptions (honey pots), local restrictions, international differences

what about local IRB processes, tools, etc

3 capabilities:

Disclosure of who can gather data

User can determine what data has been collected

Correction - deletion of data at user request?

Differentiate data collection for system administration from data collection for research

Anonymization

Can provide a baseline outside of or streamlined IRB process

of limited use for some types of research and data

verifiability

Taxonomy of opt-in classes

Taxonomy of protections and rights

benchmark - Need a way to evaluate the opt-in stories in proposals (realize that some experiments can be successful w/o, but that the platform requires it for ultimate success)

How much opt-in do we need? (how many users?)

Is there a way to learn from previous test-bed opt-in failures? (impossible to opt-out and no users opted in)

Traffic mirroring and synthetic load (use the users data, but don't perturb their packets)

Can also provide dual services and provide rollover capabilities

Need to make sure the platform supports a continuum of reliability (99% - 5 9's)

Platform also needs to support monitor only geni-ized nodes

How fast can you make the failover?

Two opt-in problems

construction phase

need to include user opt-in here in order to ensure that they are there and supported post-construction

learning experience

limited opt-in support

needs to be a calculated risk - don't want to scare users

post-construction phase

Opt-in strategy needs to be consistent with the maturity of the platform

Open issues If users can bring in sensors or other devices which could involve other "users"

Should the opt-in API be provided by the service or by the infrastructure (slice)

Matt Sanders | Research Scientist | Academic and Research Technologies

Office of Information Technology | Georgia Institute of Technology

matt.sanders@... | 404-894-9107 | 105 Rich

_______________________________________________
opt-in-wg mailing list
opt-in-wg@...
http://lists.geni.net/mailman/listinfo/opt-in-wg

Re: Presentations & agenda

2007-10-05T10:54:37Z

My sense of this problem is that a (group or individual) may wish to
opt-in for a particular experiment or arrangement of the GENI
environment, while not participating in some other experiment. Along
these lines, it would be important to be able to specify your opt-in to
specific arrangements.

There seems to be a tussle between the desire to have broad
participation (necessitating a focus on simple, widely-usable
approaches) and enabling granular opt-in controls.

Similar to Matt's thoughts, I'm thinking about approaches involving GENI
elements at the RON/campus edge that provide the essential service of
selecting and divert traffic to GENI.

Though I'm not sure what incentives would work..

-Kevin

Henning Schulzrinne wrote:

> I think you highlight an important distinction, namely between
> "individual" and "group" opt-in.
>
> This is fairly similar to how Internet2 is handled on many campuses
> today; all traffic between US I2 sites traverses Internet2. GENI
> would be Internet3 in that model... I'm familiar with the Columbia
> setup, where we have several 'commercial' Internet egress pipes plus
> our pipe to the Gigapop. We limit per-user commodity Internet traffic
> volume, but not Internet2 traffic. Thus, at least in our case, this
> wouldn't be all that attractive to students.
>
> Henning
>
> On Oct 4, 2007, at 7:30 PM, Matt Mathis wrote:
>
>
>> There is another option to consider. If some portion of the GENI
>> infrastructure is placed at the RONs (Regional Optical Networks,
>> aka GigaPoPs)
>> or at campus borders, it might be possible to "opt in" at very large
>> granularities by steering some portion of campus traffic through
>> GENI. The key
>> here is to provide fast "restoration", e.g the capability to
>> quickly reroute
>> traffic back on to production infrastructure. It also requires some
>> fairly
>> strong incentive to encourage the users to opt in as a community.
>>
>> There is good low hanging fruit - these days most campuses
>> segregate dormitory
>> traffic from general university traffic, and subject traffic
>> between the dorms
>> and external sites to separate bandwidth caps which are often much
>> smaller
>> than the presented load. They do this to control the cost of
>> providing
>> Internet service to the students, who have a huge capacity to share
>> digital
>> content. The students would probably happily accept increased
>> Internet
>> capacity in exchange for a slight reduction in robustness. The
>> university
>> might save money by using a metered service for the students. For
>> the cost of
>> providing transit service, GENI would have at its disposal a huge
>> and diverse
>> source of authentic traffic.
>>
>> The tricky parts are getting the "rerouting" to work well enough
>> and to
>> accurately balance the desirability of the GENI service relative to
>> the
>> parallel production service, such that the users continue to prefer
>> to opt in
>> as a block, but they do not become so addicted that turning off
>> GENI causes
>> problems. "Prime time down time" should probably be an ongoing
>> operational
>> requirement.
>>
>> Just a thought.
>>
>> Thanks,
>> --MM--
>> -------------------------------------------
>> Matt Mathis http://www.psc.edu/~mathis
>> Work:412.268.3319 Home/Cell:412.654.7529
>> -------------------------------------------
>> Evil is defined by mortals who think they know
>> "The Truth" and use force to apply it to others.
>>
>> On Wed, 3 Oct 2007, Henning Schulzrinne wrote:
>>
>>
>>> We have roughly 3 hours for the opt-in WG meeting in Minneapolis.
>>> After discussions with Aaron, we will be spending a good chunk of our
>>> time trying to scope the problem. One way to divide the topic into
>>> more manageable chunks is to think of a division into three problems:
>>>
>>> (1) "ISP": If GENI acts like an ISP, how do users gain access to
>>> that, both on traditional Ethernet-style (campus) networks and on
>>> wireless networks (802.11 and cellular)? What incentives are there?
>>>
>>> (2) "Generalized P2P": If end user resources become part of the
>>> experimental infrastructure, how can users restrict the use of such
>>> resources and how can experimenters access those resources?
>>>
>>> (3) Network services: How do users get access to network services?
>>> What are the motivations and possible incentive/payment mechanisms?
>>>
>>> All three problems have both a technical component, such as protocols
>>> and issues of trust, an economic component (who pays and in what
>>> currency) and a policy/legal component, such as the usual issues that
>>> worry institutional review boards (IRBs), including privacy and
>>> informed consent.
>>>
>>> To help structure the discussion, I'd like to invite members of the
>>> WG to present brief talks on WG-related topics, not necessarily
>>> following the structure above. Please let me know as soon as possible
>>> what you would want to talk about, so that I can put together an
>>> agenda.
>>>
>>> Henning
>>>
>>> _______________________________________________
>>> opt-in-wg mailing list
>>> opt-in-wg@...
>>> http://lists.geni.net/mailman/listinfo/opt-in-wg
>>>
>>>
>
>
> _______________________________________________
> opt-in-wg mailing list
> opt-in-wg@...
> http://lists.geni.net/mailman/listinfo/opt-in-wg
>

_______________________________________________
opt-in-wg mailing list
opt-in-wg@...
http://lists.geni.net/mailman/listinfo/opt-in-wg

Re: Presentations & agenda

2007-10-04T19:48:47Z

I think you highlight an important distinction, namely between
"individual" and "group" opt-in.

This is fairly similar to how Internet2 is handled on many campuses
today; all traffic between US I2 sites traverses Internet2. GENI
would be Internet3 in that model... I'm familiar with the Columbia
setup, where we have several 'commercial' Internet egress pipes plus
our pipe to the Gigapop. We limit per-user commodity Internet traffic
volume, but not Internet2 traffic. Thus, at least in our case, this
wouldn't be all that attractive to students.

Henning

On Oct 4, 2007, at 7:30 PM, Matt Mathis wrote:

> There is another option to consider. If some portion of the GENI
> infrastructure is placed at the RONs (Regional Optical Networks,
> aka GigaPoPs)
> or at campus borders, it might be possible to "opt in" at very large
> granularities by steering some portion of campus traffic through
> GENI. The key
> here is to provide fast "restoration", e.g the capability to
> quickly reroute
> traffic back on to production infrastructure. It also requires some
> fairly
> strong incentive to encourage the users to opt in as a community.
>
> There is good low hanging fruit - these days most campuses
> segregate dormitory
> traffic from general university traffic, and subject traffic
> between the dorms
> and external sites to separate bandwidth caps which are often much
> smaller
> than the presented load. They do this to control the cost of
> providing
> Internet service to the students, who have a huge capacity to share
> digital
> content. The students would probably happily accept increased
> Internet
> capacity in exchange for a slight reduction in robustness. The
> university
> might save money by using a metered service for the students. For
> the cost of
> providing transit service, GENI would have at its disposal a huge
> and diverse
> source of authentic traffic.
>
> The tricky parts are getting the "rerouting" to work well enough
> and to
> accurately balance the desirability of the GENI service relative to
> the
> parallel production service, such that the users continue to prefer
> to opt in
> as a block, but they do not become so addicted that turning off
> GENI causes
> problems. "Prime time down time" should probably be an ongoing
> operational
> requirement.
>
> Just a thought.
>
> Thanks,
> --MM--
> -------------------------------------------
> Matt Mathis http://www.psc.edu/~mathis
> Work:412.268.3319 Home/Cell:412.654.7529
> -------------------------------------------
> Evil is defined by mortals who think they know
> "The Truth" and use force to apply it to others.
>
> On Wed, 3 Oct 2007, Henning Schulzrinne wrote:
>
>> We have roughly 3 hours for the opt-in WG meeting in Minneapolis.
>> After discussions with Aaron, we will be spending a good chunk of our
>> time trying to scope the problem. One way to divide the topic into
>> more manageable chunks is to think of a division into three problems:
>>
>> (1) "ISP": If GENI acts like an ISP, how do users gain access to
>> that, both on traditional Ethernet-style (campus) networks and on
>> wireless networks (802.11 and cellular)? What incentives are there?
>>
>> (2) "Generalized P2P": If end user resources become part of the
>> experimental infrastructure, how can users restrict the use of such
>> resources and how can experimenters access those resources?
>>
>> (3) Network services: How do users get access to network services?
>> What are the motivations and possible incentive/payment mechanisms?
>>
>> All three problems have both a technical component, such as protocols
>> and issues of trust, an economic component (who pays and in what
>> currency) and a policy/legal component, such as the usual issues that
>> worry institutional review boards (IRBs), including privacy and
>> informed consent.
>>
>> To help structure the discussion, I'd like to invite members of the
>> WG to present brief talks on WG-related topics, not necessarily
>> following the structure above. Please let me know as soon as possible
>> what you would want to talk about, so that I can put together an
>> agenda.
>>
>> Henning
>>
>> _______________________________________________
>> opt-in-wg mailing list
>> opt-in-wg@...
>> http://lists.geni.net/mailman/listinfo/opt-in-wg
>>

_______________________________________________
opt-in-wg mailing list
opt-in-wg@...
http://lists.geni.net/mailman/listinfo/opt-in-wg

Re: Presentations & agenda

2007-10-04T17:30:34Z

There is another option to consider. If some portion of the GENI
infrastructure is placed at the RONs (Regional Optical Networks, aka GigaPoPs)
or at campus borders, it might be possible to "opt in" at very large
granularities by steering some portion of campus traffic through GENI. The key
here is to provide fast "restoration", e.g the capability to quickly reroute
traffic back on to production infrastructure. It also requires some fairly
strong incentive to encourage the users to opt in as a community.

There is good low hanging fruit - these days most campuses segregate dormitory
traffic from general university traffic, and subject traffic between the dorms
and external sites to separate bandwidth caps which are often much smaller
than the presented load. They do this to control the cost of providing
Internet service to the students, who have a huge capacity to share digital
content. The students would probably happily accept increased Internet
capacity in exchange for a slight reduction in robustness. The university
might save money by using a metered service for the students. For the cost of
providing transit service, GENI would have at its disposal a huge and diverse
source of authentic traffic.

The tricky parts are getting the "rerouting" to work well enough and to
accurately balance the desirability of the GENI service relative to the
parallel production service, such that the users continue to prefer to opt in
as a block, but they do not become so addicted that turning off GENI causes
problems. "Prime time down time" should probably be an ongoing operational
requirement.

Just a thought.

Thanks,
--MM--
-------------------------------------------
Matt Mathis http://www.psc.edu/~mathis
Work:412.268.3319 Home/Cell:412.654.7529
-------------------------------------------
Evil is defined by mortals who think they know
"The Truth" and use force to apply it to others.

On Wed, 3 Oct 2007, Henning Schulzrinne wrote:

> We have roughly 3 hours for the opt-in WG meeting in Minneapolis.
> After discussions with Aaron, we will be spending a good chunk of our
> time trying to scope the problem. One way to divide the topic into
> more manageable chunks is to think of a division into three problems:
>
> (1) "ISP": If GENI acts like an ISP, how do users gain access to
> that, both on traditional Ethernet-style (campus) networks and on
> wireless networks (802.11 and cellular)? What incentives are there?
>
> (2) "Generalized P2P": If end user resources become part of the
> experimental infrastructure, how can users restrict the use of such
> resources and how can experimenters access those resources?
>
> (3) Network services: How do users get access to network services?
> What are the motivations and possible incentive/payment mechanisms?
>
> All three problems have both a technical component, such as protocols
> and issues of trust, an economic component (who pays and in what
> currency) and a policy/legal component, such as the usual issues that
> worry institutional review boards (IRBs), including privacy and
> informed consent.
>
> To help structure the discussion, I'd like to invite members of the
> WG to present brief talks on WG-related topics, not necessarily
> following the structure above. Please let me know as soon as possible
> what you would want to talk about, so that I can put together an agenda.
>
> Henning
>
> _______________________________________________
> opt-in-wg mailing list
> opt-in-wg@...
> http://lists.geni.net/mailman/listinfo/opt-in-wg
>

_______________________________________________
opt-in-wg mailing list
opt-in-wg@...
http://lists.geni.net/mailman/listinfo/opt-in-wg

Presentations & agenda

2007-10-03T19:05:28Z

We have roughly 3 hours for the opt-in WG meeting in Minneapolis.
After discussions with Aaron, we will be spending a good chunk of our
time trying to scope the problem. One way to divide the topic into
more manageable chunks is to think of a division into three problems:

(1) "ISP": If GENI acts like an ISP, how do users gain access to
that, both on traditional Ethernet-style (campus) networks and on
wireless networks (802.11 and cellular)? What incentives are there?

(2) "Generalized P2P": If end user resources become part of the
experimental infrastructure, how can users restrict the use of such
resources and how can experimenters access those resources?

(3) Network services: How do users get access to network services?
What are the motivations and possible incentive/payment mechanisms?

All three problems have both a technical component, such as protocols
and issues of trust, an economic component (who pays and in what
currency) and a policy/legal component, such as the usual issues that
worry institutional review boards (IRBs), including privacy and
informed consent.

To help structure the discussion, I'd like to invite members of the
WG to present brief talks on WG-related topics, not necessarily
following the structure above. Please let me know as soon as possible
what you would want to talk about, so that I can put together an agenda.

Henning

_______________________________________________
opt-in-wg mailing list
opt-in-wg@...
http://lists.geni.net/mailman/listinfo/opt-in-wg

GENI technical risk areas

2007-09-24T19:21:45Z

To GENI Working Groups-

At the end of the current planning process, 2-4 years from now, GENI
needs to have a mature design, budget, and buildout schedule. Towards
that end, this fall the GPO is planning to issue the first of a series
of semi-annual solicitations for proposals to perform risk reduction
design and prototyping. Risk reduction activities are those that make
it more likely that the GENI will perform as desired and be
constructed on-budget and on-schedule.

The coming solicitation will be targeted at areas which GPO system
engineering feels are the top concerns that need to be addressed over
the coming year. We have compiled the following initial list:

* Architecture & requirements development. Create/improve designs for
for areas including instrumentation, security (conceptual design for
identity, authentication, and authorization; mappings to existing
technologies), resource description and discovery, federation, and
end-user opt-in. Some prototyping in these areas will be useful.

* Slicing as a basic construct, employed end-to-end across a range of
technologies. Here near-term, working demonstrations of the relevant
GENI subsystems and trial integrations will be particularly useful,
as will early demonstrations of instrumentation in a sliced
environment.

* Developing a practical approach for administrative and operational
control that addresses the needs of cooperative facility hosts
(e.g., universities); federated, interconnected facilities (e.g.,
non-NSF GENI facilities); subcontracted facilities (e.g., optical
networks or co-location facilities); and a GENI Network Operations
Center.

There will be a session for open discussion of project risks on
October 9th at the GENI Engineering Conference [1]. We are interested
in hearing feedback on whether elements on this list should be removed
(i.e., well-understood, not risky or not timely) or replaced by other
items which are of greater concern.

Looking ahead, the GPOs risk assessment will be informed by the GENI
working groups. At future GEC meetings, the GPO staff system
engineers supporting the working groups will be responsible for
reporting on each working group's readiness. Areas which are not
ready are potential risk areas. Risk areas the GPO determines to be
near-term and significant may appear in future solicitations.

We invite your participation in this discussion.

--aaron

[1] http://www.geni.net/geni-engineering-conference

---
Aaron Falk
Interim Engineering Architect
GENI Project Office
http://www.geni.net

_______________________________________________
opt-in-wg mailing list
opt-in-wg@...
http://lists.geni.net/mailman/listinfo/opt-in-wg

Welcome to the opt-in WG

2007-09-15T12:43:45Z

Welcome to the OPT-IN WG!

The WG mailing list is pretty small at this point, with about 4
non-robot members. I'd encourage you to let others know about this
effort and to opt-in.

I look forward to a productive meeting in Minneapolis, and to meet many
of you in person there.

Henning
(chair)

_______________________________________________
opt-in-wg mailing list
opt-in-wg@...
http://lists.geni.net/mailman/listinfo/opt-in-wg