Re: [v6ops] Fwd: New Version Notification for draft-lopez-v6ops-dc-ipv6-00.txt
Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 07 March 2012 19:15 UTC
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F97511E8086 for <v6ops@ietfa.amsl.com>; Wed, 7 Mar 2012 11:15:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.893
X-Spam-Level:
X-Spam-Status: No, score=-102.893 tagged_above=-999 required=5 tests=[AWL=-0.494, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 ZAFEb1V4-8sI for <v6ops@ietfa.amsl.com>; Wed, 7 Mar 2012 11:15:11 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9ACCF11E807F for <v6ops@ietf.org>; Wed, 7 Mar 2012 11:15:11 -0800 (PST)
Received: by werb10 with SMTP id b10so5229569wer.31 for <v6ops@ietf.org>; Wed, 07 Mar 2012 11:15:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=uGIHmFQe9vM/ehS17n7/O6113CENBuUph9acEVyV3Uw=; b=gcjXZCeXUCf8DKr0DuNWZW4vykmOvHK1IB0zipiRJ4TEdp+99v1SZEWahAxWA5xQn9 7nFmqn4hsRNoAiziCiR8WzktggXXrWitPnaO88d8gtWf2GJ3gEQFyiJmVza8LHpnZrbT 8i4gHVhPvbgFTktUcygA8M9hr0x4oxrVsoDLme1Qy/r5Fgx4PVGqRFwF7zXiiOXd32nA uSTW1grTcBI38XL38Xr5vNbR5CuLtwMbPbNaA7jgXADDDWo8QkyL8PJ5OyyuXffvEXQK zAeltqQp3LIAxkfuNhFlaKjRf/JuSOBCdzg8eg34Xe+mU3mAvKOpJ51tDPKuOZ/HcERv mg+Q==
Received: by 10.180.104.137 with SMTP id ge9mr6242351wib.20.1331147710705; Wed, 07 Mar 2012 11:15:10 -0800 (PST)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id fw5sm37914761wib.0.2012.03.07.11.15.06 (version=SSLv3 cipher=OTHER); Wed, 07 Mar 2012 11:15:09 -0800 (PST)
Message-ID: <4F57B3AB.4070707@gmail.com>
Date: Thu, 08 Mar 2012 08:14:51 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Washam Fan <washam.fan@gmail.com>
References: <20120303200905.31106.67929.idtracker@ietfa.amsl.com> <4F529C37.9090900@bogus.com> <4F52AE79.9020504@si6networks.com> <2D31D894-5885-4BDB-B082-036517FDE0BE@huawei.com> <CAAuHL_CxV1Lgz75BGtHaEMu7LNnfRfMG3QtTS0uh6VWgkXt9Sw@mail.gmail.com>
In-Reply-To: <CAAuHL_CxV1Lgz75BGtHaEMu7LNnfRfMG3QtTS0uh6VWgkXt9Sw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] Fwd: New Version Notification for draft-lopez-v6ops-dc-ipv6-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 07 Mar 2012 19:15:12 -0000
Hi Washam, > Finally, I feel it would be some overlap between this draft and > draft-carpenter-v6ops-icp-guidance. I think the goals are rather different. -icp-guidance is aimed at describing a process and a range of options for ICPs. -dc-ipv6 seems to be describing quite specific scenarios. Also data centres are not the same thing as ICPs. There's also overlap with draft-chkpvc-enterprise-incremental-ipv6, although that is aimed at any kind of enterprise. The three documents should aim at being consistent with each other, but I think they have different audiences. I would definitely be against combining them, because that would take for ever. Regards Brian On 2012-03-08 02:56, Washam Fan wrote: > Hi, > > I don't think the problem the draft is trying to address is clear. > Deduced from the solution, It seems to me the problem is to address > the IPv6 Internet accessing IPv4 network scenario. The solution seems > to me, is a variant of stateful NAT64. Compared to stateful NAT64, the > proposal is doing address translation whileas the statefull NAT64 is > doing address+port translation. And I don't know why the proposal is > integral to LB. It could have been an individual module even it could > be co-located with LB. > > Finally, I feel it would be some overlap between this draft and > draft-carpenter-v6ops-icp-guidance. > > Thanks, > washam > > 2012/3/7 Tina TSOU <Tina.Tsou.Zouting@huawei.com>: >> For your comments. >> http://datatracker.ietf.org/doc/draft-lopez-v6ops-dc-ipv6/ >> >> Sent from my iPad >> >> Begin forwarded message: >> >> From: <internet-drafts@ietf.org> >> Date: March 5, 2012 5:09:49 PM PST >> To: <tina.tsou.zouting@huawei.com> >> Cc: <cathy.zhou@huawei.com>, <diego@tid.es>, <18918588897@189.cn> >> Subject: New Version Notification for draft-lopez-v6ops-dc-ipv6-00.txt >> >> A new version of I-D, draft-lopez-v6ops-dc-ipv6-00.txt has been successfully >> submitted by Tina Tsou and posted to the IETF repository. >> >> Filename: draft-lopez-v6ops-dc-ipv6 >> Revision: 00 >> Title: DC Migration to IPv6 >> Creation date: 2012-03-05 >> WG ID: Individual Submission >> Number of pages: 10 >> >> Abstract: >> This document describes the issues, possible solutions, and >> opportunities in Data Center (DC) migration from IPv4 to IPv6. It >> focuses on the DC infrastructure itself, its operation, and the >> aspects related to DC interconnection through IPv6. It does not >> consider the particular mechanisms for making Internet services >> provided by applications hosted in the DC available through IPv6 >> beyond the specific aspects related to how their deployed on the DC >> infrastructure. >> >> Apart from facilitating the migration procedure itself, the >> mechanisms outlined here are intended to make this migration as >> transparent as possible (if not completely transparent) to >> applications and services running on the DC infrastructure, as well >> as to take advantage of IPv6 features to simplify DC operations, >> internally and across the Internet. >> >> >> >> >> The IETF Secretariat >> >> >> _______________________________________________ >> v6ops mailing list >> v6ops@ietf.org >> https://www.ietf.org/mailman/listinfo/v6ops >> > _______________________________________________ > v6ops mailing list > v6ops@ietf.org > https://www.ietf.org/mailman/listinfo/v6ops >
- [v6ops] Fwd: ID Tracker State Update Notice: <dra… Joel jaeggli
- Re: [v6ops] Fwd: ID Tracker State Update Notice: … Fernando Gont
- Re: [v6ops] Fwd: ID Tracker State Update Notice: … Joel jaeggli
- Re: [v6ops] Fwd: ID Tracker State Update Notice: … Fernando Gont
- [v6ops] Fwd: New Version Notification for draft-l… Tina TSOU
- Re: [v6ops] Fwd: New Version Notification for dra… Washam Fan
- Re: [v6ops] Fwd: New Version Notification for dra… Brian E Carpenter
- Re: [v6ops] Fwd: New Version Notification for dra… Washam Fan
- Re: [v6ops] Fwd: New Version Notification for dra… Cathy Zhou(Qian)
- Re: [v6ops] Fwd: New Version Notification for dra… Washam Fan