Re: [v6ops] Genart last call review of draft-ietf-v6ops-v4v6-xlat-prefix-01

Tore Anderson <tore@fud.no> Sun, 28 May 2017 11:27 UTC

Return-Path: <tore@fud.no>
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 3112712422F; Sun, 28 May 2017 04:27:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.502
X-Spam-Level:
X-Spam-Status: No, score=-0.502 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 qyxs5eOm5HQ8; Sun, 28 May 2017 04:27:31 -0700 (PDT)
Received: from mail.fud.no (mail.fud.no [IPv6:2a02:c0:4f0:bb02:f816:3eff:fed3:8342]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 866241205F0; Sun, 28 May 2017 04:27:31 -0700 (PDT)
Received: from [2a02:fe0:c420:330a::bc8] (port=55670 helo=envy.e1.y.home) by mail.fud.no with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from <tore@fud.no>) id 1dEwM5-000501-Ce; Sun, 28 May 2017 11:27:29 +0000
Date: Sun, 28 May 2017 13:27:28 +0200
From: Tore Anderson <tore@fud.no>
To: Roni Even <ron.even.tlv@gmail.com>
Cc: gen-art@ietf.org, v6ops@ietf.org, ietf@ietf.org, draft-ietf-v6ops-v4v6-xlat-prefix.all@ietf.org
Message-ID: <20170528132728.1b418349@envy.e1.y.home>
In-Reply-To: <149595419894.24426.7074020393438812680@ietfa.amsl.com>
References: <149595419894.24426.7074020393438812680@ietfa.amsl.com>
X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-redhat-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/TIsCG7GXdhluQdUrxDwIVET9PJ8>
Subject: Re: [v6ops] Genart last call review of draft-ietf-v6ops-v4v6-xlat-prefix-01
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: Sun, 28 May 2017 11:27:33 -0000

Hi Roni, and thank you for your review.

> I was wondering why this document does not update RFC6052. My
> reasoning is that RFC7915 section 6 says "The translator MUST support
> the stateless address mapping algorithm defined in [RFC6052], which is
> the default behavior."  This document suggests that the mapping in
> this document can be used.

There's nothing in RFC6052 that needs updating, as RFC6052 already
caters for the use of its stateless address mapping algorithm with
arbitrary IPv6 prefixes outside of the WKP 64:ff9b::/96.

Tore