Reporting MUD behavior to vendors
draft-lear-opsawg-mud-reporter-00

Document Type Active Internet-Draft (individual)
Last updated 2019-07-05
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Yang Validation 0 errors, 0 warnings.
Additional URLs
- Yang catalog entry for ietf-mud-reporter-collector@2019-06-21.yang
- Yang catalog entry for ietf-mud-reporter-extension@2019-06-21.yang
- Yang catalog entry for ietf-mud-reporter@2019-06-21.yang
- Yang impact analysis for draft-lear-opsawg-mud-reporter
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                                            E. Lear
Internet-Draft                                             Cisco Systems
Intended status: Standards Track                          M. Ranganathan
Expires: January 6, 2020                                            NIST
                                                           July 05, 2019

                   Reporting MUD behavior to vendors
                   draft-lear-opsawg-mud-reporter-00

Abstract

   As with other technology, manufacturers would like to understand how
   networks implementing MUD are treating devices that are providing MUD
   URLs and MUD files.  This memo specifies an extension to MUD that
   permits certain behaviors to be reported.

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 January 6, 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 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.

Lear & Ranganathan       Expires January 6, 2020                [Page 1]
Internet-Draft                MUD Reporter                     July 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  The mud-reporter-extension model extension  . . . . . . . . .   3
     2.1.  The mud-reporter-extension augmentation to the MUD YANG
           model . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  The Reporter record format  . . . . . . . . . . . . . . .   6
   3.  RESTful interface at the collector  . . . . . . . . . . . . .  11
   4.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .  12
   5.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  12
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  13
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  13
   Appendix A.  Changes from Earlier Versions  . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   Manufacturer Usage Descriptions (MUD) [RFC8520] provides a means for
   devices to identify what they are and what sort of network access
   they need.  When a device with a MUD URL and a MUD file is fielded in
   volume, manufacturers may be curious as to whether it is getting the
   access it needs.  There a few several reasons why a device would not
   be getting the access it needs.  Some examples include:

   o  The MUD file permits access only to a controller but there is
      none.

   o  The MUD file permits access only to same-manufacturer or model but
      there is none.

   o  The MUD file permits access to a particular Internet service, but
      the name of that service has not been resolved (or name resolution
      failed).

   o  The administrator overrode the recommendations in the MUD file.

   This memo sets out to provide manufacturers indications regarding
   what has happened, in a similar vein to how DMARC is usd to report
   message drops to messag senders [RFC7489].

   In order to provide meaningful reporting, it is necessary to indicate
   whether or not the above abstractions are in use at a given time, and
   any public IP addresses that have been mapped to domain names by the
   local deployment.  A communication method that may establish the
   source of the reporter is also necessary, as well as the MUD URL in
   use at the time of the report.

Lear & Ranganathan       Expires January 6, 2020                [Page 2]
Internet-Draft                MUD Reporter                     July 2019

   This memo specifies a YANG model for reporting and a means for
   transmitting the report, and appropriate extensions to the MUD file
Show full document text