MUD-Based RATS Resources Discovery
draft-birkholz-rats-mud-00

Document Type Active Internet-Draft (individual)
Last updated 2020-03-09
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Additional URLs
- Yang catalog entry for ietf-mud-rats@2020-03-09.yang
- Yang impact analysis for draft-birkholz-rats-mud
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)
RATS Working Group                                           H. Birkholz
Internet-Draft                                            Fraunhofer SIT
Intended status: Standards Track                          March 10, 2020
Expires: September 11, 2020

                   MUD-Based RATS Resources Discovery
                       draft-birkholz-rats-mud-00

Abstract

   Manufacturer Usage Description (MUD) files and the MUD URI that point
   to them are defined in RFC 8520.  This document introduces a new type
   of MUD file to be delivered in conjunction with a MUD file signature
   and/or to be referenced via a MUD URI embedded in an IEEE 802.1AR
   Secure Device Identifier (DevID).  A DevID is a device specific pub-
   key identity document that can be presented to other entities, e.g. a
   network management system.  If this entity is also a verifier as
   defined by the IETF Remote ATtestation procedureS (RATS)
   architecture, this verifier can use the references found in the MUD
   file specified in this document in order to discover appropriate
   Reference Integrity Measurements (RIM), Endorsement Documents, or
   even globally suitable Remote Attestation Services (RAS).  All three
   types of theses resources are required to conduct RATS.  Hence, the
   MUD file defined in this document enables remote attestation
   procedures by supporting the discovery of these required resources or
   services.

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 September 11, 2020.

Birkholz               Expires September 11, 2020               [Page 1]
Internet-Draft                 Muddy Rats                     March 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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Notation . . . . . . . . . . . . . . . . . .   4
   2.  MUD URIs in DevIDs  . . . . . . . . . . . . . . . . . . . . .   4
   3.  MUD File Signatures . . . . . . . . . . . . . . . . . . . . .   4
   4.  Trusting MUD URIs and MUD Files . . . . . . . . . . . . . . .   4
     4.1.  Trusting RATS Resources referenced by a MUD File  . . . .   5
   5.  Specification of RATS MUD files referenced by MUD URIs  . . .   5
     5.1.  Tree Diagram  . . . . . . . . . . . . . . . . . . . . . .   5
     5.2.  YANG Module . . . . . . . . . . . . . . . . . . . . . . .   5
   6.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   8
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   Verifiers, Endorsers, and Attesters are roles defined in the RATS
   Architecture [I-D.ietf-rats-architecture].  In the RATS architecture,
   the Attester role relies on the Verifier and Endorser roles to enable
   the appraisal of Attestation Evidence produced by said Attesters; and
   to create corresponding Attestation Results.  Attestation Results
   compose a believable chunk of information that can be digested by
   Relying Parities in order to assess an Attester's trustworthiness.
   The assessment of a remote peer's trustworthiness is vital to steer
   any future protocol interaction between the Attester and the remote
   Relying Party.  To create these Attestation Results to be consumed by
   Relying Parties, the Attestation Evidence an Attester creates has to
   be processed by one or more appropriate Verifiers.

Birkholz               Expires September 11, 2020               [Page 2]
Show full document text