January 2019 - 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

IANA Numbering Services Review Committee seeks input - 30-day public comment period
by Nurani Nimpuno 12 Feb '19

12 Feb '19

Dear colleagues, As you may be aware, as a result of the successful IANA Stewardship transition in 2016, the IANA Numbering Services are today being managed through an SLA between ICANN and the five RIRs. As part of the result the IANA Stewardship transition, the IANA Numbering Services Review Committee (IANA RC) was established in 2016. The IANA RC is composed of representatives from each RIR region, and advices and assists the RIRs in the review of the IANA Numbering Services. The IANA services are today provided by Public Technical Identifiers (PTI) which publishes monthly performance reports on the IANA Numbering Services (https://www.iana.org/performance/numbers). Based on these monthly performance reports, the five RIRs have produced the 2018 IANA Performance Matrix Summary Report: https://www.nro.net/2018-IANA-Perfomance-Matrix-Summary-Report The IANA RC IANA performance report ----------------------------------- The IANA RC is now launching a public comment period of 30 days, seeking comments and input from the community on the IANA numbering services performance and the 2018 IANA Performance Matrix Summary Report. The IANA RC encourages all members of the Internet number community to review the public IANA Performance Matrix Summary Report. Comments on the IANA service performance should be sent to: <iana-performance(a)nro.net> The IANA RC will publish an annual report in February 2019, as advice to the NRO EC with its evaluation of the IANA Numbering services. The report will be based on the IANA Performance Matrix Summary Report, as well as any input gathered on the performance from the global number community. The public comment period ends on Tueday 22 March at 23:59 UTC. All public comments will be published on the IANA RC website, and will be considered as input to the final report by the IANA. At the end of the 30-day public comment period, the IANA RC will meet and evaluate all input to the final report. The IANA RC report will be published on the IANA RC website: https://www.nro.net/iana-numbering-services-review-committee/ Kind regards, Nurani Nimpuno Chair, IANA Numbering Services Review Committee -- References: ----------- IANA Stewardship Transition Archive https://www.nro.net/internet-governance/iana/iana-stewardship-transition/ Number Community Proposal https://www.nro.net/crisp-final-proposal The SLA for the IANA Numbering Services https://www.nro.net/sla IANA Numbering Services Review Committee https://www.nro.net/iana-numbering-services-review-committee/ Public Technical Identifiers (PTI) https://pti.icann.org Further reading: ---------------- Consolidated RIR IANA Stewardship Proposal Team (CRISP Team) https://www.nro.net/internet-governance/iana/iana-stewardship-transition/st… IANA Stewardship Transition Coordination Group (ICG) https://www.ianacg.org Proposal to Transition the Stewardship of the Internet Assigned Numbers Authority (IANA) Functions https://www.ianacg.org/icg-files/documents/IANA-transition-proposal-final.p…

1 2

New for RIPE 78: Diversity Tickets!
by Amanda Gowland 29 Jan '19

29 Jan '19

Hi all, A diverse RIPE community is a strong RIPE community. For RIPE 78, we're now offering a way for you or your organisation to sponsor a "diversity ticket" to help bring someone from an underrepresented part of the community to the meeting. This is an easy and effective way to pay-it-forward and embrace the next generation of the RIPE community. You can read more about this on RIPE Labs: https://labs.ripe.net/Members/agowland/do-good-at-ripe-78-sponsor-a-diversi… Become a Diversity Sponsor for RIPE 78: https://ripe78.ripe.net/sponsors/become-a-sponsor/ We will continue to add tickets to our event on diversitytickets.org as sponsorship funds are allocated. Warm regards, Amanda Senior Communications Officer RIPE NCC

3 4

RIPE-714 - RIPE Chair document has been published
by Hans Petter Holen 17 Jan '19

17 Jan '19

Consensus has been reached on the RIPE Chair document, following a discussion on the ripe-chair-discuss list and RIPE 77, with a call for consensus at the closing plenary at RIPE 77 and on the ripe-chair-discuss list. The document is now published as RIPE 714 https://www.ripe.net/publications/docs/ripe-714 Thank you very much for all the contributions to the document. Especially to Daniel Karrenberg for authoring the document, To Mirjam Kühne for the ground work, Jim Reid for his contributions and Anna Wilson for leading the discussions at the RIPE meetings. -- Sincerely, Hans Petter Holen - hph(a)oslo.net - +47 45066054

1 0

ASO AC Elects Chair and Appoints Vice Chairs for 2019
by Antony Gollan 10 Jan '19

10 Jan '19

This message is sent on behalf of the Number Resource Organization (NRO). ASO AC Elects Chair and Appoints Vice Chairs for 2019 The Address Supporting Organization Address Council (ASO AC) has re-elected Aftab Siddiqui, the APNIC community representative, as the Chair of the ASO AC/NRO NC for 2019. The ASO AC Chair elections are held annually in January, and the term is one year. Mr. Siddiqui’s appointment was confirmed during the first ASO AC Teleconference of the year, which took place on 9 January, 2019. During this meeting, Kevin Blumberg (ARIN community representative) and Jorge Villa (LACNIC community representative) were appointed as Vice Chairs and will each serve a one-year term. Outgoing Vice Chair Ricardo Patara (LACNIC community representative) was thanked for his hard work during 2018. More information about the ASO AC/NRO NC can be found at: https://www.nro.net/about/address-supporting-organization/the-nro-number-co… Kind regards Antony Gollan Senior Communications Officer RIPE NCC

1 0

Call for presentations RIPE 78
by Benno Overeinder 10 Jan '19

10 Jan '19

Dear colleagues, Please find the CFP for RIPE 78 below or at: https://ripe78.ripe.net/submit-topic/cfp/. The deadline for submissions is *3 March 2019*. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings. However, on an individual basis, participants can apply for a RIPE Fellowship or RACI, see the "Speakers" paragraph in CFP for more information. Kind regards, Benno Overeinder RIPE PC Chair https://ripe78.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 78 will take place from 20-24 May in Reykjavik, Iceland* 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 78. See the full descriptions of the different presentation formats: https://ripe78.ripe.net/submit-topic/presentation-formats/ Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than *3 March 2019*. 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. Please note that participants can apply for a RIPE Fellowship or RACI, on an individual basis, 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 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. ---- 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://ripe78.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://ripe78.ripe.net/submit-topic/ - Lightning talks should also be submitted using the meeting submission system (https://ripe78.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. Childcare places are limited, so please be quick to reserve a spot for your child while registering for the meeting. More information at: https://ripe78.ripe.net/on-site/on-site-childcare/ 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

ICANN Board Seat 10 Elections: Comment Phase Ending Soon
by Antony Gollan 09 Jan '19

09 Jan '19

This message is sent on behalf of the Number Resource Organization (NRO). The comment phase of the Address Supporting Organization Address Council (ASO AC) ICANN Board Seat 10 Elections will end at *23:59 UTC on 15 January 2019.* Following a call for candidates, the ASO AC announced that the following three candidates had been nominated and invited the Numbers community to provide comments and feedback: - Dmitry Burkov - Akinori Maemura - Andile Ngcaba The comment phase began on 1 December 2018. If you have not done so already, please add your comments/feedback to the candidates' profiles at: https://aso.icann.org/aso-icann/icann-board-elections/2018-19-icann-board-o… Regards Antony Gollan Senior Communications Officer RIPE NCC

1 0