From benno at NLnetLabs.nl Wed Sep 2 15:52:20 2015 From: benno at NLnetLabs.nl (Benno Overeinder) Date: Wed, 2 Sep 2015 15:52:20 +0200 Subject: 2nd Call for presentations RIPE 71 Message-ID: <55E6FF14.4060105@NLnetLabs.nl> 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/ From nominations at ripe.net Mon Sep 14 12:20:02 2015 From: nominations at ripe.net (Axel Pawlik) Date: Mon, 14 Sep 2015 12:20:02 +0200 Subject: NRO NC Call for Nominations Message-ID: <8A0430C2-B112-4444-9083-7A1ACF33E743@ripe.net> 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 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 . 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-technical-community/nro/nro-nc/nro-nc-nominations-2015 Regards, Axel Pawlik Managing Director RIPE NCC From hph at oslo.net Tue Sep 15 19:26:52 2015 From: hph at oslo.net (Hans Petter Holen) Date: Tue, 15 Sep 2015 19:26:52 +0200 Subject: IANA Review Committee Selection Process - RIPE Community Support Message-ID: <55F854DC.9@oslo.net> 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-Public-v1.pdf 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 at 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 at oslo.net | http://hph.oslo.net From brian.nisbet at heanet.ie Mon Sep 21 10:58:16 2015 From: brian.nisbet at heanet.ie (Brian Nisbet) Date: Mon, 21 Sep 2015 09:58:16 +0100 Subject: IANA Review Committee Selection Process - RIPE Community Support In-Reply-To: <55F854DC.9@oslo.net> References: <55F854DC.9@oslo.net> Message-ID: <55FFC6A8.9060902@heanet.ie> Hans Petter, I think this may be an elegant solution. I am slightly suspicious of any new piece of work which is supposed to be lightweight and is then given to already busy people, as it has a habit of spiralling. I would also welcome your thoughts on managing the difference between the term lengths of the two different posts? That said, I don't think these are reasons to oppose your proposal, I just want to make sure they've been thought about. Thanks, Brian 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/ On 15/09/2015 18:26, Hans Petter Holen wrote: > 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-Public-v1.pdf > > > 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 at 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, > From jim at rfc1035.com Mon Sep 21 15:21:06 2015 From: jim at rfc1035.com (Jim Reid) Date: Mon, 21 Sep 2015 14:21:06 +0100 Subject: [cooperation-wg] IANA Review Committee Selection Process - RIPE Community Support In-Reply-To: <55F854DC.9@oslo.net> References: <55F854DC.9@oslo.net> Message-ID: On 15 Sep 2015, at 18:26, Hans Petter Holen 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! From gushkovsv at gmail.com Mon Sep 21 16:50:16 2015 From: gushkovsv at gmail.com (Sergey V. Gushkov) Date: Mon, 21 Sep 2015 17:50:16 +0300 Subject: Fwd: [cooperation-wg] IANA Review Committee Selection Process - RIPE Community Support In-Reply-To: References: <55F854DC.9@oslo.net> Message-ID: +1 I completely agree! 2015-09-21 16:21 GMT+03:00 Jim Reid : > > On 15 Sep 2015, at 18:26, Hans Petter Holen 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! > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pk at DENIC.DE Mon Sep 21 17:09:06 2015 From: pk at DENIC.DE (Peter Koch) Date: Mon, 21 Sep 2015 17:09:06 +0200 Subject: IANA Review Committee Selection Process - RIPE Community Support In-Reply-To: <55FFC6A8.9060902@heanet.ie> References: <55F854DC.9@oslo.net> <55FFC6A8.9060902@heanet.ie> Message-ID: <20150921150906.GX10075@x28.adm.denic.de> On Mon, Sep 21, 2015 at 09:58:16AM +0100, Brian Nisbet wrote: > I think this may be an elegant solution. I am slightly suspicious of any > new piece of work which is supposed to be lightweight and is then given > to already busy people, as it has a habit of spiralling. > > I would also welcome your thoughts on managing the difference between > the term lengths of the two different posts? > > That said, I don't think these are reasons to oppose your proposal, I > just want to make sure they've been thought about. I'm mostly with Brian here. Hans Petter's suggestion works well for seeding but the question should be up for review one year into the committee members' terms to identify incompatibilities or synergies arising from the "personal union" approach. -Peter From seun.ojedeji at gmail.com Tue Sep 22 09:39:39 2015 From: seun.ojedeji at gmail.com (Seun Ojedeji) Date: Tue, 22 Sep 2015 08:39:39 +0100 Subject: [cooperation-wg] IANA Review Committee Selection Process - RIPE Community Support In-Reply-To: <55F854DC.9@oslo.net> References: <55F854DC.9@oslo.net> Message-ID: As one of those that suggested the work of RC be assigned to NRO-NC globally (even though did not successfully convince the CRISP) during the proposal development, I support the suggestion made by Hans. Cheers! On Tue, Sep 15, 2015 at 6:26 PM, Hans Petter Holen wrote: > 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-Public-v1.pdf > > 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 at 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 at oslo.net | http://hph.oslo.net > > > -- ------------------------------------------------------------------------ *Seun Ojedeji,Federal University Oye-Ekitiweb: http://www.fuoye.edu.ng Mobile: +2348035233535**alt email: seun.ojedeji at fuoye.edu.ng * Bringing another down does not take you up - think about your action! -------------- next part -------------- An HTML attachment was scrubbed... URL: From hph at oslo.net Wed Sep 23 07:13:17 2015 From: hph at oslo.net (Hans Petter Holen) Date: Wed, 23 Sep 2015 07:13:17 +0200 Subject: IANA Review Committee Selection Process - RIPE Community Support In-Reply-To: <55FFC6A8.9060902@heanet.ie> References: <55F854DC.9@oslo.net> <55FFC6A8.9060902@heanet.ie> Message-ID: <560234ED.1010806@oslo.net> Hi Brian, Thanks for your questions and comments. On 21.09.15 10.58, Brian Nisbet wrote: > > I think this may be an elegant solution. I am slightly suspicious of > any new piece of work which is supposed to be lightweight and is then > given to already busy people, as it has a habit of spiralling. The NRO-NC already has the following responsibilities as ASO AC according to 3b in the MOU with ICANN: https://archive.icann.org/en/aso/aso-mou-29oct04.htm * a role in Global policy development * make recommendations to the ICANN board on new LIRs * selecting ICANN board member two out of three years * make their own procedures The work of the review committee is to give advice on IANA performance for the numbers community. We do not have any experience with how much work this is going to be, but if we look at the work IANA does for numbers - it is in the range of one request every second month on average. So I would assume reading trough the monthly reports once or twice a year and checking that the Personally I would imagine that this added workload is more than manageable. > > I would also welcome your thoughts on managing the difference between > the term lengths of the two different posts? Thats a good point. I will propose that we modify the terms of the review committee to match the ones of the NRO-NC. > > That said, I don't think these are reasons to oppose your proposal, I > just want to make sure they've been thought about. Good point. -- Hans Petter Holen Mobile +47 45 06 60 54 | hph at oslo.net | http://hph.oslo.net From mschmidt at ripe.net Wed Sep 23 11:35:05 2015 From: mschmidt at ripe.net (Marco Schmidt) Date: Wed, 23 Sep 2015 11:35:05 +0200 Subject: [news] RIPE Policy Proposals - September Update Message-ID: <56027249.4010708@ripe.net> 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 at 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 at 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 at 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-proposals We look forward to your involvement in the PDP. Kind regards, Marco Schmidt RIPE Policy Development Officer RIPE NCC From shane at time-travellers.org Wed Sep 23 17:05:40 2015 From: shane at time-travellers.org (Shane Kerr) Date: Wed, 23 Sep 2015 15:05:40 +0000 Subject: IANA Review Committee Selection Process - RIPE Community Support In-Reply-To: <560234ED.1010806@oslo.net> References: <55F854DC.9@oslo.net> <55FFC6A8.9060902@heanet.ie> <560234ED.1010806@oslo.net> Message-ID: <20150923150540.3acba173@casual> Hans Petter, On Wed, 23 Sep 2015 07:13:17 +0200 Hans Petter Holen wrote: > On 21.09.15 10.58, Brian Nisbet wrote: > > I would also welcome your thoughts on managing the difference between > > the term lengths of the two different posts? > Thats a good point. > I will propose that we modify the terms of the review committee to match > the ones of the NRO-NC. I support the proposal, including this modification. Cheers, -- Shane From brian.nisbet at heanet.ie Wed Sep 23 18:00:46 2015 From: brian.nisbet at heanet.ie (Brian Nisbet) Date: Wed, 23 Sep 2015 17:00:46 +0100 Subject: IANA Review Committee Selection Process - RIPE Community Support In-Reply-To: <560234ED.1010806@oslo.net> References: <55F854DC.9@oslo.net> <55FFC6A8.9060902@heanet.ie> <560234ED.1010806@oslo.net> Message-ID: <5602CCAE.1040808@heanet.ie> Hans Petter, On 23/09/2015 06:13, Hans Petter Holen wrote: > Hi Brian, > Thanks for your questions and comments. > > On 21.09.15 10.58, Brian Nisbet wrote: >> >> I think this may be an elegant solution. I am slightly suspicious of >> any new piece of work which is supposed to be lightweight and is then >> given to already busy people, as it has a habit of spiralling. > > Personally I would imagine that this added workload is more than > manageable. Grans so. >> I would also welcome your thoughts on managing the difference between >> the term lengths of the two different posts? > Thats a good point. > I will propose that we modify the terms of the review committee to match > the ones of the NRO-NC. Sounds good and makes it all very easy indeed. Thanks, Brian From sander at steffann.nl Wed Sep 23 19:22:18 2015 From: sander at steffann.nl (Sander Steffann) Date: Wed, 23 Sep 2015 19:22:18 +0200 Subject: IANA Review Committee Selection Process - RIPE Community Support In-Reply-To: <5602CCAE.1040808@heanet.ie> References: <55F854DC.9@oslo.net> <55FFC6A8.9060902@heanet.ie> <560234ED.1010806@oslo.net> <5602CCAE.1040808@heanet.ie> Message-ID: <83C77CDD-82C1-4474-B83C-512E726157D9@steffann.nl> Hi, > Op 23 sep. 2015, om 18:00 heeft Brian Nisbet het volgende geschreven: > > Hans Petter, > On 23/09/2015 06:13, Hans Petter Holen wrote: > >>> I would also welcome your thoughts on managing the difference between >>> the term lengths of the two different posts? >> Thats a good point. >> I will propose that we modify the terms of the review committee to match >> the ones of the NRO-NC. > > Sounds good and makes it all very easy indeed. +1. Sounds like a good way to do this. Cheers, Sander From meeting at ripe.net Thu Sep 24 09:45:53 2015 From: meeting at ripe.net (Meeting) Date: Thu, 24 Sep 2015 09:45:53 +0200 Subject: RIPE 71 Draft Programme Now Online Message-ID: <5603AA31.7020200@ripe.net> 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 From ripe-wgs.cs at schiefner.de Thu Sep 24 11:26:54 2015 From: ripe-wgs.cs at schiefner.de (Carsten Schiefner) Date: Thu, 24 Sep 2015 11:26:54 +0200 Subject: IANA Review Committee Selection Process - RIPE Community Support In-Reply-To: <560234ED.1010806@oslo.net> References: <55F854DC.9@oslo.net> <55FFC6A8.9060902@heanet.ie> <560234ED.1010806@oslo.net> Message-ID: <5603C1DE.1030405@schiefner.de> Hans Petter, all - On 23.09.2015 07:13, Hans Petter Holen wrote: > On 21.09.15 10.58, Brian Nisbet wrote: >> >> I think this may be an elegant solution. I am slightly suspicious of >> any new piece of work which is supposed to be lightweight and is then >> given to already busy people, as it has a habit of spiralling. > The NRO-NC already has the following responsibilities as ASO AC > according to 3b in the MOU with ICANN: > https://archive.icann.org/en/aso/aso-mou-29oct04.htm > * a role in Global policy development > * make recommendations to the ICANN board on new LIRs > * selecting ICANN board member two out of three years > * make their own procedures > > The work of the review committee is to give advice on IANA performance > for the numbers community. We do not have any experience with how much > work this is going to be, but if we look at the work IANA does for > numbers - it is in the range of one request every second month on > average. So I would assume reading trough the monthly reports once or > twice a year and checking that the > > Personally I would imagine that this added workload is more than > manageable. > >> >> I would also welcome your thoughts on managing the difference between >> the term lengths of the two different posts? > Thats a good point. > I will propose that we modify the terms of the review committee to match > the ones of the NRO-NC. sounds all reasonable to me. I support this. Best, -C. From benno at NLnetLabs.nl Sat Sep 26 22:16:58 2015 From: benno at NLnetLabs.nl (Benno Overeinder) Date: Sat, 26 Sep 2015 22:16:58 +0200 Subject: Last Call for presentations and Draft programme for RIPE 71 Message-ID: <5606FD3A.3000807@NLnetLabs.nl> 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/ From BECHA at ripe.net Tue Sep 29 16:57:23 2015 From: BECHA at ripe.net (Vesna Manojlovic) Date: Tue, 29 Sep 2015 16:57:23 +0200 Subject: Join RIPE Atlas Hackathon - 14-15 November - Bucharest In-Reply-To: <560AA645.8030800@ripe.net> References: <560AA645.8030800@ripe.net> Message-ID: <560AA6D3.4050408@ripe.net> Calling all software developers, designers and network operators! The next RIPE Atlas hackathon takes place 14-15 November in Bucharest, right before RIPE 71. We're looking for creative thinkers to help us find new ways to use RIPE Atlas data to monitor networks and troubleshoot issues as well as ways to improve the existing toolset. Is this you? Then we want to hear from you! ----------------------- How to Apply ----------------------- The application form is online at: https://atlas.ripe.net/hackathon/tools-2015/#!application-form *The deadline to apply is Tuesday, 6 October* Successful applicants will: - Work alongside RIPE Atlas engineers - Get to know others in your field - Contribute to the shared code - Exchange knowledge and experience All source code developed during the hackathon will be publicly licensed and available on GitHub, and will be free for the entire community to use. ---------------------- Hackathon details --------------------- Date: 14-15 November 2015 Time: Saturday 09:00-19:00, Sunday 09:00-21:00 (including party) Location: JW Marriott Bucharest Grand Hotel, Bucharest, Romania Applicants will hear back from the jury on 12 October so that travel arrangements can be made on time. Find out more on RIPE Labs: https://labs.ripe.net/Members/becha/join-the-ripe-atlas-tools-hackathon -------------------- Call for Sponsors ------------------- We are still looking for sponsors! Is your organisation interested in supporting our efforts? Please email me promptly and directly ? thank you! I look forward to seeing you there! Regards, Vesna