[v6ops] RFC 8683 on Additional Deployment Guidelines for NAT64/464XLAT in Operator and Enterprise Networks

rfc-editor@rfc-editor.org Tue, 26 November 2019 21:15 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32420120AE0; Tue, 26 Nov 2019 13:15:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RsSuh84L_Aw3; Tue, 26 Nov 2019 13:15:43 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3D33120ADC; Tue, 26 Nov 2019 13:15:42 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 4FF98F40704; Tue, 26 Nov 2019 13:15:17 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, v6ops@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20191126211517.4FF98F40704@rfc-editor.org>
Date: Tue, 26 Nov 2019 13:15:17 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ANCJVhp-yAsydhbF14bU9Ddcu5A>
Subject: [v6ops] =?utf-8?q?RFC_8683_on_Additional_Deployment_Guidelines_f?= =?utf-8?q?or_NAT64/464XLAT_in_Operator_and_Enterprise_Networks?=
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Nov 2019 21:15:44 -0000

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

        
        RFC 8683

        Title:      Additional Deployment Guidelines for NAT64/464XLAT 
                    in Operator and Enterprise Networks 
        Author:     J. Palet Martinez
        Status:     Informational
        Stream:     IETF
        Date:       November 2019
        Mailbox:    jordi.palet@theipv6company.com
        Pages:      38
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-v6ops-nat64-deployment-08.txt

        URL:        https://www.rfc-editor.org/info/rfc8683

        DOI:        10.17487/RFC8683

This document describes how Network Address and Protocol Translation
from IPv6 Clients to IPv4 Servers (NAT64) (including 464XLAT) can be
deployed in an IPv6 network -- whether it's cellular ISP, broadband
ISP, or enterprise -- and the possible optimizations. This document
also discusses issues to be considered when having IPv6-only
connectivity, such as: a) DNS64, b) applications or devices that use
literal IPv4 addresses or non-IPv6-compliant APIs, and c) IPv4-only
hosts or applications.

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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