Publishing Organization Boundaries in the DNS
draft-levine-orgboundary-03

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-11-09
Replaced by draft-levine-dbound-dns
Stream (None)
Intended RFC status (None)
Formats 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)
Network Working Group                                          J. Levine
Internet-Draft                                      Taughannock Networks
Intended status: Informational                          November 9, 2015
Expires: May 12, 2016

             Publishing Organization Boundaries in the DNS
                      draft-levine-orgboundary-03

Abstract

   Often, the organization that manages a subtree in the DNS is
   different from the one that manages the tree above it.  Rather than
   describing a particular design, we describe an architecture to
   publish in the DNS the boundaries between organizations that can be
   adapted to various policy models.

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 http://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 May 12, 2016.

Copyright Notice

   Copyright (c) 2015 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
   (http://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 May 12, 2016                  [Page 1]
Internet-Draft               Org Boundaries                November 2015

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Design Issues . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  RRTYPE format . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Lookup Process  . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  DNS Records . . . . . . . . . . . . . . . . . . . . . . . . .   5
   6.  Application scenearios  . . . . . . . . . . . . . . . . . . .   6
     6.1.  Cookies . . . . . . . . . . . . . . . . . . . . . . . . .   6
     6.2.  SSL Certificates  . . . . . . . . . . . . . . . . . . . .   6
     6.3.  DMARC . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   7.  Discussion  . . . . . . . . . . . . . . . . . . . . . . . . .   6
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   9.  Variations  . . . . . . . . . . . . . . . . . . . . . . . . .   7
   10. IANA considerations . . . . . . . . . . . . . . . . . . . . .   7
   11. Normative References  . . . . . . . . . . . . . . . . . . . .   8
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .   8
     A.1.  Changes from -02 to -03 . . . . . . . . . . . . . . . . .   8
     A.2.  Changes from -01 to -02 . . . . . . . . . . . . . . . . .   9
     A.3.  Changes from -00 to -01 . . . . . . . . . . . . . . . . .   9
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   9

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 web 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.  Some mail security applications
   such as Domain-based Messaging Authetnication, Reporting and
   Conformance (DMARC) use them to locate an organization's policy
   records in the DNS.

   [[Plese direct discusson 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.

Levine                    Expires May 12, 2016                  [Page 2]
Internet-Draft               Org Boundaries                November 2015
Show full document text