[OPSAWG] RFC 8886 on Secure Device Install

rfc-editor@rfc-editor.org Wed, 23 September 2020 23:17 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6D023A15CC; Wed, 23 Sep 2020 16:17:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 9KY4EXGKGRx7; Wed, 23 Sep 2020 16:17:40 -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 474123A15C5; Wed, 23 Sep 2020 16:17:40 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 39DE9F4076E; Wed, 23 Sep 2020 16:17:31 -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
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, opsawg@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200923231731.39DE9F4076E@rfc-editor.org>
Date: Wed, 23 Sep 2020 16:17:31 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/zcpDZTpxAuez3d2gKxjSNQ0XGXI>
Subject: [OPSAWG] =?utf-8?q?RFC_8886_on_Secure_Device_Install?=
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Sep 2020 23:17:42 -0000

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

        
        RFC 8886

        Title:      Secure Device Install 
        Author:     W. Kumari,
                    C. Doyle
        Status:     Informational
        Stream:     IETF
        Date:       September 2020
        Mailbox:    warren@kumari.net, 
                    cdoyle@juniper.net
        Pages:      16
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-opsawg-sdi-13.txt

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

        DOI:        10.17487/RFC8886

Deploying a new network device in a location where the operator has
no staff of its own often requires that an employee physically travel
to the location to perform the initial install and configuration,
even in shared facilities with "remote-hands" (or similar) support.
In many cases, this could be avoided if there were an easy way to
transfer the initial configuration to a new device while still
maintaining confidentiality of the configuration.

This document extends existing vendor proprietary auto-install to
provide limited confidentiality to initial configuration during
bootstrapping of the device.

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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