public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tore at fud dot no" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/11438] Please assign global scope to RFC 1918 addresses in getaddrinfo()
Date: Fri, 16 Apr 2010 09:23:00 -0000	[thread overview]
Message-ID: <20100416092325.23750.qmail@sourceware.org> (raw)
In-Reply-To: <20100328154610.11438.tore@fud.no>


------- Additional Comments From tore at fud dot no  2010-04-16 09:23 -------
Hi Ulrich, and thanks for your feedback.  I've brought the problem up with a 
couple of major distributions (Fedora and Ubuntu), and they've both applied the 
change, so it will be part of both Fedora 13 and Ubuntu 10.04 LTS.

I've also just realised that the current practise of assigning non-global scope 
to rfc1918-addreses is more broken than what I first thought - if a host has 
only link-local IPv6 addresses in addition to (NAT-ed) RFC1918 IPv4 addresses, 
the link-local IPv6 address will be preferred for the outbound connection to a 
dual-stacked server with (both IPv6 and IPv4 addresses globally scoped).  I had 
to read rule 2 in RFC3484 many times before actually believing this is the RFC-
mandated behaviour.  But even if it is, it is obivously not the right thing to 
do.

So I'm hoping that in light of this you might reconsider making the change prior 
to the completion of the IETF standardisation process.  I could attempt to 
persuade all the distributors to carry the change locally, but given the 
multitude of distributions out there I think it would be much more efficient to 
simply fix it in glibc centrally.

Thanks for your time!

Best regards,
Tore Anderson

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=11438

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2010-04-16  9:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-28 15:46 [Bug libc/11438] New: " tore at fud dot no
2010-03-28 15:47 ` [Bug libc/11438] " tore at fud dot no
2010-04-04  1:08 ` drepper at redhat dot com
2010-04-16  9:23 ` tore at fud dot no [this message]
2010-04-16 13:27 ` drepper at redhat dot com
     [not found] <bug-11438-131@http.sourceware.org/bugzilla/>
2010-12-16 13:01 ` chiel at gmx dot net

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=20100416092325.23750.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.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).