Re: [v6ops] New version of draft-lopez-v6ops-dc-ipv6

Diego,

	A quick comment. For the section 2.3 I think one important motivation
is cost savings by not maintaining two stacks.

	Today basically we need to maintain two datacenters networks, Have
procedures to enable and secure IPv4 and IPv6, test new applications in
both stacks, etc. As datacenter admin, to maintain a single stack is a
real motivation to run ipv6 only at least for internal infrastructure
that do not interact with users (databases, application servers, VM
infrastructure, etc.)

	
Regards
as

On 21/10/2012 06:02, Diego R. Lopez wrote:
> Hi,
> 
> This new version incorporates all the changes discussed in Vancouver,
> being the most salient a title change and the renaming of the "maturity
> levels" (and their numbers) into named "transition stages", plus more
> elaborated text for examples at each transition stage, and a first full
> attempt for the security considerations.
> 
> http://datatracker.ietf.org/doc/draft-lopez-v6ops-dc-ipv6
> 
> Diff http://www.ietf.org/rfcdiff?url2=draft-lopez-v6ops-dc-ipv6-03
> 
> Be goode,
> 
> --
> "Esta vez no fallaremos, Doctor Infierno"
> 
> Dr Diego R. Lopez
> Telefonica I+D
> http://people.tid.es/diego.lopez/
> 
> e-mail: diego@tid.es
> Tel:    +34 913 129 041
> Mobile: +34 682 051 091
> -----------------------------------------
> 
> 
> ________________________________
> 
> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
> This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>