Re: [armd] Fwd: I-D Action: draft-sakura-6rd-datacenter-03.txt

Shishio Tsuchiya <shtsuchi@cisco.com> Mon, 12 March 2012 17:31 UTC

Return-Path: <shtsuchi@cisco.com>
X-Original-To: armd@ietfa.amsl.com
Delivered-To: armd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35A5421F8924; Mon, 12 Mar 2012 10:31:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.899
X-Spam-Level:
X-Spam-Status: No, score=-3.899 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_26=0.6, J_CHICKENPOX_42=0.6, J_CHICKENPOX_53=0.6, J_CHICKENPOX_54=0.6, J_CHICKENPOX_55=0.6, J_CHICKENPOX_56=0.6, J_CHICKENPOX_64=0.6, J_CHICKENPOX_84=0.6, RCVD_IN_DNSWL_HI=-8]
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 4O-NTgwcUfTe; Mon, 12 Mar 2012 10:31:45 -0700 (PDT)
Received: from bgl-iport-1.cisco.com (bgl-iport-1.cisco.com [72.163.197.25]) by ietfa.amsl.com (Postfix) with ESMTP id 5F8C821F891D; Mon, 12 Mar 2012 10:31:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shtsuchi@cisco.com; l=4803; q=dns/txt; s=iport; t=1331573505; x=1332783105; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=XtnXJw8fKYgm1f8SQYVNshK1tAbAo8x/3LVmwOJkZSY=; b=HJfxkMyQCSUviGXLb7ZNUuoo00fCQFkXmmu0jfMmxFeNvH9FCc186Q6W NsqWtiJAVkkw1hanazMQHe2v3ID1wsdyyuFC5Ewg7CvqdAN0dt9xJ361j +9RC6/+weOcFCJh3Q3Kd12NVhHLUDbAVXNZQPtDKpj2tKSgKhHSD6F9Ah s=;
X-IronPort-AV: E=Sophos;i="4.73,572,1325462400"; d="scan'208";a="7702899"
Received: from vla196-nat.cisco.com (HELO bgl-core-4.cisco.com) ([72.163.197.24]) by bgl-iport-1.cisco.com with ESMTP; 12 Mar 2012 17:31:43 +0000
Received: from [10.71.44.89] (tky-shtsuchi-8918.cisco.com [10.71.44.89]) by bgl-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q2CHVVnU032266; Mon, 12 Mar 2012 17:31:32 GMT
Message-ID: <4F5E32F2.50302@cisco.com>
Date: Tue, 13 Mar 2012 02:31:30 +0900
From: Shishio Tsuchiya <shtsuchi@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: v6ops@ietf.org
References: <20111114092126.3494.19513.idtracker@ietfa.amsl.com><4F320549.20100@cisco.com> <CAP_bo1aZ8BQ-pC5T2FH9QVwPLSbzQaVk9eRSDpRLr6ierE1cpg@mail.gmail.com> <4F34A0AD.4040300@cisco.com>
In-Reply-To: <4F34A0AD.4040300@cisco.com>
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Cc: softwires@ietf.org, draft-sakura-6rd-datacenter@tools.ietf.org, armd@ietf.org
Subject: Re: [armd] Fwd: I-D Action: draft-sakura-6rd-datacenter-03.txt
X-BeenThere: armd@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion of issues associated with large amount of virtual machines being introduced in data centers and virtual hosts introduced by Cloud Computing." <armd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/armd>, <mailto:armd-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/armd>
List-Post: <mailto:armd@ietf.org>
List-Help: <mailto:armd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/armd>, <mailto:armd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Mar 2012 17:31:50 -0000

v6ops
I published 04,add some comments.
4.2.  Configuration
4.4.  Traffic Pattern
http://tools.ietf.org/html/draft-sakura-6rd-datacenter-04

I believe native IPv6 data center is ideal,but the operators sometimes can not reach the ideal.
Server based 6rd would be useful to  provide IPv6 to customer as solution.
Could you share presentation time slot in IETF83?

Regards,
-Shishio

(2012/02/10 13:44), Shishio Tsuchiya wrote:
> Linda
> Thanks for comments.
> 
> (2012/02/10 8:26), Linda Dunbar wrote:
>> Shishio,
>>
>> Thank you very much for sharing the v6 deployment in data center.
>>
>> I am not an IPv6 expert. So I have a simple question: when you say "server-based 6rd", do you mean that server does the IPv4 encapsulation?
> 
> Yes.
> 6rd is IPv6 over IPv4 tunnel technology.
> So backbone operator does not need to care to IPv6 on the core.
> Additionally 6rd has stateless feature.
> Once the operator has placed/configured 6rd BR on the exit point to the IPv6 internet,does not need additional operation to add 6rd CE(server based 6rd).
> And if the server would like to go  to the IPv6 internet,then IPv4 packets will through 6rd BR and de-capsulate.
> If the server would like to communicate other 6rd server within the data center,then IPv4 packets will reach 6rd server directly and de-capsulate.
> 
>>
>>
>> Does your data center allow hosts/servers under one IPv6 subnet (e.g. /64) to be placed under different server racks?
> 
> In Sakura internet 6rd cases,each of 6rd server has one 6rd delegate prefix(/64).
> http://tools.ietf.org/html/draft-sakura-6rd-datacenter-03#section-4.1
> 
> The 6rd delegate prefix calculates from Sakura's IPv6 prefix(/32) and IPv4 address.
> Sakura has the scalability problem which is same as ARMD draft.
> http://tools.ietf.org/html/draft-ietf-armd-problem-statement-00
> 
> They also had to update switches to resolve security issue(Rogue RA).
> http://tools.ietf.org/html/rfc6104
> 
> They selected "server-based 6rd" as the solution to avoid scalability and security problem.
> 
> Regards,
> -Shishio
> 
> 
>>
>> Thanks, Linda Dunbar
>>
>>
>>
>>
>>
>> On Tue, Feb 7, 2012 at 11:16 PM, Shishio Tsuchiya<shtsuchi@cisco.com<mailto:shtsuchi@cisco.com>>  wrote:
>>
>>      v6ops and ARMD
>>      Sakura internet are providing IPv6 service without scalability impact to core network equipment to customer using 6rd.
>>      We thought this is interesting idea,so published the draft.
>>
>>      http://tools.ietf.org/html/draft-sakura-6rd-datacenter-03
>>
>>      I think both of mailing list participants are also interesting in this technique.
>>      If you have any comment and question of the draft,please let me know.
>>
>>      Regards,
>>      -Shishio
>>      -------- Original Message --------
>>      Subject:        I-D Action: draft-sakura-6rd-datacenter-03.txt
>>      Date:   Mon, 14 Nov 2011 17:21:26 +0800
>>      From:<internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
>>      Reply-To:<internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
>>      To:<i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>>
>>
>>
>>
>>      A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>
>>      Title : IPv6 Rapid Deployment (6rd) in a Large Data Center
>>      Author(s) : Shishio Tsuchiya
>>      Mark Townsley
>>      Shuichi Ohkubo
>>      Filename : draft-sakura-6rd-datacenter-03.txt
>>      Pages : 15
>>      Date : 2011-11-14
>>
>>      IPv6 Rapid Deployment (6rd) as defined in RFC 5969 focuses on rapid
>>      deployment of IPv6 by an access service provider which has difficulty
>>      deploying native IPv6. This document describes how 6rd can be used
>>      to deliver IPv6 within a Large Data Center.
>>
>>
>>      A URL for this Internet-Draft is:
>>      http://www.ietf.org/internet-drafts/draft-sakura-6rd-datacenter-03.txt
>>
>>      Internet-Drafts are also available by anonymous FTP at:
>>      ftp://ftp.ietf.org/internet-drafts/
>>
>>      This Internet-Draft can be retrieved at:
>>      ftp://ftp.ietf.org/internet-drafts/draft-sakura-6rd-datacenter-03.txt
>>      _______________________________________________
>>      I-D-Announce mailing list
>>      I-D-Announce@ietf.org<mailto:I-D-Announce@ietf.org>
>>      https://www.ietf.org/mailman/listinfo/i-d-announce
>>      Internet-Draft<https://www.ietf.org/mailman/listinfo/i-d-announce%0AInternet-Draft>  directories: http://www.ietf.org/shadow.html
>>      or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>
>>
>>      _______________________________________________
>>      armd mailing list
>>      armd@ietf.org<mailto:armd@ietf.org>
>>      https://www.ietf.org/mailman/listinfo/armd
>>
>>
> 
>