From owner-freebsd-net@FreeBSD.ORG  Fri Aug 25 01:35:43 2006
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
X-Original-To: freebsd-net@freebsd.org
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6AE7B16A4DD;
	Fri, 25 Aug 2006 01:35:43 +0000 (UTC)
	(envelope-from jinmei@isl.rdc.toshiba.co.jp)
Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp
	[202.249.10.124])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 00FD743D46;
	Fri, 25 Aug 2006 01:35:42 +0000 (GMT)
	(envelope-from jinmei@isl.rdc.toshiba.co.jp)
Received: from impact.jinmei.org (unknown
	[2001:200:1b1:1010:3d5a:cc2c:134c:d985])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP
	id 5D20015228; Fri, 25 Aug 2006 10:35:41 +0900 (JST)
Date: Fri, 25 Aug 2006 10:35:03 +0900
Message-ID: <y7v64ghvbqw.wl%jinmei@isl.rdc.toshiba.co.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: Brooks Davis <brooks@one-eyed-alien.net>
In-Reply-To: <20060824184228.GC37561@lor.one-eyed-alien.net>
References: <3E654CC0217F90E20FCD806E@garrett.local>
	<44EC90B7.6090908@shapeshifter.se> <44ECB0F2.9040300@FreeBSD.org>
	<44ECBB61.9020808@shapeshifter.se>
	<5D7785ADC030FEBFB9A5E69D@garrett.local>
	<44ED8266.1060303@shapeshifter.se>
	<7C6CDF1CB0BC58A6ADE1FCA8@garrett.local>
	<44EDCEC2.7060109@shapeshifter.se>
	<93381966E13B960D4ACFF05C@garrett.local>
	<44EDF116.9050106@shapeshifter.se>
	<20060824184228.GC37561@lor.one-eyed-alien.net>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan.
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: freebsd-net@freebsd.org, Pat Lashley <patl@volant.org>,
	Doug Barton <dougb@freebsd.org>,
	Fredrik Lindberg <fli+freebsd-net@shapeshifter.se>
Subject: Re: Zeroconfig and Multicast DNS
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Aug 2006 01:35:43 -0000

>>>>> On Thu, 24 Aug 2006 13:42:29 -0500, 
>>>>> Brooks Davis <brooks@one-eyed-alien.net> said:

>> Um...I'm not sure if this is even possible. Let's forget mDNS and
>> go back to basic IP.
>> Say a multi-homed host has two interfaces both configured with an
>> address in the rage 169.254/16, say 169.254.1.1 and 169.254.2.1 and
>> it wants to initiate a connection to 169.254.3.1, how on earth should
>> it be able to tell on which side 3.1 is located? There might even be
>> one 3.1 on both side that could be completely different hosts.

> You probably would need an extension similiar to the one for IPv6 LLAs.
> i.e. the %bge0 in fe80::2e0:81ff:fe31:9f00%bge0.

(I've not followed the discussion closely, so my apologize in advance
if this message reacts to an off-topic.)

Note that the '%bge0' notation works well thanks to the sin6_scope_id
field of the sockaddr_in6{} structure.  Since sockaddr_in{} doesn't
have such an additional member to solve the ambiguity, the extension
to the IPv4 addresses would not be that trivial.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp