The IESG has approved the following document:
- 'The "_for-sale" Underscored and Globally Scoped DNS Node Name'
  (draft-davids-forsalereg-21.txt) as Informational RFC

This document has been reviewed in the IETF but is not the product of an IETF
Working Group.

The IESG contact person is Mohamed Boucadair.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-davids-forsalereg/




Technical Summary

   This document defines an operational convention that uses the
   reserved underscored DNS leaf node name "_for-sale" to indicate that
   the parent domain name is available for purchase. The convention can
   be deployed without disrupting existing operations, and it may be
   applied even when the domain name is still actively in use.

Document Quality

  The convention has been implemented in the .NL registry by SIDN and
  as a result there are +2 years of experience in using it.

  There is running code available at:

    <https://forsalereg.sidnlabs.nl/demo>

  with source code available at:

    <https://github.com/mdavids/rfc/blob/main/tools/webserver.go>

  A DNS zone has been published for the purposes of checking
  implementations of this protocol: testdns.nl

  Another implementation of a tool to perform syntax checking is
  available at <https://forsale.bitfire.nl>. Notably this tool was
  constructed using an LLM trained on the specification that is the
  subject of this review. This provides additional confidence that
  the specification is sufficiently complete and unambiguous for
  it to be used to produce a conformant implementation.

  An implementation of a lightweight Model Context Protocol (MCP)
  server that allows clients to check whether a domain name advertises
  itself for sale can be found here:

    <https://github.com/CultriX-Github/mcp-forsale>

Personnel

   The Document Shepherd for this document is Joe Abley.
   The Responsible Area Director is Mohamed Boucadair.


RFC Editor Note

  Please make this change:

  OLD: Some URI schemes RECOMMENDED in Section 2.2.3 do not mandate

  NEW: Some URI schemes recommended in Section 2.2.3 do not mandate

_______________________________________________
IETF-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to