Operational Considerations for BRSKI Registrar
draft-richardson-anima-registrar-considerations-02

Document Type Active Internet-Draft (individual)
Last updated 2019-12-05
Stream (None)
Intended RFC status (None)
Formats plain text html 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)
anima Working Group                                        M. Richardson
Internet-Draft                                  Sandelman Software Works
Intended status: Standards Track                         5 December 2019
Expires: 7 June 2020

             Operational Considerations for BRSKI Registrar
           draft-richardson-anima-registrar-considerations-02

Abstract

   This document describes a number of operational modes that a BRSKI
   Registration Authority (Registrar) may take on.

   Each mode is defined, and then each mode is given a relevance within
   an over applicability of what kind of organization the Registrar is
   deployed into.  This document does not change any protocol
   mechanisms.

   This document includes operational advice about avoiding unwanted
   consequences.

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 7 June 2020.

Copyright Notice

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

Richardson                 Expires 7 June 2020                  [Page 1]
Internet-Draft          Registrar Considerations           December 2019

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Reference Network and Diagrams  . . . . . . . . . . . . .   4
       1.2.1.  Tier-1 Network  . . . . . . . . . . . . . . . . . . .   4
       1.2.2.  Enterprise Network  . . . . . . . . . . . . . . . . .   4
       1.2.3.  Home Network  . . . . . . . . . . . . . . . . . . . .   5
     1.3.  Internal architectural view . . . . . . . . . . . . . . .   5
       1.3.1.  Pledge Interface (Southbound Interface) . . . . . . .   5
       1.3.2.  MASA client (Northbound Interface)  . . . . . . . . .   6
       1.3.3.  Join Proxy (Southbound Interface) . . . . . . . . . .   7
       1.3.4.  EST and BRSKI GRASP announcements . . . . . . . . . .   7
       1.3.5.  Certificate Authority . . . . . . . . . . . . . . . .   7
       1.3.6.  Management Interface  . . . . . . . . . . . . . . . .   8
   2.  Connecting the Autonomic Control Plane to the Network
           Operations Center (NOC) . . . . . . . . . . . . . . . . .   8
   3.  Public Key Infrastructure Recommendations for the
           Registrar . . . . . . . . . . . . . . . . . . . . . . . .   8
     3.1.  PKI recommendations for Tier-1/ISP Networks . . . . . . .   9
     3.2.  Enterprise Network  . . . . . . . . . . . . . . . . . . .  10
     3.3.  Home Network  . . . . . . . . . . . . . . . . . . . . . .  11
   4.  Architecture Considerations for the Registrar . . . . . . . .  12
     4.1.  Completely Synchronous Registrar  . . . . . . . . . . . .  12
     4.2.  Partially Synchronous Registrar . . . . . . . . . . . . .  13
     4.3.  Asynchronous Registrar  . . . . . . . . . . . . . . . . .  13
   5.  Certificates needed for the Registrar . . . . . . . . . . . .  13
     5.1.  TLS Server Certificate for BRSKI-EST  . . . . . . . . . .  14
     5.2.  TLS Client Certificate for BRSKI-MASA . . . . . . . . . .  14
       5.2.1.  Use of Publically Anchored TLS Client Certificate with
               BRSKI-MASA connection . . . . . . . . . . . . . . . .  14
     5.3.  Certificate for signing of Voucher-Requests . . . . . . .  15
   6.  Autonomic Control Plane Addressing  . . . . . . . . . . . . .  15
   7.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  16
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
     8.1.  Denial of Service Attacks against the Registrar . . . . .  16
     8.2.  Loss of Keys/Corruption of Infrastructure . . . . . . . .  17
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  17
Show full document text