Re: new issue: [LL36] Combine and rework section 1.7 and 2.11 to be clearer

Alex,

You are incorrect in asserting there is a problem.

A host whose interface is configured with a link-local address can
communicate with a host with a routable address (See Section 2.6.2).
The host with the link-local address may also *discover* the address
of a host with a routable address (on the same link), for example by
using mDNS.

A host with a routable address which complies with this specification
can communicate with a host configured with a link-local address
(See Section 3.3).  The host with the routable address that receives
discovery messages (such as sent by mDNS) will respond.  If the 
discoverer's source address is link-local, the discovered service will
respond to that destination address.

Best regards,

Erik

  = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

Alex Karahalios wrote:
> Hi Philip,
> 
> Yes, this works. But what I am trying to address is that, due to the 
> wording of section 1.7, the mDNS printer will no longer broadcast the LL 
> address once it obtains a routable address and thus the LL only device 
> will never know that the printer exists and thus cannot communicate with 
> it.
> 
> That is why the phrase
> 
>    "the host MUST always use the routable address when
>    initiating new communications, and MUST cease advertising the
>    availability of the Link-Local IPv4 address through whatever
>    mechanisms that address had been made known to others"
> 
> is not acceptable since it precludes LL only devices from participating 
> in the network.
> 
> Alex Karahalios
> 
> On Dec 18, 2003, at 2:49 AM, Philip Nye wrote:
> 
>> Provided they are on the same link, the LL device _can_ communicate 
>> with the printer just so long as the printer has the necessary route 
>> for the 169.254.x.x network. This has been the preferred mode of 
>> operation for several successive drafts now. Communication between LL 
>> and routable hosts on the same link is perfectly possible.
>>
>> I would expect a printer using mDNS to configure the necessary route 
>> automatically. Getting the IPv4LL draft to RFC status would make this 
>> even more likely!
>>
> 


-- 
  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
    Erik Guttman   -   N1 Manageability   -   Sun Microsystems
       cell: +49 172 865 5497   -   time zone: CET (GMT+1)