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-01, "Publish statistics on Intra-RIR Legacy updates"
Proposals Accepted:
2016-05, "Synchronising the Initial and Subsequent IPv6 Allocation Policies"
Proposals Awaiting Input:
2016-04, "IPv6 PI Sub-assignment Clarification"
======
Proposal Overview:
PROPOSAL: 2017-01, "Publish statistics on Intra-RIR Legacy updates"
OVERVIEW: The proposal aims to add the requirement that the RIPE NCC publish all changes to the holdership of legacy resources in the existing transfer statistics.
STATUS: Discussion Phase
WHERE TO COMMENT: Address Policy Working Group: address-policy-wg(a)ripe.net
DEADLINE: 24 May 2017
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2017-01
======
The following proposal has been accepted:
PROPOSAL: 2016-05, "Synchronising the Initial and Subsequent IPv6 Allocation Policies"
OVERVIEW: The policy change matches the subsequent IPv6 allocation requirements with the initial allocation requirements.
STATUS: Accepted & Implemented
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-05
======
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-…
During the upcoming RIPE Meeting, the Address Policy Working Group will
hold two sessions where ongoing and possible future policy proposals
will be discussed. If you can not attend the RIPE Meeting in person, we
invite you to join remotely. A live webcast and IRC chat facility will
be available for remote participation.
The two sessions will begin on 10 May at 7:00 and 9:00 (UTC).
The remote participation will be available at:
https://ripe74.ripe.net/
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
Dear colleagues,
RIPE 74 is just two weeks away. If you haven’t yet registered, follow
this link to secure your place:
https://ripe74.ripe.net/register/
------------------------
Check out the Programme!
------------------------
Interactive meeting programme for the entire week can be found at:
https://ripe74.ripe.net/programme/
Monday morning tutorials:
https://ripe74.ripe.net/programme/meeting-plan/tutorials/
BoFs:
https://ripe74.ripe.net/programme/meeting-plan/bof/
-------
Socials
-------
RIPE Meetings are famed for their socials. Here’s what we have planned
in Budapest:
https://ripe74.ripe.net/programme/social-events/
------------------------
Sunday RIPE NCC Training
------------------------
On Sunday, 7 May 2017, the RIPE NCC Training Department is organising a
full-day Measurements and Tools Training Course. This course is free to
attend and takes place at the Sofitel Budapest, which is a one-minute
walk from the RIPE 74 meeting location.
For more information and to register please visit:
https://ripe74.ripe.net/on-site/parallel-events/mat-training/
-----
More information on RIPE 74 can be found at:
https://ripe74.ripe.net/
Follow us on Twitter @ripemeeting, hashtag #RIPE74
I look forward to meeting you in Budapest!
Best regards,
Martina
--
Martina de Mas
Conference Coordinator
RIPE Network Coordination Centre
Dear colleagues,
Brief version: The RIPE PC invites submissions for plenary, tutorial,
BoF and Lightning Talks.
Longer version:
As distinct from previous RIPE meetings, the RIPE Programme Committee
decided to keep two plenary slots open for so-called “late submission”.
These plenary slots gives the community the opportunity to submit
presentations that report on recent developments, issues, security
incidents, etc., that are relevant to the RIPE audience.
Independent from the realisation of late submissions, the PC has
received a fair amount of high-quality submissions for the first
deadline on March 12th. From these submissions, we have selected 14
presentations to complete the RIPE 74 plenary programme and no second
CFP with a deadline in April was required.
For the tutorials and BoFs we have one slot for each available:
- Monday morning, 2 hour tutorial slot
- evening, 1 hour BoF slot
Also please consider to submit Lightning Talks for the Monday plenary.
During the week of the RIPE meeting we will accept LTs for Tuesday and
Friday.
Please submit your plenary “late submission”, tutorial or BoF submission
via the PC submission system,
https://ripe74.ripe.net/submit-topic/submission-form/.
The deadline for the submissions is *April 26th*.
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 26 April 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/
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,
There is an open Call for Workshop Proposals for the next Internet
Governance Forum (IGF), which will be in Geneva, Switzerland from 18-21
December 2017.
The deadline for proposals is 3 May 2017.
More information is available here:
http://www.intgovforum.org/multilingual/content/igf-2017-call-for-workshop-…
Kind regards,
Nick Hyrka
Communications Manager
RIPE NCC
