<html>
  <head>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p class="MsoNormal" style="margin: 6pt 0in; line-height: 18pt;
      background: none repeat scroll 0% 0% white;"><span
        style="font-family:Helvetica;mso-fareast-font-family:
        "Times New Roman";mso-bidi-font-family:"Times New
        Roman"">ARIN has received and issued its response to ACSP
        Suggestion 2014.14. The suggestion and response text are
        provided below. This suggestion is now closed and is available
        at: </span><span style="font-family: Times;"></span><span
        style="font-family:Times;mso-fareast-font-family:"Times New
        Roman";mso-bidi-font-family: "Times New Roman""></span><span
        style="font-family: Helvetica;"><br>
      </span></p>
    <p class="MsoNormal"
      style="margin-top:6.0pt;margin-right:0in;margin-bottom:6.0pt;
      margin-left:0in;line-height:18.0pt;background:white"><span
        style="font-family:Helvetica;mso-fareast-font-family:"Times
        New Roman"; mso-bidi-font-family:"Times New
        Roman""><a class="moz-txt-link-freetext" href="https://www.arin.net/participate/acsp/suggestions/2014-14.html">https://www.arin.net/participate/acsp/suggestions/2014-14.html</a></span><span
        style="font-family:Times;mso-fareast-font-family:"Times New
        Roman";mso-bidi-font-family: "Times New Roman""><br>
        <br>
      </span><span
        style="font-family:Helvetica;mso-fareast-font-family:"Times
        New Roman"; mso-bidi-font-family:"Times New
        Roman"">Regards,</span><span style="font-family:
        Times;mso-fareast-font-family:"Times New
        Roman";mso-bidi-font-family:"Times New Roman""><br>
        <br>
      </span><span
        style="font-family:Helvetica;mso-fareast-font-family:"Times
        New Roman"; mso-bidi-font-family:"Times New
        Roman"">Communications and Member Services</span><span
        style="font-family:Times;mso-fareast-font-family:"Times New
        Roman";mso-bidi-font-family: "Times New Roman""><br>
      </span><span
        style="font-family:Helvetica;mso-fareast-font-family:"Times
        New Roman"; mso-bidi-font-family:"Times New
        Roman"">American Registry for Internet Numbers (ARIN)</span><span
        style="font-family:Times;mso-fareast-font-family:"Times New
        Roman"; mso-bidi-font-family:"Times New Roman""><br>
        <br>
      </span><span
        style="font-family:Helvetica;mso-fareast-font-family:"Times
        New Roman"; mso-bidi-font-family:"Times New
        Roman"">***</span><span style="font-family:
        Times;mso-fareast-font-family:"Times New
        Roman";mso-bidi-font-family:"Times New Roman""><o:p></o:p></span><b><span
          style="font-family: Helvetica;mso-bidi-font-family:"Times
          New Roman";color:black"><br>
          Suggestion: </span></b><span
        style="font-family:Arial;mso-bidi-font-family:"Times New
        Roman";color:black"><o:p></o:p></span></p>
    IpV6 hexadecimal number groupings have no formal or informal name,
    unlike the "octet" of IpV4. I would like to suggest the term
    "twoctet". Obviously a mash-up of the words two and octet.
    Accurately describes the number. It is familiar enough to be
    recognizable as a networking term. Different enough to be associated
    in time with IpV6 only. A Google search reveals a surprising lack of
    hits for the term.<span style="font-family:
      Helvetica;mso-bidi-font-family:"Times New
      Roman";color:black"></span><span
      style="font-family:Arial;mso-bidi-font-family:"Times New
      Roman";color:black"><o:p></o:p></span>
    <p class="MsoNormal"
      style="margin-top:6.0pt;margin-right:0in;margin-bottom:6.0pt;
      margin-left:0in;line-height:18.0pt;background:white"><b><span
          style="font-family: Helvetica;mso-bidi-font-family:"Times
          New Roman";color:black">Response:</span></b><span
        style="font-family:Arial;mso-bidi-font-family:"Times New
        Roman";color:black"><o:p></o:p></span></p>
    Thank you for your suggestion, numbered 2014.14 upon confirmed
    receipt, about the naming of IPv6 address space parts. I think many
    people have shared your observation over the years, and I am glad
    you brought it up.<br>
    ARIN and the other Regional Internet Registries fulfill the role of
    managing the distribution of IP addresses, but do not make decisions
    about the protocol specifications and naming. As I am sure you are
    already aware, the protocols themselves are developed by the
    Internet Engineering Task Force (IETF).<br>
    The topic you have brought up in this suggestion has already seen
    active discussion at the IETF over the years. In fact, there is an
    Internet Draft on this specific topic. Contact information for the
    authors can be found inside the draft if you are interested in
    reaching out to them.<br>
    <br>
    <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-denog-v6ops-addresspartnaming-04">http://tools.ietf.org/html/draft-denog-v6ops-addresspartnaming-04</a><br>
    <br>
    Thank you for using the ARIN Suggestion and Consultation Process.<br>
    <br>
    This suggestion is now closed.<span style="font-family:Helvetica;
      mso-bidi-font-family:"Times New Roman";color:black"></span>
  </body>
</html>