> -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf > Of Saku Ytti > Sent: Tuesday, April 02, 2013 7:49 AM > To: L3VPN > Subject: Re: I-D Action: draft-ietf-l3vpn-end-system-01.txt > > On (2013-04-02 12:42 +0200), Robert Raszuk wrote: > > > > I think you can build IPv6 DC virtualization services while still > > using > > IPv4 only DC core. > > I was just worried as draft specifically allows for IPv6, yet XMPP > messages seem to be trailed with /32. I'm personally not interested much > in dual-stack control-plane. I'm happy to run 6PE now, and maybe in > future go > IPv6 only control-plane and 4PE for legacy. But I understand it might > not be popular position. >
[WEG] +1 in fact, at the Orlando IETF meeting, I and a few others kicked off a discussion in MPLS WG regarding a gap analysis for IPv6-only operation of MPLS features, because we believe that this will be necessary within the time horizon for IETF work. So the authors would do well to consider and document or resolve any IPv4 dependencies. While obviously, MPLS control plane dependencies must be solved first, anything specific to this implementation that relies on IPv4 to function should be noted. Wes George 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.
