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

Congxiao Bao <cx.cernet@gmail.com> Thu, 06 October 2011 13:54 UTC

Return-Path: <cx.cernet@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 0DB1621F8B44 for <softwires@ietfa.amsl.com>; Thu, 6 Oct 2011 06:54:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.053
X-Spam-Level:
X-Spam-Status: No, score=-3.053 tagged_above=-999 required=5 tests=[AWL=-0.055, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_74=0.6, 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 cso6YpyBNrnj for <softwires@ietfa.amsl.com>; Thu, 6 Oct 2011 06:54:38 -0700 (PDT)
Received: from mail-pz0-f50.google.com (mail-pz0-f50.google.com [209.85.210.50]) by ietfa.amsl.com (Postfix) with ESMTP id 89EBF21F8AF7 for <softwires@ietf.org>; Thu, 6 Oct 2011 06:54:38 -0700 (PDT)
Received: by pzk37 with SMTP id 37so7074452pzk.9 for <softwires@ietf.org>; Thu, 06 Oct 2011 06:57:49 -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=r+Xs4d0zKusXHBZy9t2rpDan/cdiXKgFC2ENikSlRBY=; b=uSu4mYEadlZmiVebGF+BW/NZ7J05p7Q6khEirvxFMcjZfcFEtCPSmznL6iWSWYPsBp z9OSP0Xc0BJhv2WnCRfbILAUIifmAKwurWrsbJYU+WcsuvQ+QSLgLzUCgbx5c1HQh82N a8/05sHb07WsEBsWck2IlZ8bWvgY7XDjDZt5c=
MIME-Version: 1.0
Received: by 10.68.17.193 with SMTP id q1mr5837204pbd.98.1317909469310; Thu, 06 Oct 2011 06:57:49 -0700 (PDT)
Received: by 10.142.162.1 with HTTP; Thu, 6 Oct 2011 06:57:49 -0700 (PDT)
In-Reply-To: <3C29CE19-E03A-4AC5-959A-7931FE5B9B04@employees.org>
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> <3C29CE19-E03A-4AC5-959A-7931FE5B9B04@employees.org>
Date: Thu, 06 Oct 2011 21:57:49 +0800
Message-ID: <CABv173WfM+93wRj+k1JSRdarCwXOr6q-kRrT=8p=dewDn3jn1g@mail.gmail.com>
From: Congxiao Bao <cx.cernet@gmail.com>
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary="bcaec520ea43c3b29f04aea1b57e"
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: Thu, 06 Oct 2011 13:54:39 -0000

2011/10/6 Ole Troan <otroan@employees.org>

> > i couldn't understand why we "don't see such limitation in 4v6
> translation". 4via6 translate the private ipv4 address with 4rd mapping rule
> while the public ipv4 address with RFC6052 algorithm, right? can the both
> case work fine if an ISP can only get a fairly long IPv6 prefix, like /40 or
> even longer?
> >
> > Yes, if ISP has /32 IPv6 address, then how to embed 32 bits IPv4 address
> and PSID in the first 64 bits?
>
> only part of the IPv4 address would be embedded into the first 64 bits (not
> that I think that boundary should be "hard").
> e.g. if the SP has the prefix 10/8. the user the address 10.1.2.3. then
> only "1.2.3" would be embedded in the address.
> just like what's done for 6rd.
>


Thanks, Ole. That’s the point! In this case , you can only have part of the
IPv4 address embedded in the first 64 bits. This embedding does work for
encapsulation or tunneling, but can NOT work for stateless double
translation, which requires the whole IPv4 address+PSID embeded for any IPv6
prefix length.



Best,



Congxiao

>
> cheers,
> Ole