Re: WG Last Call: draft-ietf-sasl-gs2-14

[Simon Josefsson <simon@xxxxxxxxxxxxx>]

Nicolas Williams <Nicolas.Williams@xxxxxxx> writes:

> On Mon, Jul 27, 2009 at 03:43:20PM +0200, Simon Josefsson wrote:
>> > 5). Section 9 says:
>> >
>> >   There's no requirement that any particular GSS-API name-types be
>> >   used.  However, typically SASL servers will have host-based acceptor
>> >   principal names (see [RFC2743] section 4.1) and clients will
>> >   typically have username initiator principal names (see [RFC2743]
>> >   section 4.2).
>> >
>> > This might be trivial, but I am missing the following text from RFC 4752:
>> >   ... targ_name equal to output_name from GSS_Import_Name called with
>> > input_name_type
>> >   of GSS_C_NT_HOSTBASED_SERVICE (*) and input_name_string of
>> >   "service@hostname" where "service" is the service name specified in
>> >   the protocol's profile, and "hostname" is the fully qualified host
>> >   name of the server.
>> >
>> > So possibly reword this paragraph to read:
>> >
>> >   There's no requirement that any particular GSS-API name-types be
>> >   used.  However, typically SASL servers will have host-based acceptor
>> >   principal names (see [RFC2743] section 4.1) and clients will
>> >   typically have username initiator principal names (see [RFC2743]
>> >   section 4.2). When a host-based acceptor principal name is used
>> >   ("service@hostname"), "service" is the service name specified in
>> >   the protocol's profile, and "hostname" is the fully qualified host
>> >   name of the server.
>> >
>> > ?
>> 
>> Nico?
>
> Fine with me.

Great, I've changed my local copy.

/Simon