RFC 3927 on Dynamic Configuration of IPv4 Link-Local Addresses

rfc-editor@rfc-editor.org Thu, 26 May 2005 00:24 UTC

Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Db6Ax-0003oD-S3; Wed, 25 May 2005 20:24:39 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Db6Aw-0003o5-0v for ietf-announce@megatron.ietf.org; Wed, 25 May 2005 20:24:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11392 for <ietf-announce@ietf.org>; Wed, 25 May 2005 20:24:36 -0400 (EDT)
Received: from boreas.isi.edu ([]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Db6TQ-0007DN-85 for ietf-announce@ietf.org; Wed, 25 May 2005 20:43:44 -0400
Received: from ISI.EDU (adma.isi.edu []) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j4Q0NoL23022; Wed, 25 May 2005 17:23:50 -0700 (PDT)
Message-Id: <200505260023.j4Q0NoL23022@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 25 May 2005 17:23:50 -0700
X-ISI-4-39-6-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Cc: zeroconf@merit.edu, rfc-editor@rfc-editor.org
Subject: RFC 3927 on Dynamic Configuration of IPv4 Link-Local Addresses
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

A new Request for Comments is now available in online RFC libraries.

        RFC 3927

        Title:      Dynamic Configuration of IPv4 Link-Local Addresses
        Author(s):  S. Cheshire, B. Aboba, E. Guttman
        Status:     Standards Track
        Date:       May 2005
        Mailbox:    rfc@stuartcheshire.org, bernarda@microsoft.com,
        Pages:      33
        Characters: 83102
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-zeroconf-ipv4-linklocal-17.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3927.txt

To participate in wide-area IP networking, a host needs to be
configured with IP addresses for its interfaces, either manually by
the user or automatically from a source on the network such as a
Dynamic Host Configuration Protocol (DHCP) server.  Unfortunately,
such address configuration information may not always be available.
It is therefore beneficial for a host to be able to depend on a useful
subset of IP networking functions even when no address configuration
is available.  This document describes how a host may automatically
configure an interface with an IPv4 address within the 169.254/16
prefix that is valid for communication with other devices connected to
the same physical (or logical) link.

IPv4 Link-Local addresses are not suitable for communication with
devices not directly connected to the same physical (or logical)
link, and are only used where stable, routable addresses are not
available (such as on ad hoc or isolated networks).  This document
does not recommend that IPv4 Link-Local addresses and routable
addresses be configured simultaneously on the same interface.

This document is a product of the Zero Configuration Networking
Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
IETF-Announce mailing list