Re: [Softwires] The port mapping issue

Tom Taylor <tom.taylor.stds@gmail.com> Thu, 28 March 2013 14:12 UTC

Return-Path: <tom.taylor.stds@gmail.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 022C221F8EB4 for <softwires@ietfa.amsl.com>; Thu, 28 Mar 2013 07:12:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.171
X-Spam-Level:
X-Spam-Status: No, score=-0.171 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.1]
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 5R731in6hnvW for <softwires@ietfa.amsl.com>; Thu, 28 Mar 2013 07:12:23 -0700 (PDT)
Received: from mail-ia0-x22e.google.com (mail-ia0-x22e.google.com [IPv6:2607:f8b0:4001:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 6919E21F8D2E for <softwires@ietf.org>; Thu, 28 Mar 2013 07:12:23 -0700 (PDT)
Received: by mail-ia0-f174.google.com with SMTP id b35so8193182iac.5 for <softwires@ietf.org>; Thu, 28 Mar 2013 07:12:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding:x-antivirus:x-antivirus-status; bh=W9JkwqfSmDDluRhWZb3C7pijcngR6ThE1Xl2oKbfYxY=; b=IGqguUyUTpB268u2NhW2I71qtJcCcL93rXtve64mGVndqC4oBGDV+nWnvE5aYve5Dq K0xrVF5ZA5RNEWEPSI069jC9x0duFZB0gXsQlt3PonwxxnCbrHvgwZzbZLTYdc2buvzD YGgMx1f5RJrO7XLK+E8GskFkxzNvtWgN4iQdUenZoowSjJrlmA0SFKNgClaTdybak6mh q6vgpS4u/TnGe9MVie4HF8UGzXZQyfWtElaSzYDI0aLroLrtNMj7P+eAAtHgTuxm4pW4 sb1VqwCpY8KvWlwN7QhIBCNjwBz6qf+0M35soNiFuDKRCApnujo+uKry+VNfVm9PZNVI DbDQ==
X-Received: by 10.50.150.167 with SMTP id uj7mr7331409igb.1.1364479943016; Thu, 28 Mar 2013 07:12:23 -0700 (PDT)
Received: from [127.0.0.1] ([64.56.244.88]) by mx.google.com with ESMTPS id vb15sm11917361igb.9.2013.03.28.07.12.21 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 28 Mar 2013 07:12:22 -0700 (PDT)
Message-ID: <51544FC6.4000508@gmail.com>
Date: Thu, 28 Mar 2013 10:12:22 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Wojciech Dec <wdec.ietf@gmail.com>
References: <51512618.8070704@ericsson.com> <51531757.8000707@gmail.com> <CAFFjW4iDp269jsMEX8gZA028sv-dyaqcvNemEDBZoSCN+H8chA@mail.gmail.com>
In-Reply-To: <CAFFjW4iDp269jsMEX8gZA028sv-dyaqcvNemEDBZoSCN+H8chA@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 130328-0, 28/03/2013), Outbound message
X-Antivirus-Status: Clean
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: Thu, 28 Mar 2013 14:12:24 -0000

On 27/03/2013 4:09 PM, Wojciech Dec wrote:
> On 27 March 2013 16:59, 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.
>>
>> 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?
>
> GMA codifies (power of 2) logic that translates easily into hardware
> based longest match lookups. Furthermore, it is actually trivially
> simple to implement on any platform (not hardware restricted thus):
> Something like 2 lines of C code, in optimized form. Lastly, it is
> very efficient in terms of info encoding: a PSID conveys a code-point
> that maps the entire port space or port range. Finally, embedding a
> explicit port-range in an IPv6 address is not an option (the N:1 rule
> case).
>
> Regards,
> Woj.

Thanks, Woj. I think I started off in the wrong direction, and should 
focus specifically on Suresh's proposal: GMA for both Light-Weight 4 
over 6 and MAP-E, with default a=0 for the former and a=6 for the latter.

When a=0, the GMA algorithm does degenerate to assigning ports as a 
single contiguous range per CPE. Min_port for a given PSID is given by 
the formula PSID * range size, or, in the notation of MAP-E section 5.1, 
PSID * 2^m. Max_port is given by Min_port + range size - 1.

With MAP-E, range size is inferred indirectly from the combination of 
the IPv4 prefix length in the Basic Map Rule and the number of EA bits. 
This information is not available for Light-Weight 4 over 6. Hence I 
believe the proposal to use GMA with a=0 for the latter amounts to 
explicit provisioning of PSID and range size to both the BR and the CPE.