[ipv6-wg] IPv6 on P2P links

Gunter,

I agree with you that just putting something down on paper so that you have
something to whack other parties with should not be the intention, apart
from the fact that it's hardly constructive as you point out. The problem
I see myself facing at the moment though is that as a result of several
conflicting documents available and the community as a whole inventing
their own wheels we might somewhere down the line run into trouble with
compatibility. I personally would like to be able to point at a clear
guideline for deployment that has been followed, ideally supported by
several RFCs, when ultimately I will end up talking to a third party about the
issue. (Third party can be vendor/customer/other sp/etc)

Besides that it would ofcourse be even nice if we could all agree on a
standard that has been tried and tested before we deploy and avoid issues
all together - which as it currently stands is most likely not going to
happen - but one can dream I guess.

Jasper

-----Original Message-----
From: Gunter Van de Velde (gvandeve) [mailto:gvandeve at cisco.com]
Sent: Thursday, May 26, 2011 11:36 AM
To: Jasper Jans; Marco Hogewoning
Cc: Pierre-Yves Maunier; ipv6-wg at ripe.net
Subject: RE: [ipv6-wg] IPv6 on P2P links

Ok, I bite on this one...

Jan Zorz and his team are doing a great job with the RIPE501Bis,
particular to make it inline with existing
recommendations out there. A vendor as Cisco is really happy with this
as it unifies a global expectations
pattern and will make the world the nice internet place it currently is
because of aligned expectations and investments. Which means things will
materialize quicker.
Next to that, the recommendations now will be more tailored to a more
distinct target audience, as not every little feature availability has
meaning for every kind of user. (like a SOHO office has no need for ISIS
or 50 msec fast convergence or so).

So, I think the key is that 'wacking your vendor' randomly is not the
right path... it may sound
cool to do, but is not the most constructive idea, however asking the
right expected IPv6
services is important and crucial for business continuity of the
user/enterprise/customer.
Responsibility for a good IPv6 infrastructure is the responsibility of
Vendors, Service
providers, content providers and enterprise organizations as a congruent
mutual effort.

G/


Op dit e-mailbericht is een disclaimer van toepassing, welke te vinden is op http://www.espritxb.nl/disclaimer