IPv4 Address Conflict Detection
RFC 5227, “IPv4 Address Conflict Detection”, is a Proposed Standard document published in July 2008 by S. Cheshire. It updates RFC 826. The canonical text is published by the RFC Editor.
Abstract
When two hosts on the same link attempt to use the same IPv4 address at the same time (except in rare special cases where this has been arranged by prior coordination), problems ensue for one or both hosts. This document describes (i) a simple precaution that a host can take in advance to help prevent this misconfiguration from happening, and (ii) if this misconfiguration does occur, a simple mechanism by which a host can passively detect, after the fact, that it has happened, so that the host or administrator may respond to rectify the problem. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 5227 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5226 Guidelines for Writing an IANA Considerations Section in RFCs
- RFC 5228 Sieve: An Email Filtering Language
- RFC 5225 RObust Header Compression Version 2 : Profiles for RTP, UDP, IP, ESP and UDP-Lite
- RFC 5229 Sieve Email Filtering: Variables Extension
- RFC 5224 Diameter Policy Processing Application
- RFC 5230 Sieve Email Filtering: Vacation Extension
- RFC 5223 Discovering Location-to-Service Translation Servers Using the Dynamic Host Configuration Protocol
- RFC 5231 Sieve Email Filtering: Relational Extension