RFC Series Oversight Committee (RSOC) Appointments
The IAB extends many thanks to the community members who were willing to serve on the RSOC for their ongoing support of the RFC Series and the RFC Series Editor. After reviewing the strong list of individuals who offered to serve on the RSOC, the IAB is appointing the following people to serve on the RSOC: Sarah Banks Tony Hansen Adam Roach Peter Saint-Andre In addition, Christian Huitema and Robert Sparks will serve as IAB members on the RSOC, and Portia Wenze-Danley will continue to serve as a liaison to RSOC in her role as interim IAD. The IAB sincerely thanks all of the people that offered to serve on the RSOC. The IAB particularly thanks the following current RSOC members that will be stepping off the committee later this month: Nevil Brownlee Joel Halpern Bob Hinden Martin Thomson (IAB member) On behalf of the IAB, Cindy Morgan IAB Executive Administrative Manager
RFC Series Oversight Committee (RSOC) Appointments
The IAB extends many thanks to the community members that were willing to serve on the RSOC for their ongoing support of the RFC Series and the RFC Series Editor. After reviewing the strong list of individuals who offered to serve on the RSOC, the IAB is appointing two people to the RSOC: Sarah Banks Robert Sparks The IAB sincerely thanks all of the people that offered to serve on the RSOC. On behalf of the IAB, Russ Housley IAB Chair On Mar 26, 2014, at 11:29 AM, IAB Chair wrote: As specified in RFC Editor Model (Version 2) (RFC 6635), the IAB is responsible for appointing the members of the RFC Series Oversight Committee (RSOC). Bernard Aboba has stepped down from his role on the RSOC. The IAB thanks him for his service. The IAB is now looking for a community member to appoint to the RSOC. This message is a call for nominations for that position. If you are interested, or there is someone you know of who would make a good member, please nominate yourself or that person. As noted in RFC 6635, the RSOC, which currently includes two IAB members, acts with authority delegated from the IAB, and the RSOC is responsible for approving consensus policy and vision documents developed by the RFC Series Editor (RSE) in collaboration with the community. The RSOC is also responsible for ensuring that the RFC Series is run in a transparent and accountable manner. For decisions that affect the RFC Series Editor individually, the RSOC prepares recommendations for the IAB, such as preparing the performance reviews of the RSE. RSOC members are expected to recognize potential conflicts of interest and behave accordingly. If you would like to nominate a candidate for membership in the RSOC, please send information on the candidate, including their email address, to iab-chair at iab.org and execd at iab.org. Self-nominations are acceptable. The current membership of the RSOC can be seen at http://www.iab.org/activities/programs/rfc-editor-program/. Nominations should be received by 8 April 2014. The IAB will confirm individuals willingness to be considered, and publish the resulting list so that the community can provide comments before the IAB makes any decisions on RSOC membership. The new member will begin serving on the RSOC as soon as the IAB completes the selection process. For the information of potential nominees, the RSOC will be having a half-day face-to-face meeting in Toronto on 19 July 2014, the Saturday before IETF 90. The current focus of the RSOC is on: 1) Overseeing and assisting the RSE in the process of evoling the RFC format and style. 2) Periodic reviews of the RFSE performance. 3) Working with the RSE and the IETF Administrative Oversight Committee (IAOC) on the statements of work for contracts related to the RFC Production Center and RFC Publisher. The RSOC usually meets virtually once a month for an hour, a lunch at every IETF meeting, and a half day in-person meeting once a year (usually scheduled the weekend before an IETF meeting at the same venue (as noted above the next one will be in Toronto). More time may be required if the applicant participates in leadership of the committee, design teams, or other related activities. RSOC members are expected to follow the rfc-interest mailing list, a usually low-volume list for internal communication, and to be familiar with discussion topics related to the RFC series on the i...@ietf.org list. Thank you, Russ Housley IAB Chair
Re: [IAB] RSOC Appointments
On Jun 25, 2013, at 7:53, Randy Bush ra...@psg.com wrote: Congratulations, gentlemen. and they are all male Well, all the volunteers were male, so no real surprise here. (And yes, I wish the volunteer pool had been more diverse. But it wasn't.) Lars
Re: [IAB] RSOC Appointments
On Jun 25, 2013, at 7:53, Randy Bush ra...@psg.com wrote: Congratulations, gentlemen. and they are all male Well, all the volunteers were male, so no real surprise here. (And yes, I wish the volunteer pool had been more diverse. But it wasn't.) Lars
Re: RSOC Appointments
Thank you, Fred. Tony On 6/25/2013 1:20 AM, Fred Baker (fred) wrote: Congratulations, gentlemen. On Jun 24, 2013, at 5:35 PM, IAB Chair iab-ch...@iab.org wrote: Nevil Brownlee, Tony Hansen, Joe Hildebrandt, Bob Hinden, Alexey Melnikov, Bernard Aboba (an IAB member), and Joel Halpern (an IAB member).
Re: [IAB] RSOC Appointments
I checked the call for nommitantios (Sent on april 24th 2013 on the ietf-announce) and it does not describe what should be the qualifications of the candidates. I think that this enough to alienate new people (as they may think that they are not good candidates for the position because of lack of experience in the IETF, not being an RFC author, etc.) I would recommend that future announcement of kind of positions have a very clear profile of what it is expected from the candidates in IETF experience, general requirements, etc. In the end, it is like we were filling a job positions in an organization, the difference here is that we are not receiving a salary. my 20 cents. /as On 6/25/13 8:25 AM, Eggert, Lars wrote: On Jun 25, 2013, at 7:53, Randy Bush ra...@psg.com wrote: Congratulations, gentlemen. and they are all male Well, all the volunteers were male, so no real surprise here. (And yes, I wish the volunteer pool had been more diverse. But it wasn't.) Lars
Re: [IAB] RSOC Appointments
On 6/25/13 5:10 AM, Arturo Servin wrote: I checked the call for nommitantios (Sent on april 24th 2013 on the ietf-announce) and it does not describe what should be the qualifications of the candidates. I think that this enough to alienate new people (as they may think that they are not good candidates for the position because of lack of experience in the IETF, not being an RFC author, etc.) I would recommend that future announcement of kind of positions have a very clear profile of what it is expected from the candidates in IETF experience, general requirements, etc. In the end, it is like we were filling a job positions in an organization, the difference here is that we are not receiving a salary. Agreed. Hiring without a job description is just silly... Peter -- Peter Saint-Andre https://stpeter.im/
Re: [IAB] RSOC Appointments
Arturo: The original call for nominations did this in two ways. First, it pointed to RFC 6635, which defines the role of the RSOC. Second, it included a list of the top four items that the RSOC is focusing on right now. The current focus of the RSOC is on: 1) Overseeing and assisting the RSE in the process of determining how to best meet the requirements in draft-iab-rfcformatreq. 2) Working with the RSE and the IAB to develop policies n the creation of new RFC Series streams. 3) Periodic reviews of the RFSE performance. 4) Working with the RSE and the IETF Administrative Oversight Committee (IAOC) on the statements of work for contracts related to the RFC Production Center and RFC Publisher. Russ On 6/25/13 5:10 AM, Arturo Servin wrote: I checked the call for nommitantios (Sent on april 24th 2013 on the ietf-announce) and it does not describe what should be the qualifications of the candidates. I think that this enough to alienate new people (as they may think that they are not good candidates for the position because of lack of experience in the IETF, not being an RFC author, etc.) I would recommend that future announcement of kind of positions have a very clear profile of what it is expected from the candidates in IETF experience, general requirements, etc. In the end, it is like we were filling a job positions in an organization, the difference here is that we are not receiving a salary.
Re: [IAB] RSOC Appointments
Russ, Thanks. I see it now. Nevertheless for the untrained eye as mine (and that only scans the important parts of some emails), it would be good to add something like: Requirements for the position are stated in RFC 6635. And probably it won't hurt to add at least a summary of those job requirements. Cheers, as On 6/25/13 2:46 PM, Russ Housley wrote: Arturo: The original call for nominations did this in two ways. First, it pointed to RFC 6635, which defines the role of the RSOC. Second, it included a list of the top four items that the RSOC is focusing on right now. The current focus of the RSOC is on: 1) Overseeing and assisting the RSE in the process of determining how to best meet the requirements in draft-iab-rfcformatreq. 2) Working with the RSE and the IAB to develop policies n the creation of new RFC Series streams. 3) Periodic reviews of the RFSE performance. 4) Working with the RSE and the IETF Administrative Oversight Committee (IAOC) on the statements of work for contracts related to the RFC Production Center and RFC Publisher. Russ On 6/25/13 5:10 AM, Arturo Servin wrote: I checked the call for nommitantios (Sent on april 24th 2013 on the ietf-announce) and it does not describe what should be the qualifications of the candidates. I think that this enough to alienate new people (as they may think that they are not good candidates for the position because of lack of experience in the IETF, not being an RFC author, etc.) I would recommend that future announcement of kind of positions have a very clear profile of what it is expected from the candidates in IETF experience, general requirements, etc. In the end, it is like we were filling a job positions in an organization, the difference here is that we are not receiving a salary.
Re: [IAB] RSOC Appointments
--On Tuesday, June 25, 2013 07:25 + Eggert, Lars l...@netapp.com wrote: On Jun 25, 2013, at 7:53, Randy Bush ra...@psg.com wrote: Congratulations, gentlemen. and they are all male Well, all the volunteers were male, so no real surprise here. (And yes, I wish the volunteer pool had been more diverse. But it wasn't.) I haven't looked at the volunteer pool, but all of the new appointees are also North American or European. Lars, As an outgoing member of the RSOC, it would be inappropriate for me to comment here on the new membership, but I think your comment summarizes a critical issue in the ongoing diversity discussion. Personally, I think there are lessons to be learned for the future... and I wonder how many more times the community needs to discuss them before they are considered normal practice. In particular... Arturo and Peter, There is at least an outline of a job description. It appears in Section 3.1.1 of RFC 6635 and includes: The IAB will designate the membership of the RSOC with the following goals: preserving effective stability; keeping it small enough to be effective, and keeping it large enough to provide general Internet community expertise, specific IETF expertise, publication expertise, and stream expertise. Members [...] are expected to bring a balance between short- and long-term perspectives. One can sensibly argue that the above description, possibly accompanied by comments from the IAB and/or current RSOC members, should have been in the announcement but not that it was somehow missing or secret. My personal view is that more explicitness about the description would have made little or no difference in the applicant pool as long as the announcement itself was made exclusively within IETF community mailing lists. More broadly, anyone in the community with real interest in the topics that the RSOC addresses would presumably have followed at least some of the contents of RFC 6635, 4844, and related documents; the rfc-interest list; a few recent BOFs or their minutes; RFC Editor reports in plenaries; etc. While I have no idea what the IAB did, if I were still on the IAB I certainly would have tried to determine what an applicant already knew about the work of the RSOC and the RFC Series and dropped anyone from within the community who wasn't moderately well-informed from consideration. It would be easy to deduce From those sources that the RFC Series (and hence the RSOC) face major policy and strategic challenges with authors whose technical English writing skills are not up to a professional standard for quality, with internationalization of the documents, with preserving the properties of the RFC Series as an archival collection, with document production and the relationship between generic and format markup, with increased credibility of the Series for academic publication and reference, and so on. Presumably the RSOC, as a group, should have sufficient expertise to be able to oversee investigations and decisions in those areas although RFC 6635 leaves it up to the IAB to determine how important that expertise is relative to other considerations. However, the more general issue is that the description above calls for a wide range of expertise, not all of which need to come from the same person or subset of people. While recruiting candidate IESG members from outside the IETF community would be, IMO, pretty silly, that constraint doesn't apply to the RSOC (give the description above and actual experience). It would have been, at least IMO, reasonable for the IAB to try to recruit potential RSOC members from broader communities, communities in which some of that expertise would be more broadly available than it is among normal IETF participants or the subset of us that carefully track IETF-announce or are active on this list. As people have commented in other contexts, if one cares, in practice, about diversity then part of the solution to issues of underrepresentation is broadening the applicant pool to include additional populations. Now, the IAB, in its wisdom, chose to not engage in such a broader recruiting effort. I have no idea whether they considered and discussed that option. If the community thinks that diversity is really important enough, then the various appointing bodies (including the Nomcom) should to told to consider --and maybe even report back on-- whether particular positions justify a broader search because posting announcements to IETF lists may not inform the best range of potential candidates. If the community believes that diversity is important and that members of appointing bodies aren't taking it seriously enough, that should be made clear to the Nomcom (remembering that the Nomcom has the right to recruit rather than waiting passively for nominations and the right --and maybe the obligation-- to inquire, when considering incumbents, about why
Re: [IAB] RSOC Appointments
Hola Russ, At 06:46 25-06-2013, Russ Housley wrote: The original call for nominations did this in two ways. First, it pointed to RFC 6635, which defines the role of the RSOC. Second, it included a list of the top four items that the RSOC is focusing on right now. What Mr Servin is trying to understand is how can people who are not part of the good ol' boys network (see http://www.ietf.org/mail-archive/web/diversity/current/msg00018.html ) know the desirable experience and general requirements to have a fair chance when they apply for the job. If the suggestion is that people read RFC 6635 I don't think that it is not good enough. I understand that the IAB may be reluctant [1] to talk to the Internet Community about all this. Regards, -sm 1. http://www.youtube.com/watch?v=lhmjnYKlVnM
Re: RSOC Appointments
Congratulations, gentlemen. and they are all male
RE: RSOC Appointments
But they have different ages, IQs, and shoe sizes. Yours Irrespectively, John -Original Message- From: ietf-boun...@ietf.org [mailto:ietf-boun...@ietf.org] On Behalf Of Randy Bush Sent: Monday, June 24, 2013 10:54 PM To: Fred Baker (fred) Cc: ietf list; Nevil Brownlee; Bob Hinden; IAB; Joe Hildebrand (jhildebr); Alexey Melnikov; Bernard Aboba Subject: Re: RSOC Appointments Congratulations, gentlemen. and they are all male
RSOC Appointments
The IAB extends many thanks to the community members that were willing to serve on the RSOC for their ongoing support of the RFC Series and the RFC Series Editor. The IAB especially thanks the current RSOC members for their many contributions. After reviewing the strong list of individuals who offered to serve on the RSOC, the IAB is appointing the following people to serve on the RSOC: Nevil Brownlee, Tony Hansen, Joe Hildebrandt, Bob Hinden, Alexey Melnikov, Bernard Aboba (an IAB member), and Joel Halpern (an IAB member). In addition, Ray Pelletier will continue to serve as liaison from the IAOC to the RSOC. The IAB sincerely thanks all of the people that offered to serve on the RSOC. The IAB particularly thanks the following current RSOC members that will be stepping off the committee during IETF 87 in Berlin: Fred Baker, Ole Jacobsen, John Klensin, and Olaf Kolkman. On behalf of the IAB, Russ Housley IAB Chair
Re: RSOC Appointments
Congratulations, gentlemen. On Jun 24, 2013, at 5:35 PM, IAB Chair iab-ch...@iab.org wrote: Nevil Brownlee, Tony Hansen, Joe Hildebrandt, Bob Hinden, Alexey Melnikov, Bernard Aboba (an IAB member), and Joel Halpern (an IAB member).
RSOC Appointments
The IAB extends many thanks to the community members that were willing to serve on the RSOC for their ongoing support of the RFC Series and the RFC Series Editor. The IAB especially thanks the current RSOC members for their many contributions. After reviewing the strong list of individuals who offered to serve on the RSOC, the IAB is appointing the following people to serve on the RSOC: Nevil Brownlee, Tony Hansen, Joe Hildebrandt, Bob Hinden, Alexey Melnikov, Bernard Aboba (an IAB member), and Joel Halpern (an IAB member). In addition, Ray Pelletier will continue to serve as liaison from the IAOC to the RSOC. The IAB sincerely thanks all of the people that offered to serve on the RSOC. The IAB particularly thanks the following current RSOC members that will be stepping off the committee during IETF 87 in Berlin: Fred Baker, Ole Jacobsen, John Klensin, and Olaf Kolkman. On behalf of the IAB, Russ Housley IAB Chair
