<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Hi all,</p>
    <p>I support. In my opinion: It should be possible to get this done
      after verification that all parts of the /21 are registered to the
      same resource holder.</p>
    <p>Maybe that will have to be manual action, and i guess you (Mark)
      don't mind. I'm also guessing that this only applies to very few
      cases...?<br>
    </p>
    <p>$ whois -h whois.afrinic.net -- -M 192.96.24.0/21 -T route</p>
    <p>tells me what Mark described: 8 route objects for the 8 /24s</p>
    <p><br>
    </p>
    <p>Regards,</p>
    <p>Frank<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 28/08/18 14:35, Mark Elkins wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:429fef3b-5553-acc9-12f4-0636fc318216@posix.co.za">
      <meta http-equiv="content-type" content="text/html; charset=utf-8">
      <p>Hello members of DBWG. I am an AFRINIC member who has 8
        consecutive /24's of address space. Their number were chosen so
        that I could aggregate them together into a single /21, after
        all, aggregation is good? I had (at RIPE) historically
        aggregated them together in two smaller blocks.<br>
      </p>
      <p>They are now properly aggregated in the RIPE Database as a
        single route object:</p>
      <p>% Information related to '192.96.24.0/21AS6083'<br>
        <br>
        route:          192.96.24.0/21<br>
        origin:         AS6083<br>
        descr:          Posix Systems, South Africa, Aggregate all<br>
        mnt-by:         POSIX-MNT<br>
        created:        2018-08-14T16:18:27Z<br>
        last-modified:  2018-08-14T16:18:27Z<br>
        source:         RIPE # Filtered<br>
        <br>
      </p>
      <div class="moz-forward-container">...but I can not do the same
        thing in the AFRINIC IRR?<br>
        <br>
        They are registered as eight single /24's in the AFRINIC IRR
        though.<br>
        <br>
        I would thus like some discussion and support for allowing
        blocks to be aggregated when possible - as in this case. This
        will be a "new feature" (according to Madhvi's e-mail copied
        below) in the AFRINIC IRR.<br>
        Do people thing aggregation is a good idea? (it reduces the
        amount of memory needed in Routers that hold effectively "route
        objects").<br>
        It also showing that it is currently impossible to migrate all
        route objects from RIPE to AFRINIC - which is bad because Frank
        Habicht has reminded me that route[6] objects made up of AFRINIC
        resources in the RIPE Database will have less "authority"
        (RIPE-NONAUTH) from the 4th of September - just days away. <br>
        (From :- <br>
        <table class="moz-email-headers-table" border="0"
          cellspacing="0" cellpadding="0">
          <tbody>
            <tr>
              <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Subject:
              </th>
              <td>Implementation plan and dates for NWI5 - Out-of-region
                ROUTE(6) objects and removal of ASN authorisation for
                ROUTE(6) object creation.</td>
            </tr>
            <tr>
              <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Date:
              </th>
              <td>Thu, 19 Jul 2018 15:23:58 +0200</td>
            </tr>
            <tr>
              <th nowrap="nowrap" valign="BASELINE" align="RIGHT">From:
              </th>
              <td>Nathalie Trenaman <a class="moz-txt-link-rfc2396E"
                  href="mailto:nathalie@ripe.net" moz-do-not-send="true"><nathalie@ripe.net></a></td>
            </tr>
            <tr>
              <th nowrap="nowrap" valign="BASELINE" align="RIGHT">To: </th>
              <td><a class="moz-txt-link-abbreviated"
                  href="mailto:nanog@nanog.org" moz-do-not-send="true">nanog@nanog.org</a></td>
            </tr>
          </tbody>
        </table>
        <pre>...We will implement these changes in the Release Candidate environment on
Thursday, 2 August and go to full production on Tuesday, 4 September....</pre>
        )<br>
        <br>
        I was one of three AFRINIC Members who attended a discussion on
        this at iWeek/AfPIF in Cape Town last week and I discussed the
        above problem at that session as well as via e-mail to AFRINIC
        and personally to Alan Barrett, the AFRINIC CEO. I have
        otherwise copied what I can of my objects from RIPE to AFRINIC
        and delete objects that are no longer required from the RIPE
        Database - i.e. - I am doing what I understand good members of
        AFRINIC should be doing.<br>
        <br>
        Please add your support.<br>
        <br>
--------------------------------------------------------------------------------------------------------------------------------------<br>
        <br>
        -------- Forwarded Message --------
        <table class="moz-email-headers-table" border="0"
          cellspacing="0" cellpadding="0">
          <tbody>
            <tr>
              <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Subject:
              </th>
              <td>[AFRINIC IRR #622756] Fwd: SUCCESS : Your object is
                successfully created in AFRINIC database</td>
            </tr>
            <tr>
              <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Date:
              </th>
              <td>Tue, 28 Aug 2018 13:34:53 +0400</td>
            </tr>
            <tr>
              <th nowrap="nowrap" valign="BASELINE" align="RIGHT">From:
              </th>
              <td>Madhvi Gokool via RT <a class="moz-txt-link-rfc2396E"
                  href="mailto:irr@afrinic.net" moz-do-not-send="true"><irr@afrinic.net></a></td>
            </tr>
            <tr>
              <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Reply-To:
              </th>
              <td><a class="moz-txt-link-abbreviated"
                  href="mailto:irr@afrinic.net" moz-do-not-send="true">irr@afrinic.net</a></td>
            </tr>
            <tr>
              <th nowrap="nowrap" valign="BASELINE" align="RIGHT">To: </th>
              <td><a class="moz-txt-link-abbreviated"
                  href="mailto:mje@posix.co.za" moz-do-not-send="true">mje@posix.co.za</a></td>
            </tr>
          </tbody>
        </table>
        <br>
        <br>
        <pre>Hello Mark

The scenario that you are requesting for is a new feature. We would like to
invite you to subscribe to the AFRINIC Database Working Group <a class="moz-txt-link-abbreviated" href="mailto:dbwg@afrinic.net" moz-do-not-send="true">dbwg@afrinic.net</a>
(if not already done) and propose that such a feature be incorporated in the
AFRINIC IRR. The reason is that this queue <a class="moz-txt-link-abbreviated" href="mailto:irr@afrinic.net" moz-do-not-send="true">irr@afrinic.net</a> is meant to give
support on the current IRR.
I have shared the "issue" you encountered with other colleagues working on the
IRR enhancements. We look forward to discussion on new feature
requests/improvements on the DBWG. You will also be able to share the best
current practices based on your experience.

Regards
Madhvi


On Tue Aug 21 18:42:51 2018, <a class="moz-txt-link-abbreviated" href="mailto:mje@posix.co.za" moz-do-not-send="true">mje@posix.co.za</a> wrote:

  The number resources are of course separate /24's. Nothing wrong with
  that. However, I want to be a responsible Internet citizen - which means
  aggregating the blocks together as a single block. In order to do that,
  my Transit Provider (workonline.africa - note: they used to use
  workonline.co.za) wants a route object in a routing database in order
  for that to happen. He builds filters directly from the Routing Databases.
  
  I may in the future wish to advertise one of these single /24's from
  another location - so please don't play with individual /24's that would
  break this from happening.

--------------------------------------------------------------------------------------------------------------------------------------

The original creation of the Object gave me:-
 
On Tue Aug 14 22:06:44 2018, <a class="moz-txt-link-abbreviated" href="mailto:mje@posix.co.za" moz-do-not-send="true">mje@posix.co.za</a> wrote:

  Hiya guys, What is this message all about? I did the same on RIPE and it
  was live instantly.



  -------- Forwarded Message --------

   Subject: SUCCESS : Your object is successfully created in AFRINIC database                   
    Date:   Tue, 14 Aug 2018 17:35:00 +0000                                                     
    From:   AFRINIC Database Notifications <a class="moz-txt-link-rfc2396E" href="mailto:no-reply@afrinic.net" moz-do-not-send="true"><no-reply@afrinic.net></a> (<a class="moz-txt-link-freetext" href="mailto:no-reply@afrinic.net" moz-do-not-send="true">mailto:no-reply@afrinic.net</a>) 
     To:    <a class="moz-txt-link-abbreviated" href="mailto:mje@posix.co.za" moz-do-not-send="true">mje@posix.co.za</a> (<a class="moz-txt-link-freetext" href="mailto:mje@posix.co.za" moz-do-not-send="true">mailto:mje@posix.co.za</a>)                                            
  SUMMARY OF UPDATE:
  
  Number of objects found:                   1
  Number of objects processed successfully:  1
    Create:         0
    Modify:         0
    Delete:         0
    No Operation:   1
  Number of objects processed with errors:   0
    Create:         0
    Modify:         0
    Delete:         0
  
  DETAILED EXPLANATION:
  
  
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  The following object(s) were processed SUCCESSFULLY:
  
  ---
  Create PENDING: [route] 192.96.24.0/21AS6083
  
  route:          192.96.24.0/21
  descr:          Posix Systems, South Africa, Aggregate all
  origin:         AS6083
  mnt-by:         POSIX-MNT
  changed:            <a class="moz-txt-link-abbreviated" href="mailto:mje@posix.co.za" moz-do-not-send="true">mje@posix.co.za</a>  (<a class="moz-txt-link-freetext" href="mailto:mje@posix.co.za" moz-do-not-send="true">mailto:mje@posix.co.za</a>)   20180814
  source:         AFRINIC
  
  ***Info:    Authorisation for [inetnum] 0.0.0.0 - 255.255.255.255 failed
              using "mnt-lower:"
              not authenticated by: AFRINIC-HM-MNT
  
  ***Warning: This update has only passed one of the two required hierarchical
              authorisations
  
  ***Info:    The route object 192.96.24.0/21AS6083 will be saved for one week
              pending the second authorisation
  
  
  
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I think personally that AFRINIC just has to authorise it? (not authenticated by: AFRINIC-HM-MNT)</pre>
      </div>
      <pre class="moz-signature" cols="72">-- 
Mark James ELKINS  -  Posix Systems - (South) Africa
<a class="moz-txt-link-abbreviated" href="mailto:mje@posix.co.za" moz-do-not-send="true">mje@posix.co.za</a>       Tel: +27.128070590  Cell: +27.826010496
For fast, reliable, low cost Internet in ZA: <a class="moz-txt-link-freetext" href="https://ftth.posix.co.za" moz-do-not-send="true">https://ftth.posix.co.za</a>
</pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
DBWG mailing list
<a class="moz-txt-link-abbreviated" href="mailto:DBWG@afrinic.net">DBWG@afrinic.net</a>
<a class="moz-txt-link-freetext" href="https://lists.afrinic.net/mailman/listinfo/dbwg">https://lists.afrinic.net/mailman/listinfo/dbwg</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>