Publishing Information for Entities Identified by Domain Names
draft-hoffmann-dnsop-names-as-identifiers-00

Document Type Active Internet-Draft (individual)
Last updated 2020-01-22
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf 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)
DNS Operations                                               M. Hoffmann
Internet-Draft                                      Stichting NLnet Labs
Intended status: Standards Track                        January 22, 2020
Expires: July 25, 2020

     Publishing Information for Entities Identified by Domain Names
              draft-hoffmann-dnsop-names-as-identifiers-00

Abstract

   This memo describes a mechanism to publish information related to an
   entity identified through a domain name via the Domain Name System
   (DNS).  In particular, this mechanism allows publishing the location
   of topical documents describing the entity and relationships with
   other entities.  An example application is the publishing of
   additional requirements for PKI certification authorities.

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 July 25, 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

Hoffmann                  Expires July 25, 2020                 [Page 1]
Internet-Draft            names-as-identifiers              January 2020

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Notation . . . . . . . . . . . . . . . . . . . .   2
   3.  Identifiers and Topics  . . . . . . . . . . . . . . . . . . .   3
   4.  Discovery of Published Documents  . . . . . . . . . . . . . .   3
   5.  Expressing Relationships with Other Entities  . . . . . . . .   3
   6.  Publishing Associated Certificates  . . . . . . . . . . . . .   4
   7.  Example . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   10. Informative References  . . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Various networking applications operate on entities that need to be
   addressed globally.  Domain names have been designed to serve as such
   globally unique identifiers for the Internet.  They have a number of
   advantages.  They are human readable and reasonably easy to memorize,
   can be acquired relatively cheaply and with little administrative
   hassle.  Not least of all, they are accompanied by an entire system
   to publish and query information related to them: the Domain Name
   System (DNS).

   This document describes a simple framework that uses the DNS to
   discover various aspects of entities identified by domain names: It
   allows to publish the location of documents and express relationships
   with other entities.  Because an entity may serve different purposes,
   both documents and relationships can be expressed for different
   topics.

   This concept can for example be used for enriching PKI with
   additional information conveying policies certification authorities
   adhere to or properties they are guaranteed to have by so-called
   trust schemes vouching for them.  This use case is described below.

2.  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 in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

Hoffmann                  Expires July 25, 2020                 [Page 2]
Internet-Draft            names-as-identifiers              January 2020

3.  Identifiers and Topics

   In principle, any domain name can be used as an identifier for an
   entity.  However, for interoperability with existing infrastructure
Show full document text