From: "David S. Miller" <davem@redhat.com>
To: yoshfuji@wide.ad.jp
Cc: dlstevens@us.ibm.com, 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: Wed, 19 Mar 2003 19:47:35 -0800 (PST) [thread overview]
Message-ID: <20030319.194735.31799019.davem@redhat.com> (raw)
In-Reply-To: <20030320.124428.95965257.yoshfuji@wide.ad.jp>
From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@wide.ad.jp>
Date: Thu, 20 Mar 2003 12:44:28 +0900 (JST)
In article <20030319.192331.95884882.davem@redhat.com> (at Wed, 19 Mar 2003 19:23:31 -0800 (PST)), "David S. Miller" <davem@redhat.com> says:
> Please propose alternative API, or do you suggest not
> to export this facility to user at all?
I like to assign address like unicast (using ioctl and rtnetlink
(RTN_ANYCAST)).
We suggest you not exporting this facilicy until finishing new API
(And, another API would be standardized;
This is another reason why I am against exporting that API for now.)
I think anycast addresses are more like multicast than unicast. Do
you agree about this?
But here is what really matters, does the advanced IPV6 socket API
say anything about a user API for anycast?
next prev parent reply other threads:[~2003-03-20 3:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 21:06 [PATCH] anycast support for IPv6, updated to 2.5.44 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-20 7:34 David Stevens
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=20030319.194735.31799019.davem@redhat.com \
--to=davem@redhat.com \
--cc=dlstevens@us.ibm.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;
as well as URLs for NNTP newsgroup(s).