IETF Logo Mail Archive

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

Maoke <fibrib@gmail.com> Sun, 09 October 2011 04:31 UTC

Return-Path: <fibrib@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 471F121F8BC3 for <softwires@ietfa.amsl.com>; Sat, 8 Oct 2011 21:31:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level:
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, 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 EcQqhkjvUPWz for <softwires@ietfa.amsl.com>; Sat, 8 Oct 2011 21:31:07 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id B247921F8B5D for <softwires@ietf.org>; Sat, 8 Oct 2011 21:31:07 -0700 (PDT)
Received: by qyk32 with SMTP id 32so1304719qyk.10 for <softwires@ietf.org>; Sat, 08 Oct 2011 21:31:07 -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; bh=5tomrwVDIOAPcwZrHmqYDXXC9FSV6vyx/Bfo2uQfkK8=; b=tBRZVy+JUg/BOXroLiOWz2IPRoPm353WhMo1AR+6oM4UVdcbSmTJOi3mcWbkh3TbLZ C/QsSCgFGQZ6FFN2mDv6VorAmwdUhtICrZg9/WxH9YZBnDi8EBRwy75Ia32dz+5mPCLJ irO9KfGPmReh19Yk26qPBJC9q/C7NH5EmwPsI=
MIME-Version: 1.0
Received: by 10.229.62.195 with SMTP id y3mr2780593qch.31.1318134667177; Sat, 08 Oct 2011 21:31:07 -0700 (PDT)
Received: by 10.229.40.197 with HTTP; Sat, 8 Oct 2011 21:31:06 -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 13:31:06 +0900
Message-ID: <CAFUBMqVNScO3RnhabHcLVAHwgdRNFOEZ2=4Dfy534mzfJ=ud5g@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: Qiong <bingxuere@gmail.com>
Content-Type: multipart/alternative; boundary="0016e64b1d569a70fd04aed624f0"
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 04:31:08 -0000

hi Qiong,

2011/10/9 Qiong <bingxuere@gmail.com>

> 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.
>
>
agree.

best,
maoke

v2.23.0 | Report a Bug | By Email