[ncc-services-wg] Update of RIPE NCC Procedural Document : Closure Procedure

2023-11-06 Thread Kevin Brennan
Dear colleagues, 

The RIPE NCC Procedural document 'Closure of Members, Deregistration of 
Internet Resources and Legacy Resources' has been reviewed and updated. 

The following is an overview of the amendment made.

Section A.1.2.2. (e) Termination with Immediate Effect was amended through 
deletion of the wording which required official postal notification, alongside 
the official notification by email, for termination of the RIPE NCC Standard 
Service Agreement (SSA) in the case of non-payment of the annual contribution 
(service fee) after a period of 120 days from the date of invoice. 

The main reason for this change is that the final notification of termination 
of the SSA by post is superfluous in the case of termination of the SSA due to 
non-payment as the member has already received numerous periodic notifications 
over the course of 120 days and the cause for termination in these instances 
cannot, in any event, be refuted. Further, termination due to non-payment is 
the most frequent cause for termination of the SSA and therefore removing the 
postal notification requirement will reduce the RIPE NCC's administrative 
burden and associated costs. 

Thus, in future cases whereby a member’s SSA is terminated due to non-payment 
the member will receive official notification by email only to their registered 
contacts. 

You can find the updated documents at: 
https://www.ripe.net/publications/docs/ripe-808

Kind regards, 

Kevin Brennan 
Legal Counsel 
RIPE NCC-- 

To unsubscribe from this mailing list, get a password reminder, or change your 
subscription options, please visit: 
https://lists.ripe.net/mailman/listinfo/ncc-services-wg


[ncc-services-wg] Update of RIPE NCC Procedural Document and Transfer Agreement Template

2023-05-16 Thread Kevin Brennan
Dear colleagues,
 
The RIPE NCC Procedural document 'Closure of Members, Deregistration of 
Internet Resources and Legacy Resources' has been reviewed and updated. The 
following is an overview of the amendments made.
 
Section A.1.2.1 (c) Incorrect registration in the RIPE Database was amended 
through the deletion of the following wording:
 
“The inetnum and the inet6num object(s) for approved assignments must use the 
netname(s) approved by the RIPE NCC and not be larger than the size approved by 
the RIPE NCC”

The reason for this change is that the RIPE NCC no longer approves assignments 
or netnames in this regard. Deletion of this wording under the abovementioned 
section therefore aligns current practices with the procedure outlined in 
‘Closure of Members, Deregistration of Internet Resources and Legacy Resources’.
 
Section B 1. (c) Deregistration of Internet Number Resources was amended for 
the same reason, with the same wording being deleted under this section as 
outlined above.
 
Section B.1. (b) Deregistration of Internet Number Resources was further 
amended in order to correctly reflect current RIPE policy with regards to the 
needs-based approach for RIPE NCC-assigned resources. Resources are no longer 
allocated for a specific need. However, the RIPE NCC may assign resources to 
members/End Users for a specific need. Slight changes were made to the wording 
under this section to remove reference to historical RIPE policy provisions and 
to align it with current RIPE policy.
 
Secondly, the RIPE NCC Transfer Agreement Template has been reviewed and 
updated. The following articles have been added:

“2.1 The terms and conditions of this Transfer Agreement do not violate any 
existing laws applicable to the Offering Party or to the Receiving Party.

2.2 In the event that this Transfer Agreement is nullified or deemed invalid 
due to violation of laws described in Article 2.1, the transfer of registration 
of Internet Number Resources shall be reverted and the Internet Number 
Resources shall be returned to the Offering Party”.

In light of a request for transfer of Internet Number Resources, the RIPE NCC 
was made aware of a law prohibitingcertain transactions between Ukrainian and 
Russian entities.

Considering that different national laws might be applicable to the parties 
signing a transfer agreement, these articles were added in order for the RIPE 
NCC to have the parties’ confirmation that the Transfer Agreement does not 
violate any of the laws applicable to them, and their agreement that, in the 
event that the Transfer Agreement is nullified or deemed invalid due to 
violation of such laws, the transfer will be reverted and the Internet Number 
Resources will be returned to the Offering Party. 

Members are advised to use the updated Transfer Agreement template (v6.0) from 
the date of this announcement onwards.

You can find the updated documents at:
https://www.ripe.net/publications/docs/ripe-798
https://www.ripe.net/manage-ips-and-asns/resource-transfers-and-mergers/transfer-of-ip-addresses-and-as-numbers/transfer-agreement-template
  

Kind regards,
 
Kevin Brennan
Legal Counsel
RIPE NCC
 -- 

To unsubscribe from this mailing list, get a password reminder, or change your 
subscription options, please visit: 
https://lists.ripe.net/mailman/listinfo/ncc-services-wg