<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Dear Collegues!</p>
<p>Looking at the impact analysis, the proposal and reviewing the
arguments - i would like to agree with this proposal.</p>
<p>In the best case scenario it may improve the accuracy of database
entries. I also belive it will aid the goals of the registry
because this way the usage of inetnums can be documented more
clearly.</p>
<p>Kind Regards</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 12/13/23 19:14, Jeroen Lauwers
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:95D9287F-25D6-40FC-9D22-4C2841BB36FC@a2b-internet.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<span id="docs-internal-guid-14f656db-7fff-8585-5e25-d8bf4d539b27"
class="">
<div
style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span
style="font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">Dear
colleagues,</span></div>
<br class="">
<div
style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span
style="font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">Though
we recognise that most of you are probably busy preparing for the upcoming holidays, we would like to ask you to share your opinion on proposal 2023-04. Remember that Policy Development Process requires any comments made during the Discussion phase must be
repeated during the Review phase in order to count towards or against rough consensus, as your views can now take the RIPE NCC’s Impact Analysis into account.</span></div>
<br class="">
<div
style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span
style="font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">Here
are some questions for the WG to get the discussion started: Do you already use AGGREGATED-BY-LIR when registering IPv6 assignments? Would you find it convenient and useful to be able to register IPv4 assignments in the same way? Does 2023-04 address this
use case well in its current form, or could you think of any potential improvements?</span></div>
<br class="">
<div
style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span
style="font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">We
hope you will find the time to let your voice be heard!</span></div>
<br class="">
<div
style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span
style="font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">The
Policy Development Process requires the proposers to adequately address any suggestions for changes or objections to the proposal in each phase, which we will do below.</span></div>
<h2 dir="ltr"
style="line-height: 1.38; margin-top: 18pt; margin-bottom: 6pt;"
class="">
<span
style="font-size: 16pt; font-family: Arial, sans-serif; font-weight: 400; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">1. Does 2023-04 change
the contact registration requirements for assignments?</span></h2>
<br class="">
<div
style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span
style="font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">The
argument made is that the statement </span><span
style="font-size: 11pt; font-family: Arial, sans-serif; font-style: italic; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">«When
an End User has a network using public address space this must be registered separately with the contact details of the End User»</span><span
style="font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">
found in the current policy (and removed by 2023-04 in order to bring the wording in line with that of the IPv6 policy), implicitly requires LIRs to register non-delegated/outsourced contact information for the End User in the RIPE database, not necessarily
in the mandatory «admin-c» or «tech-c» attributes, but possibly in an optional attribute like «descr», «org» or «remarks».</span></div>
<h3 dir="ltr"
style="line-height: 1.38; margin-top: 16pt; margin-bottom: 4pt;"
class="">
<span
style="font-size: 14pt; font-family: Arial, sans-serif; color: rgb(67, 67, 67); font-weight: 400; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">Proposers’
response:</span></h3>
<div
style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span
style="font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">We
do not believe so, for the following reasons, and keeping the current practice and policies in consideration:</span></div>
<br class="">
<ol
style="margin-top: 0px; margin-bottom: 0px; padding-inline-start: 48px;"
class="">
<li dir="ltr" aria-level="1"
style="list-style-type: upper-alpha; font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre;"
class="">
<div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"
class=""><span
style="font-size: 11pt; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">The
RIPE NCC does not consider that 2023-04 changes the contact registration requirements in any way[1][2][3]. Absent any (rough) consensus in the Working Group to the contrary, we defer to the RIPE NCC’s judgement on this point.</span></div>
</li>
<li dir="ltr" aria-level="1"
style="list-style-type: upper-alpha; font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre;"
class="">
<div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"
class=""><span
style="font-size: 11pt; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">The
practice of creating assignments with all contact information delegated is already widespread. If this was a policy violation made possible due to the RIPE NCC implementing RIPE policy incorrectly, we would have expected the community to take action to correct
this situation. However, no such policy proposal has been put forward by the community.</span></div>
</li>
<li dir="ltr" aria-level="1"
style="list-style-type: upper-alpha; font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre;"
class="">
<div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"
class=""><span
style="font-size: 11pt; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">Outsourcing
and delegation of contact information is a common practice across many industries, including in networking and information technology. There is no policy language that explicitly prohibits this for IPv4 assignments. Absent that, we believe any implicit prohibition
found “between the lines” is essentially «void for vagueness»[4].</span></div>
</li>
<li dir="ltr" aria-level="1"
style="list-style-type: upper-alpha; font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre;"
class="">
<div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"
class=""><span
style="font-size: 11pt; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">An
obligation to publish the End User’s contact information in the RIPE database will constitute a violation of Article 6(3) of the RIPE Database Terms and Conditions[5] and Article 6(1)(a) of the GDPR[6], if the End User’s contact person has not given explicit
consent to such publication. We believe that the RIPE policy cannot reasonably be interpreted to require LIRs to break EU law (and even if it explicitly did require that, EU law would still take precedence).</span></div>
</li>
<li dir="ltr" aria-level="1"
style="list-style-type: upper-alpha; font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre;"
class="">
<div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"
class=""><span
style="font-size: 11pt; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">The
policy’s stated goal of registering assignments is «to ensure uniqueness and to provide information for Internet troubleshooting at all levels»[7]. Requiring LIRs to publish the contact information of End Users who often will not have any knowledge or capability
to aid with troubleshooting does work towards this attaining goal. On the contrary, delegating the contact information to the LIR/ISP may well be the only way to attain this goal.</span></div>
</li>
</ol>
<br class="">
<div
style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span
style="font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">[1]
</span><a
href="https://www.ripe.net/ripe/mail/archives/address-policy-wg/2023-September/013856.html"
style="text-decoration: none;" class=""
moz-do-not-send="true"><span
style="font-size: 11pt; font-family: Arial, sans-serif; color: rgb(17, 85, 204); font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; text-decoration: underline; text-decoration-skip-ink: none; vertical-align: baseline; white-space: pre-wrap;"
class="">https://www.ripe.net/ripe/mail/archives/address-policy-wg/2023-September/013856.html</span></a></div>
<div
style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span
style="font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">[2]
</span><a
href="https://www.ripe.net/participate/policies/proposals/2023-04#impact-analysis"
style="text-decoration: none;" class=""
moz-do-not-send="true"><span
style="font-size: 11pt; font-family: Arial, sans-serif; color: rgb(17, 85, 204); font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; text-decoration: underline; text-decoration-skip-ink: none; vertical-align: baseline; white-space: pre-wrap;"
class="">https://www.ripe.net/participate/policies/proposals/2023-04#impact-analysis</span></a></div>
<div
style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span
style="font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">[3]
</span><a
href="https://www.ripe.net/ripe/mail/archives/address-policy-wg/2023-November/013892.html"
style="text-decoration: none;" class=""
moz-do-not-send="true"><span
style="font-size: 11pt; font-family: Arial, sans-serif; color: rgb(17, 85, 204); font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; text-decoration: underline; text-decoration-skip-ink: none; vertical-align: baseline; white-space: pre-wrap;"
class="">https://www.ripe.net/ripe/mail/archives/address-policy-wg/2023-November/013892.html</span></a></div>
<div
style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span
style="font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">[4]
</span><a href="https://www.law.cornell.edu/wex/void_for_vagueness"
style="text-decoration: none;" class=""
moz-do-not-send="true"><span
style="font-size: 11pt; font-family: Arial, sans-serif; color: rgb(17, 85, 204); font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; text-decoration: underline; text-decoration-skip-ink: none; vertical-align: baseline; white-space: pre-wrap;"
class="">https://www.law.cornell.edu/wex/void_for_vagueness</span></a></div>
<div
style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span
style="font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">[5]
</span><a
href="https://www.ripe.net/manage-ips-and-asns/db/support/documentation/terms"
style="text-decoration: none;" class=""
moz-do-not-send="true"><span
style="font-size: 11pt; font-family: Arial, sans-serif; color: rgb(17, 85, 204); font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; text-decoration: underline; text-decoration-skip-ink: none; vertical-align: baseline; white-space: pre-wrap;"
class="">https://www.ripe.net/manage-ips-and-asns/db/support/documentation/terms</span></a></div>
<div
style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span
style="font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">[6]
</span><a
href="https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32016R0679#d1e1888-1-1"
style="text-decoration: none;" class=""
moz-do-not-send="true"><span
style="font-size: 11pt; font-family: Arial, sans-serif; color: rgb(17, 85, 204); font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; text-decoration: underline; text-decoration-skip-ink: none; vertical-align: baseline; white-space: pre-wrap;"
class="">https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32016R0679#d1e1888-1-1</span></a></div>
<div
style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span
style="font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">[7]
</span><a href="https://www.ripe.net/publications/docs/ripe-804#3"
style="text-decoration: none;" class=""
moz-do-not-send="true"><span
style="font-size: 11pt; font-family: Arial, sans-serif; color: rgb(17, 85, 204); font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; text-decoration: underline; text-decoration-skip-ink: none; vertical-align: baseline; white-space: pre-wrap;"
class="">https://www.ripe.net/publications/docs/ripe-804#3</span></a></div>
<h2 dir="ltr"
style="line-height: 1.38; margin-top: 18pt; margin-bottom: 6pt;"
class="">
<span
style="font-size: 16pt; font-family: Arial, sans-serif; font-weight: 400; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">2. The «assignment-size»
attribute should be a CIDR prefix length</span></h2>
<div
style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span
style="font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">Leaving
it undefined could result in some LIRs using it to represent an IPv4 address count, while others would use it to represent a CIDR prefix length.</span></div>
<h3 dir="ltr"
style="line-height: 1.38; margin-top: 16pt; margin-bottom: 4pt;"
class="">
<span
style="font-size: 14pt; font-family: Arial, sans-serif; color: rgb(67, 67, 67); font-weight: 400; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">Proposers’
response:</span></h3>
<div
style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span
style="font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">We
agree «assignment-size» should be a CIDR prefix length. We understand that, if proposal 2023-04 would be accepted, the RIPE NCC could implement the «assignment-size» attribute for IPv4 inetnum objects to be a CIDR prefix length, and document it as such. Therefore
we do not believe it is necessary to spell this out explicitly in the policy document (it is not spelled out in the IPv6 policy document either).</span></div>
<br class="">
<br class="">
<div
style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span
style="font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">Thank
you for your attention and enjoy your holidays!</span></div>
<br class="">
<div
style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span
style="font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">Best
regards,</span></div>
<div
style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span
style="font-size: 11pt; font-family: Arial, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"
class="">Jeroen
and Tore</span></div>
</span><br class="Apple-interchange-newline">
<div><br class="">
<blockquote type="cite" class="">
<div class="">Op 21 nov. 2023, om 11:13 heeft Angela Dall'Ara
<<a href="mailto:adallara@ripe.net"
class="moz-txt-link-freetext" moz-do-not-send="true">adallara@ripe.net</a>>
het volgende geschreven:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class=""><br class="">
Dear colleagues,<br class="">
<br class="">
Policy proposal 2023-04, “Add AGGREGATED-BY-LIR status for
IPv4 PA assignments”, is now in the Review Phase.<br
class="">
<br class="">
The goal of this proposal is to introduce the
AGGREGATED-BY-LIR status for IPv4 PA assignments to reduce
LIR efforts in registration and maintenance.<br class="">
<br class="">
This proposal has been updated and it is now at version
2.0. The proposed policy text did not change, the only
difference is that the section "Arguments opposing the
proposal" includes a reference to the last round of
discussion.<br class="">
<br class="">
The RIPE NCC has prepared an impact analysis on this
proposal to support the community’s discussion.<br
class="">
<br class="">
You can find the proposal and impact analysis at:<br
class="">
<a
href="https://www.ripe.net/participate/policies/proposals/2023-04"
class="moz-txt-link-freetext" moz-do-not-send="true">https://www.ripe.net/participate/policies/proposals/2023-04</a><br
class="">
<a class="moz-txt-link-freetext" href="https://www.ripe.net/participate/policies/proposals/2023-04#impact-analysis">https://www.ripe.net/participate/policies/proposals/2023-04#impact-analysis</a><br
class="">
And the draft document at:<br class="">
<a class="moz-txt-link-freetext" href="https://www.ripe.net/participate/policies/proposals/2023-04/draft">https://www.ripe.net/participate/policies/proposals/2023-04/draft</a><br
class="">
<br class="">
As per the RIPE Policy Development Process (PDP), the
purpose of this four-week Review Phase is to continue the
discussion of the proposal taking the impact analysis into
consideration, and to review the full draft RIPE Policy
Document.<br class="">
<br class="">
At the end of the Review Phase, the Working Group (WG)
Chairs will determine whether the WG has reached rough
consensus.<br class="">
It is therefore important to provide your opinion, even if
it is simply a restatement of your input from the previous
phase.<br class="">
<br class="">
We encourage you to read the proposal, impact analysis and
draft document and to send any comments to
<a class="moz-txt-link-abbreviated" href="mailto:address-policy-wg@ripe.net">address-policy-wg@ripe.net</a> before 20 December 2023.<br
class="">
<br class="">
Kind regards,<br class="">
Angela Dall'Ara<br class="">
Policy Officer<br class="">
RIPE NCC<br class="">
<br class="">
-- <br class="">
<br class="">
To unsubscribe from this mailing list, get a password
reminder, or change your subscription options, please
visit:
<a class="moz-txt-link-freetext" href="https://mailman.ripe.net/">https://mailman.ripe.net/</a><br
class="">
</div>
</div>
</blockquote>
</div>
<br class="">
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
</blockquote>
</body>
</html>