<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Καλησπέρα, σε περίπτωση που δεν παρακολουθείτε την λίστα. <br>
    </p>
    <p>Γενικότερα υπάρχουν ενδιαφέρουσες εξελίξεις ως προς το rpki (θα
      προσπαθήσω να στείλω κάτι σχετικά με αυτό μόλις βρω χρόνο).</p>
    <p>Ανδρέας<br>
    </p>
    <div class="moz-forward-container"><br>
      <br>
      -------- Forwarded Message --------
      <table class="moz-email-headers-table" border="0" cellspacing="0"
        cellpadding="0">
        <tbody>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
            </th>
            <td>[routing-wg] Towards cleaning up RPKI INVALIDs</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
            <td>Sat, 15 Sep 2018 13:17:00 +0000</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
            <td>nusenu <a class="moz-txt-link-rfc2396E" href="mailto:nusenu-lists@riseup.net"><nusenu-lists@riseup.net></a></td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
            <td>RIPE Routing Working Group <a class="moz-txt-link-rfc2396E" href="mailto:routing-wg@ripe.net"><routing-wg@ripe.net></a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <pre>Hi,

we made an analysis of the RPKI INVALIDs and broke them down by
* RIR
* INVALID reason 
* causing ROA
* number of members each RIR would have to contact to fix them
after filtering them to those prefixes that actually would become unreachable in
an ROV environment.

<a class="moz-txt-link-freetext" href="https://medium.com/@nusenu/towards-cleaning-up-rpki-invalids-d69b03ab8a8c">https://medium.com/@nusenu/towards-cleaning-up-rpki-invalids-d69b03ab8a8c</a>

Looking forward to comments from the WG and RIPE NCC.

The central question in the direction of RIPE NCC is:

Would you be open to reach out to your affected members to inform them about 
their affected IP prefixes? (as has been suggested by Job Snijders before)


kind regards,
nusenu

-- 
<a class="moz-txt-link-freetext" href="https://twitter.com/nusenu_">https://twitter.com/nusenu_</a>
<a class="moz-txt-link-freetext" href="https://mastodon.social/@nusenu">https://mastodon.social/@nusenu</a>


</pre>
    </div>
  </body>
</html>