Re: [BEHAVE] AD review of LSN requirements draft

Wesley Eddy <wes@mti-systems.com> Fri, 01 June 2012 12:41 UTC

Return-Path: <wes@mti-systems.com>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3274021F8AC7 for <behave@ietfa.amsl.com>; Fri, 1 Jun 2012 05:41:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 k8YyoKgyMwbS for <behave@ietfa.amsl.com>; Fri, 1 Jun 2012 05:41:18 -0700 (PDT)
Received: from omr14.networksolutionsemail.com (omr14.networksolutionsemail.com [205.178.146.64]) by ietfa.amsl.com (Postfix) with ESMTP id B659521F8BD0 for <behave@ietf.org>; Fri, 1 Jun 2012 05:41:16 -0700 (PDT)
Received: from cm-omr11 (mail.networksolutionsemail.com [205.178.146.50]) by omr14.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id q51CfGwr027452 for <behave@ietf.org>; Fri, 1 Jun 2012 08:41:16 -0400
Authentication-Results: cm-omr11 smtp.user=wes@mti-systems.com; auth=pass (PLAIN)
X-Authenticated-UID: wes@mti-systems.com
Received: from [69.81.143.202] ([69.81.143.202:10002] helo=[192.168.1.106]) by cm-omr11 (envelope-from <wes@mti-systems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id 48/38-11548-B68B8CF4; Fri, 01 Jun 2012 08:41:16 -0400
Message-ID: <4FC8B865.3070001@mti-systems.com>
Date: Fri, 01 Jun 2012 08:41:09 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: mohamed.boucadair@orange.com
References: <4FC6F151.3080404@mti-systems.com> <4FC7ACE4.2010301@viagenie.ca> <94C682931C08B048B7A8645303FDC9F36E2CB78A4F@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36E2CB78A4F@PUEXCB1B.nanterre.francetelecom.fr>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Cc: "draft-ietf-behave-lsn-requirements.all@tools.ietf.org" <draft-ietf-behave-lsn-requirements.all@tools.ietf.org>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] AD review of LSN requirements draft
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jun 2012 12:41:19 -0000

On 6/1/2012 8:19 AM, mohamed.boucadair@orange.com wrote:
> Hi Simon, all,
>  
> 
>> -----Message d'origine-----
>> De : behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] 
>> De la part de Simon Perreault
>> Envoyé : jeudi 31 mai 2012 19:40
>> À : Wesley Eddy
>> Cc : draft-ietf-behave-lsn-requirements.all@tools.ietf.org; 
>> behave@ietf.org
>> Objet : Re: [BEHAVE] AD review of LSN requirements draft
>>
>>
>>> (6) I think it would be good to have an advisory
>>> reference to the issues in:
>>> http://tools.ietf.org/html/draft-donley-nat444-impacts-03
>>> and whether or not following the recommendations in this
>>> document helps to avoid such issues.  The RFC 6269
>>> reference already in the introduction is okay, but it
>>> probably glosses over this topic too quickly.
>>
>> In addition to Dan's response, the draft-donley does not evaluate CGNs 
>> that have a PCP server, which our draft requires. I think the 
>> inclusion 
>> of PCP would affect the results significantly.
> 
> 
> Med: Agree. FWIW, an example of a detailed report for an application tested in draft-donley-* is available at: http://tools.ietf.org/html/draft-boucadair-pcp-bittorrent-00 (various combinations are tested including playing with the configuration of the BT clients to allow multiple connections from the same IP).
> 

I think it would be great to add a sentence in the justification
of the PCP requirement to specifically say that it's intended
to improve on prior CGN implementations that did not include PCP
and were found to have problems with certain applications (with
citations).

-- 
Wes Eddy
MTI Systems