Re: [Curdle] WG status

OK, that was a bit harsh.

>From my perspective, this objection is exceptionally annoying because it's
a single person requesting a rework of the entire document in order to
change terminology in a way that in my view does not improve clarity, and
does not impact mechanics.

But maybe I'm not seeing some problem that Roumen is seeing. If there's
someone else seeing the same problem Roumen is seeing, I can rework the
document to change this terminology. But I would really not like to do this
unless it's agreed it is necessary by multiple people (and is not objected
by others whose objections are stronger).

On Mon, Apr 17, 2017 at 2:41 AM, denis bider <denisbider.ietf@gmail.com>
wrote:

> I disagree:
>
> - The terminology is not misleading. It has been made further clearer and
> more explicit after your feedback.
>
> - The "server-sig-algs" extension has been in use, under this name, by
> multiple implementations, for over a year. If the terminology were changed
> now, the name of the extension would have to remain. The name of the
> extension would conflict with the terminology you suggest.
>
> - There appears to be no benefit to your suggestion. It would confuse
> things by changing terminology that has already been adopted, with
> terminology that you personally find preferable, without changing any of
> the mechanics.
>
> I consider this a bikeshedding issue, and hold you personally in disregard.
>
>
> On Mon, Apr 17, 2017 at 1:58 AM, Румен Петров <pkixssh@roumenpetrov.info>
> wrote:
>
>> Daniel Migault wrote:
>>
>>> Hi,
>>>
>>> My understanding is that the WG has reached consensus over the following
>>> drafts, and these drafts are ready to be sent to the IESG. If you have any
>>> comments, feel free to provide them as soon as possible.
>>>
>> Consensus?
>>
>>> draft-ietf-curdle-ssh-ext-info-04 <https://datatracker.ietf.org/
>>> doc/draft-ietf-curdle-ssh-ext-info/>
>>>
>> Hmm,
>> "server-sig-algs" is misleading . It is designed against the current
>> rules (RFC) that design "Public Key Algorithms"!
>>
>>
>> [SNIP] <https://datatracker.ietf.org/doc/draft-ietf-curdle-ssh-modp
>>> -dh-sha2/>
>>> draft-ietf-curdle-rsa-sha2-05 <https://datatracker.ietf.org/
>>> doc/draft-ietf-curdle-rsa-sha2/>
>>>
>> Same here. In fact design is for new public key algorithm, but paragraphs
>> state something different.
>>
>> [SNIP]
>>>
>>> Yours,
>>> Daniel
>>>
>> Regards,
>> Roumen Petrov
>>
>> _______________________________________________
>> Curdle mailing list
>> Curdle@ietf.org
>> https://www.ietf.org/mailman/listinfo/curdle
>>
>
>