[mif] RFC 6731 on Improved Recursive DNS Server Selection for Multi-Interfaced Nodes

rfc-editor@rfc-editor.org Wed, 19 December 2012 01:48 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 95A6421F85BC; Tue, 18 Dec 2012 17:48:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.868
X-Spam-Status: No, score=-101.868 tagged_above=-999 required=5 tests=[AWL=0.132, 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 sDH+ATXV9Ohi; Tue, 18 Dec 2012 17:48:30 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 3972721F857D; Tue, 18 Dec 2012 17:48:30 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id EC3CEB1E002; Tue, 18 Dec 2012 17:39:25 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20121219013925.EC3CEB1E002@rfc-editor.org>
Date: Tue, 18 Dec 2012 17:39:25 -0800 (PST)
Cc: mif@ietf.org, rfc-editor@rfc-editor.org
Subject: [mif] RFC 6731 on Improved Recursive DNS Server Selection for Multi-Interfaced Nodes
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Dec 2012 01:48:30 -0000

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

        RFC 6731

        Title:      Improved Recursive DNS Server Selection 
                    for Multi-Interfaced Nodes 
        Author:     T. Savolainen, 
                    J. Kato,
                    T. Lemon
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2012
        Mailbox:    teemu.savolainen@nokia.com, 
        Pages:      29
        Characters: 68882
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mif-dns-server-selection-12.txt

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

A multi-interfaced node is connected to multiple networks, some of
which might be utilizing private DNS namespaces.  A node commonly
receives recursive DNS server configuration information from all
connected networks.  Some of the recursive DNS servers might have
information about namespaces other servers do not have.  When a
multi-interfaced node needs to utilize DNS, the node has to choose
which of the recursive DNS servers to use.  This document describes
DHCPv4 and DHCPv6 options that can be used to configure nodes with
information required to perform informed recursive DNS server
selection decisions.  [STANDARDS-TRACK]

This document is a product of the Multiple Interfaces 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