Re: [Softwires] 4rd Address Mapping - version-01

Maoke <fibrib@gmail.com> Tue, 18 October 2011 02: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 7820F1F0C53 for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 19:28:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.292
X-Spam-Level:
X-Spam-Status: No, score=-2.292 tagged_above=-999 required=5 tests=[AWL=-0.778, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, J_CHICKENPOX_34=0.6, J_CHICKENPOX_42=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 XKBRQ-9bOkyK for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 19:28:22 -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 AB4D41F0C43 for <softwires@ietf.org>; Mon, 17 Oct 2011 19:28:22 -0700 (PDT)
Received: by qadb12 with SMTP id b12so73550qad.31 for <softwires@ietf.org>; Mon, 17 Oct 2011 19:28:21 -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=MjQRN7w4Jx0Ohb1MF8s6ljvuL39W3hlJ+SK9D4Y2CxY=; b=sTey1d5yURVAyJ6gQe/X3z557i/BmdB43ysFk0pZWhKk+zyowy5wrOsgYZF0yiYz3I kIqYXdCdsTVmdA1p6DtE25d0rB6AzooH5+rssX3iD2N12r1IQQRF8CTP7Qa3OM8DUg6H 5pYlmi60yOVo0XN8dUq5rEMBRHcbR0HvkenSA=
MIME-Version: 1.0
Received: by 10.229.80.16 with SMTP id r16mr84146qck.107.1318904901081; Mon, 17 Oct 2011 19:28:21 -0700 (PDT)
Received: by 10.229.214.212 with HTTP; Mon, 17 Oct 2011 19:28:20 -0700 (PDT)
In-Reply-To: <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com> <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local>
Date: Tue, 18 Oct 2011 11:28:20 +0900
Message-ID: <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: c-sun@bb.softbank.co.jp
Content-Type: multipart/alternative; boundary="0016364ee7641f1cc104af897ac2"
Cc: softwires@ietf.org
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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: Tue, 18 Oct 2011 02:28:23 -0000

hi Chunfa and Jacni,

thanks a lot for the corrections and clarifications. :)

2011/10/17 <c-sun@bb.softbank.co.jp>

>  I guess the second delegated prefix should be 2001:db8:1876:5400::/53
>
>    I guess the second delegated prefix should be 2011:db8:c3b2:a000::/53.
> Because the CE3 Rule IPv6 Prefix length is not mulitipe of 4 bits,it need
> calculate using Binary as follows.
>
>                                  v(/29)
>  --elipsis(0x2001 0db)--1000
>  (2011:db8::/29)
>  --elipsis(0x4020)------    000 1100 0011 1011 0
> (64.32.24.118)
>                                                                    010 1010
> 0 (PSID 0x54)
> --------------------------------------------------------------------------
> CE3 IPv6 prefix: 2001:db8:c3b2:a000::/53
>
> If the CE3 IPv4 address is 64.32.48.236, CE3 PSID is 0xa8, calculate as
> follows,
>                                  v(/29)
>  --elipsis(0x2001 0db)--1000
>  (2011:db8::/29)
>  --elipsis(0x4020)------    001 1000 0111 0110 0
> (64.32.48.236)
>                                                                    101 0100
> 0 (PSID 0xa8)
> --------------------------------------------------------------------------
> the CE3 IPv6 prefix is 2001:db9:8765:4000::/53
>
> I think this  should be not gonna happen, since the IPv6 address planing
> must be done natively
> considering nothing about the IPv4 address. As exclusiveness, each CE has
> unique CE IPv6 Prefix.
>
> As described in the example Maoke given, since "Rule IPv6 Prefix B" is
> contained in the "Rule IPv6 Prefix A",
> if the IPv6 addresses under Rule IPv6 Prefix A and the IPv6 address under
> Rule IPv6 prefix B are assigned independently
> and have any consideration each other, same CE IPv6 prefix assigning to
> different CEs may be happen. I think this MUST be
>  avoided when designing the mapping rules or setting the IPv6 assigning
> way(such as DHCPv6 etc.).
>
>
the consensus is keeping the exclusiveness of IPv4 address blocks in IPv6.
therefore, i understand the logic of address planning for CEs in 4rd could
be the following 4 steps:

1) list all mutually exclusive IPv4 networks to be involved in the residual
deployment, i.e., Rule IPv4 prefixes;
2) calculate IPv6 prefix length for each Rule IPv4 prefix, according to the
length of the prefix and the requirement like the PSID length and the CE
prefix length;
3) allocate the IPv6 address space into exclusive blocks, i.e.
rule_IPv6_prefixes, according to the prefix length requirements in 2), and
get the mapping rules;
4) assigning IPv6 address in each block for the CE.

am i right?

cheers,
maoke


> Cheers
>
> Chunfa
>
>
>
>>
>