[v6ops] next steps for draft-palet-v6ops-464xlat-deployment

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Thu, 16 November 2017 05:13 UTC

Return-Path: <prvs=1493446864=jordi.palet@consulintel.es>
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 75C4B129470 for <v6ops@ietfa.amsl.com>; Wed, 15 Nov 2017 21:13:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
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 hVszZzi85Au4 for <v6ops@ietfa.amsl.com>; Wed, 15 Nov 2017 21:12:59 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 840011286B1 for <v6ops@ietf.org>; Wed, 15 Nov 2017 21:12:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1510809176; x=1511413976; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: Mime-version:Content-type:Content-transfer-encoding:Reply-To; bh=tJ79j7VDkmG0c7fahidCHTzpRo3oRZiR8xQNFIfYlKY=; b=kcATeorUFiGCy /UTaCLsJc4rj669elR3BQeIh/q23RmBXf1qxfcpR0vHsoxu0KRvH3PUltlFifQ9z GP9BCrGBqfdQAbjHkW0GcrMwsoUj+fVHm2nmc8bVWImkA9dVo3Bz3ugOfGHHe2qf FwksPLuAb8e/X/dbHZkZU7C4vxvLJM=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=K7euCu02q5YahiMQFIKF1G42MsuVzMOBe3cuMMfjN5etDJoIiIF8GfHs3Ty7 R924/LX1yLREG0MLt95qEWoHfsDhBRZ4WtmKgg68ehlwdiYrzjXPvpua5 PTd6SKLgJRjZRiBlVD92Cb4XcrmebFeURVti/U0Lse4kHNozXSZSI4=;
X-MDAV-Processed: mail.consulintel.es, Thu, 16 Nov 2017 06:12:56 +0100
X-Spam-Processed: mail.consulintel.es, Thu, 16 Nov 2017 06:12:56 +0100
Received: from [172.20.60.6] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005625225.msg for <v6ops@ietf.org>; Thu, 16 Nov 2017 06:12:54 +0100
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:171116:md50005625225::T7EiaJKcZlQnSp03:00002G2o
X-Return-Path: prvs=1493446864=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/f.27.0.171010
Date: Thu, 16 Nov 2017 13:12:41 +0800
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: v6ops@ietf.org
Message-ID: <1DD923D6-32AB-4017-86A7-9FDD1F03BB8A@consulintel.es>
Thread-Topic: next steps for draft-palet-v6ops-464xlat-deployment
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/hRWukiQV0a0loNvZc5IJCCGEWt8>
Subject: [v6ops] next steps for draft-palet-v6ops-464xlat-deployment
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 16 Nov 2017 05:13:01 -0000

Hi,

Before continuing with this work, I will like to make sure that the path I understood in the WG meeting is the one we want.

Instead of concentrating in 464XLAT, document how we can correctly deploy NAT64 with/without DNS64 in such way that we don’t break DNSSEC. 464XLAT is one possible scenario, but NAT64 alone as well.

Is that the correct take on this?

I think we can use most of the text of the current document, will see …

Anyone interested in co-authoring it?

I will try to have a new version around end of this month, especially if a possible co-author is pro-active enough ;-)

Regards,
Jordi
 



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.