[ipv6-wg] RIPE-501 replacement document - IPsec question to community - we need your input.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Just my 2ct:
I have 90% with IPSec but 0,000% IPv6 (whatever you think, fact, this
is not happening in real life yet! we're peering, all set-up, but no
single customer ever asked for?! Maybe there's still something wrong
with IPv6?
Both is yet freaky stuff, my cents: don't block the new freaky stuff
(V6) with the old one (IPSec) which never got real.. in real life..

Michael

On 23.12.2011 23:16, Jan Zorz @ go6.si wrote:
> On 12/23/11 5:30 PM, Eric Vyncke (evyncke) wrote:
>> Jan,
>> 
>> Let's be realistic (and the best quality of RIPE-501++ is to be 
>> realistic and 'down to the ground'): very few IPv6-nodes do
>> IPsec... So, let's remove this requirement and make it optional
>> (RFC 6434 clearly shows the path).
>> 
>> Going in holiday mode: do you use SSH or telnet+IPsec ? :-)
> 
> I see your point :)
> 
> so, +1 for all optional.
> 
> What others think?
> 
> And additional question: should we request IPsec-v3 or v2?
> 
> Cheers, Jan
> 

- -- 
Michael Markstaller

Elaborated Networks GmbH
www.elabnet.de - www.wiregate.de
Lise-Meitner-Str. 1, D-85662 Hohenbrunn, Germany
fon: +49-8102-8951-60, fax: +49-8102-8951-80
Geschäftsführer: Stefan Werner, Michael Markstaller
Amtsgericht München HRB 125120, Ust-ID: DE201281054
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk71PBcACgkQaWRHV2kMuAJZWQCePRJmxG7iJ0tutVxTD3e8hNu2
uhYAnArGJ+wHZTQRZ+/sOQfRgfcoQ6DS
=97pC
-----END PGP SIGNATURE-----