Mailing-List: contact river-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: river-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4CD9364A.70401@zeus.net.au>
Date: Tue, 09 Nov 2010 21:53:46 +1000
From: Peter Firmstone <jini@zeus.net.au>
User-Agent: Thunderbird 2.0.0.14 (X11/20080531)
MIME-Version: 1.0
To: river-dev@incubator.apache.org
Subject: Re: Discovery - Denial of Service and DNS-SD
References: <4CD64D9A.40904@zeus.net.au> <4CD67C1D.5070404@qcg.nl>
 <4CD68E18.4060504@zeus.net.au> <4CD6A09E.2050000@qcg.nl>
 <4CD70249.2020502@zeus.net.au> <4CD70592.2050007@qcg.nl>
 <4CD70826.3070906@zeus.net.au> <4CD70E98.5050504@qcg.nl>
 <4CD715C6.7020409@zeus.net.au> <4CD72148.2000903@qcg.nl>
 <4CD73C34.4010800@zeus.net.au> <4CD7AC20.4060601@qcg.nl>
 <4CD7E184.8000201@zeus.net.au> <4CD8030B.9080705@qcg.nl>
 <4CD85EAE.4050503@zeus.net.au> <4CD87E79.9040808@zeus.net.au>
 <4CD8B7D7.2040504@zeus.net.au>
In-Reply-To: <4CD8B7D7.2040504@zeus.net.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Peter Firmstone wrote:
> Peter Firmstone wrote:
>> Peter Firmstone wrote:
>>> Sim IJskes - QCG wrote:
>>>> On 11/08/2010 12:39 PM, Peter Firmstone wrote:
>>>>
>>>>> Seeing as we're not interested in Multicast DNS, we're probably 
>>>>> better
>>>>> off utilising Waiter's source and integrating only the 
>>>>> functionality we
>>>>> need into River. I'll ask the original author if he's happy to donate
>>>>> some code.
>>>>
>>>> Or http://www.dnsjava.org/, BSD license, recently updated project. 
>>>> Used by james.
>>>>
>>>> Gr. Sim
>>>>
>>>>
>>> Much better, we don't need to maintain it and can distribute it with 
>>> river as a library.
>>>
>>> Cheers,
>>>
>>> Peter.
>>>
>> Rather than use jini as the service type, which has already been 
>> defined by Daniel Steinberg for any arbitrary Jini service, do you 
>> think we should use jini-discovery as per IANA's service type 
>> definition?
>>
>> jini-discovery  4160/tcp   Jini Discovery
>> jini-discovery  4160/udp   Jini Discovery
>> #                          Mark Hodapp <mark.hodapp&sun.com>  
>>
>>
>> DNS-SRV service type:
>>
>> jini-discovery
>>
>> http://www.dns-sd.org/ServiceTypes.html
>>
> Meaning that in the internet, any port can be used for discovery, 
> provided that the "jini-discovery" DNS-SRV service type is used in DNS 
> records.
>
> Thoughts?
>
> Peter.
>
LookupLocator is used by LookupLocatorDiscovery as little more than a 
String URL parser, to store the host and port information.

ConstrainableLookupLocator extends LookupLocator to support Discovery V2.

For DNS-SRV we could have a utility that searches DNS-SRV records and 
creates ConstrainableLookupLocator instances for each record.  We'd have 
to specify constraints for the utility to set.

Currently the Discovery and Join spec requires a jini://host:port/ or 
jini://host/ syntax for URI's, if no port is specified, the default is used.

Cheers,

Peter.