[BEHAVE] RFC 7050 on Discovery of the IPv6 Prefix Used for IPv6 Address Synthesis

rfc-editor@rfc-editor.org Wed, 06 November 2013 01:32 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E43A21E8154; Tue, 5 Nov 2013 17:32:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.132
X-Spam-Level:
X-Spam-Status: No, score=-102.132 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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FWLmqY9aTul3; Tue, 5 Nov 2013 17:32:27 -0800 (PST)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 2479A21E80FF; Tue, 5 Nov 2013 17:32:25 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 755E175E001; Tue, 5 Nov 2013 17:22:59 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20131106012259.755E175E001@rfc-editor.org>
Date: Tue, 05 Nov 2013 17:22:59 -0800
Cc: drafts-update-ref@iana.org, behave@ietf.org, rfc-editor@rfc-editor.org
Subject: [BEHAVE] RFC 7050 on Discovery of the IPv6 Prefix Used for IPv6 Address Synthesis
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Nov 2013 01:32:28 -0000

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

        
        RFC 7050

        Title:      Discovery of the IPv6 Prefix 
                    Used for IPv6 Address Synthesis 
        Author:     T. Savolainen, J. Korhonen,
                    D. Wing
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2013
        Mailbox:    teemu.savolainen@nokia.com, 
                    jouni.nospam@gmail.com, 
                    dwing@cisco.com
        Pages:      22
        Characters: 50097
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-behave-nat64-discovery-heuristic-17.txt

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

This document describes a method for detecting the presence of DNS64
and for learning the IPv6 prefix used for protocol translation on an
access network.  The method depends on the existence of a well-known
IPv4-only fully qualified domain name "ipv4only.arpa.".  The
information learned enables nodes to perform local IPv6 address
synthesis and to potentially avoid NAT64 on dual-stack and
multi-interface deployments.

This document is a product of the Behavior Engineering for Hindrance Avoidance Working Group of the IETF.

This is now a Proposed Standard.

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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
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