[v4tov6transition] Comment on draft-despres-softwire-6a44-01.txt

Dong Zhang <zhangdong_rh@huaweisymantec.com> Fri, 15 October 2010 09:13 UTC

Return-Path: <zhangdong_rh@huaweisymantec.com>
X-Original-To: v4tov6transition@core3.amsl.com
Delivered-To: v4tov6transition@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A4B833A6832; Fri, 15 Oct 2010 02:13:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.857
X-Spam-Level:
X-Spam-Status: No, score=0.857 tagged_above=-999 required=5 tests=[AWL=1.351, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZUjTgn3cJbbr; Fri, 15 Oct 2010 02:13:08 -0700 (PDT)
Received: from mta2.huaweisymantec.com (unknown [218.17.155.15]) by core3.amsl.com (Postfix) with ESMTP id F0FFF3A677C; Fri, 15 Oct 2010 02:13:07 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_lxTIKUIYX3kJrsxY83betg)"
Received: from hstml02-in.huaweisymantec.com ([172.26.3.42]) by hstga02-in.huaweisymantec.com (Sun Java(tm) System Messaging Server 6.3-8.03 (built Apr 24 2009; 32bit)) with ESMTP id <0LAB004DBQZTUS40@hstga02-in.huaweisymantec.com>; Fri, 15 Oct 2010 17:14:18 +0800 (CST)
Received: from z90001956 ([10.27.154.169]) by hstml02-in.huaweisymantec.com (Sun Java(tm) System Messaging Server 6.3-8.03 (built Apr 24 2009; 32bit)) with ESMTPA id <0LAB00E0LQZTCY20@hstml02-in.huaweisymantec.com>; Fri, 15 Oct 2010 17:14:17 +0800 (CST)
Date: Fri, 15 Oct 2010 17:14:19 +0800
From: Dong Zhang <zhangdong_rh@huaweisymantec.com>
To: "remi.despres" <remi.despres@free.fr>
Message-id: <201010151714195590072@huaweisymantec.com>
X-Mailer: Foxmail 6, 10, 201, 20 [cn]
Cc: softwires <softwires@ietf.org>, v4tov6transition <v4tov6transition@ietf.org>
Subject: [v4tov6transition] Comment on draft-despres-softwire-6a44-01.txt
X-BeenThere: v4tov6transition@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <v4tov6transition.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4tov6transition>, <mailto:v4tov6transition-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v4tov6transition>
List-Post: <mailto:v4tov6transition@ietf.org>
List-Help: <mailto:v4tov6transition-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4tov6transition>, <mailto:v4tov6transition-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 09:13:09 -0000

Hi Remi,

The IPv6 host address is directly obtained by an indication message from the 6a44 server. Here is the format of the IPv6 address.
     +-------+-------+-------+-------+-------+-------+-------+-------+
     |  ISP 6a44 prefix (D)       | Customer IPv4 |NAT ext|   Host IPv4      |
     |                                  |   address (N)   |port(Z) |  address (A)    |
     +-------+-------+-------+-------+-------+-------+-------+-------+

According to the draft, N:Z is the address and port used on the CPE NAT44's external side. 
                         _                        .-------.
            Host      /   \       CPE         /          \     6a44 Relay
        +------+  . IP  .    +-----+     .   IPv4    .     +-------+    IPv6
        |6a44-C|--| no |--|NAT44|---| Provider  |--O 6a44-S|-- network
        +------+  . NAT .  +-----+     .  network  .   +-------+
             ^   ^   \ _ /        ^           \          /      |    ^
              |   A                  |            '---.---'       |    |
              |               A:W <-> N:Z                     |    |
              |   |                                                 |    |
              |   |                                                 |    |
              |    <- - - - - IPv6/UDP/IPv4 - - - - - -<      |
              |                                                           |
              |                                                           |
              < D.N.Z.A (/128) - - - - -  - - -IPv6 - - - - < D (/48)

Is the A:W<->N:Z mapping created staticly? Or dynimicly?When the host reqests the IPv6 address to the 6a44 server, the server gives the host IPv6 address and liftime directly.  If  the mapping on the CPE is allocated dynamically, how does the lifetime of the allocated host IPv6 address will be set? I mean this lifetime should longer than the expire time of the mapping on the CPE. It is because if the mapping is deleted first and the host still uses the IPv6 address embeded N:Z. It will arise problem. For instance, the CPE may allocate another port, A:W<->N:Y.

Therefore, there may be two ways to solve this.
a) set the lifetime of the allocated host IPv6 address shorter than the expire time of CPE NAT44. Thus, the host is able to re-request its IPv6 address within the NAT mapping expire time.
b) require the CPE comply with endpoint-independent mapping in RFC4787,RFC5382. But for this behavior, the premise is the host re-send the address request message must use the same source address and port, A:W. Thus, the NAT can provide the same N:Z.

I suppose this should be clarified in 6a44 draft, if I am correct and not missing someting.


Thanks.




2010-10-15 



Dong Zhang