RFC 8992: Autonomic IPv6 Edge Prefix Management in Large-Scale Networks
In plain English — editorial summary, not part of the RFC
This document defines two autonomic technical objectives for IPv6 prefix management at the edge of large-scale ISP networks, with an extension to support IPv4 prefixes. An important purpose of this document is to use it for validation of the design of various components of the Autonomic Networking Infrastructure.
Document record
- Document ID
- RFC8992
- Published
- May 2021
- Authors
- S. Jiang; Z. Du; B. Carpenter; Q. Sun
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8991GeneRic Autonomic Signaling Protocol Application Program Interface (GRASP API)Current
May 2021
- RFC 8993A Reference Model for Autonomic NetworkingCurrent
May 2021
- RFC 8994An Autonomic Control Plane (ACP)Current
May 2021
- RFC 8990GeneRic Autonomic Signaling Protocol (GRASP)Current
May 2021
- RFC 8995Bootstrapping Remote Secure Key Infrastructure (BRSKI)Current
May 2021
- RFC 8368Using an Autonomic Control Plane for Stable Connectivity of Network Operations, Administration, and Maintenance (OAM)Current
May 2018
- RFC 8366A Voucher Artifact for Bootstrapping ProtocolsCurrent
May 2018
- RFC 8982Registration Data Access Protocol (RDAP) Partial ResponseCurrent
February 2021
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?