|
IAOC Meeting 2013-04-18 10:00 EDT
Bernard Aboba [GUEST]
=================== 1. Minutes 2013-03-132. RPS Udate 3. DPM Appointment 4. Tools Maintenance Contract 5. Contracts Status 2013 6. Legal Services Contract Extension 7. Orlando Financial Results 8. Berlin Registration Gender Collection 9. IANA SLA 10. Retreat Logistics and Agenda 11. AOB Bob called the meeting to order at 10:02 AM EDT. 1. Minutes Bob moved, and Chris seconded a motion to approve the 2013- Without objection, the minutes were approved. 2. RPS Update The proposed RPS objectives are (i) to enhance the Remote Participation experience in a variety of scenarios; (ii) to broaden the potential base of IETF participants; (iii) to deploy and gain experience with the use of IETF & W3C technology; and (iv) to enlist the IETF community in the development of services to meet their needs. Some desirable capabilities as a participant: to be able to see and hear any of the WB/BOF meetings and plenaries, either in real-time or after the meeting; as a presenter: to be able to make a presentation (with face visible), show slides, and hear and answer questions from the floor and from other remote participants. As much as possible the protocols and the software should be non-proprietary, and must be usable on a wide range of PC and mobile platforms. Responses expressing interest for Meetecho, Cisco WebEx, and Jitsi. There was feedback received at IETF 86 that the community wants a lot more remote participation such as enhanced audio/video. There was substantial positive feedback on Meetecho and they appreciated the archival sessions of the IETF website and the tutorials. The time from live to archive is critical. People basically want everything to be covered. One person has to be present so there is a possible issue with that; but the desire to cover every meeting is there. One hour has set aside at the retreat, and there’s a tentative schedule. During that hour there will be a discussion of details on the RPS committee. Also discussed will be the technology roadmap and compliance requirements. Would want to make an announcement to the community that this activity is going on – that being the outcome of the retreat session. Web RTC is a strong direction the IAOC likes. A lot of developer support is needed; it’s hard to move forward without it. 3. DPM Appointment Robert is uniquely qualified through his tools experience, Code Sprint experience, service on the Tools Development Committee, service as an AD with hands-on experience with the Datatracker, and work with Henrik over the years, as well as having Henrik's trust and confidence. Henrik recommends Robert to become the next DPM. The Tools Management Committee also recommends the IAOC appoint Robert as the DPM. Scott moved and Russ seconded a motion for the IAOC to appoint Robert Sparks Datatracker Project Manager and requests the Internet Society to enter into such agreements to effect this appointment.
The motion passed. 4. Tools Maintenance Contract Tools Maintenance includes:
More than $600K has been spent on Datatracker and Tools development since 2010. Tools not under warranty need to be maintained. The tools maintenance Budget for 2013 is $75K. The Tools Management Committee is recommending that Henrik be awarded a Tools Maintenance contract. Henrik's employer, Netnod, currently donates 25% of the Henrik's time during regular work hours to working on tools maintenance. This award and compensation would be for tools maintenance performed on personal time expended each week. The compensation for such work shall be <confidential> </confidential> There may also be some travel requirements, but, as yet, unknown. Ray and the Tools Management Committee will monitor the contract. RESOLUTION: Scott moved and Russ seconded a motion to approve the award of a Tools Maintenance Contract to Henrik Levkowetz and request that the Internet Society to enter into such agreements to effect this award.
The motion passed. 5. Contracts Status 2013
All are eligible for a 2-year extension. The 2013 Budget set a Transitions Budget of $0 based on the assumption that there would be no change in contractors in 2013. There was the presumption that each contract would be extended. This was discussed when the IAOC adopted the 2013 Budget in September 2012. If we did want to issue an RFP we would target the following dates:
All RFC Editor (2-4) extensions and RFPs require approval of RSOC and/or IAB. Recommend all be extended for 2 years effective on the anniversary of their effective date; however, the IAOC needs to discuss II-IV above with RSOC and IAB before proceeding. Except for Legal Services we will take action on these beginning in May. 6. Legal Services Contract Extension This would be the first of two possible extensions. Jorge is providing very good service. The compensation arrangement is a fixed monthly retainer. There will be no change in that area over the next two years. There are some legal fees that are paid to the other lawyers, for subpoena work, depositions, litigation and others that Contreras Legal Strategy does not provide. RESOLUTION: Scott moved and Russ seconded a motion to approve a two- year extension of the Legal Services Contract with Contreras Legal Strategy LLC and request that the Internet Society enter into such agreement as to effect this extension.
The motion passed. Randy abstained because he had not seen the contract. 7. Orlando Financial Results Revenues were $31.5K less than forecast, while Expenses did better than forecast by $57K. Net Funds Available for IETF Operations were $483,535, $25K better than forecast. Revenue results of note: Expense results of Note: Bits-N-Bites Program results:
The bus service averaged about 100 people per night – it was under utilized. The survey response indicated people used taxis and many people had more rental cars than normal. It would have been worse had buses not have been provided at all. 8. Berlin Registration Gender Data Collection The IAOC asked the community for feedback on the proposal for an Optional Question to identify registrant's gender. There was a lengthy discussion on the list and email sent directly to the IAOC. Feedback included that it was OK, that we needed a professional to frame the questions, that the question itself was repugnant, that it may violate privacy regulation and much more. Ray said one option would be to send this matter to the Design Team, that the data was just one part of an overall Diversity question that the IETF is pursuing through a Design Team established by the IETF Chair. The Design Team will be engaging in a lengthy dialogue with the community to reach its recommendations. The IAOC engaged in a discussion of the pros, cons, and legality of collecting gender data, as well as its retention. The IAOC has to be clear about what they’re going to do with the data. The aggregate is the only data that should be kept. The IAOC has enough guidance that that’s okay to do, but the IAOC has to be very clear on how we’re going to keep the data. Ray noted that AMS needed a Go-No Go by 25 April in order to get the development work done in time registration to open the week of 29 April. RESOLUTION: Scott moved and Ole seconded a motion to approve the collection of Gender data on the Meeting registration form provided the question is optional, the individual data is not made public and not retained, the results are reported in the aggregate, and the registration form states why the information is being gathered. The data is being gathered to benchmark gender participation currently, over time, regionally, and inform IETF diversity initiatives, if any.
The motion passed. Chris abstained because he felt that the IAOC needed to finish the discussion on messaging for gender information gathering before they voted on doing it 9. IANA SLA 10. Retreat Logistics and Agenda The dinner schedule is: There will be breakout topic opportunities: The agenda for the IAOC retreat was discussed in detail. More than an hour should be given to the RPS discussion. 11. AOB Bob adjourned the IAOC meeting at 11:07 AM EDT. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
