I don’t think we need to do such analysis … we don’t work like that at IETF.
We must just draft a plan for our “requirements for IETF tools”, write it down in an ID, may be update the previous one, maybe a different (new) one, and see if we can reach consensus.
I’m happy to work on that, and I’m sure others as well!
Regards,
Jordi
@jordipalet
El 22/4/20 14:49, "ietf en nombre de Fernando Frediani" <ietf-bounces@xxxxxxxx en nombre de fhfrediani@xxxxxxxxx> escribió:
So folks
How can this advance within IETF ?
Is it Management responsability to ensure all tools have this requirement by default, and that any exceptions to be fairly justified.
How can a proper analisys be done in order to replace tools like GitHub and WebEx until they support IPv6 ?
Who's responsability is to make it happen and be accountable for ?
Regards
Fernando
On Wed, 22 Apr 2020, 09:40 JORDI PALET MARTINEZ, <jordi.palet=40consulintel.es@xxxxxxxxxxxxxx> wrote:
+1
Exactly, is not for "right now", but we should make sure to work on that.
Even if we plan for not removing the A RRs or to do so in several years, anticipation is needed.
Regards,
Jordi
@jordipalet
El 22/4/20 14:28, "ietf en nombre de Keith Moore" <ietf-bounces@xxxxxxxx en nombre de moore@xxxxxxxxxxxxxxxxxxxx> escribió:
On 4/22/20 7:58 AM, otroan@xxxxxxxxxxxxx wrote:
> We are 20+ years in.
> If we (as the collective we) believed in this transition shouldn't the next step be to remove the A records from {mail,datatracker,www}.ietf.org? And add a piece of _javascript_ blocking any client coming through a translator from v4.
Our recommended transition strategy was dual-stack. Removing IPv4
support is premature until IPv6 is ubiquitous. Nobody is proposing
that github be made IPv6-only.
> I would expect ridicule from such a proposal.
> Our tools including our collboration tools are centralized, they don't benefit much from IPv6 and end to end transparency either.
No but it's entirely possible that there are, or soon will be, IETF
participants who cannot access github because of the lack of IPv6
support. As IPv6 becomes more available and IPv4 space more and more
scarce we should expect that some existing access networks will
discontinue IPv4 support. Who wants to maintain equipment and routes
that aren't used anymore? When public IPv4 network access disappears,
it will happen gradually at first, and then everywhere suddenly.
I don't think the github situation is an emergency yet, but I agree that
we need to make sure that all of the tools that we use and expect
participants to use are accessible via IPv6. Maybe not this week, but
probably this year.
Keith
**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company
This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company
This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
Sure Jordi
It is indeed something great long term.
But I was also looking for something that can be done within the Management for internal stuff and things they make available for us.
For example: Board meetings can stop using WebEx and Management can find another solution so the example can start from there. Same applies to similar cases..
Regards
Fernando
On Wed, 22 Apr 2020, 09:57 JORDI PALET MARTINEZ, <jordi.palet=40consulintel.es@xxxxxxxxxxxxxx> wrote:
