From: Lee <ler762@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Please support download setup-x86_64.exe on IPv6-only network
Date: Mon, 20 Nov 2023 19:45:21 -0500 [thread overview]
Message-ID: <CAD8GWsuwdbydtG98DTZNrsmQ50Z1T7iwVs6dMx0E50qbCfCCcQ@mail.gmail.com> (raw)
In-Reply-To: <CAKwdsS_+gH+RuNwCC6h_eDcF5m_Ov2DeqTyUhbS43CTHvEEptA@mail.gmail.com>
On Mon, Nov 20, 2023 at 7:13 PM Backwoods BC via Cygwin wrote:
>
> On Thu, Nov 16, 2023 at 12:41 PM Brian Inglis via Cygwin wrote:
> > The whole IP v4 internet is available as a compatibility subnet ::ffff:0:a.b.c.d
> > on IP v6, so there is no excuse for not supporting interconnection, as it will
> > be required until the last backbone routers drop IP v4 support.
>
> Just a small correction for the mail archives as this appears solved.
> The correct IPV6 address for the IPV4 address range is
> ::ffff:a.b.c.d (no '0')
If you're going for correcting the record, let's make it correct.
::ffff:a.b.c.d is not a solution for IPv6 => IPv4 interconnection over
the Internet.
from: https://www.rfc-editor.org/rfc/rfc5156
2.2. IPv4-Mapped Addresses
::FFFF:0:0/96 are the IPv4-mapped addresses [RFC4291]. Addresses
within this block should not appear on the public Internet.
Regards,
Lee
next prev parent reply other threads:[~2023-11-21 0:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 1:40 Bin W
2023-11-16 7:13 ` Martin Wege
2023-11-16 10:18 ` Adam Dinwoodie
2023-11-16 20:40 ` Brian Inglis
2023-11-21 0:12 ` Backwoods BC
2023-11-21 0:45 ` Lee [this message]
2023-11-21 5:35 ` Brian Inglis
2023-11-21 7:36 ` Backwoods BC
2023-11-21 8:01 ` Lee
2023-11-21 18:11 ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2023-11-20 13:55 ` Jon Turney
2023-11-20 23:58 ` Lee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAD8GWsuwdbydtG98DTZNrsmQ50Z1T7iwVs6dMx0E50qbCfCCcQ@mail.gmail.com \
--to=ler762@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).