Re: [Curdle] WG status

denis bider <denisbider.ietf@gmail.com> Mon, 17 April 2017 09:02 UTC

Return-Path: <denisbider.ietf@gmail.com>
X-Original-To: curdle@ietfa.amsl.com
Delivered-To: curdle@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53D6C129513 for <curdle@ietfa.amsl.com>; Mon, 17 Apr 2017 02:02:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qcvxCODWnIIe for <curdle@ietfa.amsl.com>; Mon, 17 Apr 2017 02:02:01 -0700 (PDT)
Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43FF4129AA7 for <curdle@ietf.org>; Mon, 17 Apr 2017 02:02:01 -0700 (PDT)
Received: by mail-qk0-x235.google.com with SMTP id f133so100340813qke.2 for <curdle@ietf.org>; Mon, 17 Apr 2017 02:02:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=0C34AuyWKBUGux+D6uHL7z+Lws0IGG7WREYECHbB8r4=; b=AvMNAqDW/YRxKgTDvVx7ZX030sMoKogPceHHr7XQZcBvlVhJb8iZxbzVqw2K+g4ljD IZigaybuRngLikpPRtlwnhU1QlX/uTWH6EEOuuDn7E/BrEc7D0w5qQmz99ISuEPRyhGA +hRXQzPm6pye1v5pQ0XNP7laz9wibOP2I7wbGGKzHaAcaAGa/be1ahH1CwXnMk/beBGQ dj0RzklqlI8piAfCVpKgoLhvwZfbJOga+nlyrHTtAGGHEzzuU0veEgeXCIfRruYwMzlv zFTdglQaTOf8n6/k8hF/M9jLpT61lR0xa5bwqDa62TDFRaJzxgy9s0czabg7cke9hLr9 llhg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=0C34AuyWKBUGux+D6uHL7z+Lws0IGG7WREYECHbB8r4=; b=CeKvhHlqK5uZSrZBDY0+BoKazjRCGJUx/d2qiVIjCt171EqDOJ7D6wfgg41BGtnGXp PVUB0HElPYs2WRwdYgohTk1EfVAibaXCBb21SU9gG7ewIHOAFfL6TpMXAzevzGWCHudA S9AA6wM71n8Y+K3uYxc8XVphH5Hd1CoUxaT7dR1260OJL2vAWpPnFrYc5jHaOABoBqS8 C6PR4P5Y25+0sdtPSdRU8hYJ1OwP5rwW6wG5AMkYSu8s6zhXJTCGzzs0LGD+9DIfqbDA gQUxJkf1TmB7X1k2cXkQa/rv4Pt9kQBUim06WnvD/mBEGZ1xdv2DmtstvHCnrasYlSwI 1wkQ==
X-Gm-Message-State: AN3rC/6Y0kJ8iRf3JjVGHmuirJpUgAe4m2f+twlsB08SVqsnHIPucF5k WO4qJMDHxHxvY+p/hemNgWR9rAeKmWTVaqI=
X-Received: by 10.55.24.38 with SMTP id j38mr6908724qkh.289.1492419720444; Mon, 17 Apr 2017 02:02:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.12.138.239 with HTTP; Mon, 17 Apr 2017 02:02:00 -0700 (PDT)
In-Reply-To: <CADPMZDBjgpzMKp1UJqWMC_xRZpfce=wOOsE51HwY2dEO73kKeA@mail.gmail.com>
References: <CADZyTkkd-JpsE89z=P10Y0esc1NCZydD5NqMTs8E5xUz-DMT_g@mail.gmail.com> <58F475B5.4090504@roumenpetrov.info> <CADPMZDBjgpzMKp1UJqWMC_xRZpfce=wOOsE51HwY2dEO73kKeA@mail.gmail.com>
From: denis bider <denisbider.ietf@gmail.com>
Date: Mon, 17 Apr 2017 03:02:00 -0600
Message-ID: <CADPMZDBS3yFxWmioNRV+Vx-ThTPW636ydr1fz76vNP52DjAtZA@mail.gmail.com>
To: =?UTF-8?B?0KDRg9C80LXQvSDQn9C10YLRgNC+0LI=?= <pkixssh@roumenpetrov.info>
Cc: curdle <curdle@ietf.org>
Content-Type: multipart/alternative; boundary=001a1142e8f24b0c14054d590bdb
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/2DziaIPlMJfAsu_5Uwa5tuTV6R0>
Subject: Re: [Curdle] WG status
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "List for discussion of potential new security area wg." <curdle.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/curdle>, <mailto:curdle-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/curdle/>
List-Post: <mailto:curdle@ietf.org>
List-Help: <mailto:curdle-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/curdle>, <mailto:curdle-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Apr 2017 09:02:03 -0000

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
>>
>
>