[v6ops] Fwd: New Version Notification for draft-lopez-v6ops-dc-ipv6-04.txt

Arturo Servin <aservin@lacnic.net> Wed, 06 February 2013 00:43 UTC

Return-Path: <aservin@lacnic.net>
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 6E52021F8941 for <v6ops@ietfa.amsl.com>; Tue, 5 Feb 2013 16:43:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sis7pMfYMOy8 for <v6ops@ietfa.amsl.com>; Tue, 5 Feb 2013 16:43:39 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 7B46521F8915 for <v6ops@ietf.org>; Tue, 5 Feb 2013 16:43:38 -0800 (PST)
Received: from [IPv6:2800:af:ba30:d6e7:48c3:e9ba:4275:6547] (unknown [IPv6:2800:af:ba30:d6e7:48c3:e9ba:4275:6547]) by mail.lacnic.net.uy (Postfix) with ESMTP id 3C059308427 for <v6ops@ietf.org>; Tue, 5 Feb 2013 22:43:19 -0200 (UYST)
Message-ID: <5111A72B.2000804@lacnic.net>
Date: Tue, 05 Feb 2013 22:43:23 -0200
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: v6ops@ietf.org
References: <20130205215743.30106.77867.idtracker@ietfa.amsl.com>
In-Reply-To: <20130205215743.30106.77867.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.5
X-Forwarded-Message-Id: <20130205215743.30106.77867.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck:
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Subject: [v6ops] Fwd: New Version Notification for draft-lopez-v6ops-dc-ipv6-04.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, 06 Feb 2013 00:43:40 -0000

Hi,

	We have submitted a new version of draft-lopez-v6ops-dc-ipv6-04. Some
of the changes we made:

- We expanded the security section as suggested in the list. We included
the attacks and security issues that we considered more important in DC
infrastructure. Please let us know if you wanted to see more, or if some
need to be expanded.
- We added a new section "Other Operational Considerations" and we
included topics such as Addressing, Cost and Monitoring/Management. If
it want to include more topics let us know.
- We re-organized some text in the introduction to be now under a
renamed section "Architecture and Transition Stages"
- We added text suggesting how to start moving applications to IPv6
within the DC
- We added some text to explaining the motivations from moving from
Dual-stack to IPv6-only as suggested in the list
- We changed some text to improve reading as suggested by some people
off-list
- We fixed some typos
- We updated some references
- And we added a new author

	And I think that is all.

	Please let us know your comments.

Best regards
as


-------- Original Message --------
Subject: New Version Notification for draft-lopez-v6ops-dc-ipv6-04.txt
Date: Tue, 05 Feb 2013 13:57:43 -0800
From: internet-drafts@ietf.org
To: aservin@lacnic.net
CC: tina.tsou.zouting@huawei.com, diego@tid.es, cathy.zhou@huawei.com,
18918588897@189.cn


A new version of I-D, draft-lopez-v6ops-dc-ipv6-04.txt
has been successfully submitted by Arturo Servin and posted to the
IETF repository.

Filename:	 draft-lopez-v6ops-dc-ipv6
Revision:	 04
Title:		 IPv6 Operational Guidelines for Datacenters
Creation date:	 2013-02-05
WG ID:		 Individual Submission
Number of pages: 20
URL:
http://www.ietf.org/internet-drafts/draft-lopez-v6ops-dc-ipv6-04.txt
Status:          http://datatracker.ietf.org/doc/draft-lopez-v6ops-dc-ipv6
Htmlized:        http://tools.ietf.org/html/draft-lopez-v6ops-dc-ipv6-04
Diff:
http://www.ietf.org/rfcdiff?url2=draft-lopez-v6ops-dc-ipv6-04

Abstract:
   This document is intended to provide operational guidelines for
   datacenter operators planning to deploy IPv6 in their
   infrastructures.  It aims to offer a reference framework for
   evaluating different products and architectures, and therefore it is
   also addressed to manufacturers and solution providers, so they can
   use it to gauge their solutions.  We believe this will translate in a
   smoother and faster IPv6 transition for datacenters of these
   infrastuctures.

   The document 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 deployment on the DC
   infrastructure.

   Apart from facilitating the transition to IPv6, the mechanisms
   outlined here are intended to make this transition 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