From: Phillip Hellewell <sshock@gmail.com>
To: libc-help@sourceware.org
Subject: RFC 6724
Date: Sun, 11 Nov 2018 20:45:00 -0000 [thread overview]
Message-ID: <CA+dWQFo-rHBGgAtBR54AHpj2mk5aG==2kmWrL7RuYD_KqAuSSA@mail.gmail.com> (raw)
Assuming the comments in gai.conf are accurate, glibc still use
obsolete RFC 3484 for address selection.
RFC 6724 came out in 2012, so why does glibc still use RFC 3484 rules?
The changes since RFC 3484 can be seen here:
https://tools.ietf.org/html/rfc6724#appendix-B
Thanks,
Phillip Hellewell
next reply other threads:[~2018-11-11 20:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-11 20:45 Phillip Hellewell [this message]
2018-11-11 21:09 ` Phillip Hellewell
2018-11-12 11:21 ` Florian Weimer
2018-11-12 16:50 ` Phillip Hellewell
2018-11-12 17:43 ` Florian Weimer
2018-11-13 4:50 ` Phillip Hellewell
2018-11-13 10:51 ` Florian Weimer
2018-11-13 16:49 ` Phillip Hellewell
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='CA+dWQFo-rHBGgAtBR54AHpj2mk5aG==2kmWrL7RuYD_KqAuSSA@mail.gmail.com' \
--to=sshock@gmail.com \
--cc=libc-help@sourceware.org \
/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).