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

I've read this version of the draft, and I have a few comments.

I would not refer to your last transition stage as "Next Generation" as that is not a particularly descriptive term for the stage that you describe, and it is also a fairly overloaded term - my "next generation" DC may well be the one where I increase the bandwidth, or build out a fabric, start using some new widget, or whatever. I would maybe call it IPv6-only or Single-stack IPv6, since that is really the desired end state, where as much of the DC as possible is running IPv6 for all functions, and IPv4 connectivity is handled via transition and translation technologies at the edges of the DC (eg loadbalancers, etc).

Section 2.3 should mention the fact that this stage may be driven by either a lack of enough IPv4 resources (whether private or globally unique) or a need to reclaim IPv4 resources from portions of the network which no longer need them. There is a point at which dual stack is simply not possible anymore, and once that point has been reached, a careful evaluation of what still needs to speak IPv4 and what does not will need to happen to ensure judicious use of the remaining IPv4 resources.

It might also be helpful to discuss the different classes/categories of things that are in an average data center, as those may have a bearing on how the transition proceeds, and indeed may be at different phases of the transition at different times:

Management systems (provisioning, alarms/PMs, software distro, etc)
Fabric (and perhaps even discuss the different layers, ToR, agg, core, etc)
Hypervisor (though this is already mentioned in a few places in the draft)
Machine-to-machine communications (one application talking to another over an API)
End-user applications/content
External services
Etc

The key here is to keep it generic enough so that it's widely applicable, rather than getting so specific that you have to have multiple different scenarios to represent different potential DC applications and designs.

Security considerations: draft-vynke-opsec has been replaced by draft-ietf-opsec. However... The referenced draft covers a lot of ground, and simply referring to it by itself might be daunting to potential readers. It might be worth highlighting specific sections that are especially pertinent to DCs, such as the discussion of ND cache exhaust, etc.

Thanks,

Wes George

> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
> Of Diego R. Lopez
> Sent: Sunday, October 21, 2012 6:03 AM
> To: IPv6 Ops WG
> Subject: [v6ops] New version of draft-lopez-v6ops-dc-ipv6
>
> 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

This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.