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

Maoke <fibrib@gmail.com> Sun, 09 October 2011 04:28 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 CB74921F8BC3 for <softwires@ietfa.amsl.com>; Sat, 8 Oct 2011 21:28:14 -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 Nmx8p070DTSf for <softwires@ietfa.amsl.com>; Sat, 8 Oct 2011 21:28:14 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 18D3521F8B5D for <softwires@ietf.org>; Sat, 8 Oct 2011 21:28:14 -0700 (PDT)
Received: by qadb12 with SMTP id b12so4465150qad.31 for <softwires@ietf.org>; Sat, 08 Oct 2011 21:28:13 -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=IJpDbTbm27TvcZkHHqoThLe7heUWEy2bEhVjBxqfd6Q=; b=UfMvXTg/wBV9WxPjQJ98l3F8VWp5q170eEENadiqaINd9gCq/8XNfMnXVSGesRC5yN sLD+iLP1Brr8QM2HmbOicv/lx6FbrtzpTRP/IMLSAkYIDsWO7vUKbMT8jGiyG6jiJXue c8XWZ6QjiFt4BLpg6OJY6SW8FAW7Nadi+q8pA=
MIME-Version: 1.0
Received: by 10.229.80.16 with SMTP id r16mr2763342qck.107.1318134493523; Sat, 08 Oct 2011 21:28:13 -0700 (PDT)
Received: by 10.229.40.197 with HTTP; Sat, 8 Oct 2011 21:28: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 13:28:13 +0900
Message-ID: <CAFUBMqUdZ8dstRYdMjTi183737ms=na2OWpRSF6phqOK0FN9iA@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: GangChen <phdgang@gmail.com>
Content-Type: multipart/alternative; boundary="0016364ee76440b0d004aed61a94"
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:28:14 -0000

hi Gang,

thanks for the reply.

2011/10/9 GangChen <phdgang@gmail.com>

> >> Yes, in padding case.
> >>
> >>
> > what do you mean with the "yes"? do you mean having a short-enough
> Rule-IPv6
> > is a prerequisite for deploying 4rd-pd?
> >
> > for example, a small ISP has its Rule IPv4 prefix such as 10/8, while its
> > total IPv6 block is a /48 or a /56 prefix only. the ISP is deploying
> > stateless transition, possibly 4rd-pd. is such an ISP surely able to pad
> > necessary part of IPv4 address in the first 64 bits?
>
> I guess I have already put some comments on that. Please see below.
>
>
do you mean you *require" every ISP surely having IPv6 prefix shorter than,
e.g., /32? may i beg you answer this question without equivocation. :)
thanks!


> > i don't think all current practices are "trying to encode the information
> in
> > the first 64bits". to my humble understanding, at least divi-pd encodes
> the
> > IPv4 full address information, which identifies a specific user, not in
> the
> > first 64 bits.
>
> Thanks for the clarification. That is why you propose to insert full
> IPv4 address?
>
>
well, i didn't propose anything new. some cases need full IPv4 addresses
while these cases are included in our discussion on the unified address
mapping.


> > in your proposal draft-chen-softwire-4v6-pd-00, you have
> >
> >   Delegated IPv6 prefix = IPv6 prefix + Add set + Port set
> >
> > where your Add-set is (32 - IPv4_pref_len) long, right? if the
> IPv4_pref_len
> > = 8 while the IPv6_prefix_len = 48, can your first 64bits identify a
> user?
> >
>

on the other hand, may you also answer this question?

thanks and regards,
maoke