A Bootstrapping Procedure to Discover and Authenticate DNS-over-TLS and DNS-over-HTTPS Servers for IoT and BYOD Devices
draft-reddy-add-iot-byod-bootstrap-01
ADD WG T. Reddy
Internet-Draft McAfee
Intended status: Standards Track D. Wing
Expires: January 27, 2021 Citrix
M. Richardson
Sandelman Software Works
M. Boucadair
Orange
July 26, 2020
A Bootstrapping Procedure to Discover and Authenticate DNS-over-TLS and
DNS-over-HTTPS Servers for IoT and BYOD Devices
draft-reddy-add-iot-byod-bootstrap-01
Abstract
This document specifies mechanisms to bootstrap endpoints (e.g.,
hosts, IoT devices) to discover and authenticate DNS-over-TLS and
DNS-over-HTTPS servers provided by a local network for IoT/BYOD
devices in Enterprise networks.
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 27, 2021.
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
Reddy, et al. Expires January 27, 2021 [Page 1]
Internet-DraDoT/DoH server discovery for for BYOD/IoT devices July 2020
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Bootstrapping Endpoint Devices . . . . . . . . . . . . . . . 6
4.1. Bootstrapping BYOD . . . . . . . . . . . . . . . . . . . 6
5. Bootstrapping IoT Devices . . . . . . . . . . . . . . . . . . 8
6. Connection Handshake and Service Invocation . . . . . . . . . 9
7. EST Service Discovery Procedure . . . . . . . . . . . . . . . 10
8. Network Reattachment . . . . . . . . . . . . . . . . . . . . 10
9. Privacy Considerations . . . . . . . . . . . . . . . . . . . 12
10. Security Considerations . . . . . . . . . . . . . . . . . . . 12
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
11.1. Service Name for EST . . . . . . . . . . . . . . . . . . 13
11.2. Service Name for DoH . . . . . . . . . . . . . . . . . . 13
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
13.1. Normative References . . . . . . . . . . . . . . . . . . 13
13.2. Informative References . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
1. Introduction
Traditionally a caching DNS server has been provided by local
networks. This provides benefits such as low latency to reach that
DNS server (owing to its network proximity to the endpoint).
However, if an endpoint is configured to use Internet-hosted or
public DNS-over-TLS (DoT) [RFC7858] or DNS-over-HTTPS (DoH) [RFC8484]
servers, any available local DNS server cannot serve DNS requests
from local endpoints. If public DNS servers are used instead of
using local DNS servers, some operational problems can occur such as
those listed below:
o "Split DNS" [RFC2775] to use the special internal-only domain
names (e.g., "internal.example.com") in enterprise networks will
not work, and ".local" and "home.arpa" names cannot be locally
resolved in home networks.
o Content Delivery Networks (CDNs) that map traffic based on DNS may
lose the ability to direct end-user traffic to a nearby service-
Show full document text