- members-discuss - mailman.ripe.net

Bots subscribed to the list
by Dominik Nowacki 03 Jun '15

03 Jun '15

Following bots are again subscribed to the list: registry(a)resilans.se<mailto:registry@resilans.se> support(a)flops.ru<mailto:support@flops.ru> Manager Hoster.KZ manager(a)hoster.kz<mailto:manager@hoster.kz> arcade solutions ag <support(a)arcade.ch> Following failed responses received: SYMPA <sympa(a)list2.orange.com> Your message for list 'rus-conf.ipregs' (attached below) was rejected. You are not allowed to send this message for the following reason: you are not allowed to perform this action. For further information, please contact rus-conf.ipregs-request(a)list2.orange.com<mailto:rus-conf.ipregs-request@list2.orange.com> -- Mail Delivery System do-not-reply(a)tickets.denit.net<mailto:do-not-reply@tickets.denit.net> I'm afraid to say that I was unable to deliver your email with the subject 'Re: [members-discuss] [#VER-185-22767]: Re: NCC changing descr fields'. None of the addresses which your message was addressed to matched one which I can accept e-mail for. Please retry your message or contact the system administrator for further information. -- Can anyone from RIPE deal with this, please? I really hate getting spammed every time I chose to send a mail to this discussion list! With Kind Regards, Dominik Nowacki Clouvider Limited is a limited company registered in England and Wales. Registered number: 08750969. Registered office: 88 Wood Street, London, United Kingdom, EC2V 7RS. Please note that Clouvider Limited may monitor email traffic data and also the content of email for the purposes of security and staff training. This message contains confidential information and is intended only for the intended recipient. If you do not believe you are the intended recipient you should not disseminate, distribute or copy this e-mail. Please notify abuse(a)clouvider.net<mailto:abuse@clouvider.net> of this e-mail immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Clouvider Limited nor any of its employees therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.

3 2

NCC changing descr fields
by Paul Civati 03 Jun '15

03 Jun '15

It seems as though someone has decided to run a process of 'tidying up' in the RIPE db by fiddling with descr fields. I've been informed that: === During one of our data consistency checks, we saw that the resource holder information for these resources is not consistent: x.x.x.0-y.y.y.255 We will therefore be updating the resource holder information in the RIPE database objects to <company> and ORG-xxxx-RIPE on 2015-06-08." === This is somewhat mysterious, vague and puzzling Confusing because all the relevant handle and organisation records point to the correct objects for this block. Upon asking NCC what they are doing, I'm told that the descr field is incorrect and will be amended, actually to remove from it "London". What on earth is the point of this whole exercise? This has generated confusion on my part and a waste of support resource in NCC to deal with my query. We already have admin, tech and org fields that point to the identifying organisation for the object but now someone has decided that the descr field must have duplicated information. The help section in whois mentions nothing about what data is to be in descr field, nor do I recall any mandate that it must be set to the name of the organisation. I can't be the only one confused by this vague change and asking NCC what is going on and why. Summary: seems a totally pointless waste of time. I guess someone in NCC was bored because I can't see any other point of this. Regards, Paul. -- Paul Civati <paul(at)racksense.com> 0870 321 2855 Rack Sense Ltd - Managed Service Provider - www.racksense.com

3 3

Re: [members-discuss] [ncc-announce] [GM] RIPE NCC Charging Scheme and ASNs
by Nick Hilliard 02 Apr '15

02 Apr '15

On 02/04/2015 15:09, Nigel Titley wrote: > There will therefore be two resolutions on charging at the GM: > > - Members will be asked to vote to approve or reject the Charging Scheme > 2016 that was published on 24 March: > https://www.ripe.net/lir-services/ncc/gm/may-2015/supporting-documents > > - Members will also be asked to vote to approve or reject a resolution > that would instantiate a EUR 50 charge per ASN Nigel, thanks for bringing this in as a voting item on the agenda. I believe this to be the best way to resolve the issue in the long term. There are ~27000 asns assigned by the RIPE NCC. Assuming a €50 annual charge, this will raise additional revenue of approx. €1.3m or around €120 per LIR. If the NCC membership votes in favour of a charge for ASNs, could you clarify whether this additional revenue will be: 1. used to drop the 2016 LIR charge from €1400 to around the €1300 mark, 2. retained as a surplus by the RIPE NCC, 3. returned to the membership by way of a future credit, as outlined in the last GM, or 4. something else. thanks, Nick

4 3

auto-responders and ticket robots
by Elvis Daniel Velea 02 Apr '15

02 Apr '15

Hi, rmplc-reject(a)rmplc.co.uk do-not-reply(a)tickets.denit.net sympa(a)list2.orange.com support(a)arcade.ch Please verify your subscriptions in the LIR Portal and stop sending me auto-replies. 1. rmplc-reject(a)rmplc.co.uk said: > Your email todiscuss(a)ripe.net has not been delivered. > > The POP3 email service for domain rmplc.co.uk has been ceased. You will need to contact the intended recipient via another means. that even looks like a bad error, my e-mail has reached the list! 2. do-not-reply(a)tickets.denit.net said: > I'm afraid to say that I was unable to deliver your email with the subject 'Re: [members-discuss] [ncc-announce] [GM] Draft RIPE NCC Charging Scheme 2016'. > > None of the addresses which your message was addressed to matched one which I can accept e-mail for. Please retry your message or contact the system administrator for further information. Denit, of your subscribed employee no longer works there, maybe you should login to the LIR Portal and update the subscription e-mail address. 3. sympa(a)list2.orange.com said: > Your message for list 'rus-conf.ipregs' (attached below) was rejected. > You are not allowed to send this message for the following reason: > > you are not allowed to perform this action. > > For further information, please contactrus-conf.ipregs-request(a)list2.orange.com Bad filter? C'mon Orange.. you can do better. 4. support(a)arcade.ch said: >Elvis Daniel Velea, > > Sehr geehrter Kunde Das ist eine automatisch generierte Antwort, die den Eingang Ihrer Nachricht bestätigt. Wir werden Ihr Anliegen bearbeiten. Sollten Rückfragen unsererseits nötig sein, wird sich einer unserer Mitarbeiter so schnell wie > möglich mit Ihnen in Verbindung setzen. Wenn Sie uns auf diese Bestätigung antworten möchten, stellen Sie bitte sicher, dass die Ticket ID in der Betreffzeile für uns weiterhin sichtbar bleibt. So können wir Ihre Antwort richtig zuordnen. > > *Ticket ID: *MHJ-500-20375 > *Betreff:* Re: [members-discuss] [ncc-announce] [GM] Draft RIPE NCC Charging Scheme 2016 > *Abteilung: *arcade - service desk > *Typ: *Issue > *Status: *Offen > *Priorität:* Normal Ticketing systems subscribed to the mailing list? A new ticket with every response? I bet your colleagues handling these tickets are very happy, arcade solutions... cheers, elvis -- <http://v4escrow.net> Elvis Daniel Velea Chief Executive Officer Email: elvis(a)V4Escrow.net <mailto:elvis@v4escrow.net> US Phone: +1 (702) 475 5914 EU Phone: +31 (0) 61458 1914 Recognised IPv4 Broker/Facilitator in: This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received this email in error, please notify the sender immediately and delete the original.Any other use of this email is strictly prohibited.

3 2

Re: [members-discuss] [ncc-announce] [GM] Draft RIPE NCC Charging Scheme 2016
by Brandon Butterworth 29 Mar '15

29 Mar '15

> I'm not that sure anymore, the AS transfer policy is being implemented > and ASN16s will soon have a value once the free pool is depleted. People have learnt from v4 that you don't give up scarce things. One day people will pay for them, and as I said the other week if you want to garbage collect them you'd have to charge a high price to make it worth giving up (or pay as others have suggested) and people won't vote for that. A 50 Euro fee is way too low to do it and a pointless complication to the simplified charging scheme. I also doubt the unadvertised figure gives the whole picture, some will be used privately (no idea how many). I think trying to retrofit other hand back schemes now is futile (it was hard to hand back once, back when people wanted to hand back) brandon

6 6

Re: [members-discuss] [ncc-announce] [GM] Draft RIPE NCC Charging Scheme 2016
by Brandon Butterworth 29 Mar '15

29 Mar '15

> I do not really believe that the purpose of this discussion has ever > been garbage collection. I thought it was, at least some people said it was, and nobody said the NCC needs to tax something to raise more money how about ASNs. > That makes it 27128 assigned ASNs. If each would have a (very low) 50E > fee, that would bring ~1.35M Eur additional budget to the RIPE NCC which > could be spent on outreach or could be used to lower member fees. Has the NCC said it needs more money (it could raise the existing fee if it did) If the total stays the same it's just reverting to an older charging scheme. I don't see the value in doing that. > I think that is the discussion we are having and I believe this has > always been the reasoning for the presentation at the GM and the noise > on the mailing list. Then I totally missed it. The NCC really needs loads more money? > I also think we should forget about garbage collection in ASN16 because > it will never happen. That was my point brandon

1 0

Re: [members-discuss] [ncc-announce] [GM] Draft RIPE NCC Charging Scheme 2016
by Daniel Karrenberg 29 Mar '15

29 Mar '15

To put this discussion into perspective I suggest to have a look at http://www.potaroo.net/tools/asn32/ and specifically the second table under "Current Status". I suggest to compare the ratio of the columns "Unadv" and "Adv" for our region with the total and with other regions. Daniel

3 2

Re: [members-discuss] [ncc-announce] [GM] Draft RIPE NCC Charging Scheme 2016
by Hank Nussbacher 29 Mar '15

29 Mar '15

At 22:47 28/03/2015 +0000, Jamie Stallwood wrote: >Here's a crazy thought. Instead of trying to raise charges the members >aren't keen to accept, why not offer a one-off account credit for returned >resources? It might be a nominal amount such as EUR 10, but even a small >carrot is better than a stick that you cannot use. Or how about requesting the return of unused ASNs and in exchange issue a 1M credit on RIPE ATLAS? -Hank

1 0

Re: [members-discuss] [ncc-announce] [GM] Draft RIPE NCC Charging Scheme 2016
by Sander Steffann 29 Mar '15

29 Mar '15

Hi Nigel, > There has been discussion on charging for AS Numbers. The board believes > that this discussion was not conclusive and there was not sufficient > consensus to change the model that was approved by the membership in 2012. > The board also believes that it should not influence addressing policy > through the charging scheme, although the model can be adjusted in the > future to take into account policies that have been agreed by the RIPE > community. I strongly disagree with the board here. There is already a policy that has consensus from the RIPE community that asks for this. Saying that the board will take into account future policies from the RIPE community but not one that already exists is just wrong. The RIPE NCC should implement *all* RIPE policies, not only those it chooses to implement. That way the board is actually influencing address policy through the charging scheme by adopting a charging scheme that is in conflict with RIPE address policy. The RIPE NCC and its members have deviated from RIPE policy in 2012, and this should be rectified as soon as possible. Cheers, Sander

17 47

Re: [members-discuss] [ncc-announce] [GM] Draft RIPE NCC Charging Scheme 2016
by Jamie Stallwood 29 Mar '15

29 Mar '15

Here's a crazy thought. Instead of trying to raise charges the members aren't keen to accept, why not offer a one-off account credit for returned resources? It might be a nominal amount such as EUR 10, but even a small carrot is better than a stick that you cannot use. Kind regards Jamie Stallwood -- Jamie Stallwood Security Specialist Imerja Limited M: 07795 840385 Sent from mobile secured by Good (www.good.com) -----Original Message----- From: Nigel Titley [nigel(a)titley.com] Sent: Saturday, March 28, 2015 10:37 PM GMT Standard Time To: members-discuss(a)ripe.net Subject: Re: [members-discuss] [ncc-announce] [GM] Draft RIPE NCC Charging Scheme 2016 On 28/03/15 22:25, Sascha Luck [ml] wrote: > On Sun, Mar 29, 2015 at 12:11:35AM +0300, Fahad AlShirawi wrote: >> NCC gives us an estimate of any costs directly associated with >> ASN billing, risk assessment if any, and we vote on whether or >> not we want the NCC to pursue another option in the future that >> is ASN billing related. Yes? > > There is nothing to stop the board from proposing a CS option > with an ASN charge >0 now. Do I understand you correctly in that this > vote should determine > whether the NCC will *always* have to present a CS option with > ASN charge >0 or just for the next CS proposal? I think it is unwise to bind the NCC/Board for all time (and I don't actually think this is possible anyway). Nigel ---- 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.

2 1