One document matched: draft-ietf-homenet-redact-00.xml

<?xml version="1.0"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc compact="yes" ?>
<?rfc symrefs="no"?>

<rfc obsoletes="" updates="RFC7788" category="info" ipr="trust200902"
     docName="draft-ietf-homenet-redact-00">
  <front>
    <title abbrev="HNCP Redact">Redacting .home from HNCP</title>

    <author initials="T" surname="Lemon" fullname="Ted Lemon">
      <organization>Nominum, Inc.</organization>
      <address>
	<postal>
	  <street>800 Bridge Parkway</street>
	  <city>Redwood City</city>
	  <region>California</region>
	  <country>United States of America</country>
	  <code>94065</code>
	</postal>
	<phone>+1 650 381 6000</phone>
	<email>ted.lemon@nominum.com</email>
      </address>
    </author>

    <date year="2016" month="August" day="26"></date>
    <area>Internet</area>
    <workgroup>Home Networking</workgroup>
    <abstract>
      <t>This document updates the Home Networking Control Protocol, eliminating the recommendation for a default top-level
	name for local name resolution.</t>
    </abstract>
  </front>
  <middle>

    <section title="Introduction">
      <t>The Homenet working group has defined a mechanism for sharing information between homenet routers, in Home Networking
	Control Protocol <xref target="RFC7788"/>.   This document recomments the use of the ".home" top-level name as a
	locally-resolved domain name.</t>

      <t>RFC7788 did not follow the process defined in Special Use Domain Names <xref target="RFC6761"/>.   It is likely that,
	had this process been followed, it would not have been possible to gain consensus on the use of '.home' as the
	locally-resolved special-use top-level name for homenets, because this name is known to be informally in use by
	sites on the internet, and the use to which this name has been put is not well documented; it is impossible to
	say that there are no conflicting uses for the name, and so getting consensus to use it anyway would have been
	controversial, time consuming, and possibly futile.</t>

      <t>The RFC6761 process is not well-understood within the IETF, and the authors of RFC7788 were not aware
	of it.   Normally, authors are not expected to know all there is to know about IETF process, and IETF leadership,
	specifically working group chairs, area directors and directorate members are expected to engage in a review process
	that notices oversights of this sort.</t>

      <t>Unfortunately, in the case of RFC7788, none of the people who should have caught the missing RFC6761 reference
	did catch it, and RFC 7788 was published as a consensus document that uses '.home' without ever reserving it
	in the RFC6761 Special-Use Domain Names registry.</t>

      <t>This document updates RFC 7788 to remove the specification to use '.home' for site-local name resolution within
	the homenet.</t>
    </section>

    <section title="Updates to Home Networking Control Protocol">
      <t>The final paragraph of RFC 7788, section 8, is updated as follows:</t>
      <t>OLD:<list style="empty">
	  <t>Names and unqualified zones are used in an HNCP network to provide naming and service discovery with local
	    significance.  A network-wide zone is appended to all single labels or unqualified zones in order to qualify
	    them. ".home" is the default; however, an administrator MAY configure the announcement of a Domain-Name TLV (Section
	    10.6) for the network to use a different one.  In case multiple are announced, the domain of the node with the greatest
	    node identifier takes precedence.</t>
	</list>
	NEW: (deleted)</t>
    </section>
  </middle>
  
  <back>
    <references title="Normative References">
      <?rfc include="reference.RFC.6761" ?>
      <?rfc include="reference.RFC.7788" ?>
    </references>
  </back>
</rfc>

<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
fill-column:132
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
-->