[apps-discuss] Client-defined port -> particular port (was: [dane] AppsDir review of draft-ietf-dane-protocol-19)

[Ondřej Surý <[e-mail]>]

On 1. 5. 2012, at 21:26, Warren Kumari wrote:

> 
> [ -IESG]
> On May 1, 2012, at 3:18 PM, Paul Hoffman wrote:
> 
>> On May 1, 2012, at 11:56 AM, Peter Saint-Andre wrote:
>> 
>>> On 5/1/12 11:02 AM, Tony Finch wrote:
>>>> Peter Saint-Andre <[e-mail]> wrote:
>>>>> 
>>>>> The change from "client-chosen port" to "client-define port" is
>>>>> mystifying to me. Even assuming that "client-defined" was meant, it's
>>>>> not clear to me what a client-defined port is, and I see no effective
>>>>> difference between the old text and the new text.
>>>> 
>>>> I think the mistake is to talk about the client here. The client begins a
>>>> connection to the service's port at that IP address.
>>> 
>>> Usually, yes. Sometimes the client is configured to override the default
>>> port for the given service, as Paul noted.
>>> 
>>> Could we just say "It then begins a connection to a particular port at
>>> that address"? Perhaps the method for determining the port isn't really
>>> relevant in this spec.
>> 
>> Works for me. What do others think?
>> 
>> Current:
>> It then begins a connection to a client-defined port at that address, and sends an initial message there.
>> Proposed:
>> It then begins a connection to a particular port at that address, and sends an initial message there.
> 
> LGTM.

+1

--
 Ondřej Surý -- Chief Science Officer
 -------------------------------------------
 CZ.NIC, z.s.p.o.    --    Laboratoře CZ.NIC
 Americka 23, 120 00 Praha 2, Czech Republic
 mailto:[e-mail]    http://nic.cz/
 tel:[phone]       fax:[phone]
 -------------------------------------------