- ripe-list - mailman.ripe.net

Re: [ripe-list] RIPE Accountability Task Force Update at RIPE, 75
by Malcolm Hutty 21 Oct '17

21 Oct '17

On 19/10/2017 12:28, ripe-list-request(a)ripe.net wrote: > What Jim and I were both trying to say, and obviously something got lost > in translation, is that ever since the PDP's inception the NCC has > carried out the policies as formulated by the RIPE Community, without > exception, even when this has cost the RIPE NCC? membership considerable > amounts of money. However, because we are bound by fiduciary duty (ie we > mustn't do anything that's illegal under Dutch law) we *cannot* agree to > do absolutely *anything* that might come out of the policy process. To > take a ludicrous example, suppose the community asked us to sign an MOU > with a Colombian drug cartel, something which under the PDP they could > actually ask us to do, we would decline courteously. Nigel, I don't think anyone would seriously suggest that the NCC ought to be bound to implement absolutely anything that comes out of the RIPE community without limitation. You are rather tilting at a straw man of your own creation here. However, when the taskforce asked NCC staff to look into this, they discovered (to their own surprise) that the NCC has no formal document of any nature that sets out a normative expectation that the RIPE NCC will so much as take community policy into account. That seems a curious omission. You are quite right to point out that the NCC has faithfully followed the community's will, and while you and your fellow Board members remain in charge, I am sure it will continue to do so. But part of the purpose of this exercise is to help create the conditions that make it more likely that your legacy in this respect is honoured by those that succeed you. Nothing we do can guarantee that will happen, but writing down that the NCC's history of implementing community policy is more than a mere coincidence of opinion will both help guide future Boards and give ammunition to Board members against anyone who argues that the NCC should do otherwise. Jim correctly pointed out that the community itself, not being an entity with legal personality, cannot sign an MoU. That removes one option for how such a normative statement might be recorded - but there are several others. The NCC does, after all, have contracts with its members. Personally, I think a better idea that I would like to see considered is to write into the RIPE NCC's governing statutes that one of the purposes of the NCC is to implement RIPE community policy. Of course this phrase would have to be suitable qualified to avoid the pitfall you mention, but I do not think that insurmountable, or even difficult: the NCC does have lawyers, after all. Finally, may I gently suggest that the extremely defensive attitude of some prominent community members to the work of this Taskforce is not a good look. Most of us are reasonably long-standing members of the community ourselves, and fully share both its values and well-proven way of doing things. Our aim is to support this community, not to undermine it. As William has said, nothing we come up with will simply go into effect: we will simply publish some systematic observations and suggestions for the community's consideration. Perhaps you might try to remain a little more open to the possibility that our report might be worth the trouble of reading, maybe even contain one or two useful ideas? Kind Regards, Malcolm. -- Malcolm Hutty | tel: +44 20 7645 3523 Head of Public Affairs | Read the LINX Public Affairs blog London Internet Exchange | http://publicaffairs.linx.net/ London Internet Exchange Ltd Monument Place, 24 Monument Street London EC3R 8AJ Company Registered in England No. 3137929 Trinity Court, Trinity Street, Peterborough PE1 1DA

3 2

RIPE 75 Programme Committee Nominations
by Benno Overeinder 19 Oct '17

19 Oct '17

Dear Friends and Colleagues, The RIPE Programme Committee is responsible for recruiting and selecting presentations for the RIPE Meeting Plenary sessions. As the term of two RIPE PC members end, we are looking for new members in Autumn 2017 who will be elected by the RIPE community at RIPE 75 in Dubai. There are currently two seats up for election to the RIPE PC. Please send nominations, with a biography, statement of interest and photograph, to pc(a)ripe.net. The Charter of the RIPE Programme Committee (https://www.ripe.net/ripe/docs/ripe-pc-charter) provides more information about the composition and roles of the RIPE PC. Note that the schedule of RIPE 75 meeting starts on Sunday, and the days we are closing nominations and voting has been pushed one day forward (earlier). Nominations for the RIPE 75 PC elections can be sent in from today until Monday October 23rd, 15:30 GST. We will announce the PC elections at the RIPE meeting opening sessions, but interested parties can nominate themselves from now. We will close candidate nominations on Monday at 15:30 GST (GMT+4), and publish the biographies on the RIPE Meeting web site. Candidates (or their stand-ins) can present themselves at the start of the Monday 16:00 GST session. The RIPE PC online voting system will be open from Monday October 23rd, 16:00 GST until Wednesday October 25th, 17:30 GST, for the community members to cast their votes. The total voting numbers may be public. The official announcement of the elected RIPE PC members will be on Thursday morning, the 26th October, at the start of the 11:00 GST closing plenary session. Questions about the RIPE PC can be sent to pc(a)ripe.net. Regards, Brian and Benno on behalf of the RIPE PC -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

1 0

RIPE Accountability Task Force Update at RIPE 75
by William Sylvester 19 Oct '17

19 Oct '17

Dear colleagues, Over the past year, our task force has been reviewing the structures, documentation, and processes of RIPE to identify our accountability as an organization. At the last RIPE meeting, we finalized our mission and scope which we continue to work against. We will be giving an update on our work at RIPE 75, on Monday 23 October at 16:00 local time (UTC+4). We invite you to attend and encourage you to comment from the floor or via remote participation. We have allocated plenty of time for comments and we'd like to hear your thoughts.   In case you are not familiar with the task force and our work, here are a few key details. The task force was established at RIPE 73 in Madrid. Our focus is to identify the areas of accountability and to report back to the community with a review of RIPE's accountability. It is our goal to provide a final report which will include suggestions where the task force sees opportunity for improvement. The greater RIPE community will then decide how to respond or what actions to take. The task force will not be making corrective changes, that will be the responsibility of the community. We are mindful of the impact our recommendations might have on the community. Our intent is not to create bureaucracy, but instead to simplify and empower the values that have established RIPE and sustained the community for so many years. With that in mind, we have a few questions that have come up in our recent discussions that we would like to pose to the community. You can reply on this mailing list, or give us your feedback during our presentation at RIPE 75. 1. Do you think the "public benefit" or "the greater good" is a core aspirational factor in decisions made by the RIPE community? Alternatively, are RIPE community members merely working/cooperating for their own benefit? (If the community is only working for its own benefit, why have a last /8 policy that benefits newcomers, for example). 2. There is no explicit obligation anywhere that the RIPE NCC will adhere to policies developed by the RIPE community. Strictly speaking, the RIPE NCC is accountable to its membership only. Does the community feel that the RIPE NCC should make a declaration or perhaps sign an MoU stating that it will follow RIPE community policies? 3. There is no definition of consensus as it is used within the RIPE community. Is this something that is worth documenting? We will share some more details on this mailing list after our presentation at RIPE 75. We look forward to seeing everyone in Dubai next week and to receive community feedback on our progress. On behalf of the Accountability Task Force, William Sylvester, Chair

9 13

Announcing Diversity Task Force draft charter, plus activities at RIPE 75
by Shane Kerr 19 Oct '17

19 Oct '17

Dear RIPE Colleagues, On behalf of the Diversity Task Force (TF), we would like to ask for feedback on the draft charter: https://www.ripe.net/participate/ripe/tf/ripe-diversity-task-force As mentioned on the proposed charter page, we have a mailing list and encourage anyone interested to join: https://lists.ripe.net/mailman/listinfo/diversity We also have some activities planned at the RIPE 75 meeting in Dubai next week: * We will give a short report on our work since RIPE 74, in a lightning talk slot during the plenary session. * For longer discussions and as another venue for giving input, we will be holding a Diversity BoF on Sunday, 22 October from 18:00 to 19:00. https://ripe75.ripe.net/programme/meeting-plan/bof/ * And for those who want to become more active, we have Task Force meeting on Monday, 23 October from 18:00 to 19:00. On behalf of the Diversity Task Force, -- Shane Kerr

3 2

Buy Genuine/fake passports, drivers lisence, ids (puredocumentation@gmail.com)
by legit docu 18 Oct '17

18 Oct '17

WE ARE BEST PRODUCERS OF Ristered and unregistered passport of all countries (puredocumentation(a)gmail.com).visas,biometric passport,degrees,drivers license,I.D cards.Training certificates M GCSE, A-levels, High School Diploma Certificates ,GMAT, MCAT, and LSAT Examination Certificates , Novelty Birth, Marriage, and Death Certificates , Novelty Passports and New Identity Packages ,Replicated, False Degrees/Diplomas from most post-secondary institutions from around the world (we have over 3000 templates on file) all designed to look 100% identical to the original.Custom Printing (if we do not already have the template on file – simply email us a copy and we can make any alterations/modifications as per your directions).second, citizenship,identity, identification, documents, diplomatic,nationality, how to, where to, get, obtain, buy, purchase, make,build, a, passport, i.d,British, Honduras, UK, USA, us, u.s.,Canada, Canadian,foreign, visa, Swiss, card,ids, document, getting,visas, cards, foreign .(puredocumentation(a)gmail.com) -WE DO OFFER A LEGITIMATE SERVICE:- Contact E-mail....................puredocumentation(a)gmail.com viber contact...................+1(240)389-5438 skype id..............................live:gostavkozlov Contact E-mail...................... gostavkozlov(a)outlook.com we offer a service to help you through to meet your goals, we can help you with. Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

1 0

RIPE NCC Community Projects Fund Selection Committee Chosen
by Axel Pawlik 02 Oct '17

02 Oct '17

Dear colleagues, We are pleased to announce the names of the first RIPE NCC Community Projects Fund Selection Committee. Chosen from a list of submitted nominations by the RIPE NCC Executive Board, the community members are: Nuno Garcia Mieke van Heesewijk Andreas Larson They will join Salam Yamout from the RIPE NCC Executive Board to complete the selection committee. The Executive Board sincerely thanks all those who put themselves forward to be on the committee and warmly welcome the new committee members. The committee is responsible for reviewing applications for projects supporting Internet resilience and operations from late November until late December 2017. These members have committed to serving a minimum term of one year (and a maximum of three) to ensure continuity. The call for funding applications opens on Sunday, 22 October and the Fund will be formally introduced in the RIPE NCC Services Working Group session at RIPE 75 in Dubai. More information on the Fund can be found at: <https://www.ripe.net/support/cpf/ripe-ncc-community-projects-fund> Regards, Axel Pawlik Managing Director RIPE NCC

1 0

ASO AC Calls For Nominations to Seat 9 on the ICANN Board of Directors
by Nick Hyrka 02 Oct '17

02 Oct '17

This message is sent on behalf of the Number Resource Organization. In line with the ICANN Address Supporting Organization (ASO) Memorandum of Understanding (MoU) and the ICANN Bylaws, the Address Supporting Organization Address Council (ASO AC) is calling for nominations to Seat 9 of the ICANN Board of Directors. The selected candidate will serve for a three-year term, which will begin at the conclusion of the ICANN Annual General Assembly during the ICANN 63 meeting. ICANN 63 is currently scheduled for October 20-26, 2018, in Barcelona, Spain. Eligibility Requirements All nominated candidates must meet the selection criteria and conflict of interest requirements as outlined in Article 7 of the ICANN Bylaws. The selected candidate will undergo an independent due diligence review by an ICANN contractor, and announcement of the candidate will follow once this review has been successfully completed. Nomination Process Community members are invited to submit nominations by email to nominations [at] aso [dot] icann [dot] org by Sunday, 17 December 2017 at 23:59 UTC. Nominations must include the following information: - The full name of the person being nominated - Contact email address for the person being nominated - Contact telephone number (if available) of the person being nominated - The full name of the person making the nomination - Contact email address for the person making the nomination - Contact telephone number of the person making the nomination Regional Restrictions The ICANN Bylaws state that the directors selected by a Supporting Organization (SO) for its assigned Board seat(s) cannot reside in the same geographic region (see Section 7.2:c). The current ASO AC selection for Seat 10, Akinori Maemura, resides in the APNIC region. Therefore, no nominations for Seat 9 will be accepted from candidates residing in the APNIC region. Important Dates Nomination Phase: 2 October 2017 – 17 December 2017 Comment Phase: 18 December 2017 – 18 March 2018 Interview Phase: 17 January 2018 – 18 March 2018 Selection Phase: 19 March 2018 – 18 April 2018 Due Diligence Review: 19 April 2018 – 17 May 2018 Announcement: Around 19 May 2018 Further Information - For further information and updated announcements on the election process, see the dedicated 2017 ICANN Board Election page on the ASO website. - Detailed procedures for election of individuals to the ICANN Board of Directors by the ASO AC can be found in Section 9 of the ASO AC Operating Procedures. If you have any questions about the elections or the election process, please contact secretariat [at] nro [dot] net.

1 0

DNS Root Zone KSK Rollover postponed
by Axel Pawlik 29 Sep '17

29 Sep '17

Dear colleagues, Yesterday, ICANN announced that it is postponing the plan to roll, or change, the 'apex' cryptographic key used in the DNSSEC protocol, commonly known as the Root Zone KSK (Key Signing Key). The KSK Rollover was due to occur on 11 October 2017. This will now be postponed to allow more time for network operators using DNSSEC-validating resolvers to update their systems with the new KSK. A new date has not yet been set, however ICANN’s announcement says it is tentatively aiming for Q1 2018: https://www.icann.org/news/announcement-2017-09-27-en All network operators using DNSSEC-validating resolvers are encouraged to update their DNS resolver systems with the new KSK in preparation for the new Rollover date. If you have additional questions, please email ICANN: <globalsupport(a)icann.org> with "KSK Rollover" in the subject line. Regards, Axel Pawlik RIPE NCC

1 0

[news] RIPE Policy Proposals - September Update
by Marco Schmidt 29 Sep '17

29 Sep '17

Dear colleagues, Here is our monthly overview of open policy proposals and their stage in the RIPE Policy Development Process (PDP). If you wish to join the discussion about a particular proposal, please do so on the relevant working group mailing list. Proposals Open for Discussion: NEW: 2017-02, "Regular abuse-c Validation" NEW: 2017-03, "Reducing Initial IPv4 Allocation, Aiming to Preserve a Minimum of IPv4 Space for Newcomers" Proposals Awaiting Input: 2016-04, "IPv6 PI Sub-assignment Clarification" Proposal Withdrawn: 2017-01, "Publish statistics on Intra-RIR Legacy updates" Proposal Overview: NEW PROPOSAL: 2017-02, "Regular abuse-c Validation" OVERVIEW: The goal of this proposal is to give the RIPE NCC a mandate to regularly validate "abuse-c:" information and to follow up in cases where contact information is found to be invalid. STATUS: Discussion Phase WHERE TO COMMENT: Anti-Abuse Working Group: anti-abuse-wg(a)ripe.net DEADLINE: 6 October 2017 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2017-02 NEW PROPOSAL: 2017-03, "Reducing Initial IPv4 Allocation, Aiming to Preserve a Minimum of IPv4 Space for Newcomers " OVERVIEW: The goal of this proposal is to reduce the IPv4 allocations made by the RIPE NCC to a /24 (currently a /22) and only to LIRs that have not received an IPv4 allocation directly from the RIPE NCC before. STATUS: Discussion Phase WHERE TO COMMENT: Address Policy Working Group: address-policy-wg(a)ripe.net DEADLINE: 20 October 2017 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2017-03 ===== The following proposal is awaiting input before they can go any further in the PDP. PROPOSAL: 2016-04, "IPv6 PI Sub-assignment Clarification" OVERVIEW: The goal of this proposal is to define sub-assignments in IPv6 PI assignments as subnets of /64 and shorter. RIPE NCC IMPACT ANALYSIS: Explains feasibility and possible side effects. STATUS: Review Phase – Creating impact analysis for new version FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-04 ===== The following proposal has been withdrawn. PROPOSAL: 2017-01, "Publish statistics on Intra-RIR Legacy updates" OVERVIEW: This proposal aimed to add the requirement that the RIPE NCC publish all changes to the holdership of legacy resources in the existing transfer statistics. STATUS: Withdrawn. The proposer didn't see enough community support, especially from Legacy Resource Holders as the parties that would be most affected. FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2017-01 The RIPE NCC provides an overview of current RIPE Policy Proposals here: https://www.ripe.net/participate/policies/current-proposals/current-policy-… We look forward to your involvement in the PDP. Kind regards, Marco Schmidt RIPE Policy Development Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

1 0

New on RIPE Labs: How informal channels are important for network coordination
by Mirjam Kuehne 27 Sep '17

27 Sep '17

Dear colleagues, Please find this new article on RIPE Labs by Uta Meier-Hahn: "When Internet Interconnection Trouble Occurs, Immediate Coordination Kicks in" https://labs.ripe.net/Members/uta_meier_hahn/when-internet-interconnection-… Kind regards, Mirjam Kuhne RIPE NCC

1 0