Signaling resolver's filtering policies
draft-mglt-add-signaling-filtering-policies-00

Document Type Active Internet-Draft (individual)
Last updated 2020-03-09
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized 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)
add                                                           D. Migault
Internet-Draft                                                  Ericsson
Intended status: Standards Track                          March 09, 2020
Expires: September 10, 2020

                Signaling resolver's filtering policies
             draft-mglt-add-signaling-filtering-policies-00

Abstract

   This document defines one mechanism that enables a DNS resolver to
   inform a DNS client that filtering policies are in place and what
   their concern is.  The second mechanism describes how a DNS client
   can request a resolver whether filtering policies are in place and
   what their concern is.

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 September 10, 2020.

Copyright Notice

   Copyright (c) 2020 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.

Migault                Expires September 10, 2020               [Page 1]
Internet-Draft     filtering policies by the resolver         March 2020

Table of Contents

   1.  Requirements Notation . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Filtering semantics . . . . . . . . . . . . . . . . . . . . .   3
   4.  DNS resolver advertising filtering status . . . . . . . . . .   4
   5.  Requesting DNS resolver filtering status  . . . . . . . . . .   5
   6.  Blocking traffic under the policy . . . . . . . . . . . . . .   6
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   8.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   6
   9.  IANA considerations . . . . . . . . . . . . . . . . . . . . .   6
   10. Acknowledgment  . . . . . . . . . . . . . . . . . . . . . . .   7
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     11.1.  Normative References . . . . . . . . . . . . . . . . . .   7
     11.2.  Informative References . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Requirements Notation

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described BCP 14
   [RFC2119] [RFC8174] when, and only when, they appear in all capitals,
   as shown here.

2.  Introduction

   This document defines mechanisms that enable a DNSSEC resolver to
   signal that filtering policies are enabled by the DNSSEC resolver.
   There are two distinct mechanisms.  The first mechanism enables a
   resolver to advertise policies that are enabled/disabled without any
   explicit request from the DNS client.  The second mechanism enables a
   DNS client to request the status of the resolver.  Such consideration
   may be used, by a stub resolver for example to select an appropriated
   resolver.

   The ability for a resolver to provide such information to a DNS
   client will help a DNS client to appropriately chose its resolver.

   The ability to request or signal configuration information has
   already been done in the past for the TA.  [RFC8145] enables a
   resolver to advertise an authoritative server via an EDNS option in
   the OPT RR which TA is used for the DNSSEC validation.  The RR is
   inserted when DNSKEY RRsets are requested.  In addition, the resolver
   may also request the appropriated TA with a specific DNS query.  The
   RRsets are stored in the authoritative zone.

Migault                Expires September 10, 2020               [Page 2]
Internet-Draft     filtering policies by the resolver         March 2020

   [RFC8509] describes a sentinel mechanism where the resolver has a
   specific behavior based on the left side label.  This mechanism
Show full document text