- ripe-list - mailman.ripe.net

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

Network security and Brussels
by Gordon Lennox 14 Sep '17

14 Sep '17

The Commission has just published a little bunch of things on security. As a very simple guide: a “Communication” is about what could happen, a “Report” is about what has happened and the “Regulation” is about changing ENISA. A lot of reading! Too much? But of interest to various WGs, including of course the Cooperation WG and the new IoT community? So: A COMMUNICATION from the Commission to the European Parliament and the Council. Making the most of NIS – towards the effective implementation of Directive (EU) 2016/1148 concerning measures for a high common level of security of network and information systems across the Union https://ec.europa.eu/transparency/regdoc/rep/1/2017/EN/COM-2017-476-F1-EN-M… https://ec.europa.eu/transparency/regdoc/rep/1/2017/EN/COM-2017-476-F1-EN-A… A REPORT from the Commission to the European Parliament and the Council assessing the extent to which member states have taken the necessary measures to comply with Directive 2013/40/EU on attacks against information systems and replacing Council Framework Decision 2005/222/JHA https://ec.europa.eu/transparency/regdoc/rep/1/2017/EN/COM-2017-474-F1-EN-M… A REPORT from the Commission to the European Parliament and the Council on the evaluation of the European Union Agency for Network and Information Security (ENISA) https://ec.europa.eu/transparency/regdoc/rep/1/2017/EN/COM-2017-478-F1-EN-M… A Proposal for a REGULATION of the European Parliament and of the Council on ENISA, the "EU Cybersecurity Agency", and repealing Regulation (EU) 526/2013, and on Information and Communication Technology cybersecurity certification (''Cybersecurity Act'') https://ec.europa.eu/transparency/regdoc/rep/1/2017/EN/COM-2017-477-F1-EN-M… Gordon

1 0

Global Consultation on Identifier Technical Health Indicators (ITHI) Project
by Nick Hyrka 13 Sep '17

13 Sep '17

This message is sent on behalf of the Number Resource Organization. The Number Resource Organization (NRO) has developed a proposal for ITHI risk identification and definition in response to an ongoing ICANN initiative. Each Regional Internet Registry (RIR) is responsible for ensuring the accuracy of its registry data. This is critical to the reliability of the RIR Whois databases which provide access to the public data of the Registry. For the purposes of measuring the state of the data, accuracy has been defined as “comprehensive, correct, and current”. The Registration Services coordination (RSCG) and Engineering coordination groups (ECG) have developed recommendations for how the RIRs can identify and measure risk associated with registry data accuracy. We are now seeking feedback on the NRO ITHI project proposal, specifically on the definition of the risks and measurements to report on registry data accuracy. Proposal for ITHI risk identification and definition: https://www.nro.net/wp-content/uploads/RSCG_ITHI_Project_Proposal.pdf The deadline for providing feedback is 12 December 2017. Community feedback and discussion will be conducted on the <ithi-consult(a)nro.net> mailing list. You can subscribe to the global mailing list at: https://www.nro.net/mailman/listinfo/ithi-consult Key points for discussion: - The proposed approach - The proposed measurement matrix - Other information such as how often to measure, where to post results, what formats to share results Other links ICANN ITHI page: www.icann.org/ithi ITHI presentation from ICANN 57: https://www.icann.org/en/system/files/files/ithi-icann57-07nov16-en.pdf

1 0

SAFNOG-3: Attendees & Speakers
by Mark Tinka 03 Sep '17

03 Sep '17

Hello all. A list of all currently registered attendees is available for your inspection here: http://safnog.org/attendees.php/ This list is updated daily, so do check regularly to see if there are any personalities you would like to meet at this year's SAFNOG meeting. Also, details on each of the speakers at this year's meeting are available here: http://safnog.org/speakers.html With just 2 days to go, we look forward to seeing you all in Durban! Cheers, Mark Tinka On Behalf of the SAFNOG Management Committee

1 0

UKNOF38 Registration Deadline approaching
by Denesh Bhabuta 25 Aug '17

25 Aug '17

Hi For those interested... A reminder that UKNOF38 (12 September, Sheffield) Early Bird (FREE) registration ends in three days - on Monday 28 August. If you have not yet registered and would like to attend, please register via https://uknof.uk/register38 With thanks to UKNOF38 sponsors - Corero (Premium and Pints n' Packets Exhibitor), ThousandEyes (Premium), IPv4 Market Group (Associate), Laser 2000 (Associate), ProLabs (Associate), RIPE NCC (Contributor), LONAP (Pints n' Packets Supporter), Bogons (Partner), Portfast (Partner) - for their financial and in-kind support, allowing UKNOF38 to remain mainly free to register to attend. Regards Denesh

1 0

Last call for presentations and Draft programme for RIPE 75
by Benno Overeinder 25 Aug '17

25 Aug '17

Colleagues, A list of currently accepted RIPE 75 presentations is now published at: https://ripe75.ripe.net/programme/meeting-plan/draft-programme/ There are still plenary, BoF, tutorial and workshop slots remaining for the final RIPE 75 programme and RIPE Programme Committee will accept new proposals until *6 September 2017*. This is our last call for you to submit your proposals. You can find the CFP for RIPE 75 below or at https://ripe75.ripe.net/submit-topic/cfp/, for your proposals for plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings. Update to UAE DTCM requirments: It is now confirmed that a photocopy of speakers' passports is *not* required. Non-UAE/international speakers need only to provide: * Passport number * Date of birth * A short biography (at least 60 words) Residents of the UAE are required to upload a copy of their Emirates ID (in jpeg format). More details are available here: https://ripe75.ripe.net/attend/dctm-requirements Kind regards, Benno Overeinder RIPE PC Chair https://ripe75.ripe.net/ripe-pc/ -------------------->>><<<-------------------- Call for Presentations A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. RIPE 75 will take place from 22-26 October in Dubai, UAE. The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 75. See the full descriptions of the different presentation formats, https://ripe75.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than *6 September 2017*. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange - Connected Things (aka. Internet of Things - IoT) Speakers Due to UAE law, confirmed Non-UAE/international speakers need to provide: * Passport number * Date of birth * A short biography (at least 60 words) Residents of the UAE are required to upload a copy of their Emirates ID (in jpeg format). More details are available here: https://ripe75.ripe.net/attend/dctm-requirements Please also note that speakers do not receive any discount or funding towards the meeting fee at RIPE Meetings. Submissions RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and not attempt a product demonstration. Presenters should indicate how much time they will require. In general, the time allocated for the different presentation formats is as follows: - Plenary presentations: 20-25 minutes presentation with 5-10 minutes discussion - Tutorials: up to two hours (Monday morning) - Workshops: one hour (during evening sessions) to two hours (Monday morning) - BoFs: approximately one hour - Lightning talks: 10 minutes total for both presentation and any discussion The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe75.ripe.net/submit-topic/ - Lightning talks should also be submitted using the meeting submission system (https://ripe75.ripe.net/submit-topic/) and can be submitted any time up to and including the meeting week. The allocation of lightning talks will be announced on short notice, in some cases on the same day but often one day prior to the time slot allocated. - Presenters who propose a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. - All presentation proposals will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panellists, presenters and moderators. If you have any questions or requests concerning content submissions, please email pc [at] ripe [dot] net. -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

1 0