From: Ulrich Drepper <drepper@redhat.com>
To: netdev@oss.sgi.com, yoshfuji@linux-ipv6.org, kuznet@ms2.inr.ac.ru
Subject: RFC 3484 support
Date: Tue, 11 Nov 2003 17:05:28 -0800 [thread overview]
Message-ID: <3FB18758.8040708@redhat.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I want to implement RFC 3484 support in getaddrinfo for glibc but there
is the tiny little problem with the source address selection which has
to be solved as part of the destination address selection.
To sort the destination addresses the source address for each of the
addresses returned by getaddrinfo must be determined. This can be done
in two ways:
1. use the existing kernel functionality and provide an interface to it
which userlevel can use
2. re-implement routing at userlevel
#2 above has serious problems. To accurately re-implement the kernels
routing decision making a huge amount of data is needed. Not only the
routing information, but also transient errors, all the kernel
parameters and flags influencing routines etc. This is, I'd say,
virtually impossible which would mean an implementation with the source
address selection happening at userlevel would do a bad job in some cases.
So my question is: is there interest in adding support for method #1 to
the kernel? Could we get a syscall or whatever to pass down to the
kernel a set of addresses (and whatever else is needed) and the kernel
passing back information about the sorted list (either the sorting list
or a transformation description of some sort)?
[I'm not on this list, so please cc: me. DaveM made me post here.]
- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/sYdY2ijCOnn/RHQRAppvAJ9MuBPXJM5tH93mXwRu2prifwo+GACfSjzg
tuMC3yIgcqugevSYvuJpC2g=
=yEdb
-----END PGP SIGNATURE-----
next reply other threads:[~2003-11-12 1:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 1:05 Ulrich Drepper [this message]
2003-11-13 10:07 ` RFC 3484 support kuznet
2003-11-13 13:26 ` Pekka Savola
2003-11-13 23:17 ` Ulrich Drepper
2003-11-13 23:29 ` Pekka Savola
2003-11-13 23:12 ` Ulrich Drepper
2003-11-14 23:45 ` kuznet
2003-11-18 8:59 ` Ulrich Drepper
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=3FB18758.8040708@redhat.com \
--to=drepper@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.com \
--cc=yoshfuji@linux-ipv6.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 NNTP newsgroup(s).