RFC 8886: Secure Device Install
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8886
- Published
- September 2020
- Authors
- W. Kumari; C. Doyle
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8889Multipoint Alternate-Marking Method for Passive and Hybrid Performance MonitoringObsoleted
August 2020
- RFC 8893Resource Public Key Infrastructure (RPKI) Origin Validation for BGP ExportCurrent
September 2020
- RFC 8895Application-Layer Traffic Optimization (ALTO) Incremental Updates Using Server-Sent Events (SSE)Current
November 2020
- RFC 8896Application-Layer Traffic Optimization (ALTO) Cost CalendarCurrent
November 2020
- RFC 8897Requirements for Resource Public Key Infrastructure (RPKI) Relying PartiesCurrent
September 2020
- RFC 8901Multi-Signer DNSSEC ModelsCurrent
September 2020
- RFC 8906A Common Operational Problem in DNS Servers: Failure to CommunicateCurrent
September 2020
- RFC 8907The Terminal Access Controller Access-Control System Plus (TACACS+) ProtocolUpdated
September 2020
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?