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 network/11438] Please assign global scope to RFC 1918 addresses in getaddrinfo()
Date: Tue, 11 Sep 2012 09:30:00 -0000 [thread overview]
Message-ID: <bug-11438-131-y1EaY2Mijk@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11438-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=11438
Tore Anderson <tore at fud dot no> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|SUSPENDED |ASSIGNED
--- Comment #5 from Tore Anderson <tore at fud dot no> 2012-09-11 09:30:18 UTC ---
(In reply to comment #2)
> I'm suspending the bug. Change the state when any of the proposals are accepted.
Hi Ulrich,
RFC 6724 has just been published, obsoleting RFC 3484. It assigns global scope
to RFC 1918 addresess.
As requested, I'm therefore changing the state of the bug.
Tore
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-09-11 9:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11438-131@http.sourceware.org/bugzilla/>
2010-12-16 13:01 ` [Bug libc/11438] " chiel at gmx dot net
2012-02-21 1:59 ` [Bug network/11438] " jsm28 at gcc dot gnu.org
2012-09-11 9:30 ` tore at fud dot no [this message]
2012-09-11 17:42 ` ldv at altlinux dot org
2012-09-11 18:11 ` tore at fud dot no
2012-09-17 19:01 ` ldv at altlinux dot org
2012-09-28 16:16 ` law at redhat dot com
2012-12-06 19:53 ` vapier at gentoo dot org
2014-02-16 16:55 ` jackie.rosen at hushmail dot com
2014-05-28 19:45 ` schwab at sourceware dot org
2014-06-30 18:22 ` fweimer at redhat dot com
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=bug-11438-131-y1EaY2Mijk@http.sourceware.org/bugzilla/ \
--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).