Names
=====

Eric - doing the design, part

Prusard Calium - finsihed masters and Ohio state, half for E2E piPES, half for Ohio network. Done previous work about H323 beacon.

Jeff Boot - lives in Idaho falls, finished One-way active measurement protocol (OAMP). One of the tools that would be wanted initially on the PMP box.

Them and us and some others from Slac would be the main peeps.

Notes
=====

Send an email about our ideas, and that can start a discussion.

Jackie is going to set up an IRC channel.

Prusard has been looking into the database stuff. Will send us the options that he's come up with.

In terms of looking forward. Yee tries to say what we've been doing. Eric recommends that we should look at the input first, then the output later.

Will send us a pointer to OAMP when it comes up, also a pointer to the beacon work.

For the next week or two: focus more on the input to the PMP rather than the output. They will work on getting Iperf stored in a single database.

Yee asks about working on other tools, Maggie and stuff. They are working on Iperf and OAMP because they have much experience in that.

Eric will get us both accounts on Thunderbird (their dev machine). Thunderbird is next to the next generation abeline routers, and will be the central collection point of all data.   Initial password "changeme".

Phone meetings for everyone will be weekly or bi-weekly.

Pete
====

Eric is happy that we should be able to cleanly define our areas (as it's multinational).  Eric thinks that we should probably work on front-end stuff mainly.

Pete drops the OGSA service bombshell. Explains having a common PMP interface for a very heterogeneous set of tools on PMPs.

Eric: PMP Templates: prescribe different templates for PMPs, so that stuff is slightly homogenous.  
Eric: is it worth having an interface that you can ask "get me a measurement" or should it be "do an X measurement at T". If we could work out how to do a generic "get me a measurement" interface, then that would be harder but better. Their plan is to do the "do an X measurement" option first, and then think about option 1 later.

Eric: if there was a small number of templates, (template 1 has tool A, template 2 has tool B), the PMPs register to the scheduler saying what template they follow, and then the scheduler can deal with that. It may be that having the PMPs do the mapping between metric and tool (which would be step 2) is better, and should be just done straight off.

Eric: it might be nice if one of us from the group who was interested went and looked at what the GGF has been doing. Walk through the whole process once, and see how it works. We should start by not destroying whatever's been started already :)    That would be a bitch.

They will get the development environment up and ready, then decide what's ready to do. The dev. area will let us check code in and see their code. By the end of the month they will probably have something that one of the team could start coding on.

Next week
=========

plan on meeting at the same time next week.