[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
About draft-arifumi-lin6-multihome-api-00.txt (was Re: Call forpresentations)
Hi,
I have some questions about draft-arifumi-lin6-multihome-api-00.txt.
I fail to understand the idea behind this proposal.
I mean, if i understand correctly, the draft proposes an API that it is
capable of handling the multiple address that result when a site is
multi-homed and it uses PA addresses.
However, it seems somehow linked to LIN6 (LIN6 is mentioned multiple
times in the document), but i fail to understand how. AFAIK LIN6 maps
multiple different addresses in a single address, making the change of
address transparent to transport layer and above.
So LIN6 handles multiple addresses in the IP layer making it transparent
to upper layers and the proposed draft proposes a way to handle multiple
addresses. How is this compatible? i mean the upper layers, see one LIN6
address or multiple addresses?
If the upper layers are aware of the multiple address, what do you need
LIN6 for?
An additional question is about address discovery. I mean how do the end
nodes find out what addresses are available at the other end? There is a
mapping agent mentioned, but where is this mapping agent located? which
addresses does it announce? all the available addresses or just the ones
that are reachable at the moment? if the latter, how does it find out
whether an address is reachable or not?
Another question is related to security, i.e. how do you authenticate
the addresses actually belong to the node that is claiming its
ownership? This is a very important and difficult issue as far i can
tell, and it should be addressed.
Finally, how the multi-homed node communicates the alternative address
to be used when the address that is being used fails?
I hope you clarify these issues to me, thanks, marcelo
On Mon, 2003-06-23 at 09:17, FUJIKAWA Kenji wrote:
> [ post by non-subscriber. with the massive amount of spam, it is easy to miss
> and therefore delete posts by non-subscribers. if you wish to regularly
> post from an address that is not subscribed to this mailing list, send a
> message to <listname>-owner@ops.ietf.org and ask to have the alternate
> address added to the list of addresses from which submissions are
> automatically accepted. ]
>
> Kurt;
>
> We have already submitted internet-drafts that are related
> to multi6 WG. They can be downloded from
> http://www.users.kudpc.kyoto-u.ac.jp/~r52802/draft-ohira-assign-select-e2e-multihome-00.txt
> and
> http://hage.tori.cc/~arifumi/draft-arifumi-lin6-multihome-api-00.txt
> , and will be downloded from ftp.ietf.org soon.
>
> We would like to make presentations abount them, so would
> you assign slots for us? We'll be glad if you assign 15min
> for each draft.
>
> FYI, we now manage more than 200 wireless APs based on
> 802.11b in Kyoto city, Japan, and all of them supports
> IPv6. We are also planning to multihome them. I believe our
> platform is the largest IPv6 wireless environment in the
> world, and will be the largest wireless multihomed
> environment.
>
> The followings are detailed information on drafts:
>
> ID: draft-ohira-assign-select-e2e-multihome-00.txt
> Title: IPv6 Address Assingment and Route Selection
> for End-to-End Multihoming
> Speaker: FUJIKAWA Kenji (Kyoto University)
> Abstract:
> IPv6 suppose that network is hierarchical. Though the present IP
> network topology is not hierarchical at the point of multihoming.
>
> In this document, we clarify that
> a) how to assign address blocks to ISPs and sites in order to
> achieve multihome environment without destroying hierarchical
> structure of IPv6
> b) requirements in order for end hosts to select an adequete route
> from multiple routes when multihoming.
>
> ID: draft-arifumi-lin6-multihome-api-00.txt
> Title: Basic Socket API Extensions for LIN6 End-to-End Multihoming
> Speaker: Arifumi Matsumoto (Kyoto University)
> Abstract:
> This document describes a method for multihoming support in
> application layer. We extend the basic socket API(Application
> Programming Interface) and propose some new interfaces for
> multihoming. Multihoming nodes are expected to have multiple
> addresses. The existing socket APIs, however, are not designed to
> manipulate multiple addresses in a connection. Proposed APIs help an
> application to handle multiple addresses, to avoid connection failure
> and to do load-balancing possibly. Right now, the proposed APIs are
> for LIN6 nodes, one of the mobile protocols. This is because LIN6's
> addressing architecture, which is called "8+8", is very friendly and
> consistent with multihoming. In this document, we propose a host-
> based multihoming solution and which is called end-to-end
> multihoming. In end-to-end multihoming, a fault-tolerant connection
> can be achieved relying not on routers but on the pair of end-nodes
> only.
> ---------------------------------------------------------------
> FUJIKAWA, Kenji @ Grad. Sch. of Informatics, Kyoto Univ., Japan
> WWW: http://www.lab1.kuis.kyoto-u.ac.jp/~fujikawa/index-e.html
> TEL +81 75-753-5387 FAX +81 75-751-0482
> E-mail fujikawa@real-internet.org
>
>
>
>