November 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

some comments on the Accountability Task Force report
by Jim Reid 11 Dec '18

11 Dec '18

The TF are to be thanked for their hard work and producing a fairly good report. The explanation of consensus is excellent and long overdue. Well done for that. However I'm sorry to say the report misses a key point and also considers something that is out of scope and provides nothing to support that position. It also uses horrible American spelling in places -- center instead of centre -- but that's nit-picking. First, the biggie. The report talks about how RIPE is accountable and who it's accountable to, it does not explain what RIPE is accountable *for*. I wonder if these considerations also need to be broken down and documented for various components of RIPE -- Chair, WG Chairs, WG Chairs Collective, Working Groups, Task Forces(!?), etc. The tables starting on p10 don't do that IMO. They describe the functional roles of these entities, not what they are accountable for or to whom. Next, I strongly object to the recommendation that the process for selecting WG chairs should be aligned. This is out of scope for the TF. I fail to see how it fits with "potential gaps where RIPE accountability could be improved or strengthened", which is the closest vaguely suitable bullet point defining the TF's scope. Making that assumption still doesn't put the recommendation in scope because the reports says nothing about why or how aligning the selection process would improve or strengthen things. IMO, such a move would do the very opposite. Read on... I would have expected the role of the TF here would have been to verify (or not) that WG chairs were selected by fair, open and transparent processes that had broad WG/community support. And if there were problems, to identify them. All of that is missing. There's just a recommendation that seems to have been teleported in from a parallel universe without any context or explanation for its inclusion. In fact the report contradicts itself because it earlier states that aligning these procedures violates the principle of bottom-up decision-making. So why make that recommendation and where's the evidence to support it? Either RIPE has confidence in the bottom-up approach or we don't. If the bottom-up approach is unsatisfactory for deciding WG chair selection procedures (why?), what else at RIPE is it no good for? WG's are self-organising and autonomous. They decide their own charters, who the (co)chairs are, what documents and policies get developed, time-lines, consensus decisions, etc, etc. A top-down directive -- from whom? -- saying WG chair appointment procedures must be aligned goes against all of that. It will also undermine another key principle: diversity. [Admittedly that topic's out of scope for this Task Force.] The RIPE community should be perfectly comfortable that its WGs do things differently. That's a strength, not a weakness. Attempts to impose order on this "organised chaos" are the start of a slippery slope that leads to an institution that's in thrall to process. And look how those organisations turn out. A common appointment process is incompatible with RIPE's core values of WG independence, autonomy and diversity. Now it might happen that WGs may one day eventually converge on a common selection procedure -- my bet is some time after the heat death of the universe -- but that has to be a choice for each WG to make for itself. Without outside interference. IMO the TF has no role or authority to get involved in this. It does/did have a role to determine if the WG Chairs were appointed in an open and transparent manner and that the appointees were somehow accountable. Previous (top-down) attempts to have a common selection process have failed. IMO they always will. Getting WG consensus on any sort of selection process is already hard. I know. I've had to do it. Twice. I would prefer WGs spent their time and energies on productive work instead of bickering over process minutae that will just go on and on and on. It would be much less contentious for the report to say something like "The TF thinks a common WG chair selection process might be nice, but accept that has to be a matter for each WG to decide on its own by itself." But even that's pushing it. The evidence so far in favour of a common procedure is at best thin. It's certainly not found in the TF report. I also object to the use of the word "believe" in various places. That suggests a faith-based assessment rather than an evidence-based decision. Matters of belief have no place in RIPE documents.

2 1

RIPE Accountability Task Force: Draft Report and Next Steps
by William Sylvester 11 Dec '18

11 Dec '18

Dear colleagues, Since RIPE 73, the RIPE Accountability Task Force has been looking at the structures, processes and documentation of RIPE to ensure that we: - Are accountable to ourselves as a community - Can explain our workings to newcomers - Can demonstrate our accountability to outside observers We are now ready to share our draft report with the RIPE community and we invite you to share any input on this mailing list by 16 November. The draft report contains a set of recommendations that we will be asking the community to consider when we publish our final report towards the end of the year. You can find the draft report here: https://www.ripe.net/participate/ripe/tf/ripe-accountability-task-force/acc… We will be going over the work of the task force in more detail at RIPE 77 during the Tuesday afternoon plenary session (14:00 - 15:30). If you will be attending the RIPE Meeting or participating remotely, we encourage you to join in and share your feedback there as well. ***Next Steps*** As mentioned above, we will have a comment period until 16 November to gather community input on the draft document. The task force will then implement any required changes to the document before publishing a final version by 14 December at the latest. After the publication of this final report, the task force will disband. The RIPE community can then decide what it wants to do with the final report and whether any of the recommendations need to be implemented. Regards William Sylvester, Chair

2 2

REMINDER: ASO AC Call For Nominations for Seat 10 on the ICANN Board of Directors
by Antony Gollan 22 Nov '18

22 Nov '18

This message is sent on behalf of the Number Resource Organization (NRO). REMINDER: ASO AC Call 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

RACI: Apply Now!
by Gergana Petrova 20 Nov '18

20 Nov '18

Dear colleagues, The RIPE Academic Cooperation Initiative (RACI) is again looking for talented academics in the field of Internet technology. Successful applicants receive complimentary tickets, travel and accommodation to the meetings and the opportunity to present their research. If you are working on something interesting, please apply! If you know someone in your network who is, please forward them this message. https://www.ripe.net/raci --------------------- Application deadlines --------------------- MENOG 19, (TBC): apply by 3 February 2019 SEE 8 (16-17 April, Sarajevo): apply by 3 February 2019 RIPE 78 (20-24 May, Reykjavik): apply by 17 February 2019 ENOG 16 (3-4 June, Tbilisi): apply by 17 February 2019 At ENOG 16 you can present in either Russian or English. --------------------------- Examples of relevant topics --------------------------- - Network measurements and analyses - IPv6 deployment - BGP routing - Network security - Internet governance - Peering and interconnectivity - Internet of Things ------------------------------------------------- Get the latest news on RACI and Internet research ------------------------------------------------- - Subscribe to the RACI mailing list: https://www.ripe.net/raci/mailing-list - Follow us on Twitter: https://twitter.com/raci_ripe - Join our group on LinkedIn: https://www.ripe.net/raci/linkedin Please let me know if you have any questions. Have a lovely day! Best regards, Gergana -- Gergana Petrova External Relations RIPE NCC

1 0

RIPE 81 Call for Host
by Martina De Mas 08 Nov '18

08 Nov '18

Dear colleagues, Are you interested in hosting RIPE 81 from 26-30 October 2020? We're looking for organisations within the RIPE NCC service region to submit their proposal for host consideration no later than *14 December 2018*. A RIPE Meeting Host helps with: venue scouting, Internet connectivity, social events, finding local sponsors and administrative and on-site support. As host, we must be able to depend on you to help organise a smooth, professional and top-quality meeting for our attendees. In return, the host organisation enjoys excellent visibility among the RIPE community and the prestige of hosting a RIPE Meeting. Interested? You can find more information at: https://www.ripe.net/ripe-meetings/call-for-host You can send your proposal by *14 December 2018* to: meeting(a)ripe.net. I look forward to hearing from you, Martina de Mas Event Organiser RIPE NCC

1 0

Re: [ripe-list] [members-discuss] Our AS is in a macro that we don't authorize.
by Dominic Schallert 02 Nov '18

02 Nov '18

Hi Cedric, > If someone put you in theyr as-macro, it's maybe because they give you transit. > Maybe the first search step is search all your transit as who are in this list and check theyr as-macro (get them over peering-db) We do not pay for transit from a Russian-ISP, although our ASN is referenced in their AS-SET. We already tried to contact them multiple times but they do not respond. I’m aware that this is not a practical issue, but still it's wrong. Regards Dominic

1 0

Re: [ripe-list] [members-discuss] Our AS is in a macro that we don't authorize.
by Dominic Schallert 01 Nov '18

01 Nov '18

Hi José, Hi List, we are currently encountering the same 'issue'. We recently received a new ASN which previously had been assigned to another LIR within RIPE-Region. Our ASN is also referenced in several other AS-SETs (including some Russian providers), which we never had any business relation with. We tried to contact them multiple times in order to get our ASN removed from their macros, however, without any success. While this is the way how the RIPE-DB currently works, there are some possible improvements which might be worth to be discussed within the DB-WG; 1) RIPE should remove all macro references if an ASN is returned to the their pool 2) Ability for LIRs to remove unwanted macro references for their ASNs themselves 3) Authorization for referencing ASN’s/AS-SET's in macros (probably not a good idea) Thanks Mit besten Grüßen Kind Regards Dominic Schallert, BA schallert.com e.U. | Hauptstraße 35b, 6800 Feldkirch, Austria FN: 440372g | UID: ATU66209211 | Gerichtsstand: Feldkirch Tel.: +43 680 146 1947 | Fax: +43 134 242 642 616 www.schallert.com <http://www.schallert.com/> | office(a)schallert.com <mailto:office@schallert.com> > Am 30.10.2018 um 15:27 schrieb José Manuel Giner <jm(a)ginernet.com>: > > Hi, we checked that our AS is present in the macro: AS24748:AS-THINX > (they have thousands of AS in their macro) > > After contacting atman.pl who is responsible for this macro, they tell me: > > > It appears that AS59432 is contained in one of our customers AS-SETs and > > it is automatically added to our AS-SET AS24748:AS-THINX > > > > As soon as they remove AS59432, it will disappear from AS24748:AS-THINX > > We have asked him how we can find out who that customer is. But their answer doesn't give us any information. > > > Please be kindly informed that our macros are being built automatically > > according to our customers` macros. If your AS happens to be removed > > from whichever of our customer`s macros, ours is to be changed accordingly. > > We are concerned about this situation and do not know how to proceed. > > Thank you for your help! > > -- > José Manuel Giner > http://ginernet.com > > > _______________________________________________ > members-discuss mailing list > members-discuss(a)ripe.net > https://lists.ripe.net/mailman/listinfo/members-discuss > Unsubscribe: https://lists.ripe.net/mailman/options/members-discuss/ds%40schallert.com

1 0