From: Florian Weimer <fweimer@redhat.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Andreas Schwab via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Update getaddrinfo to RFC 6724 (bug 29496)
Date: Tue, 05 Sep 2023 14:44:18 +0200 [thread overview]
Message-ID: <87fs3s7pst.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <mvm5y4o243u.fsf@suse.de> (Andreas Schwab's message of "Tue, 05 Sep 2023 14:31:49 +0200")
* Andreas Schwab:
> On Sep 05 2023, Florian Weimer wrote:
>
>> There's an erratum for this
>
> What does that mean?
There's an unverified entry on this page:
<https://www.rfc-editor.org/errata/rfc6724>
It discusses section 2.2. I do not agree with the proposed resolution.
It essentially recommends going back to the old behavior which assumes
strictly hierarchical IPv6 address assignment.
Thanks,
Florian
next prev parent reply other threads:[~2023-09-05 12:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 9:28 Andreas Schwab
2023-09-04 15:53 ` Florian Weimer
2023-09-04 16:16 ` Andreas Schwab
2023-09-05 12:19 ` Florian Weimer
2023-09-05 12:31 ` Andreas Schwab
2023-09-05 12:44 ` Florian Weimer [this message]
2023-10-24 11:27 Andreas Schwab
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=87fs3s7pst.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
/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).