Dear colleagues,
Here is our monthly overview of open policy proposals and their stage in the RIPE Policy Development Process (PDP). This is the first update since June, as there were no significant PDP developments in recent months.
If you wish to join the discussion about a particular proposal, please do so on the relevant working group mailing list.
The RIPE Forum provides an easy access to all working group mailing lists https://www.ripe.net/participate/mail/forum/
Proposals Open for Discussion:
2015-04, "RIPE Resource Transfer Policies"
2016-03, "Locking Down the Final /8 Policy"
Proposal Withdrawn:
2016-01, "Include Legacy Internet Resource Holders in the Abuse-c Policy"
2016-02, "Resource Authentication Key ( RAK ) code for third party authentication"
Proposal Overviews:
PROPOSAL: 2015-04, "RIPE Resource Transfer Policies"
OVERVIEW: Aims to create a single transfer policy with all relevant information on the transfer of Internet number resources, replacing text in several RIPE Policies. The proposal also introduces a 24-month holding period for IPv4 addresses and 16-bit ASNs after any change of holdership.
RIPE NCC IMPACT ANALYSIS: Describes how the 24-month holding period for scarce resources will be applied.
STATUS: Review Phase
DEADLINE: 26 October 2016
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-04
PROPOSAL: 2016-03, "Locking Down the Final /8 Policy"
OVERVIEW: The third version aims to ban transfers of allocations made under the final /8 policy. The proposal also defines which IPv4 resources will be added to the RIPE NCC’s available IPv4 pool.
STATUS: Review Phase
RIPE NCC IMPACT ANALYSIS: Describes how the transfer restrictions will be applied.
WHERE TO COMMENT: Address Policy Working Group: address-policy-wg(a)ripe.net
DEADLINE: 17 November 2016
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-03
=====
The following proposals have been withdrawn.
PROPOSAL: 2016-01, "Include Legacy Internet Resource Holders in the Abuse-c Policy"
OVERVIEW: Aimed for a mandatory abuse contact for Legacy Internet Resource Holders in the RIPE Database.
STATUS: Withdrawn. The proposers decided to withdraw the proposal due to the inability to find an acceptable agreement which satisfied all parties.
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-01
PROPOSAL: 2016-02, "Resource Authentication Key ( RAK ) code for third party authentication"
OVERVIEW: Aims to allow all number resources, in exacts and more specifics,
to be authenticated via an API-key that expires on a certain date.
STATUS: Withdrawn. The proposer didn't see enough community support, especially from the external database holders who would have needed to perform their own development work.
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-02
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’t 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 26 October at 8:00 and 10:00 (UTC).
Remote participation will be available at:
https://ripe73.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 Friends and Colleagues,
*Please note that some of the times have changed from my original mail
due to the slightly later starting time of all of our sessions in Madrid.*
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 2016 who will be elected by the RIPE community at RIPE 73 in
Madrid.
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.
Nominations for the RIPE 73 PC elections can be sent in from today until
Tuesday October 25th, 15:30 CEST. 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 Tuesday at 15:30 CEST, and
publish the biographies on the RIPE Meeting web site. Candidates (or
their stand-ins) can present themselves at the start of the Tuesday
17:00 CEST session.
The RIPE PC online voting system will be open from Tuesday October 25th,
16:00 CEST until Thursday October 27th, 17:30 CEST, 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
Friday morning, the 28th October, at the start of the 12:00 CEST closing
plenary session.
Questions about the RIPE PC can be sent to pc(a)ripe.net.
Regards,
Brian
On Behalf of the RIPE PC
--
Brian Nisbet, Network Operations Manager
HEAnet Limited, Ireland's Education and Research Network
1st Floor, 5 George's Dock, IFSC, Dublin 1
Registered in Ireland, no 275301 tel: +35316609040 fax: +35316603666
web: http://www.heanet.ie/
Dear colleagues,
When Rob Blokzijl stepped down as RIPE Chair, he asked that I put the wheels
in motion to establish a selection procedure for future RIPE Chairs. At the
last meeting I presented a proposal for how this could happen to start the
discussion.
https://labs.ripe.net/Members/hans_petter_holen/draft-ripe-chair-election-p…
The RIPE Chair represents you, the RIPE community. This community has been,
and always will be, driven bottom up and by consensus. Your ideas and input
form the foundation of what this selection procedure will look like.
Key questions for a procedure are:
* Who can be selected as RIPE Chair
* Who will select the RIPE Chair
* How will the selection happen?
Should we have an election? Decided by a show of hands at a RIPE
Meeting? Evoting? A selection panel? A vetting process by the RIPE Working
Group
Chairs? Should there be a RIPE Vice Chair?
Your involvement and consensus on the selection procedure is crucial.
We've established a dedicated mailing list for this discussion:
ripe-chair-discuss(a)ripe.net
To subscribe to the list, please visit
https://www.ripe.net/mailman/listinfo/ripe-chair-discuss/
--
Sincerely,
Hans Petter Holen
RIPE Chair
Dear colleagues,
On 1 October 2016, the IANA functions contract that the United States
Government had with ICANN was allowed to expire. This represents the
final step in the community-led IANA stewardship transition process that
began in 2014. Oversight of IANA is now the responsibility of the Names,
Numbers and Protocol Parameters communities that rely on its services.
The five Regional Internet Registries have a Service Level Agreement
(SLA) in place with IANA that defines our expectations moving forward. A
community-selected IANA Numbering Services Review Committee will assist
the NRO Executive Council when it conducts periodic reviews of IANA's
services. Aside from this, our work with IANA will be unchanged and
members will not see any operational difference.
We would like to thank everyone from the RIPE community who participated
in this process — whether by sharing their views at RIPE Meetings or on
the various mailing lists, or participating more directly within the
CRISP, CCWG-Accountability and ICG groups. The ability of the five RIR
communities to organise and contribute effectively to this global effort
was a demonstration of the strength of our open, transparent and
bottom-up approach.
Since 2014, the RIPE NCC has maintained an archive of key documents and
announcements relating to the IANA stewardship transition. You can find
this on our website here:
https://www.ripe.net/iana-stewardship-transition
Kind regards
Axel Pawlik
Managing Director
RIPE NCC
