[v6ops] Document Action: 'Additional NAT64/464XLAT Deployment Guidelines in Operator and Enterprise Networks' to Informational RFC (draft-ietf-v6ops-nat64-deployment-08.txt)
The IESG <iesg-secretary@ietf.org> Mon, 15 July 2019 19:49 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: v6ops@ietf.org
Delivered-To: v6ops@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 04EF31202DB; Mon, 15 Jul 2019 12:49:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.98.3
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, v6ops@ietf.org, v6ops-chairs@ietf.org, Mikael Abrahamsson <swmike@swm.pp.se>, rfc-editor@rfc-editor.org, draft-ietf-v6ops-nat64-deployment@ietf.org, warren@kumari.net, swmike@swm.pp.se
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <156322014401.27079.13445431277610847275.idtracker@ietfa.amsl.com>
Date: Mon, 15 Jul 2019 12:49:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/0YjG-U-9fHkG02ZgqAoYWex3Z5A>
Subject: [v6ops] Document Action: 'Additional NAT64/464XLAT Deployment Guidelines in Operator and Enterprise Networks' to Informational RFC (draft-ietf-v6ops-nat64-deployment-08.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 15 Jul 2019 19:49:04 -0000
The IESG has approved the following document: - 'Additional NAT64/464XLAT Deployment Guidelines in Operator and Enterprise Networks' (draft-ietf-v6ops-nat64-deployment-08.txt) as Informational RFC This document is the product of the IPv6 Operations Working Group. The IESG contact persons are Warren Kumari and Ignas Bagdonas. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-v6ops-nat64-deployment/ Technical Summary This document describes how NAT64 (including 464XLAT) can be deployed in an IPv6 network, whether cellular ISP, broadband ISP, or enterprise, and possible optimizations. The document also discusses issues to be considered when having IPv6-only connectivity, regarding: a) DNS64, b) applications or devices that use literal IPv4 addresses or non-IPv6 compliant APIs, and c) IPv4-only hosts or applications. Working Group Summary The draft started its life as draft-palet-v6ops-464xlat-deployment in October 2017, then evolved into draft-palet-v6ops-nat64-deployment in March 2018 as a NAT64 deployment guideline document intended to be BCP. It was adopted as a working group document as draft-ietf-v6ops-nat64-deployment in July 2018 with changed intended status to Informational. The discussions in the WG has been supportive of the draft, the author has taken feedback/suggestions into account and over time evolved/progressed the document during productive discussions. There has been no general opposition to the draft itself apart from people opposing on principle on DNS64 "breaking" DNSSEC. That is not the fault of this draft and this draft suggests no technological changes. Document Quality The document describes technology implemented by numerous networks and devices, primarily in mobile networks. The author proposes this technology to be used in more deployment scenarios and that's the motivation for this draft, to analyse the deployment considerations for other types of network types. The document has received substantial technical and stylistic feedback and I believe the document is in good technical shape. The RFC editor might have some linguistic/grammar/stylistic work to do on this draft, but I believe this is normal when the author is non-native english speaker/writer. Personnel Shepherd: Mikael Abrahamsson RAD: Warren Kumari