June 2015 - ncc-announce - mailman.ripe.net

[news] RIPE Policy Proposals - June Update
by Marco Schmidt 24 Jun '15

24 Jun '15

Dear colleagues, Please find below the monthly overview of open policy proposals and the stage each has reached 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: 2015-02, "Keep IPv6 PI When Requesting IPv6 Allocation" – Discussion open until 7 July 2015 Proposals in Last Call: 2015-01, "Alignment of Transfer Requirements for IPv4 Allocations"– Last Call until 21 July 2015 Proposals Awaiting Input: 2015-03, "Assessment Criteria for IPv6 Initial Allocation Size" 2014-03, "Remove Multihoming Requirement for AS Number Assignments" Proposal Overviews: PROPOSAL: 2015-02, "Keep IPv6 PI When Requesting IPv6 Allocation" OVERVIEW: This proposal aims to remove the requirement that LIRs should return their IPv6 Provider Independent (PI) assignment when requesting an IPv6 allocation. RIPE NCC IMPACT ANALYSIS: Includes the point that little impact is expected in terms of routing table growth. STATUS: Review Phase WHERE TO COMMENT: Address Policy Working Group: address-policy-wg(a)ripe.net DEADLINE: 7 July 2015 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-02 ===== The following proposal is in Last Call. Rough consensus has been declared and the purpose of this phase is to give the community a final opportunity to present any well-justified objections to the proposal that have not already been raised and addressed during the previous discussion phases. PROPOSAL: 2015-01, "Alignment of Transfer Requirements for IPv4 Allocations" OVERVIEW: Currently, IPv4 allocations received from another LIR can only be re-allocated after 24 months, while IPv4 allocations made by the RIPE NCC can be transferred immediately. This proposal aims to align the transfer requirements with a 24-month holding period for all IPv4 allocations. RIPE NCC IMPACT ANALYSIS: Includes the point that currently around 10% of the allocations made by the RIPE NCC are transferred shortly after they have been allocated. STATUS: Last Call WHERE TO COMMENT: Address Policy Working Group: address-policy-wg(a)ripe.net DEADLINE: 21 July 2015 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-01 ===== The following proposals are awaiting input before they proceed in the PDP. PROPOSAL: 2015-03, "Assessment Criteria for IPv6 Initial Allocation Size" OVERVIEW: This proposal aims to remove the requirement that large IPv6 allocations are based only on existing users and network infrastructure. As a result of this policy implementation, the RIPE NCC will be able to consider additional criteria when evaluating IPv6 allocation requests. STATUS: Discussion Phase - Awaiting impact analysis* FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-03 PROPOSAL: 2014-03, "Remove Multihoming Requirement for AS Number Assignments" OVERVIEW: This proposal aims to ease the requirements when requesting an Autonomous System (AS) Number. To this end, the following actions are proposed: - Remove the need for evaluation - Limit the number of AS Numbers per organisation to 1,000 - Require that 16-bit AS Numbers are multihomed after nine months RIPE NCC IMPACT ANALYSIS: Includes the point that it will be the End User that decides if the need for an AS Number is technically reasonable. STATUS: Review Phase - Awaiting New Proposal Version FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2014-03 *The goal of the impact analysis is to provide supporting information to facilitate discussions about the proposal and to outline the proposal’s possible impact if it were to be accepted. ===== The RIPE NCC provides an overview of current RIPE Policy Proposals on www.ripe.net: 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

1 0

[news] Call for Comments for a Draft Internet Community Review Committee Charter
by Serge Radovcic 24 Jun '15

24 Jun '15

This message is sent on behalf of the Number Resource Organization (NRO). _______________________________________________________________ NRO – PUBLIC CONSULTATION CALL FOR COMMENTS FOR A DRAFT INTERNET COMMUNITY REVIEW COMMITTEE CHARTER Open until: 6 July 2015, 23:59 UTC On 15 January, 2015, the Consolidated RIR IANA Stewardship Proposal (CRISP) Team submitted the Internet Number Community Proposal to the request for proposals issued by the IANA Stewardship Coordination Group (ICG). One of the key elements of the Internet Number Community Proposal, described in section III.A.4, is the establishment of a Review Committee to ensure that the service level defined in the proposed SLA for the IANA Numbering Services is maintained by the IANA Numbering Services Operator. Further description of the Review of IANA Numbering services is described in Article 8 of the draft SLA. All interested parties are now encouraged to review and comment on the draft Internet Number Community Review Committee Charter. The document is available at: https://www.nro.net/review-committee-charter This call for public comments will remain open until 6 July, 2015 at 23:59 UTC. Comments can be submitted by any interested party to the ianaxfer(a)nro.net mailing list. Subscription to this list is open and available at: https://www.nro.net/mailman/listinfo/ianaxfer

1 0

[service] Urgent Network Maintenance 23/06/2015 18.30-20:00 UTC
by Marco Giuliani 23 Jun '15

23 Jun '15

Dear colleagues, On Tuesday, 23 June 2015, between 18:30 and 20:00 UTC, we will carry out maintenance work on our core network infrastructure. During this period our services may be affected, including the RIPE NCC website, RIPE Labs, the RIPE Database and the LIR Portal. Public DNS services operated by the RIPE NCC should be available as normal. We apologise for any inconvenience this may cause. If you have any questions, please contact <ops(a)ripe.net>. Kind regards, Marco Giuliani Systems Engineer RIPE NCC

1 0

[meetings] Upcoming RIPE NCC Meetings
by Meeting 22 Jun '15

22 Jun '15

Dear colleagues, We are pleased to share the dates and locations of our upcoming RIPE and Regional Meetings. Should locations or scheduling change, we will inform you as soon as possible. RIPE Meetings RIPE 71: Bucharest, 16-20 November 2015 https://ripe71.ripe.net RIPE 72: Copenhagen, 23-27 May 2016 RIPE 73: Planned for 24-28 October 2016. Location TBD. Regional Meetings ENOG 10: Odessa, 13-14 October 2015 Call for presentations: http://www.enog.org/meetings/enog-10/cfp MENOG 16: Tehran, 2-3 December MENOG 17: Istanbul, 20-29 March 2016 (TBD) SEE 5: Tirana, 19-20 April 2016 ENOG 11: Moscow, 14-15 June 2016 Call for host: http://www.enog.org/call-for-host/ We look forward to seeing many of you there! Best regards, Gergana Gergana Petrova Conference Coordinator RIPE NCC

1 0

[training] RIPE NCC Webinars - new dates
by Training Services 18 Jun '15

18 Jun '15

Dear colleagues, We are pleased to announce the dates for the RIPE NCC Webinars for the coming quarter. These interactive on-line learning sessions take about one hour, and give you the opportunity to learn and interact with our trainers without leaving your desk. In the next 3 months you can participate in the following Webinars: - Advanced RIPE Atlas Usage (NEW!) - Introduction to the RIPE Database - RIPE Database - Advanced Topics - IPv6 in the RIPE Database - IPv6 Addressing Plan - Webinar for New LIRs - Resource Certification (RPKI) Register now at https://www.ripe.net/support/training/learn-online/webinars Participation is limited to 20 people, so don't hesitate if you want to take part! If you have any questions, please email <training(a)ripe.net>. We look forward to seeing you online. Kind regards, RIPE NCC Training Services

1 0

[service] Planned Maintenance on 16 June 2015
by Gerard Leurs 15 Jun '15

15 Jun '15

Dear colleagues, On Tuesday, 16 June 2015, from 06:00 to 07:00 UTC, we will carry out maintenance work on one of our fileservers. This fileserver is used mainly for internal services, so we do not expect the maintenance work to affect external services. However, we apologise in advance for any inconvenience this may cause. If you have any questions, please contact <ops(a)ripe.net>. Kind regards, Gerard Leurs Operations Coordinator RIPE NCC

1 0

[training] RIPE NCC Academy - New “Introduction to IPv6” Course
by Sandra Bras 04 Jun '15

04 Jun '15

Dear colleagues, The RIPE NCC is pleased to announce the launch of a brand new online course: Introduction to IPv6. This course is now available on the RIPE NCC Academy, our virtual learning environment that allows you to take courses and obtain certificates online: https://academy.ripe.net/ You can sign in to the RIPE NCC Academy with your RIPE NCC Access account (if you don’t already have one, you can easily create one through the link above). The RIPE NCC Academy is available to everyone, free of charge. Before starting this course, you should know that: - You have 90 days to complete the course from the moment you start it - If you’re very confident that you already know all you need to know about IPv6, you can choose to complete the activities without studying the content - You will earn a certificate when you achieve a total score of 70% or higher in the course - Your certificate will remain valid for three years We have some prizes for you: - The first user to get a certificate for this course will receive a copy of the book “IPv6 Essentials”, signed by the author, Sylvia Hagen - The first 20 users to get a certificate for this course will get one IPv6 CIDR chart mug Don’t wait any longer - graduate to the next level today! If you don’t yet have your RIPE Database Expert certificate, make sure you get it! If you have any questions, feel free to contact us at <academy(a)ripe.net>. Watch our RIPE NCC Academy teaser: https://www.youtube.com/watch?v=P7K89w8VXCI Happy learning, Sandra Brás E-Learning Coordinator

1 0

[news] CCWG Report - Deadline for comments on 3 June 23:59 UTC
by Athina Fragkouli 02 Jun '15

02 Jun '15

Dear colleagues, This is a reminder that the CCWG-Accountability is seeking public comments until tomorrow, 3 June, 23:59 UTC. The Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability) has published a Draft Report that contains its initial Draft Proposal. The Draft Report can be found here: CCWG-Accountability Draft Report (without annexes): https://www.icann.org/en/system/files/files/cwg-accountability-draft-propos… [PDF, 1.72 MB] CCWG-Accountability Draft Report (with annexes): https://www.icann.org/en/system/files/files/cwg-accountability-draft-propos… [PDF, 2.05 MB] This initial Draft Proposal is focused on draft Work Stream 1 recommendations. Work Stream 1 relates to those changes to ICANN’s accountability arrangements that must be in place, or committed to, prior to the IANA stewardship transition. More information can be found here: https://www.icann.org/public-comments/ccwg-accountability-draft-proposal-20… The Cross Community Working Group on Enhancing ICANN Accountability (CCWG) has published a Draft Report that contains its initial Draft Proposal. The Draft Report can be found here: CCWG-Accountability Draft Report (without annexes): https://www.icann.org/en/system/files/files/cwg-accountability-draft-propos… [PDF, 1.72 MB] CCWG-Accountability Draft Report (with annexes): https://www.icann.org/en/system/files/files/cwg-accountability-draft-propos… [PDF, 2.05 MB] The ASO representatives to the CCWG encourage the numbers community to review and give feedback on any specific points in the Draft Report, and reply to the questions listed in the document. At the same time we would like to draw the numbers community’s attention to the following matters, as we believe that they are of interest to the numbers community and we would appreciate the community's feedback: 1. Revised Mission The CCWG suggests clarifications on the description of ICANN’s mission (more details in section 3.1 of the Draft Report). During the drafting process the ASO representatives provided a tentative description of ICANN’s mission in regard to the coordination of policy development for Internet number resources (page 20, paragraph 57). The tentative description reads as follows: “In this role, with respect to IP addresses and AS numbers, ICANN’s Mission is described in the ASO MoU between ICANN and RIRs.” Do you feel that this description is accurate? 2. Revised Commitments and Core Values The CCWG proposes an amendment to one of the core values of the Bylaws (page 25, paragraph 89). The proposed amendment reads as follows: “Employ open, transparent and bottom-up, [private sector led multistakeholder] policy development processes that (i) seeks input from the public, for whose benefit ICANN shall in all events act, (ii) promote well- informed decisions based on expert advice, and (iii) ensure that those entities most affected can assist in the policy development process;” Given that the RIR global policies are described as open, transparent and bottom-up, the ASO representatives have a concern on the inclusion of the notion of “private sector led multistakeholder”, which is put in square brackets. The addition of this notion may lead to uncertainty on whether ICANN’s core values include the employment of RIR global policies. Do you agree with the removal of the notion “private sector led multistakeholder”? 3. US Headquarters as part of the Fundamental Bylaws The CCWG incorporated some provisions from the Affirmation of Commitments relevant to ICANN accountability into the Bylaws (in particular regarding ICANN’s Mission and Core Values). The CCWG has suggested defining these provisions as "Fundamental Bylaws". The concept of Fundamental Bylaws is described in section 3.2 (pp 27-31) of the Draft Report. The main difference with the common Bylaws provisions is that while the Board could propose a change to this Bylaws provision, SO/ACs could block the proposed change (by a 75% vote). On the other hand any change to Fundamental Bylaws would require approval by SO/ACs (75% vote). One of these provisions requires that ICANN “remains headquartered in the United States of America”. The CCWG noted that this provision exists already in current ICANN Bylaws, at Article XVIII Section 1: “OFFICES. The principal office for the transaction of the business of ICANN shall be in the County of Los Angeles, State of California, United States of America. ICANN may also have an additional office or offices within or outside the United States of America as it may from time to time establish.” As the rest of Affirmation of Commitments provisions are suggested to be incorporated in the Fundamental Bylaws, the CCWG considered whether this provision should also be listed as a Fundamental Bylaw. The comment by the ASO Representatives was that while the rest of the Affirmation of Commitments provisions incorporated can indeed be seen as fundamental principles, the notion of US Headquarters is an administrative issue, which would not be considered as fundamental. Do you agree with the ASO representatives approach? 4. Appealing Mechanisms The CCWG has proposed enhancements to the two appealing mechanisms described in ICANN Bylaws, i.e. the Independent Review Panel and the Reconsideration process. The ASO representatives commented that, even though the ICANN Board approves its global policies, the processes and forums for bottom-up policy development relating to number resources is outside of ICANN, and there are separate appealing procedures for disputes relating to Internet number resources. In particular there is: 1. an arbitration process described in the ASO MoU for disputes relevant to the Global Policy development process 2. an arbitration process described in the draft Service Level Agreement between the five RIRs and IANA Numbering Services Operator for disputes relevant to the IANA numbering services. 3. A bottom-up process for any concerns that a third party may have relating to Internet number resources issues. Additionally the ASO representatives noted that it was requested by the CWG that decisions regarding ccTLD delegations or revocations would be excluded from standing, until relevant appeal mechanisms have been developed by the ccTLD community, in coordination with other parties. Considering the above, the ASO representatives would propose that any appeal mechanism developed by the CCWG should not cover disputes relating to Internet number resources. 5. Powers The CCWG suggested that the following powers would ensure community empowerment: - Reconsider/reject budget or strategy/operating plans (section 5.2 of the Draft Report, pp 47-48). We would like to note that this power was listed as one of the expected accountability mechanisms by the CWG. - Reconsider/reject changes to ICANN Standard Bylaws (section 5.3 of the Draft Report pp 48-49) - Approve changes to Fundamental Bylaws (section 5.4 of the Draft Report pp 49-50) - Remove individual ICANN Directors (section 5.5 of the Draft Report pp 50-52) - Recall the entire ICANN Board (section 5.6 of the Draft Report pp 52- 53) These powers would be exercised by changing ICANN’s structure into a membership-based organisation, of which the SO/ACs would be the members. Details of this structure can be found in section 5.1.1 of the proposal (pp 42-45). Do you have any concerns or comments on any of these powers or the suggested structure? Thank you, Athina Fragkouli ASO representative to the CCWG-Accountability

1 0

[news] Email Resource Requests No Longer Supported
by Ingrid Wijte 01 Jun '15

01 Jun '15

Dear colleagues, On 7 October 2014, we announced our timeline for phasing out the text-based email request forms on our website: https://www.ripe.net/ripe/mail/archives/ncc-services-wg/2014-October/002890… While the forms themselves were archived in March, we have continued accepting these forms to allow members time to adjust their internal processes. As the final part of this implementation, we will now no longer accept resource requests by email. Members can now use either the request forms available through the LIR Portal, or the Resource Request API which can be found here: https://www.ripe.net/support/documentation/developer-documentation/resource… In order to maintain transparency, we have also published the information LIRs need to provide in order to complete a request form: https://www.ripe.net/manage-ips-and-asns/resource-management/supporting-not… Kind regards Ingrid Wijte Registration Services Assistant Manager RIPE NCC

1 0