<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    <div class="moz-forward-container">fyi<br>
      <br>
      -------- Original Message --------
      <table class="moz-email-headers-table" border="0" cellpadding="0"
        cellspacing="0">
        <tbody>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
            </th>
            <td>[lacnog] Fwd: RFC 7020 on The Internet Numbers Registry
              System</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
            <td>Sat, 24 Aug 2013 01:53:44 -0300</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
            <td>Carlos M. Martinez <a class="moz-txt-link-rfc2396E" href="mailto:carlosm3011@gmail.com"><carlosm3011@gmail.com></a></td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Reply-To:
            </th>
            <td>Latin America and Caribbean Region Network Operators
              Group <a class="moz-txt-link-rfc2396E" href="mailto:lacnog@lacnic.net"><lacnog@lacnic.net></a></td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
            <td>Latin America and Caribbean Region Network Operators
              Group <a class="moz-txt-link-rfc2396E" href="mailto:lacnog@lacnic.net"><lacnog@lacnic.net></a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <meta http-equiv="content-type" content="text/html;
        charset=ISO-8859-1">
      <div>Se publicÃ&sup3; el documento sucesor de la RFC 2050, aquella que
        establecia lineamientos generales sobre la funciÃ&sup3;n de registro
        aplicada a direcciones.</div>
      <div><br>
      </div>
      <div>Saludos </div>
      <div><br>
      </div>
      <div>Carlos<br>
        <br>
        Sent from my iPad</div>
      <div><br>
        Begin forwarded message:<br>
        <br>
      </div>
      <blockquote type="cite">
        <div><b>From:</b> <a moz-do-not-send="true"
            href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a><br>
          <b>Date:</b> 23 August 2013 21:04:26 GMT-03:00<br>
          <b>To:</b> <a moz-do-not-send="true"
            href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>,
          <a moz-do-not-send="true"
            href="mailto:rfc-dist@rfc-editor.org">rfc-dist@rfc-editor.org</a><br>
          <b>Cc:</b> <a moz-do-not-send="true"
            href="mailto:drafts-update-ref@iana.org">drafts-update-ref@iana.org</a>,
          <a moz-do-not-send="true"
            href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a><br>
          <b>Subject:</b> <b>RFC 7020 on The Internet Numbers Registry
            System</b><br>
          <b>Reply-To:</b> <a moz-do-not-send="true"
            href="mailto:ietf@ietf.org">ietf@ietf.org</a><br>
          <br>
        </div>
      </blockquote>
      <blockquote type="cite">
        <div><span>A new Request for Comments is now available in online
            RFC libraries.</span><br>
          <span></span><br>
          <span></span><br>
          <span>        RFC 7020</span><br>
          <span></span><br>
          <span>        Title:      The Internet Numbers Registry System
          </span><br>
          <span>        Author:     R. Housley, J. Curran,</span><br>
          <span>                    G. Huston, D. Conrad</span><br>
          <span>        Status:     Informational</span><br>
          <span>        Stream:     IETF</span><br>
          <span>        Date:       August 2013</span><br>
          <span>        Mailbox:    <a moz-do-not-send="true"
              href="mailto:housley@vigilsec.com">housley@vigilsec.com</a>,
          </span><br>
          <span>                    <a moz-do-not-send="true"
              href="mailto:jcurran@arin.net">jcurran@arin.net</a>, </span><br>
          <span>                    <a moz-do-not-send="true"
              href="mailto:gih@apnic.net">gih@apnic.net</a>,</span><br>
          <span>                    <a moz-do-not-send="true"
              href="mailto:drc@virtualized.org">drc@virtualized.org</a></span><br>
          <span>        Pages:      9</span><br>
          <span>        Characters: 19332</span><br>
          <span>        Obsoletes:  RFC 2050</span><br>
          <span></span><br>
          <span>        I-D Tag:    draft-housley-rfc2050bis-02.txt</span><br>
          <span></span><br>
          <span>        URL:        <a moz-do-not-send="true"
              href="http://www.rfc-editor.org/rfc/rfc7020.txt">http://www.rfc-editor.org/rfc/rfc7020.txt</a></span><br>
          <span></span><br>
          <span>This document provides information about the current
            Internet Numbers</span><br>
          <span>Registry System used in the distribution of globally
            unique Internet</span><br>
          <span>Protocol (IP) address space and autonomous system (AS)
            numbers.</span><br>
          <span></span><br>
          <span>This document also provides information about the
            processes for</span><br>
          <span>further evolution of the Internet Numbers Registry
            System.</span><br>
          <span></span><br>
          <span>This document replaces RFC 2050.</span><br>
          <span></span><br>
          <span>This document does not propose any changes to the
            current Internet</span><br>
          <span>Numbers Registry System.  Rather, it documents the
            Internet Numbers</span><br>
          <span>Registry System as it works today.</span><br>
          <span></span><br>
          <span></span><br>
          <span>INFORMATIONAL: This memo provides information for the
            Internet community.</span><br>
          <span>It does not specify an Internet standard of any kind.
            Distribution of</span><br>
          <span>this memo is unlimited.</span><br>
          <span></span><br>
          <span>This announcement is sent to the IETF-Announce and
            rfc-dist lists.</span><br>
          <span>To subscribe or unsubscribe, see</span><br>
          <span>  <a moz-do-not-send="true"
              href="http://www.ietf.org/mailman/listinfo/ietf-announce">http://www.ietf.org/mailman/listinfo/ietf-announce</a></span><br>
          <span>  <a moz-do-not-send="true"
              href="http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist">http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist</a></span><br>
          <span></span><br>
          <span>For searching the RFC series, see <a
              moz-do-not-send="true"
              href="http://www.rfc-editor.org/search/rfc_search.php">http://www.rfc-editor.org/search/rfc_search.php</a></span><br>
          <span>For downloading RFCs, see <a moz-do-not-send="true"
              href="http://www.rfc-editor.org/rfc.html">http://www.rfc-editor.org/rfc.html</a></span><br>
          <span></span><br>
          <span>Requests for special distribution should be addressed to
            either the</span><br>
          <span>author of the RFC in question, or to <a
              moz-do-not-send="true"
              href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>.
             Unless</span><br>
          <span>specifically noted otherwise on the RFC itself, all RFCs
            are for</span><br>
          <span>unlimited distribution.</span><br>
          <span></span><br>
          <span></span><br>
          <span>The RFC Editor Team</span><br>
          <span>Association Management Solutions, LLC</span><br>
          <span></span><br>
          <span></span><br>
        </div>
      </blockquote>
      <br>
    </div>
    <br>
  </body>
</html>