Re: [Softwires] MAP-T DMR and IPv4 address mapping

Ole Troan <otroan@employees.org> Thu, 06 June 2013 13:28 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 83DE321F9A1E for <softwires@ietfa.amsl.com>; Thu, 6 Jun 2013 06:28:12 -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 4LihGSK1WKVA for <softwires@ietfa.amsl.com>; Thu, 6 Jun 2013 06:28:07 -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 51B0921F9A1D for <softwires@ietf.org>; Thu, 6 Jun 2013 06:28:07 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAFACeNsFGQ/khN/2dsb2JhbABZgwkwAb9GeBZ0giMBAQQBeQULCw44VwaIGgYMuxiOfzMHgnphA5hohHWLIoMROg
X-IronPort-AV: E=Sophos;i="4.87,815,1363132800"; d="scan'208";a="14039936"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-3.cisco.com with ESMTP; 06 Jun 2013 13:28:06 +0000
Received: from [10.147.112.161] (dhcp-lys01-vla250-10-147-112-161.cisco.com [10.147.112.161]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r56DS3NI031974 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 6 Jun 2013 13:28:04 GMT
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <CAFFjW4gzraH1+waG6hmGC1+i5CqO9g3RMmgcJLeoPxk4EeXYrA@mail.gmail.com>
Date: Thu, 06 Jun 2013 15:28:00 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3BA2AAEA-E6CA-4370-A66E-40F5437F47E3@employees.org>
References: <CAFFjW4gzraH1+waG6hmGC1+i5CqO9g3RMmgcJLeoPxk4EeXYrA@mail.gmail.com>
To: Wojciech Dec <wdec.ietf@gmail.com>
X-Mailer: Apple Mail (2.1503)
Cc: Softwires-wg <softwires@ietf.org>, Congxiao Bao <congxiao@cernet.edu.cn>
Subject: Re: [Softwires] MAP-T DMR and IPv4 address mapping
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, 06 Jun 2013 13:28:12 -0000

> would like to get your feedback regarding a possible change to the way IPv4 addresses are mapped into the MAP-T DMR prefix. The current text, http://tools.ietf.org/html/draft-ietf-softwire-map-t-01#section-5.4 , follows RFC6052, and sees the IPv4 address inserted after the prefix. This aligns naturally with any/all existing NAT64 implementations, i.e. in a non-shared-address domain, a MAP-T CE would work with any regular NAT64 BR. 
> A direct consequence of following RFC6052 is that, in cases where the prefix is shorter than /64, it results in some "bit spreading" of the IPv4 address across the u-byte. See http://tools.ietf.org/html/rfc6052#page-5. This is likely to be cumbersome operationally.
> 
> An option for simplifying this, and the change proposal seeking your feedback, would be to specify that the DMR should be a /64 prefix, or at least to make a recommendation to that effect in the specification.

given that 6man is removing the special meaning of the U/G bits, perhaps RFC6052 should be updated, and MAP-T could ignore the U-byte?

cheers,
Ole