This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[members-discuss] Feedback Requested: RIPE NCC Broker List
- Previous message (by thread): [members-discuss] R: Feedback Requested: RIPE NCC Broker List
- Next message (by thread): [members-discuss] Feedback Requested: RIPE NCC Broker List
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
NOC xervers
noc at xervers.pt
Thu Dec 19 11:17:59 CET 2019
Hello everyone. I would vote for option C for the following reasons: 1st - Is not the job of RIPE NCC to check how brokers work and their integrity. 2nd - RIPE already does verifications for the transfers. Isn't that a double job? Yes. So, a broker is not needed at all. 3rd - Personally, i am totally against that list. Having a broker list would mean that someone is doing benefit on resource transfers. Transfers between different entities should be done under the RIPE contract terms (enterprise acquisitions or same enterprise having several LIRs and regrouping them) and NOT otherwise. If someone has uneeded resources, these should be given back to RIPE. Those resources don't belong to that person/enterprise in first place. We have to keep in mind that all resources belong to RIPE and RIPE let us use them. They are NOT OUR property! Regards --- NOC xervers | +351 300 404 316 P Please consider the environment before printing this email [2] [3] [4] [5] A 2019-12-19 10:37, Schnabeltier escreveu: >> Dear colleagues, >> >> I think we have three options. I would vote for option B: >> >> A) Keeping the list. >> >> B) We would consider it as important to have a list of reliable brokers. The RIPE NCC would only publish information of brokers which are verified. If the majority would vote for this option, we have to find a solution how to verify the integrity of brokers. >> >> C) We do not consider a list of reliable brokers as important. While RIPE NCC cannot or does not want to validate the integrity of brokers at this moment, the list should be removed. >> >> ------------------------- >> From: Christian Kaufmann <exec-board at ripe.net [1]> >> Sent: Thursday, 19. Dec 2019 - 10:17 CET +0100 >> To: members-discuss at ripe.net [1] >> >> Subject: [members-discuss] Feedback Requested: RIPE NCC Broker List > Dear RIPE NCC members, > > The Executive Board has been following this discussion and we can see > general agreement for a change in the way brokers are listed on the RIPE > NCC's website. > > The question is whether the RIPE NCC should remove the list entirely, or > otherwise take steps to improve its approach. There are pros and cons > with both options. > > Removing the list is straightforward and would spare the RIPE NCC a few > headaches. However, it is worth considering whether the current model > provides some incentive for brokers to play by the rules and what might > happen if this incentive is gone. > > Conversely, it's clear that some brokers are still spamming RIPE > Database contacts. Is this the only problem we are seeking to eliminate > here, or are there others? Could an updated set of terms or a stricter > approach by the RIPE NCC help to mitigate this? > > Before the board makes its decision, we would like to hear your thoughts > on this list. > > Kind regards, > > Christian Kaufmann > RIPE NCC Executive Board Chairman > > _______________________________________________ > members-discuss mailing list > members-discuss at ripe.net > https://mailman.ripe.net/ > Unsubscribe: https://lists.ripe.net/mailman/options/members-discuss/ripe-member-discuss%40cidr.eu > > _______________________________________________ > members-discuss mailing list > members-discuss at ripe.net > https://mailman.ripe.net/ > Unsubscribe: https://lists.ripe.net/mailman/options/members-discuss/noc%40xervers.pt Links: ------ [1] http://xervers.pt/./#NOP [2] https://www.xervers.pt/ [3] https://www.trustpilot.com/review/www.xervers.pt [4] https://www.facebook.com/xervers/ [5] https://twitter.com/xervers -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20191219/dc70ec71/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: 9fc0e43c.png Type: image/png Size: 9562 bytes Desc: not available URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20191219/dc70ec71/attachment.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: f86205d1.png Type: image/png Size: 1339 bytes Desc: not available URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20191219/dc70ec71/attachment-0001.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: 8c978722.png Type: image/png Size: 499 bytes Desc: not available URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20191219/dc70ec71/attachment-0002.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: 310b3ada.png Type: image/png Size: 529 bytes Desc: not available URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20191219/dc70ec71/attachment-0003.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: 8c6cd433.png Type: image/png Size: 533 bytes Desc: not available URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20191219/dc70ec71/attachment-0004.png>
- Previous message (by thread): [members-discuss] R: Feedback Requested: RIPE NCC Broker List
- Next message (by thread): [members-discuss] Feedback Requested: RIPE NCC Broker List
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]