Re: [Gen-art] Gen-ART review of draft-ietf-intarea-nat-reveal-analysis-05

SM <sm@resistor.net> Fri, 22 March 2013 03:07 UTC

Return-Path: <sm@resistor.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07F2E21F8F02 for <gen-art@ietfa.amsl.com>; Thu, 21 Mar 2013 20:07:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EtdSKmiy5lIE for <gen-art@ietfa.amsl.com>; Thu, 21 Mar 2013 20:07:46 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 54E5221F8E6C for <gen-art@ietf.org>; Thu, 21 Mar 2013 20:07:46 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r2M37DoH014411; Thu, 21 Mar 2013 20:07:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1363921641; bh=xg0DLBpeiSgq+qcwn1w5PjUwCEbiIjBivATJcGClh/w=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=2yxSi07+8aKfOl7MEGDBr4527IVy/01jMoGEjcT/8U2oGep+CAVh6Bprx1N4pN9Cf bzIiCJVBvhzd3mSLWD1PmMBrLtVJpvNgOHpP7PPPof8HSS2FKKYCK0P69H6+IxBGeb sTTyQYB5ksLtlqx+xCkZaHNsz7SRv8bgIbBNXYcw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1363921641; i=@resistor.net; bh=xg0DLBpeiSgq+qcwn1w5PjUwCEbiIjBivATJcGClh/w=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=GuEmy912oluMAZ58amthDQ95TAqCRsaKGctxr/XjkzkwXSxfUgLABqBUuW3kcfrx5 nMT4OKeba4uCo9fUxiTnQnrJMnYSM30SQrhKQ156eM+RrgmBnlC0ZCC71SV6T9bX3v oDi6qmNjPsuhjVLz9ORhwBBjVMh/bbmj84m7nTys=
Message-Id: <6.2.5.6.2.20130321191544.0a5e3a48@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 21 Mar 2013 19:51:30 -0700
To: mohamed.boucadair@orange.com, Peter Yee <peter@akayla.com>
From: SM <sm@resistor.net>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EB9CFC5BF@PUEXCB1B.nanter re.francetelecom.fr>
References: <CD5FFF04.2A11%peter@akayla.com> <94C682931C08B048B7A8645303FDC9F36EB9CFC5BF@PUEXCB1B.nanterre.francetelecom.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: gen-art@ietf.org, draft-ietf-intarea-nat-reveal-analysis.all@tools.ietf.org, Brian Haberman <brian@innovationslab.net>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-intarea-nat-reveal-analysis-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 22 Mar 2013 03:07:47 -0000

Hi Med,
At 02:03 21-03-2013, mohamed.boucadair@orange.com wrote:
>I didn't received any explicit answer from your side whether the 
>changes in -06 solve your concern.

Sorry, it was IETF week.

>I would appreciate if you can check the new revision. For your 
>convenience the diff is available here: 
>http://www.ietf.org/rfcdiff?url2=draft-ietf-intarea-nat-reveal-analysis-06

There was the following in Section 2:

   "HOST_ID does not reveal the identity of a user, a subscriber or an
    application."

That was changed to state that HOST_ID is not designed to reveal the 
identity of a user.  The question is whether it can be used to reveal 
the identity of the user.  I don't see an explanation for that in 
draft-ietf-intarea-nat-reveal-analysis-06.

The layering issue for Forwarded header (Section 4.4.1) is still in 
draft-ietf-intarea-nat-reveal-analysis-06.

In Section 4.4.2:

   "Injecting Forwarded header also introduces some implementations
    complexity if the HTTP message is at or close to the MTU size."

I don't know how much breakage will occur with this.

I would leave it to the document shepherd to decide whether to 
discuss all this in the working group.  It could be used to override 
the concern if everyone looks the other way. :-)

Regards,
-sm