On Tue, 2004-02-10 at 13:38, JINMEI Tatuya / çæéå wrote:

> I've submitted a new revision of the rfc2462bis draft:
> draft-ietf-ipv6-rfc2462bis-00.txt
> 
> I expect a certain amount of delay before the draft is ready at the
> official I-D archive, so I put a copy of the draft at the following URL:
> 
> http://www.jinmei.org/draft-ietf-ipv6-rfc2462bis-00.txt
> 
> Any comments/questions/corrections are welcome.

May I ask a question about the following paragraph?

   o  Small sites consisting of a set of machines attached to a single
      link should not require the presence of a stateful server or
      router as a prerequisite for communicating.  Plug-and-play
      communication is achieved through the use of link-local addresses.
      Link-local addresses have a well-known prefix that identifies the
      (single) shared link to which a set of nodes attach. A host forms
      a link-local address by appending its interface identifier to the
      link-local prefix.

I don't understand how is it possible for two hosts to communicate when
no stateful server or router advertising a prefix is attached to the
link. In this case, both hosts are configured exclusively with
link-local addresses, but since those addresses have a fe80::/10 prefix,
how can the IPv6 stack know what interface should the packets be sent
on?

For instance, on Linux 2.6 kernels, when trying to ping another host
using its link-local IPv6, an invalid argument error is generated since
the kernel is not able to guess which interface the packet should be
sent to, since any local interface has exactly the same prefix and
length. This gets complicated even more if the machine has multiple
interfaces, for example, two Ethernet interfaces.

I thought that two IPv6-enabled hosts could only communicate if both
have a site-local or global IPv6 address configured.


--------------------------------------------------------------------
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to