Fred, On Wed, Dec 19, 2007 at 04:16:22PM -0800, Fred Baker wrote: > > On Dec 18, 2007, at 12:39 PM, Hallam-Baker, Phillip wrote: > >In the same way that there is a difference between a bricklayer and > >an architect there is a difference between an engineer and a > >network admin. > > On Dec 19, 2007, at 8:07 AM, David Kessens wrote: > >This issue will only develop into an outage if you bring the wrong > >survival tools: I suggest you leave your hammer home and make sure > >that you can use ipv6 only. There is no rocket science here. People > >have done this before. > > David, I think you missed Phillip's point. The average engineer at > the IETF meeting isn't in control of significant aspects of his IT > infrastructure, such as whether his IT department has enabled IPv6 > access to his mail server. Sure, I have IPv6 running on my Mac (it > defaults "on" and I dont turn it off) and someone with IPv6 in their > network can presumably get web pages from www.ipv6.cisco.com. That's > not the same as "being productive". No, I don't think I missed Phillip's point at all. Some engineers are apparently more creative than others in their ability to reach the mothership over an ipv6 only network despite the fact that the mothership doesn't have ipv6 vpn support (yet). This certainly hasn't stopped me from connecting back to the company that I work for and it should not stop any competent engineer. David Kessens --- _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf