IAWG Meeting Minutes 2012-02-22
Attendees:
Myisha Frazier-McElveen
Nathan Faut
Rainer Hoerbe
Linda Goettler
Colin Soutar
Joe Stuntz
Patrick Curry
Neil Clowes
John Bradley
Richard Wilsher
Richard Trevorah
Apologies:
Rich Furr
Bill Braithwaite
Staff:
Joni Brennan
Anna Ticktin
Minutes:
1. ADMINISTRATIVE:
Roll Call
Motion for minutes approval: 15 Feb 2012
Richard Trevorah moves to approve the minutes as recorded. Patrick Curry and John Bradley second. With no further discussion or objection, the motion carries.
2. F2F MEETING - proposed topics for discussion:
PAC
RAF
Marketing Collateral
It is unclear at this time whether the IAWG will require a telecon line to host its own session or simply join a P3 joint-session.
Proposed roadmap action :
Aligning with the latest revision of 800-63
3. IAF V 2.0 REVIEW
Point in Time vs. Period of Time
The wg discussed Ken Dagg's comments to the proposed text:
Table in section 1.1. I don't know if the values are set in stone or not. If not, I would suggest, given the importance of an LOA4 service (i.e., the impact if it is wrong) to a RP, that the Minimal Operational Period for a LOA4 be a minimum of 180 days (and I would be happier with a full year). Less than this period does not, to me, provide the perception of stable operations that I would expect from someone that is giving me a LOA4 assertion.
RGW will research the location of the term "operational" and then redirect language to address that point.
Section 1.2. I would suggest that the time period for the follow-on report be reduced for LOA3 and LOA4 – perhaps on a graduated scale (120 for LOA3 and 90 for LOA4). Similar to the point I made in 1) above I would also be happy if a LOA4 service could not participate in DZ. That being said, I understand the business reality. Perhaps, for a LOA4 we could require two follow-on reports at day 90 and day 180.
RGW is okay with adjusting text to address LOA 3 reducing that period to 60 days.
RGW is suggesting this language would sit in a new document within the set
4. AOB
Next week's call is cancelled due to presumed low attendance in light of the RSA conference.
Patrick volunteers that there are new issues arising around doing business in the cloud, and will provide a more detailed report in due course.