Publishing Organization Boundaries in the DNS
draft-levine-dbound-dns-04
Network Working Group J. Levine
Internet-Draft Taughannock Networks
Intended status: Informational 10 April 2020
Expires: 12 October 2020
Publishing Organization Boundaries in the DNS
draft-levine-dbound-dns-04
Abstract
The organization that manages a subtree in the DNS is often different
from the one that manages the tree above it. We describe an
architecture to publish in the DNS the boundaries between
organizations that can be adapted to various policy models and can be
queried with a small number of DNS lookups.
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 12 October 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.
Levine Expires 12 October 2020 [Page 1]
Internet-Draft Org Boundaries April 2020
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Design Issues . . . . . . . . . . . . . . . . . . . . . . . . 2
3. TXT record format . . . . . . . . . . . . . . . . . . . . . . 3
4. Lookup Process . . . . . . . . . . . . . . . . . . . . . . . 4
5. DNS Records . . . . . . . . . . . . . . . . . . . . . . . . . 6
6. Application scenarios . . . . . . . . . . . . . . . . . . . . 7
6.1. DMARC . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.2. Cookies . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.3. SSL Certificates . . . . . . . . . . . . . . . . . . . . 8
7. Discussion . . . . . . . . . . . . . . . . . . . . . . . . . 8
8. ABNF syntax of bound records . . . . . . . . . . . . . . . . 8
9. Security Considerations . . . . . . . . . . . . . . . . . . . 9
10. Variations . . . . . . . . . . . . . . . . . . . . . . . . . 9
11. IANA considerations . . . . . . . . . . . . . . . . . . . . . 10
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
12.1. Normative References . . . . . . . . . . . . . . . . . . 11
12.2. Informative References . . . . . . . . . . . . . . . . . 11
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 11
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
Often, the organization that manages a subtree in the DNS is
different from the one that manages the tree above it. Many
applications use information about such boundaries to implement
security policies. For example, web browsers use them to limit the
names where HTTP cookies can be set, and Secure Socket Layer (SSL)
certificate services use them to determine the party responsible for
the domain in a signing request. Mail security applications such as
Domain-based Messaging Authentication, Reporting and Conformance
(DMARC) use them to locate an organization's policy records in the
DNS. This specification is intended to provide boundaries usable for
DMARC, and possibly for other applications.
[[Please direct discussion of this draft to the dbound working group
at dbound@ietf.org.]]
2. Design Issues
Organization boundaries can be assigned on what one could call an
opt-in or opt-out basis. "Opt-in" means that two names are only
managed by the same organization if both actively assert that they
are related. "Opt-out" means that if there is any boundary
information at all for a DNS subtree, each name is assumed to be
under the same management as its parent unless there is a boundary
assertion to the contrary. This design describes an opt-out model.
Show full document text