[members-discuss] RIPE forces us to pay the bill unfairly

Hello,

First my email Mohamed at Bubtaina.com is the same as
Mohamed.Bubtaina at Bubtaina.com but I send my emails on the run, I think
nobody in here never suffered a breach or have had stolen a password or
some of the kind in any way, to start with, nobody should talk for in the
name of someone else and should be careful of the person submitting the
email is actually him. And not someone using his email so to know who
everyone is referring to. RIPE, Like IANA, Like ICANN has a set of rules
and regulations which we had a general election and agreed on the agenda
and on new agreements. Quarterly yearly each has his own personal
circumstances which if can’t pay or want to make a different deal would do
it directly with RIPE administration, if it needs voting from NCC members
then shall it be when they see necessary. If your organisation is
registered doesn’t mean it has an LIR I have my subsidiaries as maintainers
for my own infrastructure which if it is a problem, I’ll be glad to remove
but doesn’t change the fact that they have no resources except me which is
the same as my company which is one and not 2 according to my contract that
I signed for NCC .whatever the regulations commits to I follow sometimes
you don’t notice due to many interferences.but I thought that’s what NCC
members stand.s for we work as a network not individual! Why not talk about
having each NCC member an HPC dedicated VPN server for us and our work?
Wouldn’t that be a good idea! With the Atlas Probe and An Anchor which we
could buy also, in collaboration with IANA and ICANN to maybe connect other
RIR within we could cut lots of issues and problems and keep and eye on
data network flow making sure our iOS aren’t being used for malpractice and
fraud and crimes!  I that could be the reason why some want to get rid of
part of their Resources! They cant keep and eye for data privacy GDPR
regulations policies law and other, on 1024 people device application
network or someone using illegally their ips right! Well that’s coming from
an MBA student with human resource information system and management
background.

Regards

Bubtaina

On Friday, 20 July 2018, Max Tulyev <maxtul at netassist.ua> wrote:

> As I understand people who started that topic:
>
>
> 1. They have several LIRs for one company.
>
> 2. Last LIR was opened in 2nd quarter of this year, and payments are
> QUARTERLY.
>
> 3. They wish to transfer resource from ANOTHER LIR (NOT the last one was
> opened this year).
> 4. RIPE NCC issued the invoice for that ANOTHER LIR for 1st quarter, when
> that LIR did not exists.
>
> 5. To let the transfer from FIRST LIR, they have to paid for 1st quarter
> of the SECOND LIR, which was opened in 2nd quarter.
>
>
> So, it violates points 1 and 2(3) of what you said below (and common
> sense, of course).
>
>
> 20.07.18 16:32, Christoph Neukirch пише:
>
> Guys,
>
>
>
> There is no problem.
>
>
>
> What’s so hard to read and understand the rules and policies. It has been
> written and described multiple times in this thread. And policies has been
> accepted signing the contract with RIPE NCC.
>
>
>
> In simple short words:
>
>    - For opening a LIR in the middle of the year you have to pay the
>    current and all following quarters for the current year.
>    - If you want to close a LIR, you have to pay at least ONE FULL annual
>    fee for this LIR, no matter if it’s the first year and you would only have
>    to pay for quarters from the creation of the year.
>    - Same applies to your wish to transfer resources.
>    - Annual means once every year, not once in a timeframe including 12
>    months.
>    - You DON’T pay for resources, you pay for services from RIPE NCC,
>    both sides using policies and rules developed by the RIPE community.
>
>
>
> Having said this, I second the opinion to not expect too much sympathy on
> this topic. And IMHO you’ll achieve the opposite pushing this topic any
> further.
>
>
>

-- 

Best Regards,


Mohamed Ali Bubteina


[image: image1.png]


Tel  +44 (0) 20 7862 6331

Cell +44 (0) 747474 0934 - +961 (79) 1111 93

Fax +44 (0) 203 608 0612

Email: Manager at Bubteina.Group

Email: *Mohamed at Bubtaina.com*


Registered name: Bubtaina Group  Limited

Place of registration: England and Wales

Registered number: 08762428


The information in this email is confidential and solely for the use of the
intended recipient(s). If you receive this email in error, please notify
the sender and delete the email from your system immediately. In such
circumstances, you must not make any use of the email or its contents.


Views expressed by an individual in this email do not necessarily reflect
the views of Bubtaina Group Limited. The company and its Subsidiaries,
complies with the EU-U.S Privacy Shield Framework and Swiss U.S Privacy
Shield as set forth by the U.S Department of Commerce and with the
Information Commissioner Office in the United Kingdom, regarding use,
collection, and retention of any information held and maintained.


Compliance framework with:


[image: image2.jpeg]      [image: image3.jpeg]       [image: image4.png]




Partners and subsidiaries:



 [image: image6.png]           [image: image7.jpeg]       [image:
image9.png]        [image: image10.png]      [image: image11.png]
    [image: image12.png]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20180720/d71fc15a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 8755 bytes
Desc: not available
URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20180720/d71fc15a/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.png
Type: image/png
Size: 5179 bytes
Desc: not available
URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20180720/d71fc15a/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 12116 bytes
Desc: not available
URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20180720/d71fc15a/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 11717 bytes
Desc: not available
URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20180720/d71fc15a/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 11018 bytes
Desc: not available
URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20180720/d71fc15a/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 11965 bytes
Desc: not available
URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20180720/d71fc15a/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.png
Type: image/png
Size: 3715 bytes
Desc: not available
URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20180720/d71fc15a/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 7922 bytes
Desc: not available
URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20180720/d71fc15a/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 9713 bytes
Desc: not available
URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20180720/d71fc15a/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 4075 bytes
Desc: not available
URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20180720/d71fc15a/attachment-0006.png>