RFC 7477: Child-to-Parent Synchronization in DNS
In plain English — editorial summary, not part of the RFC
This document specifies how a child zone in the DNS can publish a record to indicate to a parental agent that the parental agent may copy and process certain records from the child zone. The existence of the record and any change in its value can be monitored by a parental agent and acted on depending on local policy.
Document record
- Document ID
- RFC7477
- Published
- March 2015
- Authors
- W. Hardaker
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 15
- Also known as
- —
- Updated by:
- RFC 9975
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 7461Energy Object Context MIBCurrent
March 2015
- RFC 7460Monitoring and Control MIB for Power and EnergyCurrent
March 2015
- RFC 7494IEEE 802.11 Medium Access Control (MAC) Profile for Control and Provisioning of Wireless Access Points (CAPWAP)Current
April 2015
- RFC 7497Rate Measurement Test Protocol Problem Statement and RequirementsCurrent
April 2015
- RFC 7454BGP Operations and SecurityCurrent
February 2015
- RFC 7501Terminology for Benchmarking Session Initiation Protocol (SIP) Devices: Basic Session Setup and RegistrationCurrent
April 2015
- RFC 7502Methodology for Benchmarking Session Initiation Protocol (SIP) Devices: Basic Session Setup and RegistrationCurrent
April 2015
- RFC 7450Automatic Multicast TunnelingUpdated
February 2015
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?