datatracker.ietf.org
Sign in
Version 5.6.2.p5, 2014-08-04
Report a bug

IPv6 Operational Guidelines for Datacenters
draft-lopez-v6ops-dc-ipv6-05

Document type: Replaced Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2013-08-14 (latest revision 2013-07-14)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Replaced by draft-ietf-v6ops-dc-ipv6
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:
http://www.ietf.org/archive/id/draft-lopez-v6ops-dc-ipv6-05.txt

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 Data Center (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.

Authors

Diego Lopez <diego@tid.es>
Zhonghua Chen <18918588897@189.cn>
Tina Tsou <tina.tsou.zouting@huawei.com>
Cathy Zhou <cathy.zhou@huawei.com>
Arturo Servin <aservin@lacnic.net>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)