DNS Resolver-Based Policy Detection Domain
draft-grover-add-policy-detection-00

Document Type Active Internet-Draft (individual)
Last updated 2019-07-08
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          A. Grover
Internet-Draft                                            P. Saint-Andre
Intended status: Standards Track                                 Mozilla
Expires: January 9, 2020                                    July 8, 2019

               DNS Resolver-Based Policy Detection Domain
                  draft-grover-add-policy-detection-00

Abstract

   This document specifies the behavior that is expected from the Domain
   Name System with regard to DNS queries for the special-use domain
   name 'TBD.arpa' and designates this domain as a special-use domain
   name.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 9, 2020.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Grover & Saint-Andre     Expires January 9, 2020                [Page 1]
Internet-Draft           Policy Detection Domain               July 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Design Goals and Constraints  . . . . . . . . . . . . . . . .   3
   4.  Behavior  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Domain Name Reservation Considerations  . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Content-control software can be used to filter (i.e., block) web
   requests that the user, the user's guardian, or the network operator
   deems objectionable or outside the usage policy of the network.
   Blocked resource categories can include advertisements, explicit
   content, known malware, and government-unapproved material, along
   with many others.

   One way to implement content control that does not rely on software
   or settings on the end-user's computing device is DNS-based content
   filtering, which examines a client's initial DNS request for the
   domain providing a resource and then either returns no result or
   returns an alternate result so that the user is presented with an
   explanation that filtering has taken place.

   DNS-based policy such as content filtering is often built into a
   network's configured DNS recursive resolver.  In addition to blocking
   a request, the resolver may also log the request for use by the
   network administrators.

   A network operator might wish to provide, or might be obligated to
   provide, a filtering policy to users of its network.  Because such a
   policy is often enforced by the network operator's default resolver,
   the use of a technology such as DNS over HTTPS (DoH) [RFC8484] or DNS
   over TLS (DoT) [RFC7858] can result in bypassing local policies.  If
   the user agent can check for the presence of a policy, this could be
   used as a signal that the network operator wishes its resolver to be
   used as a condition of using the network, and that DoH or DoT should
   be disabled.

   At present, there is no standardized mechanism for the user or user
   agent to identify the presence of a policy on a network's default

Grover & Saint-Andre     Expires January 9, 2020                [Page 2]
Internet-Draft           Policy Detection Domain               July 2019
Show full document text