Dear colleagues,
The RIPE Accountability Task Force was formed in October 2016 following a
presentation <https://ripe73.ripe.net/archives/video/1248/> at RIPE 73.
Since then task force has agreed on a draft scope (below) and published at:
https://www.ripe.net/participate/ripe/tf/ripe-accountability-task-force
We invite RIPE community members to send any feedback to this mailing list
before we consider the scope final.
We are currently undertaking a review of the community's procedures,
documentation and structures in alignment with the draft scope and we will
communicate our progress on this soon too.
Please let us know what you think.
Kind regards
Filiz Yilmaz / William Sylvester
RIPE Accountability Task Force Chairs
----
*Draft Scope*
The RIPE Accountability Task Force agreed to:
- Review existing RIPE community structures, documentation and processes
to ensure they are accountable and in alignment with RIPE values
- Document existing RIPE community structures or processes where needed
- Identify potential gaps where RIPE accountability could be improved or
strengthened
- Publish recommendations for the RIPE community
- Identify areas where communications efforts or materials may be
required
The scope of the task force is limited to an examination of the RIPE
community.
----
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:
2016-05, "Synchronising the Initial and Subsequent IPv6 Allocation Policies"
Proposals Accepted:
2015-04, "RIPE Resource Transfer Policies"
Proposals Awaiting Input:
2016-04, "IPv6 PI Sub-assignment Clarification"
Proposal Overview:
PROPOSAL: 2016-05, "Synchronising the Initial and Subsequent IPv6 Allocation Policies"
OVERVIEW: The goal of this proposal is to match the subsequent IPv6 allocation requirements with the initial allocation requirements.
RIPE NCC IMPACT ANALYSIS: Explains the requirements to request a subsequent IPv6 allocation.
STATUS: Last Call
WHERE TO COMMENT: Address Policy Working Group: address-policy-wg(a)ripe.net
DEADLINE: 28 March 2017
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-05
===============
The following proposal has been accepted and is currently under implementation:
PROPOSAL: 2015-04, "RIPE Resource Transfer Policies"
OVERVIEW: Creates a single transfer policy with all relevant information on the transfer of Internet number resources, replacing text in several RIPE Policies. Also introduces a 24-month holding period for IPv4 addresses and 16-bit ASNs after any change of holdership.
STATUS: Accepted
IMPLEMENTATION: Ongoing, until Mid June 2017
IMPLEMENTATION PLAN:
https://www.ripe.net/manage-ips-and-asns/resource-management/policy-impleme…
================
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 – Rewriting Proposal
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-04
=====
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
Have you heard about the RIPE Fellowship yet?
Earlier this year, we launched the RIPE Fellowship as part of our
ongoing efforts to make RIPE Meetings more inclusive.
The purpose of the fellowship is to support successful candidates in
their professional or academic career development, allow them to
participate in policy discussions, and to network with industry peers
and others at the event.
We are excited to have five talented individuals from across the RIPE
NCC service region join us at RIPE 74 (8-12 May in Budapest) as RIPE
Fellows.
Congratulations:
- Jie Li, University College London, UK
- Jad El Cham, Data Consult, Lebanon
- Ella Titova, K-Telecom CJSC, Armenia
- Vladimir Svanadze, Internet Development Initiative - IDI, Georgia
- Magnus Frühling, Freifunk Frankfurt am Main e. V, Germany
RIPE Fellows receive:
- Round-trip airfare to the meeting
- A full-week meeting ticket
- Hotel accommodation for the meeting week
- The opportunity to partner with a RIPE community mentor
We will accept applications for the RIPE Fellowship at RIPE 75 (22-26
October 2017, Dubai) in August. Please keep an eye on your inbox for the
announcement.
You can find out more about the RIPE Fellowship at:
https://www.ripe.net/fellowship
We also have a short post up on RIPE Labs:
https://labs.ripe.net/Members/agowland/apply-now-for-new-ripe-fellowship-pr…
Kind regards,
Nick Hyrka
Communications Manager
RIPE NCC
www.ripe.net
This message is sent on behalf of the Number Resource Organization
(NRO).
-----------------------------------------------------------------------
Dear colleagues,
This is an invitation to participate as observers of the next IANA
Review Committee (IANA RC) teleconference to be held on Wednesday March
15th 2017 at 10:00 AM UTC. Webex information below.
More Information about the IANA RC can be found at:
https://www.nro.net/iana-numbering-services-review-committee/
Regards
German Valdez
NRO
===
Draft Agenda
0. Welcome
1. Roll Call
2. Review Open Actions
3. Agreement on Review Committee Scope
4. Internal Operational Procedures
5. IANA Performance Report
5.1 performance matrix presented by RC RIR staff members
5.2 Gap review of performance matrix
5.3 Discussion of metrics and measurement
5.4 Discussion of current IANA measurements
5.4 Gap review of current IANA performance measures
5.5 Contents of IANA performance review document
6. Review process 6.1 Review process internal to the RC
6.2 Process for community feed back for performance review report
6.3 Discussion of operating procedures changes for section 5 updates
(if any)
7. Any other community engagement
8. Next Meeting
9. AOB
10. Adjourn
2nd IANA Review Committee Meeting
Wednesday, 15 March 2017
10:00 am | UTC | 1 hr 45 mins
Join WebEx meeting
https://apnic.webex.com/apnic/j.php?MTID=m38f13c81ebf643af63bd961e341e054f
Meeting number:578 906 568
Meeting password:ianarc
Join by phone:
https://apnic.webex.com/apnic/globalcallin.php
Dear colleagues,
Please note the approaching deadline of *12 March 2017* for RIPE 74
plenary programme submissions.
You can find the CFP for RIPE 74 below or at
https://ripe74.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.
Kind regards,
Benno Overeinder
RIPE PC Chair
https://ripe74.ripe.net/programme/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 74 will take place from 8-12 May 2017 in Budapest, Hungary.
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 74.
See the full descriptions of the different presentation formats,
https://ripe74.ripe.net/submit-topic/presentation-formats/.
Proposals for plenary sessions, BoFs, panels, workshops and tutorials
must be submitted for full consideration no later than 12 March 2017.
Proposals submitted after this date will be considered depending on the
remaining available space in the programme.
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)
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://ripe74.ripe.net/submit-topic/submission-form/.
- Lightning talks should also be submitted using the meeting submission
system (https://ripe74.ripe.net/submit-topic/submission-form/) and can
be submitted any time up to and including the meeting week.
Allocation of lightning talks will start a few days before the
meeting, and will continue throughout the meeting. During the
meeting, they may be announced on the day before the talk or even on
the same day as the talk.
- Lightning talks should also be submitted using the meeting submission
system (https://ripe74.ripe.net/submit-topic/submission-form/) 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.
- Due to potential technical issues, presenters/panellists should be
physically present at the RIPE Meeting.
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/
