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

Zhen Cao <zehn.cao@gmail.com> Sun, 09 October 2011 11:30 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 0B76221F84C5 for <softwires@ietfa.amsl.com>; Sun, 9 Oct 2011 04:30:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.733
X-Spam-Level:
X-Spam-Status: No, score=-2.733 tagged_above=-999 required=5 tests=[AWL=0.866, 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 FLszA0anUHaL for <softwires@ietfa.amsl.com>; Sun, 9 Oct 2011 04:30:08 -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 8EDAD21F84A9 for <softwires@ietf.org>; Sun, 9 Oct 2011 04:30:08 -0700 (PDT)
Received: by iaby26 with SMTP id y26so7663374iab.31 for <softwires@ietf.org>; Sun, 09 Oct 2011 04:30:08 -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=F/JHkxnLjSZ49QVg9SfxazYifdq7vM+NH16qnMvYTWg=; b=YLG9eGEAJ1JYdaYv8t25ZRA7g+hWNySEc0XLARQdZ4T9yMbzzGqWbJd4Dsv4jU+1pG MeBzu/oObO4UZRq+zuQu0F03n0L2YaD7GGfTCCTOEjTklyDPGABXz/MetHCu40crQuVN 1sKL056KfItpTurpRP5ZaeKDC7BN7a6GcDKYw=
MIME-Version: 1.0
Received: by 10.42.155.202 with SMTP id v10mr8974638icw.36.1318159808200; Sun, 09 Oct 2011 04:30:08 -0700 (PDT)
Received: by 10.43.52.196 with HTTP; Sun, 9 Oct 2011 04:30:08 -0700 (PDT)
In-Reply-To: <CAH3bfAA3ttXJ88kLQuNi8w1vT-Dpu5Pdv4S+O-=VHUwFGwAtHQ@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> <CAH3bfAA3ttXJ88kLQuNi8w1vT-Dpu5Pdv4S+O-=VHUwFGwAtHQ@mail.gmail.com>
Date: Sun, 09 Oct 2011 19:30:08 +0800
Message-ID: <CAProHARGzsxK9rUtS3p5Rr04pfkL=A4XO-AgQsz3T=smEsGBDg@mail.gmail.com>
From: Zhen Cao <zehn.cao@gmail.com>
To: Qiong <bingxuere@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
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:30:09 -0000

On Sun, Oct 9, 2011 at 11:57 AM, Qiong <bingxuere@gmail.com> wrote:
> Hi, Gang,
> Please see my reply inline.
>
> On Sun, Oct 9, 2011 at 11:14 AM, GangChen <phdgang@gmail.com> wrote:
>>
>> 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         |
>> +----------+-----------------+--------------------+
>>
>>
> In case you need to embed the full IPv4 address for destination address in
> CE-BR, why not define a unified address format for CE-CE model. I think it
> would be easier to implement and easier to achieve further traffic
> identification in the same way.
> Best wishes
> Qiong

I think this is a different story. For the CE-BR communication, since
the destination node is not within the domain, we can't and do not
need to use the same mapping algorithm as well as the address format
for the destination address part.  The mapping only applies to the
source address part. That's what's discussed during the interim.

-- 
Best regards,
Zhen