Re: [v6ops] IPv6 Operational Guidelines for DC (draft-lopez-v6ops-dc-ipv6-04)

[Arturo Servin <[e-mail]>]

Alexis,

    Thank you for the review. Let us check your comments and we will
reply shortly.

Regards
as/



On 6/19/13 8:55 AM, Alexis Munoz (Gmail) wrote:
> Dear Authors
>
> First of all, I would like to congratulate to all the team who is
> participating in addressing this guideline ahead. Excellent work.
>
> So, I have read the document and I took some notes focus more in Enterprise
> Datacenters that I would like to share here. I split my notes following the
> chapters on the document:
>
> 2.1. General Architecture 
>
> The generalized interconnection schema in a DC in my opinion must goes
> beyond. Normally, in a datacenter infrastructure there are modules
> interconnecting the DC. I agree, the Internet Access is one of them, but we
> cannot forget that there might be also modules interconnecting the DC such
> as WAN and Remote Access Modules, all depend on the scenario and sector. The
> IPv6 Deployment in the Datacenter might extend the interconnectivity  to
> Branch Offices, Partners, Third-Parties, so forth. The IPv6 address schema
> should consistent end-to-end, even more for delivery services and
> applications on public or private networks.
>
>
> 2.2. Experimental Stages 
>
> One of the implicit advantages of IPv6 application are Flow Labels and
> Mobile IP, only if they are applied at the ingress elements. However, it is
> not clear for me, because all the internal networks are IPv4 in this stage,
> then, why Mobile IP comes into play, also, Are we  talking about Mobile IP
> on IPv4 or IPv6?. 
>
> Additionally, for VM Migration intra or inter-DC, we might prefer to use
> mechanism offered by vendors for moving either the virtual machines or the
> data, and to keep the ip address intra or inter-DC, there are mechanism as
> VLANs, Extended LANs, so on.  
>
> I will really discuss and review the advantages and disadvantages  of this
> stage. If somebody is interested in looking this stage for experimentation
> or early evaluation, the idea is to find out a good purpose for enroll it. 
>
>
> 2.3. Dual Stack Stages 
>
> On which internal elements are required to have dual-stack??, I guess that
> an internal part or element could be defined as Switch, Router, Load
> Balancer, Firewall, NIPS, Server, Network Service, Application, so forth. I
> think that could be interesting to mention in general in a dual-stack stage
> which elements are more common to have a dual-stack to achieve a soft
> transition and avoid impact in the performance of the services and
> applications.  
>
> Additionally, the Dual-Stack is focus on LB Mechanism, what happen in
> scenarios where is not required a Load Balancer?....how is affected the data
> transmission in the farm servers??...Should left in IPV4 the Farm Servers
> and apply Dual-Stacking in the Services Layers with devices as Firewall,
> Load Balancer, DNS, Router, Wireless Controllers, So Forth?...what is the
> best practice here?
>
> 2.4 IPv6 Only Stage. 
>
> I absolutely agree that  planning the ip address schema is one of the most
> important and stronger part for a transition IPv6 into the DC Infrastructure
> successfully, also apply for any of the transition stages. 
>
> 3. Other Operational Considerations
> 3.1 Addressing
>
> The document recommend at least to have a /48 for each Datacenter, what
> should be the recommendation to allocate the subnets inside the datacenter?,
> I know all depends on the services and architecture, but I think could be
> good idea to mention some general good practices to allocate properly the
> IPv6 into the DC Infrastructure. 
>
> 3.3. Monitoring and Logging
>
> Collect data specific can be using SNMPv3 over IPv6 as well, or is not
> supported SNMPv3 over IPv6 yet?
>
> 3.4. Costs
>
> What were the parameters or model to estimate the extra costs??...that might
> be very useful to support the business case. I suggest to add to the
> document.   
>
> I hope these comments can help to the authors and the community to adopt the
> document as WG item.  
>
> Thanks a lot.
>
> Alexis Muñoz
>
> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] On Behalf Of
> Santiago Aggio
> Sent: Tuesday, June 18, 2013 9:38 AM
> To: [e-mail]
> Subject: [v6ops] IPv6 Operational Guidelines for DC
> (draft-lopez-v6ops-dc-ipv6-04)
>
> Dear Authors,
>
>     My impression is that this very good, very clear, is a guide that covers
> most of the realities faced by an operator and an engineer of a DC
> infrastructure to deploy IPv6, with several considerations that help in the
> moment of decision and the work involved in the technical side of the
> routing, management and monitoring.
>
>      The architecture described is very simple and clear, and very well the
> above stages to reach IPv6-only model. The references also seem to cover
> these aspects.
>   
> Great Job!!!!, Congratulations
>
> Santiago Aggio
> Bahia Blanca
> Argentina.
>
> _______________________________________________
> v6ops mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/v6ops
>
> _______________________________________________
> v6ops mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/v6ops