Re: [Gen-art] Gen-ART review of draft-ietf-v6ops-siit-dc-02

Tore Anderson <tore@redpill-linpro.com> Mon, 05 October 2015 12:07 UTC

Return-Path: <tore@redpill-linpro.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C58131AC409 for <gen-art@ietfa.amsl.com>; Mon, 5 Oct 2015 05:07:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 TJa6Gqcx24WQ for <gen-art@ietfa.amsl.com>; Mon, 5 Oct 2015 05:07:52 -0700 (PDT)
Received: from gallus.zimbra.h.bitbit.net (gallus.zimbra.h.bitbit.net [87.238.49.226]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1EB2E1AC40E for <gen-art@ietf.org>; Mon, 5 Oct 2015 05:07:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by gallus.zimbra.h.bitbit.net (Postfix) with ESMTP id 0DD02C1184; Mon, 5 Oct 2015 14:07:50 +0200 (CEST)
Received: from gallus.zimbra.h.bitbit.net ([127.0.0.1]) by localhost (gallus.zimbra.h.bitbit.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id Lv0IIx4Xhab3; Mon, 5 Oct 2015 14:07:48 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by gallus.zimbra.h.bitbit.net (Postfix) with ESMTP id DC696C1195; Mon, 5 Oct 2015 14:07:48 +0200 (CEST)
X-Virus-Scanned: amavisd-new at gallus.zimbra.h.bitbit.net
Received: from gallus.zimbra.h.bitbit.net ([127.0.0.1]) by localhost (gallus.zimbra.h.bitbit.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id BzaZ0sAsge1Q; Mon, 5 Oct 2015 14:07:48 +0200 (CEST)
Received: from echo.ms.redpill-linpro.com (login-osl1.i.bitbit.net [87.238.42.59]) by gallus.zimbra.h.bitbit.net (Postfix) with ESMTPSA id A67DEC1184; Mon, 5 Oct 2015 14:07:48 +0200 (CEST)
Date: Mon, 05 Oct 2015 14:07:48 +0200
From: Tore Anderson <tore@redpill-linpro.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Message-ID: <20151005140748.17bddf73@echo.ms.redpill-linpro.com>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37A839FB@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37A839FB@ESESSMB209.ericsson.se>
Organization: Redpill Linpro AS
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/gen-art/H3PC0QmDmrD365hsOdqwvL6zi-A>
Cc: "draft-ietf-v6ops-siit-dc.all@tools.ietf.org" <draft-ietf-v6ops-siit-dc.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-v6ops-siit-dc-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Oct 2015 12:07:54 -0000

Hello Christer, and thank you very much for your feedback.

Comments in-line.

* Christer Holmberg <christer.holmberg@ericsson.com>

> Q1_1:
> 
> In a few places the 'BR' abbreviation is used, but it is not enhanced until section 2. Please enhance on first occurrence in section 1.

Ack.

> Q1_2:
> 
> In a few places the 'BR' abbreviation is used, but it is not enhanced until section 2. Please enhance on first occurrence in section 1.
> 
> The text says:
> 
> "o  To ensure that that the legacy users' IPv4 addresses remain
>       visible to the nodes and applications."
> 
> ...and:
> 
> "This ensures that there is no loss of information; the end-user's IPv4
> source address remains available to the application, allowing"
> 
> It may be obvious, but would it be possible to somehow make it more clear that the text is not (I assume) talking about the application running on the IPv4 node, but an application running in an IPv6 network?

I qualified these statements as follows:

  [...] the legacy users' IPv4 addresses remain visible to the nodes and
  applications located in the IPv6 network.

  [...] the end-user's IPv4 source address remains available to the
  application located in the IPv6 network,

> Section 6 (IANA Considerations):
> ----------------------------------------
> 
> Q6_1: Do we normally remove the section if there are no requests from
> IANA? Personally I prefer to keep the explicit "This draft makes no
> request of the IANA." sentence.

OK. (I had just copied this formulation from another draft from another
author.)

> Section 2 (Terminology):
> -----------------------------
> 
> Q2_1: Is there really a need to define the edge relay (ER) here?
> 
> It is not used anywhere in the document, and it creates a cross-reference with draft-ietf-v6ops-siit-dc-2xlat - which is the document extending the SIIT mechanism, by defining the ER

The term "ER" is used in sections 4.1, 4.2, 4.3 and Figure 4 at least,
so I think the definition needs to stay in section 2.

The changes I made thanks to your review are shown here:

https://github.com/toreanderson/ietf/commit/782d337d32e13a86210d5801a758320371130ce1

Please have a look and let me know if you're happy with this, or if I
should more adjustments are desired.

Best regards,
Tore Anderson