Re: Disable IPv6 ?

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 08/18/2016
06:28:37 PM:

From: Raul A Jager W <raul@xxxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Date: 08/18/2016 06:29 PM
Subject: Re: Disable IPv6 ?
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

IPv6 is here, now. In 5 - 10 years it is very like that IPv4 users will
be small minority, and regarded as "old technology", its users will be
almost forced to migrate. At a more expensive cost, and leaving behind
the people that did not learned it.

As much as I like IPv6 and push for its adoption, I very much doubt that
IPv4 users will be in the "small majority" in 5 years. Maybe 10 years.
Dual stack will be with us for a very long time I have a feeling.
Eventually what you'll see is ISPs and other providers running out of IPv4
addresses (already happening) and putting people behind CGNAT. CGNAT has
costs as well, so eventually they'll get with IPv6 and push people to IPv6
only and IPv4 will cost extra. At this point is when it'll be very
important for IBM i shops to support IPv6 connectivity, since otherwise
their customers would be unable to reach them.

For many companies there is no immediate benefit of going IPv6, especially
smaller shops. I think people should be prepared for that day, though.

<snip>

How deep is IPv6 in the i OS? Can you still use IPv4 or is all IPv6 and
translated for outside view? I did this test (V7.3):

CRTDDMF FILE(QTEMP/TEST) RMTFILE(QGPL/TEST) RMTLOCNAME('10.0.0.8' *IP)
dspfd test

In the description//I found/:

/Archivo remoto . . . . . . . . . . . . . . : RMTFILE 'QGPL/TEST'
Ubicación remota RMTLOCNAME
Nombre o dirección . . . . . . . . . . . : '::FFFF:10.0.0.8'
Tipo . . . . . . . . . . . . . . . . . . : *IP
/

You can find IBM i-related IPv6 information in the Knowledge Center:
http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/rzai2/rzai2ipv6intro.htm

/My IPv4 address is automatically translated and stored in the file
description as the IPv6 equivalent. why?

That's an IPv4-mapped IPv6 address. It allows applications on a dual-stack
(IPv4 & IPv6) system to use only IPv6 and still talk to IPv4 clients. See
https://tools.ietf.org/html/rfc4038 and
https://tools.ietf.org/html/rfc4291#section-2.5.5 for more info.