RADIUS Extensions for Manufacturer Usage Description
draft-weis-radext-mud-00

Document Type Active Internet-Draft (individual)
Last updated 2016-10-25
Stream (None)
Intended RFC status (None)
Formats plain text 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. Weis
Internet-Draft                                             Cisco Systems
Intended status: Standards Track                        October 25, 2016
Expires: April 28, 2017

          RADIUS Extensions for Manufacturer Usage Description
                        draft-weis-radext-mud-00

Abstract

   A Manufacturer Usage Description (MUD) is a file describing the
   expected use of a class of devices, usually an Internet of Things
   class of devices.  It is prepared by a manufacturer and placed on a
   generally available web server, and is addressable via a Uniform
   Resource Identifier (URI).  The URI is often included in a discovery
   protocol (e.g., DNS, LLDP).  A Network Access Server (NAS) in the
   path of the discovery protocol can collect and forward the URI to a
   RADIUS server, which processes the URI.  This draft defines the
   RADIUS extension needed for the NAS to forward the URI to the RADIUS
   server.

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 http://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 April 28, 2017.

Copyright Notice

   Copyright (c) 2016 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
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Weis                     Expires April 28, 2017                 [Page 1]
Internet-Draft                 RADIUS-MUD                   October 2016

   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 . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Acronyms and Abbreviations  . . . . . . . . . . . . . . . . .   4
   3.  Extended Attribute for the MUD URI  . . . . . . . . . . . . .   4
   4.  MUD URI processing  . . . . . . . . . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     8.2.  Informative Reference . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Enterprise networks often use Port-Based Network Access Control
   [IEEE802.1X], where the Authentication Server is a RADIUS server
   [RFC2865].  In some cases a device will authenticate itself to the
   network using IEEE 802.1X with a digital certificate (e.g., an IEEE
   802.1AR Secure Device ID [IEEE802.1AR]) that has been placed into the
   device by the manufacturer.  Manufacturer Usage Description (MUD)
   [I-D.ietf-opsawg-mud] has defined an optional extension for digital
   certificates, which consists of a Uniform Resource Identifier (URI)
   that identifies the MUD file.  A MUD file contains identification and
   network access information for a particular class of device.  This
   information can be used to generate authorization policy such as an
   Access Control List (ACL) describing required network access for the
   device.

   However, there are cases where a MUD URI is not included in a
   device's digital certificate, or it does not support the use of
   digital certificates, or may not even support an IEEE 802.1X
   Supplicant.  This will often be the case with IoT devices, which is a
   primary use case for the use of MUD.  In each of these situations, a
   device could benefit from distributing a MUD URI in a discovery
Show full document text