IETF Logo Mail Archive

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

Qiong <bingxuere@gmail.com> Sat, 01 December 2012 09:09 UTC

Return-Path: <bingxuere@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 AFD6021F85EF for <softwires@ietfa.amsl.com>; Sat, 1 Dec 2012 01:09:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.373
X-Spam-Level:
X-Spam-Status: No, score=-3.373 tagged_above=-999 required=5 tests=[AWL=-0.075, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 x+QfF-KtVwEJ for <softwires@ietfa.amsl.com>; Sat, 1 Dec 2012 01:09:31 -0800 (PST)
Received: from mail-ia0-f172.google.com (mail-ia0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 06B0321F85E7 for <softwires@ietf.org>; Sat, 1 Dec 2012 01:09:30 -0800 (PST)
Received: by mail-ia0-f172.google.com with SMTP id z13so1089111iaz.31 for <softwires@ietf.org>; Sat, 01 Dec 2012 01:09:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=C17gyHz3jc2qFHDs2RbCTuS78C8MNqmjeLEKyifk0+s=; b=n+1TOKMq/tddbestqr/qFEsOpTf+1Sbbn3iw7X2L+OVWCU0OG70YVzPp2DFnVdz2B3 6Qfyz46e4edGrBRArEouYKA5lhlgHoDiD6WvRfISAp4KUHm3alJKxXx1Rd/goJAUXyMW /MB6LHq81bGdOogBApv8oVyWCbcU/4kQfuOKZD+JBvUCDaQucITLUfAlB0gJEUqETxG+ HcJPiEjaqWFZixiNa1hA/i+0Iblbxt1OLxOtKWc/uoIjgpbJpX1XpwjSLWlrZDVO9ies R9yQGic1MNg6MNTgD8mxIofbEcpyERk+1aNRnIARmP27hkyFc1Wsf7jJSdh82Z6PG/kb qs+w==
Received: by 10.50.152.194 with SMTP id va2mr1109363igb.25.1354352970292; Sat, 01 Dec 2012 01:09:30 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.76.200 with HTTP; Sat, 1 Dec 2012 01:08:49 -0800 (PST)
In-Reply-To: <9D4F2E9C-FA92-48D6-AF14-69BC86F3D4B9@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>
From: Qiong <bingxuere@gmail.com>
Date: Sat, 01 Dec 2012 17:08:49 +0800
Message-ID: <CAH3bfABSRon0NWGJv7H_mgocTX-VwroKcqEr5mYyrp2BXcV5MA@mail.gmail.com>
To: Ole Trøan <otroan@employees.org>
Content-Type: multipart/alternative; boundary="e89a8f3b9de9b1ddef04cfc6dfb2"
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 09:09:31 -0000

Ole,

On Sat, Dec 1, 2012 at 4:44 PM, Ole Trøan <otroan@employees.org> wrote:

> Qiong,
>
> > [Qiong] and a sub-mode for "source IPv6 address determiniation", how to
> determine the encapsulated IPv6 source address.
> > 1) algorithmic, LAN prefix + embedded IPv4 address/PSID in Interface
> Identifier (MAP)
> > 2) WAN IPv6 address (DS-Lite, LW46, Public 4over6)
> >
> > Right ?
>
> 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 ?

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

Thanks
Qiong

2) WAN IPv6 address (DS-lite, LW46, Public 4over6)
>
3) Algorithmic End-user IPv6 prefix + Well known interface-id (MAP)
>
>



> cheers,
> Ole
>
>


-- 
==============================================
Qiong Sun
China Telecom Beijing Research Institude


Open source code:
lightweight 4over6: *http://sourceforge.net/projects/laft6/*
PCP-natcoord:* http://sourceforge.net/projects/pcpportsetdemo/ *
===============================================

v2.23.0 | Report a Bug | By Email