Re: [Softwires] MAP Open issues: Interface-id

Ole Troan <ot@cisco.com> Tue, 08 November 2011 08:36 UTC

Return-Path: <ot@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 F17CB21F8C0F for <softwires@ietfa.amsl.com>; Tue, 8 Nov 2011 00:36:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.784
X-Spam-Level:
X-Spam-Status: No, score=-6.784 tagged_above=-999 required=5 tests=[AWL=-0.185, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 SLfOaFdU0EmL for <softwires@ietfa.amsl.com>; Tue, 8 Nov 2011 00:36:52 -0800 (PST)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id 18EC221F8C06 for <softwires@ietf.org>; Tue, 8 Nov 2011 00:36:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ot@cisco.com; l=1857; q=dns/txt; s=iport; t=1320741412; x=1321951012; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=wZuiM2mkbtgpU548URcJDvd2JOUn2+eoA4/PaxXoLg4=; b=K93Xx7KCxUBbL33T7/YGli+9jALaMj1DSck3M49zHc0a+vo0vcO5pkse 3J7VYzpYrg+bbbX79h4Era+ztFU7Cw1jBXMZkyTB+m+fyPyETkmjzGHZs xXcmm9vCg8C7OniVD5KvzmiKS//eHzIk7dv5ijB7QNpBUeii6YiIiDQGf 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAFfpuE6Q/khM/2dsb2JhbABDqXeBBYFyAQEBAwESARQTPxALRlcGNYdgmFYBnwuISGMElCGRbQ
X-IronPort-AV: E=Sophos;i="4.69,476,1315180800"; d="scan'208";a="2618054"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-4.cisco.com with ESMTP; 08 Nov 2011 08:36:50 +0000
Received: from dhcp-osl-vl300-64-103-53-182.cisco.com (dhcp-osl-vl300-64-103-53-182.cisco.com [64.103.53.182]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pA88aonj002395; Tue, 8 Nov 2011 08:36:50 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Ole Troan <ot@cisco.com>
In-Reply-To: <CAM+vMESudUt5PT+qxQED_P2s7DB7T+3D_M4OWQ1yUvNN-xqhzA@mail.gmail.com>
Date: Tue, 08 Nov 2011 09:36:50 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <C09B8E42-A13F-4B30-AC88-43F98C709EDD@cisco.com>
References: <703EB6B3-AB8C-4690-91C6-2666C5779874@cisco.com> <9D6EBB21-38BC-4E6C-99E6-C3448FA2D3C8@laposte.net> <CAM+vMESudUt5PT+qxQED_P2s7DB7T+3D_M4OWQ1yUvNN-xqhzA@mail.gmail.com>
To: GangChen <phdgang@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] MAP Open issues: Interface-id
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, 08 Nov 2011 08:36:53 -0000

>> 1. Checksum neutrality being an open question, it is relevant here.
>> 2. It is useful AFAIK to distinguish CE addresses from BR addresses.
>> 
>> The best proposal I know so far is as follows (with CNP = Checksum
>> neutrality preserver)
>> 
>> CE ADDRESS
>> 
>> <- - - - - - IPv6 Unformatted  address (104 bits) - - - ->
>> +-------------------+----------+----------+---------------+
>> | Rule IPv6 prefix  |IPv4 suff.| Max PSID |  Padding = 0  |
>> +-------------------+----------+----------+---------------+
>> :
>> :<- - - - - - - - - 64  - - - - - >:<- - - - 40 - - - - ->:
>> :                                  :\                      \
>> :                                  <8>                      :<- 16 ->
>> :                                  : :                      :        :
>> +----------------------------------'-'----------------------+--------+
>> | IPv6 unformatted address (part 1)|V|                      |   CNP  |
>> 
>> +----------------------------------+-+----------------------+--------+
>> <- - - - - - - - - - -  IPv6 address (108 bits)  - - - - - - - - - - >
>> 
>> 
>> 
>> BR ADDRESS
>> 
>> +------------------------------------+-+-----------------+-+-------+
>> |              BR IPv6 prefix        |V|   IPv4 address  |0|  CNP  |
>> +------------------------------------+-+-----------------+-+-------+
>> < - - - - - - - - - 64  - - - - - - ><8><- - -  32 - - -><8><  16  >
>> 
> 
> +1
> The checksum neutrality is desirable for translation case.
> I suggest to take above format into consideration

the consequence of that is that the destination IPv6 address will change for every flow.
the MAP node cannot any longer listen to a single IPv6 address for MAP traffic, but has to intercept packets for a whole prefix.

cheers,
Ole