Re: [Softwires] Unified Softwire CPE: draft-bfmk-softwire-unified-cpe

Ole Trøan <otroan@employees.org> Sat, 01 December 2012 12:11 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 B7E3221F849E for <softwires@ietfa.amsl.com>; Sat, 1 Dec 2012 04:11:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level:
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dhD8a0OeBBlW for <softwires@ietfa.amsl.com>; Sat, 1 Dec 2012 04:11:16 -0800 (PST)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id B25CC21F849B for <softwires@ietf.org>; Sat, 1 Dec 2012 04:11:15 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAL7yuVCQ/khM/2dsb2JhbABEwAYWc4IeAQEEATo/BQsLRlcGiB0GvmCQIGEDm2yKXIJz
X-IronPort-AV: E=McAfee;i="5400,1158,6912"; a="10063051"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-3.cisco.com with ESMTP; 01 Dec 2012 12:11:14 +0000
Received: from [10.61.102.248] (dhcp-10-61-102-248.cisco.com [10.61.102.248]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id qB1CBDGx026590 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 1 Dec 2012 12:11:14 GMT
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Ole Trøan <otroan@employees.org>
In-Reply-To: <CAH3bfABSRon0NWGJv7H_mgocTX-VwroKcqEr5mYyrp2BXcV5MA@mail.gmail.com>
Date: Sat, 01 Dec 2012 13:11:16 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <6DF21FCC-1B07-4826-B146-46D89FE579D6@employees.org>
References: <94C682931C08B048B7A8645303FDC9F36E98AB16AD@PUEXCB1B.nanterre.francetelecom.fr> <50B8ADAD.5010409@viagenie.ca> <94C682931C08B048B7A8645303FDC9F36E99E2D6F6@PUEXCB1B.nanterre.francetelecom.fr> <9207CAAE-7907-4103-994C-07961030FAE9@employees.org> <CAH3bfACEZC9tYfpyOXu8sCWAvD9uFou1tLAxESvwPavKV4HESw@mail.gmail.com> <9D4F2E9C-FA92-48D6-AF14-69BC86F3D4B9@employees.org> <CAH3bfABSRon0NWGJv7H_mgocTX-VwroKcqEr5mYyrp2BXcV5MA@mail.gmail.com>
To: Qiong <bingxuere@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: "softwires@ietf.org" <softwires@ietf.org>
Subject: Re: [Softwires] Unified Softwire CPE: draft-bfmk-softwire-unified-cpe
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: Sat, 01 Dec 2012 12:11:16 -0000

Qiong,

[...]

> MAP could also create its tunnel endpoint address from the WAN prefix (not address).
> so you'd have, for CPE tunnel end point address:
> Thanks for clarification. But if MAP uses the WAN prefix as its tunnel endpoint address, does BR need to keep all the records for CPEs (because the CPE's WAN prefix might be arbitary) ? Or do you mean the CPE's WAN prefix will be embedded with EA bits ? Would you please explain it a bit more ?  

from MAP's perspective it doesn't matter if it is a /64 on the WAN or a /56 delegated prefix.
any prefix can have EA bits.

> 1) arbitrary IPv6 address (DS-lite)
> Why it is arbitary ? Is it the source address of the tunnel endpoint ?

in DS-lite the tunnel concentrator learns the tunnel endpoint address when the NAT bindings are created.
so the CPE is free to pick whatever IPv6 address it has. this is different from Public 4over6 and LW46 where the
address has to be configured on both ends.

cheers,
Ole