<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="">Dear Colleagues,</div>
<div class=""><br class="">
</div>
<div class="">The RIPE NCC Procedural document 'Closure of Members,
Deregistration of Internet
Resources and Legacy Resources' has recently been reviewed and
updated. The following is an overview of the amendments made.</div>
<div class=""><br class="">
</div>
<div class="">Section A.1.1 was amended to include situations where
both the Member and the
RIPE NCC agree to terminate the SSA before the usual three month
period has
passed. Other changes were made to avoid duplication of
information.</div>
<div class=""><br class="">
</div>
<div class="">Section B.2 was updated
to specify certain conditions under which a three month timeframe
for
deregistration of either Member or End User resources would be
unreasonable.</div>
<div class=""><br class="">
</div>
<div class="">The wording in Section B.2.1
was amended to clarify that during the deregistration process the
Member is not
allowed to make new announcements using the resources to be
deregistered, and that
the RIPE NCC will update the maintainer on all the Member's
resource objects - not
just on the inetnum object.</div>
<div class=""><br class="">
</div>
<div class="">Section B.2.2 was
amended to bring about alignment of the procedures for the
deregistration of
End User and Member resources and to clarify that if an End User
does not have
a sponsoring LIR when the deregistration procedure is initiated,
they must
first establish a contractual relationship with one before they
can object to
that procedure.</div>
<div class=""><br class="">
</div>
<div class="">Other amendments were carried out to align the wording
of specific sections with the wording used in
the rest of the document, the RIPE NCC Standard Service Agreement
(Sections A.1.2.2.g and B.1.d), and other RIPE NCC
procedural documents (Section A.1.1). Similarly, changes were
made to reflect changes in the RIPE Database (both operational and
structural) and in RIPE Policy requirements (Sections A.1.2.1.1.c
and B.1.c).</div>
<div class=""><br class="">
</div>
<div class="">Please see here the relevant link:</div>
<div class="">
<a href="https://www.ripe.net/publications/docs/ripe-716/"
class=""><span style="color:blue" class="">https://www.ripe.net/publications/docs/ripe-716/</span></a>
</div>
<div class=""><br>
</div>
<div class="">Kind regards,<br>
<br>
Maria Stafyla<br>
Legal Counsel<br>
RIPE NCC <br>
</div>
</body>
</html>