Re: [Softwires] The port mapping issue

Dan Wing <dwing@cisco.com> Mon, 01 April 2013 18:43 UTC

Return-Path: <dwing@cisco.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A6C911E80E0 for <softwires@ietfa.amsl.com>; Mon, 1 Apr 2013 11:43:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 OBo0snYcGupF for <softwires@ietfa.amsl.com>; Mon, 1 Apr 2013 11:43:28 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 5708821F93B0 for <softwires@ietf.org>; Mon, 1 Apr 2013 11:43:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2200; q=dns/txt; s=iport; t=1364841808; x=1366051408; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=5lPrjl+T5q34A9Y8IOng2Uh8en9Wei/BmXxWPGtKgmw=; b=kcCv7+gQk62HOMJ795xU+I1FZVB4GjeW3mYV2aqgmzIT+XVhtSsfub9T yh+MA5xRbNQRlcjvDOwhBZGtm3YMRrM/vDrLm7bwKO1G8lV6NaNNw5Tmt +vDifk8fpzWBeRzoMJtUpWldda5iJ2q6499wIm53Z5uDF9wrgZfIEQR/+ 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAG++WVGtJV2Z/2dsb2JhbABDgzu/TnwWdIIfAQEBAwEBAQE3MgIIAwULC0YhBjAGE4gCAwkGDLZoDYlXBIxggQ8LgQQzB4JfYQOIeowRgWCLcIUbgyscgS8IFw
X-IronPort-AV: E=Sophos;i="4.87,387,1363132800"; d="scan'208";a="193782721"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-4.cisco.com with ESMTP; 01 Apr 2013 18:43:27 +0000
Received: from sjc-vpn7-1852.cisco.com (sjc-vpn7-1852.cisco.com [10.21.151.60]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r31IhRkk011030; Mon, 1 Apr 2013 18:43:27 GMT
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <51531757.8000707@gmail.com>
Date: Mon, 01 Apr 2013 11:43:27 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <5D7E58A0-C125-49BB-8609-5F650E2DCB01@cisco.com>
References: <51512618.8070704@ericsson.com> <51531757.8000707@gmail.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>
X-Mailer: Apple Mail (2.1503)
Cc: softwires@ietf.org
Subject: Re: [Softwires] The port mapping issue
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Apr 2013 18:43:29 -0000

On Mar 27, 2013, at 8:59 AM, Tom Taylor <tom.taylor.stds@gmail.com> wrote:

> The meeting minutes record a disagreement over what port mapping algorithm to use. This affects both MAP-E and LW 4over6. As I understand it:
> 
> - either of these two technologies will work with either contiguous ports or ports scattered according to the GMA algorithm
> 
> - the real objection to GMA comes from Alain Durand, who wants to set up simple min-port, max-port filters on his network equipment.
> 
> 
> We all agree that port scattering offers negligible security advantage.

Port scattering, using GMA, provides tiny security advantage.  An attacker can determine the Generalized Modulus Algorithm, by causing a victim to open a bunch of TCP connections.  One way an attacker can cause a bunch of TCP connections to be opened is by sending an email with a bunch of <img src> tags to servers where the attacker can observe the TCP source ports for the connections.  Another way is to do the same with a web page.  GMA is a good amount of engineering and confusion for little gain, but the *appearance* of a gain because to a person the port numbers will appear random.  On other words, a false sense of security.  Port numbers are being used in courts of law and explaining GMA to the lay person will be complex.  I believe it is an unnecessary complexity.

-d


> 
> The reason that I heard given for preferring GMA for MAP-E is that it eliminates a restriction on the End-User Ipv6 address because the PSID is free to range from 0 upwards rather than from some higher number upwards. I don't follow this argument for two reasons:
> 
> - you now have a restriction that the offset field A must range from 1 upwards
> 
> - the PSID field has an upper limit 2^k-1 imposed by the sharing ratio, imposing a further restriction on the End-User IPv6 address value.
> 
> Could someone spell out more clearly why the GMA was seen as necessary for MAP-E?
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires