public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Lee <ler762@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Please support download setup-x86_64.exe on IPv6-only network
Date: Tue, 21 Nov 2023 03:01:17 -0500	[thread overview]
Message-ID: <CAD8GWsvnoUuneTZxwDSzD1g2v_9_xqCAFgAfXJ7KStwJ=gLt_Q@mail.gmail.com> (raw)
In-Reply-To: <db86fa40-991c-4977-9bff-668cb28fff93@Shaw.ca>

On Tue, Nov 21, 2023 at 12:35 AM Brian Inglis wrote:
>
> On 2023-11-20 17:45, Lee via Cygwin wrote:
> > 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.
>
> These internal addresses are used by dual stack hosts to allow clients or
> servers to handle connections to IPv4 hosts the same as IPv6 hosts.

I think that at best you're terribly confused, but let's play this out.

> Whereas ::ffff:0:0:0/96 == ::ffff:0:a.b.c.d allows IPv6 only hosts without
> assigned IPv4 addresses to connect to IPv4 only hosts via SIIT see:
>
>         https://www.rfc-editor.org/rfc/rfc7915 Stateless IP/ICMP Translation.

I did see RFC 7915.  I searched for 'ffff' and there were no matches.

You need something else to back up your claim that
  ::ffff:0:0:0/96 == ::ffff:0:a.b.c.d allows IPv6 only hosts without
  assigned IPv4 addresses to connect to IPv4 only hosts.

And please explain how an ipv6 host is going to get a packet with a
0::/8 address delivered across the internet.

see:  https://www.iana.org/assignments/ipv6-address-space/ipv6-address-space.xhtml

An ipv6 prefix of 2000::/3 is defined as Global Unicast.  In other
words, an ipv6 unicast address MUST start off with 2000::/3 to be
routed across the Internet.

And look at footnotes 3 and 4
::ffff:0:0/96 reserved for IPv4-mapped Address [RFC4291].
0::/96 deprecated by [RFC4291]. Formerly defined as the
"IPv4-compatible IPv6 address" prefix.

Nothing about ::ffff:0:0:0/96

Regards,
Lee

  parent reply	other threads:[~2023-11-21  8:01 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
2023-11-21  5:35           ` Brian Inglis
2023-11-21  7:36             ` Backwoods BC
2023-11-21  8:01             ` Lee [this message]
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='CAD8GWsvnoUuneTZxwDSzD1g2v_9_xqCAFgAfXJ7KStwJ=gLt_Q@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).