From: David Stevens <dlstevens@us.ibm.com>
To: "David S. Miller" <davem@redhat.com>
Cc: yoshfuji@wide.ad.jp, kuznet@ms2.inr.ac.ru,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [PATCH] anycast support for IPv6, updated to 2.5.44
Date: Thu, 20 Mar 2003 00:34:41 -0700 [thread overview]
Message-ID: <OF4D6C9027.2F431095-ON88256CEF.002804BF@us.ibm.com> (raw)
Yoshifuji,
I created the multicast-like API because, aside from the in-kernel
use, there was no way to use anycasting otherwise, and I believe for at
least the high-availability case, it doesn't make any sense to treat it
like a unicast address. An exited DNS server program with the server
machine still up will in fact deny service to clients that might otherwise
find a working server if the "permanent" address model were not there. With
a multicast-like interface at least available, programs have the choice of
tying the anycast address to whether or not the service that needs it is
running.
That said, there's no reason why you can't have both, and that's
straightforward with the code (but not implemented). I think it's too early
to be concerned with compatibility since there is no alternative
non-permanent anycast address API. If Linux has an API to do something that
can't be done at all on other systems, there clearly isn't a portability
issue.
+-DLS
next reply other threads:[~2003-03-20 7:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 7:34 David Stevens [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-28 21:06 David Stevens
2003-03-20 0:31 ` David S. Miller
2003-03-20 3:01 ` YOSHIFUJI Hideaki / 吉藤英明
2003-03-20 3:23 ` David S. Miller
2003-03-20 3:44 ` YOSHIFUJI Hideaki / 吉藤英明
2003-03-20 3:47 ` David S. Miller
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=OF4D6C9027.2F431095-ON88256CEF.002804BF@us.ibm.com \
--to=dlstevens@us.ibm.com \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=yoshfuji@wide.ad.jp \
/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
all inboxes | Powered by JetHome®