RFC 8572: Secure Zero Touch Provisioning (SZTP)
In plain English — editorial summary, not part of the RFC
This document presents a technique to securely provision a networking device when it is booting in a factory-default state. Variations in the solution enable it to be used on both public and private networks. The provisioning steps are able to update the boot image, commit an initial configuration, and execute arbitrary scripts to address auxiliary needs. The updated device is subsequently able to establish secure connections with other systems. For instance, a device may establish NETCONF (RFC 6241) and/or RESTCONF (RFC 8040) connections with deployment-specific network management systems.
Document record
- Document ID
- RFC8572
- Published
- April 2019
- Authors
- K. Watsen; I. Farrer; M. Abrahamsson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 87
- Also known as
- —
- Updated by:
- RFC 9646
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8521Registration Data Access Protocol (RDAP) Object TaggingCurrent
November 2018
- RFC 9224Finding the Authoritative Registration Data Access Protocol (RDAP) ServiceCurrent
March 2022
- RFC 7484Finding the Authoritative Registration Data (RDAP) ServiceObsoleted
March 2015
- RFC 9692RIFT: Routing in Fat TreesCurrent
April 2025
- RFC 4390Dynamic Host Configuration Protocol (DHCP) over InfiniBandCurrent
April 2006
- RFC 3942Reclassifying Dynamic Host Configuration Protocol version 4 (DHCPv4) OptionsCurrent
November 2004
- RFC 3442The Classless Static Route Option for Dynamic Host Configuration Protocol (DHCP) version 4Current
December 2002
- RFC 2132DHCP Options and BOOTP Vendor ExtensionsUpdated
March 1997
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?