Secure Zero Touch Provisioning (SZTP)
RFC 8572
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2021-06-22
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
|
2019-12-30
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
|
2019-08-19
|
Gunter Van de Velde | Closed request for Last Call review by OPSDIR with state 'Overtaken by Events' |
|
2019-08-19
|
Gunter Van de Velde | Assignment of request for Last Call review by OPSDIR to Victor Kuarsingh was marked no-response |
|
2019-08-19
|
Gunter Van de Velde | Closed request for Last Call review by OPSDIR with state 'Overtaken by Events' |
|
2019-08-19
|
Gunter Van de Velde | Assignment of request for Last Call review by OPSDIR to Jon Mitchell was marked no-response |
|
2019-04-30
|
(System) | Received changes through RFC Editor sync (created alias RFC 8572, changed abstract to 'This document presents a technique to securely provision a networking device … Received changes through RFC Editor sync (created alias RFC 8572, changed abstract to '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.', changed pages to 87, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2019-04-30, changed IESG state to RFC Published) |
|
2019-04-30
|
(System) | RFC published |