- ripe-list - mailman.ripe.net

Last Call for presentations and Draft programme for RIPE 71
by Benno Overeinder 26 Sep '15

26 Sep '15

Colleagues, A list of currently accepted RIPE 71 presentations is now published at: https://ripe71.ripe.net/programme/ There are still few slots remaining for a final RIPE 71 programme and RIPE Programme Committee will accept new proposals until 11 October 2015. This is our last call for you to submit your proposals. You can find the CFP for RIPE 71 below, or at https://ripe71.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://www.ripe.net/participate/meetings/ripe-meetings/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 71 will take place from 16-20 November 2015 in Bucharest, Romania. 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 71. See the full descriptions of the different presentation formats, https://ripe71.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 11 October 2015. 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 in operations - Commercial transactions of IPv4 addresses - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange 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 The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe71.ripe.net/submit-topic/submission-form/. - Lightning talks should also be submitted using the meeting submission system (https://ripe71.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/

1 0

IANA Review Committee Selection Process - RIPE Community Support
by Hans Petter Holen 24 Sep '15

24 Sep '15

Dear RIPE community, As you may be aware, the proposal for IANA stewardship developed by the CRISP Team (and now incorporated into the IANA Stewardship Transition Coordination Group’s proposal) proposes establishing a community-based Review Committee to assist the RIRs in their periodic review of the IANA numbering services Service Level Agreement. In recent months, the NRO Executive Council circulated a draft charter for this Review Committee, noting that the Review Committee “will comprise 15 members, constituted by: (a) two community appointees from each RIR region (who must not be RIR staff); and (b) one RIR staff from the region (who will be a non-voting member).” The charter also notes that “Each RIR shall appoint their Review committee members by a method of its own choosing.” https://www.nro.net/wp-content/uploads/Review-Committee-Charter-draft-Publi… The RIR Executive Council have indicated that they would like to establish this Review Committee in the coming months (ahead of the IANA stewardship transition), so it is important that the RIPE community come to consensus on how we will select our Review Committee members, and who those members will be. I would like to suggest a solution for your consideration and discussion: we currently have three community representatives on the NRO Number Council, two of which are elected by the community (the third is appointed by the RIPE NCC Executive Board). Acknowledging that the work of the Review Committee will likely be quite limited, I suggest that we appoint the two community-elected NRO Number Council representatives as our representatives to the Review Committee. The third, non-voting member of the Review Committee, who will be a RIPE NCC staff member, would then be appointed by the RIPE NCC Executive Board. I believe that this is a straight forward and efficient proposal that would avoid an extra election process. It is based on our long-standing NRO Number Council process and employing the knowledge and talents of individuals who clearly have the trust of the RIPE community. It is important, however, that the community agree on a method for selecting Review Committee members, so if you support this method I would appreciate that you do so on the RIPE list (ripe-list(a)ripe.net) by Monday, 28 September. If this proposal is not acceptable we will conduct a separate IANA Review Committee selection process that would need to be planned prior to the RIPE 71 in November. I look forward to hearing your thoughts. Kind Regards, -- Hans Petter Holen, RIPE Chair email: hph(a)oslo.net | http://hph.oslo.net

8 9

RIPE 71 Draft Programme Now Online
by Meeting 24 Sep '15

24 Sep '15

Dear colleagues, RIPE 71 takes place at the JW Marriott Grand Hotel in Bucharest from 16-20 November 2015. Register for your place via this link: https://ripe70.ripe.net/register You can view the draft programme online: https://ripe71.ripe.net/programme/ There are still a few session slots left. If you have interesting information you’d like to share with the community, please submit a proposal before 11 October 2015 at: https://ripe71.ripe.net/submit-topic/cfp/ To stay up-to-date with all RIPE Meeting updates, follow us on Twitter: @ripemeeting, #RIPE71 Or join the RIPE Meetings page on Facebook: https://www.facebook.com/ripemeetings See you in Bucharest in November! Best regards, Gergana -- Gergana Petrova Conference Coordinator RIPE Network Coordination Centre Singel 258, 1016 AB Amsterdam, The Netherlands T: +31 20 535 4444 www.ripe.net

1 0

[news] RIPE Policy Proposals - September Update
by Marco Schmidt 23 Sep '15

23 Sep '15

Dear colleagues, Please find below our monthly overview of open policy proposals and the stage they have 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-04, “RIPE Resource Transfer Policies” – Discussion Phase until 25 September 2015 Proposals in Last Call: 2015-03, “Assessment Criteria for IPv6 Initial Allocation Size” - Last Call until 29 September 2015 Proposals Awaiting Input: 2014-03, “Remove Multihoming Requirement for AS Number Assignments” Proposal Overviews: PROPOSAL: 2015-04, “RIPE Resource Transfer Policies” OVERVIEW: This proposal 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. STATUS: extended Discussion Phase WHERE TO COMMENT: Address Policy Working Group: address-policy-wg(a)ripe.net DEADLINE: 25 September 2015 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-04 ===== 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-03, “Assessment Criteria for IPv6 Initial Allocation Size” OVERVIEW: This proposal introduces new criteria for the evaluation of large IPv6 allocation requests. These new criteria are hierarchical and geographical structure and segmentation for security and planned longevity. The current requirements, number of users and extent of infrastructure, are retained. RIPE NCC IMPACT ANALYSIS: Includes the RIPE NCC’s understanding of what are reasonable limits for each of the criteria. STATUS: Last Call WHERE TO COMMENT: Address Policy Working Group: address-policy-wg(a)ripe.net DEADLINE: 29 September 2015 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-03 ===== The following proposals are awaiting input before they go any further in the PDP. 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 WHERE TO COMMENT: Address Policy Working Group: address-policy-wg(a)ripe.net FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2014-03 ===== 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

Fwd: [cooperation-wg] IANA Review Committee Selection Process - RIPE Community Support
by Sergey V. Gushkov 21 Sep '15

21 Sep '15

+1 I completely agree! 2015-09-21 16:21 GMT+03:00 Jim Reid <jim(a)rfc1035.com>: > > On 15 Sep 2015, at 18:26, Hans Petter Holen <hph(a)oslo.net> wrote: > > > I suggest that we appoint the two community-elected NRO Number Council > representatives as our representatives to the Review Committee. The third, > non-voting member of the Review Committee, who will be a RIPE NCC staff > member, would then be appointed by the RIPE NCC Executive Board. > > > > I believe that this is a straight forward and efficient proposal that > would avoid an extra election process. > > +1 > > Just do it! >

1 0

NRO NC Call for Nominations
by Axel Pawlik 14 Sep '15

14 Sep '15

Dear colleagues, There is a call for nominations from the RIPE NCC service region to fill one vacant seat on the Number Resource Organization (NRO) Number Council (NC). The three-year term of Dmitry Kohmanyuk ends on 31 December 2015. The election to the NRO NC seat will take place during the Plenary at the RIPE 71 Meeting to be held in Bucharest from 16-20 November 2015. All members of the Internet community who are present at that Plenary may vote in the election. The deadline for nominations is 16 October 2015. Any individual residing within the RIPE NCC service region is eligible for nomination, except Regional Internet Registry (RIR) staff members. Self-nominations are permitted. Please send your nominations to <nominations at ripe.net> by 23:59 UTC on 16 October 2015. All confirmed nominations will be listed on the RIPE NCC website by 19 October 2015. All nominees may submit a written statement in support of their nomination for publication on the RIPE NCC website. Other individuals may express support for nominated individuals by sending an email to <nominations at ripe.net>. Expressions of support will also be published on the RIPE NCC website. To find out more about the NRO NC and the election process, please see: https://www.ripe.net/internet-coordination/internet-governance/internet-tec… Regards, Axel Pawlik Managing Director RIPE NCC

1 0

2nd Call for presentations RIPE 71
by Benno Overeinder 02 Sep '15

02 Sep '15

Colleagues, Please note the approaching deadline of 13 September 2015 for RIPE 71 plenary programme submissions. You can find the CFP for RIPE 71 below, or at https://ripe71.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://www.ripe.net/participate/meetings/ripe-meetings/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 71 will take place from 16-20 November 2015 in Bucharest, Romania. 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 71. See the full descriptions of the different presentation formats, https://ripe71.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 13 September 2015. 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 in operations - Commercial transactions of IPv4 addresses - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange 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 The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe71.ripe.net/submit-topic/submission-form/. - Lightning talks should also be submitted using the meeting submission system (https://ripe71.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/

1 0

IANA Stewardship Transition Coordination Group (ICG) Call for Public Comment on IANA Stewardship Transition Proposal
by Serge Radovcic 31 Aug '15

31 Aug '15

This message is sent on behalf of the Number Resource Organization (NRO). ------------------------------------------------------------------------------------------------------- IANA STEWARDSHIP TRANSITION COORDINATION GROUP (ICG) CALL FOR PUBLIC COMMENT ON IANA STEWARDSHIP TRANSITION PROPOSAL For the past 12 months, many in the Internet community have worked hard to formulate a plan for the transition of stewardship of the IANA functions away from the U.S. Government and into the hands of the broader Internet community. Working with and on behalf of the Internet Number Community, the CRISP Team built a plan for the IANA numbering functions, and this now forms part of the transition plan developed by the IANA Stewardship Transition Coordination Group for all of the IANA functions. We are now very close to the end of this long and complex process, and the Number Community has devoted many hours to meetings and discussions around the plan. At this stage of the process, to ensure the success of the transition, it is vital that the global Internet community expresses its support for the ICG proposal. Therefore, we encourage members of the RIR communities to review the ICG’s draft IANA Stewardship Transition Proposal and register their support or any concerns they may have: https://www.ianacg.org/icg-files/documents/IANA-stewardship-transition-prop… Comments can be submitted via an online form or by emailing <public-comments(a)ianacg.org> until 8 September 2015 at 23:59 (UTC). Please note that all questions on the online form about the proposal are optional. The form can be accessed at: https://comments.ianacg.org/form If you agree with the key priorities in the Number Community’s contribution to the proposal – which are focused on ensuring stability, security, reliability, quality of service and community empowerment – please submit your statement of support today! Your comment could be as simple as this: I, as a member of the Number Community, am in favour of the ICG proposal on the IANA stewardship transition. If for any reason you do not agree with the draft proposal, it is essential that you take the time to comment and describe your viewpoint and underlying reasoning. For more information, please review the CRISP Team’s own analysis, which shows how the ICG proposal reflects and supports the CRISP proposal, and the wishes of the global Number Community. It is available here: https://www.nro.net/crisp-response-icg-proposal

1 0

[news] RIPE Policy Proposals - August Update
by Marco Schmidt 28 Aug '15

28 Aug '15

Dear colleagues, Please find below our monthly overview of open policy proposals and the stage they have 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: NEW: 2015-04, “RIPE Resource Transfer Policies” – Discussion Phase until 14 September 2015 Proposals Accepted: 2015-02, “Keep IPv6 PI When Requesting IPv6 Allocation” Proposals Awaiting Input: 2015-03, “Assessment Criteria for IPv6 Initial Allocation Size” 2014-03, “Remove Multihoming Requirement for AS Number Assignments” Proposal Overviews: NEW PROPOSAL: 2015-04, “RIPE Resource Transfer Policies” OVERVIEW: This proposal 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. STATUS: Discussion Phase WHERE TO COMMENT: Address Policy Working Group: address-policy-wg(a)ripe.net DEADLINE: 14 September 2015 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-04 ===== The following proposal has been accepted since the last update. PROPOSAL: 2015-02, “Keep IPv6 PI When Requesting IPv6 Allocation” OVERVIEW: This proposal removes the requirement that LIRs must return their IPv6 Provider Independent (PI) assignment when requesting an IPv6 allocation. STATUS: Accepted IMPLEMENTATION: Implemented on 10 August 2015 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-02 ===== The following proposals are awaiting input before they go any further in the PDP. PROPOSAL: 2015-03, “Assessment Criteria for IPv6 Initial Allocation Size” OVERVIEW: This proposal introduces new criteria for the evaluation of large IPv6 allocation requests. These new criteria are hierarchical and geographical structure and segmentation for security and planned longevity. The current requirements, number of users and extent of infrastructure, are retained. RIPE NCC IMPACT ANALYSIS: Includes the RIPE NCC’s understanding of what are reasonable limits for each of the criteria. STATUS: Review Phase - awaiting decision from Working Group Chair WHERE TO COMMENT: Address Policy Working Group: address-policy-wg(a)ripe.net 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 WHERE TO COMMENT: Address Policy Working Group: address-policy-wg(a)ripe.net FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2014-03 ===== 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

NRO NC Call for Nominations
by Axel Pawlik 17 Aug '15

17 Aug '15

Dear colleagues, This is a call for nominations from the RIPE NCC service region to fill one vacant seat on the Number Resource Organization (NRO) Number Council (NC). The three-year term of Dmitry Kohmanyuk ends on 31 December 2015. The election to the NRO NC seat will take place during the Plenary at the RIPE 71 Meeting to be held in Bucharest from 16-20 November 2015. All members of the Internet community who are present at that Plenary may vote in the election. The deadline for nominations is 16 October 2015. Any individual residing within the RIPE NCC service region is eligible for nomination, except Regional Internet Registry (RIR) staff members. Self-nominations are permitted. Please send your nominations to <nominations(a)ripe.net> by 23:59 UTC on 16 October 2015. All confirmed nominations will be listed on the RIPE NCC website by 19 October 2015. All nominees may submit a written statement in support of their nomination for publication on the RIPE NCC website. Other individuals may express support for nominated individuals by sending an email to <nominations(a)ripe.net>. Expressions of support will also be published on the RIPE NCC website. To find out more about the NRO NC and the election process, please see: https://www.ripe.net/participate/internet-governance/internet-technical-com… Regards, Axel Pawlik Managing Director RIPE NCC

1 0