ipv6-wg

Download

ipv6-wg@ripe.net

April 2015

5 participants
2 discussions

Chair replacement procedure for ipv6-wg
by Dave Wilson 15 May '15

15 May '15

Hi all, You might remember from the last RIPE meeting that each working group had to finalise chair selection procedures. Because we were changing chairs anyway, ipv6-wg got to wait for one more meeting. Since the other working groups have gone through that process, however, we can use that to our advantage. Instead of starting from scratch, we propose to use a procedure which has already been discussed by a working group. The one we've chosen, because it seems very close to what we discussed at RIPE 69, is the procedure used by anti-abuse-wg. I hope this draft is already "good enough" for us to adopt as a result; if so, it'll save us repeating work that's already been done several times over in other WGs. We have this on the agenda for RIPE 70, and I hope we'll be able to adopt it then. Best regards, Dave ===(cut here)=== Note on Language: Throughout this document the word Chair shall be used for both Chairs and Co-Chairs. ** Introduction: This document outlines procedures dealing with the tenure of RIPE Working Group Chairs. It applies to all RIPE Working Groups. ** WG Chair Term: The term of a WG Chair is three years. A current chair may stand for re-selection at the end of their term. A WG Chair may resign voluntarily at any time. ** Selection of a WG Chair: WG Chair vacancies, along with a call for candidates, must be announced on the WG mailing list at least one month in advance of the date upon which the selection will be held. The announcement should set a closing date for candidates. A WG may request that a WG Chair vacancy be opened so long as the addition of a new Chair would not cause the number of Chairs of that WG to exceed three. WG Chairs are elected at WG sessions at RIPE meetings. Anyone physically present at the WG session is eligible to participate in the selection process. The candidate does not need to be physically present at the WG session. If possible the Chair should be elected by acclamation by the WG or by consensus after discussion. If the result is unclear, then a secret ballot should be held. In the case of a ballot, votes will be counted by RIPE NCC Staff and/or Chairs of other WGs. The result will be determined by simple majority. ** Removal of a WG Chair: A WG Chair may be unable to fulfil their duties as described in this document or otherwise fail to serve the WG and the community. With the endorsement of a significant share of the WG, a vote of no confidence may be initiated. Before a vote of no confidence is taken, due effort should be made to address the issue(s) leading to the vote. The right of reply must be given to all parties involved in the procedure. If this effort fails to resolve the issue, the vote may proceed. The vote must be requested on the WG mailing list at least one week in advance of the WG Session at a RIPE meeting and should take place during the WG session. Anyone physically present at the WG session may take part in the vote. The vote should be conducted by secret ballot and votes counted by RIPE NCC Staff and/or WG Chairs of other WGs. The result will be determined by simple majority. If the vote of no confidence in a WG Chair is passed, the seat is vacated and the WG Chair is not eligible for stand for re-selection. ** No Chair: If a working group is left with no Chair, e.g. due to the resignation or removal of the sole WG Chair, then the WG may elect an interim WG Chair according to the selection procedures specified above, but with candidates nominated at the WG session. An interim WG Chair must resign at the next WG session, but may stand for re-selection. ** Staggered Introduction: For the purposes of staggering the introduction of this policy, in the case where all co-Chairs of a WG have served for more than the standard WG Chair term limit, an optional waiver is given to these WGs to allow them to schedule the automatic resignations of their Chairs over the two RIPE meetings immediately following the adoption of this policy. If the WG decides to avail of this waiver, it is the responsibility of the WG to decide in what order its co-Chairs should stand down. ===(cut here)=== -- Dave Wilson, Service Desk Manager web: www.heanet.ie HEAnet Ltd, 5 George's Dock, IFSC, Dublin 1 tel: +353-1-660-9040 Registered in Ireland, no 275301 fax: +353-1-660-3666

5 6

RIPE70 Draft Agenda
by Jen Linkova 14 Apr '15

14 Apr '15

Dear IPv6 WG members, RIPE70 is less than a month away and IPv6 WG is going to have two sessions, both on Thu, May 14th: - session #1: 09:00 - 10:30 (overlaps with DNS WG session); - session #2: 16:00 - 17:30 (overlaps with Database WG session). Please find the draft agenda below. NB: This time we are planning to have some informal discussion on IPv6 deployment bumps so please, please get ready to actively participate in the session! === Session 1, Thu, May 14th, 9:00 - 10:30 === A. Administrativia B. "HTTP state management (cookie) in an IPv6 world: apply caution!", Eric Vynke C. “Use Cases for IPv6 Extension Headers - Let's do some Marketing”, Wilhelm Boeddinghaus D. "OS Behavior in Contradicting Environments" , Enno Rey E. “IPv6 for ISP”, Aaron Hughes === Session2, Thu, May 14thm 16:00 - 17:30 === A. Administrativia B. WG Chair replacement procedure discussion C. "IPv6 - who is and who isn't" Geoff Huston D. Lighting talks: d1. "Lost stars”, Natalie Trenaman, d2. “Software & IPv6”, Natalie Trenaman d3. "554,631 - what's the next IPV6 speed-bump?" Jan Zorz E. IPv6 deployment bumps discussion/brainstorming session === If you have any questions/comments/concerns please do not hesitate to contact WG chairs (ipv6-wg-chairs(a)ripe.net) or reply to this email. -- SY, Jen Linkova aka Furry - on behalf of IPv6 WG chairs.

1 0