September 2018 - ripe-list - mailman.ripe.net

Re: [ripe-list] [ncc-announce] [news] New RIPE NCC Ticketing System and Contact Form
by sergey＠devnull.ru 01 Jul '19

01 Jul '19

Dear Matt, I have a question regarding new ticketing system. Some days ago I sent an email and attached a file to my message. I received a receipt of ticket, then the NCC staff member replied to my question and I received a mail that contain a previous email content and a weblink to the file I attached before. The link was active and I was able to download the file. The link points to https://ripencc.zendesk.com/attachments/token/blablabla/?name=filename. The problem I see is that ripencc.zendesk.com is a hostname on the server in a cloud, the network is assigned to an Irish company and it seems that the file storage is not under RIPE NCC's control. This hostname is not reachable over IPv6, but this is not the issue I wish to discuss now. Can you clarify whether e-mail attachments/archives at RIPE NCC are stored at the third party servers? Do you think it is acceptable? Thank you. -- Kind regards, Sergey Myasoedov > On 1 Nov 2017, at 14:12, Matt Parker <mparker(a)ripe.net> wrote: > > Dear Colleagues, > > Today, the RIPE NCC launches its new ticketing system. There is a RIPE > Labs article that explains the background behind this change at: > https://labs.ripe.net/Members/AlexBand/ticketing-and-document-management-at… > > This change will mostly impact RIPE NCC staff and will not change how > you deal with the RIPE NCC. You should still make requests for > resources, transfers, company name changes, etc. through your LIR > account via my.ripe.net. > > All your questions and reports can be channeled through our new contact > form, which combines the old contact and report form functionality. The > new form also presents suggested content to users that can help to > provide them with useful information. The form is available at: > https://www.ripe.net/contact-form > > Submissions made through the form will be ticketised and all > documentation will be stored separately and securely in the RIPE NCC's > Document Management System. > > Please reply to the emails you receive to ensure your ticket is updated. > You should add your replies to tickets at the top of your email and not > reply "in line". Additional documentation can be submitted via the My > Tickets functionality available to LIR account holders at: > https://my.ripe.net/#/tickets > > We have planned the migration to have as little impact as possible. If > you do experience any delays in response during this period, please bear > with us. And if you have any questions, please let me know. > > Best regards, > > Matt Parker > Business Analyst - Product Management > RIPE NCC >

7 8

Input by the NRO Executive Council on the Public Consultation to Determine the Future Structure of the ASO
by Antony Gollan 27 Sep '18

27 Sep '18

This message is sent on behalf of the Number Resource Organization (NRO) Input by the NRO Executive Council on the Public Consultation to Determine the Future Structure of the ASO Proposed Next Steps In January 2018, the NRO Executive Council responded to the 18 resulting recommendations that were issued following the second independent review of the Address Supporting Organization (ASO) carried out in 2017 by ITEMS International. The last of these Recommendations was that a public consultation be held in each of the five RIR communities to determine the future structure of the ICANN Address Supporting Organization (ASO). The recommended public consultations have been initiated in each RIR community over the past six months, including discussions on mailing lists and at meetings in each of the five regions. The NRO EC have considered results of this process to date, and have distilled the following points as a proposed way forward. 1) While not specifically asked as part of our consultation, there was prevailing view across the communities that the number community’s relationship with ICANN (that which is referred as the ASO relationship) should continue. A significant number of community members suggested that the relationship must be significantly simplified and its focus limited to number community matters. 2) The ASO Review recognised that the number community relationship with ICANN is unlike that of other Supporting Organizations. The number community’s engagement with ICANN serves primarily to facilitate coordination of global Internet number resource policies. It follows that number community representatives be careful in appraising current and future proposed ICANN-related work items, and be prepared to decline those that lie outside this scope. 3) It is clear that the existence of two separate identities (those of the NRO and the ASO) leads to complexity and confusion in the ICANN relationship. The NRO EC will work with the ICANN organisation to determine the viability of consolidating the number community’s participation in ICANN under either the “Number Resource Organization” or the “Address Supporting Organisation”. 4) The number community finds value in the ICANN relationship and in ICANN’s defined role as described above. We support ICANN in continuing to undertake this role, and will support continuing evolution of our relationship, including further changes as needed, as time goes on. The NRO EC provides this statement to the RIR communities in each region as a possible common way forward to aid in their consideration of the future structure of the ASO. Regards Antony Gollan Senior Communications Officer RIPE NCC

1 0

2018-04 Proposal Accepted and Implemented (PDP Clarification)
by Marco Schmidt 26 Sep '18

26 Sep '18

Dear colleagues, Consensus has been reached on 2018-04, "PDP Clarification". This proposal clarified the options available to the Working Group chairs at the end of the Review Phase of the RIPE Policy Development Process (PDP). You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-04 The new RIPE Document is called ripe-710 and is available at: https://www.ripe.net/publications/docs/ripe-710 This proposal is implemented with immediate effect. Thank you to everyone who provided input. Kind regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

1 0

2018-04 Review Phase (PDP Clarification)
by Marco Schmidt 24 Sep '18

24 Sep '18

Dear colleagues, Proposal 2018-04, "PDP Clarification" is now in the Review Phase. This proposal aims to clarify the options available to the Working Group chairs at the end of the Review Phase of the RIPE Policy Development Process (PDP). The RIPE NCC has prepared an impact analysis on this latest proposal version to support the community’s discussion. You can find the full proposal and impact analysis at: https://www.ripe.net/participate/policies/proposals/2018-04 And the draft documents at: https://www.ripe.net/participate/policies/proposals/2018-04/draft As per the RIPE Policy Development Process (PDP), the purpose of this four week Review Phase is to continue discussing the proposal, taking the impact analysis into consideration, and to review the full draft RIPE Policy Document. At the end of the Review Phase, the RIPE Chair will determine whether the proposal has reached rough consensus. It is therefore important to provide your opinion, even if it is simply a restatement of your input from the previous phase. We encourage you to read the proposal, impact analysis and draft document and send any comments to <ripe-list(a)ripe.net> before 17 July 2018. Kind regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

11 11

ASO AC Calls For Nominations for Seat 10 on the ICANN Board of Directors
by Antony Gollan 24 Sep '18

24 Sep '18

This message is sent on behalf of the Number Resource Organization (NRO). ASO AC Calls For Nominations for Seat 10 on the ICANN Board of Directors In line with the ICANN Address Supporting Organization (ASO) Memorandum of Understanding (MoU) and the ICANN Bylaws, the Address Supporting Organization Address Council (ASO AC) has issued a call for nominations for Seat 10 on the ICANN Board of Directors: https://aso.icann.org/aso-icann/icann-board-elections/2018-19-icann-board-o… The selected candidate will serve for a three-year term, which will begin at the conclusion of the ICANN Annual General Assembly during the ICANN 66 Meeting, scheduled from 2-7 November 2019 in Montréal, Canada. Eligibility Requirements All nominated candidates must meet the selection criteria and conflict of interest requirements as outlined in Article 7 of the ICANN Bylaws. The nominated candidates will undergo a due diligence review by an independent ICANN contractor. Nomination Process Community members are invited to submit nominations by email to <nominations [at] aso [dot] icann [dot] org> by Friday, 30 November 2018 at 23:59 UTC. Nominations must include the following information: - The full name of the person being nominated. - Contact email address of the person being nominated. - Contact telephone number (if available) of the person being nominated. - The full name of the person making the nomination. - Contact email address for the person making the nomination. - Contact telephone number of the person making the nomination. Regional Restrictions The ICANN Bylaws state that the Directors selected by a Supporting Organization (SO) for its assigned Board seat(s) cannot reside in the same geographic region (see Section 7.2:c). The current ASO AC selection for Seat 9, Ron da Silva, resides in the ARIN region. Therefore, no nominations for Seat 10 can be accepted from candidates residing in the ARIN region. Important Dates - Nomination Phase: 15 September 2018 – 30 November 2018 - Comment Phase: 1 December 2018 – 15 January 2019 - ICANN Due Diligence for nominated candidates: 1 – 15 January 2019 - Interview Phase: 1 – 28 February 2019 - Selection Phase (deliberation): 1 February 2019 – 14 March 2019 - Selection Phase (voting): 15 – 21 March 2019 - Announcement of selected candidate: around 22 March 2019 Further Information - More information and updated announcements will be added to to the dedicated 2018/19 Seat 10 elections page on the ASO website: https://aso.icann.org/aso-icann/icann-board-elections/2018-19-icann-board-o… - Detailed procedures for election of individuals to the ICANN Board of Directors by the ASO AC can be found in Section 9 of the ASO AC Operating Procedures: https://aso.icann.org/documents/operational-documents/operating-procedures-… If you have any questions about the elections or the election process, please contact <secretariat [at] nro [dot] net>. Regards Antony Gollan Senior Communications Officer RIPE NCC

1 0

RIPE 77 Meeting - one month to go!
by Martina De Mas 10 Sep '18

10 Sep '18

Dear colleagues, RIPE 77 takes place at the Hotel Okura in Amsterdam from 15-19 October 2018. If you haven’t yet registered, follow this link to secure your place: https://ripe77.ripe.net/register --------- Programme --------- The draft meeting plan is available online: https://ripe77.ripe.net/programme/meeting-plan/ There are still some plenary, tutorial and BoF slots left. If you have something you’d like to share with the community, please submit a proposal before 21 September at: https://ripe77.ripe.net/submit-topic/cfp/ RIPE 77 socials are great opportunities to network with other attendees. Check out the socials and plan your evenings: https://ripe77.ripe.net/programme/social-events/ ---------------------- RIPE Networking App ---------------------- Easily network with fellow attendees using our open-source app built by the RIPE NCC. All you need to log in is a RIPE NCC Access account: https://ripe77.ripe.net/on-site/ripe-networking-app/ ------------------- On-site Childcare ------------------- We are making it easier for attendees with children (ages 6 months – 10 years old) to attend RIPE Meetings by offering a professional, on-site childcare service. Space is limited, so please reserve your spot ASAP: https://ripe77.ripe.net/on-site/on-site-childcare/ ---------------------------------- Become a RIPE Meeting Mentor! ---------------------------------- Are you an experienced RIPE Meeting attendee that wants to give back to the community? Pay it forward by becoming a RIPE Meeting Mentor to a newcomer: https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-mentors ------------ More information on RIPE 77 can be found at: https://ripe77.ripe.net/ Follow us on Facebook and Twitter: @ripemeeting, #RIPE77 Best regards, Martina de Mas Event Organiser RIPE NCC

1 0

Reminder: NRO NC Call for Nominations
by Axel Pawlik 10 Sep '18

10 Sep '18

Dear colleagues, This is a reminder that 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 Nurani Nimpuno ends on 31 December 2018. The deadline for nominations is *21 September 2018*. Any individual residing within the RIPE NCC service region is eligible for nomination, except Regional Internet Registry (RIR) staff members. Self-nominations are permitted. The nomination process is available at: https://www.ripe.net/s/nroncnominations2018 The election to the NRO NC seat will take place during the RIPE 77 Meeting to be held in Amsterdam from 15-19 October 2018. All members of the Internet community who are present at the RIPE Meeting may vote in the election. Please send your nominations to <nominations(a)ripe.net> by 23:59 UTC on 21 September 2018. All confirmed nominations will be listed on the RIPE NCC website by 24 September 2018. 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>. The current confirmed candidates and expressions of support for them are published on the RIPE NCC website at: https://www.ripe.net/s/nronccandidates Regards, Axel Pawlik Managing Director RIPE NCC Important dates: 21 September 2018: Deadline for NRO NC nominations 24 September 2018: Deadline for all confirmed nominations to be posted on the RIPE NCC website 15-19 October 2018: Election to fill NRO NC seat at the RIPE 77 Meeting in Amsterdam 19 October 2018: Announce successful candidate at closing plenary of RIPE 77

1 0

Last call for presentations and Draft programme for RIPE 77
by Benno Overeinder 07 Sep '18

07 Sep '18

Colleagues, A list of currently accepted RIPE 77 presentations is now published at: https://ripe77.ripe.net/programme/meeting-plan/plenary/ There are still plenary, BoF, tutorial and workshop slots remaining for the final RIPE 77 programme and RIPE Programme Committee will accept new proposals until *21 September 2018*. This is our last call for you to submit your proposals. You can find the CFP for RIPE 77 below or at https://ripe77.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, see the "Speakers" paragraph in CFP for more information. Kind regards, Benno Overeinder RIPE PC Chair https://ripe77.ripe.net/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 77 will take place from 15-19 October in Amsterdam, The Netherlands* 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 77. See the full descriptions of the different presentation formats: https://ripe77.ripe.net/submit-topic/presentation-formats/ Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than *21 September 2018*. Proposals submitted after this date will be considered depending on the slots still available in the programme. The PC is looking for presentations covering the 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) ---- Speakers ---- Presenters, RIPE Working Group Chairs and the RIPE Programme Committee are required to cover their own costs to attend a RIPE Meeting (meeting ticket, travel and accommodation). We have various ticket options available depending on your needs. In extraordinary circumstances, the RIPE Chair can waive the meeting fee for presenters. These requests are dealt with on a case-by-case basis via pc(a)ripe.net. Also note that, on an individual basis, participants can apply for a RIPE Fellowship or RACI to develop their professional or academic career. For more information, please visit: https://www.ripe.net/participate/ripe/ripe-fellowship https://www.ripe.net/participate/ripe/raci ---- Submissions ---- Presenters should be clear on whether they wish to submit a presentation for a plenary or working group (WG) session. At present, most working groups will solicit policy proposals, discussion points or other content directly via their mailing lists. If you’re not sure what kind of session you should be presenting at, please visit: https://ripe77.ripe.net/plenary-or-wg/ 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 should 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 (during evening sessions) - Lightning talks: 10 minutes in total for both the presentation and any discussion The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe77.ripe.net/submit-topic/ - Lightning talks should also be submitted using the meeting submission system (https://ripe77.ripe.net/submit-topic/) 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. ---- Diversity and Inclusion - On-Site Childcare and the RIPE Meeting Code of Conduct ---- Did you know that RIPE Meetings now have on-site childcare? You can reserve a spot for your child (age 6 months – 10 years) during the registration process for the meeting. Registrations for RIPE 77 will open mid-July. Childcare places are limited, so please be quick to reserve a spot for your child! Read about the experiences of our next generation of engineers at: https://labs.ripe.net/Members/agowland/ripe-meeting-diversity-efforts-on-si… Ensuring that RIPE Meeting values are upheld and that attendees experience a professional, respectful and safe meeting is a priority. Please do read the RIPE Meeting Code of Conduct: https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-o… --- If you have any questions or requests concerning content submissions, please email pc(a)ripe.net.

1 0