Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation

Zhen Cao <zehn.cao@gmail.com> Sun, 09 October 2011 11:25 UTC

Return-Path: <zehn.cao@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 6E76D21F8492 for <softwires@ietfa.amsl.com>; Sun, 9 Oct 2011 04:25:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level:
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 GeWX7rqtJ4ZC for <softwires@ietfa.amsl.com>; Sun, 9 Oct 2011 04:25:14 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id C6A7621F8485 for <softwires@ietf.org>; Sun, 9 Oct 2011 04:25:14 -0700 (PDT)
Received: by iaby26 with SMTP id y26so7658953iab.31 for <softwires@ietf.org>; Sun, 09 Oct 2011 04:25:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=0Fyjgz9d7UKqXvFmjoCg8mbRQ95lpGDXKY91ryRTlws=; b=vJuJd6w3PC4AeSUFVtRstSFY5pFdWo6Xo4HyntT7SJ9RDSzXdx45dZWJRz+ZSJgkTM sHyT8gPVkxjdeD+tGSXyiCdt8+EU7YrDcIB9iIFyRlvHkgjtoL1VHnI1pkGV8bDGvE22 gsSclGYokQuqVESvsDGx/7W1AJT0xtCxwKvvY=
MIME-Version: 1.0
Received: by 10.42.159.1 with SMTP id j1mr8975164icx.20.1318159513675; Sun, 09 Oct 2011 04:25:13 -0700 (PDT)
Received: by 10.43.52.196 with HTTP; Sun, 9 Oct 2011 04:25:13 -0700 (PDT)
In-Reply-To: <CAM+vMET5J4XVbrKR9zdHXN8LqhBYJ=psYMoSXBNFzwZVUkE0YA@mail.gmail.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com> <CAM+vMETVf763VWLLCHy072NcHTi0v=cMOyjQ+u2HHa5SwiFF_A@mail.gmail.com> <CAFUBMqX01bLG4Rkn=zvT9o4Q4UF3sGCqEGd7AD0aW-ZkC9AS6w@mail.gmail.com> <CAM+vMET5J4XVbrKR9zdHXN8LqhBYJ=psYMoSXBNFzwZVUkE0YA@mail.gmail.com>
Date: Sun, 09 Oct 2011 19:25:13 +0800
Message-ID: <CAProHAR4_odXQAX2X90-6BhpD5YhDzOCpnPVLV4QGhb88nJOcQ@mail.gmail.com>
From: Zhen Cao <zehn.cao@gmail.com>
To: GangChen <phdgang@gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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: Sun, 09 Oct 2011 11:25:15 -0000

On Sun, Oct 9, 2011 at 11:14 AM, GangChen <phdgang@gmail.com> wrote:
> Hello Maoke,
>
> Please see my reply inline.
>
> 2011/10/8, Maoke <fibrib@gmail.com>:
>>> > Yes, if ISP has /32 IPv6 address, then how to embed 32 bits IPv4 address
>>> and
>>> > PSID in the first 64 bits?
>>> >
>>> 4v6 translation doesn’t need to embed whole 32 bits IPv4 address
>>> according to the algorithm. Please take look EA-bits usage in
>>> http://tools.ietf.org/html/draft-murakami-softwire-4rd-01 for more
>>> details
>>>
>>>
>> i suppose Ole and Congxiao have clarified this point, right? for the double
>> translation, full ipv4 address is needed.
>
> As Ole said, "for the outside domain traffic" (Actually, I never argue
> that point for that case)
> Thereby, it's worth to be clarified whether need encoding whole IPv4
> address, as the below table
>
> +----------+-----------------+--------------------+
> |          |source address   | destination address|
> +----------+-----------------+--------------------+
> |  CE-CE   |      N/A        |        N/A         |
> +----------+-----------------+--------------------+
> |  CE-BR   |      N/A        |        Yes         |
> +----------+-----------------+--------------------+
>

I like this matrix, very clear for discussion and should serve as the
basis for any arguments regarding the reasons for our choice.

-- 
Best regards,
Zhen