IETF Logo Mail Archive

Re: [ietf-privacy] [Int-area] NAT Reveal / Host Identifiers

Stephen Farrell <stephen.farrell@cs.tcd.ie> Mon, 09 June 2014 14:01 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf-privacy@ietfa.amsl.com
Delivered-To: ietf-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F5231A017A; Mon, 9 Jun 2014 07:01:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 Nrv7TCI2lNqB; Mon, 9 Jun 2014 07:01:16 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 0C5C81A017B; Mon, 9 Jun 2014 07:01:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 69AC3BE97; Mon, 9 Jun 2014 15:01:15 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aKFLvIWC0MaF; Mon, 9 Jun 2014 15:01:14 +0100 (IST)
Received: from [172.16.23.144] (217.64.246.155.mactelecom.net [217.64.246.155]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 4E674BE79; Mon, 9 Jun 2014 15:01:14 +0100 (IST)
Message-ID: <5395BE2A.6090708@cs.tcd.ie>
Date: Mon, 09 Jun 2014 15:01:14 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Brandon Williams <brandon.williams@akamai.com>, Dan Wing <dwing@cisco.com>
References: <E87B771635882B4BA20096B589152EF628724B2C@eusaamb107.ericsson.se> <539016BE.3070008@gmx.net> <53906711.5070406@cs.tcd.ie> <5390CEC9.3000005@isi.edu> <5D2CC7D6-D9E1-49A8-818C-5FB33DC283C0@cisco.com> <5393119F.6050805@cs.tcd.ie> <5395BAD3.4040506@akamai.com>
In-Reply-To: <5395BAD3.4040506@akamai.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-privacy/ta-QHvSKUKXDHZzCv7tPBbB9E0o
Cc: "ietf-privacy@ietf.org" <ietf-privacy@ietf.org>, Internet Area <int-area@ietf.org>
Subject: Re: [ietf-privacy] [Int-area] NAT Reveal / Host Identifiers
X-BeenThere: ietf-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Internet Privacy Discussion List <ietf-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-privacy>, <mailto:ietf-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-privacy/>
List-Post: <mailto:ietf-privacy@ietf.org>
List-Help: <mailto:ietf-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-privacy>, <mailto:ietf-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jun 2014 14:01:18 -0000


On 09/06/14 14:46, Brandon Williams wrote:
> 
> Would you please indicate where the draft proposes a new identifier? If
> you are seeing a proposal for protocol changes somewhere in the draft,
> editing work is required in order to either clarify or excise the
> associated text.

Fair enough that its an assumption of mine that adding some kind of
identifier is required to meet the (no-longer mis-stated:-)
requirements for these use-cases. But I think that is logically
required, and its valid to draw obvious conclusions and its also
invalid to ignore obvious conclusions.

S.

v2.23.0 | Report a Bug | By Email