[rfc-dist] RFC 8520 on Manufacturer Usage Description Specification

rfc-editor@rfc-editor.org Wed, 13 March 2019 02:57 UTC

Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 555E813117E for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 12 Mar 2019 19:57:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R2PEUUPhDJJI for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 12 Mar 2019 19:57:20 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF82613119D for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 12 Mar 2019 19:57:20 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 54660B82423; Tue, 12 Mar 2019 19:57:17 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id D7166B82424; Tue, 12 Mar 2019 19:57:15 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20190313025715.D7166B82424@rfc-editor.org>
Date: Tue, 12 Mar 2019 19:57:15 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8520_on_Manufacturer_Usage_Description_?= =?utf-8?q?Specification?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, opsawg@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8520

        Title:      Manufacturer Usage Description Specification 
        Author:     E. Lear,
                    R. Droms,
                    D. Romascanu
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2019
        Mailbox:    lear@cisco.com, 
                    rdroms@gmail.com, 
                    dromasca@gmail.com
        Pages:      60
        Characters: 120849
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-opsawg-mud-25.txt

        URL:        https://www.rfc-editor.org/info/rfc8520

        DOI:        10.17487/RFC8520

This memo specifies a component-based architecture for Manufacturer
Usage Descriptions (MUDs).  The goal of MUD is to provide a means for
end devices to signal to the network what sort of access and network
functionality they require to properly function.  The initial focus
is on access control.  Later work can delve into other aspects.

This memo specifies two YANG modules, IPv4 and IPv6 DHCP options, a
Link Layer Discovery Protocol (LLDP) TLV, a URL, an X.509 certificate
extension, and a means to sign and verify the descriptions.

This document is a product of the Operations and Management Area Working Group Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org