RAINS (Another Internet Naming Service) Protocol Specification
draft-trammell-rains-protocol-03

Document Type Active Internet-Draft (individual)
Last updated 2017-09-20
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html 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                                        B. Trammell
Internet-Draft                                                ETH Zurich
Intended status: Experimental                         September 20, 2017
Expires: March 24, 2018

     RAINS (Another Internet Naming Service) Protocol Specification
                    draft-trammell-rains-protocol-03

Abstract

   This document defines an alternate protocol for Internet name
   resolution, designed as a prototype to facilitate conversation about
   the evolution or replacement of the Domain Name System protocol.  It
   attempts to answer the question: "how would we design DNS knowing
   what we do now," on the background of the properties of an ideal
   naming service described in [I-D.trammell-inip-pins].

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 March 24, 2018.

Copyright Notice

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

Trammell                 Expires March 24, 2018                 [Page 1]
Internet-Draft                    RAINS                   September 2017

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Architecture  . . . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Information Model . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Assertion . . . . . . . . . . . . . . . . . . . . . . . .   6
       4.1.1.  Context in Assertions . . . . . . . . . . . . . . . .   8
       4.1.2.  Signatures in Assertions  . . . . . . . . . . . . . .   9
       4.1.3.  Shards and Zones  . . . . . . . . . . . . . . . . . .  10
       4.1.4.  Zone-Reflexive Assertions . . . . . . . . . . . . . .  11
     4.2.  Query . . . . . . . . . . . . . . . . . . . . . . . . . .  12
       4.2.1.  Context in Queries  . . . . . . . . . . . . . . . . .  12
       4.2.2.  Answers to Queries  . . . . . . . . . . . . . . . . .  13
     4.3.  Address to Object Mapping . . . . . . . . . . . . . . . .  13
       4.3.1.  Context in Address Assertions . . . . . . . . . . . .  14
   5.  CBOR Data Model . . . . . . . . . . . . . . . . . . . . . . .  15
     5.1.  Symbol Table  . . . . . . . . . . . . . . . . . . . . . .  16
     5.2.  Message . . . . . . . . . . . . . . . . . . . . . . . . .  17
     5.3.  Message Section header  . . . . . . . . . . . . . . . . .  17
     5.4.  Assertion body  . . . . . . . . . . . . . . . . . . . . .  18
     5.5.  Shard body  . . . . . . . . . . . . . . . . . . . . . . .  19
     5.6.  Zone body . . . . . . . . . . . . . . . . . . . . . . . .  20
     5.7.  Query body  . . . . . . . . . . . . . . . . . . . . . . .  20
     5.8.  Address Assertion body  . . . . . . . . . . . . . . . . .  22
     5.9.  Address Query body  . . . . . . . . . . . . . . . . . . .  23
     5.10. Notification body . . . . . . . . . . . . . . . . . . . .  23
     5.11. Object  . . . . . . . . . . . . . . . . . . . . . . . . .  24
       5.11.1.  Certificate information format . . . . . . . . . . .  27
       5.11.2.  Name expression format . . . . . . . . . . . . . . .  29
     5.12. Tokens in queries and messages  . . . . . . . . . . . . .  30
     5.13. Signatures, delegation keys, and RAINS infrastructure
           keys  . . . . . . . . . . . . . . . . . . . . . . . . . .  31
       5.13.1.  EdDSA signature and public key format  . . . . . . .  32
       5.13.2.  ECDSA signature and public key format  . . . . . . .  33
     5.14. Capabilities  . . . . . . . . . . . . . . . . . . . . . .  33
   6.  Canonical signing format  . . . . . . . . . . . . . . . . . .  35
   7.  RAINS Protocol Definition . . . . . . . . . . . . . . . . . .  35
     7.1.  Message processing  . . . . . . . . . . . . . . . . . . .  35
Show full document text