RFC 6724 on Default Address Selection for Internet Protocol Version 6 (IPv6)

rfc-editor@rfc-editor.org Tue, 11 September 2012 00:18 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 602F521F873A; Mon, 10 Sep 2012 17:18:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.374
X-Spam-Status: No, score=-101.374 tagged_above=-999 required=5 tests=[AWL=0.626, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id o-mgipc6H0Zq; Mon, 10 Sep 2012 17:18:54 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id EA2C821F8737; Mon, 10 Sep 2012 17:18:53 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id DDAE8B1E00C; Mon, 10 Sep 2012 17:15:49 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6724 on Default Address Selection for Internet Protocol Version 6 (IPv6)
From: rfc-editor@rfc-editor.org
Message-Id: <20120911001549.DDAE8B1E00C@rfc-editor.org>
Date: Mon, 10 Sep 2012 17:15:49 -0700 (PDT)
Cc: ipv6@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Sep 2012 00:18:54 -0000

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

        RFC 6724

        Title:      Default Address Selection for Internet 
                    Protocol Version 6 (IPv6) 
        Author:     D. Thaler, Ed.,
                    R. Draves,
                    A. Matsumoto,
                    T. Chown
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2012
        Mailbox:    dthaler@microsoft.com, 
        Pages:      32
        Characters: 74407
        Obsoletes:  RFC3484

        I-D Tag:    draft-ietf-6man-rfc3484bis-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6724.txt

This document describes two algorithms, one for source address
selection and one for destination address selection.  The algorithms
specify default behavior for all Internet Protocol version 6 (IPv6)
implementations.  They do not override choices made by applications
or upper-layer protocols, nor do they preclude the development of
more advanced mechanisms for address selection.  The two algorithms
share a common context, including an optional mechanism for allowing
administrators to provide policy that can override the default
behavior.  In dual-stack implementations, the destination address
selection algorithm can consider both IPv4 and IPv6 addresses --
depending on the available source addresses, the algorithm might
prefer IPv6 addresses over IPv4 addresses, or vice versa.

Default address selection as defined in this specification applies to
all IPv6 nodes, including both hosts and routers.  This document
obsoletes RFC 3484.  [STANDARDS-TRACK]

This document is a product of the IPv6 Maintenance Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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

The RFC Editor Team
Association Management Solutions, LLC