Re: Comment on draft-iab-ipv6-nat-00

Christian Vogt <christian.vogt@ericsson.com> Thu, 19 March 2009 21:33 UTC

Return-Path: <christian.vogt@ericsson.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 388323A6902 for <ietf@core3.amsl.com>; Thu, 19 Mar 2009 14:33:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YXtRySQS5H-T for <ietf@core3.amsl.com>; Thu, 19 Mar 2009 14:33:23 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by core3.amsl.com (Postfix) with ESMTP id 7CA033A684E for <ietf@ietf.org>; Thu, 19 Mar 2009 14:33:23 -0700 (PDT)
Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 456222F787E; Thu, 19 Mar 2009 17:34:08 -0400 (EDT)
Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 19 Mar 2009 17:34:08 -0400
X-Sasl-enc: pP2bfV1kYE07PGy7UiVie+RqY04WiT0aArEobH9DLV7U 1237498446
Received: from [192.168.21.129] (unknown [216.239.45.19]) by mail.messagingengine.com (Postfix) with ESMTPSA id B368D38F27; Thu, 19 Mar 2009 17:34:06 -0400 (EDT)
Message-Id: <B63EFD92-6D9F-4766-BDF4-71583056C89E@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: Lixia Zhang <lixia@CS.UCLA.EDU>
In-Reply-To: <E5EABF3A-2A21-45A0-AC58-7A97FA6BC8CC@CS.UCLA.EDU>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: Comment on draft-iab-ipv6-nat-00
Date: Thu, 19 Mar 2009 14:34:05 -0700
References: <D33517E6-52B4-4509-B244-8DE8DBC62BC6@ericsson.com> <20090318172429.GQ91664@cisco.com> <D0E69C70-ADF8-4DCD-985B-4F9B4DC71935@ericsson.com> <E5EABF3A-2A21-45A0-AC58-7A97FA6BC8CC@CS.UCLA.EDU>
X-Mailer: Apple Mail (2.929.2)
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Mar 2009 21:33:24 -0000

> I will get back to your original comments in the next msg, but I feel
> the need to first correct potentially a very big error in the above:
> would you please kindly point to the exact text in draft-iab-ipv6- 
> nat-00
> that either stated or implied "end-to-end *locator* transparency", as
> you attributed to the draft?

Hi Lixia -

I used the term "locator transparency" to distinguish this from other
types of transparency, such as data transparency or, in a world with
identifier-locator separation, identifier transparency.  I found this
useful given that I was talking about identifier-locator separation.

Consequently, "locator transparency" in my posts has the meaning of "IP
address transparency", i.e., the type of transparency that NATs break.
Since your document is about NAT, I am assuming that this is also the
type of transparency that you are referring to in your document.

- Christian