IETF Logo Mail Archive

Re: [v6ops] draft-ietf-v6ops-siit-eam WGLC

Tore Anderson <tore@fud.no> Mon, 15 June 2015 12:03 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 478C21B2C10 for <v6ops@ietfa.amsl.com>; Mon, 15 Jun 2015 05:03:57 -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 RpP-P6Ratzy4 for <v6ops@ietfa.amsl.com>; Mon, 15 Jun 2015 05:03:55 -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 AEE9B1B2C0F for <v6ops@ietf.org>; Mon, 15 Jun 2015 05:03:55 -0700 (PDT)
Received: from [2a02:2121:8e:660:0:3:f793:8501] (port=51744 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 1Z4T7H-0004jK-Ni; Mon, 15 Jun 2015 14:03:51 +0200
Date: Mon, 15 Jun 2015 14:03:50 +0200
From: Tore Anderson <tore@fud.no>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
Message-ID: <20150615140350.17d819fe@envy.fud.no>
In-Reply-To: <75B6FA9F576969419E42BECB86CB1B89168A5B92@xmb-rcd-x06.cisco.com>
References: <201506141800.t5EI02ol016995@irp-lnx1.cisco.com> <75B6FA9F576969419E42BECB86CB1B89168A5B92@xmb-rcd-x06.cisco.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/kJbsW9ip8vFV4Z7CZ5mQ4SvwH1c>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] draft-ietf-v6ops-siit-eam WGLC
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: <http://www.ietf.org/mail-archive/web/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 Jun 2015 12:03:57 -0000

Hi Hemant,

* Hemant Singh (shemant)

> At the end of the A.1 section you have text that says "Note that this
> is the exact opposite of the SIIT-DC use case".  At the end of the
> A.3 section you have text that says  "Note that this is the exact
> opposite of the 464XLAT use case".
> 
> It's not clear to me what is "opposite" referring to.

The use cases are opposite to each other, e.g.:

- A.1 (464XLAT) is opposite to A.3 (SIIT-DC)
- A.3 (SIIT-DC) is opposite to A.1 (464XLAT)

...in the sense that an IPv4 packet traversing a 464XLAT CLAT and being
tranlated to IPv6 is sent by a local IPv4 app and is destined
for the public Internet, while an IPv4 packet traversing an SIIT-DC
gateway is sent from the public Internet and is destined for a local
IPv4 service.

> Do you even need these two sentences in the document?

No, probably not. We'll remove them, thanks!

Tore

v2.23.0 | Report a Bug | By Email