Re: [Softwires] MAP-E question -- first prefix

Tom Taylor <tom.taylor.stds@gmail.com> Wed, 10 April 2013 12:57 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 970EC21F974A for <softwires@ietfa.amsl.com>; Wed, 10 Apr 2013 05:57:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.048
X-Spam-Level:
X-Spam-Status: No, score=0.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=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 lVZ-xs6q+jEA for <softwires@ietfa.amsl.com>; Wed, 10 Apr 2013 05:57:38 -0700 (PDT)
Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 23A2321F9747 for <softwires@ietf.org>; Wed, 10 Apr 2013 05:57:38 -0700 (PDT)
Received: by mail-ie0-f174.google.com with SMTP id aq17so445614iec.19 for <softwires@ietf.org>; Wed, 10 Apr 2013 05:57:37 -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; bh=bsf2KDn/z/XaWE4bUMWtf+JTZ5KN2wvUDARW3bk66kk=; b=yKrAhzPjoJx0szXXWn4cNxKYigA/iLgUz85gBCGKHylpoIMw5DItyuFCxcDgGZ7Ush AfS7AeOIQ4udrgI+euFh8KzmEFbc9qMzN60Wdcuo6w1YNkP8kUgsuwBkz9K++0VgBwE+ 2/P29RDHvYKqGIMpSXqQaDBkhjFb+NB0CFrj839428MB6Ok2Wdjz8ABxAIcG3YINAOXa 61FUlVYxFC8Xz/KA2b9F8vXudw4rGjk+NeUpYvTtyNVtlgEgtv+SThpjtIO914gOT5FX EMNonDm+pL2+sX0plQ6dlaiMdOaLCSPBKfy3GyKEl0vGjNcw0btKEgYDu3oq8AtXqMXF RS0Q==
X-Received: by 10.42.192.12 with SMTP id do12mr1148513icb.53.1365598657602; Wed, 10 Apr 2013 05:57:37 -0700 (PDT)
Received: from [192.168.1.65] (dsl-173-206-2-115.tor.primus.ca. [173.206.2.115]) by mx.google.com with ESMTPS id xe9sm27098413igb.7.2013.04.10.05.57.36 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 10 Apr 2013 05:57:36 -0700 (PDT)
Message-ID: <516561BF.5080308@gmail.com>
Date: Wed, 10 Apr 2013 08:57:35 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Ole Troan <otroan@employees.org>
References: <51633480.8070209@gmail.com> <28533DEA-0DD3-43DD-9CA4-929B0DBA9BDD@employees.org> <5163FBC3.3040602@gmail.com> <409980DC-2EDB-464F-9E12-E69CBF81268D@employees.org> <51649285.7050302@gmail.com> <35D6D53C-464D-476E-BF6C-97614F24259A@employees.org>
In-Reply-To: <35D6D53C-464D-476E-BF6C-97614F24259A@employees.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: Softwires <softwires@ietf.org>
Subject: Re: [Softwires] MAP-E question -- first prefix
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: Wed, 10 Apr 2013 12:57:38 -0000

Looks like we had a misunderstanding. Did the authors think of the 
configured subnetwork identifier of the existing text as being 
configured for a particular rule, in effect another rule parameter? I 
took it to be configured as a single value used in conjunction with all 
FMRs to calculate the target MAP IPv6 addresses.

On 10/04/2013 6:54 AM, Ole Troan wrote:
> Tom,
>
>>>> I think that captures the intent. However, I see a possible difficulty: differing lengths of the End-user IPv6 prefix for different CEs. We have to add two conditions:
>>>>
>>>> -- the configured subnetwork identifier is at least
>>>>             64 - min (n + o)
>>>> bits long, where the minimization is taken over all FMRs in the domain
>>>>
>>>> -- the subnetwork identifier used with a given calculated End-user IPv6 prefix uses the right-most (64 - (n + o)) bits of the configured subnetwork identifier, where (n + o) is taken from the FMR used for the calculation.
>>>>
>>>> Seems simpler just to restrict to the all-zeros value, but please comment.
>>>
>>> I can't see how different End-user IPv6 prefix lengths within a domain can work.
>>>
>>
>> The End-user IPv6 prefix length obviously has to be the same for all nodes using the same BMR, but couldn't, for example, the PSID width (i.e., the sharing ratio) vary from one BMR to another?
>
> absolutely. 'everything' can be different between different BMRs within the same domain.
>
> cheers,
> Ole
>
>