[v6ops] Revised texts for ULA #3 NPTv6 Use Case
"Liubing (Leo)" <leo.liubing@huawei.com> Tue, 03 June 2014 03:38 UTC
Return-Path: <leo.liubing@huawei.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 415A81A0073 for <v6ops@ietfa.amsl.com>; Mon, 2 Jun 2014 20:38:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.851
X-Spam-Level:
X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P-4xoL6FfFuW for <v6ops@ietfa.amsl.com>; Mon, 2 Jun 2014 20:38:35 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05B261A0074 for <v6ops@ietf.org>; Mon, 2 Jun 2014 20:38:29 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BHT78392; Tue, 03 Jun 2014 03:38:23 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 3 Jun 2014 04:37:39 +0100
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 3 Jun 2014 04:38:22 +0100
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.207]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Tue, 3 Jun 2014 11:38:18 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: v6ops WG <v6ops@ietf.org>
Thread-Topic: Revised texts for ULA #3 NPTv6 Use Case
Thread-Index: AQHPft1CJ+GB1E45A0C5tdmrqNI6GQ==
Date: Tue, 03 Jun 2014 03:38:18 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D8B99F5@nkgeml506-mbx.china.huawei.com>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D8B7847@nkgeml506-mbx.china.huawei.com> <7783E833-2188-4993-ADCC-38C67A09553D@delong.com> <B05E3E39-3587-4A37-80B0-56907B1894B2@ecs.soton.ac.uk> <CAKD1Yr0o0BL5Km2pQN4NdeYjKVfSpA9VGXvjaNTMwOiUHj4f7Q@mail.gmail.com> <EMEW3|41d343f68fc77dbc013010afcdeef82bq50Eju03tjc|ecs.soton.ac.uk|B05E3E39-3587-4A37-80B0-56907B1894B2@ecs.soton.ac.uk> <CAKD1Yr1Gon71LA50EXvNQGBmD6ox1dFJH52bre2-ueyVeETxEA@mail.gmail.com>
In-Reply-To: <CAKD1Yr1Gon71LA50EXvNQGBmD6ox1dFJH52bre2-ueyVeETxEA@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.98.132]
Content-Type: multipart/alternative; boundary="_000_8AE0F17B87264D4CAC7DE0AA6C406F453D8B99F5nkgeml506mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/Iv81w75A_OH45rUeZcVgELX4F_w
Cc: "v6ops-chairs@tools.ietf.org" <v6ops-chairs@tools.ietf.org>
Subject: [v6ops] Revised texts for ULA #3 NPTv6 Use Case
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jun 2014 03:38:37 -0000
Hi Dear all, Based on recent discussion, I propose some revised texts as the following. Please comment to see whether we can achieve consensus on this issue. Many thanks! Revised texts in Section 3.2.1: “o Using Network Prefix Translation Network Prefix Translation (NPTv6) [RFC6296] is an experimental specification that provides a stateless one to one mapping between internal addresses and external addresses. [RFC6296] considers translating ULA prefixes into GUA prefixes as a use case. Although NPTv6 is not exactly the same with the traditional stateful NAT/NAPT (which is discouraged in [RFC5902]), it also introduces some similar additional complexity on many applications, which might cause applications break. So in general, this document doesn’t encourage to use ULA+NPTv6 (however, some operational considerations are provided below for the ones who insist to use ULA+NPTv6 for some reason). This document considers ULA+GUA as a better approach to connect to the global network when ULAs are expected to be retained. ULA+GUA is discussed in detail in Section 3.2.2 below.” Original texts: “o Using Network Prefix Translation Network Prefix Translation (NPTv6) [RFC6296] is an experimental specification that provides a stateless one to one mapping between internal addresses and external addresses. In some very constrained situations(for example, in the sensors), the network needs ULA as the on-demand and stable addressing which doesn't need much code to support address assignment mechanisms like DHCP or full ND (Note: surely it needs SLAAC). If the network also needs to connect to the outside, then there can be an NPTv6 gateway which is not subject to extreme resource constraints. Especially when a lightweight isolated network needs to add Internet connectivity, this is quite a straightforward and efficient way. This document does not intend to encourage the ULA binding with NPTv6 model, since in [RFC5902] the IAB had already gave opinions on IPv6 NAT; but this document considers it as an effective approach in some specific situations as described above.” ________________________________
- [v6ops] ULA #3 NPTv6 Use Case Liubing (Leo)
- Re: [v6ops] ULA #3 NPTv6 Use Case Lorenzo Colitti
- Re: [v6ops] ULA #3 NPTv6 Use Case Liubing (Leo)
- Re: [v6ops] ULA #3 NPTv6 Use Case Ted Lemon
- Re: [v6ops] ULA #3 NPTv6 Use Case Ted Lemon
- Re: [v6ops] ULA #3 NPTv6 Use Case Lee Howard
- Re: [v6ops] ULA #3 NPTv6 Use Case Ted Lemon
- Re: [v6ops] ULA #3 NPTv6 Use Case Brian E Carpenter
- Re: [v6ops] ULA #3 NPTv6 Use Case Lorenzo Colitti
- Re: [v6ops] ULA #3 NPTv6 Use Case Liubing (Leo)
- Re: [v6ops] ULA #3 NPTv6 Use Case Lorenzo Colitti
- Re: [v6ops] ULA #3 NPTv6 Use Case Owen DeLong
- Re: [v6ops] ULA #3 NPTv6 Use Case Lorenzo Colitti
- Re: [v6ops] ULA #3 NPTv6 Use Case Tim Chown
- Re: [v6ops] ULA #3 NPTv6 Use Case Lorenzo Colitti
- [v6ops] Revised texts for ULA #3 NPTv6 Use Case Liubing (Leo)
- Re: [v6ops] Revised texts for ULA #3 NPTv6 Use Ca… Owen DeLong
- Re: [v6ops] {Disarmed} Revised texts for ULA #3 N… Tim Chown
- Re: [v6ops] {Disarmed} Revised texts for ULA #3 N… Liubing (Leo)