Skip to main content

Special Use Domain Name ''

Approval announcement
Draft of message to be sent after approval:


From: The IESG <>
To: IETF-Announce <>
Cc:,,, The IESG <>
Subject: Protocol Action: 'Special Use Domain Name ''' to Proposed Standard (draft-cheshire-sudn-ipv4only-dot-arpa-17.txt)

The IESG has approved the following document:
- 'Special Use Domain Name '''
  (draft-cheshire-sudn-ipv4only-dot-arpa-17.txt) as Proposed Standard

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

The IESG contact person is Warren Kumari.

A URL of this Internet Draft is:

Ballot Text

Technical Summary

   The specification for how a client discovers its local network's
   NAT64 prefix [RFC7050] defines the special name '' for
   this purpose, but in its Domain Name Reservation Considerations
   section that specification indicates that the name actually has no
   particularly special properties would require special handling, and
   does not request IANA to record the name in the Special-Use Domain
   Names registry.

   Consequently, despite the well articulated special purpose of the
   name, '' was not recorded in the Special-Use Domain
   Names registry as a name with special properties.

   This document describes the special treatment required, formally
   declares the special properties of the name, and adds similar
   declarations for the corresponding reverse mapping names.

Working Group Summary

This document is AD sponsored - it was considered for adoption in the DNSOP WG. While there was no major controversy or objections, the WG didn't declined to adopt it. Warren Kumari (as Ops AD) agreed to AD sponsor it, informed the DNSOP WG / BEHAVE lists, and asked for feedback.

The authors received, and addressed / incorporated IETF LC comments. 

Document Quality
    The document is clear and understandable - it corrects an oversight / omission, and provides guidance to implementers. It also corrects / records the status in an IANA registry. 


   Warren Kumari is the responsible AD, and shepherd. 

RFC Editor Note