Sure Fernando
Certainly we all understand that recent times and the need to adapt to
it in order to keep going.
But long term the main thing I believe must be the the mindset, to be
committed to require IPv6 support on *all possible SaaS solutions* used
within IETF, specially where there are well known alternatives.
As mentioned, sometimes people are just used to an specific tools
because some specific feature or way of using and try to make that is
'really' necessary, but if you look it better it isn't and it's probably
perfectly fine let it go.
Overall the most important is to have the will to give the example on
all possible opportunities without hesitation. This not only gives
everybody a good example but also helps to push vendors to perhaps think
about when an organization like IETF denies the use of their services
due to the lack of IPv6. How long more are we going to keep accepting
all sort of excuses and pretending it is going to happen soon ?
Productivity is certainly important, but values are above.
Regards
Fernando
On 18/04/2020 23:05, Fernando Gont wrote:
Hello, Fernando,
On 18/4/20 00:10, Fernando Frediani wrote:
Hello all
I want to call attention to a open wound. Some people may feel
uncomfortable about the content of this email but I can assure I come
with good intentions.
Recently I got to know that a 6man meeting ironically was conducted
via Webex Videoconferencing tool which does not have IPv6 support.
Other tools used by IETF like GitHub also don't have and in this case
is even worst because there are several alternatives with IPv6
support as GitLab, Bitbucket or even a self-hosted option.
[...]
Shall we do the right thing and put values above other priorities
going forward ?
Thanks for posting this.
I essentially share the same concerns as you.In the specific case of
webex for the recent interim meetings, I would probably be more
flexible (when it comes to the recent interim meetings) since there
was a lot of "on the fly" planning to deal with the contingency of
COVID-19. -- and, as far as I understand,use of Webex has not been
formalized in any way (i.e., nothing prevents us from using something
else for the next IETF or interim meetings).
When it comes to GitHub, there seems to be more formalized use of it
(there's even a WG), and, as you correctly note, given the many
alternative options it seems kind of hard to back a decision to use it.
Thanks!
Cheers,
