Re: [v6ops] new draft: draft-bao-v6ops-rfc6145bis

Tore Anderson <tore@fud.no> Sat, 25 July 2015 11:00 UTC

Return-Path: <tore@fud.no>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A6EF1A1AA8 for <v6ops@ietfa.amsl.com>; Sat, 25 Jul 2015 04:00:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 WMb8QhQpRbqC for <v6ops@ietfa.amsl.com>; Sat, 25 Jul 2015 04:00:38 -0700 (PDT)
Received: from greed.fud.no (greed.fud.no [IPv6:2a02:c0:1001:100::145]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9EB61A0094 for <v6ops@ietf.org>; Sat, 25 Jul 2015 04:00:37 -0700 (PDT)
Received: from [2a02:2121:84:39a0:0:37:df5b:3401] (port=41327 helo=envy.fud.no) by greed.fud.no with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from <tore@fud.no>) id 1ZIxBw-0003PL-Ca; Sat, 25 Jul 2015 13:00:32 +0200
Date: Sat, 25 Jul 2015 13:00:29 +0200
From: Tore Anderson <tore@fud.no>
To: Alberto Leiva <ydahhrk@gmail.com>
Message-ID: <20150725130029.41fedd80@envy.fud.no>
In-Reply-To: <CAA0dE=XHppxkOQRwdwtuzB=K8rNpXEH800u3Dk+a5Vz8LRhjpg@mail.gmail.com>
References: <201507041147.t64Bl2oR005661@irp-lnx1.cisco.com> <559A5DB6.4090602@cernet.edu.cn> <CAA0dE=XHppxkOQRwdwtuzB=K8rNpXEH800u3Dk+a5Vz8LRhjpg@mail.gmail.com>
X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.28; x86_64-redhat-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/XP9aUEZlh6nf_GJj7l8-bom-F6k>
Cc: v6ops@ietf.org, draft-bao-v6ops-rfc6145bis@tools.ietf.org
Subject: Re: [v6ops] new draft: draft-bao-v6ops-rfc6145bis
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: Sat, 25 Jul 2015 11:00:39 -0000

* Alberto Leiva
 
> >   Destination Address:  In the stateless mode, which is to say that if
> >      the IPv4 destination address is within a range of configured IPv4
> >      stateless translation prefix, the IPv6 destination address is the
> >      IPv4-translatable address derived from the IPv4 destination
> >      address per [RFC6052], Section 2.3.  A workflow example of
> >      stateless translation is shown in Appendix A of this document.
> >      Besides the default algorithm defined [RFC6052], other mechanisms
> >      also exist, which are defined in Section 6 of this document (EAM)
> >      and in [I-D.ietf-softwire-map-t].
> >
> >      In the stateful mode (which is to say that if the IPv4 destination
> >      address is not within the range of any configured IPv4 stateless
> >      translation prefix), the IPv6 destination address and
> >      corresponding transport-layer destination port are derived from
> >      the Binding Information Bases (BIBs) reflecting current session
> >     state in the translator as described in [RFC6146].
> 
> I find this a little excessive. It also seems to mandate no other
> address translation mechanisms should exist (is this true?).

Hi Alberto, and thank you for your feedback!

Fernando, Fred, Xing and I met on Friday morning to discuss 6145bis.
This exact issue came up. Suffice it to say that new text that
approaches the problem in much the same way you suggested is already in
the works, so please wait for -01 and let us know if that addresses
your concern in a satisfactory manner.

Tore