Re: [Softwires] MAP-E question -- provisioning of Rule IPv4 prefix

Ole Troan <otroan@employees.org> Tue, 09 April 2013 10:53 UTC

Return-Path: <otroan@employees.org>
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 7A77621F903B for <softwires@ietfa.amsl.com>; Tue, 9 Apr 2013 03:53:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 lrPkdGgPgtKP for <softwires@ietfa.amsl.com>; Tue, 9 Apr 2013 03:53:00 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id C5FE721F9029 for <softwires@ietf.org>; Tue, 9 Apr 2013 03:52:59 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AggFAIPyY1GQ/khL/2dsb2JhbABRgwbBd4ESFnSCHwEBBAE6PwULC0ZXBoghBq4VkDyObzMHgmBhA6gBgw06
X-IronPort-AV: E=Sophos;i="4.87,438,1363132800"; d="scan'208";a="12741455"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-3.cisco.com with ESMTP; 09 Apr 2013 10:52:58 +0000
Received: from dhcp-10-61-96-164.cisco.com (dhcp-10-61-96-164.cisco.com [10.61.96.164]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r39Aqu7X011054 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 9 Apr 2013 10:52:56 GMT
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <51633F76.8080405@gmail.com>
Date: Tue, 09 Apr 2013 12:52:56 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <AE32C8A2-3EAF-4079-8F49-BFA2C8CB7347@employees.org>
References: <51633F76.8080405@gmail.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>
X-Mailer: Apple Mail (2.1503)
Cc: Softwires <softwires@ietf.org>
Subject: Re: [Softwires] MAP-E question -- provisioning of Rule IPv4 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: Tue, 09 Apr 2013 10:53:00 -0000

Tom,

> In the previous note, I meant the BMR used as FMR, to be technical. But here's another point from the same section:
> 
>   The length of r MAY be zero, in which case the complete IPv4 address
>   or prefix is encoded in the EA bits.  If only a part of the IPv4
>   address/prefix is encoded in the EA bits, the Rule IPv4 prefix is
>   provisioned to the CE by other means (e.g.  a DHCPv6 option).
> 
> Question: does that second sentence also assume r = 0? If so, I think you've moved beyond what makes sense to document as part of MAP-E. Given that you have the MAP-E BMR mechanism, why wouldn't you use it?

no, the second sentence assumes r > 0. "If only a part of the IPv4 address is encoded...", implies that
the other part comes via the BMR.

cheers,
Ole