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] [ncc-announce] [news] RIPE NCC Members and Multiple LIR Accounts - Please Discuss
- Previous message (by thread): [members-discuss] [ncc-announce] [news] RIPE NCC Members and Multiple LIR Accounts - Please Discuss
- Next message (by thread): [members-discuss] [ncc-announce] [news] RIPE NCC Members and Multiple LIR Accounts - Please Discuss
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tim Armstrong
tim at treestle.com
Thu Feb 11 17:09:01 CET 2016
That's not viable yet, have you seen how fragmented the v6 table is, even Tier 1 ISPs have gaps. I would argue that we just reduce the allocation for additional LIRs. That is if a single legal entity (or it's subsidiaries) register a new LIR, then the new LIR registered can only receive a /24 not a /22. This way no one would act in bad faith trying to skirt the rules, and young ISPs still have the ability to grow without feeling significantly choked. -Tim On 11/02/16 17:02, Janis Jaunosans wrote: > just get ipv6. > > On 11/02/16 17:58, Matthias Šubik wrote: >> Additionally … >>> On 11.02.2016, at 16:26, Simon Lockhart >>> <s.lockhart at cablecomnetworking.co.uk> wrote: >>> >>> On Thu Feb 11, 2016 at 04:22:14PM +0100, Sebastian Wiesinger wrote: >>>> * Nigel Titley <exec-board at ripe.net> [2016-02-11 12:02]: >>>>> 2. If this activity is a problem that must be prevented, what action >>>>> should the RIPE NCC take to attempt its prevention? >>>> Do not allow additional LIR accounts for a member. >>> I would concur. >>> >>> One legal entity, one LIR. This should be easy for RIPE to >>> implement, given >>> that they require evidence of company registration or equivalent when >>> establishing an LIR. >> Even if it is possible to open more legal entities in the RIPE >> region, when requiring an exclusive contact person it makes it not >> any harder for really new members, but harder for self cloning of >> members. >> >> It might even be needed, to require the new contact person to >> complete the RIPE course, to slow down abusive behavior. >> The use of a simple nominee is therefor more difficult than without >> the course requirement. >> >> just my two cents >> Matthias >> >> > > ---- > If you don't want to receive emails from the RIPE NCC members-discuss > mailing list, please log in to your LIR Portal account and go to the > general page: > https://lirportal.ripe.net/general/ > > Click on "Edit my LIR details", under "Subscribed Mailing Lists". From > here, you can add or remove addresses. -- <http://liquidns.com> Tim Armstrong Technical Director Treestle B.V. Goudsesingel 78, 3011 KD, Rotterdam, The Netherlands Chamber of Commerce: 59116803 Office: +31 (0) 10 3400 720 Mobile: +31 (0) 61 7544 472 Treestle runs one of the world's fastest global managed DNS platforms at www.liquidns.com <http://www.liquidns.com/> and offers LiquiD AutoScaler, a website-user centric autoscaling solution at www.liquidautoscaler.com <http://www.liquidautoscaler.com/>. Independent software vendor for: <https://apps.db.ripe.net/search/lookup.html?source=ripe&key=ORG-TB77-RIPE&type=organisation> Member of: <https://apps.db.ripe.net/search/lookup.html?source=ripe&key=ORG-TB77-RIPE&type=organisation> <https://aws.amazon.com/marketplace/pp/B013UXHSOO/?ref=_ptnr_pe_> <https://cloudstore.interoute.com/LiquiDAutoScalerBasic><https://liquidautoscaler.com/documentation/other/quickstart> -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20160211/90abd6fb/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: ghbchbij.png Type: image/png Size: 9152 bytes Desc: not available URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20160211/90abd6fb/attachment.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: aifibhfe.png Type: image/png Size: 124 bytes Desc: not available URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20160211/90abd6fb/attachment-0001.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: gjjbefjh.png Type: image/png Size: 3713 bytes Desc: not available URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20160211/90abd6fb/attachment-0002.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: caagfdcg.png Type: image/png Size: 2584 bytes Desc: not available URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20160211/90abd6fb/attachment-0003.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: dbaabeei.png Type: image/png Size: 3491 bytes Desc: not available URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20160211/90abd6fb/attachment-0004.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: cfbgaddf.png Type: image/png Size: 2051 bytes Desc: not available URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20160211/90abd6fb/attachment-0005.png>
- Previous message (by thread): [members-discuss] [ncc-announce] [news] RIPE NCC Members and Multiple LIR Accounts - Please Discuss
- Next message (by thread): [members-discuss] [ncc-announce] [news] RIPE NCC Members and Multiple LIR Accounts - Please Discuss
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]